Convert your Mercury statement to Excel

Mercury Checking, Savings, and Treasury PDFs for startup bookkeeping. Drop a PDF and get back a verified XLSX, CSV, or QBO in seconds.

BankPDFtoXLS is an independent service. We are not affiliated with, endorsed by, or sponsored by Mercury (Choice Financial). The name "Mercury (Choice Financial)" is used only to describe compatibility with statements you have legally obtained from your own account. See our trademarks policy.

From Mercury PDF to verified spreadsheet

  1. 1. Drop your Mercury (Choice Financial) PDF — digital or scanned, monthly statement or a combined multi-month export, up to 50 MB (or batch up to 25 files). Password-protected PDFs and image-only scans both work: scans go through vision OCR automatically.
  2. 2. Parse & reconcile — every transaction is extracted and the sum is checked against ending balance minus beginning balance within $0.01.
  3. 3. Download XLSX, CSV, or QBO — one click each, or batch up to 10 statements and download them as a single ZIP.

What a Mercury statement PDF looks like

Sections in the PDF
Account Summary · Activity · Vault and Treasury Activity · Card Transactions · Wire and ACH Detail
Transaction date format
MM/DD/YYYY
Products we've parsed
Mercury Checking, Mercury Savings, Mercury Vaults (named sub-accounts), Mercury Treasury (T-bill / money-market sweep), Mercury IO Card, Mercury Working Capital

Mercury statements are designed for startup bookkeeping rather than retail banking — the activity block carries richer counterparty metadata than typical bank PDFs (vendor name, vendor ACH ID, invoice memo) and the masthead lists the FDIC-partner bank (Choice Financial Group or Evolve Bank & Trust) explicitly. The parser uses Mercury's identifying header markers and treats both partner-bank variants identically.

Vaults are named sub-accounts under the main Checking — common patterns include 'Tax', 'Payroll', 'Operating'. Each Vault has its own running balance and the statement lists transfers between Vaults as their own rows. The exporter keeps each Vault as a separate sheet so per-budget tracking matches the founder's mental model of the cash position.

Treasury accounts hold T-bill and money-market positions and behave more like brokerage statements than checking — yields post as their own rows with descriptions like 'Treasury yield distribution', and the ending-balance figure includes accrued-but-unpaid interest. Reconciliation switches to a per-position check rather than a flat running-balance sum, with the unpaid-accrual preserved as metadata.

Supported Mercury statement types

We handle business PDFs from Mercury (Choice Financial).

  • business

Where Mercury PDFs trip up manual conversion

Format-specific quirks that break naive PDF parsers — and how the reconciliation pipeline handles each one.

Wire transfers carry SWIFT/IBAN reference codes inline

International wires on Mercury Checking print the SWIFT BIC, IBAN, and beneficiary bank name in the description column, often pushing the line over 200 characters. Parsers that truncate descriptions at a fixed width lose the routing identifiers, breaking reconciliation against an external wire log. The parser preserves the full description verbatim and adds a derived 'wire reference' metadata column extracting the SWIFT/IBAN so cross-border audits work without manual cleanup.

Working Capital draws and repayments cross account boundaries

Mercury Working Capital draws appear as deposits in Checking with description 'Working Capital draw' and matching repayments appear as debits — but the loan balance itself is on a separate Mercury Working Capital statement. Cross-statement reconciliation that ignores the Working Capital side appears to find unexplained inflows. The parser preserves the loan-reference number on every Working Capital row so the matching repayment ledger can be reconciled in a separate pass.

Vault rebalancing transactions appear on every linked sheet

When a customer moves money between two Vaults, the transaction shows up twice — once as a debit on the source Vault's section, once as a credit on the destination Vault's section. Manual reconciliation that sums all sections produces a net-zero artefact for every rebalance. The parser identifies rebalance pairs by shared transfer-ID and lets the export collapse them in a 'cross-Vault transfers' summary tab so per-Vault running balances stay accurate while inter-Vault flows remain visible.

Frequently asked questions

Do Mercury Vaults export as separate accounts?
Yes. Each Vault under Mercury Checking ends up on its own XLSX sheet with its own beginning/ending balance. Inter-Vault transfers are tagged with a shared transfer-ID so net-cashflow analysis can collapse them without losing the budget-allocation trail.
How are Mercury Treasury yields handled in QBO export?
Treasury yield distributions post as their own rows with a 'Treasury yield' description and are tagged as interest-income in the QBO export — QuickBooks treats them like investment income rather than ordinary deposits, which keeps the chart-of-accounts mapping correct without manual recategorisation.
Will it work for IO Card statements?
Yes. IO Card cycle-based statements run through the LLM path with merchant + category preserved per row. The reconciliation matches charges − payments against the printed new-balance figure on cycle close.
What about combined Vault + Treasury + Card statements?
Mercury occasionally bundles all linked accounts into one PDF for tax season. The parser treats each section independently — Checking, each Vault, Savings, Treasury, IO Card — and the export gives you one sheet per account with the cycle window and partner-bank legal entity preserved per sheet for compliance review.

Related articles

Built for these workflows

Most Mercury statements that come through us are part of one of these workflows. Each link below explains how the reconciliation guarantee maps to that practice.

Other banks we convert