Prepare a Recipient List for TIN Matching

The IRS TIN Matching service validates name/TIN combinations before information returns are filed. It is available to eligible payers and their authorized agents through the program's application and access process. It is not a general public lookup tool for researching unrelated people.

Identify the payer, permitted user and recipient population before preparing the file. Keep an internal purpose statement, such as review of documented payees expected to receive covered information returns. Do not expand the list to unrelated vendor contacts simply because their names appear in a CRM.

Confirm whether the chosen provider accepts an interactive list, a bulk file or another documented interface. The input must follow that system's current specifications; a clean spreadsheet alone does not establish program eligibility or access.

The W-9 instructions distinguish line-1 identity from line-2 business or disregarded-entity names. Preserve both in the source even if the matching input uses a particular name field.

Store TINs as text in the working process so leading zeros are not lost. Check for missing values, accidental spaces, spreadsheet scientific notation and values pasted into the wrong column. Apply the receiving specification's formatting rules without altering the underlying identifier.

Look for duplicate recipient records using the documented name/TIN relationship and internal history. Two vendor IDs may represent one payee, while two similarly named businesses can be different taxpayers. Do not merge solely on a display name or shared address.

Retain a mapping from every submitted row back to its original vendor IDs. If duplicate inputs are consolidated, document the relationship so the result can be applied to the correct records. Sorting the input without preserving keys is an easy way to attach a valid result to the wrong payee.

Fictional example. A team prepares four vendor rows. No actual taxpayer identifiers are shown, and no live match is performed in this example.

The four source rows yield two unique ready combinations, one linked duplicate and one unresolved record. The control is 4 = 2 + 1 + 1. The source mapping records that input A supports both V-10 and V-11.

The missing record remains visible with a document request. It does not receive a made-up number, and it is not described as a successful match because it was excluded from the file. Any payment or withholding implications of missing information are routed separately.

If a name appears inconsistent, compare the supplied tax document, vendor master and planned input side by side. An invoice may use a DBA while the W-9 identifies an individual owner. That can be a documented relationship rather than a typo.

Ask the payee to clarify contradictions in line 1, classification and identifier. Do not cycle through unrelated names for one TIN. The IRS e-services procedures describe controls against researching identifiers using different names and provide distinct responses for invalid and duplicate requests.

Log an authorized formatting transformation separately from a substantive identity change. Removing unwanted surrounding spaces is a different event from replacing the owner with an entity. The next reviewer should be able to tell which occurred and why.

Save the final input version in the restricted workspace, together with its source mapping, record count and exceptions. Give it a batch reference. Keep the file actually submitted so the eventual result can be tied to the same data, even if the vendor master changes tomorrow.

Plan to reconcile every submitted combination to a result or an explicit unresolved state. Do not count a submitted batch as completed while its results remain unavailable. Keep unsupported or missing records in the follow-up population rather than dropping them from the report.

The downloadable preparation checklist uses internal keys and source references to avoid repeating full TINs in a general review sheet. It is a preparation aid, not an IRS file template. Follow the current receiving-system specification for the actual protected submission.