Skip down to the research record

Multi-year deal billing: 6 figures from GitLab and Stripe

Quota Forecast Editorial Team · Published · 10 min read

GitLab’s handbook documents an 18 month deal where 6 months billed up front and the final 12 months billed at the 6 month mark. The GitLab Handbook

Key takeaways: what the published examples measure

  • Split billing structure: The GitLab Handbook describes an 18-month deal where the first 6 months are billed up front and the final 12 months are billed at the 6-month mark, entered through custom payment schedule details.
  • Invoice baseline: Stripe Documentation lists a monthly subscription invoice worth 90 USD generated on April 1 as the starting point for its revenue recognition example.
  • Contra revenue calculation: In the same documentation, a 120 USD credit note issued during the second month of an annual subscription results in 20 USD being recorded as contra revenue for the first two months.
  • Scope limitation: These figures illustrate specific product behaviors and accounting treatments within their respective platforms; they do not represent industry averages or universal standards for multi-year deal billing.
  • Action step: Compare your current split-billing quote’s upfront months and subsequent billing points directly against the GitLab 18-month structure to verify if your record captures the same timing logic.

Figure, publisher and date in one table

Each row identifies the item counted, the publisher that documents it, and the specific date or context from their documentation. Use this reference to verify your internal records against these published examples.

Item CountedPublisherDate or Context
18 month deal split billingThe GitLab Handbook6 months up front; final 12 at month 6
Non-standard quote section dateThe GitLab HandbookAs of 2024-11-20
Multi-year quote change dateThe GitLab HandbookEffective 2025-08-6
90 USD invoice, 30 USD downgradeStripe DocumentationInvoice on April 1; downgrade on April 21
2 unbilled line itemsStripe DocumentationRemaining time of subscription
120 USD credit note exampleStripe DocumentationAnnual subscription during second month

Check your own deal desk notes for similar dates before finalizing the quarter-end record.

What each figure measures and the date it carries

The figures in this section measure specific invoice generation events rather than total deal value. According to Stripe Documentation, the May 1 invoice contains line items generated by a downgrade as well as a new line item representing the month of May. The date attached to this measurement is May 1, which marks the start of the billing cycle following the April 21 downgrade event.

GAAP states that you recognize revenue when you realize and earn it, which might be earlier or later than when you actually receive payments. This distinction matters for quarter-end records because cash collected in one period may not match the revenue recognized in that same period. The source emphasizes that you must correctly recognize and defer revenue to have the most accurate insights into your business profitability and financial health. These rules set when revenue is recognized, which can differ from when payment arrives.

Use these examples to check if your own split-billing schedule aligns with standard accounting treatments. If your multi-year deal has similar mid-term adjustments, verify that your internal records separate deferred revenue from recognized amounts at the correct monthly intervals. The Stripe documentation provides the structural logic for handling such transitions. Ensure your quarter-end report notes whether revenue was realized before or after the corresponding payment date, using the GAAP principle as the guiding framework for that classification.

The 18 month example: 6 months up front, 12 at month 6

The Deal Desk Handbook in The GitLab Handbook describes an eighteen-month deal structure where the first six months are billed up front. The remaining twelve months are then billed at the six-month mark of the contract term. This specific split creates a two-part billing schedule rather than a single upfront payment or monthly recurring charges for the full duration.

To document this arrangement, the handbook instructs users to populate the “Custom Payment Schedule Details” field with this wording: “I would like a payment schedule for this deal where the first 6 months are billed up front, and the final 12 months are billed at the 6 month mark.” The handbook presents the split as an example request.

This example serves as a concrete reference for how to articulate split billing terms within internal documentation systems. When writing your quarter-end record, you can compare your own multi-year deals against this documented pattern to ensure your custom payment schedules are clearly defined. If your deal involves different splits, such as three years with quarterly billing after an initial setup fee, the principle remains the same: define the exact months and billing points in the custom details field. Use it to verify that your own records contain similar precision regarding when each portion of the deal value is invoiced.

Illustrative example: splitting a 12-month term

Suppose a 12-month contract totals 120 USD, with 6 months billed up front. The first invoice covers months 1 to 6. The second invoice covers months 7 to 12 and is billed at the 6-month mark. Record both invoice dates, both amounts and the months each invoice covers. If the amounts are unequal, note the reason in your record.

Stripe's downgrade, credit note and refund figures

The Stripe Documentation outlines a specific sequence for handling mid-term subscription changes. On April 1, the invoice is generated for a monthly subscription worth 90 USD and the customer pays for it. On April 21, the customer requests a downgrade to a 30 USD subscription. The downgrade results in 2 unbilled line items for the remaining time of the subscription. The documentation uses these figures to illustrate how line items are created when a plan changes before the billing cycle ends.

When the next billing date arrives, the system processes these new line items alongside standard charges. A full refund request can complicate this further. On May 4, the customer requests a full refund on the invoice for May, resulting in full refunds on the line item created by the downgrade as well as the new line item for May. This example shows that a refund covers all active line items on that specific invoice, not just the original subscription fee. If you are reviewing your own quarter-end records, check whether any downgrades created similar unbilled line items that were later refunded.

Beyond invoices, the documentation addresses credit notes on annual subscriptions. For example, if there’s a 120 USD credit note on an annual subscription during the second month, 20 USD for the first 2 months is contra revenue. This figure represents the portion of the credit note that offsets previously recognized revenue. It does not represent future revenue or a reduction in total contract value beyond that specific period. When measuring your multi-year deal against this example, note that the 20 USD amount is tied directly to the two months of service already delivered under the annual term.

Use these figures to verify that your internal accounting treats downgrades and refunds consistently with the documented behavior. Do not assume that every vendor handles unbilled line items identically; each publisher documents its own specific transaction flow. Compare your own quote’s billing points to see if they generate similar unbilled states during transitions. If your deal includes a downgrade or refund, ensure your records capture the exact line items affected, mirroring the structure shown in the source. This helps maintain clarity when reconciling bookings at quarter end. For more steps, see bookings reconciliation checks.

How to compare your own quote, and where the figures stop

When you sit down to record a multi-year deal at quarter end, start by matching your quote structure against the specific dates and terms documented in public handbooks. The GitLab Handbook notes that as of 2024-11-20, it created a new quote section called Non-Standard Deal Elements The GitLab Handbook. If your deal involves complex migration scenarios, the same handbook describes a common example where a customer requests a $0 subscription to maintain their existing instance for a period of time while they transition to the new paid instance The GitLab Handbook. Use this as a reference point for how zero-dollar line items might appear in a split billing schedule. Additionally, be aware that quote creation changes effective 2025-08-6 apply specifically to Ecosystem, Amendment, and Multi-Year quotes according to the Deal Desk Handbook The GitLab Handbook. Check if your internal tools have updated fields or validation rules aligned with these effective dates. For a related checklist, see accepted quote review.

Do not conflate tax year definitions with sales quarters. The Internal Revenue Service defines a short tax year as a tax year of less than 12 months Internal Revenue Service. Similarly, when figuring depreciation or amortization, a 52-53-week tax year is generally considered a year of 12 calendar months by the IRS Internal Revenue Service. These rules are strictly accounting and tax-based; they do not dictate how you should slice your pipeline for a quarterly business review. Keep your fiscal calendar separate from these tax definitions to avoid confusion in your records.

Today, open your current multi-year quote and check whether its upfront months and billing points match the 6-month split and the 6-month mark shown above.

Related guides: Forecast pull published caps: 8 figures from vendor docs · Unsigned quote review: 5 checks for quarter-end records.

FAQ: multi-year billing examples and the dates behind them

What does a multi-year deal billing example look like?

The GitLab Handbook describes an 18-month deal structure. In this example, 6 months are billed up front. The final 12 months are billed at the 6-month mark. This split schedule serves as a concrete reference for term length and billing points.

How much of a 120 USD credit note is contra revenue in Stripe's example?

According to Stripe Documentation, a 120 USD credit note on an annual subscription during the second month includes 20 USD for the first 2 months. That specific 20 USD amount is classified as contra revenue.

When did GitLab add a Non-Standard Deal Elements quote section?

As of 2024-11-20, the GitLab Handbook states that a new quote section called Non-Standard Deal Elements was created.

Does the IRS 52-53-week year rule apply to my sales quarter?

No, the Internal Revenue Service rule does not define sales quarters. Publication 538 from the Internal Revenue Service specifies that a 52-53-week tax year is generally considered a year of 12 calendar months. This definition applies specifically when figuring depreciation or amortization. It does not set fiscal calendars for revenue teams or sales forecasts.

When do GitLab's quote creation changes for multi-year quotes take effect?

Quote creation changes for Ecosystem, Amendment, and Multi-Year Quotes are effective 2025-08-6. The GitLab Handbook lists this date for these specific quote types. Check your internal records against this timeline to ensure compliance with updated procedures.

Sources