Provide the entity and account structure, party and product masters, unit conversions, approved pricing and terms, stock and cost records, open-document history and financial control totals. Include delivery commitments, production definitions and actual work in progress where relevant. Identify source owners, independent reviewers, required provider contacts and unresolved exceptions at the cutoff.
Implementation
Plan a connected rollout around your entities, goods and financial controls.
Agree the first operating scope and the evidence that will prove it works. Implementation is priced separately and depends on your source data, policies and required connections.
Implementation phases
Phase 1 · Team and ERP.ai
Define the operating boundaries
Confirm the legal entities, functional currencies, warehouses, products and dealer or supplier relationships. Decide the accepted price, credit and title terms, the standard-cost basis, and which assembly or kitting work is included. Name the people who prepare and independently approve commercial, warehouse and finance decisions. Manual delivery planning does not establish a live vehicle, driver or carrier service.
Phase 2 · Team and ERP.ai
Configure the connected rules
Review product units, pricing precedence, purchase authority, receipt acceptance, stock claims, route outcomes, production versions and posting profiles. An order approval, actual physical event and invoice release must keep their distinct evidence. Rehearse both dispatch-title and delivery-title work where applicable. Confirm entity scope and sensitive commercial or banking access across interactive and integration actions.
Phase 3 · Team and ERP.ai
Reconcile the migration cutoff
Map source identities before loading accepted open orders, purchase scope, current stock layers, reservations, unresolved delivery quantities and work in progress. Reconcile opening ledgers with nonposting detailed receivables, payables, cash and operational history. Retain original prices, source quantities and provider action identities. Importing a historical completed state must not create another receipt, shipment, invoice or settlement.
Phase 4 · Team and ERP.ai
Prove the normal and exception paths
Verify an independently accepted dealer order through physical fulfillment, invoice approval and cash application. Test partial receipts, failed or refused delivery, returns, changed prices and cost standards, competing stock claims and an uncertain payment. For production, reconcile actual material, accepted terminal output, scrap and remaining work in progress. Check that stock, open items and journals reconcile at close before enabling wider operational work.
Use Proto to prepare application changes on a branch for review before release. Version changes to policies, schema, cost standards and integrations with their migration and acceptance cases. Recheck affected quantities, historical allocations, permissions and financial balances before the updated configuration handles new work. A change to a master must not silently rewrite accepted documents or prior stock value.
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.