Fixed Fees Against Small Payments
A flat charge on a small transfer is a large percentage, which is why weekly payment costs more than monthly.
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. The unit changes part-way down: the figures below the break are in another currency, the bars below it are drawn against the published rate, and the first figure and the last are not the same kind of number. The section where the figures stop and the estimates start.
A flat charge does not care how much is being sent. The same fee on a small transfer is a large percentage and on a large one is a rounding error, which is why being paid weekly costs more than being paid monthly.
The practical point in “Fixed Fees Against Small Payments” is that a landed payment should be supported by a record somebody can explain. Used for how to monitor employees without being intrusive, how to monitor employees without being intrusive can add transparent time and project context when collection is proportionate, people can correct mistakes and financial records remain separate.
The arithmetic is obvious once written down and is almost never written down.
For an independent payment-sector perspective on “Fixed Fees Against Small Payments”, consult Swift payment resources. Compare general information with the actual route, currency, provider terms and jurisdiction involved.
The shape of the cost
Most routes carry two kinds of cost: a flat element, made of the sending fee, any correspondent deduction and the receiving fee, and a proportional element, which is the conversion margin.
The flat part is what makes frequency expensive. The proportional part is indifferent to it.
Separating the two is the first step in any decision about frequency, batching or splitting, and it takes two payments of different sizes to do.
What frequency actually costs
Twelve monthly payments carry twelve sets of flat fees. Fifty-two weekly payments carry fifty-two.
On a route with thirty units of flat cost per transfer, the same annual income carries very different costs:
| Frequency | Transfers a year | Flat cost |
|---|---|---|
| Weekly | 52 | 1,560 |
| Twice monthly | 24 | 720 |
| Monthly | 12 | 360 |
Same money moved, three different answers.
Where small payments stop making sense
When the flat cost exceeds a per cent or two of the amount. Below that threshold, the transfer is spending a meaningful share of itself on arriving.
Work out your own threshold once: flat cost divided by two per cent gives the amount below which a separate transfer is poor value.
Why people are paid weekly anyway
Cash flow, usually theirs rather than the payer's. Somebody who needs the money weekly is correct to take the cost, and the cost is worth knowing rather than ignoring.
The useful conversation is not frequency against cost in the abstract. It is whether the payer will carry the extra fees for the frequency you need.
Batching, and its own note
Fewer, larger payments reduce the flat cost and increase what is exposed to a single failure. That trade has a note of its own in the last section.
The arithmetic here is only half the decision.
Where flat fees hide
Not every service presents one. Some fold the whole cost into the rate, which makes the charge proportional and removes the frequency penalty entirely.
For anybody being paid in small amounts, that structure is usually better, and it is visible only by measuring the all-in rate at two different amounts.
Minimum charges
Several services apply a minimum, so that a small transfer costs a fixed floor regardless of the stated percentage.
That is the same trap in different clothing. Check for it explicitly at the amounts you actually receive rather than at the amounts in the pricing example.
Expenses and reimbursements
Small, irregular amounts are the worst case: a hundred units of expenses can lose several per cent to fees.
Roll them into the next regular payment. It costs the payer nothing and removes an entire category of annoying transfers.
Splitting payments across accounts
Receiving part in one currency and part in another doubles the flat cost.
Occasionally worth it for somebody with genuine costs in two places. Rarely worth it for the sake of tidiness.
Multiple clients, multiple fees
Several payers each sending separately is several sets of fees, and no amount of arranging at your end changes it.
Where one payer dominates, the frequency question is worth raising with them. Where income is spread across many small clients, a service with a proportional structure is the only real lever.
What to ask the payer for
Either less frequent payment at the same total, or the same frequency with the charges borne by them.
Both are ordinary requests. Payers choose frequency to suit their own process and generally have no view at all on which you prefer.
Ask with the arithmetic attached. Twelve against fifty-two sets of fees is a figure anybody can check, and it is more persuasive than a preference.
What frequency cannot fix
The proportional cost. Paying once a year rather than monthly removes eleven sets of flat fees and leaves the conversion margin exactly where it was, because the margin is a percentage of the money and the money is the same.
That is why this note sits beside the one on margins rather than replacing it. The two costs have different shapes, they respond to different decisions, and a change that helps one does nothing at all for the other.
Knowing which shape dominates your own arrangement is therefore the first thing to establish, and two payments of different sizes establish it in an afternoon.