Paystand's native integration with Microsoft Dynamics 365 Business Central connects your BC company to your Paystand account so that receivables, payments, and related accounting activity stay in sync between the two systems. This article gives a high-level overview of what the integration keeps in sync and in which direction data flows, so you know what to expect from the connection.
This is a conceptual overview, not a technical or developer reference. It does not describe internal implementation details, API specifications, or configuration steps.
How the connection works, at a high level
Paystand connects to your Business Central environment using a secure Microsoft Entra ID app registration set up during implementation (see the Business Central Implementation Guide for setup steps). Each connection is scoped to a single BC company — if your organization uses multiple companies, each is set up and managed as its own connection. Data generally syncs automatically in the background for the areas described below; your implementation team can confirm expected timing for your environment.
Customers
Customer records maintained in Business Central sync into Paystand, so the customers you already manage in BC appear as payers in your Paystand account. This means you don't need to duplicate customer setup work across both systems.
Invoices & Receivables
Posted sales invoices (and related receivable documents) in Business Central sync into Paystand as open receivables. This allows those invoices to be presented for payment, included in collection workflows, and paid through Paystand's checkout and billing experiences.
A couple of related document types are also part of this picture, depending on your Business Central setup:
- Service invoices — in addition to standard sales invoices, other billable document types such as service invoices can be included in the same sync and payment workflow.
- Finance charges — if a posted invoice accrues a finance charge for late payment, that finance charge document can also be presented and paid through Paystand alongside the original invoice.
Payments
When a customer pays an invoice through Paystand, that payment is posted back to the corresponding customer and invoice in Business Central. This keeps your BC customer ledger up to date without manual entry, and lets your team continue working from Business Central as the system of record for accounting.
The integration is designed to handle common real-world payment scenarios, not just simple one-invoice, one-payment cases:
- Partial payments — if an invoice is only partially paid, Business Central reflects the remaining open balance rather than treating the invoice as fully settled.
- One payment across multiple invoices — a single payment can be applied across more than one open invoice for the same customer.
- Unapplied payments — if a payment doesn't yet have a clear matching invoice, it can be held as unapplied in Business Central and applied later once it's identified.
- Corrections — if a payment application needs to be corrected or reversed, that correction is reflected on the Business Central side as well, so your customer ledger and Paystand stay consistent.
- Multi-currency — if an invoice is issued in a currency other than your company's base currency, the corresponding payment and exchange rate are correctly reflected when posted back to Business Central.
Fees
Where applicable, merchant or convenience fees associated with a payment are recorded alongside the related payment activity in Business Central, so your books reflect the full picture of what was collected and what was assessed in fees.
Credit Memos & Refunds
Credit memos in Business Central can be recognized and applied — including to a specific open invoice — as part of the payment process, so credits already issued in BC are reflected correctly when a related payment is processed through Paystand. Refunds are handled the same way: if a payment is refunded, whether or not a credit memo is involved, that refund is reflected back in Business Central so your records stay accurate.
Bank Reconciliation
Settlement activity from Paystand can be reflected in your Business Central bank reconciliation process, helping align what was deposited with what was recorded. If a statement was reconciled incorrectly, the integration also supports revisiting and correcting a previously reconciled statement rather than requiring a manual fix outside the system.
Dimensions
Dimension values (for example, cost center or department tracking) can be included as part of invoice and payment data, depending on how your Business Central environment is configured. Your implementation team can confirm current dimension support for your specific setup.
What this overview intentionally leaves out
To protect the security and integrity of the integration for all merchants, this article does not include internal API specifications, authentication internals, data schemas, or implementation-level details of how the sync is performed. If you're building a complementary or custom integration and have questions about a specific workflow not covered here, please reach out to your Paystand implementation or support contact so we can advise without exposing sensitive integration details.
Related articles
- Business Central Implementation Guide — user provisioning and permission setup
- Maximizing Efficiency with Paystand's Microsoft Dynamics Business Central Integration: Your Essential Guide