Audience: LedgerMind Premium customers who have been enabled for the Akahu Personal Token integration. Time required: 15–25 minutes (one-time setup). What you will achieve: A secure, automatic daily sync of your New Zealand bank transactions into LedgerMind — no more CSV exports.
Akahu is a New Zealand open-banking platform that lets approved applications read your bank transactions on your behalf — with your explicit consent and without ever seeing your banking password.
When you complete this guide, LedgerMind will be able to:
Important — Beta scope: During the beta, synced data is stored in a separate, read-only area inside LedgerMind. It does not automatically replace transactions you have imported via CSV. You can continue using both methods in parallel for reconciliation. A future release will let you "promote" synced transactions into your main ledger with automatic deduplication.
Have the following ready before you begin:
📌 Note for accountants: If you manage multiple entities (e.g. personal and company accounts), repeat this guide for each LedgerMind account separately. Each Akahu account is tied to one email.
Akahu uses passwordless sign-in. Instead of choosing a password, you enter your email and Akahu emails you a short verification code each time you log in.
🖼️ [SCREENSHOT #1] — Akahu sign-in page at my.akahu.nz with the email field visible.
🖼️ [SCREENSHOT #2] — The email-code entry screen showing the 6-digit code input (blur the actual code).
🖼️ [SCREENSHOT #3] — Akahu dashboard / home screen immediately after first sign-in.
💡 Tip: The code is valid for a short window only (usually 10 minutes). If it expires, just click Resend to get a new one.
Before Akahu lets you create a Personal App, it requires a one-time identity check (handled by GBG Cloudcheck, a regulated NZ identity-verification provider). You only need to complete this once.
🖼️ [SCREENSHOT #4] — Akahu's left sidebar with the "Developers" menu item highlighted (matches the screenshot showing Apps / Payments / Logs / Profile / Developers / Logout).
When you open Developers for the first time, you will see a Verify Your Identity gate screen explaining that Akahu requires identity verification and 2FA setup before you can create a Personal App.
🖼️ [SCREENSHOT #5] — Akahu's "Verify Your Identity" gate screen with the Continue button (text: "To enhance security, we require identity verification and 2FA setup before creating a personal app.").
Clicking Continue opens a secure page hosted at
akahu.cloudcheck.co.nz (GBG's identity-verification service). You will
need to provide:
123).
- ☐ NZ Passport — you will then be asked for your passport
number and expiry date.GBG will check your details against the relevant NZ government database (NZTA for driver's licences, DIA for passports). Verification usually completes within a few seconds.
🖼️ [SCREENSHOT #6] — The GBG Cloudcheck form (name / DOB / NZ Driver's Licence / NZ Passport options and consent checkbox). Blur or redact any personal information before sharing.
🖼️ [SCREENSHOT #7] — The "Verification successful" confirmation screen returned by Akahu after GBG completes the check.
❗ If verification fails: - Double-check that the name you entered matches the document character-for-character (including middle names). - Confirm the licence version number (it changes every time you renew your licence). - If it still fails, try the alternative document (passport instead of licence, or vice-versa). - As a last resort, contact Akahu support at support@akahu.nz.
🔐 Privacy note: GBG only confirms a match / no-match result. Your ID details are not stored in LedgerMind, and Akahu only retains the verification outcome — not your licence or passport number.
After identity verification succeeds, Akahu will guide you straight into the 2FA setup (Step 3 below). If for any reason you need to start 2FA manually later, return to Developers and you'll see the prompt again.
Akahu requires two-factor authentication before you can create a Personal App. This is a one-time setup per device.
If you do not already have one, install Google Authenticator, Microsoft Authenticator, or Authy on your phone from the App Store or Google Play.
After identity verification succeeds (Step 2), Akahu will display the Set up two-factor authentication screen automatically. If you closed the tab, go back to https://my.akahu.nz → sidebar → Developers, and you'll be prompted again.
🖼️ [SCREENSHOT #8] — Akahu's "Set up two-factor authentication" intro screen with the Enable button.
🖼️ [SCREENSHOT #9] — The QR-code screen Akahu displays during 2FA setup. Blur or replace the QR code* before sharing this
🖼️ [SCREENSHOT #10] — Akahu's "MFA successfully enabled" / recovery-codes screen. Blur the actual recovery codes before sharing.
⚠️ Do not skip the recovery codes step. Without them, losing your phone means losing access to your Akahu account permanently.
From now on, every time you sign in to Akahu you'll first enter the email code (Step 1) and then a fresh 6-digit code from your authenticator app.
Good news — your Personal App was created automatically when you finished identity verification + 2FA. You do not need to fill in any "Create a new app" form.
https://api.akahu.io/v1 (informational only)
- App ID Token: already populated, e.g.
app_token_cmpg7t0rl000102l576b6ekg3
- User Access Token: shows the placeholder text
"Add accounts to generate a User Access token"
- IP Address Ranges: 0.0.0.0/0 (leave as-is)🖼️ [SCREENSHOT #11] — Akahu Developers page showing the Configuration card with App ID Token populated and the User Access Token field saying "Add accounts to generate a User Access token", and the Accounts card saying "No accounts connected" with an "Add" link.
💡 Why is the User Access Token empty? Akahu only issues a User Access Token once you connect at least one bank account to the Personal App. That's what the next step does.
🔐 Treat both tokens like passwords. Anyone with both tokens can read your bank transactions through Akahu (they cannot move money, but they can see everything). Do not share them in email, chat, or screenshots without blurring.
We will use Kiwibank as the example. The flow is similar for other banks (ANZ, ASB, BNZ, Westpac, TSB, etc.) — only the bank-login screens in the middle will look different.
On the Developers page, find the Accounts card:
🖼️ [SCREENSHOT #12] — The Accounts card on the Developers page, showing either "No accounts connected" with an Add link, or an existing connection (e.g. Westpac "Choices Everyday") with a Manage link in the top-right.
Akahu will open a consent screen titled "\<Your name>'s Personal App is requesting ongoing access", listing what the app will be allowed to read:
🖼️ [SCREENSHOT #13] — Akahu's "Personal App is requesting ongoing access" consent screen with the Continue button.
Next you will see a screen titled "You're sharing the following connection with \<Your name>'s Personal App".
Click + Add another connection.
🖼️ [SCREENSHOT #14] — The "You're sharing the following connection with Personal App" screen, with the + Add another connection and Save connections buttons visible.
Akahu will show a grid titled "Select your provider" with all supported banks (ANZ, ASB, AMEX, BNZ, Booster, Demo Bank, Fisher Funds, Generate, Hatch, Heartland, Inland Revenue, Kernel Wealth, Kiwibank, Latitude, Milford, NZHL, and more — scroll if your bank is not visible).
Click your bank's logo — in this example, Kiwibank.
🖼️ [SCREENSHOT #15] — Akahu's "Select your provider" grid with the Kiwibank tile highlighted.
For Kiwibank, Akahu will show a "Connecting your Kiwibank accounts" information page explaining what you will need:
Read the page and click Continue when ready.
🖼️ [SCREENSHOT #16] — Akahu's "Connecting your Kiwibank accounts" pre-flight info screen with Continue button.
A page titled "Enter your Kiwibank credentials" appears.
🖼️ [SCREENSHOT #17] — Kiwibank credentials page (Access Number + Password + Submit). Blur both fields before sharing.
🔐 Security note: Akahu uses a screen-scraping connection for Kiwibank because Kiwibank does not yet provide an Open Banking API. Your credentials are submitted directly to Kiwibank and are not stored by Akahu or LedgerMind.
Kiwibank will prompt you with a Keepsafe challenge — it shows the name of one of your Keepsafe questions and asks you to enter specific letters of the answer (e.g. letter 2, letter 3 of a 5-letter answer).
🖼️ [SCREENSHOT #18] — Kiwibank Keepsafe challenge screen with the letter boxes and Continue button (blur the question name).
Kiwibank will text a one-time verification code to your registered mobile number.
🖼️ [SCREENSHOT #19] — Kiwibank "Verification Code" entry screen with Continue button (blur the partial mobile number).
Once Kiwibank has authenticated you, Akahu shows a list of your accounts under "Connect your accounts — Select the accounts you'd like to connect to \<Your name>'s Personal App".
🖼️ [SCREENSHOT #20] — Akahu's "Connect your accounts" screen showing your Kiwibank accounts with tick-boxes and the Connect accounts button.
💡 Tip: Only connect accounts you genuinely want imported into LedgerMind. You can come back later and tick more accounts — just repeat the Manage flow.
You will see a "Final step" confirmation page with a green checkmark: "Your Kiwibank accounts are ready to be connected to \<Your name>'s Personal App."
🖼️ [SCREENSHOT #21] — Akahu's "Final step" green-checkmark screen with Continue button.
💡 Connecting multiple banks: To also connect, say, Westpac, click + Add another connection and repeat steps 5.4 – 5.10. Each bank will have a slightly different login flow. LedgerMind groups transactions by bank automatically.
Now return to Developers (sidebar → Developers). The Configuration card will look different from before:
user_token_.... Click Show to reveal it.To copy each token:
🖼️ [SCREENSHOT #22] — Akahu Developers page after connecting a bank — Configuration card showing both App ID Token and User Access Token populated (highlighted), and Accounts card listing the newly-connected account (e.g. Free Up under Kiwibank). Blur most of each token value before sharing.

You now have both tokens on your clipboard, ready to paste into LedgerMind.
🖼️ [SCREENSHOT #23] — The LedgerMind Settings page showing the "Akahu Personal Tokens (Beta)" card before any tokens have been entered. 6. Paste your App ID Token into the App Token field. 7. Paste your User Access Token into the User Token field. 8. Click Connect.
🖼️ [SCREENSHOT #24] — The same card with the two tokens pasted in (blur the actual tokens), cursor hovering over "Connect".
If the tokens are valid, LedgerMind will:
🖼️ [SCREENSHOT #25] — The Akahu Personal Tokens card immediately after a successful connection — showing Connected timestamp, Accounts count, and Banks list (like the example in the screenshot showing "1 / Westpac").

❗ If you see an error ("Invalid token" or "Akahu rejected the credentials"), double-check that you copied the entire token (they are long — easy to miss the last character) and that you pasted them into the correct field. Then try Connect again.
Tokens stored — now pull your bank data.
Sync complete N account(s), M new of M transaction(s) across K bank(s).
🖼️ [SCREENSHOT #26] — The "Sync complete" toast notification in the bottom-right corner of the screen (like the example showing "1 account(s), 653 new of 653 transaction(s) across 1 bank(s)").
The first sync usually returns all transactions of the last 24 months. Subsequent syncs only pull new transactions since the last sync, so they are very fast.
LedgerMind now has a dedicated read-only page for browsing what Akahu returned.
🖼️ [SCREENSHOT #27] — Full Akahu Sync page with KPIs, Accounts table, filters, and Transactions table populated.
| Task | Where in LedgerMind |
|---|---|
| Pull latest transactions | Akahu Sync → Sync Now (or Settings → Akahu Personal Tokens → Sync Now) |
| Reconcile against a CSV import | Compare the Akahu Sync page side-by-side with the main Bank Import page |
| Export for your accountant | Akahu Sync → Export CSV (after applying filters) |
| Add another bank | Go back to Akahu → Connections → Add new connection. The next Sync Now in LedgerMind will pick up the new accounts automatically — no need to re-enter tokens. |
| Disconnect | Settings → Akahu Personal Tokens → Disconnect — this removes the encrypted tokens from LedgerMind. Your synced history stays unless you tick "purge data". |
💡 Recommended cadence: Run a sync once a week (e.g. every Monday morning) during GST periods, and every day during the week before a return is filed.
LedgerMind takes the safety of your banking data seriously:
Q: Does this replace my CSV imports? A: Not during the beta. The two paths run side-by-side so you can reconcile. A future release will give you a "Promote to main ledger" button with automatic de-duplication.
Q: Will my transactions be duplicated?
A: No. Akahu-synced data is stored in dedicated tables and is not
inserted into your main transactions ledger automatically. Your GST,
income tax, and reports still come from your CSV-imported / manually
entered data until you decide to merge.
Q: How often does Akahu pull from my bank? A: Akahu refreshes data on its own schedule (typically daily). When you press Sync Now, LedgerMind asks Akahu for whatever is current on Akahu's side at that moment.
Q: Can I use the same Akahu account for multiple LedgerMind accounts? A: Technically yes — but each Akahu Personal App's User Token is one "identity". For clean separation between entities, create separate Akahu accounts (one per entity) and a Personal App in each.
Q: How long are the tokens valid? A: Akahu User Tokens are long-lived but you can revoke them at any time. If you ever rotate them (re-issue from the developer page), simply Disconnect in LedgerMind and paste the new pair.
Q: What does Akahu cost me? A: Personal apps are free for personal use under Akahu's policy. There is no additional charge from LedgerMind on top of your Premium plan.
Q: Which banks are supported? A: All major NZ retail banks Akahu supports today — Kiwibank, ANZ, ASB, BNZ, Westpac, TSB, Heartland, Co-operative Bank, Rabobank, and others. See Akahu's site for the live list.
We'd love to hear from you — your feedback shapes how we graduate this beta into a flagship feature.