How should a reseller inspect a generated allocation release before licensing it onward?

Before you license a release onward, inspect it the way a buyer will. Start with structure, then behaviour, then risk.

**Structure.** Check that identifiers resolve across tables, that amounts reconcile, and that dates run in a sensible order. A payment applied before it was received, or an invoice cleared for more than it was worth, signals a generator fault.

**Behaviour.** Read a sample of cases end to end. Does the chosen allocation follow the cited policy? Are partial, combined, duplicate and unreferenced payments present, and are the ambiguous ones genuinely ambiguous rather than solved by a leaked hint?

**Variety.** Look at whether references, payer behaviour and domain terms differ across cases, or whether the same few patterns repeat with new numbers.

**Risk.** The data is generated, but that does not remove the need to inspect it. Check whether any text or combination of fields could be traced to a real organisation or individual, and ask MirrorFirm how grounding was handled so you can describe it accurately to your customers.

Finish with a small scored run: give a baseline system the inputs and compare its answers to the labels. If a trivial amount-matching rule scores well, the set is too easy for the use you intend.