---
url: "https://dfylegitscript.com/blog/prior-enforcement-history-and-certification-eligibility"
title: "Prior enforcement history, and why disclosure beats discovery"
description: "An open regulatory action, a board complaint, a previous merchant termination or a warning letter attached to a principal is rarely what ends a LegitScript application, and concealing one reliably is, because the record is discoverable and being found converts a fact into a credibility problem."
published: "2026-08-07T12:15:21+00:00"
modified: "2026-08-07T12:15:21+00:00"
---

# Prior enforcement history, and why disclosure beats discovery

An open regulatory action, a board complaint, a previous merchant termination or a warning letter attached to a principal is rarely what ends a LegitScript application, and concealing one reliably is, because the record is discoverable and being found converts a fact into a credibility problem.

## Key takeaways

- Disclosure beats discovery, because history rarely ends an application while being found concealing one reliably converts a fact into a credibility problem.
- History follows people as well as entities through public records, so a matter attached to a principal arrives with them at the next business they run.
- What changed afterwards does the work, since a dated account of what was fixed is the part a reviewer can actually weigh.
- A partner's record attaches to your model, because the pharmacy that dispenses for you is part of the business being assessed.

This is the question applicants most want to avoid asking out loud, so it is
worth answering plainly. History attached to a business or to a person behind it
is not usually disqualifying. Concealing it is.

The reason is mechanical rather than moral. A review establishes identity and
structure early, from public sources, and a matter that surfaces after going
unmentioned changes how every other statement in the file is read.

## What counts as history

Broader than most applicants assume, and it follows people as well as companies.

- Regulatory correspondence: a warning letter, an untitled letter, a state
  action.
- Professional board matters affecting a clinician associated with the business.
- A previous merchant account terminated for cause, or placement on an industry
  termination list.
- Litigation involving product claims, billing practices or patient harm.
- A prior certification declined, revoked or lapsed under adverse circumstances.
- A related company, whether or not the current business shares its name.

That last one is where applicants most often decide, honestly, that something is
not relevant. A principal's earlier venture is connected to them in public
records, and a reviewer establishing who is behind the business will find it.

## Why it is discoverable

Because most of it is published. Regulatory letters are searchable and permanent:
our
[index of FDA warning letters](/research/glp-1-compounding-warning-letters)
covering compounded GLP-1 marketing exists precisely because those letters are
public documents. Board actions are published. Court filings are public.
Corporate registries connect people to entities.

None of that requires special access, which is the point
[what is discoverable about your business](/blog/where-a-certification-reviewer-looks-first)
makes at length.

## How to disclose it

Get in first, in the submission, in your own words.

**State the facts plainly.** What happened, when, which entity or person, and
what the matter concerned. Do not characterise it as trivial; that judgement
belongs to the reader and attempting it reads as advocacy.

**Say what was resolved and how.** Closed matters are much easier to place in
context than open ones, and the resolution is usually the most useful sentence
available.

**Say what changed afterwards.** This is the part that does the work. A business
that received a letter about marketing claims and can show the allowlist, the
audit and the review gate that followed is describing a corrected organisation
rather than a past event.

**Attach the documents.** The letter, the closure, the consent order, whatever
exists. Supplying it removes the question of whether your description was
complete.

## The categories that behave differently

**Open matters.** Harder, and not automatically fatal. What matters is that the
file explains the current position honestly and that nothing about the business
suggests the underlying conduct continues.

**Matters concerning claims.** Common in this industry and closely connected to
what a certification review assesses anyway. Expect the marketing to be read
carefully, and expect the corrective work to be the substance of your answer.

**Matters concerning patient harm or diversion.** The most serious, and the ones
where the structural questions come before the presentational ones.

**Payments history.** A prior termination shows up through the acquirer rather
than the certifier, and it affects boarding independently. Both conversations go
better when the merchant raises it first.

## What not to do

Do not restructure to obscure a connection. Ownership through entities with
limited public visibility invites the question of who is behind the business,
and the answer needs to be available.

Do not omit a principal from the file because their history is inconvenient. An
undisclosed officer discovered in a filing is a worse fact than the history
itself.

Do not describe a matter as resolved if it is not, and do not describe a lapsed
certification as a business decision if it was not. Those are the specific
statements that turn a difficult disclosure into a credibility problem, which is
the pattern
[what disqualifies an application](/blog/what-disqualifies-a-legitscript-application)
returns to.

## When the history belongs to a partner

The version applicants think about least. Your dispensing pharmacy, your
provider network or your fulfilment platform may carry a record of its own, and
it attaches to your model because the model includes them.

Ask, before you sign and again before you file: has this partner received
regulatory correspondence in the last three years, and what came of it? A
partner who answers openly is a partner with a compliance function. One who
deflects has told you something useful.

Where a partner does carry history, that is not automatically a reason to
change, and it is a reason to know. The file can address it: what the matter
was, what the partner changed, and why the relationship is still appropriate.
What cannot be addressed is a reviewer finding it while you appear not to have
looked, which is the same failure as
[not knowing who actually dispenses](/blog/pharmacy-partner-requirements-for-telehealth-clinics).

## Preparing the disclosure before you need it

Write it once, as part of the file, and keep it current. One page per matter:
what happened, when, who was involved, how it was resolved, what changed, and
where the documents are.

You will use it more than once. Acquirers ask, partners ask, marketplaces ask,
and investors ask. A business that answers all of them from the same prepared
account is consistent by construction, and consistency is what the whole exercise
is measuring.

## The reassurance worth offering

Businesses with history get certified. New businesses with no record get
certified. What separates the applications that succeed from the ones that stall
is not the past; it is whether the file tells one story that survives being
checked.

## Frequently asked questions

### Will a past FDA warning letter stop me being certified?

Not on its own. What matters is whether it is disclosed, whether the conduct it concerned has been corrected, and whether the file explains both. A letter found after going unmentioned is a much larger problem than the letter itself.

### Do I have to disclose a principal's previous company?

If it is connected to them in public records, assume it will be found. Reviews establish who is behind a business from corporate filings, and an undisclosed connection discovered that way affects how the rest of the file is read.

### What about a merchant account terminated years ago?

Raise it, with your acquirer as well as in the application. A prior termination for cause can follow a business through industry systems, and both conversations go better when the merchant is the one who brings it up.

## Disclaimer

LegitScript is a trademark of LegitScript LLC. VeriScripts is an independent application-preparation service. It is not affiliated with, endorsed by, or certified by LegitScript LLC, and claims no sponsorship or partnership with it. We prepare, submit, and manage the application; LegitScript alone decides whether certification is granted. "LegitScript" is used here only to name the certification these applications are for.