Integrations

Microsoft Dynamics Integration

Capture, match and post against Dynamics 365, with the vendor master and purchase orders kept in sync.

Two colleagues at dual monitors in an office, one pointing at a record on the screen

What moves

What flows between Dynamics 365 and PTAS AI

Documents and master data come in. Vendor invoices, attachments and status go out. Dynamics stays the system of record; AI does the reading and the matching in front of it.

Dynamics 365 Finance or Business Central

Vendors, purchase orders, product receipts, vendor invoices, payments

The documents

Supplier invoices, credit notes, delivery notes, statements

Your configuration

Legal entities, financial dimensions, tax setup, approval limits

PTAS AI

Vendor invoices without the keying

One invoice per document, lines matched to the purchase order and product receipt, dimensions set, written only after approval.

Posting and payment status back in the queue

Whether the invoice posted and whether it was paid is read back on a schedule, so FinSuite can answer a supplier without anyone opening Dynamics.

A trail on both sides

The Dynamics invoice number sits on the FinSuite record; the invoice image is linked to the invoice in Dynamics.

Microsoft Dynamics is a planning example here, not a packaged connector. Whether you run Finance or Business Central, which route your partner and IT team will approve, and who approves what are confirmed in discovery.

How FinSuite posts to a ledger

Integration methods

How Dynamics 365 can be connected

Four ways in. The first question is which Dynamics you run, because Finance and Business Central are different products with different interfaces.

Native

What Microsoft ships itself

Microsoft offers its own invoice capture for Dynamics 365 Finance, and Business Central has its own incoming documents. Some customers run them. We install no extension, we are not listed on Microsoft AppSource, and nothing on this page is a packaged connector.

API

OData data entities, or the Business Central API

Dynamics 365 Finance exposes data entities over OData; Business Central has a REST API for vendors, purchase orders, purchase invoices and attachments. Both authenticate an app registered in your Microsoft Entra ID tenant. The route we expect to propose for most Dynamics 365 instances, confirmed in discovery.

File

Data packages on a schedule

Dynamics 365 Finance imports data packages through its data management framework, once or as a recurring job, with an execution log to read back. Slower than OData, and sometimes the route your implementation partner already runs. Business Central is rarely connected this way.

Custom

Dataverse, Power Automate, or several systems

Where Finance is linked to Dataverse through dual-write, or your team already runs flows in Power Automate, the traffic can pass through what you monitor today. Several legal entities, an AX or NAV instance next to Dynamics 365, or Dynamics as one of three systems need orchestration on top.

The route for your instance is confirmed in discovery. For Dynamics 365 Finance we would expect OData data entities for reads and writes, with posting status read back on a schedule. For Business Central the API covers the same objects more directly, and a purchase invoice can be created unposted and posted once approved. Older AX and NAV installations are a separate conversation, and usually a file route. Whichever applies, the calls go through interfaces Microsoft documents and your administrator can switch off.

Illustrative example · one invoice, two Dynamics products

Dynamics 365 FinanceData entities

Vendor accountV-2041

Purchase orderPO-000814

Product receiptPR-000377

Financial dimensionsIN01 · Plant 2

Lands asPending vendor invoiceAwaiting approval

Business CentralAPI v2.0

Vendor no.V-2041

Purchase order106014

Posted receipt107022

DimensionsDEPT PROD · AREA N

Lands asPurchase invoice, unpostedDraft

Same checks Different object names, the same evidence before anything is written: vendor, order, receipt, dimensions and tax.

Illustrative data. The name Dynamics covers two different ERPs with different interfaces, so the first question in discovery is which one you run, and which version.

What we would not automate. A vendor invoice is not written to Dynamics until the vendor exists in that legal entity, the match passed your tolerances and the financial dimensions are valid. We would not ask for a role that can post general journals or create payments, and we would not post through a person's login. If product receipts are recorded days after the goods arrive, a three-way match will hold invoices whether we sit in front of Dynamics or not. We would rather find that in discovery than at go-live.

Field mapping

Where each finance object lands in Dynamics 365

The mapping is agreed before build and kept per legal entity, in the terms your Dynamics team already uses. This is the starting point we bring to the assessment.

Finance objectIn Dynamics 365

Vendor The vendor account in Dynamics 365 Finance, or the vendor card in Business Central, read per legal entity or company with posting profile, terms, bank account and tax registration. We match on GSTIN or tax number and bank details before proposing a new vendor. Your master data team creates it, through your own approval.

Purchase order The purchase order header and lines, matched line by line on quantity, unit price and currency. In Finance, the invoice matching policy in your accounts payable parameters still applies once the invoice lands. We run the same comparison first, so the invoice arrives matched instead of being held for a variance.

Goods receipt The product receipt against the order line in Finance, or the posted purchase receipt in Business Central. We read the quantity received, so the match uses what arrived. Where goods are not received in Dynamics, a delivery note read by DocPro gives FinSuite the third leg of the match.

Invoice A pending vendor invoice in Finance, with each line referenced to its order line and carrying financial dimensions. A purchase invoice in Business Central, created unposted and posted once approved. Invoices without a PO are coded to main account and dimensions from your rules.

Tax The sales tax groups on each line in Finance, or the posting setup your Business Central localisation uses, so Dynamics calculates the tax it expects. In India we check GSTIN, HSN or SAC and place of supply against the document. A difference beyond your tolerance is held in FinSuite before Dynamics ever sees it.

Payment status The settlement of the invoice against a vendor payment in Finance, or the vendor ledger entry closing in Business Central. Read back on a schedule, so FinSuite shows what was paid and when.

The entry, on both sides · Illustrative example

FinSuiteValidated

VendorV-2041

Ledger5210

DimensionPlant 2

Net / tax₹ 2,29,000 / 41,220

Your ERPSystem of record

Creditor2041

GL account5210

Cost centrePLANT2

Document4500091827Posted

Linked both ways The ERP document carries a link back to the invoice image it came from.

Field mapping is yours to define. Entries are validated against it before they reach the ERP, not rejected by it afterwards.

Security of the connection

What protects the link to your Dynamics tenant

Four controls, each one visible to your Entra ID and Dynamics administrators. None of them depends on trusting us.

An app registration your tenant owns

Your Entra ID administrator registers the app and grants it access. In Finance it is mapped to a user holding only the roles it needs; in Business Central, to the permission sets you choose. Secrets or certificates are stored encrypted and can be revoked in your tenant at any time.

Least privilege, per legal entity

Read vendors, orders and receipts; write vendor invoices. No general journal posting, no payment proposals. Access is limited to the legal entities or companies in scope, and reviewed when the workflow changes.

Every write logged with its evidence

Each invoice we create records the document it came from, who approved it and the number Dynamics returned. A rejected write is kept with the message Dynamics gave and goes to a person. Nothing is retried blindly.

Sandbox first

The mapping is built against a sandbox environment with a copy of your configuration, and moves to production through your change process after your finance team has seen the invoices.

FAQ

Questions Dynamics teams ask

Do you work with Dynamics 365 Finance, Business Central, or both?

Both, but they are different products. Dynamics 365 Finance exposes data entities over OData and imports data packages through its data management framework. Business Central has its own REST API, closer to the objects a payables team works with. Which route fits your instance, and which version you run, is confirmed in discovery before anything is built.

Will invoices appear in Dynamics before they are approved?

Only if you want them to. Finance can hold a pending vendor invoice for its own vendor invoice workflow, and Business Central keeps a purchase invoice unposted until someone posts it. If approval runs in Dynamics, we write the invoice and leave approval there. If it runs in FinSuite, the invoice arrives already approved. One place approves, never both.

We are still on Dynamics AX or NAV. Can you connect?

Often, but by a different route. AX 2012 and NAV predate the APIs described on this page, so a file exchange or an interface your partner maintains is more likely. If a move to Dynamics 365 is planned, say so at assessment, and the mapping is designed to move with you.

We have six legal entities. Is that six integrations?

One integration, one mapping per legal entity. Each has its own vendors, dimensions, tax setup and approval limits, so the mapping is kept per entity and the app is given access to exactly those entities. The review queue is shared, with the entity as a dimension, so one team can work all six.

Is this an AppSource app or a Microsoft partnership?

No. We do not claim a listing on Microsoft AppSource, a Microsoft partnership or a certification, and we would rather say so here than let a logo imply it. The connection is built for your tenant, authorised by your administrator, and every call it makes is visible to your team.

Keep reading

SAP Integration

The other large ERP we plan around: OData, BAPIs, IDocs and flat files.

NetSuite Integration

Vendor bills, purchase orders and item receipts through NetSuite interfaces.

FinSuite Integrations

The four integration methods and how FinSuite posts into any ledger.

All integrations

ERPs, accounting suites, the REST API and webhooks in one list.

Next step

Bring a month of vendor invoices and your posting setup

An assessment starts with your real documents and a sandbox environment. Nothing is written to Dynamics until your finance team has seen the invoices.

Book a Call Test Your Document