Reconciliation for SAP in India — TDS, GST, Bank, Settlement
SAP customers in India run FI, MM, SD, and J1IGN India localisation against an Indian banking, GST, and TDS environment that the global SAP modules were not designed for. GR/IR clearing accumulates open items, WT codes need to map to the new TDS payment codes (1001-1092), and GSTR-2B reconciliation against MIRO postings is a manual download-and-compare exercise. TransactIG reads from documented SAP exports — no ABAP, no Z-tables — and runs the matching layer that produces a clean monthly close.
What SAP Handles Natively, and Where the India Reconciliation Gap Appears
What SAP does well
SAP's FI module is the global standard for general ledger and subledger accounting. Document-level integrity, parallel ledgers, multi-currency, multi-company-code consolidation, and a mature audit trail through change documents and table logging are all native. F-03 manual clearing, automatic clearing through F.13 with configured tolerances, and the standard ageing reports (S_ALR_*) work for cases where references are clean.
MM handles the procure-to-pay flow with full three-way match capability (PO → GRN → invoice) and OBYC-driven account determination. SD handles order-to-cash. J1IGN handles GST registers. For a customer with disciplined master data and clean references, SAP's native modules clear the large majority of transactions without intervention.
Where the India gap appears
Indian bank statements arrive with the match key in the narration field, not the structured reference field. SAP's F.13 automatic clearing cannot parse "UPI/VPA customer@hdfc/567890" or "NEFT N012 INV-2024 ABC ENT" — these route to manual clearing through F-03. GR/IR clearing accumulates open items because GRN and invoice arrive in different periods with quantity or price variances inside tolerance.
The new TDS payment-code regime (1001-1092) under Sections 393, 394, 413 of the Income Tax Act 2025 requires reconciliation between SAP WT codes and Form 26AS at code level — not at section level as the legacy WT configuration was built for. GSTR-2B and IMS reconciliation against MIRO postings is a manual export-and-VLOOKUP exercise unless automated.
TransactIG Plug Points on SAP
Six matching surfaces that sit alongside SAP without modifying it, reading from documented exports and writing back only the reconciliation status (via a configurable approach the SAP basis team controls).
Data ingestion
Scheduled exports of FBL3N, FBL1N, FBL5N, MIRO, MIGO, and J1IGN outputs to customer-owned SFTP, or read-only ACDOCA access on S/4HANA. No ABAP, no Z-tables.
Section 393 TDS handling
WT codes mapped to the new payment codes 1001-1092. Reconciliation against Form 26AS and AIS at payment-code level under Sections 393, 394, 413 of the Income Tax Act 2025.
GSTR-2B and IMS
Vendor invoices posted via MIRO matched to the GSTR-2B/IMS feed at GSTIN + invoice + tax-amount level. ITC eligibility and Rule 36(4) flags surfaced.
NACH batch matching
Mandate batch files generated through SAP payment programs reconciled against bank response files. Bounce codes mapped to ageing, re-presentation status visible at SAP document level.
Platform settlements
Razorpay, PayU, Cashfree, Amazon, Flipkart settlement reports disaggregated and matched to SD billing documents and FI customer postings. Platform fees and 18% GST on fees classified for ITC.
Bank statement ingestion
MT940, CAMT.053, CIB Excel, YONO Business, Axis Corporate Online, and Kotak ActivMoney parsed natively, matched to SAP bank subledger entries with narration-pattern extraction.
SAP Integration Architecture
Each row is a discrete data feed configured during implementation. The SAP basis team owns the export configuration; TransactIG owns the matching schema, field mapping, and variance taxonomy on the receiving side.
| SAP source | Export method | Sync cadence | Field mapping | Variance codes |
|---|---|---|---|---|
| FI general ledger | Scheduled FBL3N export to SFTP, or read-only view on ACDOCA (S/4HANA) | Daily or per-period close | GL account → TransactIG voucher class | GL_LINE_UNMATCHED, JOURNAL_MISSING |
| AP vendor open items | FBL1N export, or BAPI_AP_ACC_GETKEYDATEBALANCE for ageing | Daily for active AP, weekly for legacy | Vendor master → counterparty in TransactIG | INVOICE_OPEN, DUPLICATE_INVOICE, MIRO_PENDING |
| AR customer open items | FBL5N export to SFTP | Daily | Customer master → counterparty | CUSTOMER_OPEN, ADVANCE_UNADJUSTED, CREDIT_NOTE_PENDING |
| GR/IR clearing | FBL3N filtered on GR/IR account (e.g. 191100) | Daily | MM document number → match key | GR_PENDING_INVOICE, INVOICE_PENDING_GR, QTY_DIFF, PRICE_DIFF |
| WT (TDS) line items | FBL3N on TDS GL accounts, or table WITH_ITEM extract | Daily | WT code → new payment code (1001-1092) | TDS_NOT_IN_26AS, RATE_MISMATCH, SECTION_RECLASSIFIED |
| GST registers (J1IGN) | Output of J1IGN reports — RG23A-II, RG23C, IGST/CGST/SGST registers | Per GST return cycle | Vendor invoice → GSTR-2B/IMS row | ITC_INELIGIBLE_2B, INVOICE_MISSING_IN_2B, RATE_DIFFERENCE |
Common Reconciliation Gaps in SAP India Deployments
GR/IR balances ageing 90+ days
GRN posted without matching invoice receipt, invoices posted without GRN against blocked stock, partial receipts where MIGO and MIRO quantities disagree inside tolerance.
WT code to Form 26AS mismatch
SAP WT codes configured against legacy sections (194C, 194J) instead of the new payment codes (1001-1092). Form 26AS shows the new code; SAP shows the old. Reconciliation requires the mapping layer.
MIRO bookings not reflected in 2B
Vendor invoice posted in SAP but supplier has not filed GSTR-1, so the invoice is missing from GSTR-2B. ITC is provisional until 2B reflects the line — Rule 36(4) lock applies.
Bank narration vs SAP reference
F.13 automatic clearing cannot extract a cheque or UTR number from a free-text bank narration field. Manual F-03 clearing routes thousands of lines through the finance team every month.
Settlement net of platform fees
Razorpay or Cashfree settles a net amount; SAP SD billing was raised at gross. Without a settlement-disaggregation layer, the bank credit cannot be matched at invoice level.
Intercompany clearing in multi-code
Multi-company-code groups carry intercompany open items that should net to zero across codes. Drift accumulates from timing differences, FX, and one-sided postings — visible only at consolidation.
How TransactIG Works with SAP
Ingest
Scheduled SAP exports drop into customer-owned SFTP. Bank statements, GSTR-2B and IMS feeds, Form 26AS extracts, NACH response files, and platform settlement reports all land alongside on a defined cadence.
Match
SAP GL, vendor, customer, GR/IR, and WT line items matched against the external sources. Narration parsing extracts cheque, UTR, and VPA fragments. Payment-code mapping aligns WT to 1001-1092 codes for 26AS match.
Exception queue
Unmatched items route to a structured queue with variance codes, ageing, suggested resolution, and maker-checker workflow. Cleared items can be returned to SAP for F-03 clearing or netted in TransactIG depending on policy.
Frequently Asked Questions
Does TransactIG require any custom development on the SAP side? +
No. TransactIG reads from documented SAP export interfaces — standard transactions like F-03 line item lists, FBL3N general ledger displays, FBL1N vendor open items, MIRO invoice receipt tables, and J1IGN India localisation outputs. The integration uses scheduled file exports or read-only views from SAP. No ABAP development, no Z-tables, no schema changes, and no user-exit modifications are required. The SAP basis team owns the export configuration; TransactIG owns the matching layer.
How does TransactIG handle GR/IR clearing in SAP? +
GR/IR — the goods-receipt/invoice-receipt clearing account — is one of the most common sources of long-pending open items in SAP FI. TransactIG ingests open items from the GR/IR account (typically a 191100-series account configured via OBYC), matches goods receipts posted through MIGO against invoice receipts posted through MIRO, and routes timing and quantity variances to a structured exception queue. The output is a clean GR/IR ageing report that distinguishes timing differences (invoice expected next period) from genuine variances (price differences, partial receipts, return-to-vendor pending) — the same view auditors examine during statutory audit and tax audit (3CD clause 21).
Which SAP India localisation features does TransactIG work with? +
TransactIG reads from the J1IGN India localisation output for GST registers (RG23A Part-II, RG23C, output and input GST registers) and aligns vendor invoice postings to the GSTR-2B/IMS feed downloaded from the GSTN portal. For TDS, TransactIG reads the withholding tax line items posted via WT codes, maps them to the new payment codes (1001-1092) under Sections 393, 394, 413 of the Income Tax Act 2025, and reconciles against Form 26AS and AIS for the deductor or deductee perspective. The mapping table between SAP WT codes and the new payment-code regime is configured once during implementation.
Does TransactIG work for both S/4HANA and ECC? +
Yes. The integration is interface-level, not version-specific. ECC customers use BAPI-driven extracts or scheduled spool exports of FBL3N/FBL1N/FBL5N reports to SFTP. S/4HANA customers can use the same approach or, where Universal Journal access is available, the standard ACDOCA-based extracts. TransactIG's matching schema is the same in both cases — the bank reconciliation, GR/IR clearing, TDS, and GST modules behave identically whether the source is ECC or S/4HANA Cloud Edition or S/4HANA On-Premise.
How does TransactIG handle three-way match (PO, GRN, invoice) in SAP MM? +
The PO is read from EKKO/EKPO, the GRN from MSEG/MKPF, and the invoice from RBKP/RSEG. TransactIG matches these three documents at line-item level — quantity received versus quantity invoiced versus quantity ordered, price on PO versus price on invoice, tolerance windows on quantity and value as configured in OMR6. Variances route to the exception queue with categorisation: PRICE_DIFF, QTY_SHORT_RECEIPT, QTY_OVER_INVOICE, GR_PENDING_INVOICE, PARTIAL_INVOICE. The three-way match output is the input that AP teams use to release invoices for payment and that auditors examine for ICFR and CARO 2020 evidence.
How long does SAP integration take? +
2 to 4 weeks for most SAP customers. Week one covers the export configuration on the SAP side — scheduled FBL3N/FBL1N/MIRO/J1IGN outputs delivered to a customer-owned SFTP location. Week two maps the SAP chart of accounts, WT codes, GR/IR account, and GST registers to TransactIG's matching schema. Weeks three and four apply matching rule configuration for narration patterns on the Indian bank side, TDS payment-code mapping, GSTR-2B alignment, and the maker-checker workflow. The SAP basis team's effort is bounded to export setup and SFTP credentialing.
Reconciliation that fits the way your SAP system already runs
No ABAP. No Z-tables. No SAP schema changes. 2 to 4 weeks to first reconciled close, ISO 27001:2022 certified, running from AWS Mumbai.