Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
An Indian hotel's corporate AR portfolio runs across 30 to 200 contracted accounts with 30, 60, and 90-day credit terms, mixed Local Rate Agreement and Negotiated Rate contracts, monthly statement-of-account billing, a 30-day dispute window per invoice, partial payment allocations across folios, conditional TDS treatment under Section 393(1)(e) for long-stay rent versus no TDS for routine travel, and a strict GSTIN-vs-GSTIN match requirement against each corporate's GSTR-2B view. Manual reconciliation across the PMS folio register, the AR sub-ledger, the GSTR-1 outward register, and corporate remittance advices cannot reliably hold the four-way tie at month-end.
Ingest BTC vouchers tagged with corporate account number and contract code (LRA or NDC) from the PMS, generate the consolidated monthly invoice per corporate at the contracted rate, post to AR with a 30-day dispute window flag, ingest corporate remittance advices and bank NEFT credits, allocate cash against open folios with explicit partial-payment handling, classify each account as rent-treated (TDS payment code 1009 under Section 393(1)(e)) or routine business travel (no TDS), and run a GSTIN-vs-GSTIN match between the hotel's GSTR-1 outward register and the corporate's GSTR-2B for each invoice line.
Corporate master with GSTIN, contract code (LRA/NDC), credit terms (30/60/90/120 days), dispute window length, TDS treatment flag (rent under Section 393(1)(e) versus routine travel), invoice cycle date, and statement-of-account format. Ageing buckets at 30/60/90/120+ days from invoice date. GSTR-1-to-GSTR-2B match tolerance on taxable value and tax period.
A reconciled corporate AR view that shows each BTC folio against its monthly invoice, the consolidated statement-of-account, the corporate's remittance advice, the bank NEFT credit, the typed TDS treatment, the GSTR-1 outward line, and the corporate's GSTR-2B match status — with ageing buckets refreshed daily, the dispute queue clearly separated, and Form 26AS reconciliation evidence ready for quarterly close.
A 200-room business hotel in Gurugram serving 80 active corporate accounts can carry, at any month-end, ₹3 to ₹6 crore of open AR spread across a mix of 30-day, 60-day, and 90-day credit-term contracts. Each corporate has a Local Rate Agreement (LRA) or a Negotiated Rate (NDC) on file, each invoice goes out under a 30-day dispute window, each remittance covers six to forty folios across two or three billing cycles, and each line in the hotel’s GSTR-1 has to match the corporate buyer’s GSTR-2B for the buyer to claim input tax credit. The reconciliation here is not the OTA gross-to-net problem. It is a four-way tie between PMS folio, monthly invoice, statement-of-account remittance, and the GSTN auto-drafted view at the corporate end. This guide covers the BTC voucher flow, GST time-of-supply, ageing and dispute logic, the new TDS regime under Section 393(1)(e) for rent-treated stays, and how the GSTIN-vs-GSTIN match holds the rest together.
What Hotel Corporate Billing in India Involves
Corporate billing — bill-to-company, or BTC — is a credit-sale revenue stream parallel to direct guest payment and OTA settlement. The corporate client signs a master service agreement and a rate sheet, the hotel issues a contract code (LRA, NDC, or a property-specific identifier), and any traveller from that corporate checks in against the BTC account.
- Contract rate negotiation — the LRA is the local rate agreement filed at property level, typically negotiated annually with a confirmed-room-night commitment. The NDC is the negotiated rate that applies across a chain or a region under a master contract. Both carry a contracted room tariff that overrides the rack rate for the corporate’s stays.
- BTC voucher at check-in — the guest signs a voucher referencing the corporate account number and contract code. Folio charges accrue to the corporate, not to the guest’s personal card. Incidentals — mini-bar, laundry, room service — are usually included or excluded per the contract, with policy enforced by the front-office system.
- Monthly invoice cycle — at month-end the hotel consolidates all stays in the period for each corporate into a single tax invoice (or one invoice per contract sub-code) with the underlying folios as line items. Credit terms run 30, 60, or 90 days from invoice date.
- Statement-of-account — alongside the invoice, the hotel sends a statement summarising invoice number, invoice date, gross value, GST, TDS expected, and net payable.
The reconciliation challenge is that revenue is earned and recognised at check-out, the invoice is dated at month-end, and the cash arrives weeks later in a single NEFT credit covering many folios. Without a typed AR sub-ledger that holds the BTC voucher, the consolidated invoice, and the eventual statement payment in one view, month-end reporting and statutory audit both struggle. This is the same evidence problem the hotel reconciliation in India pillar describes for OTA settlements, applied to a slower and lumpier credit-sale stream.
Where Corporate BTC Reconciliation Breaks
GST Time-of-Supply Versus Check-Out Date
Under Section 13 of the CGST Act, time of supply for services is the earlier of invoice date or payment receipt, and the statutory invoicing window for services is 30 days from completion. For BTC, the typical pattern is month-end consolidation, so a guest who checks out on the 5th and the 25th of June is invoiced on the 30th of June with both folios on one tax invoice. GST liability attaches to the invoice date, but revenue recognition under Ind AS 115 attaches to the room-night consumption date. The reconciliation has to keep both dates. If the hotel slips past the 30-day invoicing window, the GST month moves and the corporate buyer’s GSTR-2B for the original month no longer carries the line — which means the corporate cannot claim ITC in the period it expected.
Statement-of-Account Versus Folio-Level Disputes
A corporate AR team typically reconciles at statement-of-account level, while the hotel’s PMS exports folio-level detail. When the corporate raises a dispute — a mini-bar charge the traveller denies, a no-show fee the corporate’s policy excludes, a late check-out fee outside the LRA — the dispute attaches to one folio inside a multi-folio invoice. The 30-day dispute window from invoice date is the contractual cutoff; queries raised inside the window get resolved via credit note before payment, queries raised after become recovery work. Reconciliation has to track dispute status at folio level, partial payments at invoice level, and the resulting open balance at corporate-account level — three different aggregations of the same data.
GSTIN-vs-GSTIN Match Failure
The corporate buyer downloads GSTR-2B every month to claim ITC. Each line in GSTR-2B is auto-drafted from the seller’s GSTR-1 filing. If the hotel filed GSTR-1 with the wrong buyer GSTIN, with a non-canonical invoice-number format, or filed late and missed the period, the line drops from the buyer’s GSTR-2B. The buyer’s AR team then holds the payment until the line appears, which can mean a 30-day delay turns into 60 or 90 days. The hotel’s outward register has to be reconciled against each major corporate’s GSTR-2B view through the GSTN portal before the buyer’s payment cycle, not after.
The Hotel Corporate BTC Reconciliation Process: Step by Step
Step 1 — Capture BTC Vouchers at Source
Tag each BTC voucher in the PMS with corporate account number, contract code (LRA or NDC), folio number, room-nights consumed, traveller name, and check-out date. Distinguish rent-treated long-stay arrangements from routine business travel, because the TDS treatment differs (see Step 4).
Step 2 — Generate the Monthly Tax Invoice
Consolidate all closed BTC folios per corporate per period at the contracted rate. The invoice carries the corporate’s GSTIN, the hotel’s GSTIN, the property’s room-tariff GST slab (12 percent below ₹7,500 or 18 percent at or above ₹7,500), itemised folios, and the statement-of-account. Issue within the 30-day window from the latest folio’s check-out date to keep GST time-of-supply aligned.
Step 3 — Track Ageing and the Dispute Window
Post the invoice to AR with a 30-day dispute flag, then age in 30/60/90/120+ buckets from invoice date. Disputes raised in the dispute window route to a credit-note queue; disputes raised after route to a recovery queue. Partial payments allocate against oldest-open folios first unless the corporate’s remittance advice specifies otherwise.
Step 4 — Apply the Right TDS Treatment
For routine business travel — short-stay, occasion-based — the corporate typically does not deduct TDS. For rent-treated long-stay arrangements where the contract crosses into rent character, the corporate deducts TDS under Section 393(1)(e) of the Income Tax Act 2025, using payment code 1009 in the new payment-code regime. The legacy reference is Section 194I, which Section 393(1)(e) replaces in the 2026 transition; see Section 393 TDS reconciliation and TDS payment codes 1001-1092 for the full mapping. GST law is unchanged; only the income-tax side moves.
Step 5 — GSTIN-vs-GSTIN Match Against GSTR-2B
For each major corporate, pull the buyer’s GSTR-2B view (typically shared by the corporate’s AP team or pulled via authorised access) and reconcile each hotel-issued invoice line against the buyer’s auto-drafted line: GSTIN, invoice number, invoice date, taxable value, GST amount. Any mismatch surfaces before the corporate’s payment cycle, not after a hold.
Variance Taxonomy: Corporate BTC
| Code | Variance | Typical cause | Resolution |
|---|---|---|---|
| BTC-V01 | Folio dispute (in window) | Incidentals dispute, no-show fee | Credit note within 30 days of invoice |
| BTC-V02 | Folio dispute (out of window) | Late escalation by corporate | Recovery process |
| BTC-V03 | Partial payment | Statement-of-account paid in tranches | Allocate against oldest-open folios |
| BTC-V04 | TDS deducted (Sec 393(1)(e)) | Long-stay rent treatment, payment code 1009 | Match against Form 26AS under corporate TAN |
| BTC-V05 | TDS over-deducted | Corporate misclassified routine travel as rent | Refund claim or next-month adjustment |
| BTC-V06 | GSTR-2B line missing | Hotel GSTR-1 filed late or with wrong GSTIN | File amendment, share remittance with corporate |
| BTC-V07 | GSTR-2B taxable value mismatch | Rounding or rate slab error | Issue revised invoice or credit note |
| BTC-V08 | Invoice-number format mismatch | Non-canonical numbering | Standardise series, file amendment |
| BTC-V09 | Cross-period invoice | Folio in month M, invoice in month M+1 | Track both dates, align with corporate GSTR-2B period |
What Automated Corporate BTC Reconciliation Changes
A purpose-built reconciliation software India platform that handles hotels carries the BTC voucher schema, the LRA/NDC contract code, the 30/60/90/120+ ageing buckets, the 30-day dispute window flag, the Section 393(1)(e) TDS classification, and the GSTIN-vs-GSTIN match against GSTR-2B as first-class concepts rather than spreadsheet conventions. The corporate AR sub-ledger reconciles to the bank NEFT credit and the corporate’s remittance advice automatically, partial payments allocate against open folios with audit-trail evidence, the dispute queue is separated from the recovery queue, and the Form 26AS view at quarter-end ties cumulative TDS deducted under the new payment codes. Hotels with substantial BTC books typically see month-end AR close compress from a multi-day exercise into hours of exception review, and — more importantly — the GSTIN-vs-GSTIN match runs before invoice dispatch instead of after a payment hold, which is what removes the 30-to-60-day stretch that kills working capital. For hotels also reconciling guest cards and OTA settlements, the payment gateway reconciliation layer handles the direct-pay side of the same property under one typed-variance framework. For the broader hotel industry reconciliation surface, see the Hotels & Hospitality industry guide.