- Current company, facility, department and permitted-user lists.
- Products, packs, actual supply requirements, required tracking and source date evidence.
- Supplier/customer records, agreed commercial terms, bank and account mappings.
- Assembly instructions, actual work/cost standards and appropriate independent reviewers.
- Opening balances and retained original source history, including unresolved intercompany work.
- A decision on the scope and ownership of each configured external connection.
Implementation
Agree the operating scope, verify source balances and activate reviewed workflows.
Start with the facilities and supply work the team actually runs. Agree who owns each quantity, decision and financial effect before connecting systems or importing history.
Implementation phases
Phase 1 · Team and ERP.ai
Agree the operating scope
Confirm companies, facilities, departments, product classes, units and the real supply packs assembled. Identify existing source systems and the actual people responsible for preparation, independent review and execution.
Phase 2 · Team and ERP.ai
Configure and reconcile
Prepare product and account mappings, authority limits, quality checks and assembly standards. Establish reciprocal company relationships and the selected destination-acceptance title terms. Reconcile opening stock, work in progress, commercial balances and intercompany history with each company's opening ledger.
Phase 3 · Team and ERP.ai
Prove the working paths
Test partial receiving, assembly, actual department use, local goods billing and intercompany supply. Include changed approvals, held stock, returns and a counterpart that has not completed its posting. Confirm that retries preserve successful work and that real bank evidence controls settlement.
Phase 4 · Team and ERP.ai
Activate and review
Activate only reconciled scope with trained users and current policies. Follow open exceptions, compare company source balances with the books and complete the agreed first close. Extend to another facility after its data and responsibilities meet the same checks.
Role permissionsRoles & permissions →
Review changed methods, mappings and authority before they affect new work. Preserve earlier approved quantities, dates and postings. A different intercompany title route or clinical capability needs an explicit new operating contract and verification; changing a label cannot supply it.
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.