Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A common misconception among Indian finance teams is that a well-implemented ERP solves the reconciliation problem. It does not — and the gap is not a limitation of the ERP vendors but a structural difference between what an ERP is designed to do and what reconciliation requires.
SAP Built-In Reconciliation Limitations
SAP handles the accounting layer for Indian compliance — TDS deduction and posting, GST tax determination, accounts payable and receivable management — with strong India localisation in both ECC and S/4HANA.
What SAP does not do natively:
- Connect to TRACES to download Form 26AS and compare TDS receivables
- Import GSTR-2B JSON from GSTN and match against the purchase register in the SAP MM module
- Reconcile payment gateway settlement files (Razorpay, PayU CSV formats) against SAP revenue postings
- Disaggregate NACH batch credits against individual loan or mandate records
The result: SAP users in India typically have an accurate internal record and an unvalidated external record. The matching between them is done in spreadsheets, outside SAP.
SAP + Reconciliation Layer Architecture
| SAP data source | Exported as | Matched against | External source |
|---|---|---|---|
| TDS receivable (FBL5N) | CSV | Form 26AS | TRACES portal |
| Purchase invoices (FBL1N) | CSV | GSTR-2B | GST portal |
| Bank clearing accounts | MT940 | Bank statement | Bank portal / SFTP |
| Revenue postings | CSV | Gateway settlement | Razorpay / PayU report |
A reconciliation layer connects to SAP via file export or RFC and handles the matching against external sources.
Oracle Financials and the Indian Tax Gap
Oracle Fusion Financials with India localisation covers TDS withholding tax and GST calculation well. The reconciliation gaps mirror SAP’s:
GSTR-2B matching: Oracle does not have a live GSTN API integration in standard deployments. The GSTR-2B JSON must be downloaded monthly and uploaded to Oracle’s GST module — a process that requires the GST reconciliation to happen within Oracle, but only after a manual import step.
Form 26AS vs TDS receivable: Oracle’s withholding tax reports show TDS deducted and expected, but do not connect to TRACES for verification that the deductor actually deposited the challan. Verification requires a separate process.
Platform settlements: Oracle has no pre-built connectors for Indian payment gateways. Settlement reconciliation is done through a manual comparison process or a custom integration.
Tally Reconciliation Capabilities
Tally Prime has the deepest India-specific functionality of the three major ERPs in the SME segment, and it shows in its reconciliation features:
- Bank reconciliation: Tally’s bank reconciliation module handles automated import of bank statements and matching against the cash/bank ledger. Effective for single-bank operations.
- GSTR-2B reconciliation: TallyPrime 3.0 introduced GSTR-2B import and invoice-level reconciliation. Functional for organisations with straightforward supplier bases.
- TDS: Tally handles TDS deduction, challan generation, and Form 26Q/27Q output. It does not automate Form 26AS matching.
The limitations appear at scale: Tally’s GSTR-2B reconciliation requires clean GSTIN master data, and performance degrades above 500 invoices per month in the reconciliation module.
When Your ERP Is Not Enough
The ERP becomes insufficient for reconciliation when any of the following conditions apply:
- Monthly transaction volume exceeds 1,000 items across all reconciliation types
- The organisation uses multiple payment gateways with different settlement formats
- NACH batch reconciliation is required (EMI collections, mandate-based payments)
- The organisation needs to reconcile across multiple entities or bank accounts simultaneously
- Continuous reconciliation (daily or intraday) is needed rather than month-end processing
ERP-Agnostic Reconciliation Infrastructure
An ERP-agnostic reconciliation layer integrates with SAP, Oracle, or Tally through the ERP’s export formats, applies multi-pass matching against external sources, and returns exceptions to the ERP for resolution posting. The ERP remains the system of record; the reconciliation layer validates it.
Reconciliation software India built for the Indian market connects to all three ERP platforms and adds the India-specific matching layers — TDS section-level reconciliation, GSTR-2B invoice matching, NACH disaggregation — that the ERPs do not provide natively.
For bank reconciliation specifically, bank reconciliation software that integrates via MT940 or bank API works with SAP, Oracle, and Tally as the upstream accounting system.
The Institute of Chartered Accountants of India provides guidance on ERP-agnostic reconciliation standards that apply regardless of which accounting system the organisation uses.