Polar MRR, churn & LTV analytics

• Polar is a merchant of record, so MRR uses the net pre-tax amount.
• Polar's subscription amount already covers every seat, so it is counted once — never multiplied by the seat count.
• Only orders that settled — paid, refunded or partially refunded — count as cash; drafts and pending orders don't.
• Live and sandbox tokens are detected automatically.
• Every price is amortized to a monthly amount — annual plans divided by 12, weekly and daily plans scaled up — and past-due subscriptions still count but are flagged at-risk.
• Trials count as zero until they convert.

The full rule set is on how we calculate MRR.

Polar's analytics compute MRR as the sum of every ongoing subscription's net amount, normalized to a month, with trialing subscriptions excluded. (Polar's docs, checked October 4, 2026)

Honest MRR reads the same Polar records and adds:

• One ledger across billing providers — Polar next to any of the nine we support.
• An audit trail an investor can follow: every MRR movement opens to its ledger entry, the webhook event when one recorded it, and the current Polar record, and every version we receive is fingerprinted in a tamper-evident hash chain.
• Share links and monthly statements you can save as PDF, plus ad spend for CAC and payback, and costs for burn and runway.

If Polar is your only billing source and you don't need an audit trail or investor statements, Polar's analytics may be all you need.

Every subscription imports when you connect, dated from when it started — months before you connected show each one at its current price. A webhook keeps MRR current as events arrive; without one, Honest MRR resyncs daily.

These are the same steps the in-app guide shows on Settings → Connect after you sign in, where “the field below” and “your connection card above” refer to that page.

Honest MRR keeps the latest verbatim copy of every object Polar sends and fingerprints every version in your organization's append-only hash chain, so the MRR you show investors traces back to the records it came from — and a later edit to any of them is detectable. Credentials are encrypted at rest with AES-256-GCM. Details are on the Security and Privacy pages.

Something not covered here? Email us and a person answers.