Resolving Orphans and Committing

Before an import can be posted to your books, everything in it needs to be either resolved or explicitly excluded. This article covers what "needs resolution" means, what happens if you try to commit with something unresolved, and what your options are if a commit does not go through cleanly.

What "needs resolution" means

An item, an account proposal, a vendor line, or a payer line, is considered unresolved (an "orphan") if it is still pending and has not been confirmed or excluded. URBI will not silently guess on any of these. Instead, it holds them so a person makes the call.

If you try to commit with unresolved items

If anything is still unresolved when you attempt to commit, URBI stops the commit and takes you back to the first Resolve step that has something outstanding, Accounts, Vendors, or Units, in that order. Fix or exclude the flagged items there, then continue back through the wizard to commit again.

Committing

Once every account, vendor, and payer is either confirmed or excluded, the Commit button becomes active. Click it to post the batch. This is the point where accounts, vendors, and billing accounts are actually created and journal entries are posted, nothing before this point changes your books.

If a commit does not complete

Occasionally a commit can be interrupted partway through. What you can do next depends on how far it got:

• If posting had not started yet, the batch can simply be discarded. Nothing was written, so discarding it leaves no trace behind, you can start over cleanly with a corrected file.
• If posting had already started, the batch cannot be discarded. Use Retry instead. Retry is safe to click, it picks up exactly where the batch left off and will not create duplicate entries.

Good to know

• Discarding a batch that has not started writing to your books is completely safe and leaves zero residue behind. This makes it easy to cancel a test import or start over after spotting a mistake early.
• Reversing a committed import voids the journal entries it posted, but any accounts, vendors, or billing accounts that automation created for that batch remain in place afterward. If you no longer need them, clean those up manually. See the "How to Reverse an Import" guide for the reversal steps themselves.
• This entire process is staff/board/PM facing. No notifications are sent to residents at any point, including when an import commits, fails, or is reversed.