Blog

How to track MRR across multiple Stripe accounts

If each of your products has its own Stripe account, each account has its own MRR, and adding them up for the whole portfolio is your job. Here is how to track MRR across multiple Stripe accounts and get an honest total, what Stripe itself offers for several accounts, and what usually makes the total wrong.

What counts as MRR

MRR is the monthly value of your active recurring subscriptions. A few rules keep it consistent:

  • Normalize to a month. A yearly plan counts as its price divided by twelve. A quarterly plan counts as its price divided by three.
  • Use what customers actually pay. Apply ongoing discounts. A 50% off coupon that lasts forever halves that subscription's MRR.
  • Leave out one-off charges. Setup fees and credit packs are revenue, but not recurring revenue.
  • Decide on trials. Most people leave free trials out until the first paid invoice. Pick a rule and keep it.
  • Count past-due carefully. A subscription in past_due may still recover. Track it separately so a wave of failed cards is visible.

Stripe's own Billing analytics has its definition: the monthly-normalized value of all active and past_due subscriptions, leaving out taxes, free plans, and metered usage. You can choose whether discounts come off, though permanent recurring discounts always do. Whatever rules you pick, know where they differ from Stripe's, so you can explain the gap when you compare.

Currencies

If products charge in different currencies, convert to one reporting currency at a stated rate. Mixing euros and dollars in one total is the most common reason portfolio MRR looks off.

Getting the data safely

Use a restricted key per Stripe account, with read access to subscriptions, customers, and charges. Do not use a secret key for reporting. A read-only key cannot move money if it leaks, and you can revoke it without touching anything else. Stripe's own guide to API keys recommends restricted keys for most uses and advises against secret keys for new ones. The Stripe read-only key builder lists exactly which permissions to set to Read.

What Stripe offers for several accounts

If your accounts belong to one business, Stripe Organizations group them under one login. An organization gives you:

  • Consolidated reports. Balance, payout reconciliation, and fees reports across the accounts you pick, summed in one settlement currency at a time, as Stripe's page on reports for multiple accounts describes. These cover money moving, not MRR.
  • SQL across accounts. Sigma for Organizations runs queries across every account, so you can write your own MRR query once.
  • Organization API keys. One organization key, starting sk_org, can read any account in the organization, and its permissions can be limited. Every request has to name the account in a Stripe-Context header and set a Stripe-Version. Stripe says to use one only when you need more than one account; it is still a secret, so give it the fewest permissions that work.

If your products are separate businesses, or you would rather keep each one's access separate, one restricted key per account is simpler and limits what any single leaked key can reach.

Adding it up

  1. For each account, list active subscriptions with their price, interval, quantity, and discount.
  2. Normalize each one to a monthly amount.
  3. Sum per product, then sum across products.
  4. Keep past-due and trialing totals next to the main number, not inside it.

For a quick estimate, the portfolio MRR calculator does the normalizing and the totals in your browser. Nothing you type leaves the page.

Mistakes that make the total wrong

  • Counting a yearly payment in the month it lands. A $240 yearly plan is $20 of MRR every month, not $240 in March and nothing after.
  • Counting the same customer twice. If one customer pays for two products, they are two subscriptions and belong in both products' MRR. But if you report customers, count them once.
  • Including test mode. Make sure each key reads live data. Test subscriptions look real in a quick export.
  • Forgetting a product that sells elsewhere. If one product sells through Polar or another billing tool, its MRR needs adding in the same way, normalized to a month.
  • Hiding a falling product. A portfolio total can grow while one product shrinks. Keep a row per product under the total, and look at both.

Check against Stripe

Once you have a number, check one product against what Stripe reports for that account. If they differ, the cause is nearly always one of the rules above: trials, discounts, past-due, or a yearly plan counted in full. Stripe counts past-due subscriptions in its MRR, so if you keep them apart, your number will read lower than Stripe's by exactly that amount. Settle the rule, write it down, and use it every month. A slightly different definition used consistently is more useful than a perfect one used once.

Keeping it current

A spreadsheet works for a month. After that you want the number to update itself, per product, next to signups and traffic. LopeBase's Stripe connector reads each account with its own restricted key and shows portfolio MRR on the Overview and the Revenue page, with one row per product. If one Stripe account bills several products, you connect it once for all of them. Products that sell through Polar add into the same total, and past-due subscriptions show separately under Needs attention.

Its rules, so you can compare it with Stripe: only active subscriptions count, at list price, with yearly plans divided by twelve. Trials and past-due subscriptions are left out, and discounts are not taken off. Amounts in different currencies are never converted or added together; a product billing in euros keeps its own row.

Questions about MRR across Stripe accounts

Something else? Contact us.

Can Stripe show MRR for all my accounts in one place?

Stripe Organizations give you consolidated balance, payout, and fee reports across accounts, and Sigma can query every account with SQL. For one MRR number across accounts, you write that query yourself, add up each account's MRR, or use a tool that reads every account.

Do I need a separate API key for each Stripe account?

With separate accounts, yes: one restricted key per account, set to Read. If the accounts are in a Stripe organization, an organization API key can read all of them, but it is a secret key that reaches every account, so limit its permissions.

Should past-due subscriptions count in MRR?

Stripe counts them. Some people keep them apart so a run of failed cards is visible. Either is fine if you pick one rule and keep it, and know it is why your number may differ from Stripe's.

How do I add up MRR in different currencies?

Convert each product's MRR to one reporting currency at a stated rate before adding, and keep the rate with the number. Or keep a row per currency and do not add them at all.

Is there a free way to add up MRR across products?

Yes. The portfolio MRR calculator adds up plans across products, with yearly plans and discounts handled, in your browser with no signup.

Run every product from one console.Free for one property. No card.
Start free