Re-running Matching for a General Ledger Import
Use Re-run matching when an uncommitted batch needs to be read again using the current matching rules. This is the way to update a batch imported before the general ledger import improvements. Start...
Last updated
Use Re-run matching when an uncommitted batch needs to be read again using the current matching rules. This is the way to update a batch imported before the general ledger import improvements.
Start a re-run
- Find the uncommitted batch in Import History, or open the Commit step when it offers Re-run matching.
- Select Re-run matching.
- Read the Re-run matching? confirmation carefully.
- Select Go back to keep the current staged work, or select Re-run matching to proceed.
- Watch the progress panel while URBI re-reads the file and applies the current matching rules.
What a re-run clears and keeps
It clears the staged entries and lines, unit and member picks, vendor assignments, staged vendor creates, general income marks, historical balance marks, and plain marks.
It keeps the uploaded file, confirmed column mapping, detection overrides, cutover date, mode, entry-level exclusions, and the batch itself.
After the re-run, return to the first step that has unfinished work and complete the import again.
If something goes wrong
- If the re-run fails before staged work is cleared, the failure card tells you that the existing decisions are still there. Fix the issue and select Retry when offered.
- If it fails after the clear, review the failure card and select Retry. URBI uses the current version of the batch for the retry.
- A batch with posted entries must be reversed before it can be re-run. Reversed batches do not offer Re-run matching.
- If you only need to change column mapping, go back to Map columns and select Continue. On an already staged batch, the same confirmation explains what will be replaced.