K1 Aggregator Rollover: What Carries Forward, What Doesn’t, and How to Configure It

Rollover helps you start a new tax year by carrying forward select configuration and reference data from a prior-year Instance into a new-year Instance. This page is the authoritative reference for what rolls forward, what doesn’t, and which items are optional.

Need help configuring rollover or running it?

• To configure optional rollover items (Return ID, Comments, Notes, Estimates), see K1 Aggregator Rollover Settings.

• To run rollover and validate results, see How to Run Rollover to a New Tax Year Instance.

• If your organization uses Groups, review Group Management Feature to assign new-year Instances and users.

Note: This article explains rollover behavior and expected outcomes. It does not walk through the rollover workflow step-by-step.

---

Quick Start: Rollover in 3 Minutes

Use this quick guide if you need fast answers before running rollover.

1) What does rollover do?

Rollover carries forward selected Instance and Investment configuration from a prior-year Instance into a new-year Instance.

✅ Carries forward: investment reference data, tags, basis tracking configuration, activities, settings, and certain foreign forms/transferee setup (depending on configuration).
❌ Does not carry forward: uploaded K-1 PDFs, extracted values, annotated PDFs, exports, or reports.

2) What can I choose to roll forward (optional items)?

Some items only roll forward if they’re configured in the prior-year Instance:

• Return ID (Instance Dashboard → Update Instance)

• Investment Comments (Manage Investments → Investment Information panel)

• Investment Notes (Manage Investments → Manage Notes modal)

• Final K-1 issuer flag (“Issued a final K-1…”) (Manage Investments → General Information)

• Federal K-1 Total Amount → New Tax Year Estimate column (Settings → Rollover Settings)

3) Important: Group Management does not roll forward

Group Management is a tenant-level feature, but group-to-instance assignments do not automatically carry forward.

After rollover (or after creating a new-year Instance), admins must:

1. Open Tenant Group Management

2. Confirm users are in the correct groups

3. Assign the new-year Instance(s) to the correct group(s)

4. Confirm any required 7216 consent settings (if offshore access is needed)

4) What should I verify after rollover?

After rollover, confirm:

• Investments exist and look correct (name, tags, ownership, basis tracking, activities)

• Optional items appear only if configured (Return ID, Comments, Notes, Estimate column)

• New-year Instances are assigned to Groups (if Group Management is enabled)

• Your team can access the new-year Instance(s)

End Quick Start

---

How rollover works (Tenant → Instance → Investments)

K1 Aggregator is structured as:

✅ Tenant
→ ✅ Instance (tax-year workspace + settings)
→ ✅ Investments (records within an instance)

Rollover carries forward select configuration and reference data at the Instance and Investment levels. The tenant (parent) does not control rollover inclusion.

---

When to use this article

Use this article when you need to:

• confirm what rollover includes and excludes,

• understand optional vs default rollover items,

• know where rollover is managed (Instance + Investment levels),

• or understand how Group Management affects access to a new-year Instance.

---

What rollover carries forward (high-level)

Rollover carries forward configuration and reference data that supports year-over-year setup and continuity.

✅ Typically carries forward:

• Instance configuration and settings

• Investment reference data and metadata

• Tags and ownership structure

• Basis tracking configuration and activities

• Certain portfolio/foreign forms reference data (as configured)

---

What rollover does not carry forward

Rollover does not duplicate completed tax-year work product.

❌ Does not carry forward:

• uploaded K-1 PDFs or other source documents

• extracted K-1 values / line items

• annotated PDFs

• export files or report outputs

---

Optional rollover items (configured in the prior-year Instance)

Some data only rolls forward if it’s explicitly configured in the prior-year Instance before rollover runs. Common optional rollover items include:

• Return ID

• Investment Comments

• Investment Notes

• Final K-1 issuer flag (“Issued a final K-1…”)

• Federal K-1 Total Amount → New Tax Year Estimate column

For UI locations and setup steps, see K1 Aggregator Rollover Settings (Optional Items + Where to Configure Them).

---

Rollover Settings Detail Matrix

What carries forward matrix (Default vs Optional vs Never)

Tip: Use this table to verify expected rollover outcomes.

End Matrix

---

Group Management and rollover (Important)

Group Management is a tenant-level feature that controls which users can access which Instances. Even when Group Management is enabled, group configuration and group-to-instance assignments do not roll forward.

After rollover (or after creating a new-year Instance), administrators must:

1. open Tenant Group Management

2. confirm users are assigned to the correct groups

3. assign the new-year Instance(s) to the correct group(s)

4. confirm any required 7216 consent settings (if offshore access is needed)

For details, see K1 Aggregator Group Management Feature.

---

Post-rollover expectations (what “success” looks like)

After rollover, you should expect:

✅ A new-year Instance with:

• investment list present

• tags, ownership, basis tracking, and activities carried forward

• optional items present only when configured (Return ID, comments, notes, estimate column)

✅ If Group Management is enabled:

• the new-year Instance must be assigned to the correct group(s) before end users can access it

---

FAQ

Does rollover copy uploaded K-1 PDFs?

No. Uploaded documents do not roll forward into the new-year Instance.

Does rollover copy extracted values, annotated PDFs, or exports?

No. Extracted results and generated outputs do not roll forward.

Where do I configure optional rollover items?

Optional rollover items must be configured in the prior-year Instance. See K1 Aggregator Rollover Settings (Optional Items + Where to Configure Them).

Why can’t some users see the new-year Instance after rollover?

If Group Management is enabled, the new-year Instance must be assigned to the appropriate group(s), and users must be in those groups.

End FAQ