Mapping the Columns in a General Ledger File

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

1. In the import wizard, open Map columns.
2. Review the detected columns and the sample value shown for each one.
3. Use the Maps to choice beside a source column to choose its purpose. Set columns you do not need to Ignore.
4. Make sure the mapping is complete. The count at the bottom tells you how many columns are mapped and ignored.
5. Select Continue.

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 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.