How it actually works.
No metaphors on this page. Here is the machinery: where we can sign in, what happens between your click and a filed statement, what we do when a portal fights back, and what is honestly not built yet.
Where we can already sign in
51 portals are built, and a connector only graduates once it has fetched a real statement from a real account. A portal we have not proven is a portal we do not claim.
If yours is missing, tell us and we will build it. Recent ones took days, not quarters — the machinery for adding a portal is itself most of what we have built.
36 ready for anyone
Each one driven end to end by a real login before it appears here: signed in, verification answered, statements downloaded. Nothing reaches this list on the strength of an integration that ought to work.
15 in testing
Wired, reachable, and being hardened against the portals that change their login page without warning. Visible in-app to our alpha group only. We would rather show you a short honest list than a long hopeful one.
Banks are the easy half
The awkward accounts are why people move: payment processors, buy-now-pay-later, store cards, utilities, lenders, SaaS invoices. Anything that issues you a monthly document is fair game.
What we actually do
One click per account, or one button for every account across every business you own. Six things then happen in order. Anything that goes wrong — a changed password, a portal that refuses us — is named in plain language rather than buried in a retry.
We sign in
You store a portal login once, for each entity. We sign in the way your controller would, walk to the statements page, and get to work. No shortcuts, no side doors.
The verification code gets answered
Answer from whichever screen is nearest — the code never has to reach a laptop you are not sitting at. We never say a code was sent unless the portal confirmed sending it, and there is an "I didn’t get the code" button for when one wanders off. Most portals then remember the device and stop asking: Bank of America, Wells Fargo, PG&E and Rize all do, so the second month is usually silent.
We download the months you chose
We collect the monthly statements for the date range you pick: 12 months by default, adjustable per account, which is further back than most portals will let you reach by hand. One login can hold many accounts. A real Citibank login fronts six. We fetch them all and label every statement by account.
We read the close off the statement
Beginning balance, ending balance, statement date — taken from the PDF itself, because that is where reconciliation gets them. This is the step a bank feed has never done and a transaction API cannot.
We convert each statement to a CSV
Every statement becomes a spreadsheet with Date, Description, and Amount, ready to import into QuickBooks. Documents with no transactions, like insurance declarations and privacy notices, are marked as exactly that. We never fake them into a CSV.
We file it all
Everything lands in one archive, labeled by account and month, with the original PDF kept as the audit trail behind the number. View a statement inline, download one, or export the whole thing as a ZIP.
51
portals built — 36 open to every customer, 15 still in testing
12
months fetched per account by default, further back than most portals allow by hand
0
OCR failures across every statement collected so far
For the paper the portals never had
Some statements arrive by mail and never touch a website. A merchant account, an old line of credit, the entity nobody moved online. For those there is our iPhone app: photograph the page, Apple’s on-device text recognition reads it, and it lands in the same archive as everything we fetched.
Full disclosure: the app is in private testing and not on the App Store yet. We could pretend otherwise, but pretending is the one thing we refuse to automate.
For the firm that closes your books
Invite your accountant or bookkeeper as a reader. Accountant seats are free. They browse the archive, download every PDF and CSV, or export the lot as one ZIP. They never see your credentials, and they cannot start fetches.
What they get is the statement behind every number. Which, let’s be honest, is all they ever wanted from you anyway.
And the safety part
Credentials are sealed in a vault scoped to you, encrypted in flight and at rest. Support access is time-limited and granted by you. That is two sentences standing in for a much longer page, which is where the details live.
Read the security deep diveNot shipped yet. Listed anyway.
None of the following exists for you today. We list them so you know where this is going, not to pad the page. Everything you can actually install lives on the downloads page, and that is where each of these lands the day it ships.
QuickBooks Online app
Statements and CSVs pushed straight into QuickBooks, no import step. Being built, not shipped. Today you import the CSV yourself.
Scheduled monthly runs
Every fetch starts with your click today. Putting the close on a schedule is next, and it is not live yet.
iOS app
In private testing. Not on the App Store, and not something you can install today.
macOS app
Reads the verification codes your Mac already receives and answers them for you, so a run finishes with nobody watching. In development, not released.
Chrome extension
For grabbing a statement from a portal you already have open, and for filling the logins we keep so you stop storing them twice. In development.
Plaid-backed institutions
Our application is in progress. It is not live yet, which is why this sentence is here and not on the pricing page.
Point it at one account and judge for yourself.
The first account is free. If a statement does not turn up, you have lost a login form and five minutes.