Per-Invoice Pricing: Examples & Companies

What is it

Per-Invoice Pricing is a billing unit used by billing infrastructure platforms where each invoice generated or processed is metered as a cost driver. The invoice is the deliverable these platforms produce — every subscription renewal, usage charge, or one-off bill becomes an invoice their software creates, tallies, and sends — so metering it ties the vendor’s fee to the artifact its product exists to generate.

Across the corpus the invoice plays two roles. For a minority it is a genuine per-unit charge that follows the buyer into the paid tier. For most it is a free-tier gate: a startup runs the product free up to a fixed invoice count, then crosses to a platform fee that ignores invoice volume once committed.

The reason “invoices” rarely survives as the paid meter is that it is a poor cost proxy — a $9 SaaS receipt and a $90,000 enterprise invoice take the same platform work. Vendors like Chargebee and Maxio list invoices as a dimension but bill on billings volume or a percentage of revenue instead. This page collects the seven companies that expose invoices as a billing dimension and shows where each draws that line. For the foundations, see the introduction to usage-based pricing.

How it works

An invoice meter can be structured three ways, and the seven companies here use all three:

Worked example — Stripe Billing Invoicing Starter. Suppose a business collects 200 paid invoices totaling $50,000 in a month. At 0.4% per paid invoice, the Invoicing line is 0.4% × $50,000 = $200/month. Because Stripe charges only on paid invoices, unpaid or voided invoices cost nothing — the meter is aligned with collected revenue, not sent volume. Note this stacks on top of payment processing (roughly 2.9% + 30¢ per US card charge), so the all-in cost is higher than the invoicing line alone.

Worked example — the free-invoice gate. On Hyperline, a startup can issue its first 10 invoices with no credit card, then moves to $199/month + 0.6% of billed revenue on the Quote to Cash tier. The invoice count decides when you start paying; the revenue percentage decides how much. Alguna draws the same gate at $0 for up to 10 invoices/month, then jumps to a flat $699/month — with unlimited events and seats — so past the gate the invoice count stops mattering entirely. The usage invoicing and billing cycles guide covers the implementation mechanics behind these meters.

Companies using this

Seven billing and quote-to-revenue platforms in the corpus list invoices as a billing dimension. All seven sit in the billing-infrastructure and finance-tooling category, and the table below shows how each pairs invoices with platform fees, revenue percentages, or free-tier gates.

Patterns observed

The strongest pattern is that the invoice is a free-tier gate, not the paid meter. Hyperline and Alguna both use the invoice count only to let a finance team run the product end-to-end before paying, then cross to a platform fee that ignores invoice volume. Stripe Billing is the lone company that carries the invoice as a genuine per-unit charge into the paid range.

The second pattern is a category-wide preference for revenue as the value metric over raw invoice count. Chargebee charges 0.75% on billings above a threshold, Maxio bands a flat fee by billings volume, and Sequence sets its platform fee on projected billed revenue. The shared logic: a billing platform already sits on the money flow, so a slice of revenue is a friction-free, self-aligning meter that doesn’t penalize a customer for sending many small invoices. Invoices stay in the frontmatter as what the product physically produces, but the dollar amount, not the count, moves the bill.

Counterexamples & variants

The sharpest counterexample is Zenskar, which lists invoices as a dimension yet prices on the opposite principle. Its pricing FAQ states, verbatim, “We don’t charge a % of your revenue” — Zenskar sells three custom-quoted tiers differentiated by support depth, not by invoice count or revenue, explicitly rejecting the meter its competitors use. Alguna makes the same swipe from the self-serve end: its flat fee covers unlimited events, so the thing it sells — metering — is exactly the thing it refuses to charge by.

For this category, per-invoice pricing is more marketing surface than billing engine. The vendors that lean hardest into predictability — Zenskar, Alguna, and Sequence — deliberately decouple their own price from the invoices and revenue they process, betting that finance buyers who hate variable software bills will pay a flat fee for that certainty.

What this means for buyers vs vendors

For buyers

Read past the “invoices” label to find the real meter. If you send high-volume, low-value invoices (monthly SaaS receipts), a percentage-of-revenue model can quietly exceed a flat-fee vendor’s bill — model both before committing. If you send low-volume, high-value enterprise invoices, a flat platform fee (Alguna, Zenskar’s quoted tiers) usually wins. Use a free-invoice gate (Hyperline, Alguna) to run a real end-to-end test, and see revenue recognition for usage-based pricing before you finalize.

For vendors

Pricing on invoice count is legible but leaves value on the table, since invoice size varies enormously — which is why most of the corpus meters revenue instead. If you adopt an invoice count, reserve it for the free-tier gate (a concrete, honest unit to run trials on) and switch to a value metric — billed revenue or billings volume — for the paid tiers. And know your positioning: a flat, no-revenue-share promise (Zenskar, Alguna) is a real differentiator to buyers burned by billing tools that tax their growth. Model your own margin with the pricing calculator hub.

Explore this theme in the knowledge graph →