Resources
Mercury Bank Integration for Accounting, November 2026

Mercury Bank Integration for Accounting, November 2026

Learn how to integrate Mercury bank accounting with native API connections for real-time transaction sync and automated categorization. March 2026 guide.

The Puzzle Team
4.8.26
Last updated
November 5, 2026
In article:

Your Mercury transactions are sitting in banking limbo until someone categorizes them and pushes them into your general ledger. Mercury bank accounting integrations promise to automate that flow, but standard bank feeds update slowly and arrive without the merchant metadata that speeds up categorization. API-based connections pull transaction details in real-time with counterparty information, memo fields, and Treasury account designations that make automated matching actually work. The integration architecture you choose determines how much review work remains after imports run. Here's how each connection method handles your transaction data and where the automation breaks down.

TLDR:

  • Mercury integrates with accounting software through native connections or bank feeds. Native pulls real-time data with merchant details that cut categorization time.
  • Mercury's AI learns from your transaction history to auto-categorize expenses, with custom rules overriding suggestions for vendor-specific or card-specific patterns.
  • The Mercury API delivers real-time balance updates and Treasury account details that standard bank feeds strip out or delay by hours.
  • Puzzle connects to Mercury's native API for immediate transaction sync with full metadata, categorizing about 90% of transactions automatically and matching bank activity to your books daily, with your review before anything is final.
  • Puzzle is AI-native accounting software that integrates with your full financial stack in minutes and delivers real-time burn rate, runway, and cash insights.

What is Mercury bank accounting integration

Mercury bank accounting integration connects your Mercury banking data with your accounting software, automatically importing transactions, balances, and banking activity. This connection lets you categorize expenses, match accounts to your ledger, and generate financial reports without manual data entry.

For startups using Mercury, this integration bridges raw banking data and accurate financial records. Without it, you're manually entering every transaction or importing CSV files.

Mercury connects with accounting software through two methods:

Native integrations are built for Mercury and pull transaction data in real-time or near real-time. These integrations include merchant information and metadata that speeds up categorization.

Bank feeds work through standardized protocols supported by most accounting software. They update on a delay and typically lack the granular detail that reduces manual bookkeeping work.

The integration quality determines how much manual work remains after transactions import. Real-time data access matters when you need current visibility into burn rate and cash position.

Mercury's native accounting software integrations

Mercury connects directly to QuickBooks Online, Xero, and NetSuite. Each integration syncs your transaction data automatically, but they vary in setup requirements and available features.

QuickBooks Online pulls transactions daily through Mercury's banking connection. The sync includes merchant details and AI categorization that learns from your patterns. For a broader look at best accounting software for Mercury users, all enriched automation features come free with your Mercury account.

Xero works the same way: daily transaction sync through bank feeds with merchant metadata and AI-suggested categories. You review and approve suggestions before they hit your books. No extra cost beyond your standard Xero subscription.

Enriched NetSuite categorizations require Mercury's Pro plan at $299/month. Standard bank feed imports for QuickBooks Online, Xero, and NetSuite are free on every Mercury plan, according to Mercury's accounting integrations page. The Pro integration routes banking data into NetSuite's general ledger with the enriched data feeds needed for automated reconciliation. Note that Treasury transactions are currently excluded from GL code categorization across all Mercury accounting integrations.

Accounting SoftwareIntegration TypeSync FrequencyKey FeaturesCost
QuickBooks OnlineNative Mercury integrationDaily transaction syncMerchant details included, AI categorization learns from patterns, enriched automation featuresFree with Mercury account
XeroNative Mercury integrationDaily transaction syncBank feeds with merchant metadata, AI-suggested categories with manual approval before postingFree with Mercury account
NetSuiteNative API connectionReal-time via APIEnriched data feeds for automated reconciliation, direct general ledger routing (Treasury transactions excluded from GL categorization)Mercury Pro plan required ($299/month)
PuzzleNative Mercury APIReal-time as transactions postFull metadata with memo fields and Treasury account designations, about 90% automated categorization, continuous reconciliation, real-time cash position and burn rate updatesVaries by plan
Standard Bank FeedsStandardized protocolDelayed (overnight batch)Basic transaction data, limited merchant details, manual categorization requiredSupported by most accounting software

How Mercury's AI transaction categorization works

Modern abstract illustration of AI pattern recognition and machine learning in financial transactions, showing interconnected nodes and data flows, with visual representations of transaction categorization and automated learning processes, clean minimal design with purple and blue gradient colors, isometric perspective, fintech aesthetic

Mercury's AI reviews your transaction history and suggests categories by identifying patterns across your spending. When you pay the same vendor multiple times, Mercury recalls your previous categorization and applies it to new transactions from that vendor automatically.

The system matches incoming charges against existing records using merchant data and transaction details. If you labeled a Stripe fee as "Payment Processing" last month, Mercury suggests that same category when the next Stripe charge posts. Each time you approve a suggestion, the AI learns to recognize similar transactions going forward.

You can create custom rules that take precedence over AI suggestions for specific situations. Build rules by counterparty name to tag all Amazon purchases as "Office Supplies," or by team member to route Sarah's transactions to "Sales & Marketing." Card-specific rules help when certain cards handle only travel or software expenses.

Custom rules run first, then AI fills remaining gaps based on historical patterns. You review all suggestions before they sync to your accounting system, keeping final control while reducing manual categorization time.

Setting up Mercury accounting automation step by step

Go to Mercury Settings, then Integrations. Locate your accounting software in the list and click Connect. You'll authorize Mercury to access your account through OAuth authentication.

After authorization, Mercury imports your recent transaction history. The initial sync pulls 90 days of banking activity into your accounting software within minutes. Older transactions require CSV import if needed for historical records.

Turn on enriched categorization under Mercury Settings to access AI suggestions. This activates merchant metadata and pattern recognition across your transaction feed.

Map Mercury categories to your chart of accounts so transactions land in the correct buckets without manual intervention. If your accounting system supports hierarchical categorization, create parent categories like "Software" with subcategories for specific tools.

Set up rules for recurring expenses: tag all AWS charges as "Infrastructure," route employee reimbursements by department, or categorize specific cards by function. Rules apply to future transactions and retroactively to recent imports matching your criteria.

Review the uncategorized transaction queue after setup completes. Approve AI suggestions or manually assign categories to train the system for future accuracy.

Bank reconciliation with Mercury integration

Mercury syncs statement balances to your accounting software multiple times daily, catching discrepancies before they grow into month-end issues. The bank feed runs automatic validation during import, checking that debits and credits match your statement, flagging duplicate entries, and verifying transaction dates align with posting dates.

When you open your reconciliation screen, most transactions already match your Mercury statement. You're verifying instead of investigating. Transactions appear with merchant names and amounts that align automatically when dates and values correspond.

Troubleshooting common sync issues

Sync errors typically stem from failed imports or mismatched balances. Check your integration status first: disconnected OAuth tokens cause most problems. Refresh the connection through Mercury Settings if needed.

Missing transactions usually need sync window adjustment. Mercury imports recent history by default, but you can trigger manual pulls for specific date ranges when gaps appear.

Mercury API for advanced accounting automation

Modern technical illustration of API architecture and data flow, showing real-time banking data streaming through native API connections, with visual representation of transaction metadata flowing from banking infrastructure to accounting system, clean nodes and connection lines, structured JSON data visualization, purple and blue gradient colors, isometric perspective, fintech and software integration aesthetic, no text or labels

Mercury's API opens access to banking data that standard integrations can't reach. While most accounting software connects through bank feeds or third-party plug-ins, the API delivers real-time balance updates, complete memo field data, and Treasury account transaction details that bank feeds typically strip out.

Teams building custom financial dashboards or needing sub-account level reporting benefit from API access. The connection returns structured JSON data including counterparty information, pending transactions, and statement-level reconciliation details that simplify automated matching.

Puzzle connects natively to Mercury's API without middleware or plug-ins. This architecture gives you immediate access to new Mercury features as they launch, without waiting for third-party updates or connector maintenance. When Mercury releases Treasury transaction categorization or enhanced merchant data, it flows straight through to your books.

Other accounting systems connect through intermediary services that add sync delays and filter data fields. Native API connection pulls unfiltered transaction metadata that improves categorization accuracy and reduces the manual review queue.

If you're running Treasury accounts alongside operating funds, API integration separates these transaction streams automatically. Standard bank feeds often merge everything into a single import, requiring manual sorting during reconciliation.

Puzzle's native Mercury integration for real-time accounting

We built our Mercury connection on their native API because bank feeds weren't good enough for real-time accounting. The direct API pulls transaction data as it happens, not on overnight batch schedules.

When a Mercury transaction posts, Puzzle receives the full metadata immediately: merchant details, memo fields, counterparty information, and Treasury account designations that bank feeds omit. This enriched data feeds our AI categorization engine, which categorizes about 90% of transactions automatically for your review.

Your reconciliation happens automatically in the background. Puzzle matches Mercury transactions to your general ledger continuously, flagging discrepancies the moment they appear instead of during month-end close. Cash position updates in real-time on your dashboard alongside burn rate and runway calculations.

Treasury accounts sync separately from operating funds without manual sorting. If you're earning yield on idle cash while running daily operations, both streams flow into the correct accounts automatically.

The combination of Mercury's banking infrastructure and Puzzle's AI-native accounting delivers what startups need: accurate books that update daily, not monthly compliance exercises that arrive too late to matter.

What's new in Mercury's accounting integration (November 2026)

Four Mercury launches since August expand the data your accounting integration needs to handle.

Mercury Spend (launched August 11, 2026) adds budgets and self-enforcing expense policies directly inside Mercury, including dedicated cards for AI agents. Transactions are auto-categorized to the right budget and category at the point of purchase, and admins can configure rules that control how each transaction feeds into their accounting system. Pre-categorized spend data gives any connected Mercury bookkeeping software less to sort during review.

Mercury Treasury exclusive mutual funds (announced August 18, 2026) introduced two Mercury-exclusive investment products: MCRYX (ultra-short bond fund built with Morgan Stanley Investment Management, live at announcement) and MRGXX (government money market fund share class built with State Street Investment Management, which replaced the prior fund for existing holders on August 21). Mercury notes that Treasury positions sync with QuickBooks, Xero, and NetSuite. If you hold idle cash in Treasury alongside operating accounts, verify that your integration is pulling both streams and routing them to separate GL accounts. Standard bank feeds often merge these into a single import; API-based connections separate them automatically.

Mercury Books (launched September 16, 2026) puts double-entry accounting, with accrual or cash basis, inside the Mercury dashboard. Mercury lists it as free through the end of 2026, then $35/month. If your banking lives in Mercury and your setup is a single entity, it is worth weighing against Mercury accounting integrations. If your stack spans Stripe, Gusto, Ramp, or Brex alongside Mercury, you still need a ledger that pulls from all of them.

Mercury Payroll (launched October 20, 2026) runs W-2 and 1099 contractor payroll from the Mercury account. Mercury lists it as free for eligible customers through the end of 2026, then $100/month plus $50/month for each person paid starting in 2027. Payroll adds another transaction stream, so confirm your accounting tool maps payroll debits to wages, employer taxes, and benefits.

Final thoughts on Mercury integration for startup accounting

Mercury handles your banking, but your accounting integration determines how much manual work remains after transactions import. Real-time API connections pull complete transaction metadata that AI can categorize automatically, while standard bank feeds give you the same delayed, stripped-down data that requires constant review. Your financial visibility is only as good as the connection between your bank and your books.

FAQ

How long does Mercury integration take to set up in your accounting software?

The initial connection takes just a few minutes through OAuth authentication, and Mercury will automatically import your last 90 days of transaction history within minutes of connecting. You can start categorizing and matching transactions immediately.

What's the difference between Mercury's native integrations and standard bank feeds?

Native integrations pull transaction data in real-time with full merchant details and metadata that speed up categorization, while standard bank feeds update on a delay and typically lack the granular transaction details that reduce manual bookkeeping work.

Can I set up rules to automatically categorize recurring Mercury transactions?

Yes, you can create custom rules by vendor name, team member, or card to automatically categorize transactions. Like tagging all AWS charges as "Infrastructure" or routing specific employee cards by department, these rules apply both to future transactions and recent imports.

When should I use Mercury's API instead of the standard accounting integration?

If you need real-time balance updates, complete memo field data, Treasury account transaction details, or you're building custom financial dashboards that require sub-account level reporting, the API gives you access to structured data that standard bank feeds filter out.

What tools give a startup founder real-time burn rate and runway visibility without a dedicated finance team?

The combination of Mercury and an AI-native accounting tool like Puzzle gives founders real-time burn rate and runway visibility without hiring a controller or CFO. Mercury's API pushes transaction data the moment it posts, with no overnight batch delays. Puzzle picks it up immediately, categorizes about 90% of transactions automatically, and updates your burn rate, runway, and cash position on your dashboard continuously. You're not waiting for a monthly close to know where you stand. If you're pre-Series A with no dedicated finance team, this stack replaces the manual spreadsheet loop most founders are stuck in.

What's the best accounting software for a venture-backed Delaware C-Corp raising a Series A or Series B?

At Series A or B, your investors will expect GAAP-compliant financials, clean audit trails, and real-time metrics, not a QuickBooks export you put together the week before a board meeting. The right stack depends on your complexity: most Series A companies (single entity, Stripe revenue, Mercury banking) are well-served by accounting software for Mercury and Stripe startups, with Puzzle connected to Mercury's native API keeping books current daily and surfacing burn and runway automatically. Series B companies adding entities, international operations, or complex rev-rec sometimes graduate to NetSuite, but many over-buy ERP too early and spend months on implementation instead of growth. Match the software to your current complexity, not your hoped-for complexity two years from now.

How do I automatically track ARR, MRR, and net revenue retention inside my accounting software?

Standard accounting software (QuickBooks, Xero, even NetSuite out of the box) doesn't calculate ARR, MRR, or net revenue retention automatically. You need a tool that connects to both your revenue source (typically Stripe) and your general ledger. For SaaS founders, see the best accounting software for SaaS startups using Stripe and Mercury. Puzzle pulls from both simultaneously, mapping recognized revenue to the correct period and surfacing SaaS metrics like MRR and burn rate in real-time alongside your accounting data. Your MRR figure and your general ledger stay in sync without a manual reconciliation step each month, and your NRR is derivable from the same data set instead of a separate spreadsheet exercise.

What's the best software for automating bank reconciliation at a seed-stage startup?

At seed stage, you need reconciliation that runs itself, not a dedicated accounting team or a FloQast implementation built for public-company close processes. If your primary bank is Mercury, the native API integration with Puzzle gives you continuous reconciliation: transactions are matched against your general ledger the moment they post, discrepancies surface immediately, and your statement balance stays in sync without a month-end scramble. Ramp and Brex offer spend management with some reconciliation features, but those are card-focused tools, not full accounting systems. For a seed-stage company that needs accurate books, real-time cash visibility, and automated reconciliation without a controller, Mercury plus Puzzle is sized for where you actually are.

How does Mercury's AI learn to categorize my transactions correctly?

Mercury's AI identifies patterns across your spending history. When you categorize a vendor once, it remembers and suggests the same category for future charges from that vendor, learning and improving accuracy each time you approve or correct a suggestion.

Can I import CSV bank statements or transaction files into Puzzle?

Yes. If your bank doesn't support a native API or bank-feed connection, Puzzle accepts CSV imports of transaction files directly. Upload your exported statement and Puzzle's Accounting AI maps the columns, suggests categories based on your existing transaction history, and queues any rows it can't categorize for review. For Mercury accounts, the native API connection is faster and pulls richer metadata, but CSV import is the fallback for any institution Puzzle doesn't yet connect to natively.

How reliable are Puzzle's bank connections, and how do I know if my integration is actually syncing?

Puzzle's Mercury connection runs on Mercury's native API, not a fragile screen-scraping layer, so it isn't broken by bank UI changes or credential resets. Your integration status is visible on the Puzzle dashboard: a green sync indicator updates each time new transactions arrive, and a warning surfaces immediately if the connection drops or a pull fails. If transactions appear missing, check the date range on your feed. Mercury imports recent history by default, and gaps from before the connection window require a manual CSV import or a triggered re-sync from Settings.

How does Puzzle integrate with credit cards, payroll providers like Gusto, and other banks like Chase?

Puzzle connects to your full financial stack, Mercury included. Credit card feeds (Ramp, Brex, and others) sync alongside your bank accounts so every charge lands in the right GL account automatically. For payroll, Puzzle integrates with Gusto: read the Gusto payroll automation integration guide for setup details, covering how payroll runs flow directly into your books so wages, employer taxes, and benefits post to the correct expense accounts without manual journal entries. For Chase and other banks that don't offer a native API connection, Puzzle connects through a bank-feed protocol or CSV import. The goal is one unified view of cash and expenses regardless of how many accounts or providers you run.

How do I automate payroll journal entries when I run payroll through Gusto or Rippling?

Connect your payroll provider to your accounting software natively, then let the integration draft the entry for each pay run. Puzzle integrates directly with Gusto and Rippling (and Deel). Each payroll run syncs in and is split into gross wages, employer taxes, and benefits, with the cash payment matched to the withdrawal from your Mercury account. You review and finalize the entry instead of typing it. Rippling carries an extra fee of $2/month per employee and contractor on top of your Puzzle subscription. If your provider isn't a native integration (ADP or Justworks, for example), upload the payroll report and Puzzle's AI payroll agent drafts the journal entries from it for your approval. If you run payroll through Mercury Payroll, confirm your chart of accounts maps those debits to wages, employer taxes, and benefits.

How do I split a single bank transaction across multiple clients or invoices in Puzzle?

When a lump-sum payment arrives in Mercury that covers multiple invoices or clients, Puzzle lets you split the transaction from the review queue. Select the transaction, choose Split, and allocate amounts to each corresponding invoice or GL line. For recurring usage-based billing where a single payment maps to many line items, Puzzle supports bulk payment matching: link one bank deposit to a batch of open invoices and mark them settled in one step. This prevents the common reconciliation problem where a single deposit goes without a match because no single invoice equals its exact amount.

How does Puzzle handle bank syncing when personal and business accounts share the same bank login, and how do I remove incorrectly imported transactions?

Connect only the business accounts you want in your books. If your bank login also holds personal accounts and you connect through Plaid, select just the business accounts when you authorize the connection. Set the ingestion start date for each account at connection too, because ingestion date settings can't be edited self-serve after initial setup. If personal transactions still land in your ledger, use universal transaction search to filter by account, vendor, or amount, then use bulk editing to handle the matching rows together. To delete imported transactions or disconnect a wrongly linked account, contact Puzzle support. Your audit log shows who created or modified each transaction, so you can trace where a bad import started.

Can accounting software automatically connect to international bank accounts outside the US?

Not with Puzzle. Puzzle supports USD and US entities only, with no multi-currency accounting. Bank connections run through direct integrations (Mercury, Brex), Plaid, or manual upload, and the books themselves stay in USD. If you run a US Delaware C-Corp that banks in the US, you're the right fit. If you operate entities abroad or need to hold and report in multiple currencies, you need software built for that before you commit.

How does Puzzle handle PDF bank statement imports and categorize transactions without a live bank feed?

For banks without a live connection, the supported manual route is a CSV upload from the plus-sign icon near the export button in the transactions section. CSV import carries date, amount, and description, so you add vendor name and category afterward. Puzzle does not document PDF bank statements as a transaction import format, so export a CSV from your bank if you can. PDFs do work for receipts: Puzzle's AI receipt-matching agent accepts text, PDF, and PNG files and matches them to transactions (JPEG images are not accepted). Once rows are in, categorization runs the same way as on a live feed: about 90% of transactions are categorized automatically, and anything below the 99% confidence threshold stays uncategorized for your review. Expect lower accuracy on a new account until your finalized decisions build up history and rules. Mercury and Ramp match bank activity to your books daily without any upload.

How does Puzzle's AI Cowork work, and what repeatable workflows can it run?

Cowork turns a one-time accounting request into a repeating job. You describe the task once, Puzzle saves it as a prompt-based agent, and the agent prepares the work on a schedule for your review. Nothing changes in the books without your approval. Cowork is included on all plans. It sits alongside two other parts of the AI suite: AI Chat answers questions from your actual books (read-only), while Puzzle's categorization engine runs in the background on its own. For categorization, you can also set account-based rules that apply to future transactions. For revenue recognition, you set policies by product or subscription type, and Puzzle defers and recognizes revenue at the invoice line-item level, with bulk confirmation of up to 100 schedules at a time.

How does Puzzle handle Stripe payouts deposited into a connected bank account, and what happens when an account is missing or disconnected?

Connect both Stripe and Mercury so the ledger sees the sale on the Stripe side and the payout landing in your bank. Both are native integrations, and each connects in about two minutes. If either account is missing or disconnected, one side of the transfer has nothing to pair with, and the deposit shows up in your review queue instead of clearing cleanly. Reconnect the missing account, then check that its ingestion start date covers the payout period, since those dates can't be edited self-serve after initial setup. Your dashboard flags a dropped connection, so check integration status first when a payout looks unexplained.

Can Puzzle automatically track sales, revenue, and profit margins for a digital products or e-commerce business?

For digital products sold through Stripe, yes, with limits. Stripe transactions sync natively, revenue recognition applies at the invoice line-item level, and your income statement updates daily with revenue against your cost and expense categories. Customer-level profit and loss tracking is also supported. Revenue recognition is Stripe-centric, so sales through other billing systems need manual journal entries. If you sell physical goods with inventory and cost of goods tracking, Puzzle is not the right fit, because it has no inventory management.

What happens if I import transactions manually and also connect a bank integration for the same account?

Overlap is the risk, so plan the handoff before you connect. Pick one source for each period: upload a CSV for the months before the connection, then set the integration's ingestion start date to the day after your last uploaded transaction. Set that date at initial setup, because it can't be edited self-serve afterward. If duplicates still appear, use universal transaction search to filter by account, amount, and date, review the matching rows side by side, and use bulk editing to handle them together. Contact Puzzle support to remove rows you can't clear yourself.

Does Puzzle integrate directly with Shopify for order and inventory accounting?

No. Shopify is not among Puzzle's native integrations (Stripe, Mercury, Brex, Ramp, Gusto, Carta, Finch, and Square via Plaid), and Puzzle has no inventory management or inventory-level cost of goods module. That boundary is permanent. If your Shopify payouts arrive through Stripe, Puzzle can book that revenue, but inventory and COGS for physical products need to be handled outside Puzzle. Startups with inventory-heavy e-commerce models should look at accounting software built for inventory.

Let us help you solve your financial puzzles.

Thank you for being part of our Puzzle community. Stay tuned!
Oops! Something went wrong while submitting the form.
You can unsubscribe at any anytime.

Newsroom