Bots that sign in to UltraTax CS when your staff click, run the same reports a person would, and match every return to its client and work item in Karbon. Final returns go to a review list, and printed returns are filed in Karbon and SharePoint.
Returns live in UltraTax and the work lives in Karbon. Finding the gaps, and the clients that have closed, means someone comparing one list with the other.
See how we helpRejections sit in UltraTax's report. Each one still has to be traced to the client and the work in Karbon before anyone can act on it.
See how we helpEvery finished return is printed to PDF, renamed, and dragged to the right client folder by a person.
See how we helpWhen staff click, the bot signs in to UltraTax, exports the client status report a person would run by hand, and matches every return to its client and work item in Karbon. Matching is read-only. For final returns, Karbon is updated only after staff approve.
The bot exports UltraTax's rejected e-file report and matches each rejection to the client and work item in Karbon. Staff work from one list instead of tracing each return by hand.
UltraTax CS is desktop software. The only way in is the way a staff member gets in: through the screen.
A report lists everything that ever matched, not what changed today. The automation has to keep track of what it already handled, so nothing is acted on twice.
The bot exports the report, then has to parse the clients and returns out of the PDF before it can act on any of them.
The preparer prints from UltraTax as usual. UltraTax saves the PDF to a holding folder, and a bot files it where the firm expects to find it. It runs in production at a firm on Karbon.
Each row is what the bot takes from UltraTax on the left and what it does with it on the right. Matching only reads Karbon; final returns change it only after staff approve.
RPA extracts data
Bot performs actions
When staff click, the bot signs in to UltraTax, exports the report a person would run by hand, and matches every return to its client and work item in Karbon. Staff work from one list.
Final returns found by data mining go on a review list. Once staff approve, the client is inactivated in Karbon, its open work items close, and recurring work stops.
Each rejection on UltraTax's report is matched to its Karbon client and work item, with the reason, so staff see every rejection in one place. We can add writing the status back to the work item.
Watch a return printed from UltraTax get filed in Karbon (35 seconds)
No. UltraTax CS is desktop software with no API. The only way to automate it is through the screen, the way a staff member uses it. Our bots sign in, run the same reports a person would, and pass the results to other systems.
Yes, through a bot. It exports UltraTax's client status and rejected e-file reports and matches every return to its Karbon client and work item, so staff work from one list. Final returns go on a review list, and once staff approve, the client is inactivated in Karbon. Returns printed to a holding folder are filed to the client's documents in Karbon. Writing e-file status back to the work item can be added.
UltraTax reports are cumulative. They list everything that ever matched, not what changed today. The automation keeps its own record of what it has already handled and acts only on the difference, so running it twice has the same effect as running it once.
No. Print once to a holding folder and let the automation file it: to the client's documents in the practice management system, and to the client's SharePoint folder for that tax year.
It was built to run on-premises and does not expose an API. Data can still be extracted and landed in a cloud database. To show it inside another system, that system needs a door: a real integration, or at least a custom field to write into. The realistic pattern is extract-and-push, not a live link.
No. The data is the straightforward part. Retraining experienced preparers on a different package is the bigger lift. Proving the new package handles your returns is the other: a simple 1040 looks fine anywhere, and the differences appear on complex returns, such as a US person abroad with foreign accounts. Evaluate with your genuinely complex returns.
One call is enough to see whether a bot can take it, and what it would touch in your setup.