Bank Feed or CSV Import for Household Spending?

A bank feed suits an ongoing transaction record. A CSV import suits a deliberate snapshot that you choose and upload yourself.

The better option depends on how often you want to update the record, how much control you need over the date range and whether you are comfortable keeping a bank connection active. Neither route removes the need to check what arrived.

Choose one source for an account at a time. Mixing a feed and overlapping files is where duplicates and uncertain matches begin.

Use a bank feed for a continuing record

A connected feed is useful when you want new booked transactions to arrive regularly without exporting another file each time. It reduces the repeated work of visiting the bank, choosing a period, downloading a file and uploading it.

That convenience changes the job. With a file, you inspect the source before import. With a feed, you inspect the connection, its last successful refresh and the transactions that were returned.

A feed makes sense when:

the account is used often;
you review transactions throughout the month;
the available bank and account are supported;
everyone affected understands whether the Billum account is personal or shared; and
you are willing to maintain and, when needed, renew the connection.

Do not treat “connected” as “fully reconciled”. A bank can return less history than requested. A transaction description can still be unclear. Pending payments can later book with a different date or wording. A refresh can also need your attention when it resembles a transaction already imported from a file.

Use a CSV for a bounded piece of work

A CSV import is the clearer option when you want one account and one exact period, then no continuing connection.

It works well for a one-off household review, an older statement period or an account you do not want to keep connected. You choose the export. You can inspect the rows before upload. You also have a stable source file to compare with the imported result.

Choose a file when:

you need a specific historic period;
occasional updates are enough;
the bank or account is not available through the feed;
you want to approve each upload separately; or
the connection is unavailable and the supported export format gives you a reliable alternative.

The trade-off is manual control. You must choose the right account and dates, keep the original export, review the preview and avoid importing the same period twice. The safe CSV import checklist covers that process in detail.

Compare control, effort and coverage

The difference is not simply automatic versus manual. Each route gives you a different kind of control.

A bank feed controls repetition. Once the connection is set up, refreshes can bring in later booked transactions. You still decide how those transactions should be classified or linked in the household record.

A CSV controls scope before sharing. You choose the account, period and export. That can make a narrow review easier to explain, but only if the bank offers a compatible file and you check it before upload.

Both need a boundary. A personal account should not become a shared record merely because some household costs pass through it. A shared account should not make every transaction a shared expense. Choose the Billum account scope separately from the classification of each transaction.

The Information Commissioner's Office describes data minimisation as keeping personal data adequate, relevant and limited to what is needed (ICO data-minimisation guidance). For a household, the practical question is simple: which account and period are actually needed for the review?

Consent is part of the feed decision

A bank connection is not a permanent instruction that should be forgotten. Check what provider is involved, which account is connected, what information can be accessed and how to stop the connection.

In the UK, Open Banking Limited says a customer must give explicit consent to a regulated app or website and can decide what information it may access and for how long (Open Banking FAQs). Its guidance also says access can be stopped through the app or website, or through the bank.

The exact controls depend on the bank, provider and country. If a connection is no longer useful, disconnect it in the household tool and check the bank's own consent settings. Removing a link from one service does not necessarily remove the permission held at the bank.

CSV files need care too. They are portable copies of transaction data. Store the original only as long as it serves a clear purpose, keep it away from shared folders that do not need it, and remove working copies when the review is complete.

Switch sources without making a second history

Changing from files to a feed is not a clean restart. The account may already contain months of imported transactions, categories, links and splits that should be preserved.

Before connecting a feed:

Note the latest booking date covered by the file history.
Finish or undo any file import that is still uncertain.
Keep the existing records rather than deleting them to make room for the feed.
Review the first feed import for transactions that resemble the file history.
Confirm whether each uncertain pair is the same payment or two separate payments.

The reverse move also needs a boundary. Disconnect the feed first. Then choose a file whose dates do not overlap active bank-feed imports. If you need an overlapping period, review the existing bank imports before uploading another copy.

Never solve an overlap by deleting whichever row looks less familiar. First compare the booking date, amount, description and source. A retained existing transaction may already carry useful classification, links or split details.

What Billum does with each source

Billum keeps file upload and bank feeds as separate transaction sources. Both depend on Transactions being enabled for the organisation. File upload is enabled separately; bank feeds also require an administrator to configure and enable the provider.

For supported CSV files, Billum shows a preview with the detected format, row count, date range, totals, duplicates and row errors before confirmation. At publication, the validated layouts are Amex and SEB exports.

For a configured bank feed, Billum lets you authorise an available bank account, link it to a compatible personal or shared Billum account, and review booked transactions before confirming uncertain matches. The first connection can request up to one year of available history. Later refresh behaviour depends on the organisation's settings and the bank may return less than requested.

When a feed transaction clearly matches existing CSV history, Billum keeps the existing record. When the match is uncertain, it asks whether to keep the existing payment or add the bank payment as another transaction. Keeping the existing row preserves its category, links and splits.

A linked feed blocks file uploads to that account. Disconnecting the feed does not delete confirmed transactions or import history, but overlapping file periods remain guarded against duplicate records. Billum does not turn imported transactions into bills or receipts, mark them paid or decide their household meaning for you.

Make the choice explicit

Write one sentence before setup:

We need an ongoing view of booked transactions from this account, so we will use a feed and review each refresh.

Or:

We need one closed statement period, so we will import a checked file and keep no active connection.

That sentence gives the household a test for later. If the purpose changes, change the source deliberately. Do not let a convenient connection widen unnoticed, and do not let a folder of repeated exports become a second, conflicting transaction history.