If the demonstration ends when the purchase order appears on screen, you have not yet seen whether the process works. Procurement, finance and the people who receive goods need to see the same transaction move through their part of the work, including what happens when delivery does not match the order.
User acceptance testing (UAT) is the business team’s check that a configured solution supports agreed work before it is accepted for operation. A vendor demonstration is an evaluation, not formal UAT: it can show proposed behaviour, but it does not prove your configured environment is ready for go-live. Microsoft’s Dynamics 365 guidance likewise treats UAT as a planned test cycle with named roles, outcomes and sign-off. The example below is illustrative; it does not describe a Chwezi client or prescribe approval limits.
Set up one purchase and name the people who will test it
Choose an ordinary purchase that crosses procurement, finance and receiving. For example, an East African organisation needs office equipment from an approved supplier. Use a redacted record or test data. Before the session, fill in the values and controls your own organisation actually uses.
Name four participants by role:
- Requester: raises the purchase request and explains the business need.
- Authorised approver: decides under the organisation’s current delegation and budget controls.
- Receiving clerk: records what arrived and flags a mismatch.
- Finance reviewer: checks the supplier evidence and the resulting report or accounting view.
Give each person the access they would have in the intended operating arrangement. A presenter clicking through all four screens under one administrator login cannot show whether handovers or permissions work for staff.

Illustrative photograph. Give the person reviewing the work a clear task and the records needed to complete it.
Write the expected path before anyone opens the system
Use a script with one row per action. Replace the example labels with your policy, chart of accounts, currency, tax treatment and approval route. Do not create an arbitrary monetary threshold just to make a demo look complete. Keep one row for each distinct actor and action; the owner is accountable for deciding the expected result and closing any failed step.
| Actor | Starting record | Action | Expected result | Exception to test | Evidence to retain | Pass / fail | Owner |
|---|---|---|---|---|---|---|---|
| Requester | Approved supplier list and no open request | Submit the item, quantity and purpose | Request is saved with a reference and required details | Required detail is missing | Request reference; validation message | Process owner | |
| Authorised approver | Submitted request and actual delegation rules | Approve or reject the request | Decision, user and time are recorded; a rejection has a reason | User without authority attempts approval | Approval history; rejection record | Procurement lead | |
| Procurement officer | Approved request | Create the supplier order | Supplier, item, quantity, price and terms match the approved request | A value or supplier differs from the approved record | Request and order references | Procurement lead | |
| Receiving clerk | Open order and delivery note | Record the delivered quantity | Receipt is linked to the correct order line and document | Only part of the order arrives | Receipt reference; delivery note | Receiving lead | |
| Receiving clerk | Order for 12 units; delivery of 9 in this illustrative test | Record the partial delivery and discrepancy | Received and outstanding quantities are visible; the exception has an owner | Three units are missing | Receipt and order history; exception record | Receiving lead | |
| Authorised exception owner | Open discrepancy and organisation’s written rule | Accept, correct, return, keep open or escalate as policy allows | Action follows policy, states its reason and preserves required history | Proposed correction is outside the user’s authority | Before/after record; reason; actor and time | Named control owner | |
| Finance reviewer | Approved order, receipt and supplier document | Review the document and relevant report | Status can be traced to the request, approval, order and receipt | Supplier document does not match the receipt | Document reference; report; reconciliation note | Finance lead |
The quantities, documents and expected outcomes in the test plan should match the business case you intend to accept. If your policy does not say who can accept a short delivery or correct a receipt, pause the test and assign that decision to the organisation. The ERP cannot settle an undocumented policy choice on your behalf.

Illustrative photograph. Prepare the expected result before running the acceptance scenario.
Put the exception in the receiving step
Suppose an order is for 12 identical units and the supplier brings 9. The number 12 is an illustrative test value, not a recommended rule. Ask the receiving clerk to record the nine that arrived and the supporting delivery note. Then check the outstanding quantity and the status shown to procurement and finance.
Do not tell the presenter what button to click. Ask them to explain the available paths under your policy: keep the balance open for a later delivery, record a supplier shortfall, return or reject goods, close the remaining quantity with authorisation, or follow another documented route. Which options are valid depends on the organisation’s controls and the product configuration.
For each path, record four things: who may take the action; what the system blocks or permits; what evidence and history remain; and what the next role sees. If the presenter cannot demonstrate the behaviour, record it as “not demonstrated”. A verbal assurance or a slide is not evidence that the tested workflow does it.

Assign the short-delivery decision: record the missing quantity, retain delivery evidence and name who decides the next step.
Test correction, access and the trail left behind
An exception test is incomplete until you check how an error is corrected. Ask the receiving clerk to attempt a correction, then test the role that is allowed to approve or post it. Compare the original and corrected quantities, the reason for the change, the user and time recorded, and the report after correction.
Try one action with a role that should not be allowed to perform it. The result should be understandable to that person and visible to the responsible reviewer where your control design requires it. Do not assume that an error message alone proves an adequate audit trail; inspect the underlying record and its history.
Keep separate findings for:
- a control that worked as expected;
- a control that failed or was unclear;
- a step completed by manual work outside the system;
- a requirement the demonstrator could not show;
- a policy decision your organisation still needs to make.
This distinction stops a manual workaround from being recorded as a system capability and stops an unresolved policy question from being labelled a software defect.
Sign off evidence, not confidence
At the end of each scenario, compare expected and observed behaviour. Attach screenshots or test references where permitted, record the test environment and configuration, and give every failure an owner and next review date. Define in advance which failures block acceptance and who can approve any known exception.
Sign-off should identify the workflow, roles, test data, configuration, results and open issues it covers. Record which test environment and product version were used, the entry conditions, the pass criteria and who can accept a known issue. It should not imply that the entire ERP is ready if only the purchase path was tested. Security, migrated data, integrations, other business processes and operational support need their own evidence and acceptance decisions. See Microsoft’s Dynamics 365 testing strategy for product-specific examples of test planning and outcome tracking.
Take the scenario into a Kraal Code demonstration
Kraal Code covers procurement, supplier records, requisitions, purchase orders, receipts, approval workflows and audit trails. Chwezi’s implementation approach includes testing critical workflows. Bring your approved purchase scenario so the team can work through the quantities, responsibilities and correction path with you.
Arrange a Kraal Code ERP demonstration with your purchase team. Agree the configuration and acceptance checks through Chwezi’s Kraal Code implementation service.
For the preparation questions that come before a demonstration, read Is Your Organisation Ready for an ERP Implementation?. For decisions about configuration and custom development, see Configure or Customise Your ERP?.
Sources and scope
- Chwezi Core Systems, Kraal Code ERP implementation.
- Microsoft Learn, Testing strategy for Dynamics 365 implementations. Guidance on business-process testing and acceptance evidence for Dynamics 365 implementations.
- Currentness check: Microsoft Learn page accessed 31 October 2026; its displayed update date is 1 June 2025. Use as general process guidance only and recheck before relying on Dynamics-specific instructions.
- The four roles, 12-unit example and acceptance script are illustrative editorial material. Approval limits, tax treatment, accounting and exception ownership must come from the organisation and local advisers where applicable.
Common questions
- What is ERP user acceptance testing?
- It is a business-led check that the configured system supports the organisation’s agreed work and controls. Users follow defined scenarios, compare observed behaviour with expected results, retain evidence and record unresolved issues before approving the tested scope.
- Should a purchase test include a partial delivery?
- Yes, when partial deliveries are possible in your operation. Record the quantity ordered and the quantity that actually arrived, then verify the remaining balance, receipt history, exception owner and downstream reporting against your approved process.
- Does passing one purchase scenario prove the ERP is ready to launch?
- No. It provides evidence about the scenario and configuration tested. It does not establish that other workflows, migrated data, integrations, security, performance or operational support are ready. Define those as separate acceptance areas.
- What should we bring to a Kraal Code purchase-workflow demonstration?
- Bring an approved purchase scenario, the expected quantities and your correction rules. Work through the purchase order, receipt, approval and audit history with Chwezi, then agree the configuration and acceptance checks.