Channels and formats
Bank connectivity that reads the file, not just receives it.
Your banks send on SWIFT, on EBICS, over a host-to-host drop and over their own APIs, in MT940, CAMT.053, BAI2 and CSB43. Tresora takes the channel each one already runs and reads every field the file carries — including the fields the standard leaves open.
The channel
How does a bank actually send its statements?
On whichever channel it already runs. SWIFT carries the MT messages, EBICS covers much of Europe, a host-to-host drop puts files on SFTP overnight, and a growing number of banks publish the same statement over an API. A file your own team exports is a fifth path, and Upload Center takes it.
Accounts
- Host-to-hostMT940 · BAI2 · CSB43
- 18
- SWIFTMT940 · MT942 · MT900/910
- 12
- EBICSCAMT.053 · CAMT.052 · CAMT.054
- 9
- Bank APICAMT.053 · MT941
- 8
Group accounts47
Authorization
A bank that sends on something not listed here gets a connector as well. The list grows the day one of your banks needs it to, and the work of adding it is ours.
Continuity
How do I know a statement never arrived?
Because a bank numbers its statements, and because each one opens on the balance the last one closed on. A file that never arrives breaks both chains at once. The break is what gets flagged, since the file itself is by definition not there to look at.
Two chains, and they are the bank’s own rather than ours. The sequence number is where a statement declares its place in the series. The closing balance is where it declares what the next one has to start from.
The account is flagged before anything is built on it, and the statement is asked for again on the channel it was due on. A position that quietly leaves an account out is worse than one that names the account it is short.
- Expected
- 47
- Arrived
- 45
- Missing
- 2
- Statement214· closing balance
- EUR 4,318,240.55
- Statement215
- not delivered
- Statement216· opening balance
- EUR 4,504,690.75
Unexplained between themEUR 186,450.20
:28C: (MT940) · LglSeqNb (CAMT.053)
What comes back
What do I get back once the file is read?
Movements, balances and the dates the bank stamped on them, in one shape, whichever of your banks sent them.
- Every column the file carries
- Not the handful a statement model has room for. A field nothing reads today is still on the record the day something does, and it is still the bank’s own bytes rather than our summary of them.
- The value date beside the booking date
- The day the money is actually yours is the date the bank stamped, not the day the line was booked. Value Date Monitoring is the screen for the accounts where those two keep disagreeing.
- A closing balance that has to add up
- Opening plus the day’s movement equals closing, per account, per day, checked against the figure the bank printed itself. Balance Analysis is where a difference stops being somebody’s hunch.
- One read, and every module has it
- The same movement is already in the position and already in reconciliation. Nothing is loaded twice, and no module works from a copy that can fall behind.
Nothing in the file is dropped on the way in. That is what makes the next module a configuration instead of a second integration.
Who reads it
Who owns the bank connection day to day?
Treasury operations open the missing-statement list before they open the position, because a position built on an incomplete day is worse than no position. A shared service center watches the same list across every entity it runs. The controller reads it at close, and wants to see that the days chain.
Written for
The files it carries
Where this goes next
Practical questions
What else do people ask before connecting a bank?
- 01Do you support SWIFT, EBICS and host-to-host?
- Yes, and a bank’s own API alongside them. The channel is your bank’s decision rather than ours: whichever one they run is the one we open with them, on the authorization they ask you for. A file your team exports and uploads is a fifth path, and it lands in the same place.
- 02What is the difference between MT940 and CAMT.053?
- They do the same job a generation apart. MT940 is a fixed-width SWIFT message whose references sit in :86:, a free-text field with no standard behind it. CAMT.053 is ISO 20022 XML and gives those same references elements of their own. Both arrive here as the same movement with the same fields resolved, so a group running one bank on each is not reading two sets of numbers.
- 03Can I see today’s movements before the end-of-day file?
- Yes. MT942 and CAMT.052 carry the day as it goes, and MT900, MT910 and CAMT.054 confirm single debits and credits as the bank books them. The position moves on those. The end-of-day statement is what closes the day rather than what starts it.
- 04Who authorizes the connection to our banks?
- You do, in the form your bank requires: a signed mandate, a certificate, an EBICS key exchange, an API consent. Tresora opens the channel on that authorization and on nothing else, and withdrawing it later leaves everything already loaded exactly where it is.
- 05Can we still upload a file ourselves?
- Yes, and plenty of teams keep doing it for one stubborn account. Upload Center takes the file, Processing Status shows what happened to it, and Rejected Rows shows any line that could not be read, with the reason and the raw record beside it. No line is silently skipped.
Start with the bank that gives you the most trouble.
Send a month of that bank’s statements, in whatever it sends them in. We will read them, chain the balances day by day, and tell you which days are not there.
Files are enough for a first look. Nothing has to be connected, and reading a file you already hold needs no authorization from anyone.