Keeping Your Own Record of Both Ends
Four columns, kept as payments arrive, turn a vague sense that something is wrong into a figure.
Still yours, and statedTaken, never statedUnit changes; scale restarts
Four steps from instruction to arrival. One step carries no figure: the hatching marks where the money leaves and is not drawn to scale, because there is no figure to draw. Nothing here adds them up, since an amount you cannot see is not an amount you can subtract. One line, two facts, and a gap where the rest of the journey was.
Four columns, filled in as each payment arrives, turn a vague sense that something is wrong into a figure somebody else can check.
The evidence question in “Keeping Your Own Record of Both Ends” calls for records that can be reconciled rather than one unexplained total. For teams exploring employee monitoring software with screenshots, open the related Monitask resource can supply time and project context, provided corrections remain visible and the payment provider or bank remains authoritative for settlement and currency data.
Without them every conversation about this subject is an exchange of impressions, and impressions lose to a bank's confidence every time.
The questions in “Keeping Your Own Record of Both Ends” can also be checked against IMF fintech resources. Use the outside resource to identify what evidence to request rather than assuming one provider sees the whole payment chain.
The four columns
The minimum, and enough for most of this collection:
| Column | Source |
|---|---|
| Date instructed | Their confirmation |
| Amount sent, with currency | Their confirmation |
| Date credited | Your statement |
| Amount credited | Your statement |
Everything else here is an optional fifth and sixth.
Four fields is deliberately few. A record with twelve columns is a record that stops being filled in by the third month, and an empty spreadsheet is worth less than a short one.
The fifth column
The published midpoint for the conversion day. Two seconds to look up at the time and impossible to reconstruct reliably later.
With it, the all-in cost of every payment computes itself. Without it, the table records what happened and not whether it was reasonable.
The sixth
Stated fees, both ends, where known. This separates what was disclosed from what was not, which is the distinction the middle section of this collection rests on.
Where the payer's confirmation arrives automatically, this costs nothing to fill in.
Where to keep it
A spreadsheet. Not an accounting system, which records invoices and credits and is not designed to hold a rate comparison.
One sheet, one row per payment, kept for the life of the arrangement.
Keep it somewhere that survives a change of computer and a change of bank. The value is entirely in its length, and a record that starts again every year answers none of the questions it exists for.
Doing it at the time
The whole method depends on this. A payment recorded when it arrives takes a minute; a year reconstructed in March takes a day and is missing the rates.
Attach it to an existing habit — the moment you see the credit notification is the natural one.
What three months gives you
The ordinary cost of the route and the ordinary transit time. Enough to tell whether a bad month was unusual.
That alone resolves most of the anxiety in this subject, because most of it comes from not knowing what normal looks like.
It also tells you when something is genuinely wrong, which is the other half of the same benefit and the one that actually saves money.
What twelve months gives you
Drift. Routes get worse quietly and nobody writes to tell you. A column of all-in percentages shows it at a glance.
It also gives you the seasonal shape: which months are slow, where holidays bite, what the year actually costs.
Using it with a payer
Export the relevant rows, add the payer's confirmations, and send both. The argument makes itself.
A table of twelve payments is a document. A sentence saying the payments seem short is a complaint.
Using it with your own bank
Where the conversion is theirs, the same table shows what they applied against the published rate, month after month.
Some banks will improve a rate when shown this. Most will not, and you will at least know what to compare a rival's offer against.
Using it at year end
Your tax position needs the invoice currency, the rate and the credited amount, and the table already has all three.
Several people discover at this point that the record they kept for one reason solves a problem they were dreading for another.
It also settles the question of which date a payment belongs to, which at a year end is the difference between two tax periods and is not recoverable from memory.
What not to bother with
Intermediary fees, which you cannot know. Internal reference numbers, which do not help. Anything requiring you to ask somebody a question each month.
A record that needs maintenance will not be maintained. Four columns from data that arrives by itself will.
What the record cannot establish
Fault. A year of careful measurement tells you precisely what the arrangement costs and precisely how long it takes, and says nothing about whether anybody behaved badly.
That is the right outcome. Nothing in this subject is usually anybody's misconduct, and the useful response to a measured cost is to change a term rather than to find somebody to blame — which is what the last section of this collection is for.
That is also why it is worth keeping when nothing is wrong. A record begun during a dispute is a record with no baseline, which is the one thing it needed to have.