Last Updated: November 5, 2026
Quick Summary
Import frequency is the schedule that controls how often your software pulls new transactions from a bank account, and the four common options are daily, weekly, monthly and on-demand. Match the cadence to each account's transaction volume rather than setting everything to daily, and reconcile as often as you import or slightly less.
- Daily imports suit high-volume accounts but cause authorisation refresh fatigue and more review clicks.
- Weekly imports handle moderate activity, though a missed run pushes two weeks into one batch.
- Monthly imports keep admin low for quiet accounts but delay error detection until month-end.
- Schedule automated runs one working day after the period you want to capture.
- Set the import time after your bank's daily cut-off and use the bank's local time zone.
Why Import Frequency Decides Whether Your Books Are Right
The gap between a correct set of books and a wrong one often comes down to a single setting: bank transaction import frequency options. Get the schedule wrong and you either drown in stale data or burn hours refreshing accounts that barely move.
Here is the core tension most guides ignore. A daily bank feed feels responsible. It is also pointless for an account that sees four transactions a month.
Import frequency is the schedule that controls how often your software pulls new transactions from a bank account. It sets how fresh your transaction data is, and how much manual cleanup you face at month-end.
The Import Frequency Options Compared
Bank feeds commonly offer four practical cadences: daily, weekly, monthly, and on-demand. The labels look simple, but each one behaves differently once it meets a real bank's cut-off time, consent expiry and review queue. The comparison below sets out what each schedule does to your data, your admin and your risk of duplicates.
Daily, Weekly, Monthly and On-Demand
- Daily: The feed pulls new transactions once a day, usually overnight. Best for busy current accounts and anything feeding live reporting. Each run produces a small batch, so review is quick, but the bank authorisation is exercised far more often.
- Weekly: A single weekly pull, often scheduled for a quiet morning. A reasonable middle ground for moderate activity, and the batch is still small enough to review in one sitting.
- Monthly: One pull per month, usually timed a few days after month-end so late postings are captured. Suits quiet accounts and simple books, but concentrates the work and delays error detection.
- On-demand: You trigger the import yourself, either from the software or by uploading a file. Maximum control and minimum automation, but the schedule is only as reliable as your memory.
What Each Option Costs You in Time and Accuracy
Daily imports give you the freshest transaction data and the smallest batches to review. The trade-off is more frequent bank authorisation refreshes and more entries landing in your review queue.
Weekly sits between the two. You review in manageable chunks without daily noise, and a missed week is easy to catch up. Monthly keeps admin low but concentrates the work, so errors surface late and a single failed run can leave a whole period unimported.
| Frequency | Best For | Freshness | Manual Effort | Main Risk |
|---|---|---|---|---|
| Daily | High-volume accounts | Highest | Low per run, frequent | Authorisation refresh fatigue; duplicate risk if re-run manually |
| Weekly | Moderate activity | Medium | Balanced | A missed run pushes two weeks into one batch |
| Monthly | Quiet accounts | Lowest | High at month-end | Late error detection; one failed run loses a period |
| On-demand | Irregular use | Varies | Depends on you | Gaps from forgotten runs; overlap when date ranges are guessed |
Two mechanical points decide most of the difference. First, every automated run depends on a valid bank consent, and consents expire on their own schedule, a daily cadence surfaces an expired consent within a day, while a monthly cadence can hide it for weeks. Second, each run imports a date range, and overlapping ranges are the usual cause of duplicate transactions.
Watch out: setting every account to daily "just in case" does not improve accuracy.
Matching Bank Feed Update Frequency to Your Transaction Volume
Match your bank feed update frequency to volume, not habit.
Use this as a starting point, and adjust for how often you reconcile:
- High-volume accounts (dozens of transactions a day): daily import, reviewed every few days. The batch stays small enough to scan, and a failed run is caught within 24 hours.
- Moderate accounts (a handful a week): weekly import is usually enough. One run covers the week, and the review session stays under an hour for most practitioners.
- Low-volume accounts (a few a month): monthly import keeps admin low. Set the run a few days after month-end so late postings are included.
- Irregular or project accounts: on-demand, run when you need the data, with a fixed date range each time to avoid overlaps.
A common mistake is setting everything to daily "just in case". That floods your review queue with entries you will not touch for weeks. Match the cadence to the account and you cut noise without losing accuracy.
How to Decide When Volume Is Borderline
When an account sits between two bands, decide on three questions rather than on gut feel:
- How many lines can you review in one session without skipping? If a weekly batch already exceeds that, move to daily. If a monthly batch fits comfortably, stay monthly.
- How quickly does a wrong entry need to be caught? Accounts feeding live reporting or VAT returns need fresher data than a savings account that only moves at quarter-end.
- How often do you reconcile? Importing more often than you reconcile just moves the backlog, so align the two before changing the schedule.
Bank Processing Delays, Weekends and Bank Holidays
Frequency choices interact with the bank's own posting behaviour. Most banks post transactions in batches and do not process on weekends or bank holidays, so a Monday daily run often misses Friday's late entries and a monthly run timed on the 1st can miss the last working day of the previous month. Aligning import runs with bank posting cycles reduces avoidable checking and correction, helping save time on bookkeeping.
Watch out: if you shorten a cadence to daily but keep a monthly reconciliation, the backlog simply arrives in smaller pieces. Change the import frequency and the reconciliation rhythm together, or the mismatch will show up as duplicate and missing entries at month-end.
How Often to Reconcile Bank Accounts Alongside Your Imports
Reconcile as often as you import, or slightly less. If you import daily, reconcile weekly. If you import monthly, reconcile at month-end. The two should never drift far apart.
Keeping them aligned is one of the clearest bank reconciliation best practices: frequent, small reconciliations catch fraud and errors early, while a single giant month-end session hides them. For teams planning their cadence, our guide on how to automate bank reconciliation walks through the step-by-step workflow.
The principle is simple. Frequent imports plus frequent reconciliation equals clean books and fewer surprises. Big gaps between the two are where duplicate and missing entries pile up.
Setting Import Dates, Times and Time Zones Correctly
Set your import time after your bank's daily cut-off, and set the time zone to the bank's local zone. Get either wrong and transactions land on the wrong day.
A few practical rules:
- Import time: schedule after the bank posts the day's transactions, not before.
- Time zone: use the bank account's zone, not your head office's. A multi-country setup will have several.
- Date range: for first-time connections, choose a custom date range covering the period you need.
- Historical transactions: backfill previous-year transactions once, then let the schedule take over.
Watch out: importing before the bank's cut-off means today's transactions arrive tomorrow, which quietly shifts your transaction date and skews period reporting.
When Manual Bank Statement Import Still Makes Sense
Manual or file-based import still earns its place in a few situations. A one-off account, a bank outside your connected coverage, or a historical backfill are all fair cases for a CSV, OFX, or MT940 upload.
Manual import is also useful for:
- Previous-year transactions you need once for an audit.
- Accounts you will not connect for permission reasons.
- A quick check against a downloaded bank statement.
The catch is consistency. Manual imports depend on you, so they are easy to skip. Use them as a bridge, not a permanent habit, and move recurring accounts onto an automated feed when you can.
Fixing Missing Bank Transactions After Import
Missing bank transactions after import usually trace to one of four causes. Check these in order before assuming the feed is broken.
- Timing: the transaction posted after your last import ran. Wait for the next cycle.
- Date range: your import window does not cover the transaction date. Widen the custom date range.
- Duplicates and overlaps: a re-import created duplicate transactions that mask the real one. Check for overlaps.
- Bank authorisation: the consent expired. Reconnect the account.
Weekends and bank holidays delay posting, so a Monday import often misses Friday's late entries. Build a small buffer into your schedule and review import status before chasing anything. A quick troubleshooting pass resolves most gaps without a support ticket.
Connecting Your Banks to Zenith and Setting Your Schedule
Zenith connects 2400+ banks across 30 European countries through a PSD2 consent flow, then keeps balances and transactions up to date. You authenticate through your bank and pick the accounts to sync.
A few things that make the setup straightforward:
- Read-only access: Zenith never sees more than the transaction data you authorise. Our guide on read-only open banking security explains what that means in practice.
- Five-minute setup: the PSD2 Google Sheets bank feed walkthrough shows how quick a single account connection is.
- Real-time options: if you need fresher data, see the ways to get real-time financial data into spreadsheets.
For teams weighing daily against on-demand, the right cadence depends on the account. A high-volume current account and a quiet savings account rarely need the same schedule.
