Which record types should a reseller request in a generated allocation release?
A checklist of record types that together let a release represent allocation work: payments, remittances, obligations, accounts, policies, decisions, exceptions and reversals.
Use this list when requesting a release, so the record set can support the exceptions your customers care about.
- Bank feed lines or card settlements with raw references of varying quality, including blank and misleading ones. - Remittance advices that list several obligations, some with totals that do not add up. - Open obligations (invoices, premiums, instalments) with due dates, balances and status history. - Account and payer records, including related entities and parent accounts, so payments can arrive from the wrong party. - Written policies with versions and effective dates covering ageing order, tolerances and holds. - Allocation decisions linked to a policy version, a role and a timestamp. - Exception queue entries with handover notes, reason codes and resolutions. - Reversals, refunds and re-applications that link back to the original payment.
Request the full chain from payment to decision to reversal, so buyers can test realistic exceptions rather than isolated matches.
- Audience:
- Licensed resellers
- Content type:
- Checklist
- Buyer question:
- What can be generated
Content release: r-a220eb6e099b243b
Related questions
- Can a release encode an organisation's allocation policies as well as transactions?
- What would a generated task for an insurance short-pay look like?
- What do the record schema and links look like in JSONL?
- What can a generated dataset for matching payments to obligations contain?
- Which record types should I request for a simulated payment matching environment?
- Can a release include tolerances, write-off limits and approval rules?