Which currencies does it handle?

Every currency your companies book in, held as the local amount plus the rate it was translated at rather than as a euro figure with its history thrown away. The rate source is yours, and the group reports in whichever currency it reports in.

Which rate does a conversion use?

The rate published for the day the cash actually moved, from your own rate source. Not a month-end average, and not the day somebody happened to run the report. Every converted figure keeps the pair and the rate beside it, so the local amount can be recovered exactly.

What happens when a pair has no published rate?

That row has no group figure. The currency is named on the surface, the local amount stays exact, the total states how many of how many currencies it covers, and nothing downstream silently inherits a number we invented. We do not interpolate, carry forward or triangulate.

Do local bank holidays affect the position?

Yes, and that is why they are held. Banking calendars and cut-offs are kept per country and per company, so a value date that moves because of a closed day somewhere else appears as a date rather than as an unexplained difference at the end of the week.

Can our companies in different countries all read the same figures?

Yes. One reconciled position, read in English or in Spanish and written the way each language writes numbers. A shared service center and a local finance team are pointing at the same row, so a disagreement is about the figure rather than about which file is current.

Multi-country operations

A cross-border position is not one moment. It is four, and every figure says which.

Different countries mean different cut-offs, different banking calendars, different currencies and different local conventions about when money is actually yours. Tresora holds all four of those as data rather than as folklore, so a group figure carries the instant it was read at and the rate it was translated at — and where a rate does not exist, it carries no figure.

Request a demo

Value date monitoring · one instruction

MXN → EUR

Value date

Aug 14, 2026

Released by the Mexican company, received by the Spanish one

Released · Mexico City: Aug 12, 2026, 15:10 GMT-6
Cut-off that day · Mexico City: Aug 12, 2026, 17:30 GMT-6
The same instant · Madrid: Aug 12, 2026, 23:10 GMT+2
Cut-off that day · Madrid: Aug 12, 2026, 18:00 GMT+2
The day after · Madrid Aug 13, 2026: Closed

InstructionPAY-20260812-0147

What crosses the border

What actually changes from one country to the next?

Four things, and none of them is the language. Each one moves a real figure, and each one is held as data per country and per company rather than as something the person building the file happens to know.

The clock: A cut-off is local, so one instant is comfortably inside it in one country and hours past it in another. A position stated as of today is as many moments as you have countries, until somebody names the one it was read at.
The calendar: Banking days are national. A day that is closed where the money lands moves the value date for a company that was open, paid on time and did nothing wrong.
The currency: Each company books in the currency it actually uses and the group figure is built on top. The rate that belongs to a movement is the one published for the day the cash moved, never a month-end average applied backward.
The banking convention: What a statement carries, what a value date means and how a payment is authorized all differ by country. Where a country’s banks want their own channel, that is a format and an authorization to arrange, and the same reconciled picture comes out the other side.

Held as data, those four stop being surprises. A cut-off that has moved is a fact on the calendar rather than a phone call, and a value date two days out is a date somebody can see coming.

When there is no rate

What happens when a currency has no published rate that day?

There is no group figure for that line. Not a zero, not a dash, not the last rate we hold and not a rate assembled out of two others: the currency is named on the surface, the row keeps its exact local amount, and the total states how many of how many currencies it covers.

Value date monitoring · by currency

VALUE DATE

Settling on Aug 14, 2026Rates taken Aug 14, 2026, 08:00 GMT+2

Currency	Rate	Local	Group (EUR)
EUR Base currencyEUR 684,600.00	Base currency	EUR 684,600.00	EUR 684,600.00
USD 1.1690 USD/EURUSD 412,150.00	1.1690 USD/EUR	USD 412,150.00	EUR 352,566.30
MXN 19.5313 MXN/EURMXN 5,480,000.00	19.5313 MXN/EUR	MXN 5,480,000.00	EUR 280,575.28
DOP 64.5164 DOP/EURDOP 3,905,400.00	64.5164 DOP/EUR	DOP 3,905,400.00	EUR 60,533.45
CUP No rateCUP 1,164,000.00	No rate	CUP 1,164,000.00	No figure

Settling on the value date · 4 of 5 currenciesEUR 1,378,275.03

No published rate for CUP on this value date. That row is left out of the total above and out of everything that chains from it. We do not carry an older rate forward, interpolate one, or triangulate through a third currency — a figure converted at a rate that does not exist is one your auditor cannot reproduce, and the local amount beside it is still exact.

A missing rate is a fact about the market on that date rather than a defect in the data, and treating it as a defect is how a wrong figure gets published with nobody’s name on it. The gap is smaller than the trust it costs to paper over.

What we will not do

We will not convert at a rate that was never published for that date. Nothing is interpolated, nothing is carried forward from the last day that had one, and nothing is triangulated through a third currency to close the gap. Where the market gave no rate, the answer is the local amount and the name of the currency — and what to do about it is your treasury’s call.

What answers it

Which parts of the product cross the border?

Four, and they run in this order: what the local bank sends, what it becomes, what it is worth to the group, and what leaves again.

However each country’s banks send: SWIFT, EBICS, host-to-host, API and local channels, carrying MT940, CAMT.053, BAI2 or CSB43. A country whose banks want their own channel is an authorization and a format, and if one of your banks sends something that is not here yet, we add it.
The position, with its moment on it: One stamp for the whole screen, carrying the zone it was read in, and the local amount kept beside every group figure. A position translated at four different moments is not a position, so it is never presented as one.
Rates as data, with their source: Every conversion keeps the pair, the rate and the day it was published for, so any group figure can be taken back to the local amount it came from. A rate that does not exist is stored as not existing.
Payments out, on your approval path: Instructions leave through each country’s own channel, in the format that country’s banks accept, and nothing reaches a bank without the approvals you require. The funds stay in your own accounts throughout.

The modules this page is about

The first working morning

What is actually different on Monday?

Four things, and all four are arguments your team stops having.

One position, one stated momentNobody asks whether the Mexican figure is yesterday’s. The screen carries the instant it was read at, with the zone, and every figure on it came from that instant.
Value dates you can see comingCut-offs and banking calendars are held per country, so an instruction released after a receiving country’s cut-off says so as it is released rather than two days later.
Rates stop being an argumentEvery converted figure shows the pair and the rate behind it, so a controller who disagrees with a group total goes to the line rather than to the person who built it.
A currency with no rate is visibleIt is named on the surface with its exact local amount, so your treasurer decides what to do about it instead of finding out at the close that something was quietly included.

Where to go next

Questions

What multi-country groups ask first

01Which currencies does it handle?: Every currency your companies book in, held as the local amount plus the rate it was translated at rather than as a euro figure with its history thrown away. The rate source is yours, and the group reports in whichever currency it reports in.
02Which rate does a conversion use?: The rate published for the day the cash actually moved, from your own rate source. Not a month-end average, and not the day somebody happened to run the report. Every converted figure keeps the pair and the rate beside it, so the local amount can be recovered exactly.
03What happens when a pair has no published rate?: That row has no group figure. The currency is named on the surface, the local amount stays exact, the total states how many of how many currencies it covers, and nothing downstream silently inherits a number we invented. We do not interpolate, carry forward or triangulate.
04Do local bank holidays affect the position?: Yes, and that is why they are held. Banking calendars and cut-offs are kept per country and per company, so a value date that moves because of a closed day somewhere else appears as a date rather than as an unexplained difference at the end of the week.
05Can our companies in different countries all read the same figures?: Yes. One reconciled position, read in English or in Spanish and written the way each language writes numbers. A shared service center and a local finance team are pointing at the same row, so a disagreement is about the figure rather than about which file is current.

Bring one week that crossed a border.

Statements from two countries and the payments that ran between them, and we will show you the value dates, the rate each figure was translated at, and any currency we would decline to convert.

Request a demo See every solution

Your rate source and your approval path, unchanged. Nothing reaches a bank in a working session unless you ask for it.