This Year's INFORM Act Verification Wave Is Catching Sellers on Small Mismatches. Here's What's Actually Going Wrong

The INFORM Consumers Act's annual recertification requirement isn't new, it's been running since Amazon rolled out its verification experience in 2024. What's notable about this year's cycle is how many sellers are describing the same specific failure patterns, and how little margin Amazon's automated review appears to be leaving for small mismatches that have nothing to do with actual compliance risk.

What the INFORM Act Actually Requires, Briefly

Under the federal law, Amazon must collect, verify, and disclose certain business information for high-volume third-party sellers, defined as sellers with 200 or more transactions and $5,000 or more in gross revenue within a 12-month period. That information, identity, bank account details, business address, phone number, and tax ID, requires annual reverification, and Amazon's own INFORM Consumers Act help page lays out the basic categories Amazon must confirm each cycle.

What's Actually Going Wrong This Cycle

Chris McCabe, a former Amazon employee who now runs an account-appeals practice and has spent years working annual verification cases directly, described the current wave in a recent LinkedIn post, flagging several specific patterns worth knowing before you're caught in one of them.

Bank account verification is failing on formatting, not substance. McCabe points to a specific pattern where the legal entity name, operating address, or general formatting on a submitted bank statement doesn't line up exactly with what's on file in Seller Central, and Amazon's automated system rejects the submission outright. Often the underlying cause is something as mundane as a recent address change that hasn't fully propagated across every document a seller has on hand.

That specific problem shows up independently in Amazon's own seller forums. One recurring thread describes a structural version of it: the "Legal Entity" and "Country of Establishment" fields can appear updated in Seller Central without the change actually taking effect on Amazon's backend, so when annual reverification runs, the system checks against the original data the seller entered at signup, not the corrected version, and rejects a legitimate submission as a mismatch.

Fixing one field can reset the whole review. According to McCabe, uploading a revised document to correct a single field, an address, for instance, doesn't just update that one item. It can send the entire verification file back into a specialist review queue with a stated turnaround of ten or more business days, even when the rest of the submission was already accepted. A separate, independently reported case on Amazon's own forums illustrates a related version of this problem: a seller whose business license address change hadn't yet been manually submitted had the system auto-submit their verification using the outdated information on file, triggering an automatic failure the seller had no chance to prevent.

"In Progress" can outlast the deadline it's attached to. McCabe describes sellers being told they have a fixed number of days remaining, submitting everything requested well within that window, and still ending up waiting past the original deadline because the review itself is delayed on Amazon's side, an outcome the seller has essentially no control over once documents are in.

Why This Matters More Than a Routine Compliance Task

None of these patterns describe sellers doing anything wrong. They describe formatting mismatches, backend data lag, and review-queue delays, procedural failure points that can still result in a suspended account or withheld funds despite a seller having submitted accurate, legitimate documentation. That gap, between actual compliance and what an automated system accepts as proof of compliance, is the real risk this cycle, not fraud or bad-faith noncompliance.

What Actually Works When You Get Stuck

McCabe's core advice is worth taking seriously specifically because it runs against most sellers' instinct under pressure:

Get the exact failure reason before resubmitting anything. Resubmitting the same materials hoping something changes wastes a review cycle. If a submission was rejected, pin down precisely which field or document triggered it before sending anything new.

Don't flood escalation channels hoping volume moves things faster. According to McCabe, sending repeated urgent messages to executive-level contacts while a case is still genuinely under review doesn't speed anything up, it routes into a general queue alongside everyone else doing the same thing, which can slow resolution rather than accelerate it.

Work directly with account health representatives to identify exactly what's missing, rather than assuming a rejection means something was never submitted at all, since in several of the patterns described here, the actual documents were correct, the mismatch was elsewhere.

If You're Currently Stuck in a Verification Loop

The specific failure patterns above, address-related bank mismatches, resets triggered by single-field corrections, and delays that outlast their own stated deadlines, are worth checking against your own current case before assuming your situation is unique. If your business address, legal entity name, or banking details have changed at any point in the last year, that's the first place to check for a formatting mismatch before assuming the rejection reflects something more serious.

If you're also navigating other Amazon compliance requirements alongside this, our guide on surviving Amazon's TIC compliance crackdown covers a related but separate verification process, testing and certification for flagged product categories, worth knowing the two are distinct requirements with distinct deadlines, not variations of the same process.

Frequently Asked Questions

Is this year's INFORM Act verification wave different from previous years?

The underlying annual requirement is the same, sellers must reverify identity, bank account, address, phone, and tax ID information yearly. What's being reported this cycle is a concentration of specific failure patterns, address-related mismatches and resubmission resets in particular, rather than a change to the law or requirement itself.

What should I do if my bank verification fails?

Confirm that the legal entity name, address, and formatting on your submitted bank statement match what's currently on file in Seller Central exactly, not what you believe was updated. A recent address change is a common, easily overlooked cause.

Does correcting one document reset my entire verification?

Sellers and account specialists have reported this happening, a single corrected document triggering a full specialist review of the entire file rather than a targeted re-check of just the corrected item. Confirm current status directly with an account health representative rather than assuming a partial fix will be treated as complete.

Does emailing executive escalation contacts speed up a stuck review?

Based on direct account-appeals experience shared publicly, repeated urgent messages to high-level contacts while a case is still under active review generally don't accelerate resolution, and can route into a general queue rather than getting individual attention.

What happens if my account gets suspended during this process?

Suspension or fund withholding during INFORM Act non-compliance is a real possibility under the law. If you're already in a review loop, identifying the exact, specific reason for any rejection before resubmitting anything is the most reliable path forward, given how much of the current friction reported this cycle appears to stem from formatting and backend data issues rather than actual noncompliance.

Takeaways

• This year's INFORM Consumers Act annual reverification cycle is producing a concentration of specific, procedural failure patterns rather than substantive compliance problems, according to account-appeals practitioners working these cases directly.
• Bank account verification failures often trace back to formatting mismatches between submitted documents and what's on file, frequently triggered by an address change that hasn't fully propagated everywhere.
• Correcting a single field can reset an entire verification file into a lengthy specialist review queue, an outcome corroborated by separate seller reports on Amazon's own forums.
• Flooding executive escalation contacts with urgent messages while a case is genuinely under review tends to slow resolution, not speed it, by routing into a general queue.
• Getting the exact, specific failure reason before resubmitting anything is more effective than resubmitting broadly and hoping something changes.

For ongoing coverage of Amazon compliance requirements and Account Health issues, see our newsletter.