B2B Billing Models Explained: Recurring, Usage-Based, Milestone, and Why Each One Leaks Revenue

Billing is usually treated as an administrative step: the work is done, so now produce the invoice. That framing hides the fact that billing is where revenue is actually captured — and where a surprising amount of it quietly is not.

Revenue leakage in billing rarely looks like a dramatic failure. It looks like a contractual annual uplift that nobody applied in month thirteen. A usage tier the customer exceeded that was never metered. A project milestone signed off in March and invoiced in June. A contract amendment agreed by email that never reached the billing system.

None of these produce an error. They produce an invoice that is simply smaller than it should have been, or later than it should have been — and nothing in the process flags the difference.

This guide covers the five B2B billing models, where each one leaks, how to choose between them, and what billing automation actually needs to do.

The Five B2B Billing Models

One-Time Billing

An invoice issued once, on delivery of goods or completion of a discrete service.

Where it fits: Product sales, equipment, one-off professional services, distribution and wholesale.

Where it leaks: The gap between fulfilment and invoicing. Batch-invoicing weekly rather than on despatch adds days of DSO for no commercial reason, and partial shipments invoiced as complete orders generate short payments. This is the most common and most easily fixed leak in the whole set.

Recurring Billing

A fixed amount charged on a fixed cycle — monthly, quarterly, or annually.

Where it fits: Subscriptions, retainers, maintenance contracts, managed services, SaaS platform fees.

Where it leaks:

• Un-applied escalations. Contracts specifying an annual CPI or fixed-percentage uplift that nobody actions on the anniversary. This is remarkably common and compounds every year it is missed.
• Unbilled amendments. Seats added, scope expanded, or services upgraded mid-term, agreed commercially but never reflected in the billing schedule.
• Silent auto-renewals that lapse. Contracts that end without renewal because no one was tracking the expiry date.
• Proration errors. Mid-cycle changes calculated inconsistently, usually in the customer’s favour.

Usage-Based Billing

Charges calculated from metered consumption — API calls, transactions processed, storage consumed, shipments handled, hours logged.

Where it fits: Infrastructure and platform services, logistics, payment processing, telecoms, anything with a natural consumption unit.

Where it leaks: More than any other model, because billing depends on measurement.

• Incomplete metering. Usage that occurs but is not captured is revenue that cannot be billed, and nobody notices because there is no record of it.
• Untracked tier breaches. Customers exceeding committed volumes without overage charges being applied.
• Rating errors. Complex tiered, banded, or committed-volume pricing applied incorrectly.
• Late data. Usage data arriving after the billing run closes gets deferred to the next cycle — or dropped.

Usage-based billing also generates the most customer disputes, because customers challenge consumption figures they cannot independently verify. Providing transparent usage detail alongside the invoice materially reduces both disputes and the deductions that follow them.

Milestone Billing

Invoicing on completion of defined project stages — typically design, build, delivery, acceptance.

Where it fits: Construction, systems integration, engineering, large implementation projects.

Where it leaks: The trigger. A milestone is reached, the customer signs off, and the billing event depends on someone telling finance. When project managers are measured on delivery rather than on billing, that notification is not a priority. Weeks of delay between achievement and invoicing are routine — pure DSO with no cause other than process.

Retention clauses compound this: a percentage withheld pending final acceptance frequently becomes a permanently aged balance that nobody actively pursues.

Progress Billing

Invoicing a percentage of total contract value based on work completed to date.

Where it fits: Long-duration construction and engineering contracts, extended professional services engagements.

Where it leaks: Measurement disputes. Percentage completion is inherently a judgement, and customers challenge it. Certification cycles introduce further delay, with each round of challenge pushing payment further out. Weak documentation of completion evidence is what turns a routine progress claim into a lengthy dispute.

Choosing a Billing Model

Two practical considerations usually decide it.

Align billing to how the customer derives value. Customers resist paying in a pattern disconnected from the benefit they receive. Usage-based pricing succeeds where consumption tracks value; it fails where usage is unpredictable and customers need budget certainty.

Weigh complexity honestly against the revenue it unlocks. Usage-based billing can capture more revenue than a flat fee, but only if metering is genuinely reliable. A business that cannot measure consumption accurately will lose more to leakage and disputes than the model gains. Hybrid structures — a committed platform fee plus metered overage — are common precisely because they cap the downside of imperfect metering.

Most established businesses end up running several models at once, which is itself the central operational challenge: a single customer may have a recurring platform fee, usage overages, and project milestones, all of which should appear on one coherent invoice rather than three unrelated ones.

Changing Billing Models Without Losing Revenue

Businesses change billing models more often than they expect — moving from perpetual licences to subscriptions, adding usage-based components to a flat fee, or shifting project work from milestone to progress billing. The transition is where revenue most reliably escapes.

Run both models in parallel before switching. Calculate what each customer would be billed under the new model alongside the existing one for at least one full cycle. This surfaces rating errors and metering gaps while the old model is still protecting revenue, rather than after customers have been under-billed.

Migrate contracts deliberately, not in bulk. Customers on legacy terms frequently end up on neither model properly — the old billing schedule is switched off before the new one is fully configured, and a cycle or two simply goes unbilled. Migrate in tranches small enough to reconcile individually.

Preserve the audit trail across the change. When a customer disputes a charge six months later, you need to show which model applied on which date and why. Transitions without clear effective dates generate disputes that are effectively unwinnable.

Expect disputes to spike and staff for it. Any change in how a customer is charged invites scrutiny, even where the amount is unchanged. Providing a clear comparison of old versus new on the first few invoices reduces the deduction volume that otherwise follows, and prevents those balances ageing into the AR aging report as unresolved queries.

A useful discipline during any transition: reconcile total billed revenue against total contracted entitlement monthly rather than quarterly. Leakage introduced by a migration compounds quickly, and a quarterly check can miss two full cycles.

What Billing Automation Actually Needs to Do

Producing an invoice is the easy part. The valuable functions are the ones that guarantee completeness.

Billing triggers that fire from system events. Invoices generated on despatch confirmation, milestone sign-off, or cycle date — not when someone remembers. This alone removes most milestone and one-time leakage.

Contract terms held as structured data. Escalation clauses, renewal dates, committed volumes, tier thresholds, and proration rules stored as enforceable rules rather than as PDF clauses nobody re-reads. An annual uplift held as a rule applies itself.

Complete usage ingestion. Consumption data collected continuously and reconciled against expected volumes, with gaps flagged as anomalies rather than silently under-billing.

Consolidated invoicing across models. One invoice combining recurring charges, usage, and project billing, in the format and delivery channel each customer requires.

Automatic proration and mid-cycle changes. Upgrades, downgrades, and amendments calculated consistently by rule.

Billing completeness reconciliation. The check that matters most: comparing what should have been billed this period — active contracts, recorded usage, completed milestones — against what actually was. This reconciliation is what converts leakage from invisible to visible, and almost no manual process performs it.

Clean handoff into receivables. Billing accuracy is upstream of everything in AR. An invoice that is wrong, incomplete, or missing a PO reference becomes a rejected invoice, a dispute, and an aged balance — which is why billing is the stage of the order-to-cash process where downstream collections problems are usually created.

Peakflo’s invoicing and invoice management handles generation and delivery across models, with billing data flowing directly into collections and cash application.

Finding Revenue Leakage in Your Billing

Step 1: Run a billing completeness reconciliation. Should-have-billed versus did-bill. Start here.

Step 2: Audit contracts for unapplied escalations and amendments. These compound annually.

Step 3: Reconcile metered usage against expected volumes. Gaps are metering failures, not demand drops.

Step 4: Measure the lag between billing event and invoice. Pure DSO with no commercial cause.

Step 5: Convert contract terms into enforceable rules. A rule applies itself; a PDF clause does not.

Step 6: Automate billing triggers from system events. Remove the dependency on someone remembering.

Our Verdict: Billing Is Revenue Assurance, Not Invoice Production

The question most finance teams can answer is “did we send the invoice.” The question that matters is “did we bill everything we were entitled to bill, at the right amount, at the earliest defensible moment” — and almost no manual billing process can answer it, because nothing in the workflow compares contractual entitlement against actual output.

That absence is what makes billing leakage so persistent. It never presents as an error. An unapplied annual escalation, an unmetered usage tier, a milestone signed off in March and invoiced in June — none of these fail loudly. They simply produce an invoice that is smaller or later than it should have been, and the difference is never surfaced because nothing is looking for it.

The verdict is that a billing completeness reconciliation — comparing what should have been billed in a period against what was — is worth more than any other single billing improvement, and it is the first thing to build. Beyond that, contract terms should live as structured, enforceable rules rather than as PDF clauses depending on human memory; an escalation held as a rule applies itself. Revenue recognition requirements under IFRS 15 and FASB standards make contract-level entitlement data necessary for reporting in any case, and coverage from Gartner on billing and revenue management alongside Deloitte research on revenue assurance both treat completeness controls as the differentiator between billing systems that produce invoices and those that protect revenue.

Conclusion

The useful mental shift is to stop treating billing as invoice production and start treating it as revenue assurance. The question is not “did we send the invoice” but “did we bill everything we were entitled to bill, at the right amount, at the earliest defensible moment.”

Most finance teams cannot answer that question today, because nothing in a manual billing process compares entitlement against output.

Request a demo to see how Peakflo automates invoicing across billing models and connects it directly into accounts receivable.

Frequently Asked Questions

What is recurring billing?

Recurring billing charges a customer a fixed amount on a fixed cycle — monthly, quarterly, or annually — under an ongoing agreement such as a subscription, retainer, or maintenance contract. It provides predictable revenue but leaks value through unapplied contractual escalations and mid-term amendments that never reach the billing schedule.

What is usage-based billing?

Usage-based billing calculates charges from metered consumption — API calls, transactions, storage, shipments, or hours. It aligns price closely with delivered value but depends entirely on complete and accurate measurement, making it the model most vulnerable to revenue leakage and customer disputes.

What is the difference between milestone billing and progress billing?

Milestone billing invoices on completion of defined project stages, so a milestone is either achieved or it is not. Progress billing invoices a percentage of total contract value based on work completed to date, which requires a judgement about completion percentage and is therefore more frequently disputed.

What is billing automation?

Billing automation generates invoices from system events rather than manual action, applies contract terms such as escalations and tier thresholds as enforceable rules, ingests usage data continuously, consolidates multiple billing models onto a single invoice, and reconciles what should have been billed against what actually was.

How does billing cause revenue leakage?

Leakage occurs through contractual price escalations never applied, mid-term amendments never added to billing schedules, usage that is consumed but not metered, tier breaches without overage charges, and milestones completed but not invoiced because nobody triggered the billing event. None of these produce visible errors — only smaller or later invoices.

Can a business use more than one billing model?

Yes, and most established B2B businesses do — commonly a recurring platform fee plus usage-based overages plus one-off professional services. The operational challenge is consolidating these onto a single coherent invoice per customer rather than issuing several unrelated ones from different systems.

How does billing accuracy affect collections?

Billing accuracy is upstream of every receivables outcome. An invoice that is incorrect, incomplete, or missing a required purchase order reference gets rejected or disputed, which converts a straightforward collection into an aged balance. A significant share of collections effort is spent resolving problems created at billing.

What is revenue leakage in billing?

Revenue leakage is entitled revenue that is never invoiced or is invoiced at less than the contractual amount. Common sources include unapplied contractual price escalations, mid-term amendments never added to the billing schedule, consumption that occurs but is not metered, tier breaches without overage charges, and completed milestones that were never triggered for billing.

Which billing model is most vulnerable to revenue leakage?

Usage-based billing, because the charge depends entirely on measurement. Usage that occurs but is not captured cannot be billed and leaves no record that anything was missed, so the loss is structurally invisible. It also generates the most disputes, since customers challenge consumption figures they cannot independently verify.

How do you bill a customer who has multiple billing models?

Consolidate recurring charges, usage-based components and project or milestone billing onto a single coherent invoice per customer rather than issuing separate invoices from different systems. Fragmented invoicing increases disputes, complicates cash application, and makes it far harder to establish what the customer actually owes in total.