What is B2B subscription billing?
Invoices, Net Terms, Amendments, and Collections for Business Customers
B2B Subscription Billing: The Complete Guide for Finance and RevOps Teams
By Kuldip Hillyer, Founder & CEO, Kugamon · Published September 15, 2026
B2B subscription billing is the process of invoicing business customers for recurring products and services under a contract — on negotiated payment terms, with purchase order numbers, mid-term amendments, and payment by ACH, card, check, or wire — and reconciling every invoice back to the contract and the ledger. It's invoice-led, contract-led, and finance-reconciled. That's what separates it from the card-on-file billing most people picture when they hear "subscription."
The distinction matters because B2B billing fails in ways B2C billing never does. A consumer subscription is one card, one price, one plan. A business subscription is a 12-month contract with a PO number, Net 30 terms, three seat additions in month seven, a currency finance didn't expect, and a renewal with a price uplift that has to hit the invoice, the CRM, and the revenue schedule at the same time. Get one of those wrong and you get credits, disputes, and slow cash.
This guide covers what B2B subscription billing is, how it differs from B2C, the six billing models businesses actually use, the lifecycle from quote to renewal, what billing software has to do to keep up, how the platform options compare, and where a Salesforce-native platform like Kugamon Subscription Billing fits for teams that run sales and finance on Salesforce.
What Is B2B Subscription Billing and Why Does It Matter?
B2B subscription billing is the operational layer between a signed contract and collected cash. It turns the terms a rep negotiated — products, quantities, prices, term, billing frequency, payment terms — into a billing schedule, generates invoices on that schedule, records payments against them, handles mid-term changes, and hands finance the data it needs to recognize revenue.
Why it matters: in a subscription business, the invoice is the part of the customer experience that finance owns. A late, wrong, or duplicate invoice lands on the desk of the person who signs the renewal. It also decides cash. Business customers pay on terms, so days sales outstanding is set by how fast and how accurately you invoice — and by whether the invoice carries what the customer's AP team needs to approve it: the PO number, the right legal entity, the right tax treatment.
If you want the general definition first, start with What Is Subscription Billing?. This article is about the B2B version.
B2B vs B2C Subscription Billing: What Is the Difference?
The difference is who pays, how, and under what agreement. Consumers pay a card on file at a published price. Businesses pay against an invoice under a negotiated contract. Everything else follows from that.
| Dimension | B2C subscription billing | B2B subscription billing |
| Payment method | Card on file, charged automatically | Invoice paid by ACH, wire, check, or card; sometimes auto-charged from a stored payment profile |
| Payment terms | Paid at the moment of billing | Net 30, Net 45, Net 60 — cash arrives after the invoice |
| Contracts | Terms of service; cancel any time | Signed contract with a term, start date, end date, and renewal clause |
| Amendments | Plan change takes effect next cycle | Mid-term expansions co-termed and prorated to the contract end date |
| Purchase orders | None | PO number required on the invoice or AP won't pay it |
| Tax | Sales tax or VAT applied per consumer | Sales tax, VAT/GST, exemptions, and reverse charge by customer entity and location |
| Currency | Usually one | Multi-currency by customer, often multi-entity |
| Who owns it | Product and growth teams | Finance and RevOps, with sales upstream |
The practical consequence: B2C billing is a payments problem. B2B billing is a data problem. The invoice has to agree with the quote, the contract, the CRM, and the general ledger — and most B2B billing pain comes from those four disagreeing.
The Six B2B Subscription Billing Models
Most B2B companies run more than one of these at once, which is why "what's your billing model?" is the wrong question. The right one is "which of these do you need on the same invoice?"
1. Flat recurring fee
A fixed amount per period for a defined scope — a platform fee, a support plan, a managed service. Simple to invoice, simple to recognize. The complexity only shows up in amendments and renewals.
2. Per-seat pricing
Quantity times unit price per period. The billing question is what happens when quantity changes mid-term: prorate the added seats to the contract end date, true up at renewal, or bill from the next cycle? Pick one and make the system enforce it.
3. Tiered and volume pricing
Unit price changes with quantity bands — the first 50 seats at one rate, the next 200 at another. Tiered pricing needs to live on the price book, not in a spreadsheet, so quotes, amendments, and renewals all compute it the same way.
4. Usage and overage, including per-API-call
You meter something — API calls, transactions, gigabytes, messages — and bill in arrears at a rate, often above an included allowance. This is where "flat fee per API call" pricing lives. Usage billing needs a metering source, a rating step that converts usage into money, and an invoice line that shows the customer what they consumed. High-volume metering is a specialist capability; ask any vendor for a load reference, not a demo.
5. Hybrid: base plus usage
A recurring platform fee billed in advance plus usage billed in arrears — common in infrastructure, data, and communications software. The invoice carries both on different timing, and revenue recognition treats them differently.
6. One-time plus recurring
Implementation fees, hardware, training, or professional services on the same order as the subscription. One-time lines invoice once or on milestones; recurring lines invoice on schedule. Both should come from one order so the customer sees one coherent picture.
The B2B Subscription Billing Lifecycle
Every B2B subscription moves through the same six stages. The test of a billing system is whether each stage feeds the next without someone re-keying it.
1. Quote
Sales configures products, quantities, term, and pricing, and the customer accepts. The quote is the source of truth for everything downstream; if it's built in one system and the billing schedule in another, you've created your first reconciliation job. See what quote-to-cash means for the full chain.
2. Order and contract
The accepted quote becomes an order, and the order creates or updates the contract — start date, end date, term, payment terms, PO number, billing contact. The contract is the container that every later invoice, amendment, and renewal refers back to.
3. Subscription and billing schedule
Each recurring line becomes a subscription with its own quantity, price, and dates, and the system generates the billing schedule — monthly, quarterly, annual in advance, usage in arrears. This is the step standard CRM objects don't do on their own.
4. Invoice
Invoices generate on the schedule with the PO number, payment terms, due date, tax, currency, and any credits or additional charges. Amendments generate prorated invoices or credits from the change date. A good system shows how many days an invoice is past due without anyone running a report.
5. Payment: ACH, card, check, or wire
Business customers pay the way their AP team pays. Card and ACH payments run through a gateway; wire and check payments get recorded against the invoice; one payment often applies to several invoices. Failed or missing payments trigger collections — reminders, statements, escalation — against the invoice, not just a card retry.
6. Renewal
Before the contract ends, the renewal is quoted with any uplift, accepted, and released, which extends or replaces the contract and starts the next billing schedule. If the renewal is discovered rather than scheduled, the gap between the old term and the new one is where revenue leaks. Details: how to automate subscription renewals.
What B2B Subscription Billing Software Must Do
Use this as the minimum checklist. Any platform that can't do all of these natively hands the gap to your finance team as a manual process.
- Net payment terms and due dates. Payment terms on the order and the invoice, due dates calculated from them, and an aging view of what's past due.
- PO numbers on invoices. Captured on the order, printed on every invoice. AP departments reject invoices without them.
- ACH and card. Gateway card and ACH payments, stored payment profiles for recurring charges, plus a clean way to record wire and check payments — including one payment applied across several invoices.
- Multi-currency. Quote, invoice, and collect in the customer's currency, with reporting that rolls up to yours.
- Sales tax and VAT/GST. Location-based US sales tax, international VAT/GST by country and rate, exemption flags at the account level, and effective-dated rate changes.
- Credits and adjustments. Credit memos and additional-charge lines against an invoice for downgrades, disputes, and corrections — with an audit trail, not an edited invoice.
- Dunning for invoices, not just cards. B2C dunning retries a card. B2B dunning chases an invoice: reminders before and after the due date, statements, and a record of who was contacted and when.
- Revenue recognition under ASC 606. Revenue from a contract is recognized as performance obligations are satisfied, not when the invoice is sent or paid — the five-step model in FASB ASU 2014-09. Your billing system should produce revenue schedules from the order or invoice so finance isn't rebuilding them in a spreadsheet.
- Amendments with proration and co-terming. Add seats in month seven and get a prorated invoice to the contract end date, an updated subscription, and an updated renewal — from one action.
How the Platform Options Compare
Three architectures cover most of the B2B market. They differ less on features than on where the billing data lives and whether quoting is part of the same system.
| Option | Where billing data lives | Quoting included? | Published pricing | Best for |
| Kugamon Subscription Billing | Native Salesforce records on the standard Product and Price Book — quotes, orders, contracts, subscriptions, invoices, and payments in one package family | Yes — CPQ, orders, invoicing, payments, subscriptions, and renewals in one data model | $125/user/mo; 10-user minimum; fixed-fee implementation — AppExchange listing | SMB and mid-market teams running sales and finance on Salesforce |
| Revenue Cloud Advanced + Revenue Cloud Billing (Salesforce) | Native Salesforce records on Salesforce's new revenue data model | Yes — RCA covers configure through order; Revenue Cloud Billing is a separate product | RCA $200/user/mo ($150 Growth), billed annually — Salesforce pricing; Billing not published | Enterprises standardizing on Salesforce's first-party revenue platform |
| Standalone billing platform (Zuora, Chargebee) synced to the CRM | The billing vendor's platform; a synced summary in Salesforce | Usually no — quoting stays in the CRM or a separate CPQ, kept in line by a sync | Not published — contact vendor | Finance-led organizations whose billing complexity outruns any CRM-side platform |
In a Salesforce-native platform, the lifecycle above is a chain of native records: releasing an order creates the contract, subscriptions, and renewal opportunity; invoices generate from the order on schedule with the customer PO number and payment terms; card and ACH payments run through the connected gateway — Kugamon processes ACH through its Authorize.Net (eCheck) and Stripe (ACH Direct Debit) connections — while wire and check payments are recorded against the invoice; and every one of those records shows up in standard Salesforce reports. For a six-vendor comparison, see the best CPQ with subscription billing; for the cost model on Salesforce's own option, see how much Revenue Cloud Advanced costs.
B2B Billing Metrics to Track
Four metrics tell you whether billing is working. None has a universal benchmark — track your own trend and set targets against it.
| Metric | Formula | What it tells you |
| Invoice accuracy rate | Invoices issued without a correction or credit ÷ total invoices issued × 100 | How often the invoice agreed with the contract the first time |
| Days sales outstanding (DSO) | (Accounts receivable ÷ credit sales in the period) × days in the period | How long cash takes to arrive after you invoice; rises when invoices are late, wrong, or missing the PO |
| Billing-related credits and churn | Credit memo value (or churned ARR with a billing-related reason) ÷ billed revenue in the period × 100 | How much revenue billing errors and disputes are giving back |
| Invoices auto-generated | Invoices created by schedule or automation ÷ total invoices × 100 | How much of billing still depends on someone remembering |
For the wider subscription metric set — MRR, ARR, net revenue retention, churn — see how to measure subscription metrics.
Common B2B Subscription Billing Mistakes
- Running B2B billing on a B2C tool. If the platform's core loop is "charge the card," net terms, PO numbers, and invoice-level collections are bolted on — and you'll feel every bolt.
- Quoting in one system and billing in another. Every discount, term, and amendment has to survive the sync. Ask where the subscription record lives, then run a report on it.
- Treating amendments as exceptions. Mid-term changes are the normal case in B2B. If proration and co-terming are manual, you'll under-bill expansions and over-credit downgrades.
- Letting renewals surprise finance. The renewal should exist as a record from day one, with notices and orders on a schedule. A renewal found in a report thirty days out is already late.
- Ignoring revenue recognition until close. If revenue schedules aren't produced from the order or invoice, finance rebuilds them at month-end from whatever the billing system exported.
- Comparing license price instead of three-year cost. Implementation, integration, and the second product you didn't count decide the real number. Model it on the 3-year cost calculator.
Frequently Asked Questions
Q: What is B2B subscription billing?
B2B subscription billing is the process of invoicing business customers for recurring products and services under a contract, on negotiated payment terms, with purchase order numbers, mid-term amendments, and payment by ACH, card, check, or wire. It's invoice-led and contract-led, and every invoice reconciles back to the contract and the ledger.
Q: How is B2B subscription billing different from B2C?
B2C billing charges a card on file at a published price with no contract. B2B billing issues invoices under a signed contract, on net terms, with PO numbers, mid-term amendments, multi-currency, and tax by entity and location. B2C is mostly a payments problem; B2B is mostly a data problem — the invoice has to agree with the quote, the contract, the CRM, and the ledger.
Q: What billing models do B2B subscription companies use?
Six models cover most cases: flat recurring fees, per-seat pricing, tiered and volume pricing, usage and overage (including per-API-call), hybrid base-plus-usage, and one-time plus recurring. Most B2B companies combine several on one order, so the billing system needs to handle them on the same invoice.
Q: Does B2B subscription billing software need to support ACH?
Yes. Many business customers pay invoices by ACH, wire, or check rather than card, so the billing system needs to record those payments against invoices, apply one payment across several invoices, and keep the account balance current. Card payments through a gateway and stored payment profiles matter too, but they're not enough on their own for B2B.
Q: How does B2B subscription billing handle mid-term changes?
Through amendments. An expansion adds lines that are co-termed to the existing contract end date and prorated from the change date, producing a prorated invoice, an updated subscription, and an updated renewal. A downgrade produces a credit or a reduced schedule. The key is that one action changes all three records together.
Q: What is dunning in B2B billing?
Dunning is the collections process for unpaid invoices: reminders before and after the due date, statements, escalation, and a record of every contact. In B2C it usually means retrying a failed card. In B2B it means chasing an invoice on net terms, so the system needs invoice-level aging and contact history, not just a card retry schedule.
Q: How does B2B subscription billing relate to ASC 606?
ASC 606 (FASB ASU 2014-09) says revenue from a customer contract is recognized as performance obligations are satisfied, not when the invoice is issued or paid. For subscriptions, that usually means recognizing ratably over the service period. Your billing system should produce the revenue schedule from the order or invoice so finance doesn't rebuild it by hand.
Q: Can you run B2B subscription billing inside Salesforce?
Yes. Salesforce sells Revenue Cloud Advanced with Revenue Cloud Billing as a separate product, and Salesforce-native AppExchange packages such as Kugamon store quotes, orders, contracts, subscriptions, invoices, and payments as native Salesforce records. External billing platforms such as Zuora and Chargebee can also sync summaries into Salesforce, with the billing system of record living on the vendor's platform.
Next Steps
Start by listing which of the six billing models you need on the same invoice, then demo the amendment: add seats mid-term and follow the change to the invoice, the renewal, and the revenue schedule. If you'd like to see all of it as native Salesforce records, explore Kugamon Subscription Billing, read What Is Subscription Billing? and the best CPQ with subscription billing, or schedule a demo and bring a real invoice with a PO number on it. No pitch — just a working billing run on your own terms.