Marketplace Bookings vs Billings: Four Numbers

Bookings, billings, collected and disbursed are four different marketplace revenue numbers, not four estimates of one. Each counts a different thing, and bookings is not even dated by the same event as the other three, so the finance meeting where “we booked $X but billed less” turns into an argument is really a meeting where four correct numbers were mistaken for one.

---

Finance says you booked a certain number on marketplace this quarter. RevOps says you billed less. Someone opens a third report and finds a third figure. Nobody is wrong, and that is exactly why the meeting goes in circles: the three people are quoting three different measures, each taken at a different stage of the deal, and treating them as rival answers to one question.

There are four numbers worth naming precisely — bookings, billings, collected, disbursed — and the trap is the first pair. Collected and disbursed are about cash, and their gap is intuitive: money takes time to arrive. Bookings and billings are about commitment versus invoice, they are keyed on different dates, and their gap can run the counterintuitive way — billings can exceed bookings in a quarter, which looks like an error and is not.

This post is about that first gap. The invoiced-collected-disbursed cash story is covered in cloud marketplace metrics, and why three consoles disagree in why your marketplaces report different numbers. Here we stay on what bookings is, why it is not billings, and how to read the ratio between them.

---

What are bookings, billings, collected, and disbursed?

The four numbers describe a marketplace deal at four moments: what the customer committed to, what got invoiced, what cash arrived, and what reached your bank. Fours’ Revenue workspace defines each as a separate measure, with its own rule for what counts and a stated date that places it in a period, which is what makes the following table possible rather than hand-wavy. Take each in turn.

Bookings is the committed contract value from entitlement terms that start in the period. A new, renewal, or upsell term counts at its full contract value; a plan or quantity change counts only its incremental difference from the term it amends. The date that places a booking in a period is the term start date — not when you signed, not when the invoice was issued, but when the entitlement begins. Bookings answers “how much did customers commit to, for terms beginning now?”

Billings is the net revenue of the records that have actually been invoiced. A record is billed once it carries an invoice amount, an invoice date, or any later lifecycle stage. The date that places a billing in a period is the invoice date, and the figure is net of refunds — a voided or canceled record counts as zero. Billings answers “how much was actually invoiced this period?”

Collected is the revenue on records that have reached the cash stage: a collected date or amount, a paid or partially paid marker, or a disbursement already recorded. Each record counts at its invoice amount, so a partly paid invoice counts in full, and the figure is cumulative: a record stays counted as it moves on to disbursement. Collected is placed in a period by the invoice date, the same as billings, so a quarter’s collected figure is that quarter’s invoices that have been paid so far, in full or in part. Collected answers “how much of what was invoiced has been paid?” That is close to what customers have paid, but not identical: a record that has been paid out counts even when the marketplace paid you before collecting from the buyer, as Microsoft often does on Enterprise Agreement sales.

Disbursed is the amount on records that carry a disbursement stage, date, or amount — the money that reached your account, net of the marketplace’s channel fees. Fees come out here, not at the collected stage, so disbursed is the only one of the four that is already net of what the marketplace kept. It too is placed in a period by the invoice date: a quarter’s disbursed figure is what has been paid out so far on that quarter’s invoices. Disbursed answers “how much actually landed in our bank?”

---

The four stages as a table

Read each row as measure → what it counts → the date that places it in a period → the ratio to the stage above it. The ratios are how you read the funnel, and the first one is the one that surprises people.

Measure	What it counts	The date that places it in a period	Ratio to the previous stage
Bookings	Committed contract value from entitlement terms that start in the range; plan and quantity changes count only their incremental difference	Term start date	— (this is the top of the funnel)
Billings	Net revenue of records that have been invoiced (invoice amount, invoice date, or a later stage), net of refunds	Invoice date	Billings ÷ Bookings = % of bookings invoiced — can exceed 100%
Collected	Records with a collected date or amount, a paid or partially paid marker, or a disbursement, each at its invoice amount; cumulative as they move to disbursement	Invoice date	Collected ÷ Billings = % of billings collected
Disbursed	The disbursed amount that reached your account, net of the marketplace’s channel fees	Invoice date	Disbursed ÷ Collected = % of collected cash paid out

The two lower ratios normally sit below 100% and climb as time passes — invoices get paid, cash gets disbursed — though the paid-out ratio levels off below 100% on channels that keep a fee, because disbursed is net of it. They behave that way because billings, collected and disbursed share one clock: all three count the records invoiced in the period, so collected and disbursed are the paid and paid-out parts of the same invoices. The top ratio is the odd one, because bookings and billings are not two readings of one pipeline taken at different times. They are keyed on different dates entirely, so within any single quarter there is no arithmetic rule that billings must be smaller.

On the Overview, four separate dates do appear in one place: the Revenue Trend chart, which places each series on the timeline by its own date. Bookings sit at the term start and billings at the invoice date, as in the table; collected falls back from the collected date through the disburse, payment-due and invoice dates, and disbursed from the disburse date to the provider’s last update, then the record’s own. So a record can land in a different bucket on the chart from the period whose totals count it.

---

Why can billings exceed bookings? A worked example

Billings can exceed bookings in a period because the two are dated on different events — invoice date versus term start date — so a quarter can invoice contracts that began in an earlier quarter. The ”% of bookings invoiced” ratio compares this period’s invoices against this period’s newly starting commitments, and there is no reason those two sets describe the same contracts.

Walk it through with Acme Corp, a fictional ISV selling on AWS Marketplace.

• Q1. Acme closes a large annual private offer, paid in installments, with a customer whose entitlement term is set to start on the first day of Q2. That full contract value lands in Q2 bookings, because bookings is dated on the term start. Nothing about it is in Q1 bookings.
• Q2. The term begins. AWS, not Acme, invoices the buyer, on the dates Acme set in the offer’s payment schedule, and the contract’s first installment is dated in Q2 — so it lands in Q2 billings. AWS also invoices Q2 installments on several smaller Acme contracts whose terms started back in Q1. Those contributed to Q1 bookings, but their invoices are dated Q2, so they land in Q2 billings too.

Now total Q2. Bookings holds one big new commitment. Billings holds that same contract’s first invoice plus the Q2-dated invoices for deals that were booked in Q1. Stack enough invoiced-in-Q2, booked-in-Q1 value on top and Q2 billings exceeds Q2 bookings — the ratio prints above 100%. No number is wrong. The period simply invoiced against contracts it did not newly book, which is the normal state of any business with a backlog.

The practical reading: a ”% of bookings invoiced” above 100% is usually a timing signal (prior-period commitments are still being invoiced), not a data error and not double-counted revenue. Below 100% is just as ordinary, for the mirror-image reason: a contract on an installment plan books its full value in the quarter its term starts, but is invoiced on the dates in its payment schedule, which can spread across the whole contract, so that quarter bills only the installments dated within it. Neither side of 100% is an error on its own. The ratio mostly reflects how your payment schedules line up with your term start dates, plus any usage billed with no contract value behind it.

---

How does a downgrade lower bookings?

A downgrade lowers bookings because a plan or quantity change counts only its change against the term it amends, and a reduction is a negative change. Bookings does not re-book the whole contract when a customer changes its plan or quantity; it books the delta. An expansion adds its increase, and a downgrade — fewer seats, a cheaper plan — subtracts, so the contract value attributed to the amending period goes down. Renewals and upsells work differently: they are renewal terms (a manual renewal also covers an upsell), and a renewal term counts at its full contract value. One display detail: the Revenue Trend chart leaves negative values out, so a downgrade lowers the Bookings card but adds no bar.

That rule keeps bookings honest in both directions. If every plan or quantity change re-counted the full contract, a customer who cut their plan in half could still look like a fresh full-value booking, and the number would drift upward on churn. Counting only the incremental difference means an expansion reads as growth and a contraction reads as a reduction — which is what a controller needs bookings to mean.

This is also the cleanest way to see that bookings is not recognized revenue and not your invoiced total. It is the commitment line, measured at the term. The reconciliation between that commitment line and the cash that eventually arrives — across marketplaces that each report a different state of the same dollar — is its own discipline, and one the reconciliation post linked above works through.

---

One caution: “Booked” is not “Bookings”

Fours’ Revenue workspace carries a Revenue Recognition view with a trend labeled Booked, and it is a different measure from the Bookings card — do not read one as the other. Booked on the Revenue Recognition page is invoiced revenue, reported by invoice month in a USD base and before refunds. Recognized revenue is another series on the same page, Recognized. Bookings is committed contract value, dated on the term start. Same four letters at the root, opposite ends of the lifecycle: one is what was invoiced, the other is what was committed.

Two notes on scope. These are Fours’ own metric definitions, not a marketplace’s rule — AWS, Microsoft and Google Cloud each measure and name their money differently, which is the subject of the reconciliation post linked above. And the Revenue workspace is an analytics surface inside the Fours console; its views are not exposed through a public API, so these numbers are read in the product, not queried programmatically.

---

Frequently asked questions

What is the difference between bookings and billings on cloud marketplaces? Bookings is committed contract value from entitlement terms that start in the period, dated on the term start. Billings is net revenue of records actually invoiced, dated on the invoice date. They count different things on different dates.

Why can billings exceed bookings in a quarter? Because they are dated on different events. A quarter’s billings include invoices for contracts that started in earlier quarters, while its bookings count only terms newly starting now. So a period can invoice more than it newly books — the ratio runs above 100%.

Which number is “right” when finance and RevOps disagree? All of them, for different questions. Bookings answers what customers committed to; billings, what was invoiced; collected, which of those invoices have been paid, in full or in part; disbursed, what reached your bank. The fix is naming which measure each figure is, not reconciling them to one.

How does a downgrade affect bookings? It lowers them. A plan or quantity change counts only its difference from the term it amends, so a reduction is a negative amount. An expansion adds its increase and a downgrade subtracts its decrease; renewals and upsells are renewal terms, counted in full.

Is “bookings” the same as recognized revenue? No. Bookings is committed contract value, dated by the entitlement term start, whenever the invoices fall. Recognized revenue is spread over the periods it is earned in: the “Recognized” series on Fours’ Revenue Recognition view. That view’s “Booked” series is invoiced revenue by invoice month, not the Bookings card.

What date places each number in a period? Two dates. Bookings uses the term start date; billings, collected and disbursed all use the invoice date, so collected and disbursed are the paid and paid-out parts of that period’s invoices. On the Overview, only the Revenue Trend chart places collected and disbursed by dates of their own.

---

Takeaways

• Bookings, billings, collected and disbursed are four measures, not four estimates of one. Each counts a different thing; bookings is dated by the term start, the other three by the invoice date.
• Bookings is committed contract value dated on the term start; billings is invoiced net revenue dated on the invoice date. They are not the same pipeline read twice.
• ”% of bookings invoiced” can exceed 100% — a quarter invoices contracts that started in earlier quarters. That is usually a timing signal, not an error.
• A downgrade lowers bookings because a plan or quantity change counts only its incremental change, and a reduction is negative. Renewals and upsells count in full.
• “Booked” on the Revenue Recognition view is invoiced revenue by invoice month — a different number from the Bookings card. Don’t conflate them.

---

When finance and RevOps quote different marketplace numbers, the answer is a shared definition and one place each measure is computed the same way. In Fours, the Revenue Overview shows bookings, billings, collected and disbursed side by side, and its documentation states the formula behind each. See marketplace reporting in Fours for the rest of the reporting layer.