Microsoft Dynamics GP integration.

Choose whether the integration moves master data, reports transactions, or creates an approved financial document. Preserve entity, currency, accounting period, and header/line references. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

Write-back support is not established for this connection. Review the Microsoft Dynamics GP records and fields you need with a Stacksync engineer, then test the required operation with a representative record.

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.

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

Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact. Reconcile totals within the same entity and currency. A repeated delivery does not post the same financial transaction twice.

Start with one workflow and a sample record from Customers, GL Accounts & Journal Entries and Vendors. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document.