1099-LTC Policyholder and Insured Furnishing Workflow

Begin with the approved reporting record and the contract ownership history. The policyholder owns the contract; the insured is the person on whose behalf benefits are paid. Those roles can belong to one person or to two different people. The person receiving the payment can be a third party, such as a nursing home, without becoming the policyholder.

The IRS issuer instructions require reporting only where the policyholder is an individual. Within that reportable population, record both parties and preserve the source that establishes each identity. Do not infer ownership from a bank account receiving benefits or replace a policyholder with a caregiver who called customer service.

Keep an internal party key, mailing-address source and verification date for each role. The dispatch system needs the correct relationship, not merely a list of names copied from claims checks. Resolve inconsistent ownership data with policy administration before releasing statements.

The April 2025 continuous-use issuer instructions apply to 2025 and subsequent years until superseded. They specify Copy B for the policyholder and Copy C for the insured. When the policyholder is also the insured, Copy B satisfies the stated copy requirement and Copy C is optional. Apply that distinction to each approved reporting record.

This is a copy-selection rule. It does not mean that two different people living at the same address become one recipient, nor that identical names establish the same individual. Conversely, producing an optional Copy C for a person already receiving Copy B should not create another IRS information return.

Configure statement generation from the reviewed role relationship. Test a record with the same person in both roles and a record with different people. Include a policyholder who lives at a different address from the insured when that case exists in the population.

Use one row for each required statement instance, with the parent return reference, copy designation, intended person, approved address or electronic destination, output version and delivery method. Keep full taxpayer identifiers in restricted source records; the operations worksheet can reference those records by internal keys.

Before selecting electronic furnishing, verify that the method satisfies the applicable recipient-statement rules and any required consent. An email address in a claims system does not by itself establish consent to receive a tax statement electronically. Preserve the furnishing evidence associated with the method actually used.

The register should distinguish generated, released and delivery-exception work. These are internal tracking descriptions rather than IRS statuses. A printer finishing its batch does not establish that both parties were included, and an IRS filing acknowledgment does not establish that either statement was furnished.

Fictional 2026 example. Cedar Care Insurance has 80 approved reporting records. In 60 records, the same individual is policyholder and insured. In the remaining 20, the policyholder and insured are different people. The example assumes the population and any permitted contract aggregation have already been reviewed.

The control is 60 + (20 x 2) = 100 required statement instances. It is not a count of envelopes, unique people or IRS returns. If the vendor receives only 80 Copy B instructions, all 20 required Copy C statements are missing. Optional additional copies should have a separate count so they cannot conceal that omission.

Compare each generated copy with the approved reporting record, including the policyholder and insured identities, benefit amounts and applicable indicators. Confirm the copy designation and delivery destination. Where recipient TIN truncation is used, follow the issuer rules: it is permitted on payee statements, not on documents filed with the IRS, and the payer TIN cannot be truncated.

A returned envelope or failed electronic delivery should remain tied to the original statement instance. Investigate the destination through the established servicing process, then preserve the subsequent delivery action. Reprinting an unchanged statement does not mean the original information return was incorrect.

A confirmed identity or amount error follows a different path. Determine which reporting data changed, whether the agency return was already filed and which statement parties need corrected output. Regenerate from the approved correction data rather than typing a replacement amount into one recipient PDF.

Reconcile required Copy B and Copy C counts separately to the approved role matrix. Account for each omitted, held, released or repeated statement. Link delivery exceptions to their next action and preserve the actual evidence for completed furnishing. Avoid marking a record finished merely because the other party received a copy.

Keep the final output manifest with the approved reporting population and its version. If policy administration changes a party relationship after release, the original manifest remains evidence of what was sent, while the revised record explains the subsequent correction or replacement.

The download provides a role matrix, copy-count bridge and delivery-exception log. Together these records allow the insurer to answer a concrete question: for each reportable return, which statement was required for each party, what was produced and what action established furnishing?