B
Glossary
Billing in Arrears
Billing in arrears is a billing model where a company invoices a customer after the service period ends, once the quantity consumed is known. Usage-based and metered products bill this way by necessity, because the amount owed doesn't exist until the period closes.
Key Takeaways
Arrears billing invoices after delivery. Being in arrears means paying late. The two share a word and nothing else.
Metered pricing can't bill in advance, because you can't price consumption that hasn't happened yet.
On a $10,000 monthly contract, moving from advance to arrears with net-30 terms pushes collection from day 31 to day 61, a 30-day working capital gap.
Most real invoices are split: the fixed platform fee bills in advance, the metered portion bills in arrears, on one document.
Arrears billing needs a defined close, because usage that lands after you invoice forces a credit memo or a re-rate.
Why does usage-based pricing force billing in arrears?
Usage-based pricing has no choice about arrears, because the billable quantity only exists after the customer consumes it. A subscription knows its price on day one. A metered charge doesn't know its price until the meter stops.
What has to happen before an arrears invoice can be correct:
The period closes and event ingestion stops accepting events for that window.
Aggregation sums the events into a quantity per meter.
Rating applies the price, producing rated usage.
Credits, discounts, and minimums resolve against the rated total.
The invoice finalizes and leaves draft.
Skip step 1 and the number moves after you've sent it. The full pipeline is walked end to end in Flexprice's guide to usage based billing. That's why arrears billing depends on a watermark or a hard cutoff rather than a wall-clock date, and why teams that bill metered usage keep the invoice in draft for a few days after the period ends.
Billing in arrears vs billing in advance: what changes for cash flow?
Arrears billing delays cash by one full billing period compared with billing in advance, and that's the entire tradeoff. The revenue is identical. The timing isn't.
The same $10,000 monthly contract under both models, with net-30 terms:
Event | Billing in advance | Billing in arrears |
|---|---|---|
Service period | Day 1 to day 30 | Day 1 to day 30 |
Invoice issued | Day 1 | Day 31 |
Payment due | Day 31 | Day 61 |
Cash collected for month 1 | Day 31 | Day 61 |
Days from service start to cash | 30 | 60 |
The consequence nobody prices in: arrears billing means you carry the cost of delivery before you collect for it. For an AI product paying inference costs on day 3 and collecting on day 61, that gap is real money, and it's the reason prepaid credits exist as a model. Credits let a metered product collect in advance and still meter in arrears.
Arrears also shifts credit risk. Bill in advance and the invoice exists before the service does, so a customer who vanishes mid-period has at least been billed. Bill in arrears and a customer who disappears on day 29 has consumed a month you never invoiced at all, which is why spending caps matter more under arrears than under advance.
Can one invoice do both?
Yes, and most enterprise invoices do. Splitting the document by charge type is standard practice, not a workaround.
A typical hybrid invoice issued on 1 March:
The $2,000 platform fee for March, billed in advance for the period starting that day.
$840 of API overage for February, billed in arrears against closed and reconciled usage.
A $500 credit grant applied against the combined total.
The two halves reference different periods on the same document, which confuses customers unless the invoice labels each line with the period it covers. I've seen more support tickets come from unlabeled period boundaries than from pricing disputes. Print the service period on every line, which Billing and Invoicing does on the split document by default.
Related terms
Arrears is a timing decision, so the neighbouring terms are the ones that define the window and the number.
Billing period is the window an arrears invoice covers and closes against.
Draft invoice is the state an arrears invoice sits in while late usage still lands.
Rated usage is the priced quantity that only exists once the period ends.
Usage reconciliation confirms the arrears number is right before anyone sends it.
Consumption-based pricing is the pricing model that makes arrears mandatory.
FAQ
Does billing in arrears mean the customer is paying late?
No. Billing in arrears describes when you issue the invoice, and being in arrears describes a customer who has missed a due date. An arrears invoice sent on day 31 for a period ending day 30 is perfectly on time. The overlap in wording is the single most common confusion around the term.
Is billing in arrears the same as postpaid?
Effectively yes, in billing contexts. Postpaid is the telecom word for the same arrangement: consume first, get invoiced after the cycle closes. Prepaid is its opposite and works by drawing consumption against a balance the customer funded up front.
How soon after the period ends should an arrears invoice go out?
Late enough that usage has settled and early enough that payment terms don't slip. Teams billing high-volume metered usage typically hold the invoice in draft for two to five days after the period closes, which covers most late-arriving events without pushing the due date into the next cycle.
Can you charge interest on arrears billing?
That's a payment terms question rather than a billing model question. Late fees attach to an invoice that passed its due date, regardless of whether the invoice was issued in advance or in arrears.
Back to glossary
