Connect your ERP to CFO safely

This guide takes an ERP team from authority discovery through dry-run, persistence, and CFO reconciliation using evidence produced by the customer-controlled integration runtime.

Current boundary: DEV for the reference connector and UAT for customer acceptance. There is no PRD scope.

1 · DiscoverObtain a token and verify the organization, destinations, periods, and granted capabilities.

2 · ValidatePersist durable identities and dry-run every required grant tuple before a real write.

3 · ProvePoll jobs, inspect every row, test restart/retry, and reconcile the CFO UI.

Begin with the Quick start, give security owners the authentication guide, and use the UAT checklist for acceptance. Exact methods and schemas are in the API reference.

What counts as final UAT evidence

Postman is useful for connectivity diagnosis, but a final pass must originate from the customer's ERP or integration runtime. That is the only way to prove its token lifecycle, durable retry, and source data flow.