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.
- Travel Expense Optimizer
- Features
- Changes and receipts
Changes and receipts
Cancel trips under policy, record no-shows only after the threshold, correct approved scope and reconcile the receipt of every controlled action.
OverviewUnresolved Operations×
Travel Expense Optimizer · Changes and receipts
New
Unresolved Operations
Operation receipts
| Operation key | Action | Expected revision | Result state | Occurred at | External reference | |
|---|---|---|---|---|---|---|
| OK-674 | ACT-557 | 120 | Pending | 21 Oct | ER-906 | |
| OK-613 | ACT-982 | 250 | Needs review | 12 Oct | ER-689 | |
| OK-226 | ACT-869 | 830 | Pending | 26 Oct | ER-701 | |
| OK-560 | ACT-326 | 280 | Needs review | 08 Oct | ER-784 | |
| OK-715 | ACT-849 | 150 | Pending | 18 Oct | ER-377 |
6 of 6 records
OK-674Operation receipts · OR-89286
PendingActionACT-557
Expected revision120
Occurred at21 Oct
External referenceER-906
Effect referencesER-662
What you can do
Change plans without losing what happened
Trips change. A meeting moves, a traveler falls ill, a flight is missed. A cancellation is checked against the cancellation policy and the actual timing, and releases the units reserved with the supplier. A no-show is recorded only after the threshold has passed, so a traveler who is merely late is not marked absent. Completed trips keep their history whatever happens afterwards.
Corrections follow one rule. Anything not yet carried out is cancelled and its claims released. Anything already carried out, such as a flown leg, needs a compensating action approved by a Travel Approver and linked to the original. Booking history is never deleted.
Each controlled action, whether a hold, a confirmation, a cancellation or a correction, leaves an operation receipt with its operation key, the action, the revision it expected and its result: Pending, Completed, Failed or needs review. The Payments Analyst reconciles pending and unresolved receipts against the records they claim to have changed, without simply calling the provider again.
How the work is organized
- Cancel under policy. Cancellations respect the policy and the timing, and release reserved units.
- No-show after the threshold. A no-show is recorded only once the threshold has passed.
- Receipts reconciled. Pending and unresolved receipts are checked against their effects and closed as Completed or needs review.
What to agree during setup
Agree the cancellation policy for each supplier type and who may override it. Agree the no-show threshold, for example two hours after the start. Agree who reconciles receipts and how often, and who investigates a needs review receipt. Agree what counts as a compensating action, such as a change fee booking or a refund request.
Check the handoff on an actual case
A confirmed Denver trip is cancelled two days before departure because the workshop moves. The coordinator cancels the booking under policy; the reserved seat is released and the airline’s refund is recorded. The receipt shows the cancellation Completed.
On another trip the traveler flew out but missed the return. The outbound leg is executed, so it is not cancelled. The coordinator prepares a compensating rebooking for the return, the approver approves it, and both legs stay on the trip’s history. That evening the analyst finds a confirmation receipt still Pending after a provider timeout. The booking shows the supplier’s confirmation date, so the analyst marks the receipt Completed instead of confirming again.
What your team sees
- Unresolved Operations — Pending and needs-review receipts with operation key, action, expected revision and effects.
- Failed Operations — Failed receipts with their failure reason.
- Completed Bookings — Finished trips with supplier, quoted amount and completion date.
Follow the work through
- Cancellation and no-show: Cancel under policy or record a no-show.
- Correction of approved scope: Correct a trip with part of it already travelled.
- Receipt reconciliation: Close pending and unresolved receipts.
Check permissions before go-live.
What it keeps track of
Data model- Operation receipts
- Durable receipts for guarded operations with stable operation keys.
- Bookings
- Travel booking records with lifecycle, quoted amount and counterparty.
- Payment evidence
- Provider payment events reconciled against a booking.
- Review decisions
- Independent reviewer decisions recorded against a booking revision.
Who uses it
Permissions- Travel Coordinator
- Cancels trips and prepares corrections.
- Travel Approver
- Approves compensating actions.
- Payments Analyst
- Reconciles receipts.
- Admin
- Investigates repeated failures.
Set up Travel Expense Optimizer your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.