Mercury SaaS Renewals: One Feed, Every Contract

To build a SaaS renewal calendar from Mercury, export 12 months of transactions, separate ACH/wire vendor payments (annual invoiced contracts) from recurring card charges (subscriptions), estimate each contract end date from the last annual payment, then subtract the vendor's notice period to get your cancellation deadline. Because Mercury is both your bank account and your debit/credit card, a single CSV export captures invoice-paid annual deals and card-billed monthly tools in one feed — a structural advantage over card-only expense platforms.

Mercury's unique position as a startup's primary bank means mercury saas renewals work differently from other spend sources: you see the full payment picture, not just what cleared a corporate card. That said, Mercury does not push transaction data into contract tools automatically — the workflow is a CSV export, then an import into a renewal tracker.

This guide covers how to extract that data and turn it into a system that catches renewals before they auto-charge.

Why Mercury Is a Better Spend Source for SaaS Tracking

Most startup expense tools capture only card spend. Mercury covers both payment rails:

• ACH and wire payments — how most mid-sized annual SaaS contracts are invoiced (Salesforce, HubSpot, security tools). These never appear on a corporate card but flow through Mercury as bank debits.
• Debit and credit card charges — monthly subscriptions, usage-based tools, and smaller annual plans billed to the card.

Because annual invoiced contracts are typically your largest SaaS commitments and carry the longest notice periods, missing them in a card-only export is where budget surprises actually come from.

Step-by-Step: Mercury Transaction Data to Renewal Calendar

Step 1: Export 12 Months of Transactions

In Mercury, navigate to Transactions, set the date range to the past 12 months, and export to CSV. Mercury's export includes columns for Date, Description, Amount, Type (Debit/Credit), and Category. You do not need to filter by category before exporting — filtering in the spreadsheet gives you more control.

Step 2: Separate Payment Rails and Identify Vendors

Open the CSV in your spreadsheet tool. Add a helper column Payment Rail and use the Type column to classify rows:

• ACH Debit / Wire → Invoice-paid (likely annual)
• Card charge → Card-billed (monthly or annual)

Sort by vendor description. Group duplicate vendor names to identify billing intervals: vendors appearing once in 12 months are likely annual; vendors appearing every 30 days are monthly.

Step 3: Calculate Contract End Dates and Notice Deadlines

For each annual vendor, take the most recent payment date and add 365 days (or 366 for the current year if applicable) to estimate the next billing date. That is your Estimated Renewal Date.

Add a Notice Period (Days) column from your contract terms — typically 30, 60, or 90 days. Subtract the notice period from the renewal date to get the Cancel Deadline: the last day you can send a written cancellation and have it honored.

Worked Example: 7-Vendor Mercury Export, Converted

The first four columns come from the Mercury CSV export. The final three are added during enrichment:

Two findings jump out immediately. First, Rippling's cancel deadline of May 11 has already passed — that $18,600 contract auto-renewed for another year, and it was an ACH payment that would be invisible in a card-only export. Second, Intercom's 60-day window closes July 16, so a usage review needs to start within days of this export being built. The two rolling monthly tools (Loom, Vercel) carry no deadline risk and can sit at the bottom of the queue.

Step 4: Import Into an Alert System

A spreadsheet is a starting point, not a system. Once the cancel deadlines are mapped, import your cleaned CSV into a renewal tracker like Satellite. Satellite's expense-based discovery parses your transaction export, matches vendors to contracts, and sends email alerts to tool owners 90 and 30 days before each deadline closes.

If you are migrating from a manual sheet, the spreadsheet-to-renewal-tracker walkthrough covers the import step in detail. For teams using Brex alongside Mercury (for example, a separate travel card), the Brex SaaS renewals guide covers the equivalent card-only workflow.

Frequently Asked Questions

Does Mercury integrate directly with renewal management tools?

Not natively, as of mid-2026. Mercury does not offer a live API feed to third-party SaaS management platforms. The practical workflow is a CSV export from Mercury's Transactions page, followed by an import into your renewal tracker. Satellite accepts CSV imports directly — upload the Mercury export and the platform maps vendor names to contracts and flags gaps.

Why does the payment rail (ACH vs. card) matter for renewal tracking?

Annual invoiced contracts paid via ACH are typically your largest SaaS commitments and carry the longest notice requirements — 60 or 90 days is common. Card-billed tools tend to be smaller and monthly. If you only track card spend, you miss the category of contracts most likely to cause a large, unexpected budget hit when they auto-renew. Mercury's bank export is the only way to see both in one place.

What if a vendor description in the Mercury CSV is ambiguous?

Mercury's transaction descriptions often use legal entity names rather than product names (for example, "Salesforce.com Inc" vs. "Salesforce"). When the description is unclear, cross-reference the amount and date against your accounts-payable records or vendor invoices. For the SaaS renewal calendar template approach, a manual vendor-name lookup column handles this gap — add a "Canonical Vendor Name" column and normalize descriptions before import.

Ready to turn your Mercury export into a proactive renewal engine? Start with the free Satellite renewal tracker — upload your CSV, map your deadlines, and automate alerts to tool owners. Or sign up for Satellite at a flat $299/month.