Bank Feed Connectors
This course covers automatic bank feed connectors in Quickenerp: connecting a live bank/payment provider feed (Plaid, GoCardless, Stripe, PayPal, Wise, Ponto) so transactions import automatically instead of manual file upload, plus the file-based import formats (OFX, CAMT, CSV) for banks without a live connector.
| Responsible | System |
|---|---|
| Last Update | 07/21/2026 |
| Completion Time | 1 day 12 hours |
| Members | 1 |
Bank Feeds Overview
View allFrom Bank Journal to Live Feed
Connecting
- Open the relevant Bank Journal (Accounting > Configuration > Journals).
- Click Connect (or Add a Bank Account if setting up fresh) and choose your provider.
- You'll be redirected to the provider's own secure login/consent flow (e.g. logging into your actual bank via Plaid or GoCardless's interface) — Quickenerp never sees or stores your online banking password directly.
- Select which specific account(s) to link if the provider covers several.
Pull Schedule
- Scheduled Update Interval – how often to check for new transactions (e.g. every 6 hours, once a day).
- Transactions Interval to Obtain – whether each pull fetches a day's, week's, or month's worth of activity.
- Last Successful Pull / Next Scheduled Pull are shown on the provider record so you can see at a glance whether the connection is actually running.
Manual Pull & Debugging
Trigger an immediate manual pull rather than waiting for the schedule (useful right after initial setup, or to fetch a transaction you know just posted). A debug/diagnostic wizard is available if a connection stops returning new transactions, to inspect what the provider is actually responding with.
Re-Authentication
Bank/Open Banking connections typically expire periodically (often every 90 days for regulatory reasons in Open Banking regions) and need re-consent through the provider's login flow — if a feed silently stops updating, this is the first thing to check.
Transactions That Arrive Without You Doing Anything
Instead of downloading a statement file from your bank and importing it manually (see the Accounting course's Bank Reconciliation article for that flow), a Provider connects directly to your bank or payment processor and pulls new transactions automatically on a schedule.
Supported Providers
| Provider | Typical Use |
|---|---|
| Plaid | Broad bank account aggregation, especially North American banks. |
| GoCardless (Open Banking) | European Open Banking bank connections and Direct Debit collection. |
| Ponto | Belgian/European bank account aggregation (Isabel Group). |
| Stripe | Pulls in your Stripe payment processor's own transaction/payout activity as a feed. |
| PayPal | PayPal account transaction history as a feed. |
| Wise | Multi-currency Wise account balances/transactions. |
If your bank isn't covered by a live connector, file-based import (OFX, CAMT.053, generic CSV/spreadsheet formats) still works exactly as before — see the last article in this course.
Once Transactions Arrive Automatically
Auto-pulled transactions land in the bank journal exactly like a manually-imported statement line — the daily habit doesn't change, just the manual download/upload step disappears. Go to Accounting > Bank > Reconciliation as usual (see the Accounting course's Bank Reconciliation article for the matching mechanics).
What's Different With Payment-Processor Feeds
A Stripe or PayPal feed brings in gross transaction amounts, which typically need matching against your actual invoice (net of processor fees) — the processor's own fee is usually a separate small deduction. Set up a small automated reconciliation rule for recurring processor fees so they're not manually categorised every single time.
Duplicate Prevention
If you ever also manually import a statement file covering a period a live feed already pulled, Quickenerp detects and skips transactions it recognizes as already imported (matched by the bank's own transaction reference) rather than creating duplicates — but it's still good practice not to mix both methods for the same account routinely.