Bank Feed Connectors

When There's No Live Connector for Your Bank

Most banks let you export a statement file from their own online banking portal — download it and import it manually into the matching journal.

Supported Formats

Importing

1. Open the bank journal → Import.
2. Select the downloaded file.
3. For CSV/spreadsheet formats, map each column once — the mapping is remembered for future imports of the same format.
4. Review the preview and confirm.

Reconciliation afterward works identically whether transactions arrived via a live feed or a file import.

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.

From Bank Journal to Live Feed

Connecting

1. Open the relevant Bank Journal (Accounting > Configuration > Journals).
2. Click Connect (or Add a Bank Account if setting up fresh) and choose your provider.
3. 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.
4. 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.