K1x Aggregator is not picking up CA differences from CA K-1s for CA residents.

Describe your idea. The more information you provide, the clearer picture of your idea we will have.

The K1x Aggregator is not correctly recognizing the differences in California (CA) data for CA K-1s filed on behalf of CA residents. Specifically, for CA Form 541, CA Form 568, and CA Form 100S, the Aggregator only captures data from column (e), California source amounts and credits. It does not account for data from column (d), Total amounts using California law. Combine columns (b) and (c). By defaulting to column (e), which is intended for non-residents, the tool creates challenges for CA residents trying to import information from their resident columns. This issue undermines the efficiency of importing data to Axcess via K1x. Additionally, would it be possible to enable importing both resident and non-resident columns for CA filings handled separately?

How will this idea help you and potentially others? Understanding how things are done today, where the pain is, and how the idea is beneficial puts us in your shoes.

The idea will help the efficiency and effectiveness of importing data to Axcess via K1x, especially for CA residents filing CA state returns. Or we will have to manually delete all CA input from column (e ) and re-enter all data from column (d) to Axcess.

Who will benefit from this idea? Whether it's specific roles of users, users of a specific product, or certain departments/markets, this helps us know who to talk to when we need more information.

Any returns filed for CA residents and CA non-residents will benefit from this idea.

How do you envision this idea being implemented at K1x? You're the expert and understanding how you see this working helps kickstart the idea.

To solve this problem, K1x Aggregator will need to be able to recognize the California states filing for CA residents and import CA forms column (d) for CA residents. [We might update this section for further idea discussion.]