Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Restaurant POS terminals accept eight payment instruments — UPI, debit, domestic credit, international credit, wallet, BNPL, food card, prepaid — each with a different MDR, settlement cycle, and refund pattern, but the bank credit lands as a single net figure that hides the instrument mix.
Reconstruct gross sales from the gateway settlement file at transaction level. Apply instrument-level MDR (UPI 0%, debit 0.4-0.9%, domestic credit 1.5-2%, international 2.5-3.5%) to derive expected MDR. Match each settlement batch to the bank credit narration. Book gross revenue with output GST, MDR as expense with 18% GST as ITC, and refunds in the cycle they reverse. T+1 to T+3 timing is reconciled via a payments-receivable ageing ledger.
POS-terminal connectors for Pine Labs, MSwipe, Innoviti, Razorpay POS, Paytm-for-Business; instrument-level MDR rate cards by acquirer; settlement-cycle calendars (T+1 vs T+2 vs T+3); refund-reversal mapping; bank statement ingestion with acquirer-narration parsing.
Per-instrument gross sales, per-acquirer MDR with ITC claim, refund reversals applied to the correct period, and a payments-receivable ageing report that shows which settlements are still in-flight versus credited.
A 12-outlet casual-dining chain in Mumbai accepts payments through Pine Labs at four outlets, MSwipe at six, and a mix of Razorpay POS and Paytm-for-Business at the remaining two. UPI volumes are 45% of transactions, credit cards 30%, debit cards 20%, and the rest a mix of wallets and BNPL. The bank credits the operating account every other day with a narration like “PINELABS SETTLEMENT 24042026” — a single number that compresses 800 transactions across five instruments. This article is for finance and audit teams running multi-acquirer POS estates at Indian restaurants.
What Restaurant POS Payment Gateway Reconciliation Involves
Restaurant POS payment gateway reconciliation is the process of matching three data sets for every settlement period: the POS terminal transaction log (gross sale value, instrument, time, terminal ID), the gateway or acquirer settlement file (MDR by instrument, GST on MDR, refunds reversed in the cycle, payout batch reference), and the bank credit narration. The output is gross revenue split by instrument, an MDR expense with claimable ITC, and a payments-receivable ledger that ages each settlement batch from sale date to bank credit date.
The complication is that no two acquirers structure their settlement file the same way. Pine Labs splits by terminal ID and instrument. MSwipe groups by merchant ID and date. Razorpay’s POS product follows the API gateway settlement format. Paytm-for-Business uses its own QR-merchant payout structure. The reconciliation must normalise these into a common shape before matching back to the POS sale log.
How the Three-Way Match Works
Reconstructing Gross from Net Settlement
The settlement file shows gross transaction value, MDR deducted, GST on MDR deducted, refunds applied in the cycle, and the net payout. The reconciliation reads the gross figure as revenue (not the net) and books MDR plus GST on MDR as separate expense and ITC entries. Booking the net as revenue is the single most common error and it understates output tax filed in GSTR-3B.
Matching Settlement to Bank Credit
The bank credit narration carries the acquirer’s merchant ID and a settlement batch reference. The reconciliation matches the batch to the corresponding settlement file payout-batch ID and confirms the net amount agrees to the rupee. Variances are usually fee adjustments — chargebacks, dispute reversals, or platform-fee true-ups — which appear as separate negative lines in the next settlement.
Refund Reversal Mapping
A guest refund processed on the terminal flows back through the same instrument. The gateway reverses the original transaction, often in the next settlement cycle. The reconciliation matches the refund to the original sale by transaction reference, reverses revenue and output GST, and applies a credit note in GSTR-1 if the refund crosses a filing period. MDR on the original transaction is usually not refunded by the acquirer.
Restaurant POS Acquirer Reference
| Acquirer | Default Settlement | UPI MDR | Card MDR Range | GST Invoice |
|---|---|---|---|---|
| Pine Labs | T+1 cards, T+1 UPI | 0% | 0.4% to 2% | Monthly merchant tax invoice |
| MSwipe | T+1 standard | 0% | 0.5% to 2% | Monthly merchant statement |
| Razorpay POS | T+2 cards, T+1 UPI | 0% | 1.75% to 2% | Razorpay dashboard tax invoice |
| Paytm-for-Business | T+1 UPI, T+2 cards | 0% | 1.5% to 2% | Paytm Business tax invoice |
| PayU | T+1 to T+2 | 0% | 1.75% to 2.5% | PayU monthly invoice |
India Compliance Angle: GST Output and ITC on MDR
Restaurant supply attracts 5% GST without ITC for standalone restaurants under the composition-style notification, or 18% with ITC for restaurants in specified hotels. The output GST is collected on gross sales — the bank net credit is irrelevant for output tax computation. On the input side, GST on MDR at 18% is ITC-eligible only for restaurants on the 18%-with-ITC track. Composition or 5%-without-ITC restaurants book MDR and the GST on MDR together as expense; no ITC claim arises. Misclassifying which track the restaurant operates on is a recurring error in multi-format chains where some outlets are inside hotels and others are standalone — the GST track is per outlet, not per chain.
Finance teams using payment gateway reconciliation tooling can normalise Pine Labs, MSwipe, Razorpay, and Paytm settlement files into a single ledger that ages each batch from sale to credit. Reconciliation software India extends this to handle the multi-outlet chain rollup with per-instrument MDR and ITC tracking. The NPCI publishes UPI merchant settlement rules including the zero-MDR notification that governs the 0% UPI rate.
For the restaurant chain industry surface, see the Restaurant Chains industry guide. For the buying-intent surface covering this rail, see the restaurant reconciliation software for India overview, and for a head-to-head against the aggregator-side reconciliation tool category, see TransactIG vs Cointab.
The following questions address the POS payment gateway reconciliation issues restaurant operators encounter most frequently.