Accounts Missing After an UltraTax CS Trial Balance Import? Why It Happens (and How to Fix It)

You export a trial balance, map it, run the import into UltraTax CS, and it reports success. Then the balance sheet is off, or an expense line reads low, or the return simply won't tie to the workpapers. An account that was clearly in the source is nowhere in UltraTax — and nothing warned you.

This is the most frustrating class of UltraTax import problem, because a failed import is easy to catch and a silently incomplete one isn't. UltraTax CS doesn't reject a trial balance that's missing accounts; it imports what it can understand and quietly discards the rest. There are four specific reasons an account disappears. Each has a distinct symptom and a distinct fix.

First, understand what UltraTax actually does with an import

UltraTax CS doesn't import your chart of accounts. It examines the trial balance, groups every account by its tax code, sums the accounts that share a code, applies whole-dollar rounding, and transfers each total to the input screen the tax code points at. The account name, the account number, the debit/credit layout — none of that survives as-is. Only the tax-coded totals land in the return.

That design is why accounts go missing without an error. If UltraTax can't attach a balance to a tax code and a valid destination, it has nowhere to put the number, so it drops it. From UltraTax's point of view nothing failed — there was simply nothing importable there.

Here are the four reasons that happens.

1. The account has no tax code (the silent exclusion)

This is by far the most common cause. An account with no tax code isn't an error in UltraTax CS — it's excluded from the import entirely. You mapped 95 of your 100 accounts, five slipped through untagged, and those five are simply gone. No prompt, no highlight, no reconciliation warning.

Symptom: The return is off by the exact total of the accounts you forgot to code. Often it's the accounts that don't have an obvious home — a suspense account, a rounding account, an ask-my-accountant account, a new account added mid-year — because those are the ones you skip when you're mapping quickly.

Fix: Every account needs a tax code, including the ones you intend to leave off the return. If an account genuinely shouldn't hit the return, code it deliberately (see the exclusion codes below) rather than leaving it blank — a blank looks identical to an oversight on review. The reliable check is to reconcile the imported tax-code groupings back to the source trial balance total before you touch the return. If they don't tie to the penny, an account is missing.

2. Account numbers longer than 12 characters collide and drop

UltraTax CS limits the account number field to 12 characters. Longer numbers are truncated to their first 12. That's harmless on its own — until two accounts truncate to the same 12 characters and map to the same tax group. When that happens, UltraTax treats them as a duplicate and the second account doesn't import at all.

This bites firms whose source books use long, structured account codes — department-prefixed or location-prefixed numbering, for example, where the distinguishing digits sit past position 12.

Symptom: Two accounts that should both appear collapse to one, or one of a matched pair vanishes. The total for that tax group reads low by exactly one account's balance.

Fix: Make sure the meaningful part of each account number lives within the first 12 characters, or that any two accounts sharing a 12-character prefix don't also share a tax group. Renumbering in the source is the durable fix; trimming in the import file works for a one-off.

3. An exclusion code (88888 or 99999) was applied by accident

UltraTax and the CS write-up products use two reserved tax codes to deliberately keep an account out of the return: 88888 and 99999. Both exclude the account from importing. The only difference is reporting — an account coded 88888 still prints on the Tax Code Groupings report, while 99999 doesn't print at all.

These exist for good reasons — memo accounts, statistical accounts, an account you're reconciling but not filing. The problem is when one gets applied to an account that should be on the return, usually by copying a mapping from another client or reusing last year's template.

Symptom: A specific account is consistently absent across imports, even though it's coded. Because it is coded, it survives the "untagged accounts" check in reason #1 — which is what makes it hard to find.

Fix: Scan for 88888 and 99999 in your mappings and confirm every account carrying one genuinely belongs off the return. If you can't see an account on the Tax Code Groupings report at all, suspect a 99999.

4. The entity type doesn't match on both sides

Tax codes are entity-specific. The same "Interest Income" account maps to a different code and a different line on a 1065, an 1120-S, an 1120, and a Schedule C. If the trial balance was coded for one entity and the UltraTax client is set up as another, codes that are valid for the intended entity have no valid destination in the actual return — and those balances drop.

Symptom: Whole categories of accounts go missing or land on the wrong schedule, not just one or two lines. Separately-stated items are a common casualty — on an S-corp, interest and dividends belong on Schedule K, and if the map thinks it's a C-corp they end up somewhere else or nowhere.

Fix: Confirm the entity type agrees across the source mapping, the tax codes, and the UltraTax client before you import. If you prepare a mix of entity types, don't reuse one client's mapping on another without re-checking the entity — this is the single fastest way to import a plausible, wrong return.

The reconciliation habit that catches all four

Every one of these failures shares one tell: the imported totals don't tie back to the source trial balance. Before you start working the return, sum the tax-code groupings UltraTax imported and reconcile them to the trial balance total from QuickBooks Online or Xero. If they tie to the penny, nothing was dropped. If they don't, the difference is the missing account — and the size of the difference usually tells you which one.

That check takes a couple of minutes and it's the only thing standing between a silently incomplete import and a return you file wrong. This is the same reason mapping accounts to tax codes is the part of the workflow worth slowing down for — the formatting is forgiving, the tax coding is not.

Stop re-diagnosing this every season

These failures are all downstream of the same thing: a hand-built trial balance import, where the tax code on every account is your responsibility and a single blank or stale code silently drops a balance.

AccountantSync is built to remove that surface. It's the universal trial balance bridge to UltraTax CS — connect QuickBooks Online or Xero, or upload a spreadsheet, and it assigns a tax code to every account for the entity you select, so nothing imports untagged. It generates the UltraTax-ready file to spec — signs, whole-dollar rounding, description and account-number handling, and grouping sums — and your mappings persist year over year and copy between similar clients, so a code you fixed once stays fixed. Instead of re-keying and re-reconciling every trial balance, you map once and the import ties every time.

Frequently asked questions

Why did my UltraTax CS trial balance import succeed but leave out accounts?

UltraTax CS imports accounts by tax code and silently excludes anything it can't attach to a code and a valid destination. An account with no tax code, an account whose number truncates into a duplicate at 12 characters, an account coded with an exclusion code (88888 or 99999), or an account coded for the wrong entity type will all be dropped without an error message.

How do I find which account is missing from an UltraTax import?

Reconcile the imported tax-code groupings back to the source trial balance total. If they don't tie, the difference equals the missing account's balance. Then check, in order: is the account untagged, does its number collide at 12 characters, is it carrying an 88888 or 99999 exclusion code, and does its tax code match the client's entity type.

What do the 88888 and 99999 tax codes do in UltraTax CS?

Both exclude an account from the import. The difference is reporting: an account coded 88888 still prints on the Tax Code Groupings report, while 99999 keeps it off the report entirely. They're meant for memo and statistical accounts — but applied by accident, they silently drop an account that should be on the return.

Why does UltraTax cap account numbers at 12 characters?

The account number field in UltraTax CS holds 12 characters, and longer numbers are truncated. If two accounts truncate to the same 12 characters and share a tax group, UltraTax treats the second as a duplicate and doesn't import it. Keep the distinguishing part of each account number within the first 12 characters to avoid it.

Does AccountantSync prevent missing accounts?

AccountantSync assigns a tax code to every account for the entity you select, so no account imports untagged, and it generates the UltraTax-ready file to spec — handling signs, whole-dollar rounding, and account-number and description limits. Because mappings persist and reconcile against the source, the import ties to the trial balance instead of quietly dropping balances. Start free with your first two clients, no credit card required.