Bank Integrations

Without a bank connection, the loop costs you two trips to e-banking: download a statement file and upload it here, then export a payment file and hand it back to your bank. It works, and plenty of businesses run that way — see CAMT Import and Bank Payments.

Connect a provider and both trips disappear. But the reason worth connecting is quieter than “no more files”:

You find out when a payment is rejected. Hand your bank a payment file by hand and neoo never learns what happened next. If the bank refuses a payment — a bad reference, a closed account, insufficient funds — your books say paid and the bank disagrees, and you discover it weeks later at reconciliation. Through a connection, the rejection comes back with the bank’s own reason attached to the payment, and you see it the next time you open the page.

You’ll find this under Integrations → Bank Integrations (requires the integrations permission).

Which provider does what#

All four import transactions and send payments. The differences that matter in practice:

Konfipay is a gateway to the bank you already have: it delivers the same ISO 20022 payment file your bank accepts today, and brings your statements back the same way — you just never touch the file. It’s also the only connection that supports batch booking (one collective debit and a single e-banking authorisation for the whole file) and the only one where you can choose who covers the transfer fees on cross-border payments.

Amnis, Revolut and Wise connect their own multi-currency business accounts, and all three are self-service. If you already hold an account with one of them, connecting it takes minutes. Wise has one honest difference: for European accounts, Wise’s own rules require that money movements are confirmed in Wise itself — so payments are prepared here and get a final approval in your Wise app, much like authorising a payment file in e-banking.

Connecting#

Amnis#

Create API credentials in your Amnis account, then enter them on the Amnis card:

Save Connection checks the credentials against Amnis straight away — if they’re wrong, you’re told now rather than at your first payment run. Once connected, the card shows a Connected badge and offers View Accounts, Import Transactions, Update Credentials and Disconnect.

Konfipay#

Contact Support and we’ll connect Konfipay for your dataset and link your bank accounts. There’s nothing to enter on your side — the card tells you as much until it’s done.

Once it’s connected, the card gives you a date range and Import Transactions. To add or change a linked account later, contact Support again.

Revolut#

Revolut takes the longest, because Revolut requires a certificate as well as the usual sign-in. It’s a one-time job. The card walks you through it and shows three readiness ticks along the way — certificate, client ID, and the return address — so you can always see what’s still outstanding.

1. Generate certificate on the card. neoo creates the keypair and keeps the private half encrypted; it never leaves the system.
2. Download .cer and upload that file to Revolut, under Settings → API in your Revolut Business account.
3. While you’re there, paste in the Redirect URI shown on the card, and enable the READ, WRITE and PAY scopes.
4. Revolut gives you a Client ID. Paste it back on the card and save it.
5. Connect with Revolut sends you to Revolut to confirm, and returns you here connected.

Regenerate replaces the certificate with a new one. It disconnects the current connection and you’ll need to upload the new certificate to Revolut — so only do it when the certificate is expiring or you believe it’s compromised. The expiry date is shown on the card.

Wise#

In your Wise business account, create an API token under Settings → API tokens — choose Full access if you want to send payments, read-only is enough for imports alone. Paste it on the Wise card and Save Connection; the token is checked against Wise straight away, and the card confirms which Wise business profile it connected.

Once connected, the card offers View Balances, Import Transactions, Update Credentials and Disconnect. Each currency balance in your Wise account links to its own bank account in your dataset (see below).

Linking your accounts#

A connection on its own doesn’t move anything. Each account at the provider has to be pointed at the matching bank account in your dataset, so imports and payments land in the right ledger.

Open View Accounts on the connected card (View Balances on the Wise card — there, each row is one currency balance) and set Linked Account on each row. Clearing the selection unlinks it again. (For Konfipay, Support does this for you.)

Two things worth knowing:

• A bank account can only be linked to one provider. You can’t have the same ledger account served by both Amnis and Konfipay.
• An unlinked account is silently skipped. Only Revolut says so outright; an Amnis import with nothing linked simply reports that it imported nothing and looks like it worked. If an import comes back empty, check the links first.

Revolut also needs a Transition Account set under Defaults → Accounting before it will import.

Day to day#

Transactions coming in#

Once connected, transactions are pulled in for you and land in Bank Transactions, matched against your open invoices exactly as an uploaded statement would be. There’s no CAMT file to fetch.

You can also import on demand from the provider card — pick a start date (Konfipay and Revolut also take an optional end date) and click Import Transactions. That’s the tool for catching up after a gap, or pulling in history when you first connect.

Importing the same period twice is safe. Transactions already in your books are recognised and skipped, so overlapping date ranges cause no duplicates. Every import reports what it did: Imported, Skipped (already there), Matched (settled against an invoice automatically), and Transition GL (posted to your transition account to be classified later).

Payments going out#

Approved payments are sent from Bank Payments with Pay with Amnis, Upload to Konfipay, Pay with Revolut or Pay with Wise — whichever connection the selected bank account uses. The provider button only appears when the connection is live, so a missing button means the connection needs attention rather than that you’ve lost a permission.

After a Konfipay upload, a dialog shows the file’s reference and the status Konfipay reports back, refreshing itself for about half a minute. You can close it whenever you like; the payments carry on regardless.

Pay with Wise creates the selected payments as one batch in your Wise account and moves them to Uploaded — then you log in to Wise and approve and fund the whole batch with a single action, the same way you’d authorise a payment file in e-banking. Once Wise sends the money, the payments move to Completed on their own; if a transfer is cancelled in Wise instead, the payment is marked Failed so nothing silently stays open. Two Wise particulars: QR-bill payments (QR-IBAN with a QR reference) can’t go through Wise — use Konfipay or the payment file for those — and Wise’s transfer fee arrives as its own line in Bank Transactions, so your bank account reconciles to the cent.

When the bank says no#

For payments uploaded to Konfipay, the rejection can arrive after the fact: the payment gets the Failed status and stays in the Uploaded tab — it was in flight, so that’s where you’d look for it. The row carries the bank’s own rejection reason and when it was last checked, and opening the page re-checks pending uploads and tells you if any new rejections have arrived. Wise works the same way: a transfer cancelled or refunded in Wise turns its payment Failed the next time the page checks.

Amnis and Revolut tell you at the moment of sending instead: if some payments in a batch went through and others didn’t, you’re told exactly which — so you can fix and resend the failures without re-sending the whole batch and paying twice.

If a session has expired, payments will say so. Reconnect on the Integrations page for Amnis and Revolut; for Konfipay, contact Support.

Disconnecting#

Disconnect clears the stored connection. Nothing you’ve already booked is affected — imported transactions and posted payments stay exactly as they are, and the account links survive too, so reconnecting later picks up where you left off. For Revolut, your certificate and Client ID are kept, so reconnecting is a single click.