Skip to main content

Connect a bank or an aggregator

Instead of uploading a statement each month, let a connection fetch it: choose the service that reaches your bank, give it read-only credentials, link each account it finds to your books, and sync. Every synced transaction waits for your review like an uploaded statement — nothing posts on its own. Where an installation keeps bank connections closed, Settings → Connections says so, and statements are uploaded instead.

All how-tos

  1. 1

    Choose the service that reaches your bank

    Under Settings → Connections, Add a bank connection opens three steps. The first, Choose the service, lists the services that can read an account for you, each with what it reaches and where it works. Mercury reads a Mercury business account through its own API token. SimpleFIN Bridge reaches most US banks and cards — Chase, Bank of America, Wells Fargo, Amex and more — for a small yearly fee you pay SimpleFIN. Wise reads every currency balance of a Wise account. Enable Banking (PSD2) reaches Bulgarian and European banks — UniCredit Bulbank, DSK, UBB, Postbank, Fibank, Revolut — through the bank's own open-banking consent. Teller and Plaid reach US banks through a developer account of your own, and only on a server install. Interactive Brokers (Flex) brings in a brokerage account's cash movements to review like a bank statement; its trades and other securities rows come in flagged, to be recorded under Investments rather than posted here. Only a workspace owner, or an administrator with edit access to banking, sees Connections.

  2. 2

    Add the connection

    Below the services, give the connection a name you will recognise — the bank and what the account is for; left empty, it takes the service's name — and choose Next. The connection is made then and listed under Bank connections, marked Not finished. A dialog closed from here on leaves it there: its row opens with Access, and its menu offers Delete.

  3. 3

    Give it read-only credentials

    The second step, Give it access, asks for exactly what that service issues, and says where to get it: an API token from Mercury or Wise, a setup token from SimpleFIN Bridge, an application ID and private key for Enable Banking, the keys of your Teller or Plaid developer account. For Plaid and Teller, the Connect button opens the service's own window to sign in to your bank, so no token has to be copied by hand. Create every token read-only, tick the promise that it grants only the access this connection needs, and choose Save access. The connection turns Active. Credentials are sealed as you save them and never shown again: the connection's row then only says they are saved, and Replace access asks for new ones; a SimpleFIN setup token is used once, so a new one is needed for each connection. For Enable Banking, once the application ID and key are saved, Connect your bank picks your country, Find banks lists the banks there, and Connect your bank opens your bank's own sign-in to give consent; you come back to Bank connections with the bank connected. The desktop edition cannot be returned to, so there you authorize the bank in Enable Banking's control panel and paste the authorization code it returned. On the desktop edition nothing leaves the machine until the service's host is allowed by name, and the form names the hosts to allow.

  4. 4

    Find the accounts

    Saving the access asks the service which accounts it can read, and the third step lists them with their name, the last digits of their number and their currency — a card and a savings account beside the checking account, and with Wise one per currency. The connection's row shows them too, under Accounts at the bank: Find accounts asks again when none were found, and Look for new accounts, later, adds one you opened since; it never duplicates one already listed.

  5. 5

    Link each account to your books

    The third step, Link the accounts, says where each one goes in your books. When the workspace keeps more than one book, choose the Book first; with one, it is not asked. Activity from, the first day the activity comes in, is chosen for you, and the line under it says why: the day after the last entry of the account it goes to (the latest of them, when several accounts are linked at once), so nothing is brought in twice; for an account with nothing in it, the start of the book's first open period, so everything since then comes in; and never earlier than the service reaches back. An earlier day can still be typed, with a word on what it risks, except one before the service reaches, which is refused; a book with no open period asks for one first. Each account offers the accounts in your books of the same currency and a fitting type — so a card goes to a credit card account and a checking account to a bank account, and the one that fits is chosen already — or New account with the bank's name, made from what the bank says with no opening balance, since the sync brings the activity in, or Skip this account. Sync automatically every day is ticked; Link and sync links them, sets the daily sync and runs the first one, and the list then says the connection is connected, with Review what came in. While the workspace does not yet sort new transactions in the background, an administrator is also offered Sort new transactions into categories in the background, ticked: Link and sync then turns that on too, so every sync's new transactions get suggested categories, scheduled ones included, and Settings → General turns it off again. Later, on the connection's row, an account left unlinked is one line — Not linked yet, then where it would go and from which day — with Link to do just that, Link all, when two or more have an offer, to link them all at once, and Skip, which folds it into accounts set aside, where Show lists it and Link… brings it back. The third step's Skip this account sets an account aside the same way. Change… opens the same choices as the third step: the Account in your books, Create “…” and link with the account's name, or Change details first… for the full account form, and Activity from; when the book has no account of a fitting kind in that currency, the form says why and offers only to create one. Once linked, the row says which account it feeds, and from which day. Change link moves an account to another one from a later day; a day whose activity was already brought in cannot be brought in twice.

  6. 6

    Sync and review

    Sync now fetches each linked account's settled transactions — a pending card payment waits until it settles — from its Activity from day on the first sync and from where the last one stopped after that — Choose dates… picks other days, and Close dates goes back to those days — and says Completed, with Review what came in beside it. They arrive under Inbox → Statement imports as a statement of that account, to be reviewed, posted and balanced exactly as an uploaded one is, with categories already suggested — and when the workspace has AI switched on, a sync you start with Sync now or Link and sync, as the workspace's owner or with edit access to AI operations, also asks the AI about the merchants nothing else suggested a category for, as it does for an uploaded statement; the balance the bank reports is kept for the balance check, and when it is the bank's booked balance and a sync has read the account's activity through its day, an account whose opening balance is not known says Opening balance to review under Accounts: its page proposes the opening from that balance, and nothing is posted until you choose Establish opening balance. Syncing the same days again brings in only what is new or what the bank corrected, so a repeated sync never doubles a row, and a transaction that also arrives in an uploaded statement is shown as a possible duplicate.

  7. 7

    Let it sync automatically

    Link and sync sets a daily sync when Sync automatically every day stays ticked. On the connection's row, Automatic sync changes it: How often — every 6, 12 or 24 hours, or Manual only — Bring activity in from, the day the first automatic sync starts from, and, under Late activity, Look back for late activity, how many days each run looks back for transactions the bank posted late; Save turns on once something changed. The row says when the next sync is due, and each automatic sync that brings in something new tells you a statement is waiting; a sync more than an hour late is said too, with Sync now to bring the activity in meanwhile. On the desktop edition automatic sync runs while the app is open; on the hosted service it is not running yet, so Sync now brings the activity in. Interactive Brokers statements are synced by hand. While the workspace does not sort new transactions into categories in the background, an administrator sees Scheduled syncs are not sorted into categories above the connections, with Turn on background categorization.

  8. 8

    When the bank asks again

    An open-banking consent lasts 90 to 180 days: a week before it ends you are notified that the connection needs attention, and choosing Connect your bank again renews it without losing anything. A token revoked or expired, or a consent left to run out, stops the connection: its row says Needs new access and opens by itself, automatic syncs stop, and you are notified. Create new credentials with the service and save them under Access — for Enable Banking, connect your bank again — and the connection is Active again and the next sync catches up from where it stopped. The row's menu, Actions for the connection, holds the rest: Pause stops a connection for a while, Disable until you Activate it again, and Delete, which asks first, for good — what it already brought in stays in your books. A disabled connection is listed last, under Show disabled connections.