Why consolidate 2 Budget leaves into this page?

Because the useful action is one control system. Refund Watch, Points Audit belong together when a traveler is making the same money decision.

What should I do first for refunds, points & loose ends?

Start with the ledger row that can cost money soonest. Then build the packet, check the proof table, and calendar the next date or decision.

Is this a spreadsheet page?

No. The sheet is just one tool. The page is the control desk: what number to know, what proof to keep, what choice to make, and what to do when the plan bends.

What should stay in the future breakout queue?

Highly specific search questions, country variants, card-by-card examples, route-specific price studies, and traveler-type versions should break out later without weakening this canonical desk.

How should I use the source links?

Use them to verify rules, fees, rights, and current terms before money moves. Editorial structure helps you ask the right question; the live provider or official source confirms the current answer.

THE TREASURY DESK - CANONICAL CASE FILE

Refunds, Points & Loose Ends - Refund watch, points audit, pending credits, disputes, and rewards that still need to land.

Refunds, Points & Loose Ends travel budget dossier: Refund watch, points audit, pending credits, disputes, and rewards that still need to land. Includes ledger rows, proof checks, timing, scenarios, mistakes, rescue flow, and queued breakout guides. Some trip money keeps moving after you get home. Watch it until it posts.

Case intake

This canonical page consolidates refund-watch, points-audit.

Control ledger

Refund: track Expected credit; proves Amount, method, promised date; avoid Trusting a verbal promise.

Points: track Earned or redeemed; proves Whether rewards posted correctly; avoid Never checking loyalty accounts.

Dispute: track Incorrect charge; proves Evidence and deadline; avoid Waiting too long.

Credit: track Voucher or travel bank; proves Expiration and rules; avoid Letting value disappear.

Packet build

Keep a pending-money list.

Refunds, deposits, travel credits, points, and disputes belong in one watch list until they close.

Watch by statement cycle.

Some credits are slow. The question is not only whether they are promised, but whether they posted.

Audit rewards after posting.

Points and miles can fail to credit, especially with partner bookings, fare classes, and changed tickets.

Escalate with evidence, not frustration.

Confirmation, receipt, policy, date, and amount make a better dispute than a long story.

Timing strip

Trip end

List every refund, deposit, voucher, credit, and points expectation.

One week

Check obvious credits and missing receipts.

One statement

Compare promised refunds to posted credits.

Before expiry

Use or calendar travel credits before they become a donation.

Decision rules

If it repeats, give it a line.

A cost that happens daily, per booking, per traveler, or per movement is not incidental on a real trip.

If it can block the trip, check it early.

Fees, payment limits, route costs, cancellation rules, and refund windows belong in planning, not panic.

If it is optional, name what it replaces.

Splurges are fine when they have a swap. They break budgets when they arrive as add-ons without a cut.

If it teaches you something, keep the lesson.

The cleanup is not shame. It is the next trip getting cheaper, calmer, or more honest.

Scenario drawers

A hotel deposit has not returned

Check the hold release timing, then contact the hotel with folio and card details.

Airline points did not post

Save boarding pass and ticket number, then file the missing-credit request.

A refund posts to a closed card

Ask the issuer where the credit landed before asking the merchant to redo it.

A voucher has odd rules

Write the expiration, eligible routes, and name restrictions in the next-trip file.

Mistakes and rescue flow

Assuming pending credits are the same as posted credits.
Letting points audits wait until the boarding pass is gone.
Missing voucher expiration dates.
Starting disputes without receipts or policy screenshots.

Gather proof before contacting anyone.
Use official support channels and record case numbers.
Calendar follow-up dates.
Close the line only when money, points, or credit posts.

Source box

Future breakout queue

Refund Watch
Points Audit

Frequently asked questions

Why consolidate 2 Budget leaves into this page?: Because the useful action is one control system. Refund Watch, Points Audit belong together when a traveler is making the same money decision.
What should I do first for refunds, points & loose ends?: Start with the ledger row that can cost money soonest. Then build the packet, check the proof table, and calendar the next date or decision.
Is this a spreadsheet page?: No. The sheet is just one tool. The page is the control desk: what number to know, what proof to keep, what choice to make, and what to do when the plan bends.
What should stay in the future breakout queue?: Highly specific search questions, country variants, card-by-card examples, route-specific price studies, and traveler-type versions should break out later without weakening this canonical desk.
How should I use the source links?: Use them to verify rules, fees, rights, and current terms before money moves. Editorial structure helps you ask the right question; the live provider or official source confirms the current answer.