Integrations and source ownership

• Bank and payment provider. Configure the bank evidence handoff and any permitted payment instruction connection. Agree ownership of payment references and reconciliation; keep provider outcomes separate from the local release action.
• Customer invoice delivery. Configure the service that delivers customer documents. Check the recipient mapping and retain delivery evidence separately from the invoice send operation receipt.
• Document store. Choose the location for invoice files, statements and tax documents. Keep stable file references and test access with the roles that review the linked record.
• Tax filing service. If the business uses a filing provider, agree the reviewed information it receives and retain its own acknowledgement. Confirm the customer’s filing responsibilities and applicable rules with the responsible adviser during setup.
• Existing accounting or operating systems. Agree which system owns each source document and the ledger. Map account codes and source references before moving opening balances or supplier and customer documents.

Name an owner for each connection and agree the data direction, record mapping and retry behavior. Preserve external references so repeated delivery can be identified before creating another invoice, bill or payment. Keep credentials in the approved connection settings and scope access to the work being performed.

Rehearse a timeout, a repeated message and a changed source document before enabling scheduled transfers. Compare accepted records with rejected and pending work. A successful local action and an external acknowledgement answer different questions; retain both when the process depends on both.

Use the implementation plan to agree the handoff and review evidence.