Skip to content
  • There are no suggestions because the search field is empty.

How K – 1 Reader (Upload) Matches Investments Automatically

Understanding how the K-1 Aggregator matches incoming K-1 documents to existing investments can help you streamline your review process and avoid duplicate investments.

When you upload K-1s into K1 Aggregator, K-1 Reader automatically tries to attach each K-1 to the correct existing investment. This process is designed to reduce manual work while avoiding incorrect matches.

Because K-1s are issued by many different entities and systems, you typically can’t control the format or identifiers included on the K-1 itself. K-1 Reader works with the information available on the document and compares it to the investment records already in K1 Aggregator.

What happens during upload

For each uploaded K-1, K-1 Reader asks a simple question:

Does this K-1 clearly match one existing investment?

  • If one clear match is found, the K-1 is linked to that investment.

  • If no clear match is found, a new investment record is created.

  • If multiple investments look like valid matches, K-1 Reader may create a new investment rather than risk attaching the K-1 to the wrong one.

This behavior is intentional and helps protect data accuracy.

What information K-1 Reader uses

K-1 Reader compares identifiers on the K-1 (such as EINs, names, and partner information) to the identifiers saved on your existing investment records. It starts with the strongest identifiers and uses additional fields only when needed to narrow the match.

You don’t need to configure or manage this process during upload.

Common scenarios you may see

Multiple investments with the same EIN

In some cases, multiple K-1s with the same Partnership EIN are expected, such as spouse or multi-partner scenarios. When this happens, K-1 Reader uses additional identifiers to try to distinguish between investments.

If there isn’t enough information to confidently select one investment, creating a new investment is often the correct outcome.

For more detail, see:
Multiple K-1s with the Same EIN
https://support.k1x.io/multiple-k1s-with-the-same-ein

New investment created during upload

A new investment may be created when:

  • the K-1 includes a new or missing EIN,

  • identifiers on the K-1 differ from existing investments,

  • multiple investments share the same identifiers and can’t be reliably distinguished.

This does not necessarily indicate an error.

What to do after upload

After uploading K-1s, it’s a best practice to:

  • review any newly created investments,

  • confirm whether they are expected (for example, spouse K-1s),

  • investigate unexpected duplicates early.

Important: K1 Aggregator does not support merging investment records.

Want the exact matching rules?

This article provides a high-level overview of what happens during upload. For a detailed explanation of the field order, tie-breakers, and examples of how matches are determined, see:

K-1 Reader Matching Logic: How Uploads Map to Investments
https://support.k1x.io/k1-reader-matching-logic