How to Print From UltraTax CS to SharePoint After Leaving GoFileRoom

Your firm moved from GoFileRoom to SharePoint, and the migration went fine. Then tax season came, and the frustration started to surface.

In GoFileRoom, a preparer printed from UltraTax CS and the return went straight to the client's file. In SharePoint, they print to PDF, save it, rename it, find the client folder, and drag it in. Nobody thought about that step before the migration. Now it happens on every return, and some land in the wrong year or on someone's own drive.

Can UltraTax CS print directly to SharePoint?

Not out of the box. But the filing step can be automated, and we've built it for a firm that made this same move.

What happens when the preparer prints

The preparer opens the return in UltraTax CS and prints it, the way they always have. UltraTax is set up to save every printed PDF to one holding folder by default. At this firm it's called UltraTaxPrint.

A bot takes it from there. It picks up the new file, works out which client and tax year it belongs to, and saves it in two places: the client's documents in Karbon, and the right client folder in SharePoint.

The bot never touches UltraTax CS itself. The only change inside UltraTax is where the PDF is saved, so nobody renames a file or goes looking for a folder. The 49-second demo below shows the whole loop, starting with Karbon and SharePoint before the print, when the return isn't there yet.

It took five pieces

The routing is the part staff see. It only works because of what sits underneath it.

1. One folder structure for every client. Same numbered subfolders everywhere, so a return has one home.
2. Metadata instead of file names. Fields for path, tax year, and file type.
3. Folders created by Power Automate. A new client in Karbon gets a SharePoint folder set automatically.
4. One-click sign-off. Review status lives on the document, not in an email.
5. UltraTax CS PDFs routed automatically. The printed return lands in the right client folder on its own.

That fifth piece actually depends on the first four. A file can't be routed automatically until every client has the same destination.

Karbon is the starting point for a reason. It already holds the firm's client list, so when the SharePoint folders are created from Karbon, the client record and the client folder come from the same source instead of two lists someone has to keep in step by hand.

What to settle before you automate it

The bot has to tell which client a PDF belongs to. That only works when each client in UltraTax CS matches a client in Karbon, so check the two lists against each other before go-live. A migration tends to surface the clients that don't match.

Then decide what happens to a file that matches nobody: where it waits, and who looks at it. A return that quietly lands in the wrong place is worse than one that waits for a person.

Last, agree on which print counts. A preparer prints a return more than once over its life (drafts for review, the client copy, the filing copy), and the client folder only needs the ones the firm keeps.

What changed for the firm?

The manual filing step is gone. Preparers print the return and move on, the same way they did in GoFileRoom.

Because the same file also lands in Karbon, the people working the client in Karbon see the return without asking where it went.

Is your firm in the same spot?

If your team has been filing returns by hand since the move, this might fit your setup. At Silver Sea, we build it on SharePoint and Power Automate and connect it to Karbon, so each return goes where your team expects to find it. See what else we connect on the UltraTax CS and Karbon pages.

If you're still planning the move, put printing on the list now. It's one of the process changes we cover in planning a GoFileRoom to SharePoint migration.

To talk through how your team files returns today, book a discovery call.