OverviewBilling Support1 / 6

FinanceRevenueLive

Subscription Billing

5.0 out of 55 sold

Recurring revenue is easy to report and hard to prove. This build ties every MRR movement to a subscription event, so the number on the board slide reconciles to the ledger.

Function
22
Roles
3
Users
Unlimited
  • Next.js
  • TypeScript
  • PostgreSQL
  • Recharts

Inside the app

What it does out of the box

22 connected functions on one schema, spanning three permission levels. Everything below is in the template before a line of customisation.

  • Dashboard for Sara

    18 payments failed overnight and 6 subscriptions are in their final dunning step.

  • Subscriptions

    Every active, trialling and cancelled subscription with its billing state.

  • Invoices

    Raised by the billing run, with tax applied by customer location.

  • Failed payments

    Retry schedule and what happens when it runs out. Cancellation is never silent.

  • MRR movement

    New, expansion, contraction and churn. Every movement ties to an event.

  • Usage

    Metered consumption against plan limits, with overage before it becomes a surprise.

  • Plans and pricing

    Price changes never apply retrospectively without an explicit decision.

  • Audit log

    Every price change, refund and cancellation. Retained for seven years.

Permissions

Three roles, one build

Billing support fixes what broke. A revenue manager owns the numbers leadership quotes. An administrator owns pricing. Pricing changes are the highest-risk action here, so they are the most tightly controlled.

  1. Billing Support

    7 of 22 functions

    Subscriptions and what broke

    Preview as billing support
    • Create, upgrade and cancel subscriptions
    • Reissue invoices and credit notes
    • Work the failed payment queue
    • See exactly why a card declined
    • Cannot change plan pricing
  2. Revenue Manager

    14 of 22 functions

    The numbers on the board slide

    Preview as revenue manager
    • Everything billing support can do
    • MRR movement tied to subscription events
    • Separate voluntary from involuntary churn
    • Usage and overage as upsell signals
    • Set the dunning retry schedule
  3. Administrator

    22 of 22 functions

    Plans, pricing and tax

    Preview as administrator
    • Everything a revenue manager can do
    • Publish plans and price versions
    • Migrate a cohort onto new pricing, deliberately
    • Configure tax by location and status
    • Read and export the audit log

The build

Every function in the box

9 screens, all of them live in the preview. Nothing on this list is a mockup or a roadmap item.

Access

  • Sign in

Billing

  • Overview
  • Subscriptions
  • Invoices
  • Failed payments

Revenue

  • MRR movement
  • Usage

Administration

  • Plans and pricing
  • Audit log

What you get

Delivered as a repository, not a login.

SaaS and service businesses billing monthly or annually, from 100 to 50,000 customers.

  • 9 production functions spanning three permission levels
  • Full source code and PostgreSQL schema in your repository
  • Role-based access control, enforced server-side
  • Immutable audit log written on every change
  • Responsive layouts, usable on a phone, not just resized
  • CSV import and export on every core record
  • Deployment configuration for your cloud account
  • Twelve months of updates, and no per-seat charge ever

Access and evidence

MRR you can reconcile

An MRR number nobody can tie back to subscription events is a number that falls apart in diligence. Every movement here traces to an event, and every price change is a version rather than an edit.

  1. Every MRR movement ties to a subscription event with a date
  2. Voluntary and involuntary churn reported separately, one is a product problem, one is payments
  3. A published price cannot be edited, only superseded
  4. Existing subscribers keep their agreed price until deliberately migrated
  5. Cancelled subscriptions keep their history so movement can always be explained
  6. Customers are emailed at every dunning step and told when access ends
  7. Immutable audit log with seven-year retention and export

Related

Apps that pair with this one

CRM & SalesLive

Pipeline CRM

Deal stages, forecasting and activity history for a sales team that has outgrown a spreadsheet.

5.0 out of 511 sold

From$549View details
CRM & SalesLive

Client Portal

A branded space where your customers see their documents, requests and invoices without emailing you.

5.0 out of 59 sold

From$529View details

Questions

Subscription Billing, in practical terms

Not covered here?

Ask a consultant directly. No form to fill in first, and no follow-up sequence.

Book a consultantAll questions
Do I get the source code for Subscription Billing?

Yes. The repository, application code, database schema, migrations, seed data and deployment configuration, is transferred to your organisation on delivery. There is no licence key and nothing that calls home.

Does it process payments itself?

No, and you should be wary of anything that claims to. It records what is owed, what was charged and what failed, and drives the retry schedule. Taking the money is your payment provider's job, a fitted build connects your existing merchant account so we are never in the money flow and you keep your own rates.

How does it handle price rises for existing customers?

A price change creates a new plan version; nobody moves onto it automatically. Migrating a cohort is a separate, deliberate, reversible action with customer notification. Silently repricing an existing subscriber is the fastest route to a cancellation and a public complaint, so the app makes it impossible to do by accident.

Can it bill on usage rather than a flat fee?

Yes. Metered consumption is tracked against plan limits, customers are warned at 80% and 100% rather than surprised by the invoice, and overage is either billed automatically or raised as an upsell, depending on the plan.

Can Subscription Billing be changed to match our model?

That is the usual route. A fitted build sets up your plans, metering, proration rules, dunning schedule, tax treatment, invoice design, branding and up to two integrations, and typically takes one to three weeks from a signed scope.

What does it cost to run?

Hosting only, paid to your own cloud provider, roughly $50 to $200 a month, rising with subscriber count and how granular your usage metering is.

Start here

Want Subscription Billing shaped around your process?

A fitted build adjusts fields, stages, roles and integrations to how your team already works. One scoping call, a fixed price, one to three weeks.

  • No sign-up to open one
  • One-time price, no seats
  • Source code transferred on delivery