Key Takeaways
- Transformance reads customer ledger entries, invoices, journal entries and bank statements from Business Central and writes back applications, journal entries and reversals after a person approves.
- The connection typically takes 2-3 days and your IT team may be involved; full rollout takes up to 4-8 weeks.
- Six Business Central settings stop or change a posting from any external system, from the posting window to duplicate CAMT transaction IDs.
- ClearMatch auto-matches 95% of payments and runs end to end in under 8 minutes (Transformance customer data, 2026).
- Business Central stays the system of record; Transformance keeps the evidence and the approval for every posting.
In This Article
- Key Takeaways
- How does Transformance integrate with Business Central?
- How does the connection to Business Central work?
- What does Transformance read from Business Central?
- How are payments applied and posted back in Business Central?
- What happens with short payments and exceptions?
- Which Business Central settings stop a posting?
- Who approves postings, and what is logged?
- How is a wrong posting corrected in Business Central?
- Illustrative example: one lump sum against three invoices
- How long does a Business Central integration take?
How does Transformance integrate with Business Central?
Transformance reads customers, open customer ledger entries, invoices and bank data from Business Central, and posts payment applications, journal entries and reversals back after a person approves.
What Transformance reads and writes in Business Central
Object names follow Microsoft’s documentation; your Business Central partner may have renamed pages or fields.
Dynamics 365 Business Central runs in production with Transformance customers today, alongside Dynamics 365 Finance & Operations (how the F&O connection works). The full ERP list is in the ERP integrations overview.
An application in Business Central is the posted link that ties a payment entry to the invoice entries it pays; posting it closes the invoices it fully covers, which SAP users call clearing. Customer ledger entries are Business Central’s AR sub-ledger; detailed entries hold the applications, tolerances and currency differences behind them.
Business Central stays the system of record for open items, the ledger and the posting history; Transformance keeps its matching evidence, approvals and decision log in its own layer. Start with cash application alone, or run the full order-to-cash on the same connection.
How does the connection to Business Central work?
The connection method follows your environment: options include an app registration in your Microsoft Entra tenant, APIs, file or SFTP, middleware, or Transformance’s own on-premises agent.
In Business Central online, an integration without a named user signs in with service-to-service authentication, which “uses the Client Credentials OAuth 2.0 Flow”. Your admin registers an app in Microsoft Entra, enables it on Business Central’s Microsoft Entra Applications page and assigns permission sets. “Applications can’t be assigned the SUPER permission set”, so an integration app runs on least privilege (Microsoft Learn, 2025).
Three facts from Microsoft’s Business Central API documentation shape the scoping (Microsoft Learn, 2026):
- Environments. Every online API call names one environment, production or sandbox.
- Companies. Most endpoints also name one company, so each set of books is addressed on its own.
- On-premises. The on-premises API is “disabled by default” and “must be exposed through a firewall”.
List every environment and company in scope, and connect to a sandbox first. Your IT team or Business Central partner may be involved, for the app registration and permission sets or another route.
Your data is hosted in your region, VPC deployment in your own cloud is available, sign-in runs through SSO/SAML with role-based access control, and no customer data is used to train models (how AI agents access ERP data safely).
What does Transformance read from Business Central?
Transformance reads customer master data, customer ledger entries, posted invoices and credit memos, journal entries and bank statements; remittances usually arrive outside Business Central and are read in Transformance.
On the customer card, six fields change how a payment is matched and posted: payment terms, application method (Manual or Apply to Oldest), Blocked, currency, customer posting group and Block Payment Tolerance.
Customer ledger entries carry the open item: Remaining Amount, Due Date, payment discount date, Open, On Hold and External Document No., the customer’s own reference.
Bank data comes either from statements already imported into Business Central or from the bank file read directly in Transformance. One dated change affects bank accounts in the EU: “Starting in November 2025, most countries/regions in the European Union (including Switzerland) are mandating the SEPA CAMT.053.001.08 format”, Microsoft notes. In a camt.053 import, the transaction ID from the EndToEndId tag must be unique in the open reconciliation, and “if the information isn’t present, Business Central ignores the payment” (Microsoft Learn, 2025).
Remittances arrive by email, PDF, portal download or EDI. DocSense reads them with over 97% extraction accuracy across 100+ document types and 170+ languages, with no templates (Transformance platform data, 2026; how AI reads remittance advice).
How are payments applied and posted back in Business Central?
Transformance proposes which open entries each payment pays, a person approves within your thresholds, and the approved application is posted to Business Central, closing the invoice entries it fully pays.
In Microsoft’s terms, a payment line that pays one invoice uses Applies-to Doc. No.; one that pays several uses Set Applies-to ID, with an Amount to Apply per entry, so a partial payment leaves a remaining amount. If the customer card says Apply to Oldest, “payments are applied to the oldest open credit entry, unless you manually specify an entry” (Microsoft Learn, 2025).
Business Central’s own Payment Reconciliation Journal imports bank transactions, suggests applications by rules with a Match Confidence of Low, Medium or High, and recognises bank entries already posted, which “helps prevent double-posting” (Microsoft Learn, 2024).
In Transformance, matching draws on the remittance and the customer’s history as well as the bank line, which is what lump sums, short pays and wrong references need. ClearMatch auto-matches 95% of payments, runs end to end in under 8 minutes and validates 100% of postings, and nothing posts without human sign-off (Transformance customer data, 2026). See ClearMatch.
Applying entries in different currencies must be enabled first; small residuals then post to the Realized Gains or Realized Losses account (Microsoft Learn, 2025). The approver sees the proposed application and its amounts before anything posts. Across ERPs: how external systems clear open items and the ERP field map.
What happens with short payments and exceptions?
When a payment does not match, Vero investigates from Customer 360 and internal and external sources, proposes an application with the evidence, and a person decides before anything posts.
A short pay goes one of two ways. Inside the payment tolerance (Payment Tolerance % and Max Pmt. Tolerance Amount), Business Central closes the invoice and posts the difference to the tolerance accounts on the customer posting group. Outside it, the difference stays as remaining amount on the invoice entry (Microsoft Learn, 2024).
Behind a larger gap there is usually a deduction. ClaimIQ classifies it into one of six categories with 97% identification accuracy, in under 15 seconds per deduction (Transformance customer data, 2026). In Business Central, a partial application leaves the deducted amount open on the invoice until a person settles or disputes it. See ClaimIQ and automating partial payments and deductions.
An unidentified payment (no reference, a wrong invoice number, a parent company paying) starts from Customer 360: the customer’s history, group links and open items (matching a payment with no reference).
On the AR collections side, Business Central skips entries marked On Hold when it creates reminders, which is where a disputed invoice belongs (Microsoft Learn, 2024). CollectPulse actions 100% of overdue invoices within 24 hours, and Vero handles 60-80% of routine touches, in Microsoft Teams.
Which Business Central settings stop a posting?
Six Business Central settings stop or change a posting from any external system: the posting window, blocked customers, currency application, payment tolerance, Apply to Oldest and duplicate bank transaction IDs.
Business Central settings that stop or change a posting
Agree the posting window first. Allow Posting From and Allow Posting To on General Ledger Setup “apply to the company and to all users”, and User Setup periods “overrule” them (Microsoft Learn, 2026). A payment with a 31 October value date that reaches the statement on 1 November, after October is closed, falls outside the window if it posts on 31 October, and Business Central rejects it with “Posting date is not within your range of allowed posting dates”. Microsoft documents that exact message on a page about the Adjust Cost batch job (Microsoft Learn, 2026).
Blocked = All means “No transaction is allowed for this customer, including payments” (Microsoft Learn, 2024). Cash from an insolvent customer is a decision for a person.
Who approves postings, and what is logged?
Approval thresholds are set by amount, entity and customer; administrators configure the rules, finance users approve, and every decision is logged with its input, confidence and approver.
Transformance runs a 4-level approval model (read, recommend, execute, post) with a human in the loop for every ERP posting. In Business Central, an entity is a company. An illustrative rule: every application above a set amount in one company, or for a key account, goes to a named approver.
The Transformance log stores the timestamp, what the system did, what the user did, who approved, the input and the confidence. Business Central keeps its own posting history in G/L entries, customer ledger entries and the G/L Register. Together they give your auditor the why (Transformance) and the what (Business Central); the audit trail is the join between them.
More on approval thresholds and what an AI agent’s audit trail records.
How is a wrong posting corrected in Business Central?
In Business Central a wrong application is corrected in two steps: unapply the entries, then reverse the transaction; Transformance writes the correction back after a person approves it.
Microsoft’s rules: “You can only reverse entries that are posted from a general journal line. An entry can only be reversed one time.” The reversing entry keeps the document number and posting date, with the opposite sign, and “after you reverse an entry, you must make the correct entry” (Microsoft Learn, 2026).
How a wrong application is corrected in 4 steps:
- A person approves the correction in Transformance, with the reason.
- Unapply the customer ledger entries, latest application first; the closed entries reopen.
- Reverse the transaction. For a payment reconciliation journal posting, use Reverse Register on the G/L Register page, or copy the posted lines to a journal with the opposite sign (Microsoft Learn, 2024).
- Post the correct application as a new proposal, approved like any other.
One case belongs to your Business Central team: if you use an additional reporting currency (ACY), Microsoft says “you must manually reverse the amounts”.
Illustrative example: one lump sum against three invoices
In an illustrative case, a customer pays USD 24,550 against three invoices totalling USD 25,000, with a USD 450 deduction noted in the remittance. Names and amounts are fictional.
Customer A has three open invoice entries in the company C100: USD 10,000, USD 8,000 and USD 7,000. Payment tolerance is a maximum of USD 5. The bank line of USD 24,550 names only two of the three invoices.
- The remittance. DocSense reads the emailed PDF, which lists all three invoices and “less 450 damaged goods”.
- The proposal. Vero proposes applying USD 10,000 and USD 8,000 in full and USD 6,550 to the third invoice, leaving USD 450 open. ClaimIQ classifies the USD 450 as a damaged-goods deduction.
- Why tolerance does not close it. USD 450 is far above the USD 5 maximum, so Business Central keeps it as remaining amount on the third invoice.
- The approval. The application exceeds the threshold set for C100, so the AR lead approves it in Microsoft Teams.
- The result. Two invoice entries close, and one stays open with USD 450 until the deduction is settled or disputed.
The arithmetic: 10,000 + 8,000 + 6,550 = 24,550, and 7,000 less 6,550 leaves 450.
How long does a Business Central integration take?
The Business Central connection typically takes 2-3 days, and your IT team may be involved; full rollout takes up to 4-8 weeks.
A proof of value takes 4-5 weeks on one entity. Prepare six things before the first call with IT:
- the environments and companies in scope;
- who creates the Entra app registration and assigns permission sets, or which other route your environment needs;
- a sandbox for the first tests;
- bank statement formats per bank account;
- the mailboxes and portals where remittances arrive;
- approval thresholds per company.
Data access, the IT security review and the approval rules decide the rollout more than the connection does (what drives the implementation timeline). For groups, name every Business Central company in the scope (AR across many legal entities).
Who Transformance is for
- ERPs: Dynamics 365 Business Central, in production with customers, alongside SAP S/4HANA, SAP ECC, NetSuite, Dynamics 365 Finance & Operations and Odoo; Oracle and Infor supported.
- Size: mid-market to large enterprise, 250 to 2,000+ employees, including groups with several entities and shared service centres.
- Payment volume: from under 1,000 to over 100,000 payments a month.
- Industries: manufacturing, consumer goods and food and beverage, logistics, e-commerce, agriculture, energy and professional services.
- Scope: cash application alone, or the full order-to-cash (cash application, deductions, AR collections, cash forecasting).
Conclusion: Business Central keeps the books, Transformance does the matching
On Business Central, Transformance reads the open entries and the documents behind them, matches and investigates in its own layer, and posts only what a person approves.
Business Central’s own rules still apply to every posting. Start with one company and one bank account in a sandbox, then extend; Book a Call to scope it.
Key terms
- Sub-ledger: a detailed ledger, such as customer ledger entries, that rolls up into a general ledger account.
- Cash application: matching incoming payments to the open invoices they pay and posting the result.
- Remittance advice: the payer’s note that says which invoices a payment covers and why amounts differ.
- Bank reconciliation: agreeing the bank statement with the bank account ledger, line by line.
- Short pay: a payment below the invoiced amount, often because the customer took a deduction.
- Audit trail: the record of who or what did each step, when, on what input, and who approved it.
Related guides
- Which ERP systems does Transformance integrate with?
- How Transformance integrates with Dynamics 365 Finance & Operations
- What AR automation reads from and writes to the ERP
- How external systems post payments and clear open items
- Who approves what when an AI agent works in your ERP
- How AI agents access your ERP and customer data safely
- How long AR automation implementation takes
Frequently Asked Questions
Which Dynamics 365 products does Transformance connect to?
Transformance runs in production with customers on both Dynamics 365 Business Central and Dynamics 365 Finance & Operations. It also connects to SAP S/4HANA, SAP ECC, NetSuite and Odoo, and Oracle and Infor are supported.
How long does it take to connect Transformance to Business Central?
The Business Central connection typically takes 2-3 days, and your IT team may be involved. A proof of value runs 4-5 weeks on one entity, and full rollout takes up to 4-8 weeks.
Can Transformance work across several Business Central companies?
Transformance is built for groups with several entities and shared service centres, with approval thresholds per entity. Because Business Central addresses each company separately, list every company and environment when you scope the connection.
Does Transformance post to Business Central without approval?
No. Nothing posts to Business Central without human sign-off, and approval thresholds are set by amount, entity and customer.
What payment volume does Transformance handle on Business Central?
Transformance is built for companies with from under 1,000 to over 100,000 payments a month, and ClearMatch auto-matches 95% of them.
Is our Business Central data used to train AI models?
No customer data is used to train models. Your data is hosted in your region, and VPC deployment in your own cloud is available.
What does a Business Central integration cost?
The cost depends on scope and the number of entities, for example cash application alone or the full order-to-cash across several companies. Book a Call to scope it.
SAP, SAP S/4HANA, Microsoft, Dynamics 365, Business Central, Oracle, NetSuite, Odoo and Infor are trademarks of their respective owners (SAP SE, Microsoft Corporation, Oracle Corporation, Odoo S.A., Infor). Transformance is not affiliated with or endorsed by them.
