Skip to Main Content
K1x Ideas
Status Ready to Plan
Categories K1 Aggregator
Created by Guest
Created on Dec 5, 2023

Map Out Matching Logic for Import into CCH Axcess

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

Map out matching logic for import into CCH Axcess to give clients the ability to test import


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.

It will give clients the ability to test import to catch errors in advance of performing the actual task.

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.

All K-1 Analyzer users who import into CCH Axcess

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.

K1x would itemize the matching logic and document required fields, possibly with collaboration from CCH.


  • Attach files
  • Guest
    Mar 7, 2024

    When importing into Axcess/GST, can the EIN be validated between the two systems before data is imported? This would avoid potentially importing data into the wrong locator/return.

    Plante - High

1 MERGED

Allow Control of What Gets Sent to CCH

Merged
For example, K1A defaults to nonpassive status while CCH Axcess defaults to passive for investments. Instead of having users design a workflow to accommodate the mismatch or manually update each investment status in K1A prior to import, please all...
almost 3 years ago in K1 Aggregator 0 Ready to Plan