ERPNext UAT checklist
ERPNext UAT Checklist: How to Test Before Going Live
A practical ERPNext UAT checklist for UK businesses covering sales, purchasing, stock, finance, VAT, MTD, permissions, reports, integrations, defects and go-live sign-off.
User Acceptance Testing, or UAT, is one of the most important stages of an ERPNext implementation. It is the stage where real business users test ERPNext before it becomes the live system. Technical testing asks whether the system works. UAT asks whether your people can run the business correctly in ERPNext.
ERPNext should not go live until real users have tested real business scenarios and signed off that the system is ready.
Before go-live, test quotation to payment, purchase to supplier payment, stock movements, opening balances, VAT/MTD route, permissions, approvals, print formats, emails, reports, integrations and exception scenarios—with business users, not only consultants.
1. What Is ERPNext UAT?
ERPNext UAT is the formal testing stage where business users confirm ERPNext supports their daily work before go-live. It usually happens after configuration, trial data migration, workflow setup and basic technical testing. Users test real scenarios: quotations, stock receipts, invoices, payments, approvals, VAT reports and permissions.
2. Why UAT Matters Before ERPNext Go-Live
- Users cannot complete basic transactions or approvals block urgent work
- Stock quantities wrong; VAT incorrect on invoices
- Print formats unacceptable; reports do not match expectations
- Opening invoices missing; warehouse users return to spreadsheets
- Finance cannot complete month-end; management loses confidence
3. UAT Is Not Just Clicking Buttons
A weak UAT session creates one simple invoice and marks UAT complete. Strong UAT tests real business scenarios, real users, real permissions, migrated data, tax rules, reports, exceptions, approvals, print formats and integrations. It should be hands-on testing by the client team—not a partner demonstration.
4. Who Should Be Involved in ERPNext UAT?
| Role | Responsibility |
|---|---|
| Business Owner | Final go-live decision |
| Finance Lead | Accounts, VAT, balances, invoices |
| Sales / Purchasing / Warehouse | Daily operational workflows |
| Accountant / VAT Adviser | VAT, MTD and finance review |
| ERPNext Partner | Configuration, fixes, support |
The people who will use ERPNext every day must be included—not only managers.
5. ERPNext UAT Preparation Checklist
System, data and UAT management
- Staging site ready with company, accounts, VAT, users, roles, workflows, print formats
- Customers, suppliers, items, warehouses and trial opening data imported
- Test scripts prepared; defect log ready; UAT dates and responsibilities assigned
6. ERPNext UAT Test Script Format
| Field | Example |
|---|---|
| Test ID | UAT-SALES-001 |
| Scenario | Create Quotation and convert to Sales Order |
| User Role | Sales User |
| Expected Result | Sales Order with correct customer, item, price and VAT |
| Status | Passed / Failed / Retest Required |
7. ERPNext UAT Pass/Fail Rules
A test passes when the user completes the full scenario with correct data, VAT, stock/accounting impact, print format, permissions and reports. A test fails when the process cannot be completed, VAT is wrong, permissions block work or a manual workaround is needed for a core process. Retest after fixes—do not mark failed scenarios as passed without retesting.
8. UAT Defect Priority Levels
| Priority | Meaning |
|---|---|
| P1: Go-live blocker | Cannot go live until fixed—wrong VAT, broken invoices, unreconciled balances |
| P2: Must fix before go-live | Serious operational risk—wrong approvals, missing addresses |
| P3: Fix soon after go-live | Non-blocker—dashboard layout, minor wording |
| P4: Future improvement | Nice-to-have automation or phase two workflow |
9. CRM and Customer UAT Checklist
Test Lead → Opportunity → Contact → Address → Quotation → Won/Lost. Confirm customer names, groups, VAT numbers, addresses, payment terms and pipeline reports. Poor customer data affects every sales and finance process.
10. Selling UAT Checklist
- Quotation: price list, discount, VAT, email and PDF
- Sales Order: from quotation, warehouse, partial delivery
- Delivery Note: stock reduction, returns
- Sales Invoice: VAT, due date, credit note, part/full payment
Selling UAT should include both normal and exception scenarios across quote-to-cash.
11. Buying and Supplier UAT Checklist
Test Material Request → Purchase Order → Purchase Receipt → Purchase Invoice → Payment Entry, plus approvals, partial receipt and supplier credit notes. Confirm supplier prices, stock increase on receipt and supplier balances. Purchasing and finance should both sign off.
12. Stock and Warehouse UAT Checklist
- Stock items, UOMs, warehouses including returns and damaged goods
- Material Receipt, Issue, Transfer, Reconciliation
- Serial and batch: receive, deliver, transfer, expiry, duplicate prevention
- Reports: Stock Balance, Ledger, Valuation, warehouse-wise and low stock
Stock UAT must include warehouse users—not only finance or consultants.
13. Accounting and Finance UAT Checklist
Test Sales/Purchase Invoice posting, Payment Entries, credit notes, part payments, Journal Entries, cost centres and finance reports: Trial Balance, P&L, Balance Sheet, aged debtors/creditors and VAT. Finance leadership and accountant should sign off.
14. UK VAT and MTD UAT Checklist
- Standard, reduced, zero-rated, exempt, reverse charge and credit note VAT
- VAT control accounts, tax template mapping and invoice VAT wording
- MTD route agreed; localisation app or bridging software tested
- Accountant reviews test results before go-live
Do not leave VAT testing until after go-live. VAT errors create serious compliance and cash flow issues.
15. Opening Data UAT Checklist
Test opening Sales Invoices against Aged Debtors, opening Purchase Invoices against Aged Creditors, opening stock by warehouse with valuation, and opening balances including Trial Balance, bank, VAT and retained earnings. Opening data should be tested in UAT—not only at final cutover.
16. Project and Timesheet UAT Checklist
Test project creation, tasks, timesheet entry, billable vs non-billable hours, approval, Sales Invoice from Timesheet and project profitability reports.
17. Manufacturing UAT Checklist
Test BOMs, workstations, Production Plan, Work Order, Job Card, material consumption, finished goods receipt, scrap and manufacturing cost reports. Manufacturing UAT should not be rushed.
18. User Roles and Permissions UAT Checklist
Test with real user accounts for sales, purchase, warehouse, finance, project and manufacturing roles—not only Administrator. Confirm users can access required documents, cannot access restricted records, and company/warehouse restrictions work correctly.
19. Workflow and Approval UAT Checklist
Test PO, Sales Order, quotation, expense, stock adjustment and discount approval workflows. For each: draft, pending, approved, rejected, resubmission and notifications. Overcomplicated workflows can slow go-live.
20. Print Format and Email UAT Checklist
Test quotation, Sales Order, Delivery Note, Sales Invoice, Purchase Order and statement formats. Confirm logo, VAT number, bank details, payment terms and reverse charge wording. Test send quotation, invoice and PO emails with PDF attachments from normal user accounts.
21. Reports and Dashboard UAT Checklist
- Finance: Trial Balance, P&L, Balance Sheet, aged debtors/creditors, VAT
- Sales/Purchase: open orders, pipeline, customer/supplier outstanding
- Stock: balance, ledger, valuation, ageing
- Management dashboards: sales, margin, stock value, cash, open orders
22. Integration UAT Checklist
Test Shopify, WooCommerce, payment gateways, bank feeds, payroll, courier, 3PL and custom APIs. Confirm data flow, duplicate prevention, error logging, retry process and manual fallback. Integration issues often appear after go-live if not tested with realistic scenarios.
23. Negative Testing and Exception Testing
- Out of stock; no credit limit; missing approval
- Partial delivery/receipt; part/over payment
- Customer return; supplier credit note; wrong warehouse
- Missing VAT template; no permission; integration or email failure
24. ERPNext UAT Defect Log Template
| Field | Description |
|---|---|
| Defect ID / Date / Raised By | Unique tracking and ownership |
| Module / Test Scenario | Selling, Buying, Stock, Accounts, etc. |
| Priority / Status | P1–P4; Open, Fixed, Retest, Closed |
| Assigned To / Retested By | Fix owner and validation |
Review defects daily during UAT. Do not let issues remain in chat messages only.
25. ERPNext UAT Sign-Off Criteria
- All P1 defects closed; P2 closed or formally accepted
- Critical workflows passed; finance and VAT reports approved
- Opening balances reconciled; permissions and print formats approved
- Integrations approved or clearly deferred; business owner accepts go-live risk
UAT sign-off should be documented—a verbal “looks fine” is not enough.
26. Department-Level UAT Checklist Summary
| Department | Key Tests |
|---|---|
| Sales | Lead, quotation, SO, delivery, invoice, returns, reports |
| Purchasing | Supplier, MR, PO, receipt, invoice, payment, reports |
| Warehouse | Items, stock entry, reconciliation, serial/batch, reports |
| Finance | Invoices, payments, VAT, opening balances, financial reports |
| Management | Dashboards, KPIs, approvals, permissions, go-live readiness |
27. Common ERPNext UAT Mistakes
- Testing only with Administrator or only simple scenarios
- Not involving real users; not testing VAT, stock exceptions or permissions
- Not recording defects; not retesting fixes
- Signing off with unresolved blockers; going live because the date arrived
28. ERPNext UAT Timeline Example
- Week 1: Preparation—scripts, users, test data, roles
- Week 2: Department testing—sales, purchase, stock, finance, projects
- Week 3: Defect fixing and retesting
- Week 4: Final sign-off—finance, VAT, management, go-live readiness meeting
Timeline depends on project size. Small implementations may complete UAT faster; complex projects may need several rounds.
29. Why Work With Talpha Solutions?
Talpha Solutions helps UK businesses prepare and run ERPNext UAT—test scripts, data validation, sales/purchase/finance workflow testing, VAT/MTD testing, permissions, reports, print formats, integration testing, defect tracking, retesting and go-live readiness review. We help real users test real scenarios before ERPNext becomes the live system.
Final Advice
Do not skip ERPNext UAT. Go live when business users have tested it, defects are fixed, reports reviewed and the organisation is ready—not only because configuration is complete. For UK businesses, UAT must include VAT, MTD planning, opening balances, stock accuracy and finance sign-off.
Call to Action
Preparing for ERPNext UAT? Book a free ERPNext UAT readiness review with Talpha Solutions. We will review your test scripts, data migration, workflows, VAT setup, user permissions, reports and go-live risks, then help you build a practical UAT plan before ERPNext becomes your live system.
FAQ
Frequentlyasked questions
Answers to common evaluation questions.
ERPNext UAT, or User Acceptance Testing, is the stage where real business users test ERPNext before go-live to confirm that workflows, data, reports, permissions and transactions work correctly for daily operations.
ERPNext UAT should be done by business users from finance, sales, purchasing, warehouse, operations, projects, manufacturing and management. It should not be done only by developers or consultants.
ERPNext UAT should test sales, purchasing, stock, finance, VAT, opening balances, reports, permissions, workflows, print formats, emails, integrations and exception scenarios.
Yes. UK businesses should test VAT templates, VAT accounts, VAT reports, invoice wording and the Making Tax Digital submission route before go-live.
UAT should use realistic migrated data where possible. Customers, suppliers, items, warehouses, opening invoices and stock should be close enough to live data for users to test properly.
No. UAT should be done using real user accounts and real roles. Testing only with Administrator hides permission problems that may appear after go-live.
A UAT defect log records issues found during testing, including defect ID, module, issue description, priority, owner, status and retest result. It helps control fixes before go-live.
ERPNext UAT is complete when critical test scenarios have passed, high-priority defects are closed or accepted, finance and operations have signed off, VAT has been reviewed and the business owner approves go-live readiness.
The biggest mistake is treating UAT as a quick demonstration instead of real business testing. UAT must test real workflows, real users, real permissions, real data and real exceptions.
Yes. Talpha Solutions can help UK and European businesses prepare ERPNext UAT scripts, run testing sessions, track defects, retest fixes and review go-live readiness.