These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Trade Finance Platform
- Features
- Operations Control
Operations Control
Keep a receipt of every guarded action and resolve those that are pending, failed or need review.
OverviewOperation Exceptions×
Trade Finance Platform · Operations Control
New
Operation Exceptions
Operation receipts
| Parent | Action | Operation key | Result state | Occurred at | Failure reason | |
|---|---|---|---|---|---|---|
| LA-91469 | ACT-618 | OK-303 | Pending | 27 Oct | Cut to length | |
| LA-27830 | ACT-150 | OK-316 | Failed | 08 Oct | Weld frame | |
| LA-33686 | ACT-505 | OK-308 | Needs review | 15 Oct | Drill and tap | |
| LA-16032 | ACT-963 | OK-550 | Pending | 22 Oct | Deburr | |
| LA-33238 | ACT-125 | OK-800 | Failed | 07 Oct | Assemble |
6 of 6 records
ACT-618Operation receipts · OR-86956
PendingParentLA-91469
Operation keyOK-303
Occurred at27 Oct
Failure reasonCut to length
What you can do
Know that every action happened once
Every guarded action, such as an underwriting decision, a disbursement, an allocation or a letter of credit issuance, leaves an operation receipt. The receipt records the action, a unique operation key, the version it expected, the outcome, the time, any external reference, the records it affected and the failure reason. Outcomes are Pending, Completed, Failed or needs review.
A repeated action with the same key returns the original receipt. Receipts that stay Pending or Failed are reconciled by reading what was actually recorded: if the expected effect is there, the receipt is marked Completed; if not, it is marked needs review with the discrepancy. External actions are never repeated from this step.
How the work is organized
- Receipts for every guarded action. Each receipt names what it expected and what it found.
- Exceptions in one list. Pending, Failed and needs review receipts sit together for operations.
- Organizations and team scope. Each lending entity has its own time zone and currency, and team members act within their entity.
What to agree during setup
Agree who reviews operation exceptions and how quickly. Decide when the routine reconciliation runs. Agree what evidence lets a receipt be marked Completed and who signs off a needs review receipt.
Check the handoff on an actual case
A repayment import times out halfway through allocation. The receipt is left Pending. The next morning the Loan Servicing Officer opens Operation Exceptions. The reconciliation reads the repayment and finds its allocations recorded in full, so the receipt is marked Completed.
A disbursement receipt shows Failed with a provider timeout. No disbursement is recorded and the provider has no record of the transfer. The receipt is marked needs review with that finding, and the Credit Officer calls the provider before anything is resubmitted.
What your team sees
- Operation Exceptions — Receipts waiting for review, with action, outcome and failure reason.
- Review Decisions Log — The decisions behind each guarded action, with reasons.
Follow the work through
- Servicing changes and reconciliation: Resolve receipts and changes.
- Loan disbursement to repayment: See where receipts are left.
Map the source records before importing history.
What it keeps track of
Data model- Operation receipts
- Durable operation receipts
- Organizations
- Lending and operating organizations
- Team members
- Platform members with role scope
- Loan applications
- Operational loan applications
Who uses it
Permissions- Loan Servicing Officer
- , Credit Approver, Admin.
- The Loan Servicing Officer resolves receipts.
- The Credit Approver reads the trail.
- Admin
- Maintains organizations and team members.
Set up Trade Finance Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.