Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Microsoft Dynamics 365 Business Central (v23+) and Finance & Operations (10.0.34+) ship with Indian localisation for GST tax determination, TDS deduction, and e-invoice IRP integration but do not pull GSTR-2B from the GST portal, do not match Form 26AS against TDS receivable, and do not disaggregate NACH batch credits from NPCI response files.
Bolt an external reconciliation layer via one of three integration patterns: OData REST API for standard entities (VendInvoice, GeneralJournalAccountEntry, BankStatementLine) with OAuth 2.0, Data Management Framework (DMF) for batched CSV/Excel export and import through the DMF job scheduler, or Dataverse integration for Business Central feeding Power Automate and external tools.
D365 connector with OData endpoint registry, DMF export templates for GL, AP, AR, bank statement entities, OAuth 2.0 credentials, Dataverse entity mapping for BC, and GSTR-2B JSON, Form 26AS, and NACH NPCI file adapters on the external side with writeback to D365 via DMF import.
A reconciled D365 ledger with statutory (26AS, GSTR-2B) and NACH variances all matched externally and cleared back into BC or F&O — TDS receivable, ITC, and customer receivables reliable at close across Indian entities on Microsoft's ERP stack.
Microsoft Dynamics 365 covers the Indian market with two distinct products — Business Central for SMEs and mid-market, and Finance & Operations (F&O) for large enterprise. Both have India localisation for GST, TDS, and e-invoice, and both stop short of reconciliation against external authorities. This guide covers the boundary in each product and the integration options for adding a reconciliation layer.
What D365 India Localisation Covers
Business Central (version 23+) and Finance & Operations (release 10.0.34+) deliver:
- GST tax determination on purchase and sales lines with multi-rate support
- TDS deduction under active sections including 194C, 194J, 194I, 194Q, 195
- Form 26Q and 27Q quarterly return file generation
- e-invoice generation with IRN (Invoice Reference Number) via GSP integration
- GSTR-1 JSON export for portal upload
- PAN validation at vendor master level
F&O additionally supports ISD (Input Service Distributor), TCS under 194O, and the Tax Engine multi-jurisdiction model for complex entities.
Where D365 Reconciliation Stops in India
Form 26AS / TDS receivable
D365 tracks TDS payable (what the entity deducted) accurately but does not verify TDS receivable (what customers deducted and deposited on the entity’s behalf) against Form 26AS. The external matching happens after the TDS return has already been filed.
GSTR-2B matching
F&O supports GSTR-2B JSON import for reconciliation from release 10.0.34. Business Central does not have a native GSTR-2B matching module as of Business Central 23 — third-party AppSource extensions fill the gap, or the matching moves to an external layer. In either case, the GSTR-2B JSON must be downloaded manually from the GST portal.
NACH batch and platform settlement
Bank Reconciliation in both products ingests the bank statement line for the NACH batch credit. The NPCI mandate-level response file is not parsed. Payment gateway settlement CSVs (Razorpay, PayU, Cashfree) are not recognised by the standard Bank Statement Import functionality.
D365 Integration Options for Reconciliation
| Integration path | Products | Use case | Format |
|---|---|---|---|
| OData REST API | BC, F&O | Real-time entity query | JSON |
| Data Management Framework (DMF) | F&O | Scheduled bulk extract | CSV, Excel |
| Bank Statement Import | BC, F&O | Inbound bank statement | MT940, BAI2 |
| Dataverse sync | BC | Power Automate flows | Dataverse tables |
| AL extension | BC | Custom logic in-product | AL code |
| X++ extension | F&O | Custom logic in-product | X++ code |
An external reconciliation software India layer typically reads D365 through DMF or OData, processes the India-specific matches outside the ERP, and pushes cleared-status journals back via OData. For GST-specific scale, GST reconciliation software consumes the D365 purchase extract and the GSTR-2B JSON in a single pipeline.
India-Specific Considerations
The D365 India localisation tracks challan numbers against TDS sections but has no TRACES connector — the same gap covered in automating TDS reconciliation in India. GSTR-2B matching logic, when handled externally, follows the pattern in the GSTR-2B reconciliation guide. Microsoft’s official documentation for the India localisation is published on Microsoft Learn — Dynamics 365 India GST. The reconciliation in SAP, Oracle and Tally India guide covers the parallel gaps across other enterprise ERPs.
The FAQ below addresses the most common D365-India reconciliation questions.