How to Track Client Payment Evidence and Verification
By the TripTended team
A client sends a receipt for a deposit. Before you describe that deposit as paid, you need to establish what the receipt concerns, check the relevant external record and decide which payment obligation it covers. Saving the file is only the first step.
This guide helps you produce a payment review note with traceable evidence, a verification result, an allocation and a named next action. Use one trip and your organization’s designated payment or accounting records. The method is for recordkeeping; it does not process payments, establish settlement rules or replace your organization’s financial procedures.
1. Identify the obligation before counting receipts
List what is due for the trip from the applicable reviewed agreement or payment schedule. Give each obligation a reference and retain its amount, currency, payer, payee, purpose and stated due date. Keep the original schedule and its version. Leave an unknown date or time zone open for clarification.
Separate client receipts from supplier payments. Money received from a client does not establish that a supplier was paid. A software subscription invoice is also separate from the traveler’s trip payments.
For each obligation, record the evidence references, the amount actually verified and allocated to it, and the remaining amount in that same currency. Do not reduce an obligation because a receipt exists. If the scope or amount has changed, establish the applicable revised obligation before updating the review; retain the earlier version and reason.
Checkpoint: you can explain what is due without using the number of uploaded files as a payment total.
2. Record what the evidence actually says
Keep the original receipt or message in the authorized trip record. Reference it from your review rather than copying account numbers, card details or private access links into a shared worksheet. If a file covers several transactions, identify the specific entry you reviewed.
| Evidence field | What to record |
|---|---|
| Trip, evidence and source references | The trip, a unique evidence reference, and the original file or message version. |
| Direction and counterparty | Whether this is a client receipt or supplier payment, and the stated payer or payee. Do not infer these from an invoice total. |
| Amount and currency | The amount shown for this transaction, with its original currency. Keep fees or differences visible rather than silently changing the value. |
| Transaction time and reference | The stated time, its known time zone or offset, and the external transaction reference if supplied. Mark missing details as unknown. |
| Verification result | Start as not verified. Record the reviewer, check time, method, external reference and finding after the separate review. |
| Allocation and follow-up | Which obligation each verified amount covers, any unapplied amount, and an owner and next check for unresolved differences. |
An invoice describes an amount requested; it does not by itself show a payment. A screenshot labeled pending is not evidence of a completed transaction. Keep the source’s wording and resolve the uncertainty through the appropriate external system or responsible person.
3. Verify separately, then allocate deliberately
Compare the evidence with the record your organization uses to check that transaction. Confirm the trip, transaction identity, payer or payee, direction, amount, currency and reported status. Record where you checked, who checked and when. Apply your organization’s procedure for deciding whether that result is sufficient; there is no universal waiting period in this guide.
If a field disagrees or the external record is unavailable, leave the verification open. Write the exact difference and the next check. Do not resolve a mismatch by editing the receipt to match the planned amount.
Once the transaction has been verified, identify the obligation it supports. Check both sides of the allocation:
- The allocated amounts must not exceed the verified amount of that transaction.
- A new allocation must not exceed the amount still due on the obligation.
- The trip, currency and direction must agree. Keep different currencies and client/supplier directions in separate totals.
- Any verified but unapplied amount needs an explicit note; it does not automatically cover another obligation.
In TripTended, recorded payment evidence and verified payment are separate states. Recording evidence leaves a review for the advisor; it does not move money. Verification and allocation concern the internal record, not a transfer or a guarantee from a bank or supplier. The worksheet fields here are a suggested review method, not an import format or a claim that software performs the external check for you.
4. Reconcile the fictional deposit example
The following numbers and references are invented for a paper exercise. They are not a real client payment, bank result or production test. Assume an authorized reviewer has checked one external client receipt R-01 for EUR 500.00. There are no earlier allocations or refunds in this example.
| Client obligation | Amount due | Allocation from R-01 | Remaining |
|---|---|---|---|
| M-01: deposit | EUR 300.00 | EUR 300.00 | EUR 0.00 |
| M-02: later balance | EUR 400.00 | EUR 150.00 | EUR 250.00 |
The allocations total EUR 450.00: 300.00 + 150.00. The receipt has EUR 50.00 unapplied: 500.00 − 450.00. Across the two client obligations, EUR 250.00 remains: 700.00 − 450.00. These are different questions; an unapplied amount is not another receipt or an automatic allocation.
Now suppose a second screenshot arrives with the same transaction reference as R-01. Preserve it as additional evidence of the same transaction while you check for duplication. It does not establish another EUR 500.00 payment. A separate supplier obligation for EUR 400.00 also stays in the supplier-payment review; the client receipt does not cover it merely because the currency matches.
Check your result: the receipt total is 500.00, allocated total 450.00, unapplied total 50.00 and client obligation remainder 250.00. You should be able to trace each allocation back to both R-01 and an obligation. If your note counts two screenshots as two payments, or clears the supplier obligation, revisit the mapping.
5. Keep discrepancies and later changes visible
Use a specific unresolved question instead of a vague paid/not-paid summary:
| Situation | What remains open |
|---|---|
| Two files appear to describe the same transaction | Confirm transaction identity before counting a second receipt. Keep both sources and the comparison. |
| Amount, currency or direction differs | Record the stated values and ask the responsible person to explain the difference. Do not invent an exchange rate or treat a supplier payment as a client receipt. |
| A payment or allocation changes after review | Preserve the earlier result, record the correction and repeat the affected checks against current evidence. |
| A refund is requested or a refund receipt arrives | Track the refund evidence and its verification separately from the original payment. A request or a file does not establish that money was returned. |
Do not apply the example’s simple subtraction to a trip with unresolved refunds or corrections. Establish the current verified records and applicable allocations first. If a disputed amount affects an approved itinerary change, link it to the change record so the next advisor can see the unresolved dependency.
6. Hand over a review someone can repeat
Copy the note below into the authorized trip record. Replace the prompts with actual references and results; keep a dated earlier copy when the basis changes. Use separate lines for each currency and direction rather than one combined trip balance.
Trip / obligation schedule version:
Currency / direction / obligation references:
Evidence / external transaction references:
Reviewer / check time with time zone / method:
Verification findings and unresolved differences:
Allocations by obligation / verified unapplied amount:
Next action / owner / next check with time zone:
Sources or corrections that require another review:
Before handing it over, follow one allocation back to the original evidence and one obligation back to its current schedule. Check the arithmetic, then confirm that every open difference has an owner and a next action. A note that cannot identify its sources is not a repeatable review.
Payment review is one part of delivery. Client approval, supplier confirmation, the client-facing version and Trip Ready still require their own checks. Continue with the pre-departure review or the trip readiness review log. If you are deciding which system should hold each record, use the payment workflow responsibility map.
Explore TripTended · Browse workflow guides · Review current plans
Prepared with AI assistance using TripTended’s documented evidence and business-state boundaries. The review note is a recommended method. The fictional exercise does not claim a real advisor, payment provider or supplier has completed these checks.