Which records and relationships can a generated cash-matching release contain?

A generated release for this workflow can contain a connected set of records rather than isolated rows. Typical groups are:

- **Parties and accounts**: payers, customer or policy accounts, payment terms and contact roles. - **Obligations**: invoices, instalments, premiums, credit notes and adjustments, with due dates and outstanding amounts. - **Payments**: bank-feed lines, card settlements and cheque deposits, each with raw remittance text of varying quality. - **Relationships**: which payment settles which obligations, which credit note offsets which invoice, which case blocks which item. - **Policies**: tolerance for rounding differences, write-off authority, hold periods, and rules on disputed amounts. - **Tasks**: a prompt, a starting state, the allowed tools and a reference outcome.

Relationships are what make the material usable in environments. A set of payments without the open items they could settle gives an agent nothing to act on.

A release can be set to different difficulty mixes: clean one-to-one matches, one-to-many, many-to-one, short-pays, duplicates, and payments with no usable reference. What goes into a given release is scoped with the buyer.

The material is generated and synthetic. MirrorFirm's approach is informed by direct observation of how real businesses run this work, but buyers should still inspect the output for grounding and disclosure risk rather than assume it is clean.