IRN generation, QR-coded invoices, e-way bills and GSTR reconciliation built directly into Dynamics 365 Finance & Operations. Built to order against your GSPs, GSTINs and document flows — not a ready-made download. Built to order by ECOSIRE for Dynamics 365 F&O (build-to-order) — indicative price from $1499.00 USD; request a quote for a scoped proposal.
IRN generation, QR-coded invoices, e-way bills and GSTR reconciliation built directly into Dynamics 365 Finance & Operations. Built to order against your GSPs, GSTINs and document flows — not a ready-made download.
Built to order
India's e-invoicing mandate has moved steadily down the turnover ladder, and the threshold now catches mid-market organisations that were previously outside it. Once you are in scope, an invoice is not legally valid until the Invoice Registration Portal has returned an Invoice Reference Number, and goods cannot move without a valid e-way bill.
Dynamics 365 Finance & Operations has a strong India localisation for GST calculation, HSN/SAC codes and GSTIN registration numbers. What it does not solve on its own is the round trip: taking a posted CustInvoiceJour or transfer order, mapping it to the current portal JSON schema exactly, calling the portal through your GSP, handling the portal's error codes, storing the IRN, signed QR code and acknowledgement, printing them on the document, and then proving at month end that what you posted in F&O equals what the portal holds and what your GSTR return says.
Teams end up keying invoices into a portal by hand, printing a QR code from a browser and stapling it to a delivery, and reconciling GSTR-1 against F&O in a spreadsheet. Every schema revision breaks the workaround again.
We build the full round trip inside F&O as X++ extensions with no overlayering, sitting on top of the standard India GST localisation rather than replacing it.
A mapping layer converts a posted sales invoice, credit note, debit note or export invoice into the portal's current JSON schema — seller and buyer GSTIN blocks, dispatch and ship-to addresses, item lines with HSN/SAC, unit codes, taxable value, CGST/SGST/IGST/cess split, reverse charge and export flags. Field lengths, mandatory conditional groups and decimal precision are validated before the call, so a schema rejection is caught in F&O rather than at the portal. The IRN, acknowledgement number, acknowledgement date and signed QR payload are stored against the invoice journal and printable on the document.
E-way bills are generated from the same document with transporter ID, vehicle number, transport mode, distance and sub-supply type, either together with the IRN or as a separate call. Part-B updates, vehicle changes on transhipment, extension of validity and cancellation are all handled from a form, and stock transfers between your own locations are supported as well as customer shipments — a TransferOrder moving goods across state lines needs an e-way bill exactly as a sale does.
The portal enforces its own windows: an IRN can be cancelled only within the permitted period and only if no active e-way bill exists, and an e-way bill has its own cancellation and rejection rules. Those constraints are enforced in F&O before the call, with clear messages, so users are not left guessing why the portal refused.
A reconciliation workspace compares F&O outward supplies against the data filed or available on the portal, matching on document number, GSTIN, taxable value and tax split. Mismatches are categorised — missing at portal, missing in F&O, value difference, GSTIN difference, wrong tax head — and exported for correction. Purchase-side data can be imported through the Data management framework and matched against vendor invoices to surface input tax credit gaps.
All portal calls run through SysOperation batch jobs with configurable recurrence, plus an on-demand action from the invoice form for urgent documents. Failures are retried with backoff and never silently swallowed: every attempt is logged with the request payload, the portal response and the error code. Duplicate submission is prevented by an idempotency check on the document, because the portal will return an existing IRN rather than a new one and that response must be handled as success, not failure.
Registration numbers, GSP credentials, series and portal endpoints are configured per GSTIN and per legal entity, so a group operating in several states from several DataArea values files under the correct registration without user intervention.
IRN status, e-way bill status and reconciliation results are exposed as data entities over OData, so a compliance dashboard in Power BI or a Power App for the logistics team reads live status without a second integration. Where you already use Dual-write, the same entities are available to the customer engagement side.
Organisations running Dynamics 365 Finance and Supply Chain Management with one or more Indian GSTINs that are in scope for e-invoicing, or expect to be as thresholds move. It suits manufacturers and distributors moving goods interstate, groups filing under several registrations, and finance teams that currently reconcile GSTR against F&O manually.
This app is built to order. There is no pre-built package waiting to be downloaded.
1. Scoping call. We confirm your GSTINs, your GSP or portal access route, the document types in scope (sales invoice, credit and debit notes, export, stock transfer), your current India localisation configuration, and your F&O version and platform update. 2. Fixed quote. A written scope listing the exact document types, forms, entities, batch jobs and reconciliation views included, with a fixed price and a delivery date. 3. Build. Developed as X++ extensions in a dedicated model against your target platform update, tested against the portal's sandbox using your GSP sandbox credentials. 4. Install in test. A deployable package for your LCS/sandbox pipeline, installed with your team in UAT. We run real document types end to end in sandbox with your tax team watching, including a cancellation and an amendment. 5. Production. After UAT sign-off, the same package goes through your release pipeline. We support the first live IRN and the first live e-way bill. 6. Support. A defined support window covering defect fixes and schema or platform changes that land during that window.
We are not a GST Suvidha Provider and we do not file returns on your behalf. The app connects to the GSP or portal access route you hold. We are not affiliated with, endorsed by, or certified by Microsoft or by any tax authority. Statutory interpretation — what is taxable, at what rate, under which head — remains with your tax advisors; we implement the mapping they confirm.
A short call to confirm the workflow, your platform version and where the integration boundaries sit.
You receive a written scope and a fixed price. Nothing is built until you approve it.
We develop against a copy of your configuration and test it there. Typically two to four weeks.
We install on your instance, hand over the source, and support it for twelve months.
Is accountable for GSTR filings that must tie back exactly to the ledger, but currently reconciles portal data against F&O in a spreadsheet each month. A reconciliation workspace that categorises every mismatch turns filing from a reconstruction exercise into a review of exceptions.
Cannot release a vehicle without a valid e-way bill and loses hours when a transhipment needs a Part-B update done in a browser. Generating and updating the e-way bill from the same F&O document as the shipment keeps trucks moving without a second system.
Has to keep the India localisation configuration intact through every platform update and cannot afford overlayered compliance code. Extension-only X++ layered on top of the standard localisation, with a documented field mapping, keeps the environment upgrade-safe and auditable.
| Criterion | ECOSIRE | Custom Build | Competitor |
|---|---|---|---|
| IRN generated directly from posted F&O invoices | Included | Partial support | Included |
| E-way bill lifecycle including Part-B and transhipment updates | Included |
From $1499.00
Starting point — quoted to your scope
| Partial support |
| E-way bill for transfer orders as well as sales shipments | Included | Not included | Partial support |
|---|
| GSTR reconciliation workspace with categorised mismatches | Included | Not included | Partial support |
|---|
| Portal cancellation and amendment windows enforced in F&O | Included | Not included | Partial support |
|---|
| Multi-GSTIN and multi-legal-entity configuration | Included | Partial support | Included |
|---|
| Field-level mapping document for tax advisor sign-off | Included | Not included | Not included |
|---|
| Source code ownership handed to the customer | Included | Included | Not included |
|---|
An X++ extension that imports bank statements into Dynamics 365 F&O and fuzzy-matches lines against payments, deposits and fees. Built to order for your legal entities after a scoping call and fixed quote.
A behaviour-aware treasury forecasting app for Dynamics 365 Finance & Operations. Built to order as an X++ extension after a scoping call and a fixed quote — nothing is pre-built or downloadable today.
A built-to-order forecasting and planning layer for Dynamics 365 Finance & Operations, with external demand signals, explainable forecasts and scenario comparison. Scoped and built by ECOSIRE after a fixed quote.
A build-to-order X++ extension that captures vendor invoices, extracts line data, matches them against purchase orders with tolerance rules and routes exceptions through F&O workflow. ECOSIRE builds it for your entity structure after a fixed quote.