--- title: "ERP implementation checklist: 10 phases from scoping to your first month-end" description: "An ERP implementation checklist for trading businesses: scoping, data cleanup, opening balances, cutover, permissions, test scripts, go-live and month-end." url: https://1flux.ai/guides/erp-implementation-checklist last_updated: 2026-10-11 --- Implementation guide # ERP implementation checklist: 10 phases from scoping to your first month-end A practical checklist for trading, distribution and project-supply businesses, with exit criteria for every phase. Tick items as you go; your progress stays in this browser. Guide Updated 11 October 2026 1. Prepare 1. 1 Scoping 2. 2 Data cleanup 3. 3 Master data 2. Cut over 1. 4 Opening balances Cutover date set 3. Configure and prove 1. 5 Configuration 2. 6 Roles and permissions 3. 7 Testing scenarios 4. 8 Training 4. Go live 1. 9 Go-live on the cutover date 2. 10 First month-end Period closed 1) Prepare: 1. Scoping. 2) Prepare: 2. Data cleanup. 3) Prepare: 3. Master data. 4) Cut over: 4. Opening balances, Cutover date set. 5) Configure and prove: 5. Configuration. 6) Configure and prove: 6. Roles and permissions. 7) Configure and prove: 7. Testing scenarios. 8) Configure and prove: 8. Training. 9) Go live: 9. Go-live on the cutover date. 10) Go live: 10. First month-end, Period closed. Ten phases in four stages. The cutover date is agreed in phase 4 and used at go-live in phase 9. ## In short This ERP implementation checklist splits the project into ten phases, each with a checklist and a clear "done when" test. The phases that decide success are the unglamorous ones: cleaning data before it moves, agreeing a cutover date, loading opening balances that tie to your old books, and testing full quote-to-cash and procure-to-pay flows with real documents. Finish with a supported first month-end, not a go-live party. ## Who owns the ERP implementation checklist? One named project owner owns the ERP implementation checklist, with authority to make process decisions. Each phase also needs the right people at the table. | Role | Responsibility | | --------------------------------------------------- | ------------------------------------------------------------- | | Executive sponsor (owner or MD) | Sets priorities, breaks deadlocks, protects time for the team | | Project owner | Runs the plan, chases decisions, signs off each phase | | Process owners (sales, purchasing, stores, finance) | Describe today’s process, approve the new one, test it | | Data owner | Cleans and loads data, signs off reconciliations | | Implementation lead (vendor or partner) | Configures the system, advises on design, trains trainers | If one person holds several roles in your business, that’s normal for an SME. Just make sure nobody is the only one who knows how a key process works. ## Phase 1: Scoping Scoping decides what goes live, for which companies and on what date. Most later problems trace back to a scope that was never written down. Phase 1 checklist 0 of 7 done - \[ ] Write a one-paragraph goal: what will be different 12 months after go-live. - \[ ] List the legal entities, warehouses and currencies in scope. - \[ ] Map today's flows with real document names: quotation, customer PO, sales order, delivery note, tax invoice, LPO, GRN, purchase invoice. - \[ ] Decide what is in phase one and what waits (for example, sales and stock first, then purchasing). - \[ ] List what stays outside the ERP (payroll, bank payments, an e-invoicing provider) and how data passes between them. - \[ ] Agree a target cutover date, ideally a month-end or quarter-end. - \[ ] Agree the decision process: who signs off, and how fast. Done when A signed scope document lists entities, processes, out-of-scope items and the target cutover date. ## Phase 2: Data cleanup [Data migration](https://1flux.ai/glossary/data-migration) only works if the data is clean before it moves. Cleanup belongs in the old system or spreadsheet, not in the new ERP. Phase 2 checklist 0 of 8 done - \[ ] Remove duplicate customers and suppliers. Merge their open balances first. - \[ ] Archive customers and items with no activity in the past two years, unless finance needs them. - \[ ] Standardise names, including Arabic or other-language names, and agree one spelling. - \[ ] Fill missing tax registration numbers, company registrations and addresses. - \[ ] Split structured addresses into their parts where a country requires it (a Saudi national address has a building number, street, district, postal code and additional number). - \[ ] Give every item a unique code, a unit of measure and a category. - \[ ] Fix credit terms stored as free text ("30 days from invoice") as numbers with a basis. - \[ ] Agree the owner of each data set and a deadline for each. Done when Each data set has an owner who has signed it off as clean. In 1flux The import workbench validates every row on the server before anything is saved and gives you a downloadable error file. Run a test import early to find problems while you still have time to fix them at source. ## Phase 3: Master data Master data is the reference data every transaction uses: customers, suppliers, items, the [chart of accounts](https://1flux.ai/glossary/chart-of-accounts), warehouses and tax codes. Load and check it before any opening balance. Phase 3 checklist 0 of 8 done - \[ ] Chart of accounts per company, including input and output tax accounts, [goods received not invoiced](https://1flux.ai/glossary/goods-received-not-invoiced), price variances and exchange gains and losses. - \[ ] Tax codes per country with their rates and effective dates. - \[ ] Legal entities with registrations, letterheads, bank details and signatories. - \[ ] Warehouses for each company. - \[ ] Customers with salespeople, credit days, credit basis and addresses. - \[ ] Suppliers with currency, credit days, tax numbers and contacts. - \[ ] Items in the [item master](https://1flux.ai/glossary/item-master) with codes, units, packs, categories, tax codes, barcodes and prices. - \[ ] Spot-check 20 records of each type against the source after loading. Done when Record counts match the cleaned source files, and spot checks pass. In 1flux Companies and contacts import in batches of up to 5,000 rows (10 MB) per file, from CSV, Excel or a paste. Company duplicates are matched by website domain, and you choose to skip them, report them as errors or update them. Items import in batches of up to 10,000 rows, can create missing categories and match on item code or barcode. A one-click 25-account trading chart gives you a starting point, or you can import your own chart from CSV. See [data import and migration](https://1flux.ai/platform/data-import-and-migration). ## Phase 4: Opening balances and the cutover date The [cutover date](https://1flux.ai/glossary/cutover-date) is the date your new ERP becomes the book of record. [Opening balances](https://1flux.ai/glossary/opening-balances) are the account balances, stock quantities and stock values carried over on that date. Phase 4 checklist 0 of 9 done - \[ ] Fix the cutover date and tell everyone, including customers and suppliers if documents will change. - \[ ] Produce a closing [trial balance](https://1flux.ai/glossary/trial-balance) from the old system as at the cutover date. - \[ ] Map every old account to an account in the new chart. - \[ ] Count stock in every warehouse as close to the cutover date as possible. - \[ ] Agree the unit cost for each item with finance. - \[ ] Decide how open customer invoices and supplier bills move: as individual open items, or as one balance per account. - \[ ] Load opening stock and check its value against the inventory balance in the old trial balance. - \[ ] Load the opening trial balance and check that debits equal credits. - \[ ] Get finance to sign off that opening balances tie to the old books. Done when The new system’s opening trial balance matches the old closing trial balance, and opening stock value matches the inventory account. In 1flux Set the ledger cutover date in each company’s ledger policies. The opening trial balance imports from CSV, Excel or a paste (account code, debit, credit), must balance exactly, and posts once per company on the cutover date. Opening stock goes in by form (up to 500 lines) or by import (up to 10,000 rows of item code, warehouse, quantity and unit cost). The import is all or nothing: one bad row stops it, with the row number and reason. Opening stock posts its own value against opening balance equity, so leave inventory out of the opening trial balance, or offset it, so it isn’t counted twice. Opening receivables and payables come in as control-account balances in the opening trial balance. ## Phase 5: Configuration Configuration turns your agreed processes into system settings. Change the process to fit standard features before you customise the system. Phase 5 checklist 0 of 10 done - \[ ] Document numbering per company and document type. - \[ ] Costing method per company (weighted average, FIFO or standard cost), agreed with your auditor. - \[ ] Negative stock policy: block, or allow and flag. - \[ ] Backdating rules and fiscal-year start. - \[ ] Accounting periods opened for the go-live month. - \[ ] Posting accounts mapped for every document type. - \[ ] Approval rules: quotation amount bands, requisition approvers. - \[ ] Credit-days caps and who can override them. - \[ ] Quotation and document layouts, including a second language where needed. - \[ ] Exchange rates for every foreign currency you trade in. Done when A walkthrough of each process runs without workarounds, and every setting has a named owner. In 1flux A country pack seeds the essentials when you create each company. The UAE pack adds VAT 5% input and output codes and zero-rated; the Saudi pack adds VAT 15% input and output and zero-rated; the India pack adds GST rates. Each pack also adds legal forms, regions and registration fields, such as the TRN and trade licence in the UAE, or the CR, VAT number and unified number in Saudi Arabia. Every workspace also starts with 30 units of measure, 10 conversions, quotation stages and default templates. ## Phase 6: Roles and permissions Roles decide who can see and do what. Design them around jobs, not around people, and keep the people who prepare a transaction separate from those who approve or post it. Phase 6 checklist 0 of 8 done - \[ ] List job roles: salesperson, sales manager, buyer, storekeeper, GRN approver, accountant, finance manager, admin. - \[ ] For each role, list what it must see, create, approve and post. - \[ ] Separate duties: requesting from approving, receiving from invoicing, preparing journals from posting them. - \[ ] Decide record visibility: does each salesperson see only their own customers, or everyone's? - \[ ] Limit people to the legal entities they work in. - \[ ] Hide prices from warehouse roles if they should not see them. - \[ ] Test each role by logging in as a sample user. - \[ ] Plan offboarding: who takes over a leaver's customers and tasks. Done when Each role has been tested by logging in as it, and finance has approved the segregation of duties. Read more about [role-based access control](https://1flux.ai/glossary/role-based-access-control) and how [roles and permissions work in 1flux](https://1flux.ai/platform/access-control). ## Phase 7: Testing scenarios Testing proves the configured system runs your real flows end to end, with real data and the people who will use it. Test complete flows, not single screens. Write down the expected result before each test. ### Quote-to-cash test scenarios | # | Scenario | Expected result | | --- | -------------------------------------------------------------------- | ------------------------------------------------------------------------- | | QC1 | Quotation with a document discount and tax, above the approval limit | Can’t be sent until approved; tax calculated correctly after the discount | | QC2 | Revise an approved quotation | New revision number; the earlier version is kept | | QC3 | Accepted quotation plus customer PO becomes a sales order | Lines, prices, discounts and tax carry over without retyping | | QC4 | Order for more stock than is available | Shortage is flagged before the promise is made | | QC5 | Partial delivery (8 of 10 units) | Delivery note for 8; 2 remain open; stock and cost of sales update | | QC6 | Invoice only what was delivered | Invoice for 8 units; receivable, revenue and output tax post | | QC7 | One payment settles two invoices, one in a foreign currency | Both invoices cleared; exchange difference posted | | QC8 | Customer exceeds agreed credit days | Blocked, or allowed only with override permission | ### Procure-to-pay test scenarios | # | Scenario | Expected result | | --- | ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | | PP1 | Requisition above a buyer’s authority | Waits for approval | | PP2 | Three supplier quotes compared and one awarded | Award reason recorded; purchase order created for the winner | | PP3 | Purchase order issued and printed as an LPO | Correct letterhead, supplier tax number and tax | | PP4 | Receive 40 of 50 units, 2 damaged | Reason recorded for the short and rejected quantities; order stays open for the rest | | PP5 | Goods received before the price is agreed | Stock carries a provisional cost; the value is corrected, or flagged for finance, when the price is agreed | | PP6 | Supplier invoice price differs from the order | Difference needs a reason and posts to its own account | | PP7 | One delivery note covers two purchase orders | One receipt linked to both orders | Also test month-end controls: posting into a closed month must fail, and a posted journal must be corrected by reversal, not edited. Use our [quote-to-cash guide](https://1flux.ai/guides/quote-to-cash) and [procure-to-pay guide](https://1flux.ai/guides/procure-to-pay) to adapt these scenarios to your business. Phase 7 checklist 0 of 5 done - \[ ] Write every scenario with expected results before testing starts. - \[ ] Test with real items, customers and suppliers, not "Test 1". - \[ ] Have process owners run the tests, not the implementer. - \[ ] Log every failure, fix it and re-test. - \[ ] Check the accounting result of every flow, not just the screens. Done when Every scenario passes, and each process owner has signed off in writing. ## Phase 8: Training Training should mirror jobs, not menus. A storekeeper needs to receive goods and dispatch orders well, not tour every module. Phase 8 checklist 0 of 7 done - \[ ] Build training around the test scenarios for each role. - \[ ] Train a "super user" in each team first, who then trains colleagues. - \[ ] Create one-page guides for daily tasks, with screenshots from your own configuration. - \[ ] Give people a test environment or test company to practise in. - \[ ] Train managers on approvals and on the dashboards they'll use daily. - \[ ] Schedule training close to go-live, no more than two weeks before. - \[ ] Plan training for new joiners after go-live. Done when Every user has completed their role’s scenarios at least once without help. ## Phase 9: Go-live Go-live is the controlled switch from the old system to the new one. Plan it hour by hour, and agree in advance what would make you postpone. Phase 9 checklist 0 of 9 done - \[ ] Agree go or no-go criteria: tests passed, balances signed off, users trained. - \[ ] Freeze the old system for new transactions at the cutover point. - \[ ] Run the final stock count and load opening stock. - \[ ] Load and sign off the opening trial balance. - \[ ] Enter open sales orders and purchase orders that weren't completed before cutover. - \[ ] Confirm document numbering starts where you want it. - \[ ] Switch on user access and send people their invitations. - \[ ] Staff a support desk for the first two weeks, with the implementer on call. - \[ ] Keep the old system read-only for reference. Done when The first quotations, orders, receipts and invoices have been posted in the new system and checked by finance. ## Phase 10: The first month-end The first [month-end close](https://1flux.ai/glossary/month-end-close) is the real test of an implementation. It shows whether stock, receivables and the ledger agree after a month of live transactions. Phase 10 checklist 0 of 8 done - \[ ] Post or delete every draft journal. - \[ ] Reconcile stock value to the inventory account in the ledger. - \[ ] Review goods received but not yet invoiced by suppliers. - \[ ] Reconcile customer balances to the receivables control account. - \[ ] Check input and output tax against the period's invoices. - \[ ] Compare key figures to the same month last year for sense. - \[ ] Close the period so nothing more can post into it. - \[ ] Hold a lessons-learned session and update the training guides. Done when The period is closed, the reconciliations are signed off, and finance and management trust the books. In 1flux The Accounting overview shows a six-step close checklist that ticks itself as you clear draft journals, provisional costs, goods received not invoiced and differences between stock and the ledger. Closed periods refuse every posting. ## Where do 1flux tools help? 1flux includes tools for the phases where implementations most often stall. This table summarises them. Apps are switched on for you by the 1flux team; see [implementation and onboarding](https://1flux.ai/implementation) for how the 1flux team works with you. | Phase | 1flux tool | What it does | | ------------------------- | ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Data cleanup, master data | Import workbench | Add data from CSV, Excel or a paste; map columns; validate on the server before saving; download an error file. Companies and contacts up to 5,000 rows per file; items up to 10,000 rows | | Master data | Trading chart template | One-click 25-account starting chart, including VAT, goods received not invoiced, price variances and exchange gains and losses | | Opening balances | Opening trial balance | CSV, Excel or paste; must balance exactly; posted once per company on the cutover date | | Opening balances | Opening stock | By form (up to 500 lines) or import (up to 10,000 rows), all or nothing, posted against opening balance equity | | Configuration | Country packs | Tax codes, legal forms, regions and registration fields for the UAE, Saudi Arabia and India, seeded when each company is created | | Roles and permissions | Roles, hierarchy and entity access | Custom roles built from more than 100 permissions, own-records visibility and access limited by legal entity | | First month-end | Close checklist and periods | A six-step close checklist; closed periods refuse every posting | ## What are the most common ERP implementation mistakes? - **Moving dirty data.** Duplicates and missing fields multiply once transactions reference them. - **No cutover date.** Without one, the old and new systems run in parallel indefinitely. - **Testing screens, not flows.** Each screen works; the hand-off between them doesn’t. - **Customising before standardising.** Every customisation adds cost at every upgrade. - **Training too early.** People forget what they learned a month before go-live. - **Leaving finance out of testing.** The accounting result of every flow needs checking. - **Declaring victory at go-live.** The first month-end is where problems surface. FAQ ## Questions, answered Still deciding? [Talk to sales](https://1flux.ai/contact) ### What should an ERP implementation checklist include? An ERP implementation checklist should cover ten phases: scoping, data cleanup, master data, opening balances and the cutover date, configuration, roles and permissions, testing, training, go-live and the first month-end. Each phase needs a list of tasks, a named owner and a clear test of when it's done, such as opening balances tying to the old trial balance or every test scenario being signed off by its process owner. ### What is a cutover date in an ERP implementation? A cutover date is the date your new ERP becomes the official book of record. Opening balances, stock quantities and stock values are struck as at that date and loaded into the new system, and transactions after it are entered only in the new ERP. Choose a month-end or quarter-end if you can, because the old system's closing figures are already reconciled then. ### How do you migrate opening balances into a new ERP? Produce a closing trial balance from the old system at the cutover date, map each old account to the new chart and load it as one balanced opening entry. Count stock in every warehouse, agree unit costs and load opening stock separately, making sure the inventory value isn't counted twice. Finance should then sign off that the new opening figures tie exactly to the old books. ### What should you test before ERP go-live? Test complete business flows, not single screens. For a trading business, that means quote to cash (quotation, approval, sales order, partial delivery, invoice and payment) and procure to pay (requisition, supplier quotes, purchase order, receipt with shortages, supplier invoice). Check the accounting result of each flow, test each user role by logging in as it and confirm that nothing can post into a closed month. ### How long does an ERP implementation take? It depends on scope, data quality and how quickly decisions are made. A single company with clean data and standard processes moves much faster than a group with several entities, warehouses and currencies. The phases that usually take longest are data cleanup and testing. Agree a realistic cutover date in phase one and protect your team's time to meet it. ### What happens in the first month-end after ERP go-live? The first month-end checks that the implementation works with live data. Finance clears draft journals, reconciles stock value to the ledger, reviews goods received but not yet invoiced, reconciles customer balances to the receivables control account and checks VAT before closing the period. Expect to find small configuration issues; fix them, update the training guides and close the period only when the reconciliations are signed off. Related ## Keep exploring ### [ERP buyer's guide](https://1flux.ai/guides/erp-buyers-guide-gcc) How to choose an ERP: requirements, vendor questions, demo scripts, five-year cost and a scoring table. ### [Data import and migration](https://1flux.ai/platform/data-import-and-migration) Import companies, contacts, items, opening stock and an opening trial balance, validated before anything is saved. ### [Implementation](https://1flux.ai/implementation) Seven steps from discovery to your first month-end close in 1flux. ### [Quote-to-cash guide](https://1flux.ai/guides/quote-to-cash) The eight stages from enquiry to cash in the bank, with the documents, controls, KPIs and a checklist. ### [Procure-to-pay guide](https://1flux.ai/guides/procure-to-pay) Eleven steps from requisition to supplier payment, with the documents, controls, accounting, KPIs and a checklist. ### [Roles, permissions and audit](https://1flux.ai/platform/access-control) Custom roles, record visibility along reporting lines, entity access and row-level security. Last updated 11 October 2026