For a very long time, the most important problem in commerce was not moving value. It was moving it without moving the thing that represented it.
Across the Indian subcontinent, merchants used hundis: written instruments that could carry an instruction for payment from one place to another. They were used for remittance, credit and trade. The merchant did not have to load silver onto a cart simply because a debt was due in another city. A trusted instruction could travel instead.
There is a beautiful idea inside that old system. Commerce should not have to wait for capital to catch up with intention.
The Friday problem.
Imagine a finance lead at the end of a Friday. An overseas team has payroll coming due early next week. A supplier has to release a shipment. There is enough money in the group. There is no question about intent, approval or need.
The question is timing.
So the team sends early, or holds a buffer in another account, or asks someone to stay available over the weekend. In every version, the business pays for uncertainty before anything has gone wrong.
The amount may still appear on a balance sheet. But it is no longer as useful as it was yesterday.
The word for this is often pre-funding. It sounds neutral. Every pre-funded balance is a small admission that the next move cannot be trusted to happen when it should.
The business starts to orbit the payment system.
Once a team expects payment uncertainty, the behavior spreads outward. Procurement changes its release schedule. Operations asks for longer lead times. Payroll teams add buffers. Leadership keeps more cash idle than it wants to. The enterprise begins to organize itself around when a rail is awake rather than when the work is ready.
That is backwards. Money should serve the operating calendar. The operating calendar should not serve money.
This is why speed matters, but only when we define it carefully. A faster message is not enough. A faster conversion is not enough. The useful question is simpler: when can the business rely on the capital being where it needs to be, in a form it can use, with enough information to close the loop?
If there is no clear answer, the business will create a buffer. And the buffer will become an invisible tax on every plan that follows.
What a better system changes.
A better system does not ask a finance team to become less careful. It gives them fewer reasons to compensate for uncertainty.
An instruction should carry its purpose and approval with it. A rate should become a real commitment, not a number that vanishes before someone can act. Delivery should be visible. Exceptions should surface before they become inbox archaeology. And when the payment is complete, the accounting record should have enough context to be useful without another hunt for evidence.
That is not recklessness. It is confidence earned by a system that can explain itself.
Questions worth asking.
Is pre-funding always bad?
No. Some reserves are intentional risk management. The distinction is whether a balance exists because the business chose resilience, or because it cannot trust timing, visibility or delivery.
Is the issue only settlement speed?
No. The operating question includes approval, evidence, execution, local delivery, status and reconciliation. A payment that moves quickly but cannot be explained still creates work.