Integrations and source ownership

• Accounts payable and ledger. Approved invoices are paid in your AP system and marked Paid by AP; inventory and adjustment values post to your ledger.

• Carriers. Tracking events arrive from carrier AP is against each shipment’s tracking number.

• Suppliers. Purchase orders and acknowledgments can be exchanged by EDI or supplier portal.

• Forecasting tools. Statistical forecasts can be loaded from your forecasting engine into a draft version.

• Production system. Production orders carry an external reference to your plant system for completion updates.

Each connection needs an agreed source of truth, field mapping, event identifier and retry policy. Keep credentials in the approved secret store and grant the smallest permitted scope. A repeated tracking event must not be recorded twice, and a repeated acknowledgment must not change an order twice. Queue rejected records with their source identifier and a visible reason.

Reconcile source totals to accepted, rejected and pending events. Review a provider timeout, a duplicate delivery, a changed source record and a revoked credential before enabling schedules. Availability depends on each provider’s API, commercial access and configuration.

Use the implementation plan to agree integration acceptance criteria.