Skip to article content
Insurance & health

2026 transactions; filing rules reviewed October 7, 2026. Historical examples explicitly identified.

Two Long-Term Care Contracts Pay on Different Bases: Separate the 1099-LTC Records

Two long-term care contracts covering the same person should not automatically become one Form 1099-LTC. The IRS permits certain aggregation only when the reportable information is identical apart from the amounts of benefits paid.

Published 3 min read

Source review: · Updated

Filing guide
In this guide

Two long-term care contracts covering the same person should not automatically become one Form 1099-LTC. The IRS permits certain aggregation only when the reportable information is identical apart from the amounts of benefits paid.

The case: fixed daily benefits and expense reimbursement

Hypothetical example: An insurer has two contracts for the same individual policyholder, who is also the insured. During 2026, Contract A pays $18,000 on a fixed daily basis without regard to actual expenses. Contract B pays $12,000 reimbursing actual qualifying expenses. Assume both are reportable long-term care benefits rather than accelerated death benefits.

The insurer prepares separate reporting records because the payment basis differs. The first record reports the $18,000 with the per-diem basis; the second reports the $12,000 with the reimbursed basis. Combining $30,000 under a single basis would misdescribe part of the benefits.

One person, one insurer and one reporting year do not satisfy the aggregation condition when another reportable attribute differs.

Define the basis from the actual contract

The IRS uses per-diem or other periodic basis for payments made without regard to actual expenses. Reimbursed basis means payments for expenses actually incurred.

Payment frequency is not the test. A monthly deposit can contain either type. A claim-system label such as “monthly benefit” therefore needs a connection to the policy terms and benefit calculation.

In the example, Contract A's amount may be calculated using covered days, while Contract B requires an expense claim. Keep those source records distinct even if both payments are sent to the same bank account.

Test all reportable attributes before aggregation

The form instructions allow reporting benefits from each contract separately. If the insurer wants to aggregate eligible contracts, the review must compare the information that would be reported, not merely match the policyholder's TIN.

Check policyholder and insured identities, benefit type, payment basis and other reportable form information. Where the records differ, retain the separate reporting treatment required by those facts.

A useful data control groups candidates only after those attributes are approved. Starting with one annual amount per person and trying to reconstruct contract differences afterward is more error-prone.

Preserve account and contract traceability

Separate forms should remain traceable to their source contracts and approved benefit totals. Follow the applicable account-number requirement where multiple accounts produce multiple forms.

An internal policy number can help the claims team answer questions, but do not expose unnecessary sensitive contract details in an unrestricted review file. Keep the approved mapping available to authorized staff.

Reconcile both records to the insurer's $30,000 aggregate benefits in the example. That aggregate is a useful control total even though it is not the amount to place under one payment-basis indicator.

Do not calculate the recipient's taxable amount

The payer reports the required gross benefits and related facts. It is not required to determine whether those benefits are taxable or nontaxable.

Per-diem and reimbursement benefits can have different significance for the recipient's tax analysis, which makes accurate separation valuable. Do not use a recipient's estimated exclusion to reduce the reported benefit amount or choose a basis.

If a recipient asks why two statements arrived, explain the two contracts and different payment bases. Investigate a factual error, but do not merge accurate records solely because the recipient prefers one statement.

The final check should prove three things: each contract's basis is supported, each amount reconciles to claims payments, and the two-form result preserves rather than duplicates the $30,000 total.

Prepare the reviewed contract records in E-File Magic's Form 1099-LTC workflow, then preview the copies against your aggregation analysis before release. Preserve contract and account references so different payment bases remain understandable. The filing workspace helps organize the separate statements; it does not determine the recipient's final taxable amount.

PUT YOUR GUIDE INTO PRACTICE

Put your filing plan into practice.

Start with your reviewed records, or contact our team to confirm the services your filing needs.

The official reference

IRS instructions for this guide

Preview here, or save a copy for later.

Tax year 2026
1 PDF for tax year 2026.

Instructions for Form 1099-LTC

April 2025 editionPDF · 137 KBContinuous use

Browse the instruction library

Need another form or year? Explore the full library. Edition dates reflect the IRS publication and may differ from the tax year.

Sources & further reading

Official references used in this guide. Check the applicable form revision and current instructions for your filing year.

  1. IRS instructions: 1099LTC
All articles