Reconciliation for Microsoft Dynamics 365 in India — TDS, GST, Bank, Settlement
Dynamics 365 customers in India run Business Central or Finance & Operations against the India localisation pack — TDS, TCS, GST, and the related registers. Both products carry strong subledger architecture and a defined extension model, but neither parses Indian bank narration at scale, runs GSTR-2B reconciliation against AP invoices at line level, or maps WHT codes to the new payment-code regime against Form 26AS without external tooling. TransactIG reads Dynamics via OData, DMF, and standard report extracts and runs the matching layer alongside.
What Dynamics Handles Natively, and Where the India Gap Appears
What Dynamics does well
Business Central and Finance & Operations both carry strong AP, AR, GL, and bank ledger architecture. Multi-legal-entity, financial dimensions, automated approval workflows, and the India localisation pack for TDS/TCS/GST give Indian customers a defensible base for compliance reporting and statutory close.
The BSR (Bank Statement Reconciliation) feature handles MT940-based matching for the simple case. OData and DMF interfaces give clean read access to subledger data without writing custom extensions.
Where the India gap appears
BSR was not built for CIB Excel, YONO Business Excel, or co-op bank PDF. UPI VPA, NEFT fragment, and cheque-clearing narration extraction does not exist natively — bank lines without clean references route to manual matching.
India localisation WHT codes were built for the legacy section regime; the new payment codes 1001-1092 under Sections 393, 394, 413 of the Income Tax Act 2025 require external mapping during the transition. GSTR-2B reconciliation against AP invoices is a manual export-and-compare unless a matching layer sits alongside.
TransactIG Plug Points on Dynamics 365
Six matching surfaces sitting alongside Dynamics — no AL or X++ extensions deployed.
Data ingestion
OData read endpoints (Business Central), DMF data entity exports (F&O), or scheduled report exports. Read-only access, no extensions, no schema changes.
Section 393 TDS handling
India localisation WHT codes mapped to new payment codes 1001-1092 under Sections 393, 394, 413 of the Income Tax Act 2025. Reconciled to Form 26AS and AIS at code level.
GSTR-2B and IMS
AP invoices matched to GSTR-2B and IMS at GSTIN + invoice + tax-amount level. ITC eligibility and Rule 36(4) provisional credit per invoice.
NACH batch matching
Outbound mandate batches reconciled to bank response files; bounce codes mapped, re-presentation tracked at vendor and customer level.
Platform settlements
Razorpay, PayU, Cashfree, Amazon, Flipkart settlements disaggregated and matched to Dynamics customer transactions. Fees and GST on fees classified.
Bank statement ingestion
MT940, CAMT.053, CIB Excel, YONO Business, and PDF parsed natively; matched to Dynamics bank account ledger with narration-pattern extraction.
Dynamics 365 Integration Architecture
Discrete read feeds configured during implementation. The Dynamics admin team owns the export configuration; TransactIG owns the matching layer.
| Dynamics source | Read method | Sync cadence | Field mapping | Variance codes |
|---|---|---|---|---|
| GL transactions and balances | OData GeneralLedgerEntries (BC) / DMF General journal entity (F&O) | Daily or per-period close | GL account → TransactIG voucher class | JOURNAL_UNMATCHED, BALANCE_DRIFT |
| AP invoices and payments | OData PurchaseInvoices (BC) / DMF Vendor invoice transactions (F&O) | Daily | Vendor → counterparty GSTIN | INVOICE_OPEN, 2B_MISSING, ITC_BLOCKED |
| AR invoices and receipts | OData SalesInvoices (BC) / DMF Customer transactions (F&O) | Daily | Customer → counterparty | INVOICE_OPEN, ADVANCE_UNAPPLIED, CREDIT_NOTE_PENDING |
| Bank account ledger | OData BankAccountLedgerEntries (BC) / DMF Bank account transactions (F&O) | Daily | Bank account → Indian bank narration profile | BANK_LINE_UNMATCHED, CHARGE_UNCLASSIFIED |
| Withholding (TDS) lines | India localisation TDS transaction extract via DMF or report export | Per deduction cycle | WHT code → new payment code (1001-1092) | TDS_NOT_IN_26AS, RATE_MISMATCH, SECTION_RECLASSIFIED |
| GST output (India localisation) | GSTR-1/3B register output, e-invoice IRN extract | Per GST cycle | Vendor invoice → GSTR-2B row | ITC_INELIGIBLE_2B, INVOICE_MISSING_IN_2B |
Common Reconciliation Gaps in Dynamics India Deployments
BSR exception backlog
BSR cannot parse narration patterns; lines without clean references route to manual matching, accumulating month over month.
WHT code drift
India localisation WHT codes reference legacy sections; Form 26AS shows new payment codes; the mapping layer sits outside Dynamics.
AP vs GSTR-2B
Vendor invoice posted in Dynamics; supplier has not filed GSTR-1; ITC provisional under Rule 36(4); reconciliation needs to surface at AP level.
Multi-entity intercompany
Inter-legal-entity transactions drift on timing, FX, or one-sided entry; consolidation surfaces the drift but not the resolution path.
Settlement net vs gross
Payment gateway settles net of fees; AR raised gross; disaggregation needed before receipt application inside Dynamics.
AX/Nav legacy bridge
Customers mid-migration run AX 2012 R3 alongside F&O, or NAV alongside BC; reconciliation needs to span both during transition.
How TransactIG Works with Dynamics 365
Ingest
OData/DMF/REST feeds pull AP, AR, GL, bank account, TDS, and GST data per legal entity. External feeds (bank statements, GSTR-2B, 26AS, NACH responses, settlement reports) land alongside.
Match
Dynamics subledger lines matched to external sources. Narration parsing handles Indian bank narration; payment-code mapping aligns WHT to 1001-1092 codes; GSTR-2B match runs per GSTIN.
Exception queue
Unmatched items route to a structured queue with variance codes, ageing, suggested resolution, and maker-checker workflow. Reconciliation artefacts exported per legal entity for the audit team.
Frequently Asked Questions
Does TransactIG work with Business Central and Finance & Operations?+
Both. Business Central (the SMB/mid-market product, formerly NAV) exposes OData and REST endpoints for AP, AR, GL, and bank ledger data. Finance & Operations (the enterprise product, formerly AX) exposes data through Data Management Framework (DMF) entities, OData, and SOAP services. TransactIG configures one read path per environment. Customers running both products in a hybrid deployment can integrate both with one TransactIG instance — the matching schema normalises to a single model.
How does TransactIG handle Dynamics 365 India localisation?+
The India localisation pack adds TDS, TCS, GST, and India-specific tax setup to the standard Dynamics modules. TransactIG reads the AP invoice and vendor payment posting with the TDS tax-component breakup, maps the configured WHT code to the new payment codes (1001-1092) under Sections 393, 394, 413 of the Income Tax Act 2025, and reconciles against Form 26AS at payment-code level. GST registers and the e-invoice/e-way bill audit trail are read via the standard report extracts.
How does TransactIG reconcile against the Dynamics 365 bank account ledger?+
Dynamics 365 maintains a bank account ledger that captures every payment and receipt against a bank account. The product also supports bank statement reconciliation through the BSR (Bank Statement Reconciliation) feature, which accepts MT940 and other formats. The challenge in India is that statement formats and narration conventions exceed what BSR is configured for. TransactIG parses MT940, CAMT.053, CIB Excel, YONO Business, and PDF natively, extracts narration patterns, and matches against the Dynamics bank ledger — surfacing exceptions that BSR routes to manual entry.
Does TransactIG handle multi-legal-entity and financial dimensions?+
Yes. Dynamics 365 F&O supports multi-legal-entity, financial dimensions, and consolidation hierarchies. TransactIG ingests data per legal entity, applies the dimension structure during matching, and rolls up to a group consolidated view. Intercompany open items between entities auto-match on amount-and-date pairs; intercompany imbalances surface in the exception queue with FX and timing classification. Business Central customers with a multi-company model are handled the same way at the company level.
What about AX/Nav legacy customers migrating to D365?+
Many Indian customers still run Dynamics AX 2012 R3 or Dynamics NAV 2018 alongside or while migrating to D365 F&O or Business Central. TransactIG reads from both — AX through AIF/DMF, NAV through its OData and report exports. The matching schema is the same; once the migration completes, the source path switches without changing the reconciliation configuration.
How long does Dynamics 365 integration take?+
2 to 4 weeks for most Dynamics customers. Week one configures OData or DMF entities, sets up scheduled exports, and tests the read flow. Week two maps the chart of accounts, financial dimensions, India localisation WHT codes, and tax registration to TransactIG's matching schema. Weeks three and four configure narration patterns, TDS payment-code mapping, GSTR-2B alignment, settlement disaggregation, and the maker-checker workflow. The Dynamics admin team owns the export configuration; no custom AL/X++ code is written.
Reconciliation that fits the way your Dynamics 365 environment already runs
No AL or X++ extensions. No schema changes. 2 to 4 weeks to first reconciled close, ISO 27001:2022 certified, running from AWS Mumbai.