Google Cloud private offer proration adjusts the first installment of an eligible monthly-billed offer. Before choosing it, reconcile the acceptance deadline, scheduled start, term and billing calendar: those dates determine whether the offer can be accepted and what period its first payment covers.
Consider a fictional deal: on October 8, 2026, Acme prepares a $3,000-per-month offer for Globex, intended to cover January 1 through December 31, 2027. Procurement asks for a January 31 acceptance deadline. That deadline is too late for the publishing window and the proposed start. The table below separates those constraints from the billing choice.
Google Cloud private offer dates at a glance
Use Pacific calendar days and distinguish a deadline date from the midnight timestamp that ends it. The rules come from Google’s Producer API reference, pricing setup guide and API guide.
| Field | Provider rule | Practical check |
|---|---|---|
| Acceptance deadline | At most three months after publishing, on a Pacific day boundary | An October 8, 2026 publication permits a deadline date no later than January 7, 2027 |
| Deadline clock time | Producer Portal says 11:45 PM Pacific on the selected date; the API guide represents an end-date field as the following midnight | Give the buyer the earlier time rather than the API’s displayed calendar date |
| Replacement deadline | Before the current offer ends and before its next installment starts | The running offer can make the deadline earlier than the three-month limit |
| Scheduled start | Later than the deadline date in Producer Portal, and at most one year after publishing | A January 1 start requires a December 31 or earlier deadline |
| Term | Monthly, quarterly and annual billing require a duration; the term ends on the corresponding day in the ending month, or its last day if that date does not exist | Twelve months from January 1, 2027 ends at January 1, 2028 |
| Maximum total duration | Seven years including renewal terms; unlimited renewals have not been allowed since May 2024 | Fit the initial term and all renewals inside 84 months |
| Time zone | The API uses America/Los_Angeles day boundaries | Convert with that zone rather than a fixed UTC-8 offset |
The fictional January 31 deadline fails even before proration matters. The three-month window ends at January 8 midnight, represented as a January 7 deadline date. The January 1 scheduled start is tighter still: the buyer must accept by December 31 or earlier. A start on the first has no partial first calendar month.
How do you calculate the acceptance window?
Count from publishing, then apply any earlier limit imposed by the start or the offer being replaced. Google’s API example publishes on March 5 at 1 PM and allows a deadline at or before June 5 midnight in America/Los_Angeles. Because Producer Portal’s selected deadline date means the end of that day, June 4 is the last deadline date in that example.
For an offer with a scheduled start, the API allows the deadline timestamp to equal the start timestamp. Producer Portal expresses the same boundary with dates: the start date must be later than the deadline date. A December 31 deadline and January 1 start fit those representations.
A replacement has another boundary. Check both the current offer’s end and the start of its next installment before offering the buyer an acceptance window. A deadline inside three months of publishing can still be too late for the running contract.
Why can an end date appear a day late?
The API can display the day a period stops while the contract names the last day covered. Google’s API guide uses a December 31, 2026 deadline to illustrate the difference: the effective midnight is January 1, 2027, which is the date the API displays. Start-time fields mean the beginning of the selected day, so their dates agree between the UI and API.
The duration calculation follows the same boundary convention. A 12-month term beginning January 1, 2027 ends January 1, 2028; December 31, 2027 is its last covered day. Check the time and meaning of the field before treating those dates as a discrepancy.
Month ends need special attention. Google’s API example begins January 31, 2024 and runs for 13 months, ending February 28, 2025 because February has no 31st. Do not replace that rule with a fixed number of days.
The provider pages also use two descriptions of expiry: 11:45 PM Pacific in Producer Portal’s pricing guide, and the following midnight in the API guide. Communicate the earlier time to procurement. The payments guide describes Pacific time as UTC-8 or UTC-7 depending on daylight saving time, so use America/Los_Angeles for conversions throughout.
What does proration change?
It adjusts the first installment of a monthly offer, using the basis selected for the offer. Producer Portal lets you choose the offer’s anniversary date or the first of the month as the basis. Its pricing guide describes the first installment; it does not establish a universal formula for the last partial period.
The API distinguishes MONTHLY_PRORATED from MONTHLY_NOT_PRORATED, QUARTERLY_NOT_PRORATED and YEARLY_NOT_PRORATED. There is no prorated quarterly or yearly interval in that set.
Compare the calendar the buyer wants with the generated installment schedule. An anniversary schedule and a calendar-month schedule can have the same term end while distributing the installment periods differently. The date you put on the contract is not, by itself, a payment schedule.
A worked monthly example
Suppose Globex instead starts April 15, 2027, keeps the 12-month term and pays $3,000 per month. Compare anniversary installments with installments aligned to calendar months:
| Period | Anniversary schedule, without proration | Calendar-month schedule, with proration |
|---|---|---|
| First installment | April 15 to May 15: $3,000 | April 15 to May 1: a partial month |
| Illustrative first amount | $3,000 | $1,600 if calculated as 16 of April’s 30 days |
| Second installment | May 15 to June 15: $3,000 | May 1 to June 1: $3,000 |
| Later installment starts | The 15th | The 1st |
| Term end | April 15, 2028 | April 15, 2028 |
The $1,600 is illustrative arithmetic, not a quote from Google’s billing engine. The private-offer guides do not give that calculation formula. Producer Portal generates the payment installment schedule, and its fields cannot be edited for monthly, quarterly or annual frequencies. Check the generated amounts before publishing.
Also inspect the final April 1–15, 2028 stretch. The term still ends on April 15, but the guide’s first-installment description does not tell you how that last period is charged. Keep the generated schedule with the commercial review instead of extrapolating from the first installment.
For a start based on customer acceptance, the first period is not fixed until acceptance happens. Google’s review-and-publish guide therefore marks the revenue share as an estimate for acceptance-based offers with proration enabled, until the customer accepts.
When should you choose proration?
Choose a calendar-month schedule when that is what the buyer’s finance team needs; keep anniversary installments when that is the agreed billing pattern. Work through these decisions before sending the offer:
- Check the frequency. The prorated interval applies to monthly billing.
- Check the start day. On the first of the month, the anniversary and calendar-month boundaries already coincide.
- Check the buyer’s accounting calendar. Google generates customer invoices on Pacific month boundaries. Calendar-month installments can align with that calendar, while anniversary installments follow the offer’s start day.
- Check whether the first amount must be known in advance. An acceptance-based start with proration leaves that amount dependent on the acceptance date. Consider a scheduled start or unprorated installments if the buyer needs a fixed first amount.
A replacement needs its own check. The API permits a monthly offer to move between prorated and unprorated intervals, except when its end policy is MATCH_AMENDED_OFFER: coterming to the amended offer requires the proration policy to stay the same. The decision about when to replace a contract is covered in renewing a Google Cloud Marketplace private offer.
The modify-offer guide documents the extension and last-day restrictions below.
Frequently asked questions
Can an acceptance deadline be extended without changing the buyer’s link?
Yes. Google keeps the same URL. Its Producer Portal guide measures the three-month extension window from the extension; the API reference measures it from publishing. Until those descriptions agree, plan against the earlier boundary: three months from publishing.
Can you modify an offer on its last day?
Google’s modify-offer guide says an offer cannot be modified or replaced when it expires in 24 hours or less. Complete changes with more than a day remaining.
How Fours handles these dates
Fours’ Google Cloud private-offer workflow can link the offer to Salesforce or HubSpot. It refuses an Expiry Date later than today plus three months minus one day on Google’s Pacific calendar at create and submit, names the last valid date, and applies the same cap to a replacement. Draft save does not check the date. The documented example rejects January 5, 2027 and names December 22, 2026 as the last valid date for that submission. The form accepts terms of 1–84 months and checks the initial term plus renewals against the 84-month ceiling: at most six renewals for 12 months, 20 for four months, and none for terms longer than 42 months. Standard monthly, quarterly or yearly offers cannot also carry a scheduled end date; submit reports that conflict.
The Proration switch appears only with Monthly recurrence and not Usage Discount Only. It defaults to Off for anniversary installments; On aligns billing to calendar months by prorating the first installment. The choice is always sent to Google, a clone retains it, and a Postpay replacement inherits it read-only. Offer details show On, Off or Not set (GCP default). Dates display in Pacific time with PST or PDT labels, and an entitlement end date that drifts from the offer term, usually by a day, is corrected on the next sync.
For a resale authorization, the documented plan-start boundary is 07:00 UTC: today is accepted only before that time, checked again at submit with the earliest valid date named. Acceptance Due Date treats today as a UTC calendar date, cannot follow End Time, and is capped at today plus three months minus one day on the Pacific calendar. These validations leave the commercial choices to you: agree the buyer’s deadline, choose proration deliberately and inspect Google’s generated amounts, especially the last partial period. They do not resolve the differences between Google’s deadline descriptions.
For the broader selling motion, see the guide to Google Cloud Marketplace.
Sources
Primary sources for the platform rules cited above. Last verified October 8, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure.
- Google Cloud Commerce Producer API: REST Resource: projects.locations.privateOffers — Last updated 2026-07-13: an acceptance deadline not more than 3 months from publishing, with the 03/05 at 1PM to 06/05 12AM America/Los_Angeles example; an extension still limited to 3 months from publishing; deadlines only on day boundaries in the America/Los_Angeles time zone, at or before the scheduled start; a scheduled start no more than one year from publish; a term in months ending on the same day of the month, or the month's last day, with the 01/31/2024 to 02/28/2025 example; 7 years including all renewal terms; no unlimited renewals as of May 2024; MONTHLY_PRORATED beside the not-prorated monthly, quarterly and yearly intervals; switching proration on a monthly amendment, except under MATCH_AMENDED_OFFER, where the proration policy must not change
- Google Cloud Marketplace: Set up your offer's pricing — The offer expires at 11:45 PM US and Canadian Pacific Time (UTC-8) on the deadline date; a replacement's deadline before the current offer's end date and next installment; proration of the first installment, based on the anniversary date of the offer or the first day of the month; a scheduled start later than the acceptance deadline, selectable once automatic offer approval is on; a duration required for monthly, quarterly and annual billing; the generated installment schedule, not editable for those frequencies
- Google Cloud Marketplace: Create and manage private offers using the API — UI start-time fields mean the start of the day and match the API; UI end-time fields such as the acceptance deadline mean the end of the day, so a 2026-12-31 deadline is 12:00 AM Pacific Time on 2027-01-01, the date the API displays
- Google Cloud Marketplace: Modify a published offer — No modification or replacement if the offer expires in 24 or less hours; an extended acceptance deadline keeps the offer URL and must be within three months of when you extend the offer
- Google Cloud Marketplace: Review and publish your offer — The revenue share is marked as an estimate for offers with start dates based on customer acceptance that have proration turned on, until the customer accepts
- Google Cloud Marketplace: Receiving payments from Google — Customer invoices are created on month boundaries in the US and Canadian Pacific Time zone, UTC-8 or UTC-7 depending on daylight saving time
- Fours docs: Create Private Offer on Google Cloud Marketplace — Fours behaviour: an Expiry Date later than today plus three months, minus one day, on Google's Pacific calendar is refused at create and submit, before anything reaches Google, with a message naming the last valid date, and is not checked on draft save; the same cap on a replacement; Offer Duration from 1 to 84 months and the renewal cap; Proration shown only with Monthly recurrence and not for Usage Discount Only, Off by default, always sent to Google, and inherited read-only on a Postpay replacement; standard-interval offers refused with an end date; dates in Pacific time with a PST or PDT label, and entitlement end dates resynced to the offer's term
- Fours docs: CPPO on Google Cloud Marketplace — Fours behaviour: a resale authorization's Start Time accepts today only before 07:00 UTC, when Fours' documentation says GCP starts a plan, and is checked again at submit with the earliest valid date named; the Acceptance Due Date counts today as a UTC calendar date, can't fall after the End Time, and is refused at submit after today plus three months, minus one day, on Google's Pacific calendar
Keep reading
Stay Updated
New posts, product updates and marketplace strategy are shared on LinkedIn as they publish.
Follow Fours on LinkedIn