WhatsApp INR Billing: Migrate Your WABA Before 2027

What is the WhatsApp INR billing migration, and who does it apply to?

Meta bills a WhatsApp Business Account in a currency that is fixed on the account itself. For one group of India-based customers, that currency now has to be rupees, and there is a date attached to it.

Meta's pricing documentation describes the start: "Billing localization launched on January 1, 2026 for partners and directly-integrated clients whose Sold-To country is India in Billing Hub (eligible customers)" (Meta — Pricing on the WhatsApp Business Platform).

That parenthesis is the whole definition. There is no separate eligibility test published elsewhere that we could find. "Eligible customer" means partners and directly-integrated clients whose Sold-To country in Meta's Billing Hub reads India — a field on Meta's billing record, not a judgement about where your company is registered or where your customers live.

Then the requirement, which is the sentence this entire page exists for: "Eligible customers must ensure all WABAs in their business portfolio are migrated to INR by December 31, 2026 to avoid disruptions, since as of January 1, 2027 Meta will no longer deliver the messages of non-INR WABAs of eligible customers" (Meta — Pricing on the WhatsApp Business Platform).

It says all WABAs in the business portfolio, not the one you send most of your volume from. A dormant second account created during a trial two years ago is inside that sentence.

Checked against Meta's documentation on 28 August 2026.

• What is the WhatsApp INR billing migration, and who does it apply to?
• What happens if I miss the 31 December 2026 deadline?
• How do I tell which currency my WhatsApp Business Account bills in?
• Does my software provider migrate my WhatsApp Business Account, or do I?
• What changes on my invoice after moving to INR?
• Does the INR migration change what Meta charges per message?
• What does this mean if my provider bills me on its own credit line?
• How does GST interact with a WhatsApp bill raised in rupees?
• What should an Indian business do about this before December?
• Why did Meta make INR billing mandatory at all?

What happens if I miss the 31 December 2026 deadline?

Meta's own words are worth reading slowly, because they are not the words a documentation team reaches for lightly: it "will no longer deliver the messages of non-INR WABAs of eligible customers" (Meta — Pricing on the WhatsApp Business Platform).

Not a surcharge. Not a warning banner. Not a grace period that the documentation names. Delivery.

We are not going to dress that up, and we are also not going to embellish it. Meta does not publish, on that page, what the failure looks like from the API side — whether a send returns an error code, or is accepted and silently dropped, or whether the number is put into some other state. Anyone telling you which of those happens is guessing unless they quote it.

What we can say with confidence is the shape of the risk. A business that sends order updates, delivery notifications and one-time passcodes over WhatsApp has built an operational dependency on delivery. If that stops on a date, the failure arrives on a public holiday weekend for most Indian teams, on an account nobody was watching, in a channel whose whole appeal is that messages arrive.

The remedy is dull and available now, which is the best combination a compliance deadline ever offers.

Checked against Meta's documentation on 28 August 2026.

How do I tell which currency my WhatsApp Business Account bills in?

Here is the honest answer, and it is less satisfying than the one most articles give you.

Meta's developer documentation does not publish a screen-by-screen route to your WABA's billing currency. We looked. The pricing page names the currencies billing is available in — USD, AED, ARS, AUD, BRL, CLP, COP, EUR, GBP, IDR, INR, MXN, MYR, PEN, SAR and SGD — and states the migration requirement, but does not walk you to the field (Meta — Pricing on the WhatsApp Business Platform).

What is documented is the constraint that makes the currency findable in practice: "A WABA's time zone and currency cannot be edited once a line of credit has been attached to it" (Meta — WhatsApp Business Accounts). Currency is a property that gets set once and then locks.

In practice the value surfaces where the money does: the payment settings on the WhatsApp Business Account inside Meta's business settings, and the invoice Meta raises against it. If the amount you are charged arrives in dollars, the WABA is a USD WABA, whatever anyone's dashboard says.

We would rather tell you that Meta does not document the click path than invent one for you and have it be wrong after the next interface change. Read the invoice. It is the artifact that cannot be stale.

Checked against Meta's documentation on 28 August 2026.

Does my software provider migrate my WhatsApp Business Account, or do I?

This is the question the deadline turns on, and the answer depends on a distinction most businesses have never been asked to care about.

Meta's own partner documentation draws it in two sentences. Of Solution Partners: "Solution Partners have credit lines which can be extended to clients who they bring on board", "thus removing the need for those clients to enter their own payment method during the onboarding process". Of Tech Providers: "Unlike Solution Partners, however, Tech Providers do not have credit lines", and "Instead, clients onboarded by Tech Providers must provide their own payment method after onboarding is complete" (Meta — Partners). The taxonomy in full is in our guide to how a Solution Partner differs from a Tech Provider. If the answer to that question changes what you want from a vendor, what carries over when you switch providers covers the move itself — the billing currency sits on the account, so it travels with you either way.

If you attached your own card to your own WhatsApp Business Account, the currency on that account is yours, and so is the migration.

Read from Meta's partner and pricing documentation on 28 August 2026.

WabaCRM is a Meta-verified Tech Provider, verified on 30 July 2026. We are not a Meta Business Partner, we hold no credit line, and Meta bills our customers directly for messages. The consequence is one we would rather state than let a customer discover in January: we cannot migrate your WABA's billing currency for you, and neither can any other Tech Provider. We can tell you the deadline exists. That is the extent of it.

The numbers screen above is a good illustration of the boundary. It shows the connection state, the quality rating, the messaging tier and the template count, because Meta exposes those to the connected application. It does not show a billing currency, because that is not the software's to see or to change.

Checked against Meta's documentation on 28 August 2026.

What changes on my invoice after moving to INR?

The mechanism matters more than the invoice layout, so start there.

Meta's migration is not an edit. It is a clone. "The Currency Migration API allows you to change the billing currency or payment method on a WhatsApp Business account (WABA) by creating a new WABA and automatically migrating your phone numbers, message templates, and Flows" (Meta — Change billing currency via API).

You end the process on a different WhatsApp Business Account ID than you started on. Meta says the old one survives: "The original WABA is not deleted after migration", and "The original WABA can no longer send messages after the migration is complete".

Your history does not come with you. Meta is explicit: "Historical data remains on old WABA. New data appears on the new WABA after migration", and "Continue querying the old WABA ID for all historical insights, analytics, and billing data generated before the migration".

So a business that reports on WhatsApp spend across a financial year should expect its records to be split across two account IDs at the migration date, permanently. If you keep your own send records — a message log with CSV export is the usual place — that split matters less, because your copy spans both.

Meta also notes what may not survive the clone: "Templates with outdated formats may not migrate", and phone numbers in a manual review state are listed among the exclusions. Meta's own pre-completion verification list asks you to confirm your templates have been cloned to the new WABA, that your app is installed on it, and that users and permissions synced correctly — do all three before you complete.

Checked against Meta's documentation on 28 August 2026.

Does the INR migration change what Meta charges per message?

We publish no per-message rates on this page, deliberately. Rates change, and a stale numeral on a page arguing that its numbers are checkable is simply a lie with a date on it. The current India figures live in our WhatsApp Business API pricing guide for India, which is the page we keep current.

What is worth understanding is the structure. Meta publishes separate rate cards per currency, and introduces them as reflecting "our current rates and volume tiers, effective July 1, 2026, based on WhatsApp Business account timezone" (Meta — Pricing on the WhatsApp Business Platform).

Read that last clause again. The rate card that applies to you is selected by the WABA's timezone, and timezone is the other field locked by the same sentence that locks currency.

Meta's pricing documentation does not publish a conversion methodology — there is no statement that the INR card is the USD card multiplied by a rate. Treat the INR rate card as its own set of published numbers, not as a translation of a dollar number.

Meta's documentation states no percentage saving from migrating to INR, and does not compare the cards. If a saving matters to your decision, compute it yourself from the two rate cards for the countries you actually message.

Some things do not change with currency at all: "All non-template messages are free", "Utility templates delivered within an open customer service window are free", and "All messages are free for 72 hours ... if sent within an open free entry point window" (Meta — Pricing on the WhatsApp Business Platform). Those apply on either currency — but the first two stop applying at all, in any currency, from 1 October 2026, when Meta starts charging per message for both. Free entry point windows are unaffected. See what changes on 1 October 2026 for the detail.

Checked against Meta's documentation on 28 August 2026.

What does this mean if my provider bills me on its own credit line?

If you never entered a payment method during onboarding, and your WhatsApp message charges arrive on your software vendor's invoice rather than Meta's, you are almost certainly on a Solution Partner's line of credit.

In that arrangement the currency question sits with the partner. Meta's documented constraint — currency "cannot be edited once a line of credit has been attached" (Meta — WhatsApp Business Accounts) — binds the account the credit line is attached to, and that is the relationship your partner holds, not you.

The migration API covers the credit-line case, but narrowly: "Only credit card to Line of Credit and Line of Credit to Line of Credit migrations are supported" (Meta — Change billing currency via API).

This is a legitimate model, not a worse one. A shared credit line removes a card-entry step that stops plenty of businesses cold, and it puts one invoice in front of finance instead of two. The trade is that you are exposed to your partner's diligence on a deadline you cannot act on yourself.

The only useful thing to do here is ask, in writing, and keep the answer. A one-line email — is our WABA on INR, and if not, when will you migrate it — costs nothing and produces a record.

Checked against Meta's documentation on 28 August 2026.

How does GST interact with a WhatsApp bill raised in rupees?

Carefully, and not from us.

Meta's WhatsApp pricing documentation contains no statement about GST, VAT or any other tax treatment. We read the page for it. Publishing a confident paragraph on Indian indirect tax sourced from a messaging API's pricing page would be exactly the kind of plausible invention this site exists to avoid.

Our India pricing guide goes no further, and deliberately: it tells readers to budget for tax and then settle the figure from their own first Meta invoice, because we could not find Meta stating a rate and Meta's rate cards are published exclusive of tax.

Whether your business can claim input credit on WhatsApp message spend is a question for your chartered accountant, who will want to see the actual invoice. Not a blog post, and not a software vendor.

That is not a dodge. It is the correct division of labour: we can tell you which entity raises the invoice and in what currency, because Meta documents the billing structure. We cannot tell you how it lands on your return, and any vendor that offers to is selling certainty it does not have.

What should an Indian business do about this before December?

Six things, in order, none of them urgent today and all of them overdue by November.

1. Establish which model you are on. Did you enter a card during onboarding? If yes, the migration is yours. If your message charges appear on a vendor invoice, ask the vendor.
2. List every WABA in your business portfolio, not just the active one. Meta's requirement names all of them.
3. Read a recent Meta invoice and note the currency. This is the check that cannot be wrong.
4. Check whether the account is eligible for the API path at all. Meta states plainly: "Coexistence and Authorized Agents WABAs are not eligible for migration via this API" (Meta — Change billing currency via API). If your number is running in coexistence mode, the API route is closed to you and you need to ask Meta what is open.
5. Audit your templates before you migrate, not after. "Templates with outdated formats may not migrate", and rebuilding a rejected template under time pressure in the last week of December is a bad plan.
6. Do it well before the deadline. Meta notes that "Migration duration varies depending on the number of templates and assets", and the completion step "moves phone numbers and deprecates the old WABA. Plan for any operational timing requirements."

That last quotation is Meta telling you there is a cutover moment. Schedule it somewhere other than your peak sending hour, and keep an eye on messaging limits afterwards, since a new account ID is a new place for those numbers to be reported.

Checked against Meta's documentation on 28 August 2026.

Why did Meta make INR billing mandatory at all?

Meta does not say. There is no rationale published on the pricing page, and we are not going to supply one dressed as reporting.

What is observable is a pattern. Meta lists WABA billing in sixteen currencies, launched India localization on a specific date, shipped dedicated migration APIs "available as of June 1, 2026" to move accounts onto local currency, and then set a hard date after which the old currency stops working (Meta — Pricing on the WhatsApp Business Platform). That is the shape of a platform consolidating a market onto one billing rail rather than running two indefinitely.

Whether the driver is regulatory, tax, payment-rails economics or simple operational tidiness is not something Meta has stated and not something we can read off a documentation page.

What matters commercially is narrower and is stated: after 1 January 2027, an eligible customer on a non-INR WABA does not get message delivery. That is enough to act on without a theory of why.

For what it is worth, the same pull toward rupee-denominated billing runs through the vendor layer. WabaCRM moved its own software pricing to rupees in August 2026 for a reason that has nothing to do with Meta's deadline and everything to do with UPI and netbanking working only on rupee orders — our pricing page shows the result. That is a software subscription, entirely separate from what Meta charges you for messages, and moving one does nothing to the other.

Checked against Meta's documentation on 28 August 2026.

Every Meta quotation on this page was read from Meta's own documentation on 28 August 2026. Meta changes that documentation without notice; the linked pages are authoritative and this one is not.