Accounting Software Setup and Migration

The setup is the reporting

Businesses tend to choose accounting software on price and interface, then have it configured by whoever installed it, using defaults. The result is a system that records transactions accurately and cannot answer a single question the owner actually has.

Can we see margin by product line? Not unless the chart of accounts and item structure support it. Can we compare branches? Not unless a dimension was set up for it. Can we produce a VAT return without manual adjustment? Not unless the tax codes were configured for the supply types this business actually makes.

None of these are software limitations. They are setup decisions, and they are considerably cheaper to make at the start than to retrofit across two years of history.

Which businesses this applies to

New businesses setting up for the first time, where getting it right is cheap. Businesses whose reporting cannot answer the questions they need it to. Businesses migrating between systems, usually because they have outgrown the current one.

And businesses whose current package cannot support e-invoicing — a population that is larger than most of them realise, and that has a defined deadline to work against for the first time.

The work, step by step

What this looks like in practice:

1. Establish what the reporting has to produce. Segments, dimensions, KPIs, statutory output. Everything else follows from this and it is the step most often skipped.
2. Select or confirm the system. Where the current one is adequate we say so — we do not sell software and have no reason to move you.
3. Design the chart of accounts around the business rather than around the template.
4. Configure tax codes for the supply types you actually make, including zero-rated, exempt and reverse charge, so returns come out of the system rather than being assembled beside it.
5. Set up dimensions — branch, project, product, cost centre — with rules for applying them consistently at the point of entry.
6. Configure documents, including a compliant tax invoice template.
7. Connect the integrations: bank feeds, point of sale, e-commerce platform, payroll.
8. Migrate opening balances and reconcile them, which is where migrations most often go wrong.
9. Train the people who use it daily, because a configuration nobody follows degrades within a quarter.

Choosing a system, honestly

We are not a reseller and take no commission, so the following is what we actually think:

• Zoho Books — the most common SME choice in this market, well localised, reasonable for most businesses under AED 20 million
• QuickBooks Online and Xero — strong for service businesses where reporting matters more than inventory
• Tally — still widespread in trading businesses and perfectly workable, though the e-invoicing transition needs planning earlier here than elsewhere
• Odoo — capable and flexible, but implementation-dependent; a good Odoo build is excellent and a poor one is worse than nothing
• Sage, Dynamics 365 Business Central, SAP Business One — where manufacturing, multi-entity consolidation or genuine scale justify the cost

The honest general answer is that the software is rarely the constraint. A business that has genuinely outgrown its system usually knows. A business hoping new software will fix a process problem generally ends up with the same problem in a more expensive place.

Migration is where projects fail

The configuration is the interesting part; the migration is the part that goes wrong. Opening balances that do not reconcile, historic transactions imported without their tax treatment, subledgers that do not agree to the control accounts, and a cut-over date chosen for convenience rather than for a clean period end.

We migrate at a period end, reconcile the opening position before anything is posted in the new system, and run a parallel check on the first month rather than assuming. That adds a couple of weeks and removes the class of problem that otherwise surfaces at the following year end, when reconstructing what happened during the migration is considerably harder.

Common mistakes

The expensive mistakes in this area are consistent:

• Accepting the default chart of accounts, and discovering two years later that the reporting cannot answer anything.
• Tax codes configured generically, so every return needs manual adjustment beside the system.
• No dimensions, so segment analysis is impossible without recoding history.
• Migrating mid-period, leaving a split year that complicates every comparison that follows.
• Opening balances imported without reconciliation, which carries every existing error into the new system and adds a few.
• No training, so the configuration degrades within a quarter as users work around it.
• Choosing a system without checking its e-invoicing route, which is now a live question rather than a future one.

Timing and deadlines

At setup for a new business, or at a period end for a migration — ideally a year end, so comparatives stay clean.

For e-invoicing, work backwards from your band’s go-live: 1 July 2027 for businesses with Revenue under AED 50 million, and 1 January 2027 for Revenue AED 50 million or more. A system migration ahead of that needs a couple of quarters, and it should complete before the data preparation work rather than alongside it.

What you get

• A configured system with a chart of accounts designed around your reporting
• Tax codes covering every supply type you actually make
• Reporting dimensions with rules for consistent application
• Compliant tax invoice template
• Integrations connected and tested
• Opening balances migrated and reconciled
• Training for daily users, and a short written procedure

Documents we will ask for

What we ask for up front:

• Current accounting system access and a recent backup or export
• Current chart of accounts
• Last reconciled trial balance
• Details of how the business is organised for reporting purposes
• The supply types you make, for tax code configuration
• Details of systems to integrate: bank, point of sale, e-commerce, payroll
• Names of the people who will use it daily

Fees

Fixed fee for the setup, scoped on the number of entities, dimensions and integrations. Migration is quoted separately from configuration, because the effort depends on the state of the data being migrated rather than on the design.

Software licence costs are paid by you directly to the vendor. We take no commission and hold no reseller arrangement, which is the only basis on which advice about which system to use is worth anything.

Related

Frequently Asked Questions

Last reviewed 27 July 2026. Rates, thresholds and deadlines change — the e-invoicing provider deadline has already moved once. Confirm current requirements with the Federal Tax Authority before acting, or ask us to check your position.