Supplier data, open balances, approval policy, bank-connection requirements, source-system identifiers and the people authorized to accept the rollout. Confirm the effective tax-year configuration with the responsible finance team before enabling filing.
Implementation
Start with a controlled supplier and invoice population, then expand after reconciliation.
Implementation phases
- Confirm scopeTeam and ERP.ai
- Prepare source dataTeam and ERP.ai
- Configure decisionsController / CFO
- Connect handoffsTeam and ERP.ai
- Reconcile the pilotTeam and ERP.ai
- Operate and reviewTeam and ERP.ai
Phase 1 · Team and ERP.ai
Confirm scope
Agree supplier populations, approval bands, source ownership, bank methods and filing ownership. Identify the ledger and identity directories that remain external.
Phase 2 · Team and ERP.ai
Prepare source data
Resolve duplicate vendors and invoice identifiers. Confirm opening bills, credits, pending payments and tax-document exceptions.
Phase 3 · Controller / CFO
Configure decisions
Controller / CFO reviews the authority policy with the administrator, who binds authenticated identities to scopes and approval tiers. Test independent bank verification and payment release with both allowed and rejected actions.
Phase 4 · Team and ERP.ai
Connect handoffs
Verify intake retries, procurement references, draft journals, payment acknowledgements and filing results in a controlled environment.
Phase 5 · Team and ERP.ai
Reconcile the pilot
Trace matched, disputed, partially paid, returned and corrected cases. Compare balances with the source records before widening the supplier population.
Phase 6 · Team and ERP.ai
Operate and review
Assign exception owners and monitor connector failures, stale approvals and reconciliation differences.
Use Proto to propose and review changes to fields, views and workflows. Re-test affected authority and accounting handoffs before release. Existing approvals and reporting snapshots retain the basis on which they were made.
1
Say what you need"Add a second approval above 10,000." Plain language.
2
Review the branchThe change lands on a branch with the diff and a test run.
3
ReleaseMerged into your workspace. Every user gets it.