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.
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.
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.
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 tool | Typical strength | What to test hardest |
|---|---|---|
| Gateway or marketplace dashboard and reports | Source data and its own fees | Matching to bank and ledger; combining several gateways |
| Accounting suite or ERP module with bank feeds | Same books, no export step | Order-level detail, fee and tax lines, many-to-one credits |
| Marketplace-seller tool or order-management module | Marketplace file formats | Gateways and bank, tax lines, ledger posting |
| Specialist payment reconciliation platform | Matching depth and exception workflow | Implementation effort, Indian formats, posting to your ERP |
| Global finance-close platform | Control framework | Indian rails (UPI, NEFT, IMPS, UTR) and Indian tax lines |
| In-house scripts or BI | Fit to your data | Format 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 report | Amount |
|---|---|
| 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.
| Source | Typical fields | Key to match on |
|---|---|---|
| Gateway settlement report | Settlement ID, payment ID, order ID, fee, GST, refund, adjustment | Settlement ID and UTR for the credit; order or payment ID below it |
| Marketplace payout report | Settlement or payout ID, order ID, SKU, commission, fees, TCS, TDS | Payout ID to the bank credit; order ID to your sales |
| Bank statement | Date, narration, UTR or reference, credit | UTR in the narration or the reference field |
| Order or sales register (OMS or ERP) | Order ID, invoice, amount, date | Order ID |
| Courier COD remittance | AWB, COD amount, remittance date | AWB or order ID |
Three questions to ask about inputs:
- 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.
- 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.
- 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 payout | Typical treatment on your side | Rule to know |
|---|---|---|
| Gateway fee or MDR | Expense | Rate and effective date per your merchant agreement; UPI charges change once the new MDR starts on the date NPCI notifies |
| GST on the fee | Input credit if eligible | Shown 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 fee | Expense with GST | As per the marketplace’s tax invoice |
| GST TCS under section 52 | Tax credit to match against your ledger and returns | 0.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-O | Tax credit to match against your credit statement | 0.1 percent of the gross amount from 1 October 2024; 1 percent before |
| Chargeback and dispute fee | Expense, or receivable until the outcome | Disputes follow the gateway’s process and the RBI turnaround framework |
| Hold or rolling reserve | Asset until released | Gateway terms |
| Instant-settlement fee | Expense | Gateway 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.
| ID | Scenario | What a sound tool does |
|---|---|---|
| S1 | Negative or zero net payout (refunds and fees exceed sales) | Shows a debit or carry-forward, not an error |
| S2 | One settlement, two or more bank credits | Groups them (the worked example above) |
| S3 | Several settlements in one bank credit | Splits the credit back into settlements |
| S4 | Settlement dated the 30th, credit on the 2nd | Timing item at month-end with its age |
| S5 | Partial refund after the settlement | Ties the refund to the original order and the later payout |
| S6 | Chargeback and dispute fee | Posts the debit, links it to the order, tracks the outcome |
| S7 | Fee change mid-month, including any change in UPI charges on the date NPCI notifies | Applies the old and new fee by transaction date; shows the effective date used |
| S8 | GST on fees | Separates the GST amount; shows it as creditable or not as per your rule |
| S9 | Marketplace payout with commission, fixed fee, shipping fee, TCS and TDS lines | Classifies each line: expense, tax credit to match later, or receivable |
| S10 | Courier COD remittance short by a few orders | Names the orders and the courier’s report |
| S11 | Instant settlement with its fee | Separates the instant-settlement fee |
| S12 | Rolling reserve or hold and its later release | Tracks the hold as an asset with its release date |
| S13 | UPI credits where UTR, RRN and gateway reference differ | Matches on the right key per rail |
| S14 | Duplicate settlement line or reused reference | Flags 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 answer | Why it matters |
|---|---|---|
| 1 | Which orders were paid, and which are unpaid or failed? | Basic completeness |
| 2 | Which transactions were paid in one period but settled in another? | Timing items at month-end |
| 3 | Which gateway payments have no matching internal sale? | Leakage on the sales side |
| 4 | Which sales are not yet disbursed? | Receivable ageing |
| 5 | Which settlement lines have no bank credit, and which bank credits have no settlement? | Both directions of the tie-out |
| 6 | Which remittances were short, and by how much? | Courier and marketplace shortfalls |
| 7 | Which orders were returned or marked RTO, and did the return trigger a reversal? | Refund and return leakage |
| 8 | What was deducted, line by line (fee, GST on fee, commission, TCS, TDS, hold)? | Fee and tax classification |
| 9 | Which items are open, how old are they, and who owns each? | Exception discipline |
| 10 | Can 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:
| Line | Amount |
|---|---|
| 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.
| Area | What good looks like | How to test |
|---|---|---|
| Exception queue | Each item has a reason, an age and an owner | Walk the queue after the scenario runs |
| Write-offs and adjustments | Approved by a second person; reason captured | Try a write-off as a junior user |
| Posting | Journal entries for fees, GST, TCS, TDS and holds post to the right ledgers | Post one month to a sandbox of your ERP or Tally |
| Audit trail | Every match, rule change and override logged by user and time | Ask for an auditor-style sample of twenty settlements |
| Re-runs | Same inputs give the same result, with run IDs and rule versions stamped | Re-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.
| Dimension | Weight | Tested by |
|---|---|---|
| Rebuilds net payout from components | 20 | The rebuild test and S1 to S6 |
| Handles Indian rails and keys | 15 | S13 and the bank-credit tests |
| Fee and tax line classification | 15 | S7 to S9 |
| Exceptions: reason, age, owner | 10 | Queue walk-through |
| Formats and change handling | 10 | The format-change question |
| Posting to ledger and ERP | 10 | One month to a sandbox |
| Audit trail and exports | 10 | Auditor-style sample |
| Security and data location | 5 | Written answers |
| Scale and time to result | 5 | A run at three times normal volume |
| Total | 100 |
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.
- ▸ RBI, Master Direction on Regulation of Payment Aggregator (PA), 15 September 2025
- ▸ RBI, Storage of Payment System Data, 6 April 2018
- ▸ RBI, Harmonisation of TAT and customer compensation for failed transactions, 20 September 2019
- ▸ Department of Financial Services, FAQs on MDR on select UPI (P2M) transactions
- ▸ Income Tax Department, section 194-O of the Income-tax Act, 1961
- ▸ CBIC, Notification No. 15/2024-Central Tax (TCS rate under section 52)
- ▸ CBIC, Circular No. 245/02/2025-GST (card settlements up to ₹2,000 by payment aggregators)