Obligations and repayments

An approved case can have a linked obligation. The obligation record carries its own status, revision, submission and decision dates, organization and initial deposit amount. Operations Manager can follow that record alongside the application without confusing an obligation approval with the credit application decision. The two status histories answer different questions.

When a provider repayment arrives, Repayments keeps its operation key, application, expected revision, received date and outcome. A confirmed receipt may have an external reference and effect references. A receipt needing review carries a failure reason. Principal allocation records hold an amount and direction with links to an application and provider account record. The receipt and obligation must be compared through the case and evidence; the allocation has no direct link to either record.

• Obligation. The obligation record holds its status and initial deposit amount under the parent application and organization.
• Receipt. Repayments holds the provider repayment event and verification state.
• Allocation. Principal allocations record direction and amount against the application and provider account record.

Agree which team records obligations and which events move their status from draft through submission and review. Decide how provider references are captured, how a repeated event is recognized through its operation key, and who resolves a receipt that needs review. Make the provider’s confirmation evidence available before treating an effect as complete. Do not equate a pending receipt with money applied to an obligation.

A practical example is a confirmed repayment against a case that also has an open obligation. Operations Manager records the receipt and compares its external reference with the provider event. The team checks the principal allocation’s amount and direction against its linked application and provider account, then compares the obligation and receipt separately. If the local effects do not match what the receipt claims, the item belongs in review until the discrepancy is explained.

Start from an authorized application with a linked obligation. Follow the obligation’s submission and decision state. Bring in a provider repayment reference, then inspect the receipt, expected revision and effect references. Compare the principal allocation with the case and account record. Repeat the same provider event and confirm that staff recognize the same operation instead of recording a second effect. Rehearse a mismatch and inspect the resulting review reason.

• Open obligations. See obligations still in draft, submitted or approved state.
• Pending repayments. Review receipts before their effects are verified.
• Repayments needing review. Find discrepancies with a recorded reason.

See provider follow-up and reconciliation.