Integrations and source ownership

• Detailed time capture. If work is recorded in another service, agree how its supporting evidence reaches the client document and billable submission. Preserve the source identity and let Accounting Reviewer decide the submitted scope before invoicing.
• Invoice delivery. Configure any service used to deliver the client invoice. Agree the reviewed amount, destination and returned reference. Retain delivery evidence separately from approval and cash confirmation.
• Bank or payment service. Configure receipt imports with stable event references and a verification policy. Reconcile amounts with the source and test duplicate deliveries before allowing cash application.
• Accounting service. Where posting uses an external provider, map the intended account identities and retain its actual result with the operation receipt. Agree who owns the accounting-period check and correction process.
• Exchange-rate source. Agree the source of effective rates and the handling of imported currencies. Keep the rate’s effective date visible and reconcile a sample to the original amount before using it in routine work.

Treat each connection as setup work with an accountable owner, field mapping and retry rule. Use the source event or operation identity to distinguish a repeat delivery from a new action. Keep credentials in the approved secret store and limit the connection to its required organization and actions.

Rehearse a timeout after an effect has been saved, a repeated event and a rejected request. Retain failure reasons and reconcile source totals with accepted results. Query an external provider during completion checks only when that operation used the provider. Agree acceptance evidence in the implementation plan.