MANUFACTURING ERP ACCEPTANCE-TEST PACK
Tellency evaluation resources | Reviewed 3 November 2026
https://tellency.com/resources/erp-evaluation-tools

Purpose: test the ERP you are evaluating with a shared evidence register.
These are illustrative acceptance criteria, not a claim that every system,
configuration or Tellency deployment passes every test. Agree your own expected
results and implementation scope with the vendor. No customer data is used.

HOW TO USE
1. Copy this pack into your project register and assign an accountable reviewer.
2. Use a sandbox with agreed products, units, dates, roles and opening balances.
3. Run each case with the roles your team will actually use.
4. Save document IDs/screenshots after removing personal or confidential data.
5. Record PASS, FAIL, CONFIGURATION REQUIRED, INTEGRATION REQUIRED or NOT TESTED.
6. Repeat failed cases after changes, including their downstream stock/finance.

For EACH test capture:
Test ID / requirement:
Environment and software version:
Data and preconditions:
Expected result agreed before test:
Steps and role performing them:
Observed result and record IDs:
Stock and financial reconciliation:
Evidence location:
Status / unresolved gap / owner / due date:
Reviewer and sign-off date:

M01 — BOM REVISION AFTER ORDER RELEASE
Set up product A with a released order using BOM revision 1. Create revision 2
with a changed component quantity. Check which revision applies to existing
and new orders and whether changes require approval. Expected: the revision
used by each order is identifiable; an unapproved change does not silently
alter the agreed released-order requirements. Save order and revision IDs.

M02 — COMPONENT SHORTAGE
An order requires 100 units of component B; usable stock is 80. Add a late
supplier receipt for 20. Run planning. Check shortage quantity, suggested
supply, proposed dates and whether existing supply is counted twice.
Expected: demand, usable stock, expected supply and shortage reconcile.
Record planning assumptions, reservations and any manual overrides.

M03 — CAPACITY CONFLICT
Two operations need the same work centre during the same period. Add a shift
closure or maintenance interval. Check the schedule against available capacity
and the agreed planning model. Expected: a conflict or feasible sequence is
visible; calendar assumptions and manual overrides are traceable.
Do not assume a displayed calendar proves finite-capacity scheduling.

M04 — MATERIAL ISSUE AND LOT IDENTITY
Receive a lot, issue part to an order and trace the remainder. Test an invalid
lot and insufficient quantity. Expected: authorised issues reconcile to stock;
lot identity and rejected attempts can be investigated using retained records.
Validate unit conversion and location rather than assuming pack equivalence.

M05 — GOOD OUTPUT, SCRAP AND REWORK
For an order of 100, record 95 good units and 5 units requiring disposition.
Confirm how scrap/rework differs from completed usable output. Expected:
quantities and material usage reconcile and no double-counting of output occurs.
Trace the disposition and the role allowed to approve it.

M06 — QUALITY HOLD
Record a failed inspection and place affected stock on hold where required.
Attempt the prohibited next operation or shipment using an ordinary role.
Expected: the agreed control prevents or flags the action; release authority,
reason and follow-through are visible. A warning is not equivalent to a block.

M07 — COST AND LEDGER RECONCILIATION
Agree the costing method before running the test. Capture component, labour,
machine and overhead assumptions. Compare planned cost, recorded activity,
WIP, output and any posted variances. Expected: each reported amount has a
reproducible calculation and an identifiable ledger or reporting treatment.
Do not equate a BOM estimate with complete actual-cost accounting.

M08 — CLOSE, CORRECT AND AUDIT
Close an order with an exception, then request a correction. Check permissions,
period restrictions, reversal method and resulting balances. Expected: a
reviewer can trace who changed what and reconcile the corrected result.

M09 — AGENT ACTION BOUNDARIES
Ask an enabled agent to prepare a supported production-related action.
Run a permitted action, an approval-required action and an out-of-scope action.
Expected: role permissions and approval rules hold; the resulting business
record and execution evidence identify what actually happened.
No agent should be assumed to have unrestricted access to all workflows.

DECISION REGISTER
Must-have tests passed:
Conditional scope and price:
Unresolved gaps and workarounds:
Integrations and owner:
Migration and training assumptions:
Acceptance decision / approver / date:

Reuse: you may copy and adapt this worksheet for ERP evaluation. If publishing
an adaptation, identify your changes and cite the resource page above. A link
is welcome when useful to readers; no endorsement or reciprocal link is required.