Why use EBICS to connect Sage Intacct to your banks
In most companies, Sage Intacct and the bank do not talk to each other directly. Invoices are approved in the ERP, then the payment file is exported, uploaded to each bank's portal and signed, while statements travel the other way to be imported and reconciled. Every manual step adds time, risk of error and a gap in traceability.
EBICS (Electronic Banking Internet Communication Standard) is the protocol European banks use to exchange payment and statement files securely. Each user has their own keys, orders are signed electronically and the bank checks the signature before execution.
Connected natively to Sage Intacct through its APIs, Arkaio uses EBICS to set up one standardized channel with each of your banks, however many accounts you hold. It supports EBICS 2.5 and EBICS 3.0: see EBICS 2.5 vs 3.0: what changes for your treasury.
What the EBICS connection automates
Supplier payments (pain.001)
Select invoices approved in Sage Intacct, apply credit notes, prepayments and partial payments, then send the SEPA transfer to the bank.
Customer direct debits (pain.008)
SEPA CORE and B2B direct debits generated from customer invoices, with built-in mandate management.
Payment status (pain.002)
Bank status reports are retrieved after submission: a rejected batch is flagged and its invoices become available again.
Statements and reconciliation (camt)
camt.052, camt.053 and camt.054 statements retrieved automatically and matched with Sage Intacct entries.
The flow, from Sage Intacct to the bank
- Invoices are entered and approved in Sage Intacct, as they are today.
- In Arkaio, the user selects the invoices to pay; amounts are locked as soon as the batch is prepared, and a payment batch is created in Sage Intacct.
- The batch is approved and signed according to the defined workflow, then sent to the bank over EBICS.
- Arkaio tracks the submission status (pain.002) and raises an alert on rejection.
- When the statement arrives, the payment is reconciled and the entries are posted in Sage Intacct. Unmatched transactions are submitted for review.
Sage Intacct keeps showing its native statuses, so your team and your auditors find the information where they already look for it.
Security and control
VEU distributed signature
Several signatories can approve the same order without re-keying.
Workflow and permissions
Approval, signature and cancellation depend on the roles configured in Arkaio.
Dual IBAN validation
A change to a supplier IBAN in Sage Intacct triggers an approval request in Arkaio, and vice versa.
Duplicate prevention
A selected invoice leaves the list of invoices to pay, and each batch gets a unique identifier.
Audit trail
Every action is logged: who did what, and when, on each batch.
Secure access
Passkey authentication (WebAuthn) and AES-256 encryption.
Multiple banks, multiple entities
One Arkaio instance handles several banks and several Sage Intacct companies. Groups centralize payments without juggling portals; accounting firms run their clients' flows from a single tool. See Accounting firms: centralize payments for all your clients.
If a bank does not offer EBICS, Arkaio can also connect over Open Banking PSD2 or SFTP, depending on what the bank provides. See Open Banking PSD2 vs EBICS.
Setup: prerequisites and timing
- Sage Intacct: API access must be subscribed.
- Bank: an EBICS agreement is required. The subscriber is then initialized (key exchange and initialization letter) and activated by the bank.
- Arkaio: a cloud-only (SaaS) service, with nothing to install on your servers.
Configuring Arkaio is quick. For EBICS, allow a few days before going live: the timing mostly depends on activation by each bank. Arkaio is listed in the Sage catalog for Sage Intacct.
Frequently asked questions
Do we need to change banks to use EBICS?
No. Your bank needs to offer EBICS and you need the corresponding agreement. Arkaio connects to the banks you already use.
Do we have to give up our approval processes in Sage Intacct?
No. Invoice approval stays in Sage Intacct. Arkaio takes over for payment, transmission to the bank and reconciliation.
Does Arkaio read supplier invoices (OCR)?
No. Invoices must already exist in Sage Intacct.
Where can I find more answers?
The most common questions about Arkaio are gathered in the FAQ.
See Arkaio on your own flows
A demo lets you check compatibility with your banks and walk through the full flow on a case close to yours.