Connect payment providers and bank accounts
Connect PayPal, Mollie, Amazon Pay and bank accounts via FinTS, EBICS, XS2A or camt file – transactions arrive automatically in payment matching.
Instead of downloading every bank statement, you connect your bank accounts and payment providers to allverto once. The transactions are then fetched regularly and appear in Payment matching, where allverto assigns them to the invoices – fully automatically if you wish.
You'll find the payment providers in two places:
- in Payment matching via the Payment providers button (opens the Set up payment providers window),
- under Finance → Settings → Payment providers & bank accounts.
Before you start
- Creating, editing, pausing and deleting payment providers requires the Set up payment providers and bank access (PayPal, Mollie, Amazon Pay, FinTS, EBICS, XS2A) permission – by default the owner, Administration and Accounting.
- Fetching transactions manually and uploading camt files requires Post payments, match bank statements, send reminders and record supplier invoices.
- Anyone with View financial data can view them (list and fetch log).
Which connection is right?
| Provider | What you need |
|---|---|
| PayPal | REST app in the PayPal developer portal (client ID and secret) with the "Transaction Search" permission |
| Mollie | API key from the Mollie dashboard (test_… for test mode, live_… for real payments) |
| Amazon Pay | Public key ID and private key from Seller Central (Integration → API access keys) and the region |
| FinTS / HBCI (PIN/TAN) | Your online banking access (login name and PIN); authorisation via pushTAN/app or TAN entry |
| EBICS | An EBICS contract with your bank (EBICS URL, host ID, customer ID, user ID) – for business accounts, also for sending payment runs |
| XS2A (PSD2) | Only the authorisation in online banking – fetching runs via a licensed account information service |
| XML (camt files) | Bank statements as camt.052/053/054 from your banking software, uploaded or delivered by script |
Step by step
- Click New and choose the provider under Choose payment provider.
- Enter a Name (this is how the account appears in payment matching) and, with several companies, choose the Company – or All companies.
- Enter the access data (see table). For FinTS, the Bank code is enough – allverto fills in the FinTS address itself for known banks. For FinTS, choose the Format (camt.052 (recommended) or MT940).
- Under First fetch from, set the day from which transactions are fetched (empty = the last 30 days).
- Switch on Assign reliable suggestions automatically if transactions with a reliable suggestion (85 % or more) should be posted without confirmation. For PayPal, Mollie and Amazon Pay you can first connect the provider's test environment with Test mode.
- Save. Bank accounts (FinTS, EBICS, XS2A) are then in Setup status – open the steps for your bank via right-click → Setup (see below).
- Automatic fetching is off after creation. Open the account again and choose the interval under Fetch (Manual only, Every 30 minutes up to Daily).
Set up FinTS
- Query bank connection fetches the accounts and TAN methods from the bank.
- Choose the Account, the TAN method and – if the bank requires it – the TAN medium.
- For the first fetch, the bank requires an authorisation (pushTAN/app or TAN entry in the window). After that, automatic fetches usually run for 90 days without authorisation.
Set up EBICS
The setup guides you through four steps:
- Generate keys and send them to the bank (INI, HIA).
- Print the initialisation letter, sign it and send it to the bank.
- After activation by the bank: Fetch bank keys (HPB).
- Compare the bank key hashes with the bank's letter/portal and confirm – only if they match exactly.
Via EBICS you can also send payment runs directly to the bank (see Outgoing payments).
Set up XS2A
You give your consent in your bank's online banking. Without your login, PSD2 allows a maximum of 4 fetches per day; the authorisation expires after 180 days at the latest and must then be renewed.
XML (camt files)
With XML there is no fetching. Via right-click → Upload file / upload key you upload camt files or generate an upload key with which a script or your banking software (e.g. StarMoney, SFirm) delivers the files automatically. The key is shown only once – copy it immediately and keep it safe. Duplicate transactions are skipped.
Manage accounts
The list shows for each account the Provider, Name, Status (Setup, Active, Paused, Error), Last fetch, Transactions 30 days and the Fetch interval. Via right-click:
| Action | Effect |
|---|---|
| Fetch now | Fetches new transactions immediately |
| Setup | Steps for FinTS, EBICS, XS2A or upload for XML |
| Edit | Change name, access data, fetch and automatic assignment |
| Fetch log | Every fetch with time, trigger (Automatic, Manual, File, Connection test) and result |
| Fees… | Fee rule for this account (fixed per payment and percent of amount) – see Payment fees |
| Pause / Resume | Stop automatic fetching without deleting the access data |
| Delete | Removes access data, keys and fetch log. Transactions already fetched remain in payment matching |
You can also see the status of all fetches under Settings → Sync overview.
Frequently asked questions
The status says "Error".
Open the Fetch log – it contains the message from the bank or provider. Common reasons: expired authorisation (FinTS after about 90 days, XS2A after 180 days), a changed PIN or a revoked API key. After fixing it, fetch again with Fetch now.
Are transactions created twice if I also import files?
No. allverto recognises existing transactions and skips them.