In custom software development, there is a critical difference between developer testing and User Acceptance Testing (UAT). Developers test whether the code runs without crashing when clean sample data is entered; UAT tests whether the software actually handles the messy reality of your daily Singapore business operations—partial deliveries, last-minute credit notes, fat-finger mobile typos, and strict staff permission boundaries.
Once your software vendor delivers a staging build based on your custom software requirements, run these eight UAT checks with your real front-line staff before approving live cutover.
1. End-to-end “Happy Path” workflow testing by actual front-line users (not just directors)
Why it matters: Managing directors often approve a staging demo because the summary dashboard looks clean, only for warehouse packers or clinic receptionists to discover on Day 1 that printing a label now takes nine clicks instead of two.
How to run the check: Have the actual staff members who perform the job daily execute 10 complete real-world transactions from quotation/order creation through fulfilment and invoicing without developer coaching.
2. Role-boundary and permission-leak testing
Why it matters: A common software vulnerability occurs when hiding a menu button in the UI fails to restrict the underlying URL or export endpoint—allowing a junior account to view cost margins, payroll figures, or full customer lists in breach of internal controls and PDPA Protection obligations.
How to run the check: Log in with a test account for each restricted role (e.g., Field Staff, Sales Coordinator, External Client) and attempt to view, edit, delete, or export records belonging to another branch or higher permission tier.
3. “Dirty data,” duplicate clicks and invalid input stress testing
Why it matters: Real users paste phone numbers with spaces, enter negative quantities by mistake, upload 18MB smartphone photos, or double-tap the “Confirm Order” button when office Wi-Fi lags.
How to run the check: Deliberately test blank mandatory fields, special characters (&, ', Chinese/bilingual characters where applicable), negative numbers, and rapid double-clicks on submit buttons to verify that the app prevents duplicate records and shows clear error messages.
4. Real-world exception workflows: cancellations, partial deliveries, exchanges and credit notes
Why it matters: Almost every software project works smoothly when a customer orders 10 units, receives 10 units, and pays in full. Systems break when a customer orders 10 units, 7 are delivered today, 3 are backordered, and 1 arrives damaged requiring a partial credit note.
How to run the check: Write out your top 5 monthly operational exceptions—voided invoices, split shipments, mid-month leave cancellations, or price overrides—and verify the system handles them without corrupting stock or ledger totals.
5. Financial, tax and inventory math reconciliation against historical batches
Why it matters: Subtle floating-point rounding discrepancies (such as calculating 9% GST per line item vs on the invoice subtotal, or rounding unit discounts to two decimal places) can cause cent-level mismatches that block accounting reconciliation.
How to run the check: Take 5 real historical invoices and stock movements from last month, enter the exact same inputs into staging, and verify that line totals, tax amounts, and closing stock balances match your accounting records (such as SumBook) to the exact cent.
6. Third-party API, payment webhook and notification failure handling
Why it matters: What happens if a customer pays via PayNow QR or an automated email triggers while an external API is temporarily slow? If the application fails silently without logging the event or retrying, orders go missing.
How to run the check: Verify that email, WhatsApp, payment, and accounting sync actions log their status clearly and display an admin retry button if an external service times out.
7. On-site device, scanner and network testing in the real workspace
Why it matters: A web application tested on a fast fibre connection in an office conference room may behave very differently on a rugged Android tablet or barcode scanner at the back of a Tuas warehouse or a busy retail counter.
How to run the check: Test the staging application on the exact tablets, smartphones, receipt/label printers, and mobile data connections your staff use on the floor.
8. Cutover rehearsal, legacy data freeze window and rollback plan
Why it matters: Switching from legacy spreadsheets or old software to a new system on a busy Monday morning without a rehearsed cutover sequence leads to staff entering data into two systems at once.
How to run the check: Agree on a specific off-peak cutover window (for example, Saturday afternoon), verify the final master data import from your legacy spreadsheets, and confirm a clean rollback snapshot exists before going live.
Custom Software UAT Scenario Sign-Off Matrix
Use this UAT sign-off table to track testing progress before authorising production deployment:
| UAT Test Category | Specific Business Scenario to Execute | Tester Role | Pass Criteria for Go-Live |
|---|---|---|---|
| 1. Happy Path Flow | Complete 10 standard end-to-end orders/jobs without assistance | Front-Line Operations Staff | Zero blocker bugs; task completion time meets daily workflow needs |
| 2. Permission Boundaries | Attempt to view/export restricted margin, payroll or branch data | Project Sponsor / DPO | Unauthorized URLs, buttons, and exports strictly blocked & logged |
| 3. Exception Handling | Process partial delivery, order cancellation, refund & credit note | Operations & Finance Lead | Inventory counts and invoice balances adjust accurately without manual hacks |
| 4. Math & GST Parity | Re-run 5 complex historical invoices with discounts & tax | Finance Officer | Subtotal, discount, and tax rounding match accounting ledger to S$0.01 |
| 5. Field Device & Cutover | Test on warehouse/outlet tablets + verify final data import | IT / Engineering Lead | Fast mobile response + verified backup & rollback snapshot |
Build and launch custom business software with structured engineering QA
At W Creates Digital, our software and cloud engineering team guides Singapore SMEs through requirements scoping, milestone staging, and structured User Acceptance Testing—whether deploying our modular SaaS tools (SumBook, PeopleBook, StockBook) or bespoke web and mobile applications. Contact our engineering team to discuss your software project.