Check the SKU, renewal term and ramp structure against the rules governing the quote before adding an annual-payment or multi-year deal to the forecast.
Key takeaways
- Read the SKU and payment schedule together.
- Check renewal terms against your company's approved list.
- Confirm the applicable rule date before reviewing a revised quote.
It might be the total contract value, or the annual amount that goes into the forecast. By the time that number arrives, several choices have already been made behind it. Someone picked a product SKU. Someone set the term. Someone chose how the customer pays. Each choice changes what the number means, and some of them are governed by rules that a quote tool may or may not enforce.
This post covers three SKU rules that appear in published deal desk guidance. These rules give revenue leaders specific quote fields to check before forecasting. The main example comes from the GitLab Handbook's Deal Desk page. GitLab's rules belong to GitLab, and your company's rules may differ, so read them as a model of what to check rather than a standard to copy. Each quoted rule links to its source so you can confirm the wording yourself.
Why the SKU matters more than the product name
A SKU is the code a quote is built from. In a well-run catalog, it tells you what the customer bought, at which tier, and under which terms. That is why it matters to revenue leaders. If the SKU and the rest of the quote disagree, the forecast is working from two sources that say different things.
The problem is easy to miss. A quote can look complete. The product line is right, the customer name is right, and the amount falls in the expected range. The mismatch sits in the codes. A multi-year SKU on a quote with annual billing tells a different story from the one the payment schedule tells, and only someone who reads both lines will notice.
GitLab's handbook gives a concrete case. Before a rule change in 2025, its guidance used a split: annual payments on a multi-year deal used the one-year SKU, while prepayment used a multi-year SKU such as "SaaS - Premium - 2 Year" (GitLab Handbook). A reader who saw only the SKU could infer the payment plan. A forecast should not depend on that kind of shortcut, because the inference breaks as soon as the rules change.
Rule 1: annual payments need the one-year SKU
The first rule is the simplest. The GitLab Handbook states: "All quotes with Annual Payments must use the “1 Year” Product SKU." (GitLab Handbook)
The same page describes what happens when the rule is broken. The quote tool warns the user: "You will see an error message if you select Annual Payments and anything other than the 1 Year SKU." (GitLab Handbook)
Why this matters for a revenue leader is straightforward. Under this rule, an annual payment schedule attached to a SKU that is not the one-year SKU is a mismatch between two parts of the same quote. Whatever the cause, the forecast now has to choose which part to believe, and that choice is a guess.
The cost of that guess shows up later. A forecast built on a mismatched quote can show a payment schedule that never happens, and the correction arrives after the deal is already in the pipeline numbers. Catching the mismatch at the quote stage is cheaper than explaining it in a forecast review.
Three habits follow from this rule:
- Ask whether your quote tool enforces the match. An error message is a control. The absence of an error is not proof that the quote is right, because the check may not exist in your system.
- Read the SKU line first on any annual-billing quote. If your policy requires the one-year SKU for annual payments and the SKU names a longer term, send the quote back before forecasting.
- Do not work around the warning. If the tool blocks a combination, the fix is to correct the quote, not to change a second field until the error goes away.
Rule 2: renewal terms come from a fixed list
The GitLab Handbook also limits renewal terms: "On a Renewal quote, Renewal Term must equal 24, 36, 48, or 60." (GitLab Handbook)
The scope matters. The rule applies to renewal quotes, and the quoted text says nothing about new-business quotes. Don't carry it over to other quote types unless your own policy does.
Why does a renewal term outside the list matter? Under GitLab's rule, a renewal term outside the list does not meet the requirement. Confirm the term and any approved exception before relying on the amount beside it. That is the point where the forecast should pause and someone should confirm which term the customer actually signed.
Checks for this rule:
- Take the term from the quote itself, not from the deal notes or the CRM summary. Notes drift from what was signed.
- If the renewal term is not on your approved list, ask deal desk what changed and when.
- Record the reason for any exception in the forecast notes, so the reason can be found later.
Rule 3: multi-year deals become ramp quotes on the one-year SKU
The third rule is the one that changed. Effective 2025-08-06, the GitLab Handbook requires all multi-year deals, defined as quotes with a term greater than 12, to use ramp quotes and the one-year SKU. (GitLab Handbook)
Read together, the structure and SKU requirements tell you that the SKU on a multi-year deal no longer describes the length of the deal.
The practical result is that the SKU no longer tells you whether the customer prepaid or paid annually. Under the new rule, you have to read the payment schedule from the quote itself. A forecast model that reads the SKU as a payment signal will misclassify deals signed under the new rule.
What a revenue leader should do with this:
- Find out which date controls each deal. The handbook gives an effective date, and your process needs to say which date controls: the quote date, the signature date, or another date.
- Don't compare across the change without a flag. A deal signed before the change may carry a multi-year SKU for prepayment. A deal after the change carries the one-year SKU whatever the schedule. Tag them so the trend lines compare like with like.
- Understand what a ramp quote means in your systems. The handbook uses the term "ramp quotes." Check how your billing and revenue systems represent a ramp before you forecast one.
Walk through one deal from quote to forecast
Suppose a revenue leader receives a quote for a multi-year renewal, and the customer has asked to pay annually. Three checks apply, and they should run in a fixed order.
Start with the payment schedule. The customer wants annual billing, so the first check under Rule 1 applies. The SKU line should be the one-year SKU. If the line shows a multi-year SKU, the quote fails before anyone looks at the amount.
Next, look at the term. This quote is a renewal, so Rule 2 applies. Check that the term is one of the four lengths the GitLab rule lists. If it is not, the quote needs an explanation before it goes further.
Then confirm whether the deal is multi-year in the handbook's sense, meaning a term greater than 12. If it is, Rule 3 applies. The structure should be a ramp quote, and the SKU should be the one-year SKU, whatever the payment schedule.
Only after those checks should the amount move toward the forecast. If any check fails, the deal waits. A failed check does not prove the deal is wrong. It means the deal has to be explained before anyone relies on it. Use the related guide to quote checks before the forecast call for a broader review.
Illustrative example: review a renewal term
An illustrative renewal governed by these rules has a term of 60 months and annual payments. The term passes the renewal check. The reviewer then finds a multi-year SKU on the quote. The term check has passed, but the SKU check has failed. Return the quote for correction, then confirm its ramp structure before carrying the amount into the forecast.
Why billing settings belong in the review
SKU rules set how a quote is built. Billing settings decide what happens after the customer signs. A quote that is correct on the page can still produce a payment problem if the billing system handles a later change in a way nobody expected.
Stripe's API reference describes one such option. It "Controls how Stripe handles payment when a subscription update requires payment and collection_method=charge_automatically." (Stripe API Reference) You do not have to use Stripe to take the lesson. A mid-term change can require a payment, and how the system handles that payment is a setting someone chose. If that setting is unknown to the revenue team, the forecast can miss cash that the deal was supposed to produce, or count cash that arrives on a different schedule.
Chargebee's documentation makes a related point about the quoting layer. Its CPQ product "enables advanced pricing models, flexible quote configurations, and a more scalable quoting experience." (Chargebee Docs) Ask whether your quoting tool can enforce the specific SKU rules your company uses. When it does not, the review falls to people, and people miss things.
Questions to put to your vendor or your own team:
- Which billing option controls payment after a mid-term change?
- Does the quote tool hold the SKU rule, or does a person?
- Who owns the setting, and who approves a change to it?
Common mistakes revenue leaders see in quote reviews
Watch for these in your own reviews:
- Reading only the total. The total can match the approved price while the SKU and schedule break the rule.
- Assuming the SKU shows the payment plan. Under the current GitLab rule, it does not.
- Carrying old SKU logic into new deals. A forecast rule written for the earlier split will misread deals after the change.
- Treating a warning as a suggestion. Investigate an error on a quote before relying on the combination.
- Fixing the number, not the codes. Adjusting the amount to hit a forecast target while leaving the SKU wrong moves the problem without solving it.
What the forecast record should hold
The deal amount and a close date are example forecast fields. For multi-year deals under these rules, that is not enough. A record should also hold the SKU as quoted, the term in months, whether the deal is a ramp quote, the payment schedule as its own field, and the rule or effective date that applied. Each field lets a later reader check the amount without reopening the quote.
This list is a suggestion, not a standard. Your finance team will have its own fields. The point is that the fields the forecast relies on should be filled in from the quote, not inferred from the SKU. For changes to those fields, see how to choose a deal field type.
A checklist before the amount reaches the forecast
- Read the payment schedule and the SKU together. If annual billing uses another SKU and GitLab's rule or an equivalent company rule governs the quote, stop.
- Check the term against the renewal rule above or your own approved list. Anything else gets a question.
- Identify multi-year deals and confirm they follow your policy for ramp structure and SKU.
- Confirm which effective date governs each deal, and tag deals on either side of any rule change.
- Ask whether the quote tool blocks mismatches. If it does, confirm no one has worked around the block. If it does not, add a manual review step.
- Store the payment schedule as its own field in the forecast record, so later readers do not have to infer it from the SKU.
When a rule changes during a deal cycle
A deal can stay open for a long time. If a rule changes between the first quote and the signature, the deal may fall under a different version of the rule than the one the rep first used.
Decide the rule in advance. Write into the deal desk process which version applies and which date controls, whether that is the quote date, the signature date, or the booking date. When a quote is revised, run the checks again, because a revision can change the SKU, the term, or the schedule even when the amount looks the same.
Do not restate older deals to make the history look uniform. Tag deals on each side of the change so the forecast can explain its own trend.
How to run the review with deal desk
Deal desk owns the rules, so the review works best as a partnership. Ask them for the written version of the SKU rules your company uses, including the effective dates. Pull a sample of recent quotes, both before and after any rule change, and check them against the written rules. Count the mismatches. If they cluster in one quote type or one region, investigate the shared quote setup or process before attributing them to individual people.
Bring the forecast owner into the room. Ask what the forecast assumes from the SKU, the term, and the schedule, and write those assumptions down. Every assumption that reads a code instead of a field is a place where a rule change can quietly break the forecast.
Talking to reps about SKU rules
Reps are rarely trying to break a rule. They are trying to close a deal the customer wants on a particular payment schedule. When you explain a SKU rule, lead with the customer's request and show the path that satisfies it. Say which SKU to use, whether the quote tool warns about the other combination, and who to call when the customer's request does not fit the standard options. A rule that is explained once, with a clear route through it, gets followed. A rule that is only enforced after the fact produces workarounds.
Keep the message short and consistent. Give reps the same answer that deal desk gives, and point them to the written rule rather than to memory. If the rule changes, say so in the same channel where reps already get pipeline updates, so the change reaches the people building quotes.
What to take into your next review
The three rules share one principle. A forecast should not guess from a code what the quote does not state plainly.
Today, ask deal desk for the written rules and check a recent quote with the checklist above. The number that reaches the forecast should be one you can explain from the quote, the rule, and the effective date. That is the test.
Questions before the forecast
Does a one-year SKU mean the contract lasts one year?
No, the SKU alone does not establish the contract length under GitLab's multi-year rule. Read the quoted term separately.
Does an error message prove the tool blocks the quote?
No, an error message alone does not establish that the tool prevents the combination. Confirm the tool's actual enforcement with your team.
Should every company copy these rules?
No, apply your own company's written SKU policy. Use these checks to identify which fields and enforcement questions need review.