How to Import a Spreadsheet (CSV or Excel) Trial Balance into UltraTax CS

Plenty of trial balances never touch a cloud ledger. The client runs QuickBooks Desktop, or Sage 50, or a write-up package, or the bookkeeper just keeps the year in Excel. Whatever the source, the balances land in a spreadsheet on your desk — and Thomson Reuters UltraTax CS has no native import for any of them, the same way it has no native import from QuickBooks Online or from Xero.

The good news: UltraTax can read a trial balance from a spreadsheet — if the spreadsheet is in the exact shape it expects. The bad news is that "the exact shape" is doing a lot of work in that sentence, and most exports don't arrive in it. This guide covers what UltraTax actually accepts, how to reshape a raw export into it, and the version that skips the reshaping entirely.

What UltraTax actually accepts from a spreadsheet

UltraTax CS reads a trial balance import as a set of columns it maps to its own fields:

  • Account number
  • Description
  • Unit (for returns with multiple activities/units)
  • Tax code
  • Amount

It examines and summarizes the balances, applies whole-dollar rounding, and transfers each amount to the correct input screen — but only according to the tax code you assign each account. Every other column is bookkeeping. The tax code column is the accounting, and it's the entire reason a spreadsheet import is more than a copy-paste.

Here's the part firms miss until it bites: the correct tax code depends on the entity type. UltraTax publishes a separate Tax Code Listing for each return — 1040/Schedule C, 1065, 1120, 1120-S — and the codes aren't interchangeable. The same "Officer Compensation" account maps to one line on an 1120-S and doesn't exist as a concept on a Schedule C. You commit to the entity first, then map. (We break down the entity-specific mappings in the QBO account-to-tax-code guide — the tax codes are identical no matter where the trial balance came from.)

Reshaping a raw export into an import file, step by step

1. Get the trial balance into a spreadsheet

From QuickBooks Desktop, run the Trial Balance report at year-end and export to Excel. Sage, Wave, and most write-up packages have the same report. If you're already working in Excel, you're a step ahead — but the reshaping below still applies.

2. Collapse debits and credits into one signed amount

Most trial balance exports arrive with separate debit and credit columns. UltraTax wants a single amount column with the sign carried in the number — debits positive, credits negative (or per your import's sign convention). Combine the two columns into one before anything else, because a two-column balance won't map to UltraTax's single amount field.

3. Delete every total and subtotal row

Export reports include a Total row, and often subtotals by section. UltraTax will try to read a "Total" line as an account, and a total with no tax code is the single most common reason an otherwise-clean import fails. Strip all total and subtotal rows so every remaining row is a real account.

4. Trim account numbers to 12 characters and keep them unique

The account-number field caps at 12 characters. Longer codes from a desktop chart of accounts get rejected or truncated — and if two accounts truncate to the same string, they collide into one. Shorten long account numbers and confirm each one is still unique.

5. Trim long descriptions

Import formats cap the description length (29 characters is a common limit), so "Officer compensation — health insurance" arrives clipped. It's cosmetic until two accounts truncate to the same label and you can't tell them apart on review.

6. Add the tax code column

This is the one column your export will never contain, and the one that matters. Add a tax code column and assign every account a code from the Tax Code Listing for the client's entity type.

Assigning tax codes without silent errors

A few mechanics decide whether the import lands clean:

  • Untagged accounts silently disappear. An account with no tax code isn't flagged as an error — it's simply excluded. A balance you forgot to map doesn't bounce back; it just isn't on the return, and the numbers are quietly off until review catches it.
  • Exclude on purpose with 88888 or 99999. For accounts you don't want imported — suspense, clearing, rounding accounts — assign 88888 (still prints on the Tax Code Groupings Report) or 99999 (doesn't print), rather than leaving them blank. The exclusion becomes intentional and visible instead of an accident.
  • Accounts sharing a tax code are summed. Map five expense accounts to one "Other deductions" code and they collapse into a single summed line. Usually what you want — but a mismapped account then hides inside a correct-looking total, so groupings are worth a second look before you file.
  • Whole-dollar rounding is automatic. UltraTax rounds on import, so don't pre-round or reconcile to the penny against the imported figures.

The limits that quietly break a spreadsheet import

None of these throw a loud error. They produce a return that imports successfully and is subtly wrong — the most expensive kind of mistake to catch on review.

  • Account number: 12 characters max.
  • Amount: 12 places max. A large balance sheet line can exceed it — check your biggest asset and liability figures.
  • Entity type has to match the return. A trial balance shaped for a partnership imports into a 1065 client, not an 1120. The entity you built the tax codes for and the UltraTax client's entity type must be the same, or balances flow to the wrong screens even when the codes look right.
  • Cash vs. accrual has to match how the return is filed, or the trial balance reconciles to nothing.
  • No duplicate account numbers. The account number is the key; two rows with the same number break the import.

The faster path: upload the spreadsheet, skip the reshaping

AccountantSync is the universal trial balance bridge to UltraTax CS, and direct spreadsheet/CSV upload is generally available alongside QuickBooks Online and Xero. For a client whose books aren't on a cloud ledger, the workflow is:

  1. Upload the CSV or Excel trial balance — no OAuth connection, no cloud account required.
  2. Set the entity type (Partnership, Sole Proprietor, S Corporation, or C Corporation) and the accounting method. That choice scopes every mapping to the right UltraTax Tax Code Listing.
  3. Auto-map the accounts. AccountantSync pre-fills the codes it's confident about and flags the handful that need your judgment — the same mapping logic behind the QBO and Xero workflows.
  4. Generate a UltraTax-ready import file. Signs, whole-dollar rounding, the 12-character account limit, description truncation, and grouping sums are handled to spec — so you're not hand-reshaping columns.

The part that compounds: your mappings persist year over year and copy between similar clients. The first spreadsheet client you set up takes a few minutes of review; every one after that — and every similar client — is close to a one-click export, instead of re-keying the trial balance every season. Each file maps to one UltraTax return. It's the same launch that brought Xero and spreadsheet upload online, aimed squarely at the clients who never left the desktop.

Frequently asked questions

Can UltraTax CS import a trial balance from Excel or CSV?

Yes, if the spreadsheet is in the layout UltraTax expects — columns it maps to account number, description, unit, tax code, and amount, with debits and credits collapsed into one signed amount column and every account assigned a tax code. UltraTax then summarizes the balances, rounds to whole dollars, and routes each amount by tax code. A tool like AccountantSync does the reshaping and mapping for you and exports the file.

What columns does UltraTax CS need in the import spreadsheet?

Account number, description, unit, tax code, and amount. The account number caps at 12 characters, the amount at 12 places, and any account without a tax code is excluded from the import. The tax code is the critical column — it's what tells UltraTax which form line each balance belongs on, and the correct code depends on the entity type.

Do I need QuickBooks Online or Xero to use AccountantSync?

No. Spreadsheet/CSV upload is generally available, so you can bring in a trial balance from QuickBooks Desktop, Sage, a write-up package, or a plain Excel file — no cloud ledger or OAuth connection required. You still connect QuickBooks Online or Xero directly if the client is on one of those.

How does AccountantSync handle the UltraTax import limits?

It builds the export to UltraTax's spec: single signed amount column, whole-dollar rounding, the 12-character account-number limit, description truncation, and grouping sums. You set the entity type once, review the flagged mappings, and export. Start free with your first two clients, no credit card required.