Use this step to tell URBI which column in your file holds each part of the import, such as the entry date, account, debit, credit, person, and description.
Map the file
- In the import wizard, open Map columns.
- Review the detected columns and the sample value shown for each one.
- Use the Maps to choice beside a source column to choose its purpose. Set columns you do not need to Ignore.
- Make sure the mapping is complete. The count at the bottom tells you how many columns are mapped and ignored.
- Select Continue.
Reference, Period, Person and Description
- Reference: if your export has a column such as a check number, transfer ID or memo code, choose Reference for it. The value is saved onto the journal entry, so it shows beside the entry in your general ledger.
- Period: if your export has a column with the accounting period, usually a year and month such as 2024-03, choose Period for it. The Entry date column still decides when the entry posts. Period tells URBI which historical accounting period the entry reconciles into.
- Person and Description are two separate fields. Person names who the entry belongs to, such as a payer or vendor. Description carries the free-text memo from your file. Map each one on its own.
Reference and Period are both optional. If your file does not have them, the import works as normal.
Reading the structure tiles
For a sectioned Excel export, the step shows tiles that summarize what URBI found in your file:
- GL Accounts Detected is the number of accounts URBI found.
- With Activity is how many of those accounts have transaction lines.
- Nets to zero is how many of those accounts net to zero over the file. They are not skipped: they still import and post like every other account.
Use the tiles to check that the shape of the import matches what you expect before you continue.
A file with account names but no account codes
Every line must be tied to an account code. If your file has account names but no code column, URBI refuses it here: a warning reads This file has account names but no account codes, the footer shows Still need: Account code, and Continue stays unavailable. Map the column that holds each account's code to Account. If the file has no code column, add one in your spreadsheet and upload it again with Back. A file that gets its codes from section headers, such as a sectioned export, still passes.
If you choose the corrected file while this import is open, URBI asks whether to Keep my current import or Start over with this file. Start over with this file discards the current import and begins again with the new file; it works from this refused state.
This file has account names but no account codes.
Map the column that holds each account's code to Account. If the file has no code column, add one and upload it again with Back.
Still need: Account code
Back Continue
*Names without codes are refused on Map columns.*
What you will see
URBI shows its suggested matches, such as Exact or Fuzzy, alongside sample values. A complete mapping enables Continue. If required information is still missing, the screen explains what is still needed and keeps Continue unavailable.
If the opening balance falls in a closed period
On the review step, a warning can say that opening balances are dated in a closed period. Commit Import stays unavailable until you deal with it. Reopen the period named in the warning, then return to the review step and select Commit Import. You do not need to run the import again.
If you are correcting an earlier import
If the batch is already staged, selecting Continue opens Continue staging?. It warns that continuing re-reads the file and clears every decision made after Map columns.
- Select Go back to keep the existing staged work unchanged.
- Select Continue only when you want to replace the staged work using this mapping.
The uploaded file, column mapping, cutover date, mode, and batch stay in place. The later matching decisions are replaced.
If something goes wrong
- If staging fails, review the message and select Continue to try the same complete mapping again. There is no separate Retry button on this step.
- If reading the file never starts within three minutes of selecting Continue, URBI stops waiting and tells you nothing was imported and your ledger is unchanged. Select Continue to try again, or Back to choose a different file.
- If URBI cannot find the uploaded file when re-staging, it stops before clearing your current staged work. Upload the file again from Import History, or select Back to start a new import.
- If the batch changed while you were working, refresh the import and review the current mapping before continuing.