Integrations and source ownership

• Banks. Import bank statement lines as evidence of actual receipts, returns and settlements, and send approved payment instructions for supplier payments and refunds. A payment counts as settled only when the bank’s evidence arrives, and a timeout is treated as uncertain until it is reconciled.

• Carriers and transport providers. When a shipment goes by external carrier, record the carrier reference and bring shipment and delivery events back as integration events. Route optimization and live tracking stay with the transport provider.

• Plant and packing line systems. Production entries for packing work orders can arrive as integration events from the plant’s own systems. Kiln control, process data and laboratory test results stay in those systems.

• Document acknowledgments. Where an invoice or other document has to be acknowledged by an outside service, record the acknowledgment as an integration event against the document. Tax codes hold your configured treatment; the app does not file returns.

• Your previous ERP or spreadsheets. Bring opening balances and open documents across through a reviewed migration batch with one opening journal and itemized remaining balances.

Every inbound message is recorded in integration events with its source, external key, payload hash and the time it occurred and was received. It is verified before it changes anything, and applying the same event twice has no further effect. Outbound instructions are recorded in integration deliveries with their destination, economic key and payload hash, and a retry points to the attempt it repeats. Events that cannot be applied stay in a review state with their original payload.

Agree the source of truth, field mapping and retry policy for each connection before it runs on a schedule. Keep credentials in the approved secret store with the smallest scope the provider allows. Reconcile received, applied, ignored and rejected events against the provider’s totals, and rehearse a duplicate event, a timeout and a rejected payment before go-live. Availability depends on each provider’s API and your agreement with them.

Use the implementation plan to agree integration acceptance criteria.