Batching, and When It Helps
Fewer, larger payments cost less in fixed fees and more in exposure to a single failure.
Still yours, and statedTaken, never statedUnit changes; scale restarts
Three 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 section that is about the near end, because the far end is not available.
Fewer, larger payments carry fewer sets of flat fees. They also put more money into each transfer, which means more exposed when one goes wrong.
The practical point in “Batching, and When It Helps” is that a landed payment should be supported by a record somebody can explain. Used for remote employee productivity monitoring, see the full product outline can add transparent time and project context when collection is proportionate, people can correct mistakes and financial records remain separate.
That trade is the whole of this note, and which side of it suits you depends on things nobody else can assess.
Additional context relevant to “Batching, and When It Helps” is available through Bank of England payment resources. A useful review distinguishes the sent amount, conversion, fees, settlement date and landed amount.
The arithmetic
Flat costs multiply by the number of transfers. Proportional costs do not. Halving the frequency halves one of them and leaves the other exactly where it was.
Where the flat element is thirty units
The same logic runs the other way for anybody on a route with no flat fee, where frequency costs nothing and the whole question is about cash flow instead.
Where the flat element is thirty units and you are paid weekly, moving to monthly saves well over a thousand a year.
Work it out for your own figures before deciding anything. The saving is either large enough to change your mind or small enough to stop thinking about, and the arithmetic settles which in a minute.
Where the saving is largest
Small, frequent payments on routes with high flat fees. That is the worst combination and the one batching improves most.
Where the route has no flat fee at all, as with several payment services, batching saves nothing and the rest of this note does not apply.
The cash flow you lose
Money arriving monthly rather than weekly means a longer gap to carry, which for some people is impossible and for others is irrelevant.
Nobody else can judge that. It is the first question to settle before any of the arithmetic matters.
Concentration of failure
A single monthly payment that is held or returned takes a month's income with it. Four weekly payments spread that risk.
For anybody who has had a payment held, this consideration tends to outweigh the fee saving permanently.
Twice a month
Most of the fee saving, half the concentration, and a gap short enough for most people to carry.
It also suits payers, whose runs are frequently twice-monthly anyway.
Batching across clients
Not available. Several payers each send separately and no arrangement at your end combines them.
Where one payer dominates, the conversation is worth having with them. Where income is spread thinly, the lever is the route rather than the frequency.
Expenses and small items
The clearest case. Rolling reimbursements and small items into the next regular payment costs the payer nothing and removes a category of transfer where fees are a large share.
Ask for this specifically. It is almost always agreed.
It also simplifies their bookkeeping, since one payment against two invoices is less work than two payments. That is worth saying when asking, because it makes the request sound like a favour rather than a demand.
Agreeing a minimum transfer size
A term saying amounts below a stated figure are carried to the next payment. One line, and it prevents the twenty-unit transfer that costs eight units to make.
Set the floor from your own measured flat cost.
The first large payment
Disproportionately likely to be held for review, because it is unusual for the account. Expect it when moving from frequent small payments to infrequent large ones.
Telling your bank in advance sometimes prevents it and never hurts.
Buffer requirements
A monthly arrangement needs a larger buffer than a weekly one, both for the ordinary gap and for the month something goes wrong.
Changing frequency without changing the buffer is how a sensible saving becomes an uncomfortable quarter.
Revisiting it
As the amounts grow, the flat cost matters less and the concentration matters more. An arrangement that was right at one scale is often wrong at another.
Look at it once a year rather than treating it as settled.
The review is two questions: has the flat cost changed, and has the amount grown enough that concentration now matters more than fees. Both are answered from the record you already keep.
What batching cannot improve
The proportion taken by conversion. A year's income converted in twelve lumps and in fifty-two loses the same percentage to the margin, because the margin is a percentage.
Batching is a tool for one of the two cost shapes and does nothing for the other. Anybody whose cost is mostly margin rather than fees should leave the frequency alone and spend the effort on who converts instead.
Which is why anybody whose income arrives through a low-fee service should not spend any time on this note at all, and anybody paid weekly through a bank should read it twice.