Supply the test records yourself
| Scenario | Input/action | Observe in source | Observe in target |
|---|---|---|---|
| Valid record | Send CUST-47 with agreed fields | Delivery result with reference | Matching values under one identity |
| Invalid required field | Omit required status | Actionable rejection | No unintended record |
| Unknown result | Simulate lost acknowledgement | Outcome marked uncertain | Search/reconcile before repeating write |
| Correction | Resend approved change for CUST-47 | Same identity and change reference | Agreed update, no extra customer |
Ask which parts are live, simulated or manually prepared. Record the environment, data set and integration version. A demonstration establishes what was observed in that setup; it does not establish production readiness or an untested vendor capability.
Turn gaps into proposal questions
Only the first successful record is shown. What should the buyer ask next?
Show the worked answer
Request the rejected, uncertain-result and correction scenarios. Ask who reviews failures and what configuration, custom work or customer access is required to deliver those paths.
Put unresolved observations in the requirement matrix with an owner and requested evidence. Keep a copy of the supplied synthetic records so later acceptance tests can reproduce the same cases.