Meta Business Verification Documents: Exactly What Meta Accepts, and What "Ineligible for Verification" Means

The short answer: two facts, proven on paper

Meta is checking two things. First, that your business legally exists under a specific name. Second, that it is reachable at a specific address or phone number.

Every document rule follows from those two facts. One document proves the legal name. A second proves the address or the phone number. Occasionally a single document carries both and one is enough. Plan for two.

The flow lives in Security Center in Meta Business Suite. Click Start Verification, then enter your organization details (legal name, address, phone number, website). Meta next tries to match you against public records and shows you a list of candidate businesses to confirm. If nothing matches, you pick My business isn't listed or None of these match, and that is the point where Meta may ask you to upload official documents. You then choose how to confirm your connection, by email, phone, text message, WhatsApp message, or domain verification, and complete that step.

Meta's developer documentation for partner-led verification puts a hard ceiling on the upload step: a maximum of three documents per submission, in PDF, JPEG, JPG or PNG. Three is the ceiling, not the target. Two clean documents beat three ambiguous ones.

The document types Meta names

Meta's published lists vary by country, because company registries vary by country. Across Meta's own documentation, the same categories keep appearing.

One important split: a utility bill proves address and phone and nothing else. Meta states plainly that a utility bill is accepted only for business address and phone number, and is not an acceptable document for legal business name verification. A bank statement sits differently. Meta lists a business bank statement among the primary supported document types for business verification, though its Horizon developer documentation treats bank statements as supplementary. A submission built on a utility bill alone has nothing establishing that the company exists.

• Certificate or Articles of Incorporation
• Articles of Organization (for an LLC)
• Business registration or business license document issued by a government body
• Government-issued business tax document (in the US, an IRS CP 575 or Letter 147C)
• Tax registration certificate, such as an EU VAT certificate or an Indian GST certificate
• Partnership agreement, for partnerships
• Business bank statement, as address and phone evidence
• Utility bill in the business name, as address and phone evidence

The matching rules are stricter than people expect

This is a quiet way to fail. The business details you type into Business Settings have to match the documents you upload. Not approximately. Character for character where it counts.

Meta exposes a rejection reason in its API called LEGAL_NAME_NOT_FOUND_IN_DOCUMENTS. That string tells you what the reviewer is doing: looking for your typed legal name inside the document text and failing to find it. Meta's own developer documentation also names a mismatch between the uploaded document name and the account name as a common rejection reason.

Some specifics that decide the outcome:

• Use the legal entity name, not your trading name. If you are registered as Carson Holdings LLC and trade as Bench Clearers, the field says Carson Holdings LLC.
• Keep the suffix. LLC, Inc., Ltd. and GmbH are part of the registered name. Dropping one creates a mismatch.
• Match punctuation and spacing. Commas before LLC, ampersands versus "and", and hyphens all count.
• Use the registered address from the filing, not your warehouse or your mail drop, unless the filing shows that address.
• The phone number should be a business line that can receive the confirmation code. Meta sends the code to a contact method you select.
• Both documents showing the legal name is the safest build, given what the rejection enum is looking for.
• If your document is not in a language Meta supports, get it translated into English with the translating agency's official stamp. A translation you produced yourself will not be accepted.

File format, size and legibility

The technical requirements are simple, and it is easy to fail on them rather than on substance.

Accepted formats are PDF, JPEG, JPG and PNG. Size limits differ by surface: Meta's partner-led verification documentation caps each document at 5 MB, while Meta's Horizon developer verification documentation allows 10 MB per document. Build to 5 MB and you are safe in both.

Meta's documentation is explicit that documents must be legible with all text readable, and that blurry, cropped, or low-resolution files will fail. Documents must not be expired.

A few practical rules that follow from that:

• Scan, do not photograph. A flatbed or a phone scanner app beats a handheld photo with a shadow across the seal.
• Show the whole page, including all four corners, the header, and any seal or signature block.
• Do not crop, rotate, annotate, or let a corner fall outside the frame. Redaction is the exception. Meta's own business documents article tells you to cover any personal information it does not need, such as a social security number or the local equivalent, if that information appears on the page. The stricter rule, where Meta will not accept an image modified in any way including to cover up or block out information, comes from its personal ID policy and governs the identity step, not your company paperwork.
• Keep it in color. Seals and stamps are often the part that proves the document is official.
• Do not compress a PDF to the point where the text goes soft. Under 5 MB at readable resolution is achievable for a two-page filing.

"Ineligible for verification" is not a rejection

This state is easy to misread, and misreading it sends you down the wrong path.

Meta's own Business SDK defines the verification_status field with these values: expired, failed, ineligible, not_verified, pending, pending_need_more_info, pending_submission, rejected, revoked, and verified.

Look at that list carefully. "ineligible" and "rejected" are different states. If you are seeing ineligible, or a greyed-out Start Verification button, your documents were never the problem. Meta has not looked at them. Your business portfolio cannot enter the queue at all.

Re-uploading better documents will not change anything, because there is nothing to upload into. Meta's own wording is that if you see Ineligible for verification, you do not need to complete verification in Security Center at all. Depending on the product you are trying to unlock, Meta may email or notify you from a different platform with its own instructions. Look for that notification first, before you start hunting for a defect in the portfolio.

Things that put a portfolio in that position:

• No qualifying asset attached. Verification is triggered by something that needs it. If you are a developer, an app has to be created and connected to the portfolio first. For WhatsApp, a WhatsApp Business Account has to exist before the button activates.
• The portfolio is restricted, disabled, or carrying a policy limitation. Resolve that in the Account Quality dashboard first. Verification will not override a restriction.
• Verification is already complete, or already in flight, on that portfolio.
• A duplicate portfolio for the same legal entity. Consolidate onto the one holding your real assets.
• The portfolio's country is not in scope for verification.
• A brand-new portfolio that has not finished provisioning.

The government ID step is yours, and only yours

Business verification is about the company. Some flows, including Meta Verified, also ask a human to confirm their identity. Meta states you may be asked to provide a government-issued ID, and in selected regions to submit a selfie video.

For Meta's general ID verification flow, Meta accepts one government ID showing either your name and date of birth, or your name and a photo. Meta Verified for businesses is stricter: there Meta asks for a valid, unexpired government-issued photo ID carrying a name similar to the business asset you are verifying. Its published examples include a driver's license, national identity card, passport, or birth certificate. Where a government ID is not available, Meta accepts two different non-government documents, at least one of which shows a date of birth or photo.

We do not handle any of that. The business owner uploads their own ID, in their own session, directly to Meta.

This is a firm line, not a preference. We never take a client's government ID, passport scan, driver's license, password, or card number. We prepare the company-side documents, we check the matching, we tell you exactly which screen to be on and what to upload, and you complete the identity step yourself. Any agency willing to collect your passport scan and log in as you is creating a risk for you that no verification outcome justifies.

How long it takes

Timelines vary by path, and honest ranges are wide.

Meta's partner-led verification documentation gives an average turnaround of about 5 minutes, and notes it can take several hours. Meta's Horizon developer documentation says most verifications are processed within 48 hours, though some take longer. Meta's help center puts a figure on the standard Security Center path: a decision may take up to 14 business days. That is closer to three calendar weeks than two. Plenty of submissions clear far sooner, but 14 business days is the number to plan against.

If you are past 14 business days with no movement, check your portfolio state rather than resubmitting. A stalled case and an ineligible portfolio look identical from the outside and have completely different fixes.

When you should not submit yet

We would rather tell you to wait than take a fee for a submission we expect to fail.

Do not submit if your registration is not yet filed, or is filed under a name you no longer use. Fix the registry first. Meta is reading a government record, and it cannot approve a name that record does not contain.

Do not submit if your registered address changed and the filing still shows the old one. Update the filing, then verify.

Do not submit if your portfolio is currently restricted. Clear the restriction first.

Do not submit if the only document you have is a utility bill or a bank statement. You have address evidence and no existence evidence.

Do not submit a fourth time on a partner path after three rejections. That route is closed and you need the direct one.

And if you are a sole trader with no registration certificate anywhere, be honest with yourself about what you are asking Meta to confirm. In some countries there is a straightforward answer, such as a tax registration. In others there is not, and no amount of resubmitting produces the document that does not exist.

Working with us

We ran this stack on our own business before we sold it to anyone. Bench Clearers, our hockey apparel store, has a Verified Mark Certificate through GlobalSign, BIMI live in Gmail, and Meta Verified on a 52,000-follower Instagram account. We work only through official channels, we never touch your passwords, ID documents, or card numbers, and we screen jobs before we take them. If we do not think your submission can succeed as things stand, we will tell you what to fix first and decline the work rather than take the fee. Meta makes the final call, always, and nobody can promise you otherwise.