Import History: Troubleshooting

This page covers the messages and blocks you may run into during an import, what each one means, and how to clear it.

"Start an import" is disabled

What it means: This property already has a committed import that has not been reversed. URBI allows one active import per property so balances do not get doubled up.

Fix: Reverse the existing import first (see the "How to Reverse an Import" guide), then start a new one.

The file will not upload

What it means: The file is not a CSV or Excel (.xlsx) file, or it is too large (the limit is 50 MB).

Fix: Re-export the ledger from your accounting system as a .csv or .xlsx file. If the file is very large, narrow the date range of the export or split it.

Commit is blocked by held entries

What it means: One or more entries cannot be posted as-is. The review screen shows them as held, in two categories:

• Held, unbalanced: the entry's debits do not equal its credits.
• Held, closed-period conflict: the entry falls in a fiscal period that is already locked.

Fix: Open Fix Held Entries from the review screen and clear each one:

• For an unbalanced entry, click Fix to edit the lines until debits equal credits, or click Exclude to leave it out of the import.
• For a closed-period entry, click Acknowledge & exclude. URBI never re-opens a closed period during an import. If you need that entry posted, re-open the period manually first, then re-run the import.

Once every held entry is fixed or excluded, Commit Import becomes active.

Commit sends me back to an earlier step

What it means: URBI found an account, vendor, or unit match that is still unresolved, for example a proposal that was never confirmed, or a payer that was never assigned to a unit or member. Rather than fail the import, URBI takes you back to that Resolve step so you can finish it.

Fix: Resolve or exclude the flagged item on the step you land on, then continue forward through the wizard again to Commit Import. See the GL Upload Automation article for how these proposals are generated and how to exclude an item you cannot resolve.

"Trial balance only" on Core

What it means: You are on the Core plan, which supports a trial-balance import (opening balances per account) but not line-by-line transaction history. The Units and Vendors steps are hidden, and the wizard runs as 5 steps instead of 7.

Fix: This is expected on Core. Upgrade to Premium if you need full transaction-level history for the current fiscal year.

The import shows a "Failed" status

What it means: Something stopped the commit before any entries were posted, for example the property's plan was downgraded, or the user's permission to manage accounting settings was removed while the import was running. No partial data is posted in this case.

Fix: Open the batch to read the failure reason. You will also receive a "Import failed" email confirming nothing was posted. Resolve the underlying cause (restore the plan or the permission), then retry the import or discard it and start fresh.

Re-upload duplicate warning

What it means: The file you selected matches one from a previously committed batch (by content or by overlapping date range). This is a safeguard against importing the same history twice.

Fix: Cancel if it is a duplicate. If you genuinely intend to re-import (for example after reversing the earlier batch), you can proceed knowingly.