Most teams do not set out to run payments across a stack of disconnected tools. It happens one rail at a time: a card provider here, a Direct Debit bureau there, a bank portal for payouts. Each works. Together they leave you reconciling by hand across systems that do not share a view, and that is the problem orchestration exists to solve.
The multi-rail reality
A lender collecting over Direct Debit, paying out over Faster Payments, taking the odd card payment and holding client money ends up with a portal for each. Every one has its own login, its own export, its own idea of what happened today. The money is moving fine. The picture is fragmented.
What the fragmentation costs
Reconciliation becomes a job of stitching exports together. There is no single view of what you are owed, what you have paid and what has failed, so questions that should take seconds take a morning. Retries live in one place, chargebacks in another, indemnity claims in a third. The reconciliation never quite closes, and the true position is always a little out of date.
The one-ledger model
The alternative is simple to state. Every inbound and outbound payment, over every rail, posts once to one reconciled ledger, carrying a structured reference and matched to the right account on arrival. The rails still do what they do; what changes is that there is a single source of truth sitting over all of them.
What that unlocks
With one ledger, positions are live rather than reconstructed. Every retry, failure, chargeback and indemnity claim is in one view. Collections and payouts reconcile against the same accounts, so a drawdown and a repayment meet in one place instead of two systems. Finance stops matching money to invoices by hand, because the matching already happened on arrival.
This is what orchestration is for
Adding rails is the easy part. The value of payments orchestration is the layer above them: routing each payment to the rail that fits, running the collection and payout rules, and posting it all to one ledger. One integration, every UK payment rail, one reconciled ledger. If you are not sure which rails you need, the comparison of the seven is the place to start.