This is not legal advice. It’s a reading of the regulation and FDA’s own guidance on it, as published in October 2026. Your quality and regulatory teams make the call for your systems.
Here’s why the question matters. At one rare-disease biotech, a large share of the old data bill existed because everything ran as regulated data. Change control, documentation, and qualification overhead on every change to a weekly commercial dashboard. That’s the right price for clinical data. It’s the wrong price for sales reporting nobody at FDA will ever ask to see.
What Part 11 actually covers
The scope is one sentence. 21 CFR 11.1(b) says Part 11 “applies to records in electronic form that are created, modified, maintained, archived, retrieved, or transmitted, under any records requirements set forth in agency regulations.” It also covers electronic records submitted to FDA.
The trigger is a records requirement in an FDA regulation. FDA calls those predicate rules. Its 2003 scope and application guidance says Part 11 “will be interpreted narrowly,” and that records “not required to be retained under predicate rules, but that are nonetheless maintained in electronic format, are not part 11 records.”
GxP is the umbrella for the good practice predicate rules, such as Part 58 for nonclinical labs and Part 211 for manufacturing. None of them governs a weekly TRx report.
Where commercial data sits
| Commercial data | FDA records requirement? | Part 11 applies? |
|---|---|---|
| Syndicated sales and prescriptions (IQVIA, Symphony) | None found | No, by default |
| Specialty pharmacy dispense and status files | None found | No, by default |
| Territory alignment and incentive comp inputs | None found | No |
| CRM call activity | None for the activity itself | No, unless it carries an adverse event |
| Drug sample requests and receipts | Yes, 21 CFR 203.60, kept 3 years | Yes, if electronic |
| Adverse drug experiences from commercial channels | Yes, 21 CFR 314.80, kept 10 years | Yes, if electronic |
| Open Payments submissions | CMS rule (42 CFR 403), not FDA | No, but the reporting company attests to accuracy |
The table reads the regulations cited. It is a starting checklist for your regulatory team, not a determination.
The two exceptions that live in commercial systems
Drug samples. The Prescription Drug Marketing Act rules let you keep sample request and receipt records electronically “provided the requirements of part 11 of this chapter are met.” Records go back at least 3 years. A paper form scanned into a computer becomes an electronic record that must meet Part 11 too. If your sample management feed lands in the commercial warehouse, the copy of record still needs to be the controlled one.
Adverse events. 314.80(b) requires prompt review of adverse drug experience information “from any source,” and it names “commercial marketing experience” explicitly. Field reps, hub services, and specialty pharmacy patient status notes are commercial sources. A safety signal in any of them belongs in the pharmacovigilance system, which keeps it 10 years. Your commercial data platform’s job is to route it there and not be its only home.
What to control instead
Outside those two, you still want an audit trail. It just isn’t Part 11’s. Due diligence asks whether the commercial story is accurate, auditable, and defensible. Leadership asks whether last quarter’s number changed. A reconciliation record on every feed answers both, and the commercial pharma FAQ covers how that held up through three acquisitions.
So separate the systems. Put sample and safety records under validation. Run everything else on tested pipelines with version control and a record of each test result, the setup described on the commercial data platform page. Those tests catch the partial files and restatements that actually break commercial reporting, which validation paperwork never did.
Open Payments sits apart again. It’s a CMS program, and the company’s attestation is the control: 42 CFR 403.908(e) requires an officer to attest that the report is timely, accurate, and complete. That’s why testing the file against the reporting rules before you submit pays for itself. See how to validate Open Payments data before you submit.
Validation overhead on a dashboard makes every change slower and no number more accurate.