A loan isn’t complete until it’s settled. With a single currency, settlement is mostly about timing. Add a second currency, and the question becomes: Who absorbs the difference between what was agreed and what actually happened?
Consider a situation many lending operations teams will recognise. A corporate client borrows in USD and repays in AED. The payment goes through a correspondent bank that closed its window twenty minutes before your cut-off. The FX rate on the repayment instruction doesn’t match the rate on the confirmation. By the time the mismatch is spotted, someone in operations is already trying to reconcile it by hand.
It’s not an unusual edge case. It’s the kind of thing that can happen on an ordinary Tuesday. In our work with banks across the Middle East, South Asia and Europe, we’ve seen how often the settlement process, not pricing or origination, determines whether cross-border lending is straightforward or frustrating to run.
Most banks assess lending platforms by looking at how well they book a loan. We’d suggest looking just as closely at how they settle one.
Each additional currency brings new considerations: exchange-rate movements between drawdown and repayment, different clearing cut-offs, separate holiday calendars, and often another intermediary. Each is manageable on its own. Together, they can create exceptions that consume operations time and lead to client disputes.
We group the eight checks into three layers: how the money is priced and applied, how instructions and records move, and how the whole thing is controlled.
FX rate handling
Start here, because this is where disputes often begin. Ask where the rate comes from, when it is fixed,
how spreads are applied and who can override it If the answer to that last question is “anyone with the right login,” you’ve found a control gap worth
addressing.
Payment allocation
When a repayment arrives in a different currency, the order matters. How are principal, interest and fees handled? Does conversion happen before or after allocation? A system may work well when the currencies match and struggle when they don’t. Test partial and early payments early.
Value dates and cut-offs
A business day in Dubai is not a business day everywhere. The calendar of every currency involved has to be respected by the system, not by a spreadsheet on someone’s desktop.
Messaging and standards
Automated SWIFT messaging is a baseline. ISO 20022 readiness is where we see the real gap is opening up. Structured data is only useful if the loan platform can use it without someone rekeying it.
Reconciliation
Nostro and vostro accounts should be reconciled frequently. If breaks surface only at the end of the day or the end of the week, they add both cost
and risk.
Straight-through processing
Ask for the STP rate on multi-currency settlements specifically. The overall number can make performance look better than it is. The cross-currency number tells the truth.
Compliance and reporting
Sanctions screening should be part of the settlement flow, where it can hold a payment, rather separate check that flags an issue afterwards. The same goes for audit trails on every FX decision.
Risk exposure
Can you see settlement exposure by currency and counterparty right now, without asking someone to prepare a report? If not, you may be managing yesterday’s risk.
What good and not-yet-good look like
We find it easier to judge a process by comparing it with a clear picture of both ends. Use the table below as a quick diagnostic with your team.
# | Area | Where many start | Where you want to be | Question to ask |
1 | FX handling | ▼ Typically manual | ▲ Mature | Who can change a rate, and where is it recorded? |
Rates keyed by hand, informal overrides | Defined source and timing, approved overrides, full log | |||
2 | Allocation | ▼ Typically manual | ▲ Mature | What happens to a part-payment in a second currency? |
Works only in loan currency | Correct across currencies, incl. partial and early payments | |||
3 | Value dating | ▼ Typically manual | ▲ Mature | How often do we amend value dates? |
Corrected after the fact | Calendars and cut-offs enforced by the system | |||
4 | Messaging | ▼ Typically manual | ▲ Mature | Can we consume structured ISO 20022 data today? |
Rekeyed between systems | Automated SWIFT, ISO 20022 supported | |||
5 | Reconciliation | ▼ Typically manual | ▲ Mature | How old is our oldest unmatched item? |
End-of-day or later | Automated, intraday, owned breaks | |||
6 | STP | ▼ Typically manual | ▲ Mature | What is our multi-currency STP rate? |
Not measured for cross-currency | Measured, tracked, improving | |||
7 | Compliance | ▼ Typically manual | ▲ Mature | Can screening hold a payment automatically? |
Checks sit outside the flow | Screening and audit built in | |||
8 | Risk | ▼ Typically manual | ▲ Mature | Can we see exposure by |
Periodic manual reports | Real-time exposure view |
The pitfalls we see again and again
Manual rekeying between loan, payments and treasury systems. Rounding differences that look harmless per transaction and painful in aggregate. FX confirmations that arrive after the account has already been updated. And exception handling is so informal that the customer finds the problem first. If two or more of these sound familiar, treat that as a signal, not a coincidence.
Managing multi-currency lending takes coordination across facility servicing, settlement workflows, and day-to-day operational controls.
FINEXCORE supports corporate and institutional lending across the post-disbursement lifecycle through an integrated, web-based banking environment.
Its settlement solution, SettleX, brings together key settlement-related capabilities:
FINEXCORE’s integration-oriented architecture connects with existing banking platforms, helping align lending and settlement-related workflows without requiring banks to replace their existing core banking infrastructure.
☑ FX source, fixing time and overrides are controlled and auditable
☑ Allocation works across currencies, including partial and early payments
☑ Value dates respect all relevant calendars and cut-offs
☑ SWIFT is automated and ISO 20022 is supported
☑ Nostro/vostro reconciliation is automated with clear break ownership
☑ Multi-currency STP rate is measured and improving
☑ Screening and audit trails sit inside the workflow
☑ Exposure is visible in real time by currency and counterparty
Mostly ticked: you are in good shape. A few gaps: targeted fixes will pay off quickly. Many gaps: settlement is a risk worth addressing now.
Where we land
Multi-currency settlement is not the final step in a lending transaction. It affects the client experience, risk, compliance and cost. The banks that handle it well tend to share one habit: they treat settlement as part of the lending lifecycle and evaluate it that way, from the start.
You cannot copy content of this page