Skip to main content
Comparison · 15 min read

Payment Reconciliation Software in India: A Vendor-Neutral Guide

Payment reconciliation software in India should be judged on whether it can rebuild each gateway and marketplace payout from orders, fees, taxes, refunds and holds, then match the net to the bank credit. This guide gives the test, fourteen scenario files, a fee-and-tax line catalogue and a score sheet.

Terra Insight
Terra Insight Editorial Team Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 18 November 2026
Domain expertise
TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops
Knowledge Card
Problem

Finance teams buy payment reconciliation software on demos that match clean payouts, then find at month-end that split credits, netted refunds, holds, chargebacks and marketplace tax lines leave settlements unexplained.

How It's Resolved

Choose the kind of tool first, make each product rebuild awkward payouts from orders, fees, taxes, refunds and holds before matching the net to the bank, then run fourteen scenario files from last quarter and score with gates.

Configuration

A settlement-rebuild worksheet, fourteen scenario files with expected results, a fee-and-tax line catalogue showing where each line posts, a data-and-keys checklist and a weighted score sheet with pass-or-fail gates.

Output

A shortlist of tools that tie every settlement to a bank credit or a named exception on your own payouts, classify every deduction line and answer ten month-end questions, filed as evaluation evidence.

Payment reconciliation software in India is easy to show on a clean payout and hard to judge on a real one. The differences appear when a gateway settlement lands as two bank credits, when refunds exceed sales on a slow day, when a marketplace deducts commission, shipping, TCS and TDS from one payout, or when a courier remits cash-on-delivery money short by three orders.

This guide is for the finance head at an e-commerce, D2C, marketplace-seller, fintech or platform business, and for the accountants who run the monthly tie-out of gateway and marketplace settlement. It gives a settlement-rebuild test, fourteen scenario files to build from last quarter’s payouts, a catalogue of fee and tax lines with where each one posts, and a score sheet. No product is named or ranked. Rules cited come from RBI, CBIC, the Income Tax Department and the Department of Financial Services, checked on 18 November 2026.

Every table below is also packaged as a payment reconciliation software evaluation kit (Excel worksheet, scenario templates and score sheet).

What kind of payment reconciliation tool do you need?

Decide the kind of tool before comparing products. A shortlist that mixes a gateway dashboard, an accounting suite and a specialist platform will be compared on the wrong things. Each kind below has a different strength and a different weak point to test.

Kind of toolTypical strengthWhat to test hardest
Gateway or marketplace dashboard and reportsSource data and its own feesMatching to bank and ledger; combining several gateways
Accounting suite or ERP module with bank feedsSame books, no export stepOrder-level detail, fee and tax lines, many-to-one credits
Marketplace-seller tool or order-management moduleMarketplace file formatsGateways and bank, tax lines, ledger posting
Specialist payment reconciliation platformMatching depth and exception workflowImplementation effort, Indian formats, posting to your ERP
Global finance-close platformControl frameworkIndian rails (UPI, NEFT, IMPS, UTR) and Indian tax lines
In-house scripts or BIFit to your dataFormat changes, audit trail, key-person risk

Three questions settle most of the choice. How many gateways, marketplaces and couriers send you money? Do you need order-level tie-out or only settlement-to-bank? And where must the result post: Tally, an ERP, or a data warehouse? A tool that covers only one gateway’s transactions will not help if you collect through three. For how the three kinds of payout differ in structure, see marketplace payout versus gateway payout versus COD remittance.

Can the tool rebuild a payout from orders, fees, taxes, refunds and holds?

This is the test that separates tools. A tool earns trust when it can rebuild each payout from its parts and only then match the net to the bank credit. Matching the bank credit to a settlement total proves little; rebuilding the total proves the tool understood every line.

The rebuild, in one line:

Net payout = sales captured − refunds − fees − GST on fees − chargebacks and dispute fees ± adjustments − holds + releases − tax lines shown by a marketplace.

Test it on an awkward payout, not a clean one.

Worked example (illustrative). A gateway settlement of ₹1,84,300 reaches the bank as two credits: ₹1,00,000 on one day and ₹84,300 on the next. The settlement report shows:

Line on the settlement reportAmount
Sales captured₹2,00,000
Refunds− ₹9,000
Gateway fee− ₹3,800
GST on the gateway fee (separate line)− ₹684
Chargeback debit with its dispute fee− ₹2,216
Net settlement₹1,84,300
Bank credit 1 (day 1)₹1,00,000
Bank credit 2 (day 2)₹84,300

Check: 2,00,000 − 9,000 − 3,800 − 684 − 2,216 = 1,84,300, and 1,00,000 + 84,300 = 1,84,300. A sound tool rebuilds ₹1,84,300 from the five lines, groups the two credits by UTR and settlement ID, and closes the settlement. A weak tool compares ₹1,84,300 with each credit separately and raises two false exceptions, or matches on amount alone and never notices the chargeback.

Ask the vendor to rebuild three of your own payouts in front of you: one with a negative day, one split across credits and one with a chargeback. For the difference between the settlement and what arrives in the bank, see settlement versus payout on a gateway.

Which files, fields and keys must it read?

Payment reconciliation joins at least four sources, and each has its own key. A tool that matches every source on amount and date will produce confident wrong matches the moment two orders share a value.

SourceTypical fieldsKey to match on
Gateway settlement reportSettlement ID, payment ID, order ID, fee, GST, refund, adjustmentSettlement ID and UTR for the credit; order or payment ID below it
Marketplace payout reportSettlement or payout ID, order ID, SKU, commission, fees, TCS, TDSPayout ID to the bank credit; order ID to your sales
Bank statementDate, narration, UTR or reference, creditUTR in the narration or the reference field
Order or sales register (OMS or ERP)Order ID, invoice, amount, dateOrder ID
Courier COD remittanceAWB, COD amount, remittance dateAWB or order ID

Three questions to ask about inputs:

  1. Format change. When a gateway or marketplace adds or renames a column, what happens? A weak answer is “send us the new file and we will map it”. A good answer names who changes the mapping, how long it takes and whether old periods still re-run.
  2. Narration parsing. Indian bank narrations carry the UTR in different places for NEFT, RTGS, IMPS and UPI. Ask to see how the tool reads your bank’s narrations, not a sample bank’s.
  3. Rail keys. For UPI, the UTR, the RRN and the gateway’s own reference can all differ. Ask which one the tool matches on for each rail.

Column-by-column guides: gateway settlement report columns and how to find a gateway settlement in your bank statement.

How should fees and taxes be treated?

Every deduction on a payout is a separate accounting line, and a tool that lumps them into “charges” leaves your books unable to claim credits or spot overcharges. The catalogue below lists each line, how it usually posts on your side and the rule that applies.

Line on the payoutTypical treatment on your sideRule to know
Gateway fee or MDRExpenseRate and effective date per your merchant agreement; UPI charges change once the new MDR starts on the date NPCI notifies
GST on the feeInput credit if eligibleShown as its own line; card settlements up to ₹2,000 by payment aggregators are exempt per CBIC Circular 245/02/2025-GST
Marketplace commission, fixed fee, shipping and collection feeExpense with GSTAs per the marketplace’s tax invoice
GST TCS under section 52Tax credit to match against your ledger and returns0.5 percent in total (0.25 percent CGST plus 0.25 percent SGST or UTGST) from 10 July 2024; 1 percent before
Income-tax TDS under section 194-OTax credit to match against your credit statement0.1 percent of the gross amount from 1 October 2024; 1 percent before
Chargeback and dispute feeExpense, or receivable until the outcomeDisputes follow the gateway’s process and the RBI turnaround framework
Hold or rolling reserveAsset until releasedGateway terms
Instant-settlement feeExpenseGateway terms

Points that trip tools up:

  • Outdated tax rates. Several vendor and third-party pages still print 1 percent for TCS or TDS on marketplace payouts. Ask the vendor which rate its tool applies to each period and whether it handles periods before and after the change. A tool computing expected TDS at 1 percent on a current payout will report a false shortfall on every order.
  • Section 194-O exemption. No deduction is made where the seller is an individual or HUF whose gross sales through the operator in the year do not exceed ₹5 lakh and who has given PAN or Aadhaar. From 1 April 2026 the same deduction sits in section 393 of the Income-tax Act, 2025.
  • UPI charges. The Department of Financial Services FAQ sets an MDR of 0.4 percent on person-to-merchant UPI transactions above ₹2,000, capped at ₹300 per transaction for ₹75,000 and above; UPI payments up to ₹2,000 and person-to-person transfers carry none. These charges apply only once the new charges start, on a date NPCI is to notify. A tool must apply fees by transaction date, not by the date you load the file.
  • Settlement timing is contractual. RBI’s 2025 Master Direction on payment aggregators leaves the time to credit a merchant to the agreement between the aggregator and the merchant. A “T+1” or “T+2” cycle is a commercial term of your gateway, not a regulation, so the tool should take it from your agreement.

For fee-level checks, see MDR fee reconciliation; for the tax lines on a seller payout, see TDS 194-O and TCS 52 on a seller payout; and for GST on the fee line, see is GST charged on payment gateway fees.

Fourteen scenarios to run from last quarter’s payouts

Give every shortlisted vendor the same fourteen scenario files, built from your own closed payouts and masked where needed, with the expected result written down before the run. These are the cases that break tools built on clean samples.

IDScenarioWhat a sound tool does
S1Negative or zero net payout (refunds and fees exceed sales)Shows a debit or carry-forward, not an error
S2One settlement, two or more bank creditsGroups them (the worked example above)
S3Several settlements in one bank creditSplits the credit back into settlements
S4Settlement dated the 30th, credit on the 2ndTiming item at month-end with its age
S5Partial refund after the settlementTies the refund to the original order and the later payout
S6Chargeback and dispute feePosts the debit, links it to the order, tracks the outcome
S7Fee change mid-month, including any change in UPI charges on the date NPCI notifiesApplies the old and new fee by transaction date; shows the effective date used
S8GST on feesSeparates the GST amount; shows it as creditable or not as per your rule
S9Marketplace payout with commission, fixed fee, shipping fee, TCS and TDS linesClassifies each line: expense, tax credit to match later, or receivable
S10Courier COD remittance short by a few ordersNames the orders and the courier’s report
S11Instant settlement with its feeSeparates the instant-settlement fee
S12Rolling reserve or hold and its later releaseTracks the hold as an asset with its release date
S13UPI credits where UTR, RRN and gateway reference differMatches on the right key per rail
S14Duplicate settlement line or reused referenceFlags it; does not net it silently

For chargebacks in S6, the RBI circular of 20 September 2019 sets turnaround times for failed transactions (for example, auto-reversal within T+5 days for a card or UPI merchant payment debited without confirmation), and the 2025 Master Direction requires aggregators to follow it in their dispute process. The tool should track each dispute from debit to outcome; see chargeback reconciliation.

Ten questions your first month-end output must answer

A tool that passes the scenarios should also produce a month-end output that answers these ten questions without a spreadsheet on the side. Ask each vendor to show the screen or export that answers each one, on your data.

#Question the output must answerWhy it matters
1Which orders were paid, and which are unpaid or failed?Basic completeness
2Which transactions were paid in one period but settled in another?Timing items at month-end
3Which gateway payments have no matching internal sale?Leakage on the sales side
4Which sales are not yet disbursed?Receivable ageing
5Which settlement lines have no bank credit, and which bank credits have no settlement?Both directions of the tie-out
6Which remittances were short, and by how much?Courier and marketplace shortfalls
7Which orders were returned or marked RTO, and did the return trigger a reversal?Refund and return leakage
8What was deducted, line by line (fee, GST on fee, commission, TCS, TDS, hold)?Fee and tax classification
9Which items are open, how old are they, and who owns each?Exception discipline
10Can I re-run last month and get the same answer?Repeatability

Marketplace and cash-on-delivery payouts

Marketplace payouts carry more deduction lines than gateway settlements, and COD money arrives through a courier on its own schedule. Test both separately; a tool strong on gateways can be weak on marketplaces and the other way round.

Illustrative marketplace payout. Orders of ₹1,25,000 settle as one payout:

LineAmount
Orders₹1,25,000
Commission− ₹14,000
GST on commission− ₹2,520
Shipping fee− ₹6,500
GST on shipping fee− ₹1,170
Refunds on returned orders− ₹8,000
GST TCS (section 52)− ₹500
Income-tax TDS (section 194-O)− ₹125
Net payout₹92,185

Check: 1,25,000 − 14,000 − 2,520 − 6,500 − 1,170 − 8,000 − 500 − 125 = 92,185. The amounts are illustrative; the TCS and TDS lines are computed by the marketplace on its own bases, so the tool should read them from the report and then match them to the TCS credit on the GST portal and the TDS credit in your annual statement, not recompute them blindly.

What to check on marketplace and COD files:

  • Each line is classified (expense, GST credit, TCS credit, TDS credit, receivable), not netted.
  • Returns and RTO orders reverse the original sale and its fees.
  • The COD remittance is matched by AWB or order ID to the courier report, and short remittances list the missing orders.
  • Under the 2025 Master Direction, an aggregator’s escrow account may not be used for cash-on-delivery transactions, so COD money follows a different path from prepaid money and the tool should treat it as a separate stream.

Column guides: marketplace settlement report columns, COD versus prepaid settlement reconciliation and the marketplace fee audit.

How should exceptions, posting and audit work?

Matching is half the job. The other half is what happens to the items that do not match, how the result reaches your books and whether an auditor can follow it.

AreaWhat good looks likeHow to test
Exception queueEach item has a reason, an age and an ownerWalk the queue after the scenario runs
Write-offs and adjustmentsApproved by a second person; reason capturedTry a write-off as a junior user
PostingJournal entries for fees, GST, TCS, TDS and holds post to the right ledgersPost one month to a sandbox of your ERP or Tally
Audit trailEvery match, rule change and override logged by user and timeAsk for an auditor-style sample of twenty settlements
Re-runsSame inputs give the same result, with run IDs and rule versions stampedRe-run last month

Scoring rubric, gates and red flags

Score in two steps. First apply gates: a tool that fails any gate is out, whatever its total. Then weight the dimensions. The weights are an example to adapt, not a standard.

Gates (pass or fail): every settlement ties to a bank credit or becomes a named exception; nothing is netted silently; the worked-example payout rebuilds exactly; re-runs give the same result with versions and run IDs stamped; data storage location and sub-processors are disclosed in writing.

DimensionWeightTested by
Rebuilds net payout from components20The rebuild test and S1 to S6
Handles Indian rails and keys15S13 and the bank-credit tests
Fee and tax line classification15S7 to S9
Exceptions: reason, age, owner10Queue walk-through
Formats and change handling10The format-change question
Posting to ledger and ERP10One month to a sandbox
Audit trail and exports10Auditor-style sample
Security and data location5Written answers
Scale and time to result5A run at three times normal volume
Total100

Score each dimension 0 to 5, multiply by its weight and divide by 5. On security, RBI’s circular of 6 April 2018 requires payment system data to be stored only in India, and the 2025 Master Direction applies that requirement to payment aggregators. Whether it reaches a reconciliation vendor depends on the vendor’s role, so ask in writing where your settlement data is stored and processed. You can also check whether a gateway in a pitch appears on RBI’s published list of payment aggregators. For a wider view of categories, see comparing reconciliation platforms for India.

Red flags. Pause the evaluation if a tool:

  • quotes an accuracy or “percent of sales recovered” figure with no method behind it;
  • computes TCS or TDS at outdated rates;
  • matches on amount and date only;
  • lumps fee lines together;
  • cannot handle a settlement split across credits;
  • treats UPI as one rail with one key;
  • answers every format change with “send us the file”;
  • keeps no per-line audit trail;
  • covers only its own gateway’s transactions when you use several.

Where Terra Insight fits today

Gateway and marketplace settlement reconciliation is on the TransactIG roadmap. Delivered today are TDS reconciliation and bank-to-books matching, with an exception queue, exports and presets, which covers matching each settlement credit in your bank statement to your books. For the category view, see payment gateway reconciliation; use this guide’s tests on any tool you evaluate.

Primary reference: RBI Master Direction on Regulation of Payment Aggregators, 2025 — where the RBI sets the rules for escrow, merchant settlement, disputes and data storage that apply to payment aggregators.

Frequently Asked Questions

What is the best software for payment reconciliation?
There is no single best product. The right tool depends on how many gateways and marketplaces you use, your order volume and your ERP. Decide the kind of tool first, then make each shortlisted product rebuild a few awkward payouts from orders, fees, taxes, refunds and holds, run fourteen scenario files from last quarter and score the results with gates.
What is the difference between settlement and payout?
A settlement is the batch of transactions a gateway or marketplace closes for a period, with its fees, taxes, refunds and adjustments. A payout is the money that actually reaches your bank, which may arrive as one credit or several and may combine more than one settlement. Reconciliation has to tie both: orders to the settlement, and the settlement to the bank credit.
Why does my settlement differ from my sales?
Because the payout is a net figure. Refunds, gateway fees or MDR, GST on those fees, chargebacks and dispute fees, holds or rolling reserves and, on marketplaces, commission, shipping fees, TCS and TDS are all deducted before the money moves. A sound tool lists each deduction by line so that sales minus deductions equals the credit.
Is GST charged on payment gateway fees?
Gateway fees usually carry GST, and the settlement report shows it as a separate line next to the fee, which you may be able to claim as input credit. A CBIC circular of January 2025 exempts settlement of card transactions up to ₹2,000 by RBI-regulated payment aggregators, but not gateway services. Confirm the rate on your invoice and with your Chartered Accountant.
How do I match a gateway credit in my bank statement?
Match the bank credit to the settlement using the UTR in the narration or reference field and the settlement ID on the gateway report, not the amount alone. Then tie the orders or payment IDs inside that settlement to your sales register. Where one settlement arrives as two credits, or two settlements arrive as one, group them before matching.
Can AI do payment reconciliation?
Software can automate most matching of settlements, bank credits and orders, whatever technique it uses. What matters is whether each match carries a recorded reason, whether a re-run gives the same answer, and whether a person approves write-offs and rule changes. Our guide on what to make an AI reconciliation vendor prove sets out the tests.
Do UPI MDR charges change how I should test a tool?
Yes. Once the new UPI charges start on the date NPCI notifies, person-to-merchant UPI payments above ₹2,000 will carry an MDR. A tool should apply the old and new fee by transaction date, show the effective date it used and keep the UTR, RRN and gateway reference apart, because UPI keys differ from card keys.

See how TransactIG handles reconciliation for your industry

Configuration takes 2–4 weeks. No code development required. ISO 27001:2022 certified.