Use this step to confirm where each account from your file belongs in your property’s chart of accounts.
Resolve an account
- Open GL accounts in the import wizard.
- Review the source account, suggested target, and confidence label. Auto is a certain match, AI shows the suggested percentage, and Manual means it needs your decision.
URBI also makes one of four kinds of proposal for each account:
- Create: URBI found no good match in your chart of accounts, so it proposes a brand-new account with the name from your file, and suggests an account type based on the name and on whether the account behaves like a debit or a credit in your file. Check the suggested type before you continue.
- Recode: URBI found an existing account with the exact same name, and it is safe to adopt your file's account code as that account's new code. Select Accept to adopt the code, or Keep URBI code to keep the existing one.
- Map only: URBI found a likely match, but recoding was not safe, for example because the account already has posted activity or the code is used elsewhere. Your file's account links to the existing account without relabeling it, and the reason is shown on the card.
- Manual: URBI found more than one existing account with the same name, so it does not guess. You need to pick the right one yourself.
- Select Accept when the suggested account is right.
- Select Adjust when it is not right.
- In the adjustment panel, choose Rename or renumber to update the account’s name or number, or choose Map to a different account to use an existing account instead.
- Select Save changes. When all accounts are resolved, select Continue to Units.
Rename or renumber one account
- Select Adjust on the account.
- Select Rename or renumber.
- Enter the new account name, number, or both.
- Select Save changes.
If you decide not to use the edit, choose Use the file's values or Keep URBI's values as appropriate.
What you will see
The account stays identified as the same account even if you change its name or number. You can also select several rows and use the bulk Accept action, then select Clear selection when finished.
When a new account's code is already in use
If a new account in your file has a code that another account already uses, URBI flags the row in red as soon as the step opens, before you press Accept. The row carries a Code clash label and explains which account holds the code, for example Code 2210 is already used by "2210 · Accrued Liabilities". Choose a different code or map to that account. Accept is switched off on that row.
- A banner at the top says how many codes clash and has a Show me button that scrolls to the first one.
- The footer reads Resolve 1 code clash to continue (or Resolve 2 code clashes to continue), and Continue stays unavailable until none are left.
- Select Change code to pick a free code and Stage account, or Map to existing account to use the account that already has the code. The row, banner and footer clear together as soon as the code is free.
- With several rows selected, bulk Accept skips any clashing row and tells you how many it skipped.
- A row that maps to an account that has since been switched off or removed is flagged the same way.
1 account code clashes with your chart of accounts. Fix it before continuing. Show me
2210 · Accrued Utilities Code clash
Code 2210 is already used by "2210 · Accrued Liabilities". Choose a different code or map to that account.
Change code
Map to existing account
Accept
Resolve 1 code clash to continue
*A clashing row is red with Accept off, and the footer names what unblocks Continue.*
If something goes wrong
- If the new number is already in use, URBI flags the row as a code clash (see above) and blocks the save. Choose a free number or select Map to a different account.
- If the table cannot load, select Retry.
- If you have no remaining work, URBI shows All GL accounts resolved and offers Continue to Units.