How-to · Odoo GST reconciliation

Odoo can file the e-invoice and fetch GSTR-2B on its own. The matching, it still leaves to you

The short answer

Odoo's e-invoicing module uploads signed invoices to the NIC portal once you register API credentials under its GSP partner. A separate feature fetches GSTR-2B and auto-matches it against your bills — but a "partially matched" bill, shown in orange, still needs a human correction and a re-match. Odoo doesn't close that last step on its own.

Odoo's India localization does two separate jobs — generating a signed e-invoice with an IRN, and pulling GSTR-2B back from the GST portal to match against your bills. Both are documented. What the documentation doesn't dwell on is what a "partially matched" result actually means for the credit sitting behind it.

Two separate jobs, easy to think of as one

Odoo's India localization splits GST compliance into two features that get bundled together in conversation but work quite differently. E-invoicing (the Indian E-invoicing module, on top of the base Indian Accounting localization) uploads your outward invoices to the government's e-invoice portal (the IRP), which returns them signed with an IRN. GSTR-2B reconciliation fetches the government's record of your inward supplies and tries to match it against the vendor bills already in Odoo. The first is about what you sold; the second is about what you bought. Setting up the first doesn't configure the second, beyond the GSP setting the two features share — they otherwise use different menus, and (as of Odoo 19) a visibly different workflow from the one Odoo shipped a version earlier.

Who actually needs the e-invoicing half

Rule 48(4) of the CGST Rules doesn't itself name a threshold — it delegates to whichever class of registered persons the government notifies. The operative number, from Notification 13/2020-CT as amended by Notification 10/2023-CT (in force 1 August 2023), is a registered person whose aggregate turnover in any preceding financial year from 2017-18 onwards exceeds ₹5 crore, supplying to another registered person or exporting (unamended as of July 2026). The test looks back across years, not at the current year: once your turnover has crossed ₹5 crore in any one year since GST began, the obligation doesn't lapse if turnover later falls below it. A handful of categories are carved out regardless of turnover — government departments, local authorities, SEZ units, and the specific categories already covered by Rule 54 (insurers, banks and NBFCs, goods transport agencies, passenger transport, multiplex cinema admission).

The reason this isn't optional paperwork: Rule 48(5) says an invoice issued by someone Rule 48(4) covers, in any manner other than the one it specifies, "shall not be treated as an invoice." Skip the e-invoicing step and, as far as the law is concerned, you haven't issued an invoice at all — whatever your accounting system shows.

Registering the NIC API credentials

Per Odoo's own India localization documentation, the credential step happens on the government side first, then inside Odoo:

StepWhereWhat you're doing
1. Register an API userNIC e-Invoice portal > API Registration > User Credentials > Create API UserVerify the OTP sent to your registered mobile number
2. Choose the API interfaceSame screenSelect "Through GSP" and set the GSP to BVM IT Consulting Services India Private Limited — the GSP Odoo's documentation specifies, not a choice you make freely
3. Set a username and passwordSame screenThese are the credentials Odoo will use on your behalf — note them down
4. Enter the company's PAN and GSTINOdoo 19: Settings app > Companies section > Update Info (Odoo 18: Settings > Users & Companies > Companies)Required before any e-invoice can generate
5. Enter the GSP credentials (Odoo 19)Odoo > Accounting > Configuration > Settings, under Select GSP Provider / Indian Integration (Odoo 18: same path, under Indian Electronic Invoicing)Paste the username and password from step 3, and enable Registered Under GST and E-Invoicing
6. Pick an environment (Odoo 19 only)Same settings pageCheck Production Environment for live filing; leave it unchecked while you're testing — Odoo 18's documentation doesn't mention this toggle
7. Turn it on per journal (Odoo 18 only)Odoo > Accounting > Configuration > Journals > your sales journal > Advanced Settings > Electronic Data InterchangeEnable E-Invoice (IN) for that journal — Odoo 19's documentation has no equivalent per-journal step
The NIC-side registration (steps 1–3 above) and the GSP partner are identical in Odoo 18's documentation. The Odoo-side steps differ by version, as marked in the table above and in the sections below.

Generating and verifying the IRN

Once an invoice is confirmed, the two documented versions generate the e-invoice differently. In Odoo 19, click Send, select E-Invoicing, then click Generate; the signed JSON file and the status appear in the chatter. In Odoo 18, Odoo uploads the validated invoice automatically after a short delay — click Process now to force it immediately — and the status shows in the Electronic invoicing field and the EDI Document tab. Either way, a successfully generated e-invoice carries its Invoice Reference Number (IRN), acknowledgement number and date, and a QR code on the printed PDF — the QR code requirement comes from Rule 46(r), separate from Rule 48(4) itself, and it must have the IRN embedded in it.

To verify a signed invoice independently of Odoo, download the JSON file from the invoice's chatter, go to the NIC portal's Search > Verify Signed Invoice, and submit it. Cancelling also differs by version: in Odoo 19, click Request Cancel and fill in Cancel Reason and Cancel Remarks in the Cancel E-Invoice window; in Odoo 18, fill in a cancel reason and remarks on the invoice's Other info tab and click Request EDI cancellation, which moves the field to To Cancel while the request is pending. Odoo 18's documentation says cancelling an e-invoice also cancels any linked e-way bill; Odoo 19's documentation describes e-way bill cancellation as a separate step and makes no such claim, so don't assume the two are still linked on a current installation. Odoo's documentation doesn't state a cancellation time limit either way, so don't take the button's availability as proof none applies — check the current NIC portal rules before relying on it for anything time-sensitive.

GSTR-2B reconciliation — and why the workflow genuinely differs by version

This is the half of the job Odoo's own documentation describes very differently between its two most recently published versions — not a wording tweak, a real redesign of the feature. If your instance hasn't been upgraded recently, don't assume the newer screens below are what you'll see.

Odoo 19's workflow runs as a multi-stage check: a Fetch E-Invoice validation starts in an "Anomaly" state and turns "Reviewed" once fetched, then you click Validate. Clicking Fetch GSTR-2B retrieves the statement from the GST portal (the stage turns green on success; GSTR-2B (IN) shows the raw data), and Odoo automatically matches the fetched invoices against your e-invoices. View Bills shows the detail. The match stage itself is colour-coded: orange for "Partially matched (some bills require correction)", green for "Fully matched (all bills reconciled)." After all bills are fully matched, open the ellipsis menu and select Mark as Complete. One timing detail worth knowing before you assume something's broken: per Odoo's own documentation, the Fetch E-Invoice check only turns green if the data is fetched two days after the end of last month's reconciliation period.

Odoo 18's workflow is simpler: clicking Fetch GSTR-2B Summary moves the status to "Waiting for Reception," then "Being Processed" while Odoo reconciles against your bills, ending at either "Matched" or "Partially Matched." A partial match surfaces via View Reconciled Bills, which categorises the discrepancies — for example, bills missing in Odoo or in GSTR-2.

Both versions land on the same practical fork: a full match needs no further matching work (on 19 you still click Mark as Complete), and a partial match does — correcting the affected bills and then re-running the match (Re-Match, or Reset to return to the Match stage, on 19; re-match on 18) rather than Odoo resolving it for you.

Where the orange stays orange — and it isn't always Odoo's fault

A persistent partial match usually traces to one of a few causes that have nothing to do with a bug in Odoo's matching logic:

  • GSTR-2B is a draft, not a fixed file. GSTR-2B is prescribed by Rule 60(7) of the CGST Rules, but how it behaves comes from GSTN's portal, not the rule itself. Per GSTN's revised IMS advisory, a draft is generated on the 14th, any accept/reject/pending action you change after that requires a recompute, and the statement stabilises only when GSTR-3B is filed (as of July 2026). If Odoo fetched the statement before your own Invoice Management System actions settled, or because a supplier filed its GSTR-1 late, the fetch and your books can disagree through no fault of either side — it's a timing gap, not a data error.
  • No action is deemed accepted. A record you never touch in IMS still flows into your GSTR-2B as accepted (as of GSTN's April 2026 IMS advisory) — which can pull a figure into the statement that your books never recorded as confirmed, leaving Odoo with a bill to match that, from your side, doesn't exist yet.
  • The vendor's own invoice missed the reporting window. For a supplier with an aggregate annual turnover of ₹10 crore or more, GSTN's advisory of 5 November 2024 has, since 1 April 2025, configured the IRP to refuse an invoice, credit note or debit note reported more than 30 days after that document's own date. This is a portal validation, not a rule or a notification, and GSTN can change it (as of July 2026). A document that misses the window gets no IRN, so it won't appear among the vendor e-invoices Odoo 19's GSTR-2B reconciliation fetches and matches. If the supplier still reports it in GSTR-1, whether it counts as a valid invoice at all is a separate Rule 48(5) question.

None of this is something a re-match click fixes by itself. Chasing down which of these three (or a genuine data-entry slip) is behind a specific orange bill, invoice by invoice, every reconciliation cycle, is exactly the kind of continuous checking that's painful to do manually — and the pressure to just click through to "Mark as Complete" once the totals look close enough is real, even though a bill that's actually wrong doesn't become right because the status turned green.

What a partial match means for the credit, not just the status field

A "Partially matched" bill isn't a UI nuisance — it's Odoo telling you the credit you're holding and the credit GSTN's records support aren't yet the same number. Under Section 16(2)(aa) of the CGST Act, read with Rule 36(4), your ITC on an invoice depends on the supplier having furnished it and on its communication in your GSTR-2B — not on what your own books say, and not on what Odoo's reconciliation screen shows before the correction is actually made. Marking a batch complete to clear the queue, without resolving what's actually causing the mismatch, doesn't change what the portal will support if it's ever checked.

How Recoup fits in

Recoup doesn't replace Odoo's e-invoicing or its GSTR-2B fetch — those are Odoo's job, and the setup above is what makes them work. What Recoup does is sit on top of the result: it reconciles what your books say against what the GST portal actually shows, invoice by invoice, continuously rather than at the point you happen to run Odoo's own matching — so an orange bill that's been sitting unresolved for a cycle or two surfaces as a named, aged gap, not a status color nobody's gotten back to.

Don't let "partially matched" become the permanent state

Recoup reconciles what Odoo says you bought against what the GST portal actually shows — invoice by invoice, continuously — and names the gap before it becomes someone else's ITC problem.

Book a demo →

Related guides