Quick answer: Australia’s SMS Sender ID Register has been enforceable since 1 July 2026, and the second enforcement window now under way makes the change operational rather than theoretical: participating telcos’ pre-send checks, which warned on unregistered alphanumeric sender IDs during the first window, now block, and active checks extend to MMS. If you send Australian traffic under an alphanumeric name, the question is no longer whether the identity should be registered but whether the exact string on your live routes is registered, because the ones that are not are the ones bouncing at the pre-send check. This update covers where enforcement stands in October 2026, what ACMA’s published position says, and the tenant-owned checks to run before your next Australian send. Nothing here is a Devotel Orbit product change; the controls referenced at the end already exist on the platform.
What the second enforcement year changed
Two shifts define the current window, both covered on ACMA’s SMS Sender ID Register pages:
- Pre-send checks now block instead of warn. When enforcement began on 1 July 2026, participating telcos checked outbound alphanumeric sender IDs against the register, but an unregistered identity more often drew a warning or an “Unverified” label than a hard stop. The second window is the change operators feel: the pre-send check returns a block for unregistered IDs on participating networks. A sender that tested fine in June and assumed the posture would hold can now fail at the pre-send check with nothing changed on their side except the calendar.
- The register’s MMS scope is actively checked. The register always covered alphanumeric sender IDs used for SMS and MMS, but first-window checks concentrated on SMS. The second window extends active pre-send checks to MMS traffic, so MMS-only programs that treated the register as an SMS story face the same question as everyone else: is the exact identity registered?
The through-line is that enforcement moved from the register’s existence to its operation at send time. The rulebook is the same as it was on 1 July; the difference is what happens to a message whose sender is not on the register.
What the explainer already covered, so this post does not repeat it
Our register explainer, Australia’s SMS Sender ID Register in 2026, remains the reference for the mechanics this update takes as given:
- Who must register, and the 1 July 2025 opening and 1 July 2026 enforcement dates.
- Why registration follows the sender identity, not the platform account or aggregator relationship, and the authorization evidence to keep.
- The tenant posture: a per-identity record, an accountable owner, and reconciliation after every route or brand change.
Read that post for the how of registration. This one is the enforcement update: what the checks do now, what is bouncing, and what to reconcile this quarter. If you have not registered an identity yet, the explainer is your starting point; this post is what happens after filing.
What is actually bouncing
The failures arriving in the second window share a shape:
- Unregistered alphanumeric IDs blocked pre-send. The dominant case. Campaigns that sent fine through the first window now stop at the pre-send check on participating networks, because the warning became a block. The delivery receipt shows a rejection, not a relabel.
- Exact-string mismatches. The registered identity and the configured sender differ by a space, a punctuation mark, or a case variant. The register holds an identity as filed; the check compares what is on the wire.
- MMS senders that skipped registration. Programs that read the register as SMS-only and left MMS identities unregistered now meet the same check on the MMS path.
- “Unverified” labelling where blocking is not applied. Not every network blocks; some still label. A receipt that says delivered does not prove the recipient saw the brand name you expected.
None of these is a transport fault, and none retries usefully. They are registration-state failures, and the fix sits in the registration record and the live configuration, not in the route.
October 2026 enforcement state
The state of play, against ACMA’s published position on the SMS Sender ID Register:
| Item | State as of October 2026 |
|---|---|
| Register open for applications | Since 1 July 2025 |
| Enforcement period | In force since 1 July 2026 |
| Pre-send checks at participating telcos | Active; the second window blocks unregistered IDs rather than warning |
| Scope | Alphanumeric sender IDs on SMS and MMS |
| Unregistered ID treatment | Blocked pre-send, or labelled “Unverified,” depending on the receiving telco |
| Who registers an identity | The business or brand the identity represents, not the messaging platform |
Treat the table as a status snapshot, not a compliance conclusion: confirm the current position on ACMA’s pages and with your messaging provider before you rely on a row for a launch decision.
The checks you own: Channels → SMS → Sender IDs
Registration is tenant-owned compliance, filed under your entity for your traffic; no platform can certify it for you. What a platform can do is make the reconciliation cheap, and that is where the Channels → SMS → Sender IDs screen comes in. Before Australian volume, and again after any route, brand, or agency change, run the same pass there:
- Pull the list of alphanumeric identities configured on routes that can reach Australian numbers, including agency-managed traffic.
- Match each configured sender against the registration record: exact string, owning entity, approval evidence.
- Pause any identity whose registration you cannot produce, and resolve the registration rather than quietly substituting another name.
- Reconcile again after every change that can alter the sender on the wire.
The screen shows your configured identities; the register status is your record’s job. Keeping the two in agreement is the whole game in the second window: the network-side check is automated and unarguable, so the only place left to catch a mismatch is your own reconciliation.
New Zealand is running a parallel transition
New Zealand is moving on sender identity under its own framework, the Unsolicited Electronic Messages Act, on a clock that is not aligned with ACMA’s. The practical read for trans-Tasman programs: an Australian registration does not satisfy New Zealand requirements, a New Zealand approval does not register an identity in Australia, and a launch plan that treats the two as one workstream will miss one of the two deadlines. Our New Zealand sender rules reference tracks the NZ side; verify the current position before sending.
Related reading
- Australia’s SMS Sender ID Register in 2026 — the registration mechanics this update assumes.
- Sender ID Registration Country Playbook — the sender-ID cluster hub: per-country rules across the markets you launch, with Australia as one row.
- Australia Spam Act compliance reference — the consent and sender-identification obligations that run alongside the register.
- Sender ID registration guide — the platform walkthrough for filing and maintaining sender ID registrations.
Frequently asked questions
My sender ID delivered fine during the first window. Why is it blocking now?
Because the first window’s pre-send checks warned more often than they blocked, and the second window changed that treatment on participating networks. Nothing on your side needed to change for the outcome to change. Verify the exact identity’s registration status on ACMA’s SMS Sender ID Register pages and reconcile your configured sender against it.
Does registering for Australia cover my MMS traffic?
The register covers alphanumeric sender IDs on SMS and MMS, and the second window checks MMS actively. An identity registered for an SMS program is on the register for MMS too, but only if the exact string on the MMS path matches the registration.
Does this change how Devotel Orbit routes my Australian traffic?
No. Outbound routing and registration posture are separate concerns. The platform carries your traffic and keeps your configured sender IDs legible; the registration itself remains a tenant-owned record, audited as yours because it is yours.
Published 13 October 2026.