--- title: "Marketplace Bookings vs Billings: Four Numbers" url: https://www.suger.io/resources/blog/bookings-billings-collected-disbursed/ canonical: https://www.suger.io/resources/blog/bookings-billings-collected-disbursed/ type: Blog description: "Marketplace bookings vs billings, collected and disbursed: what each of the four revenue numbers counts, its date, and why billings can exceed bookings." --- # Marketplace Bookings vs Billings: Four Numbers > Canonical HTML version: https://www.suger.io/resources/blog/bookings-billings-collected-disbursed/ 1. [Home](/) 2. / 3. [Resources](/resources/) 4. / 5. [Blog](/resources/blog/) 6. / 7. Marketplace Bookings vs Billings: Four Numbers # Marketplace Bookings vs Billings: Four Numbers Bookings, billings, collected, disbursed: four marketplace revenue numbers, the date that places each in a period, and why billings can exceed bookings. [![Shirley Guo](/authors/shirley-guo.jpg)](/resources/blog/author/shirley-guo/) [Shirley Guo](/resources/blog/author/shirley-guo/) Sep 30, 2026 ![Marketplace Bookings vs Billings: Four Numbers](/images/blog/bookings-billings-collected-disbursed/hero.png) Explore AI Summary [![](/logos/company/openai.svg)](https://chat.openai.com/?q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Fbookings-billings-collected-disbursed%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Billing%20%26%20Metering%2C%20Cloud%20GTM. "Summarize with ChatGPT")[![](/logos/company/anthropic.svg) ](https://claude.ai/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Fbookings-billings-collected-disbursed%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Billing%20%26%20Metering%2C%20Cloud%20GTM. "Summarize with Claude")[![](/logos/company/gemini.svg)](https://www.google.com/search?udm=50&aep=11&q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Fbookings-billings-collected-disbursed%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Billing%20%26%20Metering%2C%20Cloud%20GTM. "Summarize with Gemini")[](https://www.perplexity.ai/search/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Fbookings-billings-collected-disbursed%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Billing%20%26%20Metering%2C%20Cloud%20GTM. "Summarize with Perplexity") Table of Contents - [What are bookings, billings, collected, and disbursed?](#what-are-bookings-billings-collected-and-disbursed) - [The four stages as a table](#the-four-stages-as-a-table) - [Why can billings exceed bookings? A worked example](#why-can-billings-exceed-bookings-a-worked-example) - [How does a downgrade lower bookings?](#how-does-a-downgrade-lower-bookings) - [One caution: “Booked” is not “Bookings”](#one-caution-booked-is-not-bookings) - [Frequently asked questions](#frequently-asked-questions) - [Takeaways](#takeaways) _Bookings, billings, collected and disbursed are four different marketplace revenue numbers, not four estimates of one. Each counts a different thing on a different date, 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 on a different clock, 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](/resources/blog/cloud-marketplace-metrics/), and why three consoles disagree in [why your marketplaces report different numbers](/resources/blog/marketplace-revenue-reconciliation/). 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. Suger’s Revenue workspace defines each as a separate measure with its own date field, 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 you invoiced, 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 did we actually invoice this period?” **Collected is the revenue on records the marketplace has marked paid, in full or in part.** It is cumulative: a record stays counted as it moves on to disbursement. The date is the collected date where present, falling back through disburse date, payment due date, and finally invoice date. Collected answers “how much has the customer actually paid?” **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. 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; 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 the marketplace has marked paid or partially paid; cumulative as they move to disbursement Collected date (then disburse, payment-due, invoice) Collected ÷ Billings = % of billings collected **Disbursed** The disbursed amount that reached your account, net of the marketplace’s channel fees Disburse date (then provider update) Disbursed ÷ Collected = % of collected cash paid out The three lower ratios normally sit below 100% and climb toward it as time passes — invoices get paid, cash gets disbursed. 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. * * * ## **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 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. Acme invoices the first period of that contract, and the invoice date falls in Q2 — so it lands in **Q2 billings**. Acme also invoices several smaller 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 (you are working through invoicing on prior-period commitments), not a data error and not double-counted revenue. A number persistently _below_ 100% across several quarters is the one worth a look — it can mean new commitments are outrunning your ability to invoice them, or that terms are starting well ahead of their first invoice. * * * ## **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 amends it; it books the _delta_. A renewal or upsell adds its incremental value, and a downgrade — fewer seats, a cheaper plan, a reduced commitment — subtracts, so the contract value attributed to the amending period goes down. That rule keeps bookings honest in both directions. If every amendment 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”** Suger’s 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.** 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 Suger’s 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 Suger 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 you invoiced; collected, what customers paid; 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 incremental difference against the term it amends, so a reduction is a negative amount. Upsells add their delta; downgrades subtract theirs. **Is “bookings” the same as recognized revenue?** No. Bookings is a commitment measured at the entitlement term start, before anything is invoiced. Recognized or invoiced revenue is a later, separate measure — on Suger’s Revenue Recognition view it appears as “Booked,” invoiced revenue by invoice month, which is not the same as the Bookings card. **What date places each number in a period?** Bookings uses the term start date; billings uses the invoice date; collected uses the collected date (falling back to disburse, payment-due, then invoice date); disbursed uses the disburse date. Four measures, four clocks. * * * ## **Takeaways** - Bookings, billings, collected and disbursed are four measures, not four estimates of one. Each counts a different thing on its own 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 a timing signal, not an error. - A downgrade lowers bookings because an amendment counts only its incremental change, and a reduction is negative. - “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. See how [billing and metering in Suger](/platform/billing-metering/) holds offers, entitlements, invoices and disbursements at one grain — so bookings, billings, collected and disbursed are each their own number, on their own date. ## Keep reading - [Cloud GTMInstrumenting Your Marketplace Motion for 2027Aug 27, 2026](/resources/blog/instrumenting-your-marketplace-motion-for-2027/) - [Billing & MeteringUsage-Based Renewal Risk: The Leading SignalsAug 18, 2026](/resources/blog/renewal-risk-signals-usage-based-deals/) - [Billing & MeteringWhy Your Marketplaces Report Different NumbersAug 10, 2026](/resources/blog/marketplace-revenue-reconciliation/) - [Cloud GTMCloud Marketplace Metrics Worth a DashboardAug 9, 2026](/resources/blog/cloud-marketplace-metrics/) [Browse every post on the Suger Blog](/resources/blog/) ### Stay Updated Get the latest Cloud GTM insights, product updates, and marketplace strategies delivered to your inbox.