Completion, hold & cancel
Complete an order when all conditions are met, and handle the special paths — putting an order on hold or cancelling it.
This is the end of the lifecycle. An order reaches Order Completed6 once everything is done. Along the way, orders can also be paused (On Hold9) or terminated (Cancelled8).
Completing an order
An order is completed when all of its conditions are met:
- the report is Report Accepted13 by QC,
- it has been delivered to the borrower,
- UCDP/EAD has been submitted (if required), and
- payment has been processed.
Completion moves the order to Order Completed6, closes the audit trail, and starts the retention clock.
You don't usually "force" completion — it's the natural result of finishing delivery, submission, and payment. If completion is blocked, check which of those prerequisites is still open.
Putting an order on hold
Any active order can be paused — for example, while waiting on the client, a document, or a payment issue. A hold requires a reason.
| Action | Endpoint |
|---|---|
| Put an order on hold | |
| Reactivate a held order |
A held order is On Hold9; reactivating it returns it to its prior flow, recording who reactivated it and why.
Cancelling an order
An order can be cancelled from most states with a required reason. Cancellation may unassign the vendor and, depending on how far the order progressed, trigger a refund.
| Action | Endpoint |
|---|---|
| Cancel an order (client/ops) | |
| Cancel an order (vendor) |
A cancelled order is Cancelled8 — a terminal state.
Cancelling before work begins is generally fully refundable; cancelling after a vendor has done work may be partially refundable or non-refundable. The further along the order, the more constrained the refund — and the more likely it needs approval. Always capture the cancellation reason for the audit trail.
Reconsideration paths
Even late in the lifecycle, value can be disputed through a reconsideration of value, which reopens a review cycle rather than completing the order. See QC review & revision loop.
You've reached the end of the lifecycle
That's the full journey — from creating an order to completion. From here:
- Integrate with webhooks to react to status changes
- Audit trail & history to prove what happened
- API Reference for the exact contract of every endpoint