How to Import a Bank Statement
If an account does not have a live bank connection, or you need to bring in a period from before a connection existed, you can upload the statement file itself and URBI will read the transactions out...
Last updated
If an account does not have a live bank connection, or you need to bring in a period from before a connection existed, you can upload the statement file itself and URBI will read the transactions out of it.
Who can do this: Anyone with General Ledger edit access for the property.
Start an upload
- Go to Accounting > General Ledger > Banking.
- On the account you want to bring a statement in for, choose Import statement.
- Choose the file from your computer. CSV and PDF statement exports are both supported.
Confirm how URBI read the file
URBI works out where the transactions start, which columns are which, and how dates and amounts are written. Before anything is imported, you see exactly what it detected, so you can catch a misread before it becomes a wrong transaction:
Confirm how we read this statement
| Header row | Row 3 |
| Date format | MM/DD/YYYY |
| Amount columns | Separate Debit / Credit |
This card now shows what was actually read from your file, not placeholder text.
If anything here looks wrong, for example a date column read the wrong way round, open Adjust mapping, correct it, and use Re-run detection. The re-run now re-reads the file with your correction applied and updates this card to match, so what you see is genuinely what will be imported. If a column choice you make on this step (such as "single signed amount column" versus separate debit and credit columns) is not detected correctly on its own, your choice is the one that is used.
Review the lines
The review step lists every transaction URBI found. This reflects the actual file you uploaded, including any correction you made on the mapping step, so a line that looked wrong before you fixed the mapping now looks right here too.
- A line that is already on your feed is flagged as a duplicate so you do not import it twice.
- A statement with separate Debit and Credit columns is read correctly even when the unused column on a row is blank or filled with a placeholder like "0.00": the deposit is no longer recorded as a $0.00 line.
If something goes wrong partway through
Every recovery control on the result screen now does what its label says:
- Retry on a line that failed to commit actually retries it, and once a statement has committed successfully, the lines that failed the first time can still be committed, edited, or dropped rather than being stuck forever.
- Reverse on lines that committed in the wrong currency actually reverses them.
- Resume on an upload or review you left partway through actually reopens it. If there is only one account this could apply to, URBI opens it there directly.
- If a re-run is refused because someone already moved the statement forward, you now see a message saying so, instead of a button that looks broken.
A finished statement is read-only
Once a statement has been fully reconciled or locked, its review screen shows a Finished banner and every field is locked from editing. You can still open it to look, but there is no way to accidentally re-edit or re-commit something that has already been signed off.
Canceling an upload before it is committed
If you discard a statement before committing it, that is now recorded in your property's history, the same way a completed import already was.