Skip to main content

UAT checklist and pass criteria

The customer must run these checks from the named ERP/integration runtime. Postman can diagnose a problem but cannot replace ERP-origin evidence for a step the ERP did not complete.

  • Obtain a token and run discovery from the ERP/integration runtime.
  • Match authority, destinations, and capabilities to the private manifest as exact sets.
  • Dry-run every required grant tuple and inspect every item.
  • Persist one bounded row for every required tuple.
  • Poll all jobs to terminal and reconcile counters with items.
  • Prove same-key replay creates no duplicate.
  • Prove lost-response and ERP restart recovery with the same durable identity.
  • Prove business duplicate is skipped and new business creates one row.
  • Prove an ungranted destination is denied without a job/write.
  • Run the capability/validation branch required by grant mode.
  • Reconcile organization, facility, period, Scope, quantity, unit, emission, and updater in CFO.

Every tuple must be PASS, FAIL, BLOCKED, or NOT_APPLICABLE with a reason. The signed report records runtime version, zone, manifest SHA-256, schema/catalog versions, test window, and customer/CFO owners.

Download the UAT checklist and acceptance report template.