Number Porting Rejected: Common Reasons and How to Fix Them
A rejected number port is almost always down to a mismatch between the details on your port request and what your current provider has on file — not a sign of a deeper problem. The most common causes are incorrect account details, an invalid Letter of Authorisation, an outstanding balance, or a number that's already mid-transfer elsewhere. Nearly all of these are fixable by correcting the paperwork and resubmitting.
Reason 1: Name or Address Doesn't Match
This is the single most common cause of a rejected port. If the business name or address on your port request doesn't exactly match what your current provider has on record — even a small difference, like "Ltd" versus "Limited," or a missing suite number — the port will be rejected.
Fix: Pull the exact name and address straight from a recent bill or account portal with your current provider, rather than from memory or your own records, and use that wording exactly.
Reason 2: Incorrect Account Number
Port requests need your current provider's account number, and if it's wrong or slightly out of date, validation fails.
Fix: Check your most recent invoice for the correct account number, not an old one you might have saved from years ago, since account numbers do sometimes change after internal system migrations.
Reason 3: Invalid or Incorrectly Signed Letter of Authorisation
A Letter of Authorisation (LOA) needs to be signed by someone with genuine authority on the account, dated recently, and formatted the way your losing provider expects.
Fix: Confirm who's listed as the authorised contact on your current account before signing — it's not always whoever handles day-to-day admin. If your new provider supplies an LOA template, use theirs rather than writing your own.
Reason 4: Outstanding Balance on the Account
Some providers won't release a number if there's unpaid balance on the account it's leaving.
Fix: Check your account is fully paid up before submitting the port request, or settle any outstanding balance immediately if the rejection flags this as the reason.
Reason 5: Account Already Cancelled or Inactive
If your existing service has already been cancelled or the account closed, the number may no longer be portable, since it can fall out of service once the account's gone.
Fix: This is why providers consistently advise against cancelling your old service before a port completes. If this has already happened, contact your current provider directly and ask whether the number can still be recovered — timescales matter here, so act quickly.
Reason 6: Number Already Being Ported Elsewhere
Occasionally, a port gets rejected because the number's already mid-transfer to a different provider, sometimes from an old, forgotten request.
Fix: Contact your current provider to check whether any other port request is active on the number, and cancel it if it's no longer wanted, before resubmitting your own.
Reason 7: Non-Transferable Number Type
A small number of legacy or specialist number ranges genuinely can't be ported, regardless of paperwork accuracy.
Fix: Ask your new provider to confirm upfront whether your specific number type is portable, before you commit to a migration plan built around keeping it.
What to Do If Your Port Is Rejected
- Read the rejection reason carefully — it's usually stated explicitly, not left vague.
- Correct the specific issue, using information taken directly from a recent bill or your current provider's account portal.
- Resubmit the port request through your new provider.
- If a second attempt is also rejected for the same reason, ask your new provider to contact the losing provider directly, since some issues are easier to resolve provider-to-provider than through repeated resubmission.
How to Avoid Rejection in the First Place
- Use a recent bill, not memory, for every detail on the port request
- Confirm who's authorised to sign the LOA before you need it
- Check your account balance is clear
- Don't cancel your existing service until the port is confirmed complete
- Ask your new provider upfront if there's anything unusual about your number type
Frequently Asked Questions
How many times can I resubmit a rejected port? There's no fixed limit — you can resubmit as many times as needed once the underlying issue is fixed, though it's worth getting it right on the second attempt where possible to avoid unnecessary delay.
Does a rejected port mean I've lost my number? No, not on its own. A rejection simply means the request wasn't approved as submitted — the number stays with your current provider until a port is successfully completed.
How long does a resubmitted port take compared to the first attempt? Broadly the same timescale as the original request, since it goes through validation again from scratch.
Should I contact my current provider directly if my port keeps getting rejected? It's usually more effective to let your new provider manage this, since they're the one submitting the request and have a direct relationship with the process — but it doesn't hurt to check your own account is in good standing in the meantime.
Most rejected ports are a paperwork problem, not a real obstacle — they just need the right details resubmitted. Request a quote if you'd like T2K to manage your port and handle any rejections on your behalf, or read our guide to how long porting normally takes to plan your migration realistically.
