Step 01
Connect the data
A native MS Dynamics 365 Business Central connector is on our roadmap. Today the data comes in by CSV import or a custom API mapping, into the same ledger every other source feeds. No engineering time on your side.
Commenda integration
for MS Dynamics 365 Business Central
Your books sit in MS Dynamics 365 Business Central. Keeping them compliant across borders is a separate job, and it is the one Commenda does. Commenda pulls transactions and trial balances straight from MS Dynamics 365 Business Central, then registers, files, and remits across 70+ countries.
Trusted by global businesses
How it works
How Commenda's integration works for MS Dynamics 365 Business Central
Step 02
Full control over what you share
You choose which data models sync, and what Commenda can read and write. Scopes stay visible and editable after setup, and access runs per user and per entity.
Step 03
Get global compliance
Sales tax, VAT, and GST calculate on every transaction. Your monthly tax and accounting close on the same data. Cross-company transactions get checked against your transfer pricing policy.
Products
How MS Dynamics 365 Business Central integrates with Commenda's product stack
One MS Dynamics 365 Business Central connection serves every Commenda product. The same sync that calculates sales tax, VAT, and GST also feeds your transfer pricing checks and your books, so you never wire up MS Dynamics 365 Business Central twice.
MS Dynamics 365 Business Central indirect tax integration
We calculate sales tax, VAT, and GST on every transaction. Your global exposure summary updates in real time.
Learn more
MS Dynamics 365 Business Central transfer pricing integration
We pull intercompany transactions from your ERP and check them against your transfer pricing policy.
Learn more
MS Dynamics 365 Business Central tax and accounting integration
We fetch financial statements from all your accounting tools and help you stay financially compliant across 70+ countries.
Learn more
Custom integrations and API access, supported
Running custom workflows in MS Dynamics 365 Business Central? We shape the integration around how your business and your accounting actually work, then maintain it after launch.
API docs
Most Commenda products are also available as an API. Pull sales tax calculations, exposure data, and filings straight into your own product or stack. REST API for anything custom.
Read the API docs (opens in a new tab)Integrations supported
100+ integrations with one unified API
Built for finance teams running international operations without a dedicated compliance function.
StripePayments
ShopifyE-Commerce
QuickBooks OnlineAccounting
XeroAccounting
Oracle NetSuiteAccounting
SAP S/4HANAERP
SAP Business OneERP
BigCommerceE-Commerce
WooCommerceE-Commerce
Zoho BooksAccounting
MS Dynamics 365 Business CentralAccounting
OdooAccounting
Sage IntacctAccounting
Sage Business CloudAccounting
Tally ERP9Accounting
Zoho InvoicePayments
WaveAccounting
WafeqAccounting
Frequently asked questions
What finance teams ask before they connect MS Dynamics 365 Business Central to Commenda.
A native MS Dynamics 365 Business Central connector is on our roadmap. Today it connects through CSV import or a custom API mapping, which covers transaction sync, exposure tracking, and filing from the same ledger as every other source. Raise it during onboarding and we will confirm the path for your setup and prioritise accordingly.
Yes. A monthly CSV upload is fully supported, with mapped fields for transaction date, amount, ship-to state, and zip, plus optional invoice, shipping, and handling. Where data sits in a warehouse such as Metabase rather than a supported system, we work from structured exports or a custom data connection.
Yes. We read the system you are on today and the one you are moving to, so the ledger stays continuous across the migration and your filings do not gap. Product mapping is redone against the new catalogue as part of the move.
A voluntary disclosure agreement usually waives penalties and leaves interest, and the waiver succeeds in roughly 98% of the ones we run. Lookback periods are two to four years in most states and unlimited in a few, Nevada among them. Below a meaningful liability a plain backdated registration costs less than a VDA.
Every source is read separately and consolidated into one ledger tagged by ship-to state, with the source visible on each transaction. Tax a marketplace already collected stays separate from revenue that still needs it, so a direct MS Dynamics 365 Business Central sale gets tax applied while an already-taxed marketplace order does not.
Yes. Three endpoints cover tax calculation by product, tax code, and address, physical nexus management by warehouse address, and registrations and exemptions. Roughly 100ms on a calculation, and white-label, so your customer never sees Commenda.
We do. The platform gives you structure and visibility, and an in-house team handles the registrations, filings, and jurisdiction-specific work. You get a named point of contact rather than a ticket queue.
A five-step migration: consultation, integration, data transfer, testing, go-live. A dedicated team does the product tax code mapping, re-runs your exposure footprint, moves your exemption certificates, and rebuilds the channel connections. You also get a named account manager instead of a ticket queue. We have written up both routes: switching off Avalara and switching off Vertex.
