Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Oracle Fusion Cloud ERP's India Localization module handles TDS withholding and GST tax determination through release 24C but does not pull GSTR-2B JSON via GSTN API, does not match Form 26AS, and does not parse payment gateway settlement files from Razorpay, PayU, or Cashfree — forcing large Indian enterprises on Oracle Fusion to reconcile statutory and gateway data outside the ERP.
Bolt an external reconciliation layer on top of Oracle Fusion via REST API pulls for AP invoices, GL journals, and bank statements, BI Publisher scheduled export to SFTP/UCM for bulk data, and FBDI inbound to write cleared-status updates back to Fusion. Ingest Form 26AS, GSTR-2B JSON, gateway settlement files externally and run multi-pass matching with tolerance bands, then clear items via FBDI.
Oracle Fusion connector with REST endpoints for AP_INVOICE_DISTRIBUTIONS_ALL, XLA_AE_LINES, GL_JE_LINES, JG_ZZ_* India tax tables, BI Publisher report templates scheduled via Enterprise Scheduler, FBDI import zip templates for cleared-status posting, and gateway adapter library for Razorpay, PayU, Cashfree.
A reconciled Oracle Fusion FI ledger with statutory (26AS, GSTR-2B) and gateway (Razorpay/PayU/Cashfree) variances all matched and cleared via FBDI writeback — no manual JSON uploads, TDS and ITC positions reliable at close, and audit trail surviving Oracle and statutory review.
Oracle Fusion Cloud ERP is positioned as the enterprise-grade ERP of choice for large Indian entities after SAP. Its India Localization module — available in all Financials releases from 2020 onwards — covers TDS withholding and GST tax determination. What it does not cover is the reconciliation step against external authorities: Form 26AS, GSTR-2B, bank statements, gateway settlements. This guide explains the boundary.
What Oracle Fusion India Localisation Covers
The India Localization module, activated through the Manage Tax configuration pages, delivers:
- Withholding tax codes for TDS sections (194C, 194J, 194I, 194Q, 194O, 195, and all active sections as of the FY 2024–25 schedule)
- GST tax determination on AP and AR transactions through tax jurisdictions
- GSTR-1 outward supply report generation as a JSON file for upload to gst.gov.in
- Form 26Q quarterly TDS return XML generation
- PAN-at-invoice-level validation during invoice entry
What it does not deliver: automated matching of these outputs against what the tax portals actually reflect.
Where Oracle Fusion Reconciliation Stops in India
GSTR-2B vs AP invoice register
Oracle’s GST Reconciliation dashboard accepts GSTR-2B JSON but requires a manual download from the GST portal each month. Matching is invoice-level (GSTIN + invoice number + date + taxable value). Supplier-entry errors — a swapped digit in the invoice number, a missing space in the GSTIN — produce line-level mismatches that the dashboard flags but does not auto-resolve.
TDS receivable vs Form 26AS
Oracle tracks TDS payable with high fidelity. TDS receivable, the amount deducted by the entity’s customers on payments received, lives in revenue postings at the AR level and must be matched against Form 26AS. Oracle has no TRACES connector. Verification happens in a spreadsheet or in an external layer.
Platform settlement and NACH batch
Oracle Cash Management consumes bank statements at the aggregate level. Razorpay’s net payout with MDR and GST-on-MDR deductions, a Flipkart settlement with commission and shipping fee splits, a NACH batch credit with 200+ mandate outcomes — none of these are parsed by Cash Management.
Oracle Fusion Integration Options for Reconciliation
| Integration type | Direction | Typical use | Data format |
|---|---|---|---|
| REST API | Pull / Push | AP invoices, GL journals | JSON |
| BI Publisher + SFTP | Outbound | Scheduled bulk extract | CSV, XML |
| FBDI import | Inbound | Status updates, cleared flag | Zipped CSV |
| OTBI analytics | Outbound | Ad-hoc reconciliation queries | CSV, Excel |
A reconciliation layer connects via a combination of these. The reconciliation software India category includes tools that pre-build the BIP export templates and the FBDI return path specifically for Oracle Fusion in India, including the India-specific fields like GSTIN, PAN, section code, and challan number.
For GST-specific reconciliation, GST reconciliation software reads GSTR-2B JSON, compares against AP extracts from JG_ZZ tables, and returns invoice-level match outcomes that can be written back to Oracle via FBDI.
India-Specific Considerations
Oracle’s India Localization module has quarterly release updates, and the TDS section list is refreshed as CBDT notifies new sections — for instance, the addition of 194T for partner remuneration was supported from release 24A. Compliance teams should map every active section in Oracle’s setup to the rate and threshold in force for the assessment year. The reconciliation in SAP, Oracle and Tally India guide covers the parallel gaps in other ERPs, and the GSTR-2B reconciliation guide details the matching logic that sits outside Oracle’s GST Reconciliation dashboard. Oracle’s full India Localization setup is documented on Oracle Fusion Financials documentation.
The FAQ below addresses the most common Oracle-India reconciliation questions.