Can a release encode an organisation's allocation policies as well as transactions?

Yes. Policies can be generated as structured records and as plain-language text, and the two can be linked so an agent must read the text while a grader checks the structure.

**What does a policy record hold?** - An allocation order, such as oldest due first, or fees and interest before principal. - Tolerance bands for short and over payments. - Treatment of disputed, on-hold and plan items. - Approval thresholds by role. - Rules for unapplied cash, including when to refund and when to hold.

**Can policies differ between customers?** Yes. A release can attach a policy version to a customer segment or contract, so the right rule depends on a lookup. Tasks can also include a policy change mid-period, with the effective date stored, to test whether an agent applies the version in force on the payment date.

**Can policies conflict?** A buyer can ask for deliberately ambiguous or conflicting clauses, with a stated precedence, to check whether the agent escalates instead of improvising.

**What are the limits?** The policies are generated and will not match your organisation's exact rules. Use them to test reading and applying rules, then substitute your own policy text in a pilot if you want a closer fit.