Can a release include policies, exceptions and handovers, not just transactions?

**Can a release include the policies, not just the transactions?** Yes, a buyer can ask for them. Policies can be generated as structured rules with identifiers, plus plain-language text, so a task can cite the rule that decides the outcome.

**What kinds of exceptions can be included?** Short and over payments, payments from a third party, duplicate receipts, references pointing at closed accounts, disputed items, credit notes in flight, foreign currency differences, and bank fees netted off the credit. Each can be tagged so a buyer can sample by type.

**Can handovers be represented?** A release can include case notes, queries to customers, internal escalations and the approval step, with timestamps and role labels such as the credit controller or the finance manager.

**Can the policy be changed between cases?** A task pack could vary tolerance limits, ordering rules or approval thresholds across versions. That allows a lab to test whether a model reads the rule in front of it rather than reproducing a habit.

**Are these real records?** No. Everything delivered is generated, synthetic material informed by direct observation of how businesses operate. A buyer should still check grounding and disclosure risk on a sample, because generated text can resemble real patterns more closely than intended.

**Is there a reference for structure?** Aster Financial is MirrorFirm's sample organisation, and a buyer can ask to see its generated material as a starting reference for how the records and policies are laid out.