A New Ledger Does Not Fix an Old Balance: How to Prepare Your Accounting Department for ERP

Preparing the accounting department for ERP means agreeing, before configuration, on the chart of accounts, the accounting policies, the posting rules, the controls, the opening balances, and the closing calendar, and naming an owner for each. The software then applies those decisions to every transaction. It cannot make them for you.

This guide is for finance managers, chief accountants, and business owners in Egypt and the Arab region who are preparing to move their books into an ERP system. It answers a question that matters more than “Which ERP has the best accounting module?”: Can our finance team explain every number the new system will start from, and every number it will produce?

01The short answer: what does an ERP-ready accounting department look like?

An accounting department is ready when it has decided, in writing, how the business will be recorded, not only which software will record it. Four signals show it:

1. 01A chart built for decisionsClear account types and levels, dimensions such as cost centres instead of an account for every branch, and a signed map from every old code to the new chart.
2. 02Written policies and posting rulesEach recurring event—a sale, a receipt, a goods receipt, an issue to production—has an agreed treatment and an owner.
3. 03Opening balances you can explainA fixed cutover date, a trial balance that ties to the old system, and open items that add up to every control account.
4. 04Controls inside the systemWho creates, approves, posts, reverses, and closes is designed before go-live, not policed in a spreadsheet after it.

Microsoft's guidance on defining accounting policies calls the definition of the financial structure and of organisational policies crucial steps that significantly affect the success of an implementation. It also notes that the chart of accounts, financial dimensions, and ledger settings are used in downstream processes. In plain terms: every other module inherits finance's decisions.

02Why finance has more to prepare than any other department

In an ERP, accounting is where every operational transaction ends. Deliveries, purchase receipts, stock movements, production, payroll, and payments post automatically, once someone has decided how. Before ERP, an accountant could correct a figure while re-entering it. After ERP, a rule posts the figure. A wrong rule repeats the same mistake on every transaction, quietly and quickly.

So the department's role changes. It moves from recording what others did to designing how everything others do will be recorded. That design has to be ready before the operations teams finish theirs, because their documents are what will post.

Signs that the accounting department is not ready yet

• The trial balance carries suspense, “other”, or old balances that nobody can explain.
• Customer and supplier balances in the books differ from their statements, and nobody owns the difference.
• The chart of accounts grew one account at a time, with separate accounts for branches, projects, or people.
• Accounting policies live in people's heads: when revenue is recognised, how stock is costed, when a cheque counts as collected.
• Bank reconciliations are months behind.
• Mistakes are corrected by editing or deleting entries.
• Nobody has asked the tax adviser what e-invoicing, e-receipts, and VAT require from the new system.
• Finance expects to “receive the system” after operations has designed it.

• Ask 01Which balance would we not sign today?List every account whose balance the finance manager could not defend to the auditor.
• Ask 02What must finance get from the ERP?A faster close, reliable receivables, real product cost, or tax compliance: choose the first priorities.
• Ask 03Who owns the chart and the rules?Name the person who approves a new account, a posting rule, or a change in policy.
• Ask 04When do we switch?Choose the period end that becomes the cutover date, and what must close in the old system before it.
• Ask 05How will we prove it worked?Agree which reconciliation, report, or month-end result will show that the new books are right.

03The finance team's new job: from entering transactions to owning the rules

An ERP does not remove the accountant. It moves the work upstream, into the design of rules, and downstream, into review, reconciliation, and analysis.

This shift needs time from the people who know the books best. If the chief accountant joins only for training, the rules will be designed by people who do not post the entries, and the accountant will inherit them.

04Ten steps to prepare your accounting department for ERP

1. Agree what finance needs from the ERP

Start from the duties and decisions the department carries: closing the month on time, knowing who owes what, knowing what a product really costs, filing tax correctly, and forecasting cash. Choose no more than three priorities for the first phase.

For each priority, record today's baseline from your own data: how many days the close takes, how many manual adjustments it needs, how old the oldest unreconciled bank item is. Do not borrow a benchmark from another company. If the business case is still open, start with FLAPP's ERP readiness guide for business owners.

2. Redesign the chart of accounts for decisions, then map the old one

Do not copy the old chart account by account, and do not redesign it in isolation. Design it for the statements, tax returns, and management reports you need, then connect every old code to it.

• Give every account a type (asset, liability, equity, revenue, or expense) and a level. Post only to the lowest level.
• Build reports on account types and groups, never on what a code “starts with”. A new chart can give a familiar first digit a different meaning.
• Use dimensions such as cost centres, branches, and projects for analysis instead of opening an account for each one. Microsoft's chart-of-accounts guidance describes these segments as financial dimensions, such as department and cost centre.
• Let control accounts—receivables, payables, and inventory—be fed only by their documents. Block manual journals on them.
• Write a mapping table: every old code, the new account it moves to, the reason, and the approver.

3. Write the accounting policies before configuration

An ERP applies a policy to every transaction without asking. List the decisions it will apply, and settle each one explicitly:

Some options are limited by the accounting standards that apply to you. For example, IAS 2 Inventories assigns cost by specific identification for items that are not ordinarily interchangeable, and by the first-in, first-out or weighted average formula for items that are. Confirm each choice with your auditor under the Egyptian Accounting Standards or IFRS, whichever apply to you.

Keep the decisions in a policy register: the decision, the reason, the effective date, the owner, and the approver. When a dispute appears months later, the register settles it, not the memory of whoever configured the system.

4. Turn every recurring event into a posting rule

Build a posting map with one row per event: the document that triggers it, the debit, the credit, who triggers it, and who reviews it. Cover sales deliveries and invoices, receipts, cheque movements, goods receipts, supplier invoices, payments, returns, issues to production, finished-goods receipts, stock-count adjustments, payroll, depreciation, bank charges, and custody settlements.

This table is an illustration; your policy register decides the exact accounts. Point automatic postings at named default accounts such as “receivables”, “output VAT”, and “cost of sales” rather than codes written into the software. Moving an account later then becomes a settings change, not a development project.

Then test each rule with a real transaction from last month and compare the entry with what the accountant would have posted by hand. Any difference is either a wrong rule or an old habit. Decide which before go-live.

5. Clean the sub-ledgers before you move the balances

A ledger balance is only as reliable as the detail behind it. Before cutover, reconcile each sub-ledger and name an owner for every difference:

• Customers: statements agreed, duplicates merged, tax registration numbers checked, every open invoice and advance identified.
• Suppliers: statements agreed, with open invoices, debit notes, and advances listed.
• Banks: every account reconciled to the cutover date, with uncleared cheques and transfers listed.
• Cheques: in hand, under collection, and issued but not cleared, in one list for each bank.
• Inventory: a count close to the cutover date, valued under the agreed policy.
• Fixed assets: a register with cost, accumulated depreciation, location, and custodian that agrees with the ledger.
• Staff advances and custody: each holder's balance confirmed in writing.

For the method, from data dictionaries to duplicates and owner sign-off, use FLAPP's complete ERP master data preparation manual.

6. Choose the cutover date and the opening-balance method

• Choose a period end, such as the start of a month, a quarter, or the fiscal year, and avoid peak trading days and tax filing dates.
• Close the old books for the period before cutover. Keep the old system read-only for history and audit.
• Migrate balances and open items, not every historical entry. Microsoft's data migration guidance separates master data from open transactions such as open sales and purchase orders, stock on hand, and open balances.
• Load everything through an opening-balance clearing account. Each load—the trial balance, customers, suppliers, stock, and assets—posts against it, and it must end at zero.
• Agree the freeze window: which documents post in the old system, which wait, and who enters what after go-live.

Before anyone signs, the opening position must pass six checks:

1. 01Trial balanceThe opening trial balance equals the old system's closing trial balance, account by account, through the mapping table.
2. 02Customers and suppliersOpen items for each party add up to the receivables and payables control accounts.
3. 03InventoryQuantities at the agreed cost add up to the inventory accounts.
4. 04Fixed assetsThe register's cost and accumulated depreciation equal the ledger.
5. 05Banks and chequesEach bank balance equals the statement, adjusted for listed items.
6. 06Clearing accountThe opening-balance clearing account is zero after the last load.

7. Build controls and approvals into the system

Design the controls with the accounts, not after them. The COSO Internal Control—Integrated Framework, first issued in 1992 and refreshed in 2013, is a widely used reference for this work.

• Segregation of duties: whoever creates a supplier should not approve its payments; whoever posts a manual journal should not approve it; whoever handles cash should not reconcile the bank.
• Approval limits by amount and document type, with a named substitute for absences.
• Final posted entries: a mistake is corrected by a reversing entry with a reason, never by editing or deleting.
• Locked periods: a closed period refuses new entries; reopening it needs approval and leaves a record.
• Personal access: no shared accounts, and a regular review of who can do what.

8. Prepare tax and e-invoicing before go-live

In Egypt, the eInvoicing and eReceipt system of the Egyptian Tax Authority is where taxpayers register the documents they issue, and its SDK documents the APIs that ERP and point-of-sale systems use to connect to it. Treat it as part of the finance design, not an add-on:

• Confirm your obligations with your tax adviser: e-invoices, e-receipts, VAT, and withholding where it applies.
• Collect and verify the tax registration numbers of customers and suppliers.
• Give every item the code the system requires, and name who maintains those codes.
• Decide who holds the electronic signing certificate and when it must be renewed.
• Test submission end to end in the authority's pre-production environment, including a credit note and a rejected document.
• Agree how the cutover period is filed: what the old system reports and where the new system starts.

9. Design the close calendar and the day-one reports

Write the month-end close as a calendar with an owner for each task:

• Cut-offClose sales, purchases, and stockEvery document for the month is posted, or knowingly carried to the next month.
• ReconcileBanks, cheques, customers, suppliers, stockEach control account agrees with its detail.
• AdjustAccruals, prepayments, depreciation, revaluationAdjustments are posted with support and approval.
• ReviewThe trial balance and key ratiosUnusual balances are explained before reports leave finance.
• Report and lockStatements, tax, and the management packThe period is locked; later corrections go into the next open period.

Then define the reports finance must have on day one: trial balance, income statement, balance sheet, receivables and payables aging, cash position, VAT, and inventory valuation. Give each figure one definition, such as what counts as “collected”, “overdue”, or “net sales”, and keep that definition in one place. When the same figure means different things on two screens, people stop trusting both.

10. Rehearse the close before go-live

A demo shows a screen. A rehearsal shows whether the books close. Run at least one full mock month-end in a test environment with migrated data: post a month of real transactions, reconcile, adjust, and produce the statements and the VAT report. Microsoft's implementation guidance also describes a mock cutover: a test that simulates the deployment process in the production environment.

Running every transaction in both systems for months is expensive and tiring. A targeted parallel run is usually more practical: compare one month's VAT, receivables aging, and inventory value from both systems, and explain every difference.

Train accountants by scenario, not by screen: receive, invoice, collect, reverse, reconcile, and close, including how to recover from a mistake. For the people side of the change, see FLAPP's ERP employee adoption guide.

05The accounting department's 24-point ERP readiness scorecard

This is a practical FLAPP diagnostic, not a published industry benchmark. Score each statement zero if it has not started, one if it is partial, and two if it is documented and agreed.

1. Finance has up to three agreed priorities for the ERP, each with a baseline.
• The new chart of accounts is approved, with types, levels, and dimensions.
• Every old account code is mapped to a new account, and the map is signed.
• The accounting policy register is written and approved.
• Every recurring event has a posting rule tested with a real transaction.
• Customer and supplier balances agree with their statements.
• Bank accounts and cheques are reconciled to a recent date.
• Inventory and fixed-asset values agree with the ledger.
• The cutover date and the opening-balance method are agreed.
• Segregation of duties and approval limits are documented.
• E-invoicing, e-receipt, and VAT requirements are confirmed and tested.
• A mock month-end close has been completed with migrated data.

Use the score to find gaps, not to look ready. Its value is in showing which balances, rules, and decisions nobody owns yet.

06A 30-day finance preparation plan

A small or mid-sized company can run this plan at its own pace. Thirty days is a working frame, not a promise that every finance team will be ready in the same time.

• Week 1Priorities, owners, and the chartAgree finance priorities and baselines, name owners, review the current chart, and list the balances nobody can explain.
• Week 2Policies and posting rulesWrite the policy register, draft the posting map, and test the main rules on last month's transactions.
• Week 3Sub-ledgers and controlsReconcile customers, suppliers, banks, cheques, inventory, and assets; design approvals and segregation of duties.
• Week 4Cutover and rehearsal planFix the cutover date and the opening-balance method, confirm tax requirements, write the close calendar, and schedule the mock close.

Deliverables that should exist at the end

• An approved chart of accounts and a signed old-to-new mapping table.
• An accounting policy register.
• A posting map, tested with real transactions.
• Reconciled lists of customers, suppliers, banks, cheques, inventory, and assets.
• A cutover plan with the opening-balance method and its six checks.
• A matrix of roles, approvals, and access.
• A tax and e-invoicing checklist with a test plan.
• A close calendar and the definitions of the day-one reports.

07The go-live decision: when should the finance manager say “not yet”?

A short, controlled delay can cost less than months of correcting the books. Do not go live only because the date was announced.

Say “not yet” when the opening trial balance does not tie to the old system, the clearing account is not zero, a sub-ledger does not agree with its control account, a critical posting rule is untested, e-invoice submission fails in testing, or nobody has closed a month in the test environment.

Go-live can proceed when the opening position passes its six checks, the critical posting rules have passed with real transactions, approvals and access have been reviewed, tax submission works in testing, and the accounts team has completed a mock close.

After go-live, check every day for the first weeks: documents waiting to post, balances left in clearing or suspense accounts, manual entries on control accounts, and rejected tax submissions. Close the first month together with the implementation team. Keep the old system read-only at least until the first audit after go-live, and for as long as your record-retention duties require.

08Common accounting mistakes before ERP go-live

Copying the old chart of accounts as it is

The old chart carries every past workaround, and copying it moves those workarounds into the new system. Redesign it for the reports you need, then map.

Leaving accounting policies to the implementer

The implementer can explain the options and their effects. The finance manager decides, and owns the result in front of the auditor and the tax authority.

Opening an account where a dimension belongs

An account for every branch, project, or salesperson multiplies the chart and breaks comparisons. Use dimensions for analysis and keep accounts for accounting meaning.

Correcting mistakes by editing posted entries

An edited entry erases the evidence of what happened. A reversing entry with a reason keeps the trail that auditors and managers rely on.

Joining the project after operations has designed the flows

Sales, purchasing, and inventory documents are what will post. If finance is not in the room when those flows are designed, the posting rules have to fit decisions finance never saw.

09Frequently asked questions about preparing accounting for ERP

What does it mean to prepare the accounting department for ERP?

It means settling the chart of accounts, the accounting policies, the posting rules, the controls, the opening balances, and the closing calendar before configuration, with an owner for each, so the ERP posts what the finance team would have posted by hand.

Should we change our chart of accounts when we move to an ERP?

It is usually the right moment to review it, but not to break it without a map. Redesign it for the statements and reports you need, then map every old code to the new structure so balances and comparatives move with a clear trail.

When is the best date to move the books to a new ERP?

At a period end you can close cleanly, often the start of a month, a quarter, or the fiscal year, away from peak trading and tax filing days. The start of the fiscal year is the simplest, because after the year-end close only balance-sheet accounts carry balances. A mid-year cutover also has to bring the year-to-date income and expense balances, so the year's statements are complete.

Do we need to migrate all past journal entries?

No. Migrate the balances at the cutover date and the open items behind them: unpaid invoices, advances, cheques, stock, and assets. Keep the old system read-only for detail, and bring summarised balances where you need comparatives.

What is an opening-balance clearing account?

It is a temporary account that every opening load posts against: the trial balance, customers, suppliers, stock, and assets. When everything is loaded correctly, it returns to zero. Any balance left on it points to a difference that must be explained before go-live.

Do we need to run the old and new systems in parallel?

A full parallel run of every transaction is costly and tiring. A rehearsed mock close plus a targeted comparison, such as one month's VAT, aging, and inventory value from both systems, usually gives better evidence for less effort.

Who should own the chart of accounts and the posting rules?

The finance manager, together with the chief accountant. The implementation team configures them; finance approves every account, rule, and change, and keeps the policy register.

Will the ERP replace our accountants?

No. It removes re-entry and manual posting, and moves the work to designing rules, reviewing exceptions, reconciling, and explaining the numbers. That work needs accountants more than before.

10How FLAPP helps finance teams prepare for ERP

The FLAPP team can work with the finance manager and the accounts team before configuration, starting from your current books, not from a generic demo.

Depending on your size and scope, the sessions can cover:

• A review of the current chart of accounts and a mapping table from old codes to the new structure.
• A policy register for revenue, purchasing, inventory, cheques, currencies, and fixed assets.
• A posting map tested with your own transactions.
• A cutover plan with the opening-balance method and its reconciliation checks.
• A matrix of roles, approvals, and access.
• A close calendar and the definitions of your day-one reports.

Then we configure FLAPP's accounting module around those decisions, not the other way round. The module covers the chart of accounts and journals; automatic entries from sales, purchasing, and production; receivables, payables, instalments, and cheques; treasury and custody; fixed assets and depreciation; currencies and exchange rates; financial statements; the cash-flow forecast; and period close.

We will not promise a close in a fixed number of days, and we will not load a balance that nobody can explain. The aim is a finance team that knows what the system will post before the first entry is posted.

Book a finance readiness session with FLAPP

11Authoritative references

• Overview of the Define accounting policies business process area — Microsoft
• Plan your chart of accounts — Microsoft
• Manage configuration and migration data for Dynamics 365 projects — Microsoft
• Types of tests that implementation projects use — Microsoft
• IAS 2 Inventories — IFRS Foundation
• Internal Control—Integrated Framework — COSO
• Egyptian eInvoicing and eReceipt SDK — Egyptian Tax Authority