Integrations and source ownership

• Laboratory and document systems. Agree how approved result evidence becomes a stability result or supporting certificate document. Preserve the batch mapping and source evidence identity through a verified capture route. External laboratory execution, controlled document approval and signatures remain governed by the source system.
• Supplier exchange. Map supplier orders and receipt information to purchase orders, purchase order lines and goods receipts. Agree provider access and replay handling before enabling supplier EDI.
• Shop-floor scanners and instruments. A scanner can request a permitted stock or execution action after its actor and unit mapping are configured. Use the instrument’s calibration evidence when assessing whether it is suitable for the requested inspection. Test wrong product, wrong unit and repeated-device-event refusals.
• Carrier service. Connect the agreed shipment command and confirmation source to the delivery’s carrier reference. A label or booking response is separate from the recorded Shipment stock movement. Reconcile partial shipments and retries before release.
• Bank and external ledger. Agree payment preparation, confirmation references and any reviewed journal export. Retain the bank reference on each supplier payment and customer receipt for reconciliation. Reconcile an authorized payment run with the bank’s actual settlement confirmation.

Assign a source owner and field mapping to each connection. Credentials stay in the approved secret store with the permitted scope. Use the actual platform or external event identity for duplicate prevention; verify the import mapping and replay rule before accepting repeated source deliveries.

Rehearse a repeated source event, conflicting content, revoked access and a provider timeout. Retain rejected evidence with the source identity and cause through the configured error-handling route. Specialty captures must not duplicate stock or journal effects. Reconcile accepted source records with their operational result before enabling a schedule.

Agree the implementation boundary and inspect reference mappings. Each provider’s access and validation requirements form part of the connection scope.