TIN Mismatch Supplier Outreach Checklist

Compare the original match response with the submitted name, protected TIN reference and source-document version. Confirm that the result belongs to the correct supplier. A sorting or mapping error can attach another recipient's response to the row you are reviewing.

Check whether the issue is a genuine name/TIN mismatch, incomplete input, invalid formatting or a duplicate request. The supplier cannot fix a file-format problem created by your export. Correct local transformation errors before asking for new documentation.

When the submitted input matches the source but the result still needs follow-up, record the specific question. Examples include an unexplained owner/business-name relationship or a tax document that appears inconsistent with a later name-change notice.

A pre-filing TIN Matching response is distinct from a CP2100 or CP2100A notice. The IRS notice guidance and Publication 1281 describe what to do when a formal notice is received, including comparison with payer records and applicable B-notice procedures.

Do not send a generic request when a formal first or second B-notice procedure applies. Those processes can require different documentation and timing.

Identify your business, the supplier account reference and the information that needs confirmation. Explain that the name and taxpayer information used for reporting needs review. Ask for the applicable current tax documentation and any relevant name or ownership change.

Use the current W-9 instructions when W-9 is the appropriate documentation. Do not tell the supplier to change a number simply to satisfy your system. The correct relationship must come from its tax facts and documentation.

Keep full identifiers out of the subject and ordinary message body. Direct the supplier to the existing protected submission method. For electronic W-9 collection, the requester instructions describe requirements for the system and applicable certification, not just an upload button.

Fictional example. An accounts payable team confirms that a pre-filing mismatch belongs to supplier SUP-028. Its stored documentation and invoice display name appear inconsistent. No CP2100 or CP2100A notice has been received.

Subject: Tax documentation review for supplier account SUP-028

Hello, we are reviewing the tax information used for supplier account SUP-028 before information-return preparation. Please confirm the taxpayer name, business or disregarded-entity name, federal classification and applicable identifier on your current tax documentation. If your legal name or ownership changed, please include the relevant effective date.

Please use our established secure supplier-document process to provide the applicable updated form. Please do not send your full taxpayer identifier in a reply to this message. If you need help locating the secure process, contact our usual supplier-support team.

The message requests facts without claiming the supplier committed wrongdoing or that the IRS issued a formal notice. Its use does not excuse any separate duty triggered by other facts.

Confirm that the response came through the expected supplier relationship and that the document answers the question. Compare line-1 name, line-2 relationship, classification and identifier together. A fresh date on an otherwise contradictory form does not resolve the inconsistency.

Record the new document version, what changed and when the change applies. Keep the earlier version that supported prior reporting. If only your mapping was wrong, record a mapping repair instead of attributing a false identity change to the supplier.

Create a new match event from the reviewed source and link it to the earlier exception. Do not close the item merely because an attachment arrived. Record the actual later result or the remaining unresolved question.

Track the original event, issue type, request date, contact route, response, source update and next action. Use internal supplier keys in the working register and protect the underlying documents containing full identifiers.

If the supplier does not respond, route the case to the responsible reporting and withholding reviewer with the actual facts. Avoid automatically blocking or releasing payments based solely on a generic mismatch label. The applicable duties depend on the specific trigger, documentation and notices.

The downloadable template includes an ordinary message and a place to identify any formal-process referral. Keep those tracks visible so the person managing filing season can distinguish a completed documentation clarification from a formal notice case that still has required actions.