Wisoft Logo
Odoo Ready Partners Logo
Phone number

How to Test an ERP Before Go-Live: A User Acceptance Testing Checklist

Reading Time: 8 min

Written by Githin AntonyUpdated on Oct 29, 2026
GoogleShare this article
Blog Banner

Your implementation partner says the system is ready. Modules are configured, data is loaded and the go-live date is set. One question remains, and only your business can answer it: can your people actually run the company on this system?

That is what user acceptance testing (UAT) is for. The people who will use the ERP every day work through real processes with real data and confirm the system supports how the business operates. When UAT is rushed, problems surface after go-live, when invoices go out wrong or stock counts don't match.

This checklist covers preparation, what to test, defects and the go-live decision.

What UAT Should Prove

The International Software Testing Qualifications Board (ISTQB) defines UAT as acceptance testing done by future users in a simulated or real operational environment, focused on their needs. In practice, UAT tests business processes, not individual features.

"Can we create an invoice?" is a feature check. "Can we turn a CRM opportunity into a quotation, deliver half the order, invoice it and record a partial payment?" is a UAT scenario.

UAT is the last stage of the ERP testing process before go-live, and it depends on earlier stages being finished:

Test stage Question it answers Usually led by
System integration testing Does the ERP exchange data correctly with your CRM, online store, payment gateway and other systems? Implementation team and IT
Performance testing Does it stay responsive at peak volumes, such as month-end invoicing? Implementation team and IT
User acceptance testing Can real users complete real processes from start to finish? Business users and process owners
Regression testing (throughout) Does everything that worked before still work after a fix? Implementation team and key users

Microsoft's Dynamics 365 implementation guidance recommends finishing integration testing before UAT and running performance testing alongside it. The same logic applies to most ERP projects: unstable integrations leave business users reporting technical faults instead of validating processes.

Set Up UAT Properly

Many UAT problems are created before testing starts. Put these in place first:

  • Agree the scope. List every process going live, by department. Anything not on the list isn't being accepted.
  • Name a process owner for each area. Sales, finance, procurement and operations each need one person accountable for testing and sign-off.
  • Pick testers who do the work. The accountant who posts vendor bills is more likely to spot problems than a manager.
  • Train them first, so they test the process rather than learn the screens.
  • Test in a production-like environment. Match the live system's configuration, customisations and integrations.
  • Use migrated data. Real customers, products, opening balances and open orders expose the duplicates and missing tax numbers that demo data hides.
  • Give testers their real roles, not administrator access. Approval limits and permission gaps are most reliably found this way.
  • Write scenarios with expected results. Record steps, data, expected and actual outcomes, and pass or fail.
  • Define defect severity up front. Then nobody argues later about what counts as "critical".

The UAT Checklist: What to Test

Organise testing around how work moves through the business. In every area, test the normal flow and the exceptions, such as partial payments, rejected approvals, returns and cancellations, which are easy to skip and costly to discover live.

Sales and CRM

  • Opportunity to quotation to sales order, with correct pricing and discounts
  • Credit limits blocking or flagging orders as intended
  • Order amendments and cancellations after confirmation
  • Customer history visible on the customer record
  • If you use a separate CRM: records reach the ERP once, with the right fields mapped, and updates don't create duplicates

Procurement and Inventory

  • Purchase request to purchase order, including approval and rejection
  • Full and partial receipts, and supplier returns
  • Vendor bills matched to orders and receipts
  • Stock transfers, counts, adjustments and reordering rules

Finance

  • Invoices and credit notes with correct VAT on standard, zero-rated and exempt lines
  • Payments, partial payments and overpayments
  • Bank reconciliation
  • Foreign-currency transactions and exchange differences, if you trade outside AED
  • A full period-end close, including the trial balance, receivables ageing and the VAT report for your tax period
  • Customer-facing documents (quotations, invoices, delivery notes, statements) with correct layout, tax details and numbering, in both languages if you issue them in Arabic and English

Data and Access

  • Migrated balances and open transactions reconciled to the legacy system
  • Tax registration numbers (TRNs) present and correct for VAT-registered customers and suppliers
  • Each role can do its job and nothing more, with approval limits enforced
  • Reports showing the right figures to the right people

Integrations, Including Failures

Confirm data flows correctly, then test what happens when it doesn't:

  • The CRM or online store is unavailable when an order comes in
  • A payment gateway times out mid-transaction
  • The same customer arrives from two different systems
  • A record arrives with mandatory fields missing

Each case should end with a clear error, a recoverable state and a named person who knows about it, not silent data loss.

Include UAE VAT and E-Invoicing

Microsoft's guidance includes country-specific regulatory requirements as part of UAT. For in-scope UAE businesses, that increasingly includes e-invoicing as well as VAT.

The UAE Ministry of Finance defines an e-invoice as structured invoice data exchanged electronically and reported to the Federal Tax Authority (FTA). PDFs, scans and emailed invoices don't qualify. Invoices pass through an Accredited Service Provider (ASP), which validates them and returns status messages. That means an invoice can be rejected, so rejection has to be tested.

As of October 2026, the timeline is:

  • Annual revenue of AED 50 million or more: appoint an ASP by 30 October 2026 and implement e-invoicing by 1 January 2027.
  • Other in-scope businesses: appoint an ASP by 31 March 2027 and implement e-invoicing by 1 July 2027.

Businesses dealing only in B2C transactions are currently outside the mandate. Check your category and the latest dates on the Ministry's e-invoicing portal, as the programme is still evolving.

Where e-invoicing is in scope, test that:

  • Invoices and credit notes carry all mandatory fields
  • TRNs pull correctly from master data where applicable
  • Invoices reach your ASP and the status returns to the ERP
  • Rejected invoices are visible, explained and correctable
  • Past invoices stay retrievable for audit

In Odoo, how this works depends on your version, configuration and ASP connector. Test the exact setup you'll go live with.

Manage Defects in One Place

Log every issue with its severity, owner, target date and status. After a fix, the original tester retests it and related processes get a quick regression check.

Keep defects separate from change requests. A defect means the system doesn't do what was agreed. A change request is something users would now like. Mixing them can delay go-live over wishes rather than faults.

If a serious defect appears close to go-live, you have four options:

  1. Fix and retest, if there's time to retest properly.
  2. Use a workaround, documented and trained, with the project sponsor formally accepting the residual risk.
  3. Defer the affected process to a later phase.
  4. Move the date.

Decide against your exit criteria, not deadline pressure.

Decide on Evidence: Exit Criteria and Sign-Off

Agree exit criteria before UAT begins. Without them, the go/no-go meeting becomes a debate. Here is an example set to adapt:

  • All critical scenarios passed
  • No open critical or high-severity defects, unless the sponsor has accepted a documented workaround
  • Every open medium defect has a workaround and an owner
  • Migrated balances reconcile to the legacy system
  • Each process owner has signed off in writing

Bring test results, the defect log, reconciliation reports and signed acceptances to the meeting.

Passing UAT doesn't settle the decision on its own. Your ERP implementation checklist should also confirm:

  • Cutover plan: final data load, sequence, owners and verification steps, rehearsed through dry runs
  • Rollback plan: what happens if cutover fails
  • Training: for all users, not just testers
  • Support: who users contact, and how issues are logged and prioritised
  • Hypercare: closer monitoring and faster response in the first weeks after launch

The Sign-Off Belongs to Your Business

If you work with a partner providing ERP solutions and services, agree early who owns the groundwork: the test environment, migration dry runs, integration testing before users start, and support through hypercare.

Acceptance, though, has to come from the people who run the processes every day. If they can't sign it off, the system isn't ready.

FAQs

What is user acceptance testing in an ERP project?

UAT is the final check before go-live, where the people who will use the ERP run real business processes with migrated data. It follows integration testing and ends with formal sign-off from the business.

What should an ERP UAT checklist include?

End-to-end processes for each department (sales and CRM, procurement and inventory, finance), migrated data and balances, user roles and approvals, integrations including failure scenarios, period-end reporting and, for in-scope UAE businesses, VAT and e-invoicing. Test both the normal flow and the exceptions in every area.

Who should sign off ERP user acceptance testing?

Each process owner signs off their own area, and the project sponsor makes the final go/no-go decision. The implementation partner supplies evidence and fixes defects, but acceptance should come from the business.

How long should UAT take?

It depends on scope and how many fix-and-retest cycles you need. Plan for at least two cycles: one to find issues and one to confirm the fixes.

Do UAE businesses need to test e-invoicing during UAT?

If e-invoicing applies to your business, yes. Test mandatory fields, transmission to your ASP, and how status messages and rejections return to the ERP. Confirm your phase with the Ministry of Finance.