Resources
How to replace bank statement uploads with automatic bank feeds in Australia
Move an Australian ledger from statement uploads to a consented bank feed. Work through the first reconciliation, catch up after a gap and decide when to keep a file.
Start with one bank account. Reconcile the last statement you uploaded, connect the feed to the same account in your books, then check where the two histories meet. Once the first feed period agrees with the bank’s records, you can retire routine uploads for that account. Keep the file option for missing history, accounts you can’t connect and cases where someone needs the bank-issued statement itself.
Choose the last day you trust
Suppose a business has imported its October statement and reconciled its operating account through 31 October. The closing balance is A$2,400. That’s the starting point for November. If someone has already entered a November payment by hand, leave it in place and match it when the feed arrives.
Do this separately for each account. Note the account, currency, closing date and reconciled balance. A CSV can stop halfway through a month, and the date someone uploaded it says little about which days it covers. Check the period against the bank’s statement before deciding where routine uploads should stop.
Connect the account the customer can actually share
In Australia, sharing banking data through the Consumer Data Right is opt-in. Explain what the app needs, who can use it, for what purpose and for how long. Show the customer where they can manage or withdraw consent. An earlier statement upload gives you no permission to start a feed. Consumer Data Right guidance on consent
With Fiskil, your app starts an Auth Session for the signed-in customer and directs them to the consent flow. They choose an available institution, authenticate with it and select the accounts to share. The institution list depends on your configuration. For a company account, check who can authorise data sharing at that bank. Someone who can download the monthly statement may still need to be appointed as a nominated representative. Fiskil linking flow · Business account permissions
Ask the customer to confirm which existing ledger account should receive each feed. Two accounts can both be called “Business Saver”. Hold an uncertain match for review before posting entries to either one.
Import the first period
Use this transaction-import recipe for the handover and each later catch-up. Start with a short overlap into the last reconciled period so you have bank records to compare.
Transaction-import recipe for a reconciled account
- Wait for the transaction dataset. Fiskil sends
banking.transactions.sync.completedwhen detailed transactions have synced. A customer returning from the consent screen can still be waiting for data. Banking sync events - Request
GET /v1/banking/transactionsfrom your backend with the customer’send_user_id, the selectedaccount_idand the agreedfromandtodatetimes. Usestatus=POSTEDfor the statement comparison. Fiskil interprets date filters using the posted time first and the execution time as a fallback. Express your local cut-off with the correct time-zone offset. Get Transactions - Read the
transactionson each page and followlinks.nextuntil there is no next page. Record your progress after processing each page so a failed request can be repeated. Use the returnedfiskil_idto recognise a feed record you have already processed for that account. Fiskil’s worked example with posted transactions · Pagination and history coverage - Match the overlap to the uploaded rows before adding entries. A file row may have no feed identifier. Compare the account, currency, direction, amount, date and reference. Two purchases at the same shop on the same day can cost the same amount. Send ambiguous pairs to review and keep a record of which source supplied each row.
Worked example. The first feed returns three posted transactions for the operating account. These figures are illustrative.
| Date | What the feed returns | What goes into the ledger |
|---|---|---|
| 30 October | A$60 paid to a supplier | The bank reference confirms the payment is already in October’s file. Match it and leave the reconciled balance alone. |
| 1 November | A$300 received from a customer | Match it to an existing receipt if there is one. Otherwise record the A$300 credit. |
| 2 November | A$45 paid for a courier | Match or record the A$45 debit once. |
If those are the only posted November movements through 2 November, the expected close is A$2,655. Compare that figure and the individual entries with the bank’s records for the same date. A balance can agree even when a missing debit and a missing credit cancel each other out. Getting to the last API page alone also leaves open whether the bank supplied the whole period.
Keep the feed current and recover a broken connection
On subsequent transaction syncs, fetch the affected account’s data and update recognised records. Your app should be able to process a repeated notification without booking the same payment twice. Keep pending activity out of the posted statement comparison. Fiskil banking guide
Give the bookkeeper a meaningful “last updated” time. Fiskil’s freshness endpoint reports on datasets such as banking.transactions. A manual refresh queues work asynchronously. While it runs, show the last confirmed update and when your ledger last reconciled. A refresh request by itself tells you neither that a new transaction has posted nor that the books balance. Data freshness · Refresh Banking Transactions
Before consent expires, you can offer renewal through a new Auth Session using the existing arrangement_id. If sharing ends, pause collection for that connection. Let the customer choose whether to reconnect. Once they do, confirm the accounts they selected, wait for transaction sync and reconcile from the last trusted date, including any files used during the gap. Fiskil consent renewal guide · Reconnecting bank feeds
When to ask for a file
| Situation | What to ask for |
|---|---|
| The account is unavailable, or the customer chooses to continue manually | Offer a supported bank export, such as a CSV your importer accepts. Check its account, dates and currency before import. |
| The feed starts later than the records you need | Request only the missing period. Compare the boundary with the first feed entries. A quiet week can be genuine, so verify the gap with the customer first. |
| Updates have paused and the books need to close | Offer a one-off file for the outstanding dates. Mark that period for an overlap check when sharing resumes. |
| A reviewer needs a bank-issued statement | Request the original statement for the specified period. A transaction export can populate a ledger, but it does not reproduce the bank-issued document. |
Implementation checklist
- Confirm the institution, account type and person authorised to share. Keep the manual route available.
- Agree the last reconciled date and balance with the person who keeps the books.
- Map each selected bank account to its existing ledger account before importing.
- Test the first import with a repeated page, a genuine duplicate-looking payment and a gap in the available history.
- Check posted entries and the closing balance for the first feed period before turning off routine uploads.
- Rehearse a paused feed, a file used during the pause and a reconnect that shares fewer accounts. Resume only the accounts the customer approved.


