What is a pricing effective date?
A pricing effective date is the moment a new rate card or billing rule starts to apply to messages. Meta changes WhatsApp Business Platform pricing only on the first day of a calendar quarter — 1 January, 1 April, 1 July or 1 October — and gives notice in advance: at least one month for rate changes, three months for pricing add-ons and six months for changes to the pricing model itself.
Meta's pricing updates take effect at 12 am in each WhatsApp Business Account's timezone (Meta's pricing documentation now calls the account a Messaging account), the same clock that resets the monthly counts behind volume tier pricing and the monthly service-message tier, so two accounts in different timezones switch at different instants. Meta charges a message when it is delivered, so reconcile a boundary by delivery time in the account's timezone, not by the moment your system queued the send. Meta's documentation does not spell out every edge case at the boundary, so the deliveries in the minutes around midnight are the ones to check against its own pricing data during billing reconciliation.
Meta's dates are not the only ones that matter. A provider's rate card has its own effective date: InfiQ's current India card took effect on 1 July 2026, for example, while Meta's per-message pricing began on 1 July 2025 and service messages became chargeable on 1 October 2026. An effective date is the mechanism by which any single change starts to apply; WhatsApp pricing history is the long-run sequence of those changes. Reading any price correctly means asking which rate card it comes from and from when it applies.
Key takeaways
- A pricing effective date is the moment a new rate card or pricing rule starts to apply to delivered messages.
- Meta changes WhatsApp rates only on the first day of a quarter: 1 January, 1 April, 1 July or 1 October.
- Notice is at least one month for rate changes, three months for add-ons and six months for changes to the pricing model.
- Meta's updates take effect at 12 am in each WhatsApp Business Account's timezone, the clock that also resets volume tiers.
- A provider's rate card has its own effective date, which need not match Meta's quarterly changes.
Example: A renewal campaign across the 1 October switch
A Mumbai insurance broker starts a renewal-reminder campaign at 10 pm on 30 September 2026, with its WhatsApp Business Account set to India time. Most messages are delivered before midnight; the ones still in flight are delivered after 00:00 on 1 October, the date service replies also became chargeable in India. The broker's month-end job splits traffic by delivery timestamp in IST and matches the September and October invoices — an older script that split by send time in UTC had put several hours of the campaign in the wrong month.
A pricing effective date: key facts and limits
- Meta change days
- 1 Jan, 1 Apr, 1 Jul, 1 Oct
- Notice for rate changes
- At least 1 month
- Notice for pricing add-ons
- 3 months
- Notice for model changes
- 6 months
- Clock
- 12 am in each WABA's timezone
- Charge trigger
- Delivery of the message
- Recent effective dates
- 1 Jul 2025 per-message pricing; 1 Oct 2026 service charged
How does a pricing effective date work?
- Step 1
Watch for the announcement
Meta publishes rate changes at least one month before they apply. Note the effective date and exactly which categories and markets change.
- Step 2
Update forecasts and calculators
Re-run budgets and your WhatsApp pricing calculator with the new rates for every month from the effective date, and flag scheduled campaigns that straddle it.
- Step 3
Confirm your provider's date
A provider with bundled rates may reprice on Meta's date, later, or on its own schedule. Ask when its card changes and keep that date too.
- Step 4
Use the account's timezone
Align reports and reconciliation to midnight in the WhatsApp Business Account's timezone, the clock Meta's pricing updates and volume tiers follow.
- Step 5
Reconcile by delivery time
Split the boundary month by the delivery timestamp from status webhooks or
pricing_analytics, not by send time, and look closely at the hours around midnight.
Why the difference matters
Why does a pricing effective date matter?
Effective dates are where forecasts and invoices disagree. A budget built in September on the old card is wrong from 1 October; a campaign that runs across midnight on a quarter boundary splits between two rate cards; a reconciliation job that uses UTC while the account bills in India time misplaces five and a half hours of traffic. Knowing the rules — quarter start, notice period, account timezone, delivery time — turns these from surprises into calendar entries.
Common mix-ups
Common mistakes with a pricing effective date
Reconciling in the wrong timezone
If the account bills in India time and your reports use UTC, five and a half hours of traffic land on the wrong day — and at a quarter boundary, on the wrong rate card. Align to the account's timezone.
Splitting by send time
Charges follow delivery. A message queued before midnight and delivered after it belongs with the later deliveries, so split by delivery timestamp.
Assuming every provider follows Meta's date
A bundled-rate provider may change its card on a different date, or not at all. Track its effective date separately from Meta's.
Using an undated rate
A rate without an effective date cannot be trusted in a forecast. Store every rate with the date it starts applying and keep the old row.
Pricing Effective Date FAQs
How often can Meta change WhatsApp prices?+
Which rate applies to a message sent just before a change?+
What were the most recent WhatsApp pricing effective dates?+
Is a provider's rate card date the same as Meta's?+
Rules of thumb
Best practices for a pricing effective date
- Keep a rates table with an effective_from column instead of overwriting old rates.
- Avoid starting large campaigns in the hour before a quarter boundary if you need clean month splits.
- Put the first day of every quarter in the finance calendar as a pricing checkpoint.