A dispensary's banking is never just one account
Most retail businesses have a checking account, a merchant processor for card payments, and that's the whole picture. A licensed cannabis dispensary usually has more moving pieces than that — a checking account with a credit union willing to take the relationship, a separate account or third-party processor handling card-adjacent payments (since major card networks still restrict direct card transactions for cannabis), and sometimes a second account entirely for payroll or vendor payments, kept deliberately separate from retail deposits.
Every one of those accounts prints its own statement, in its own format, often from an institution too small to have invested in the kind of clean digital export a national bank offers. Reconstructing a month's full financial picture means reading all of them — by hand, line by line, which is where the hours actually go.
Why dispensary statements are harder to read than most
Small institutions, inconsistent formatting
The credit unions and community banks that serve cannabis accounts are rarely the same ones that invest in a clean, uniform statement export — layouts vary far more than they do across the small number of banks that dominate ordinary retail banking.
Merchant-processor and cashless ATM statements aren't bank statements
A high-risk merchant processor or cashless ATM settlement statement often prints daily batch totals rather than a per-transaction ledger, and needs to be read on its own terms rather than forced into a checking-account template.
Multiple accounts, deliberately kept separate
Retail deposits, vendor payments and payroll are often split across accounts specifically to satisfy a bank's own risk appetite — which means reconstructing one month's full picture means reading several statements, not one.
Cash-heavy deposit patterns
A dispensary that still handles a meaningful share of sales in cash produces deposit lines that need to be checked against a till count or a point-of-sale total, not just read and trusted at face value.
None of this reflects badly on any single institution — it's the normal shape of banking for an industry that remains federally restricted even where it's fully licensed at the state level, and it's exactly why a generic bank-statement reader built around a handful of major banks tends to struggle here.
What this doesn't do, stated up front
Doesn't connect to your bank or processor account
There's no login, no OAuth, no API. You download the statement yourself, the same way you already do to check it, and upload it here.
Doesn't file your bank's SAR or CTR reporting
Suspicious Activity Reports and Currency Transaction Reports are your bank's own regulatory obligation under FinCEN guidance — this has nothing to do with that pipeline.
Doesn't verify a cash deposit against your till count on its own
That comparison — point-of-sale total to bank deposit — is a separate step, covered in the POS-to-bank reconciliation guide.
Doesn't classify transactions for 280E on this page
COGS versus non-deductible operating expense tagging is a dedicated feature, built to run once your statements are already structured.
What's left is narrow and specific: turning whatever a dispensary's accounts actually print, however inconsistent, into one place a bookkeeper or accountant can work from.
What gets read
| Field | Typically found on |
|---|---|
| Transaction date and description | Every account type |
| Amount (debit or credit) | Every account type |
| Running balance | Checking and credit-union accounts |
| Daily batch total | Merchant-processor and cashless ATM settlement statements |
| Fee lines (processing, cash-handling, monthly account) | Merchant-processor and high-risk banking accounts |
| Account holder and account number (masked) | Every account type |
| Statement period | Every account type |
Not every account type prints every field — a merchant-settlement statement rarely carries a running balance, and a checking account rarely breaks out a per-batch processing fee the way a merchant account does. Reading each statement for what it actually contains, rather than expecting a fixed template, is what makes combining several account types into one spreadsheet possible at all.
The account types a dispensary actually has
| Account | What it typically reports |
|---|---|
| Operating checking account | Cash deposits, vendor payments, payroll transfers — often at a small credit union or community bank with a cannabis banking program. |
| Merchant processor / cashless ATM settlement | Card-adjacent retail payments, since major networks still restrict direct card use for cannabis purchases in most cases — settled as daily batches, net of processing fees. |
| Vendor / accounts-payable account | Some operators keep a second account specifically for supplier and cultivator payments, separated from retail deposits at the bank's own request. |
| Reserve or compliance account | A smaller number of operators maintain a separate account tied to state licensing or bonding requirements, rarely touched day to day. |
Not every dispensary has all four — a small single-location operator might run everything through one checking account and one processor, while a multi-location operator often has the full set duplicated per location. Either way, every account's statements get read the same way and land in the same spreadsheet.
One month, three accounts, reconciled
A single-location dispensary with a checking account at a regional credit union, a cashless ATM settlement account, and a separate vendor-payment account.
| Account | Lines read | Net movement |
|---|---|---|
| Operating checking | 61 transactions | +$118,240 |
| Cashless ATM settlement | 29 daily batches | +$94,610 |
| Vendor payment account | 18 transactions | -$71,330 |
Read separately, each statement is a partial picture — the checking account alone doesn't show the cashless ATM settlement income at all, since it lands in a different account entirely. Structured together, all 108 lines across three institutions sit in one spreadsheet, ready for the next step: checking the deposit totals against what the point-of-sale system actually reported selling.
How it works
Upload every account's statement
Checking, merchant processor, cashless ATM, vendor account — whatever the dispensary actually banks with, in whatever format each one exports.
Every line is read
Date, description, amount and balance where printed, kept linked to its source account and file.
Structured into one spreadsheet
Every account's transactions land in the same table, with the source account visible per row rather than merged into one undifferentiated total.
Export
Excel, CSV or JSON — ready for a POS-to-bank check or for feeding into 280E cost classification.
Why the statement itself looks different
Cannabis remains federally scheduled even in states where it's fully licensed, which is why federal banking guidance treats a cannabis account differently from an ordinary retail one. A bank willing to serve the industry generally files enhanced monitoring reports and categorizes accounts by risk tier under long-standing FinCEN guidance for marijuana-related businesses — none of which changes what a dispensary itself needs to read off its own statement, but it does explain why the institutions serving this industry are a small, specific list rather than any mainstream bank, and why their statement formats are rarely as polished as a national bank's.
None of that compliance layer is something this tool touches or needs to know about — it reads the statement your account actually produced, the same way it would read any other.
Multiple locations, multiple accounts
A multi-state or multi-location operator typically banks separately per license, since a single account rarely covers more than one state's licensed operation — different regulators, often a different bank willing to serve that specific state's program. That multiplies the number of statements to read every month without multiplying the time it should reasonably take.
Every location's accounts upload and read the same way, and the source file stays attached to every row, so a finance team rolling up several locations into one consolidated view can still trace any single transaction back to the exact account and location it came from — the same principle covered in more depth for a multi-site operator in multi-entity bank reconciliation and multi-site sales reconciliation.
Where this feeds into 280E bookkeeping
A structured, reconciled set of bank and vendor-account statements is the foundation a cannabis business's 280E position is built on — you can't correctly split cost of goods sold from non-deductible operating expense without first knowing, line by line, what actually moved through every account. This page is that foundation step; the classification itself is covered separately in COGS vs. OPEX tagging for 280E.
Who this is for
Single-location dispensary owners
One clean spreadsheet across checking, merchant-processor and vendor accounts, instead of a separate manual tally per institution.
Multi-state operator finance teams
The same reading process applied consistently across every state license's own accounts and banking relationships.
Cannabis-specialized bookkeepers and CPAs
A faster starting point for a client's monthly books, freeing time for the judgment calls that actually need an accountant's attention.
Anyone switching banks or processors
A reliable way to read a new institution's statement format from day one, without waiting for a template to be built for it.
This isn't a banking relationship or a compliance filing
Worth being precise about the boundary. This doesn't open a bank account, doesn't connect to one, and doesn't file anything with a regulator on your behalf. It reads a document you already have and turns it into a spreadsheet you can actually work from — the underlying banking relationship, and everything your bank is required to report because of it, stays exactly as it is.
What happens when a dispensary changes banks
Losing a banking relationship with little notice is a real, recurring risk in this industry — a credit union revising its own risk appetite, a change in leadership at the institution, or a compliance review that goes against the account can end a relationship a dispensary had counted on. When that happens, the new institution's statement format is, almost by definition, something the business has never dealt with before.
Reading a statement by its own printed layout, rather than expecting a specific bank's template, means a forced transition doesn't also mean weeks of relearning how to read the new account's own statements by hand — the first upload from a brand-new institution gets read the same way a twentieth one would.
Moving off a hand-built spreadsheet
Most dispensaries that reach for this have already built a spreadsheet — retyping figures from each account's statement, tab by tab, every month. It works, in the sense that it produces a number, but it's slow enough that it usually only happens once a month, and a transcription error rarely gets caught until much later, if at all.
The transition doesn't require throwing that spreadsheet away on day one. A reasonable first step is running the automatic extraction alongside the existing process for one statement cycle, comparing the two, and building confidence before switching over fully.
How often to reconcile
A cash-heavy retail business benefits from reading statements more often than the calendar month a bank issues them on. Many operators pull their checking and merchant-processor activity weekly, specifically so a deposit variance or an unexpected fee gets caught while the specific week is still easy to investigate, rather than buried in a month's worth of activity by the time the full statement arrives.
A full reconciliation against the point-of-sale system's own reported sales — the subject of POS-to-bank reconciliation for dispensaries — is worth running at least monthly, and weekly for any location handling a meaningful volume of cash.
What accuracy actually looks like
A dispensary's primary checking account, once its layout is recognized, reads at the same high confidence as any ordinary business bank statement — the underlying document structure isn't exotic. A merchant-processor or cashless ATM settlement statement, with its batch-total shape and processor-specific fee lines, more often needs a first-pass review the first time a given processor is uploaded, after which the layout is recognized reliably going forward.
The honest number for most operators: a primary checking account reads essentially error-free from the first upload, while a first-time processor statement is worth a quick manual check on that initial pass, the same discipline any new document format deserves before it's trusted at scale.
Privacy
Uploads go over TLS, encrypted end to end.
Processing runs on EU-hosted infrastructure.
Original documents are deleted immediately after extraction.
Financial data is never used to train AI models.
Given how sensitive banking access already is for this industry, full details are worth reading on the security page.