GSTR-2B Reconciliation with Oracle Fusion: Setup Guide

Input tax credit (ITC) in India depends on what your suppliers report, not only on what you record. If an invoice in your Oracle Fusion Payables ledger does not appear in your GSTR-2B statement, the credit is at risk. Finding those gaps by hand every month is slow and error-prone, especially with thousands of supplier invoices.

This guide explains how to set up GSTR-2A/2B reconciliation with Oracle Fusion as the book of record. It is written for finance controllers, tax teams and Oracle consultants. It covers the data you need, the matching rules, the controls, and how to test it.

GSTR-2A, GSTR-2B and GSTR-3B in brief

The practical rule: reconcile your purchase register to GSTR-2B before filing 3B, and use 2A during the month to fix gaps early.

What Oracle Fusion provides

Oracle Fusion Tax supports India GST: tax regimes, taxes, rates and rules, first-party registrations for each of your GSTINs, and third-party registrations for suppliers. When this is set up well, each Payables invoice carries the data a reconciliation needs: your GSTIN, the supplier GSTIN, invoice number, invoice date, taxable value and tax amounts by type.

What Fusion does not do on its own is download your GSTR-2B from the GST portal and match it line by line to your books. That is the job of a reconciliation solution sitting alongside Fusion. See the Oracle Fusion Financials documentation for tax setup, and our Fusion Financials implementation steps for where tax sits in the build.

Setup steps

1. Clean the supplier master first

Most mismatches start in the supplier master. Before building anything:

1. Confirm every GST-registered supplier site has a valid GSTIN in its tax registration.
2. Check the state code in the GSTIN matches the supplier site's state.
3. Flag unregistered and composition suppliers so they are not expected in 2B.
4. Put a validation step in supplier onboarding so bad GSTINs cannot be added again.

2. Define the purchase register extract

Extract validated Payables invoices, credit memos and debit memos with tax lines for the period. Common approaches are a BI Publisher report, a BICC extract, or an OIC integration. Our OIC connection playbook covers outbound options. Include:

• Your GSTIN (first-party registration) and the supplier GSTIN
• Supplier invoice number exactly as entered, and invoice date
• Taxable value, IGST, CGST, SGST and cess amounts
• Document type (invoice, credit note, debit note), reverse charge flag
• Accounting date and Fusion invoice identifier for drill-back

3. Load GSTR-2A and 2B data

Bring in the portal data for each GSTIN and period, either from downloaded files or through an approved GST data provider. Store each download with its date. GSTR-2A changes over time, so you need to know which version you matched against.

4. Normalise before matching

Supplier invoice numbers are the main source of false mismatches. Normalise both sides before matching: trim spaces, standardise case, strip leading zeros and common separators. Keep the original value for display and audit.

5. Configure matching rules and tolerances

Match in passes, from strict to loose:

1. Exact: GSTIN + invoice number + date + tax amounts.
2. Normalised: GSTIN + normalised invoice number + tax amounts within tolerance.
3. Probable: GSTIN + amounts + date window, for review by a person.

Set an amount tolerance agreed with the tax team, for example for rounding. Anything outside tolerance is a mismatch, not a match.

6. Classify every exception

Each unmatched or partly matched line should land in one bucket with an owner and an action:

• In books, not in 2B: ITC at risk; chase supplier.
• In 2B, not in books: missing or unposted invoice; check with AP.
• Amount or date mismatch: correct in books or ask supplier to amend.
• Wrong GSTIN: fix supplier master or ask supplier to amend.
• Reverse charge or blocked credit: treat under the relevant rules.

7. Tie out to GSTR-3B

The ITC figure you file in 3B should be explainable from the reconciled data: matched ITC, less blocked and ineligible credits, with reversals recorded. Keep a working paper for each period.

Month-end GST reconciliation checklist

• Supplier GSTINs validated and state codes checked
• Purchase register extracted for all GSTINs and the period
• GSTR-2B downloaded and stored with date for each GSTIN
• Invoice numbers normalised on both sides
• Matching passes run; tolerance applied
• Every exception classified with owner and action
• ITC-at-risk list sent to procurement or suppliers
• 3B ITC figure tied to reconciled data and approved
• Working papers saved for audit

Testing the solution

Before relying on the reconciliation, test it with known cases. Our GST reconciliation test playbook lists them: exact matches, amount mismatches inside and outside tolerance, invoices in books but not in 2B, invoices in 2B but not in books, credit and debit notes, duplicate invoice numbers across suppliers, reverse charge and blocked credits, and the 3B tie-out. The expected result is that every mismatch is flagged with a reason and an action owner.

Case: Policy Bazaar

Egisedge built a GSTR 2A/2B/3B solution for Policy Bazaar, a fintech client. It automates GSTR 2A reconciliation, GSTR 2B matching and GSTR 3B preparation. We also delivered a vendor portal with KYC and GSTR 2B reconciliation for Policybazaar, which checks supplier details at the point of entry. That second point matters: fixing the supplier master at onboarding prevents many of the mismatches described above.

How Egisedge helps

Egisedge Technologies is an Oracle Partner with a GSTR Solution (2A/2B/3B reconciliation) and a Vendor KYC Solution among its products. Our patented AI Financial Compliance Reporting platform also includes GST reconciliation and works alongside Oracle, SAP and other ERPs. The Compliance AI demo shows a 2B reconciliation and the ITC-at-risk list on sample data.

Want to see GSTR-2B reconciliation running against Oracle Fusion data? Email info@egisedge.com or book a demo with our team.

Frequently asked questions