.png)
A GFI is a manufacturer's formal request to investigate a potential 340B compliance concern. They've flagged something in their data and they want answers. What that "something" is varies widely, and understanding what triggered the inquiry is the first step to resolving it.
A Good Faith Inquiry is a formal, manufacturer-initiated request asking a covered entity to confirm that a 340B transaction was handled correctly. Manufacturers are permitted under HRSA guidance to conduct these inquiries when they have a reasonable basis to suspect a compliance issue.
The key word is suspect. A GFI does not mean a violation has been confirmed. It means a manufacturer has identified a data pattern that, from their vantage point, needs clarification.
A GFI is a request for validation. It is not a finding of wrongdoing.
This is where most covered entities get surprised: GFIs aren't just about duplicate discounts. Manufacturers now have access to data from multiple sources like ESP, state Medicaid systems like Kentucky DMS, wholesaler purchase records, and their own internal sales data, and they cross-reference all of it. Any inconsistency across those systems can generate a flag.
The classic GFI trigger. A manufacturer cross-references their 340B-priced sales against Medicaid rebate invoices and finds what appears to be the same claim on both sides, purchased at a 340B discount and then rebated through Medicaid. This is prohibited under the 340B statute. That said, what looks like a duplicate discount is often a data alignment gap rather than an actual violation. A missing NPI, a participation form that didn't process correctly, a claims attribution delay in Kentucky DMS. All of these can produce a false positive that looks identical to a real duplicate discount from the manufacturer's side.
Manufacturers may flag a covered entity if purchasing patterns suggest 340B-priced drugs are being dispensed to patients who don't qualify. These include non-patients of the entity, patients outside the registered sites, or otherwise ineligible recipients. Inquiries like these often arise when purchase volumes are disproportionate to the covered entity's patient population or when dispensing data doesn't line up with eligibility records.
Several major manufacturers now require covered entities to submit claims-level data through the ESP platform as a condition of accessing 340B pricing at contract pharmacies. If your ESP submissions are incomplete, late, contain mismatched identifiers, or don't align with what the manufacturer sees in their own sales data, a GFI can follow. This is increasingly common as manufacturers expand their ESP requirements and tighten their data validation.
Manufacturers receive purchase data from wholesalers and track 340B account designations at the point of sale. If your wholesaler account designations are incorrect, if 340B purchases are being made under the wrong account, or if purchase volumes look inconsistent with your registered program, that can trigger an inquiry.
Sometimes it's none of the above. It is a mismatch between what the manufacturer sees from one data source and what they see from another. Conflicting information across ESP submissions, DMS records, and wholesaler data can raise enough questions that a manufacturer sends a GFI to sort it out.
The through-line in all of these: manufacturers are working from their own incomplete picture. They can see parts of the transaction, but not all of it. GFIs often exist because the data they have doesn't explain the data they're seeing.
For covered entities operating in Kentucky, DMS adds a specific layer to the GFI landscape worth understanding on its own.
Kentucky's Department for Medicaid Services requires covered entities to register contract pharmacies and submit claims data directly through the DMS system. When that data is accurate and up to date including, NPIs on file, participation forms processed, claims correctly attributed, DMS creates the documentation trail that protects covered entities from duplicate discount liability.
When that data has gaps, the protection breaks down. The manufacturer can't verify 340B status from their side, a Medicaid rebate request goes through without the corresponding 340B carve-out, and you have the conditions for a GFI.
The key principle for Kentucky covered entities: if you have submitted accurate data to DMS and maintained proper participation documentation, your obligation is fulfilled. You do not owe the manufacturer a payment or a direct reconciliation process. Your compliance obligation runs to the state system, not to the manufacturer. DMS is the mechanism that resolves this on your behalf, but only if your data is right.
The way a covered entity responds to a GFI matters as much as the substance of the response. Engaging without documentation, agreeing to manufacturer-defined reconciliation terms, or ignoring the inquiry entirely can each turn a solvable data problem into a real compliance exposure.
Manufacturer communications are technical and consequential. What you say, and what you don't say, can shape how the inquiry proceeds. Get expert support in place before any direct engagement.
Duplicate discount concern, diversion flag, ESP data gap, wholesaler anomaly: the response strategy depends entirely on what the manufacturer is actually questioning. Read the GFI carefully and understand exactly which claims, time periods, or data sources are in scope.
Depending on the trigger, you may need DMS submission records, ESP data, wholesaler account documentation, dispensing records, and patient eligibility files. The fuller your documentation, the faster the resolution.
GFIs cite specific NDCs, date ranges, or claim identifiers. Map those against your own records before drawing any conclusions about what happened or didn't happen.
Once the root cause is identified, fix it and document the correction. Whether it's an NPI update, an ESP resubmission, a DMS participation form correction, or a wholesaler account adjustment, prompt documented remediation is what closes GFIs cleanly.
We start by analyzing the inquiry to understand exactly what the manufacturer is seeing and what data source generated the flag. We then validate your submissions across every relevant system. We closely analyze DMS, ESP, wholesaler records and identify where the discrepancy lives. Once we know the root cause, we coordinate the correction and manage all communication with the manufacturer directly.
When direct manufacturer engagement is required, RxTrail steps in to own it. We confirm the data, provide the validation the manufacturer needs, and enable them to take action through the state system rather than against the covered entity. Throughout the process, you stay protected and informed. We manage the complexity.
The covered entity's job is to run a compliant program and keep their data current. Our job is to make sure that's enough to protect them when a manufacturer comes knocking.
Common Questions
Not necessarily. Many GFIs stem from data inconsistencies like , discrepancies between what different systems show, rather than actual violations. A GFI is a request for explanation, not a confirmed finding. That said, every GFI deserves a thorough response. Even administrative gaps create real exposure if they're not addressed.
It depends on what they find. If your documentation is in order and your data is accurate across DMS, ESP, and your wholesaler accounts, you don't owe the manufacturer a direct payment. Your obligation runs to the state system. Before agreeing to any manufacturer-requested financial reconciliation, talk to us. The terms manufacturers propose in GFI responses are not always what covered entities are actually obligated to accept.
A GFI is manufacturer-initiated and typically focused on a specific concern: duplicate discounts, diversion, data inconsistencies. A HRSA audit is government-initiated and covers broader program eligibility and compliance. Both require thorough documentation and a structured response, but they operate through different channels and have different implications.
Not automatically. ESP submission is increasingly a requirement for 340B pricing access at contract pharmacies, but submission alone isn't the same as clean, complete, matched data. Manufacturers validate ESP submissions against their own records, and gaps or mismatches in that data can still generate a GFI. Accurate, timely, well-matched ESP submissions reduce risk, they don't eliminate it.
We strongly advise against it without expert support in place. The framing of your response, the documentation you provide, and the commitments you make in that communication all have real compliance implications. This is exactly the kind of situation RxTrail is built to handle.
The longer a GFI sits unaddressed, the more complicated the resolution becomes. RxTrail handles every step, from identifying the trigger to closing the inquiry, so your program stays protected and your team stays focused on what matters.
