Operations and payment

An operation receipt records an action, stable operation key, expected revision, result state and occurrence time. It can also hold an external reference, effect references and a failure reason. Pending, completed, failed and needs-review states tell staff whether the requested action has a matched result. A repeated request with the same key should return the same outcome rather than issue another copy or duplicate a payment-dependent effect.

Payment evidence records provider events by ID, type, amount, occurrence time, verification flag and provider reference. Authorization, capture, refund and void are separate event types. A prepared refund is a reviewed next step; it is not a completed transfer until the provider’s effect is verified. The operational history and money evidence must agree before completion is accepted. Keep the provider event ID with the parent loan so another analyst can check the same event later.

• Guarded request. The actor’s organization, source record and expected revision are checked before a write.
• Provider evidence. A verified capture supports payment-dependent custody and completion decisions.
• Reconciliation. An analyst compares open receipts to their local effects and the authoritative external reference when present.

Choose the provider event that counts as a verified capture, and decide how its ID and reference enter the record. Set the source used to check an external reference during reconciliation. Define who handles a discrepancy and how the failure reason is written for a colleague. Staff should know that a receipt in needs review calls for investigation, not another execution attempt.

The pilot should exercise a repeat request and an uncertain provider outcome. The team should find one receipt per operation key and examine the actual linked effects before marking it completed. If the provider effect is missing or mismatched, the receipt stays for review with a concrete discrepancy.

An Admissions Coordinator attempts to issue reserved copies. The action receipt records the expected loan revision and the provider reference. The Finance Reviewer checks the capture event and its verified flag. The Operations Analyst finds the local loan-event line and compares it to the receipt’s effect reference. If the line exists but the capture is unverified, the analyst marks the receipt for review and records why. Once the authoritative effect matches, completion can proceed without issuing the copies a second time.

• Receipts needing review — Find guarded actions whose effect needs investigation.
• Capture evidence — Compare provider capture records with their verification state and loan parent.

See payment reconciliation and correction and closure.