Meta Business Verification — Rejection Reasons & Troubleshooting Guide

For: Chakra Chat Support / Onboarding team Use this when: A client's Meta Business Verification (submitted directly, or via partner-provided information) comes back rejected, incomplete, or stuck.

This guide has two layers:

1. Official system reason codes — what you'll see when a submission is processed via partner-provided information (the exact values Meta returns).
2. Broader troubleshooting — for cases submitted directly by the client, where Meta shows a general message rather than a formal code.

Start with Section 1 if you're looking at a partner submission result. Use Section 2 for everything else.

Section 1: Official rejection reason codes (partner-submitted verification)

When business verification is submitted using partner-provided information, Meta returns one of these values. This is the authoritative list — match the code exactly, then follow the fix.

ADDRESS_NOT_MATCHING

What it means: The country in the submitted address doesn't match the country on the client's business profile.

Note: This checks the country, not the full street address — so this is specifically a country-level mismatch, not a minor formatting difference.

Fix:

1. Confirm which country is actually correct — check the client's business profile in their Meta account against what was submitted.
2. Either correct the submission to match the profile, or have the client update their business profile to match, then resubmit.
3. Don't guess — confirm with the client which one is wrong before editing anything.

BUSINESS_NOT_ELIGIBLE

What it means: The client isn't eligible for verification through partner-provided information for this submission.

Fix:

1. This isn't something you can fix by editing and resubmitting the same way.
2. Direct the client to apply for Meta Business Verification directly through their own Meta Business Portfolio/Suite, rather than through partner-submitted info.
3. Let them know this is a Meta eligibility decision, not a data error on either side.

LEGAL_NAME_NOT_MATCHING

What it means: The legal name in the submission doesn't match the legal name or business name on the client's business profile. Meta checks this multiple ways — exact match, "fuzzy" match, and normalized match — so even close variations can still fail.

Fix:

1. Get the client's exact legal name as it appears on their official registration document — word for word, including suffixes (Ltd, LLC, Inc, GmbH, etc.).
2. Compare it character-by-character against both the submission and the business profile.
3. Correct whichever one is wrong (submission or profile) so they match exactly, then resubmit.

LEGAL_NAME_NOT_FOUND_IN_DOCUMENTS

What it means: Automated document review couldn't locate the business legal name anywhere in the uploaded documents. Two common causes:

• The legal name genuinely isn't printed anywhere in the document
• The text is unclear, low-resolution, or otherwise hard to read

Fix:

1. Open the submitted document yourself and confirm the legal name is actually printed on it.
2. If it's not there: this document isn't a valid choice — use a different official document that does show the legal name.
3. If it is there but hard to read: get a clearer scan or photo — good lighting, high resolution, no glare, all text sharp — and resubmit.

MALFORMED_DOCUMENTS

What it means: The uploaded document(s) couldn't be processed at all. Common causes:

• The file is corrupted
• The file is password-protected
• The file format isn't supported

Fix:

1. Ask the client how the file was created/exported — password protection is a frequent, easy-to-miss cause.
2. Have them remove any password protection and re-export or re-save the file.
3. Confirm it's in a standard, supported format (PDF, JPG, PNG are generally safest).
4. Re-upload and resubmit.

NONE

What it means: This isn't a rejection — it indicates the submission was not rejected. If you see this value, don't treat it as an error to fix.

WEBSITE_NOT_MATCHING

What it means: The website domain in the submission doesn't match the website domain on the client's business profile.

Fix:

1. Confirm the correct, live domain the client actually wants associated with their business.
2. Either correct the submission to match the profile, or update the business profile to match, then resubmit.
3. While you're in there, it's worth double-checking the site is actually live and clearly shows the business name — a mismatched domain and an unverifiable domain are different problems, and it's easy to fix one and still get flagged for the other.

Quick lookup: official codes

Section 2: Broader troubleshooting (direct client submissions)

If the client submitted verification themselves and got a general "not approved" message rather than one of the codes above, work through this instead.

Step A — Get the exact message, if there is one

Meta sometimes shows more specific wording even outside the formal codes. Ask the client to copy the exact text — it usually narrows things down fast.

Step B — No specific message? Walk through this checklist

Have the client check each of these, in order:

1. Does your business name match your document exactly (including Ltd/LLC/Inc, punctuation)?
2. Does your address match your document exactly, including how it's abbreviated?
3. Is your phone number listed, and does it match?
4. Is your document one Meta actually accepts (see list below)?
5. Is the document recent, clear, and unedited?
6. Is your website live, and does it clearly show your business name, logo, and contact info?
7. Are you using a business email address, not a personal Gmail/Yahoo account?
8. Are you a full admin on the account? Only full admins can submit verification.
9. Do you have at least two admins with two-factor authentication enabled?
10. Has this business, or a connected WhatsApp Business Account, had any past policy issues? If so, that needs resolving first.

Step C — Accepted document types

Accepted:

• Certificate of Incorporation / Formation
• Articles of Incorporation / Association
• Business License or Operating Permit
• VAT certificate or equivalent tax registration
• Business bank account statement (showing business name and address)
• Utility bill in the business's name
• Government-issued business ID / Chamber of Commerce extract
• Business credit report

Not accepted:

• Invoices or purchase orders
• Self-filled forms without an official stamp
• Personal tax returns or personal bank statements
• Screenshots, flyers, letterheads, marketing materials
• Anything that looks edited or self-generated

If the document is in an unsupported language, attach a certified translation alongside the original — not instead of it.

Step D — Authorization-type rejections need careful handling

If a message suggests Meta couldn't confirm the client is authorized to represent the business, don't just resubmit right away:

• Confirm the person submitting is genuinely authorized (owner, or someone with clear authority).
• Double-check every piece of submitted info is accurate and consistent.
• Repeated fast resubmissions on this specific type of issue tend to invite more scrutiny, not less — get it right before trying again.

Step E — General advice for every case

• Don't resubmit immediately after a rejection. Fix the specific issue first, then wait before retrying.
• Check spam/junk folders — sometimes Meta asks for more info instead of rejecting outright, and a missed request becomes an automatic rejection.
• Don't change other business details mid-review (name, address, website) — this can trigger extra scrutiny.
• A "Verified" pop-up isn't always the full story — check the actual status in Security Center.
• If "Start Verification" is greyed out, the account usually just doesn't have anything connected yet that requires verification — connecting a WhatsApp Business Account typically resolves this.

Escalate when:

• The client has been rejected 3+ times despite following every applicable fix above
• The rejection is BUSINESS_NOT_ELIGIBLE, or the message mentions authorization/policy violations
• The account, or a connected WhatsApp Business Account, has a prior restriction that isn't clearing
• Verification has been "in review" far longer than normal with no update