Uploading a GL File
The first step of an import is bringing in your file. This step now accepts more file types and does more of the cleanup for you automatically. Supported file types CSV , as before. Excel (.xlsx) ,...
Last updated
The first step of an import is bringing in your file. This step now accepts more file types and does more of the cleanup for you automatically.
Supported file types
- CSV, as before.
- Excel (.xlsx), newly supported. You no longer need to convert an Excel export to CSV before uploading it.
Steps
- Go to Accounting Settings → Import History and click Start an import.
- Drag your file onto the upload area, or click browse files to choose it.
- URBI reads the file and runs its column and layout detection. For an Excel file, it also looks at the sheet structure to figure out where your data actually starts.
- Review the summary URBI shows you: which sheet it read (for Excel files), the header row it detected, the number of rows found, and any date-format conversions it made. If something looks off, use Adjust to correct it before continuing.
- Click Continue to Map Columns to move to the mapping preview.
What gets skipped automatically
Many ledger exports include rows that are not real transactions, such as report titles, section markers, and subtotal or total lines. URBI recognizes and skips these automatically so they do not show up as accounts, vendors, or payers later in the wizard. You do not need to strip these rows out of your file before uploading.
Good to know
- You do not have to reformat or clean your export before uploading. URBI's column detection and row-skipping handle the common cases in Yardi, Buildium, AppFolio, QuickBooks, and similar exports.
- If a detail about the parse looks wrong (wrong sheet, wrong header row, a date that did not convert correctly), fix it here before continuing. Getting the upload step right saves rework in the later Resolve steps.
Next: Reviewing Account Proposals.