EBICS
Connect a business bank account directly over EBICS to import the daily camt.053 statements, without an open-banking provider in between.
EBICS is the standard German, Austrian, Swiss and French banks use to exchange files with their business customers. SaaSFlow connects to your bank's EBICS server itself, with keys it creates for you, and downloads the daily account statements (camt.053). No third-party provider sits between SaaSFlow and your bank, and nobody has to log in to online banking for the import to run.
Use EBICS when your bank offers it for your account and you want booked statements with the bank's own balances, or when an open-banking connection through Bank connections keeps expiring. Setting it up takes a signed letter to your bank, so plan for a few working days between the first step and the first import.
What you need from your bank
Ask your bank for an EBICS subscriber for SaaSFlow that can download statements and nothing else. The bank sends you a letter or email with the access data:
| In the bank's letter | In SaaSFlow |
|---|---|
EBICS URL (the server address, starts with https://) | EBICS URL |
| Host ID | Host ID |
| Kunden-ID, partner ID or customer ID | Customer ID (Kunden-ID) |
| Teilnehmer-ID or user ID | Subscriber ID (Teilnehmer-ID) |
| Hash values of the bank keys | Compared in step 3 |
The subscriber needs the right to download daily statements (camt.053, called "Kontoauszug im camt-Format" or "EOP" at most banks). Many banks charge a small monthly fee per EBICS subscriber.
SaaSFlow never sends payment orders. When your bank reports the subscriber's permissions, SaaSFlow refuses one that may sign payments (signature class E, A or B) or whose signature class the bank does not say. A transport signature (class T) can deliver a payment file to the bank but cannot authorise it. Some banks do not report permissions, so ask for a download-only subscriber ("nur Abholung") either way: a key the bank limits to reading statements cannot move money, even if someone got hold of it.
Connect
In SaaSFlow, go to Integrations, click Add integration, and pick EBICS under Banking. The setup has four steps. You can close the dialog at any point and come back to it later: the integration shows Finish setup until it is done.
Enter the access data
Fill in the bank name and the four values from the bank's letter. The bank name is only the label you see in SaaSFlow.
When you press Send keys to the bank, SaaSFlow creates a fresh set of keys for this subscriber (RSA, 3072 bit) and sends their public halves to your bank (the EBICS orders INI and HIA). The private keys never leave SaaSFlow.
Sign and send the letter
Your bank does not use the new keys until you confirm in writing that they are yours. Open the letter (German or English) and print it. It has three pages, one INI letter and two HIA letters. Sign each page with the signature your bank has on file and send all three the way your bank asked: by post, or scanned through online banking at some banks.
SaaSFlow asks your bank every morning whether it has activated the keys, and sends you a notification once it has. Check now asks right away.
Compare the bank's keys
Once the bank activated the subscriber, SaaSFlow fetches the bank's own keys and shows their hash values. Compare both with the hashes in the letter from your bank, character by character. This is what makes sure SaaSFlow talks to your bank and not to someone in between.
SaaSFlow shows the hashes of the bank's certificates, which is what EBICS 3.0 uses. Some banks print several hashes per key: a Sparkasse "Bankparameterblatt", for example, has lines for X001, X002 and Zert. Compare with the certificate lines (Zert).
If they match, tick the box and confirm. If they do not, do not confirm, and call your bank.
Choose the accounts
SaaSFlow lists the accounts the subscriber may read. Pick the ones to import and press Start import. An account that is already in SaaSFlow, for example through a bank connection, is marked: importing it a second time counts its money twice, so connect each account one way only. To move such an account to EBICS, see Switching from a bank connection.
Some banks do not list the accounts. Then SaaSFlow imports every account that appears in the statements, each as a new account.
What gets imported
| From the statement | In SaaSFlow |
|---|---|
| Each booked entry | A transaction with the counterparty, the payment reference and the booking date |
| The opening balance of the oldest statement | One opening balance row, so the running balance starts right |
| The closing balance of the newest statement | Compared with the account's balance in SaaSFlow after every import. The account is flagged when the two differ. |
| Pending and informational entries | Skipped. Only booked entries count. |
Each account is an account like any other. Its transactions go through your categorization rules and arrive uncategorized otherwise.
Before SaaSFlow imports a statement it checks that the opening balance plus the bookings equals the closing balance. A statement that does not add up stays out and the integration shows an error, so a broken file from the bank never turns into wrong numbers.
The first import
The first import asks your bank for up to 5 years of statements, newest first. The navigation bar shows the progress. If your company has a data start date set, nothing before it is imported. How far back your bank serves statements over EBICS is up to the bank: many keep less, and the import stops where the bank's history ends. Some banks only have statements from the day they set up the subscriber, so the first import can bring a few days of history and nothing older.
Switching from a bank connection
An account that already comes into SaaSFlow through a bank connection (finAPI) can usually move to EBICS with its booked history and categorizations. Write to support@saasflow.com before you import it over EBICS. We check the account and walk you through the switch: the old account stays and imports over EBICS from then on, a booking both imports have is kept once, and the balance is checked against your bank's statement before anything changes.
Staying in sync
Every morning at 06:30 (Berlin time) SaaSFlow downloads the statements your bank has ready, which are usually the ones of the previous business day. Import now in the integration's dialog does the same right away.
A statement your bank delivers twice is imported once. A statement that arrives again with different bookings stops the import of that statement and shows an error, instead of silently replacing what is already there.
When your bank changes its keys
Banks renew their keys every few years. When that happens, SaaSFlow pauses the import and sends a notification. Open it, compare the new hashes with the ones your bank sent you, and confirm. The import picks up where it stopped.
When the import stops
If your bank locks the subscriber, the integration shows an error. Ask your bank to unlock it: SaaSFlow tries again every morning, and the import picks up by itself once the bank answers again.
If your bank gives you new access data instead, delete the integration and add it again, which means a new letter. Untick "Keep accounts as manual accounts" when you delete it, so the new connection imports the history fresh rather than next to the old accounts. Your categorization rules apply to the new import, but changes you made by hand to single transactions are lost.
Disconnecting
From Integrations, open the integration menu (⋯) and choose Remove. Leave "Keep accounts as manual accounts" ticked and the accounts and their transactions stay in SaaSFlow, without the live connection. SaaSFlow deletes its keys. To block the subscriber at the bank as well, ask your bank to lock it.