Request for Information (RFI): Glossary

Glossary definition of a Request for Information (RFI) in vendor contract and invoice auditing, covering when and how it is used and its limits versus a full.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Request for Information (RFI): Glossary

A request for information, or RFI, is a written ask sent to a vendor for the documents or data needed to check an invoice line against the underlying contract. It is a fact-finding step, not an accusation. AP and procurement teams use it before deciding whether a charge is a legitimate increase or a drift worth disputing.

1. When does a team send a request for information?

A team sends an RFI when an invoice line cannot be checked against the contract with the documents already on hand: an unlisted rate, a volume tier calculation with no visible total, a surcharge with no stated basis. The RFI asks the vendor to supply the missing document or number rather than assuming the charge is right or wrong. It is the step before a dispute, not a substitute for one.

Common triggers are a rate that does not match the last signed rate card, a fee code the contract does not define, or a volume tier calculation with no visible total behind it.

2. What does a well-formed RFI contain?

A well-formed RFI names the specific invoice, the specific line, and the specific document or figure requested: the current signed rate card, the amendment covering a rate change, or the delivery record supporting a charge. It states a response date. It does not ask the vendor to explain the whole bill, because a broad request produces a broad, unusable answer and stalls the review.

Attaching the invoice line and the contract clause in question, side by side, shortens the vendor's response time and narrows the reply to what was actually asked.

3. How does an RFI fit into a broader audit process?

An RFI resolves one open question on one invoice line. A contract compliance audit runs the same kind of check across every vendor and every category at once, using RFIs as one input where the contract file is incomplete. Relying on RFIs alone means drift outside the specific lines already flagged goes unchecked, because nobody asked about them.

Categories such as freight, contract labor, and MRO each carry their own recurring gaps in the contract file that an RFI process surfaces one at a time.

4. What happens after the vendor responds?

A vendor's response to an RFI either confirms the charge matches the contract, in which case the review closes, or it exposes a mismatch, in which case the team moves to a formal dispute and requests a credit. The RFI record, dated and specific, becomes the evidence behind that dispute rather than a separate step that gets discarded.

Keeping RFIs and their responses filed against the invoice they concern makes the next audit cycle faster, since the same rate question does not need re-asking.

For the wider pattern this sits inside, start with the margin drift guide. See also margin drift vs. legitimate price increases: how to tell them apart and accessorial charge audit: the surcharges nobody validates.

5. Frequently Asked Questions (People Also Ask)

What is a request for information in vendor auditing?

A request for information, or RFI, is a written ask sent to a vendor for documents or data needed to check an invoice against a contract, such as a current rate card or a delivery record. It does not commit either party to a change. It only gathers the facts a comparison needs.

How is an RFI different from a formal dispute?

An RFI asks for information. A dispute asserts that a specific charge is wrong and asks for a credit. Teams typically send the RFI first, because disputing a charge before confirming the underlying rate or scope risks disputing the wrong thing.

Who normally sends the RFI, AP or procurement?

Either can, depending on which team owns the vendor relationship. AP sends it when the question is about an invoice in front of them. Procurement sends it when the question concerns contract terms or a rate card it negotiated directly.

Does a vendor have to respond to an RFI?

Most service contracts do not set a legal deadline for an information request, unlike a formal audit clause, which sometimes does. A written RFI still creates a dated record showing when the question was raised, which matters if the item is disputed later.

Can an RFI alone catch margin drift?

An RFI supplies facts for one invoice or one vendor question at a time. Catching drift across a full vendor book means comparing every invoice to its contract systematically, which is what a contract compliance audit does using RFIs as one input among several.

What should an RFI ask for?

A specific document or figure tied to a specific invoice line: the current rate card, the signed amendment, a delivery receipt, or the volume total behind a tier calculation. A vague RFI asking a vendor to explain a bill produces a vague answer.

1. When does a team send a request for information?

A team sends an RFI when an invoice line cannot be checked against the contract with the documents already on hand: an unlisted rate, a volume tier calculation with no visible total, a surcharge with no stated basis. The RFI asks the vendor to supply the missing document or number rather than assuming the charge is right or wrong. It is the step before a dispute, not a substitute for one. Common triggers are a rate that does not match the last signed rate card, a fee code the contract does not define, or a [volume tier calculation](/glossary/volume-tier) with no visible total behind it.

2. What does a well-formed RFI contain?

A well-formed RFI names the specific invoice, the specific line, and the specific document or figure requested: the current signed rate card, the amendment covering a rate change, or the delivery record supporting a charge. It states a response date. It does not ask the vendor to explain the whole bill, because a broad request produces a broad, unusable answer and stalls the review. Attaching the invoice line and the contract clause in question, side by side, shortens the vendor's response time and narrows the reply to what was actually asked.

3. How does an RFI fit into a broader audit process?

An RFI resolves one open question on one invoice line. A contract compliance audit runs the same kind of check across every vendor and every category at once, using RFIs as one input where the contract file is incomplete. Relying on RFIs alone means drift outside the specific lines already flagged goes unchecked, because nobody asked about them. Categories such as freight, contract labor, and MRO each carry their own recurring gaps in the contract file that an RFI process surfaces one at a time.

4. What happens after the vendor responds?

A vendor's response to an RFI either confirms the charge matches the contract, in which case the review closes, or it exposes a mismatch, in which case the team moves to a formal dispute and requests a credit. The RFI record, dated and specific, becomes the evidence behind that dispute rather than a separate step that gets discarded. Keeping RFIs and their responses filed against the invoice they concern makes the next audit cycle faster, since the same rate question does not need re-asking. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide. See also [margin drift vs. legitimate price increases: how to tell them apart](/guides/margin-drift-vs-legitimate-price-increases-how-to-tell-them) and [accessorial charge audit: the surcharges nobody validates](/guides/accessorial-charge-audit-the-surcharges-nobody-validates).

Questions & Answers

What is a request for information in vendor auditing?

A request for information, or RFI, is a written ask sent to a vendor for documents or data needed to check an invoice against a contract, such as a current rate card or a delivery record. It does not commit either party to a change. It only gathers the facts a comparison needs.

How is an RFI different from a formal dispute?

An RFI asks for information. A dispute asserts that a specific charge is wrong and asks for a credit. Teams typically send the RFI first, because disputing a charge before confirming the underlying rate or scope risks disputing the wrong thing.

Who normally sends the RFI, AP or procurement?

Either can, depending on which team owns the vendor relationship. AP sends it when the question is about an invoice in front of them. Procurement sends it when the question concerns contract terms or a rate card it negotiated directly.

Does a vendor have to respond to an RFI?

Most service contracts do not set a legal deadline for an information request, unlike a formal audit clause, which sometimes does. A written RFI still creates a dated record showing when the question was raised, which matters if the item is disputed later.

Can an RFI alone catch margin drift?

An RFI supplies facts for one invoice or one vendor question at a time. Catching drift across a full vendor book means comparing every invoice to its contract systematically, which is what a contract compliance audit does using RFIs as one input among several.

Margin Drift Resources