Quick answer: H2 2026 moved two layers at once. The fee layer kept repricing — destination operators raised per-message pass-throughs and registration-side fees kept accumulating on 10DLC, while the major vendors split how a message is metered (Twilio billing SMS per message, Vonage and Infobip billing conversation-capable channels per conversation, per our H2 2026 carrier-fee explainer). The enforcement layer went operational in three markets on published clocks: Australia's Sender ID Register has been enforceable since 1 July 2026 and its October second window blocks unregistered alphanumeric IDs pre-send instead of warning, with active checks extended to MMS; India's DPDP Phase II makes Consent-Manager receipts mandatory for consent-based A2P SMS on 13 November 2026; and US carriers completed their H2 10DLC sanction sweeps with TCR vetting now verifying traffic rather than filing completeness. This round-up ties those events into one calendar, states each row as the carrier- or regulator-posted change it is, and maps every row to the tenant-owned check it triggers on Devotel Orbit. Nothing here is a Devotel Orbit product change; every control referenced below already exists on the platform.
The H2 2026 fee and enforcement calendar, per market
Each cell states the carrier- or regulator-posted change as published; the deep-dive column links the explainer that carries the mechanics. Where the underlying source reports a percentage or a fee figure, the explainer quotes it — this table deliberately carries posture and dates, not opinion.
| Change | US (10DLC) | UK | DE | FR | AU | IN |
|---|---|---|---|---|---|---|
| Fee schedule, H2 2026 | Registration-side fees keep accumulating; H2 sanction sweeps completed (carrier-posted, per the enforcement-state explainer) | Destination-operator pass-throughs repriced per segment; the posted "from" rate is public and decomposable (carrier-posted, per the fee explainer) | Same operator pass-through layer; alphanumeric sender IDs filtered or replaced on German routes (carrier-posted, per the Germany explainer) | Same fee layer, plus the statutory 20:00–08:00 and Sunday/public-holiday send window in force (regulator-posted, per the France explainer) | Register-side fees apply to alphanumeric sender IDs; enforcement in force since 1 July 2026 (regulator-posted, per the register explainer) | Consent-Manager receipts mandatory for consent-based A2P SMS from 13 November 2026 (regulator-posted, per the DPDP Phase II explainer) |
| Enforcement window now open | TCR vetting verifies live traffic, not filing completeness; rejection mix shifted since H1 (carrier-posted) | No new window; the change is the fee layer, not a regime | No new window; UWG §7 consent and the Abmahnung economy unchanged | CNIL enforcement of the send window and prior opt-in ongoing | Second window under way in October 2026: pre-send checks block unregistered IDs rather than warn, and active checks extend to MMS (regulator-posted, per the October enforcement update) | Phase II enforcement begins 13 November 2026 |
| Tenant-owned check it maps to | Campaign readiness pass before the next sweep | Repricing pass on your top destinations | Consent evidence and sender-string reconciliation | Quiet-hours configuration against the statutory window | Sender-ID register reconciliation, exact string, SMS and MMS | Consent-proof scope against the receipt model |
Read the table as a status snapshot, not a compliance conclusion: confirm the current position with the named source and your messaging provider before you rely on a row for a launch decision. Markets outside this table — including Mexico, where short-code reader numbers replaced alphanumeric sender IDs under the 2026 rules — carry their own explainers because their changes are structural rather than calendar events.
What tenants need to do
Every row above resolves to a check you own. Platform controls can make each check cheap; none of them can be filed on your behalf, because registration, consent evidence and send-window policy are tenant-owned compliance:
- Review quiet-hours configuration per market. France's statutory window and Germany's conventions are configuration, not vendor policy. The quiet-hours settings API announcement covers the console surface where per-market send windows live; reconcile each configured window against the statutory row before a campaign, not after a complaint.
- Re-scope your consent proof. India's receipt model and the EU consent regimes ask the same question in different vocabulary: for each consent-based flow, can you produce the evidence, in the form the regime names, at send time? The compliance bundles hub maps the packs that provision the controls; your job is the scope — which flows, which markets, which evidence.
- Run your fallback matrix. Germany's sender-ID filtering and Australia's pre-send blocks mean the configured sender is not always the sender on the wire. For each market, name the fallback identity, verify it is registered where registration applies (Australia's register covers SMS and MMS), and pause any identity whose registration or authorization evidence you cannot produce.
None of these is new work invented for this quarter; they are the same tenant-owned controls the explainers name, run against this quarter's calendar.
What did not change
Most markets entered Q4 2026 with their regime exactly where it was at the start of the year. The UK and Germany moved on the fee layer, not the rulebook: no new UK statutory send window, no change to UWG §7 or the Abmahnung posture. The US regime is the same rulebook with stricter verification, not new rules. For senders into markets outside the table, the durable answer is unchanged too — Mexico's structural shift and New Zealand's parallel sender-identity transition run on their own clocks, and the country playbook remains the reference. Stabilization is itself useful information: a regime that did not change is a reconciliation you can schedule rather than an emergency, and a fee layer that moved without a rulebook change is a repricing pass, not a compliance project.
Looking ahead: Q1 2027
The next installment of this cadence is the Q1 2027 forward look, which recaps what is live on Devotel Orbit today and labels the agenda for the coming quarter as Preview. When the Q4 2026 enforcement windows close out — Australia's second window through to year-end, India's 13 November start — the quarterly review will carry the retrospective the same way the Q4 2026 review closed the loop on the Q4 preview.
Related reading
- 10DLC Carrier Registration in Q4 2026: The State of Enforcement — the US row in depth.
- France A2P SMS Rules, Decoded and Germany A2P SMS Rules, Decoded — the EU rows in depth.
- Australia's SMS Sender ID Register in 2026 and the October 2026 enforcement update — the AU row in depth: 1 July 2026 enforcement, the blocking second window, MMS scope.
- Mexico A2P Messaging Rules 2026 and India DPDP Phase II — the structural-shift markets.
- H2 2026 carrier-fee explainer — the fee-layer and metering-layer decomposition behind the UK/DE/FR cells.
Published 14 October 2026.