Compute
Microsoft Dynamics 365 Finance Sync mapping
Choose the Dynamics 365 edition, map a customer payable record to Business Central purchaseInvoices, and read it back.
On this page
Resolve the edition first
Microsoft Dynamics 365 is a family. Finance Sync must distinguish Business Central from Dynamics 365 Finance before planning a write.
An unclear edition returns FINANCE_SYSTEM_EDITION_REQUIRED. Do not select an edition from a company name alone.
Business Central recipe
For a customer-payable flow in Business Central, the external object kind is purchaseInvoices. The recipe is a direction-specific mapping, not a Lithi-owned connector.
Confirm the organization, supplier, duplicate check, currency, purchase-order policy, destination, and accounting treatment. Preserve provenance, freshness, and conflict state.
Review and apply
Inspect the source, plan a dry run, show the exact purchaseInvoices change, receive entitled approval, apply idempotently, and read the object back.
Never guess tax treatment, legal entity, account, cost centre, project, or approver. Stop when the edition or treatment is unresolved.
Keep the payment boundary
Dynamics Paid is an external annotation only. It cannot settle a Lithi invoice. Authoritative Lithi invoice read-back remains customer payment truth.
If read-back differs, preserve the evidence and reconcile it before another apply.