Skip to content
ERP · Two-way sync platform

Dynamics 365 Business Central and SuiteAnalytics integration

Plan how Dynamics 365 Business Central and SuiteAnalytics should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

  • Scope your workflow with an integration engineer
  • Review the systems, records, and updates you need
Integration planning
stacksync.com
Dynamics 365 Business Central
SuiteAnalytics
Review the integration scope

Built for teams where self-serve, reliability and scale matter

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo

Proposed workflow

Customer sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting eventA change involving Dynamics 365 Business Central Customers or SuiteAnalytics Customer needs a defined result in the other system.

  1. Start with Dynamics 365 Business Central Customers and SuiteAnalytics Customer. Use the record-matching and field-ownership rules from your mapping worksheet.

  2. Resolve person or company type, legal entity, business role, and any billing account before transactions.

  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyTest an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

Review records and field ownership

Proposed record relationships

Records to connect

Use these examples to define record matching and field ownership for your technical review.

Download the mapping worksheet

CSV · No email required

Example record relationships between Dynamics 365 Business Central and SuiteAnalytics
Dynamics 365 Business Central recordSuiteAnalytics recordRecord matchingField ownership
CustomersProposed record; confirm Stacksync object support.Record matchingCustomerDocumented record: Read: Supported. Write: see guide.Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.
CustomersProposed record; confirm Stacksync object support.Customer identity assessmentContactDocumented record: Read: Supported. Write: see guide.Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.
Sales InvoicesProposed record; confirm Stacksync object support.Record matchingInvoiceDocumented record: SupportedRetain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.The financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite.

These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.

Record coverage to review

Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.

Dynamics 365 Business Central

Connection and object support require review

Record types to review with Stacksync

Record typesCoverage and requirements
  • Customers
  • Vendors
  • Items
  • Sales Orders
  • Sales Invoices
  • Purchase Orders
Confirm support for this record type and the direction you need.

Discuss Dynamics 365 Business Central requirements

SuiteAnalytics

Read-only connector

Record types covered in the setup guide

Record typesCoverage and requirements
  • Customer
  • Contact
  • All custom objects
  • Nexus
  • Tax Type
  • Sales Tax Item
  • Billing Schedule Customer Subsidiary Relationship
  • Account
  • Accounting Period
  • Bin Transfer
  • Currency Rate
  • Price Level
  • Term
  • Subsidiary
  • Vendor
  • Vendor Category
  • Employee
  • Other Name Category
  • Vendor Subsidiary Relationship
  • Project
  • Project Status
  • Project Task
  • Job Type
  • Task
  • Partner
  • Customer Status
  • Phone Call
  • Support Case
  • Calendar Event
  • Note Type
  • Message
  • Contact Category
  • Contact Role
  • Customer Category
  • Customer Message
  • Department
  • Expense Category
  • Job Status
  • Classification
  • Location
  • Saved Searches
  • Deleted Records
Reading: ✅ Supported. Updating this object: confirm availability.
  • Invoice
  • Sales Order
  • Check
  • Credit Card Charge
  • Credit Card Refund
  • Credit Memo
  • Currency Revaluation
  • Customer Deposit
  • Customer Payment
  • Customer Refund
  • Deposit
  • Deposit Application
  • Estimate
  • Expense Report
  • Intercompany Journal Entry
  • Advanced Intercompany Journal Entry
  • Item Fulfillment
  • Item Receipt
  • Journal Entry
  • Opportunity
  • Purchase Order
  • Transfer
  • Vendor Bill
  • Vendor Credit
  • Vendor Payment
✅ Supported. Confirm field permissions and sync direction.
  • Lead
  • Case
  • Published Reports
Reading: 🔓 Request Access. Updating this object: confirm availability.

Read the SuiteAnalytics connector guide

Connection essentials

Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.

View setup requirements and limits
Connection requirementDynamics 365 Business CentralSuiteAnalytics
Integration interfaceREST API built on OData v4 (standard API v2.0), extensible with custom API pages in ALSQL over ODBC, JDBC, and ADO.NET (SuiteAnalytics Connect)
AuthenticationConfirm the credentials, API plan, and permissions required for Dynamics 365 Business Central.NetSuite token-based authentication with integration credentials, access token, account ID, and a role with SuiteAnalytics permissions.
Change detectionConfirm how Stacksync detects changes for this connector and the objects you need.The saved Stacksync guide does not specify the change-detection mechanism.
Read accessConfirm with StacksyncAvailable for supported records
Write accessConfirm with StacksyncNot supported by this connector

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

  • SOC 2 Type II
  • ISO 27001
  • HIPAA BAA
  • GDPR
  • CCPA
  • DPF US-EU-UK-CH

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

Dynamics 365 Business Central
Integration interface
REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL
Authentication
Confirm the credentials, API plan, and permissions required for Dynamics 365 Business Central.
Change detection
Confirm how Stacksync detects changes for this connector and the objects you need.
Read access
Confirm with Stacksync
Write access
Confirm with Stacksync
Setup requirements
  • Identify the Dynamics 365 Business Central account, edition, environment, and business objects the integration must access.
  • Confirm a Stacksync connector or implementation path for Dynamics 365 Business Central, including read/write support, authentication, and initial-load limits.
Limitations to check
  • Confirm Stacksync support for Dynamics 365 Business Central and the record types your workflow needs.
  • Review write-back, deletion handling, update timing, and account limits with the integration team.
SuiteAnalytics
Integration interface
SQL over ODBC, JDBC, and ADO.NET (SuiteAnalytics Connect)
Authentication
NetSuite token-based authentication with integration credentials, access token, account ID, and a role with SuiteAnalytics permissions.
Change detection
The saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
Read access
Available for supported records
Write access
Not supported by this connector
Setup requirements
  • Have a NetSuite administrator enable SuiteAnalytics Connect and token-based authentication.
  • Create an integration, access token, and role with the SuiteAnalytics Connect permissions listed in the authorization guide.
Limitations to check
  • SuiteAnalytics is a read-only route. Use a separately supported NetSuite connector for write-back requirements.
Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

SuiteAnalytics setup guide

Prepare Dynamics 365 Business Central and SuiteAnalytics access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

Dynamics 365 Business Central setup checklist
  • Identify the Dynamics 365 Business Central account, edition, environment, and business objects the integration must access.
  • Confirm a Stacksync connector or implementation path for Dynamics 365 Business Central, including read/write support, authentication, and initial-load limits.
SuiteAnalytics setup checklist
  • Have a NetSuite administrator enable SuiteAnalytics Connect and token-based authentication.
  • Create an integration, access token, and role with the SuiteAnalytics Connect permissions listed in the authorization guide.

Setup guides: Authorize SuiteAnalyticsNetSuite SuiteAnalytics Connect

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the Dynamics 365 Business Central and SuiteAnalytics planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Record identity and field ownership

Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.

Download the mapping worksheet · CSV, no email required

Record matching

Customers / Customer

Compare whether Dynamics 365 Business Central Customers and SuiteAnalytics Customer describe the same customer in your business.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Dynamics 365 Business Central
Object support to establish
SuiteAnalytics
Documented record · Read: ✅ Supported. Write: see guide.
Record identity
Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
Field ownership
Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

Fields to include

  • Source customer ID
  • Person/company classification
  • Legal entity or business unit
  • Destination identity reference
Record dependencies
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Validation
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Recovery
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

References: SuiteAnalytics: Customer documentation

Customer identity

Customers / Contact

Before linking Dynamics 365 Business Central Customers to SuiteAnalytics Contact, check whether the customer is an individual or a company. Match the correct record type in each system.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Dynamics 365 Business Central
Object support to establish
SuiteAnalytics
Documented record · Read: ✅ Supported. Write: see guide.
Record identity
Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
Field ownership
Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

Fields to include

  • Source customer ID
  • Person/company classification
  • Legal entity or business unit
  • Destination identity reference
Record dependencies
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Validation
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Recovery
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

References: SuiteAnalytics: Contact documentation

Record matching

Sales Invoices / Invoice

Compare whether Dynamics 365 Business Central Sales Invoices and SuiteAnalytics Invoice describe the same customer invoice in your business.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Dynamics 365 Business Central
Object support to establish
SuiteAnalytics
Documented record · ✅ Supported
Record identity
Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.
Field ownership
The financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite.

Fields to include

  • Source invoice ID
  • Customer or supplier reference
  • Line totals
  • Currency
  • Posting/payment status
Record dependencies
Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
Validation
Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
Recovery
Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.

References: SuiteAnalytics: Invoice documentation

Business process

Sales Orders / Invoice

Order-to-invoice handoff: Dynamics 365 Business Central Sales Orders provides context for SuiteAnalytics Invoice. These are related records, not equivalent entities.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Dynamics 365 Business Central
Object support to establish
SuiteAnalytics
Documented record · ✅ Supported
Record identity
Link order and line IDs to invoice and line IDs; allow partial invoicing and multiple invoices per order.
Field ownership
Finance owns invoice posting; the order system supplies the approved commercial context.

Fields to include

  • Source record reference
  • Destination record reference
  • Approved handoff state
  • Duplicate-detection key
Record dependencies
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Validation
Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.
Recovery
Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

References: SuiteAnalytics: Invoice documentation

Business process

Sales Orders / Item Fulfillment

Order-to-fulfillment handoff: Dynamics 365 Business Central Sales Orders provides context for SuiteAnalytics Item Fulfillment. These are related records, not equivalent entities.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Dynamics 365 Business Central
Object support to establish
SuiteAnalytics
Documented record · ✅ Supported
Record identity
Link the order and selected line IDs to separate fulfillment IDs; allow split shipments.
Field ownership
The fulfillment owner decides when an approved order can ship and how cancellations are handled.

Fields to include

  • Source record reference
  • Destination record reference
  • Approved handoff state
  • Duplicate-detection key
Record dependencies
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Validation
Test partial fulfillment, an out-of-stock line, and a repeated request that must not create a second shipment.
Recovery
Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

References: SuiteAnalytics: Item Fulfillment documentation

Record matching

Sales Orders / Sales Order

Compare whether Dynamics 365 Business Central Sales Orders and SuiteAnalytics Sales Order describe the same sales order in your business.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Dynamics 365 Business Central
Object support to establish
SuiteAnalytics
Documented record · ✅ Supported
Record identity
Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.
Field ownership
Decide which system approves the order and which can cancel or amend it after fulfillment begins.

Fields to include

  • Source order ID
  • Customer reference
  • Line references and quantities
  • Order status
  • Currency
Record dependencies
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Validation
Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
Recovery
Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

References: SuiteAnalytics: Sales Order documentation

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Customers / Customer to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.

Stacksync managed sync

Best fit
Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility
Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose
Check record matching: Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit
A vendor-built integration may fit if it supports your Dynamics 365 Business Central and SuiteAnalytics record types.
Operating responsibility
Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose
First check whether either vendor offers this integration. If available, verify Customers / Customer, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit
Consider explicit orchestration for the Sales Orders / Invoice handoff.
Operating responsibility
Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose
Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.

File or scheduled snapshot

Best fit
Consider for a one-time Dynamics 365 Business Central / SuiteAnalytics migration or a reporting need with an explicit freshness window.
Operating responsibility
Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose
Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Customer sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Customers or Customer record needs a defined result in the other system.

  1. Start with Dynamics 365 Business Central Customers and SuiteAnalytics Customer. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve person or company type, legal entity, business role, and any billing account before transactions.
  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Customer sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Customers or Contact record needs a defined result in the other system.

  1. Start with Dynamics 365 Business Central Customers and SuiteAnalytics Contact. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve person or company type, legal entity, business role, and any billing account before transactions.
  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Customer invoice sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Sales Invoices or Invoice record needs a defined result in the other system.

  1. Start with Dynamics 365 Business Central Sales Invoices and SuiteAnalytics Invoice. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.

If it fails: Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.

Reconcile Dynamics 365 Business Central business records with SuiteAnalytics

This is an evaluation scenario; connector and operation support require confirmation.

Starting event: A finance-owned record in Dynamics 365 Business Central needs operational visibility through Customer or Vendor.

  1. Select Customers or Vendors with the correct legal entity, period, and currency.
  2. Define a reporting relationship in SuiteAnalytics; do not equate customer records, ledger accounts, and posted transactions.
  3. Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.

Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.

If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.

Initial load and acceptance testing

Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.

Customers / Customer

Test case

Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

Expected result

The expected customer relationship is preserved with no duplicate action or unintended write.

Customers / Contact

Test case

Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

Expected result

The expected customer relationship is preserved with no duplicate action or unintended write.

Sales Invoices / Invoice

Test case

Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.

Expected result

The expected customer invoice relationship is preserved with no duplicate action or unintended write.

Sales Orders / Invoice

Test case

Test a partially invoiced order, tax rounding, and a repeated handoff without generating another invoice.

Expected result

The expected sales order relationship is preserved with no duplicate action or unintended write.

Direction and permissions

Test case

Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.

Expected result

Only an approved, supported direction and permitted fields are written.

Freshness and reconciliation

Test case

Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.

Expected result

The process meets its agreed freshness target and reconciliation has no unexplained differences.

Failed updates, retries and recovery

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated customer change

Investigate

Inspect Dynamics 365 Business Central Customers and SuiteAnalytics Customer, their IDs, and the destination error.

Next action

Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Rejected or repeated customer change

Investigate

Inspect Dynamics 365 Business Central Customers and SuiteAnalytics Contact, their IDs, and the destination error.

Next action

Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Rejected or repeated customer invoice change

Investigate

Inspect Dynamics 365 Business Central Sales Invoices and SuiteAnalytics Invoice, their IDs, and the destination error.

Next action

Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.

A record type or update is unavailable

Investigate

Check the Dynamics 365 Business Central and SuiteAnalytics connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between Dynamics 365 Business Central and SuiteAnalytics

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

Dynamics 365 Business Central SuiteAnalytics Direction not supported

Detect changesThis route requires read access from Dynamics 365 Business Central and write access to SuiteAnalytics; the documented connector restrictions do not permit it.

Apply updatesUse a supported direction or review a separate integration method for this requirement.

SuiteAnalytics Dynamics 365 Business Central Direction requires confirmation

Detect changesThe saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.

Apply updatesConfirm that Stacksync can create or update the records you need in Dynamics 365 Business Central.

Update timing and record limits
  • Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
  • Review write-back, deletion handling, update timing, and account limits with the integration team.
FAQ

Dynamics 365 Business Central and SuiteAnalytics integration FAQ

Further reading

Resources for your technical review

Next step

Plan your integration with an engineer

Walk through your Dynamics 365 Business Central and SuiteAnalytics records, field mappings, and requirements with an integration engineer.

Talk to an engineer Explore plans and pricing