• Solutions for Every Building, Every Stakeholder

    URBI is the first Building OS powered by HERO AI. Whether you manage properties, own them, or operate them day to day, URBI transforms complex, disconnected workflows into a single, intelligent platform that drives efficiency and builds stronger communities.

    Role Benefits

    • For Property ManagersStreamline operations and enhance tenant satisfaction with centralized management tools.
    • For Building OperatorsSimplify daily tasks and maintenance with intelligent automation and workflow management.
    • For OwnersMaximize ROI and property value with comprehensive oversight and analytics.
    • For Finance TeamsClose faster with double entry books, trust accounting, and reconciliation that runs nightly.
    • For BusinessesConnect with building communities and expand your service offerings.

    Building Benefits

    • Residential BuildingsSimplify living with one app for bookings, packages, payments, and community updates.
    • Commercial BuildingsStreamline operations, vendors, and compliance while giving tenants a frictionless experience.
    • Education BuildingsManage facilities, visitors, and compliance for safer, smarter, more connected campuses.
    • Senior LivingAnswer families around the clock, publish life enrichment once, and see every community on one screen.
  • One Platform. Smarter Buildings.

    URBI centralizes daily operations and adds AI intelligence to transform complexity into clarity.

    Products

    • URBI KoreThe central hub where managers, owners, and staff run building operations in one place.
    • URBI KonnectA marketplace that connects buildings with trusted vendors, services, and community events.
    • URBI AccountingAI consolidation, invoices and receipts processed by AI, books pre reconciled before month end. In Beta.
    • URBI AIOne intelligence across URBI. HERO answers your team's questions, Arthur answers your community's calls, texts, and emails 24/7.

    Features

    • Operations & Workflow
    • Amenities & Booking
    • Events & Ticketing
    • Communication & Community
    • Payments & Transactions
    • Data & Compliance
    • HERO AI Intelligence
    • IoT & Hardware Integration
    • Community Experience
    • Accounting (In Beta)
    View All
  • Customers
    • All ResourcesGuides, support, and customer stories in one place
    • Help CenterGuides and answers for every part of URBI
    • BlogWhy URBI works the way it does
    • ReleasesEvery update we ship, in plain language
    • System StatusHow every part of URBI is running right now
    • About UsLearn about our story and mission
    • MilestonesHow URBI got here and where it is going
    • CareersWe're HiringJoin our growing team
    • FAQStraight answers about URBI, HERO and Arthur
    • ContactGet in touch with us

Schedule a Demo

  1. Help Center
  2. /URBI Kore Accounting
  3. /General Ledger
  4. /Import Errors and What They Mean

Import Errors and What They Mean

Use this reference when a general ledger import has failed, refused an action, or is showing an outcome you did not expect. It answers, for every case, whether any money has posted and whether your...

Last updated November 10, 2026

URBI Kore Accounting
    • Accounting Settings: Overview
    • Accounting Settings: Troubleshooting
    • Cash Basis vs Accrual Basis in Financial Reports
    • Credit card processing fees in the GL
    • How to Configure the Fiscal Year
    • How to Set the Reporting Basis and Budget Rollover
    • Refund troubleshooting
    • Unallocated Cash and the Suspense Row
    • What a card refund costs your property
    • What is new in accounting: bills, reports, and budgets
    • Where to Find Your Budget
    • Archiving Budgets and the Archived Section
    • Budgets: Overview
    • Editing the budget grid
    • Explaining your budget numbers
    • How to Activate a Budget
    • How to Adjust Budget Amounts by Percentage
    • How to Create a Budget
    • How to Create Groups
    • How to Duplicate, Rename, Archive, or Delete a Budget
    • How to Edit or Resume a Budget
    • How to Enter Amounts: Split or Monthly
    • How to Make a New Budget When One Is Already Active
    • How to Read Budget Performance and Variance
    • How to Reallocate Budget Funds
    • How to Use Spreadsheet Shortcuts
    • Modelling budget scenarios
    • Review and export budget performance
    • Starting a budget from last year
    • The AI Assist Tab
    • The Full-Page Budget Editor
    • Troubleshooting: Saving a Budget
    • Understanding the Budget Hierarchy
    • Why Can't I Activate This Budget?
    • Amending a contract's amount
    • Automatic payment and bank details
    • Billing Residents to the Reserve Fund
    • Bypassing board voting on a VARIABLE contract
    • Charging Back an Expense: The New Recovery Model
    • Choosing a Fund on a Journal Entry or a Payment
    • Choosing a Fund on an Expense
    • Choosing the payment date when you mark something paid
    • Choosing which account the money moved through
    • Contract approval and how it expires
    • Creating a recurring contract
    • Direct Deposit payout questions
    • Direct Deposit payouts
    • Enter a tax rate as a percentage
    • Expense Actions Now Update Instantly
    • Expense and Invoice Void Reliability: Overview
    • Expense System, Troubleshooting
    • Expense System: Frequently Asked Questions
    • Expenses: Dates, Payment References, and Refunds
    • FAQ and troubleshooting
    • Find and use HERO Bills
    • Finding voided expenses
    • For board members
    • Funds: FAQ
    • How a Reserve Expense Posts
    • How to Approve Expenses
    • How to Confirm Expense Actions
    • How to Create a Journal Entry With the Assistant
    • How to Create an Expense
    • How to Create and Manage Reimbursements
    • How to filter Expenses: Bills, Reimbursements and Cheques
    • How to Forward a Receipt by Email
    • How to Record an Expense From a Receipt the Assistant Read
    • How to Require a Board Decision on an Expense
    • How to Review Journal Entry Details
    • How to Set Up a Receipt Email Address
    • How to Set Up the Approval Chain
    • How to Void Invoices
    • If a review rejects something that is already paid
    • Pay several bills at once by Direct Deposit payout
    • Paying an expense from any account
    • Paying instantly when you record a direct payment or quick expense
    • Paying several bills at once
    • Reading the Scheduled tab
    • Recording a Vendor Bill
    • Recurring contracts and board-decision tagging
    • Releasing a bill for payment
    • Renewing an expired contract
    • Reserve in Budgets and Reports
    • Reviewing a HERO-scanned receipt
    • Saving an expense as a template
    • Set up Direct Deposit payouts
    • Setting Up Reserve Spending
    • Tagging an expense to a board decision
    • Tax on an expense and the tax recoverable line
    • The Expense System: Overview
    • Track a Direct Deposit payout
    • Troubleshooting Email Receipts
    • Troubleshooting Expense and Invoice Voids
    • Troubleshooting Funds
    • Understanding recurring contracts
    • Using the Inbound Email Log
    • Voiding an expense
    • Weekly Reminder for Bills Waiting for Review
    • What a Fund Is
    • What approvers see: the commitment summary
    • What changed for bank matching rules
    • What the review step means now
    • AI Assist for Balancing Your Accounts
    • Amenity and Event GL Posting: FAQ
    • Amenity and Event Payments: Automatic GL Posting
    • Attribute Manual-GL Income to a Resident or Unit: Overview
    • Choosing Vendors and Marking Plain Ledger Lines
    • Claiming, releasing, or forfeiting a deposit
    • Closing an Accounting Period
    • Correcting a Journal Entry Keeps Linked Payments and Invoices in Sync
    • Deciding Who an Incoming Payment Is From
    • Delete a Draft Journal Entry
    • Deleting or Deactivating a Chart of Accounts Row: Overview
    • Deposit notices: who is told and when
    • Deposit payouts: how kept deposits reach your bank
    • Draft Journal Entry Deletion FAQ
    • FAQ: Deleting or Deactivating a GL Account
    • FAQ: GL Account Management
    • FAQ: GL Void & Locked-Period Policy
    • FAQ: Recurring Journal Entries
    • FAQ: Why did my payment look detached after correcting a GL entry?
    • Filtering the General Ledger
    • Following a Payment to Its Invoices
    • Former Payer Balances
    • General Ledger and Invoice Display: Overview
    • GL Account Management: Overview
    • GL Period Close: Frequently Asked Questions
    • GL Void & Locked-Period Policy: Overview
    • How a Manual Amenity Booking Posts to Your Books
    • How Deferred Deposits Post to Your Books
    • How deposit money moves: the accounting behind keep and return
    • How the Card Processing Fee Works in Amenity and Event Booking Accounting
    • How to Create a GL Account
    • How to Create a Recurring Journal Entry Schedule
    • How to Delete a Draft Journal Entry
    • How to Delete or Deactivate a GL Account
    • How to Edit a GL Account
    • How to filter General Ledger entries
    • How to Filter the Ledger with the Summary Cards
    • How to Fix an Entry in a Closed or Locked Period
    • How to Import Your Accounting History
    • How to Manage Account Groups
    • How to Reconcile and Close a Cash Account
    • How to Record an Income Journal Entry and Attribute It to a Unit or Member
    • How to Reopen a Closed Period or Account
    • How to Reverse an Import
    • How to Review Drafts and Use Run Now
    • How to Set a GL Account's Opening Balance
    • How to View an Amenity Booking's Invoice from the Booking Drawer
    • How to Void a Journal Entry (Open Period)
    • Import Errors and What They Mean
    • Import History: Bringing Your Existing General Ledger into URBI
    • Import History: Troubleshooting
    • Importing a Previous Fiscal Year
    • Managing Import History
    • Mapping the Columns in a General Ledger File
    • Re-running Matching for a General Ledger Import
    • Reading the Colours on Journal Entries
    • Recording a security deposit
    • Recurring Journal Entries: Overview
    • Renewing a lease
    • Resolving General Ledger Accounts
    • Reviewing and Committing a General Ledger Import
    • See the transactions behind a report or budget figure
    • Setting up a lease with a deposit and first rent
    • Troubleshooting accounting drill down
    • Troubleshooting Draft Journal Entry Deletion
    • Troubleshooting: GL Void & Locked-Period Policy
    • Troubleshooting: Recurring Journal Entries
    • Understanding the Suspense Account (1900)
    • What's Blocking My Period Close?
    • Account Credit - What It Is and Where It Comes From
    • Applying Account Credit to an Invoice
    • Bank debit problems and what they mean
    • Bank debit rows that are refused or need confirming
    • Changing the Account on a Draft Invoice
    • Charges in the Transaction Center
    • Charges: common questions
    • Choosing a billing day and End of month
    • Choosing How Tax Is Added to a Charge
    • Choosing properties and reading totals on accounting screens
    • Choosing Which Account an Invoice Posts To
    • Choosing Which Invoices a Payment Covers
    • Choosing your dates and launch settings
    • Combined payments, accounting and refunds
    • Condo Fee Billing Activation - Overview
    • Condo Fee Owner and Billing Defaults - FAQ
    • Condo Fee Owner and Billing Defaults - Overview
    • Declaring that you already hold signed agreements
    • FAQ: Invoice Debit Account
    • Filtering and Searching Transactions
    • Forwarded Invoices and Where Payments Land
    • Forwarded Invoices: Troubleshooting
    • Frequently asked questions
    • How bank debit agreements work in a bulk upload
    • How to assign or change a unit's primary billing account holder
    • How to create an invoice from a unit
    • How to edit a repeating charge
    • How to filter Collections
    • How to filter transactions with the search bar
    • How to Refund a Payment on an Invoice
    • How to set up condo fees with an Owner
    • How to stop or end a repeating charge
    • How to void or delete a charge on a unit
    • Invoice Debit Account: Overview
    • Matching units and choosing who pays
    • Preparing your bank details spreadsheet
    • Preparing your fee and lease spreadsheet
    • Primary Billing Account Holder, FAQ
    • Primary Billing Account Holder, Overview
    • Problems matching units and leases
    • Problems sending messages to residents
    • Problems with amounts, fees and dates
    • Problems with payers and email addresses
    • Problems with permissions and access
    • Problems with the file you uploaded
    • Reading Forwarded Splits on an Invoice
    • Reading the error report, row by row
    • Recording an Invoice That Was Already Paid
    • Refunding as Account Credit, and What Happens to the Card Fee
    • Resident combined payments, staff overview
    • Sending the messages to residents
    • Setting up condo fees: the three billing modes
    • Setting Up Tax Rates
    • Start here: uploading fees, leases and bank debit agreements
    • Tax on Recurring Charges - Overview
    • The staff declaration, and bank debit problems your residents report
    • The unit Accounting tab
    • Troubleshooting the unit Accounting tab
    • Understanding declined charges
    • Uploading fees, leases and bank debit agreements in bulk: overview
    • Uploading your fees and leases, step by step
    • What every status means, and what stops you committing
    • What exists after you commit, and what you can still change
    • What happens to condo fees on move-out
    • What Tax Looks Like on an Invoice
    • What you need before you start
    • What your residents and owners see
    • When something changed while you were working
    • Banking and Reconciliation: Overview
    • Cheque Alignment Guides, Overview
    • Cheque controls and the Cheques register
    • Cheque Printing: Overview
    • Collecting fees by pre-authorized debit
    • How to Add a Manual Bank Account
    • How to Add National Bank Numbers
    • How to Calibrate and Print a Cheque
    • How to Connect a Bank Account
    • How to filter bank lines on Bank reconciliation
    • How to find a cheque, and what to do when it is locked
    • How to Import a Bank Statement
    • How to Match Transactions
    • How to Reconcile a Statement
    • How to Set Up Cheque Alignment With the Guides
    • How to Set Up Reconciliation Rules
    • Match a Bank Withdrawal to a Bill You Have Already Paid
    • Printing a batch of cheques
    • Record Money That Arrived in Your Bank Account
    • Tie a Refund to a Bank Line
    • Troubleshooting: Banking and Reconciliation
    • Backfilling your fiscal year
    • Connecting QuickBooks Online to URBI
    • Disconnecting and reconnecting QuickBooks
    • Handling Drift: Using Re-push to Restore
    • How the QuickBooks Online Sync Works
    • Mapping your accounts to QuickBooks
    • QuickBooks Notifications You Will Receive
    • QuickBooks Period Reconciliation Checkpoints
    • QuickBooks Shortcuts and Where to Find Things
    • Reading QuickBooks Sync Status: The Sync Pill
    • Reconnecting a Broken QuickBooks Connection
    • Understanding QuickBooks Sync States and Errors: A Glossary
    • Understanding the post-connect wizard
    • Using the Sync Console and Retrying Failed Transactions
    • What Syncs to QuickBooks Online: Reference
    • When a QuickBooks Checkpoint Goes Stale (and How to Refresh It)
    • AI insights on your accounting reports
    • Ask and answer board questions
    • Budget, Cash Flow & Governance Reports
    • Build a board package
    • Build the agenda for a board meeting
    • Choose which columns a report shows
    • Core financial reports
    • Estoppel statements and combined accounts
    • Exporting Reports to PDF, Excel and CSV, and Generating Statements in Bulk
    • How to ask a question about a report
    • How to issue an estoppel statement for one or two accounts
    • How to read, check and regenerate insights
    • Leasing & occupancy reports
    • Payables & vendor reports
    • Read a board package and vote
    • Reading a statement and the Account Ledger
    • Receivables reports
    • Report figures corrected, September 2026
    • Review and share a board package
    • Run a board meeting in Meeting mode
    • Segment-specific reports (Condo / Commercial / Education)
    • The Reports page
    • Troubleshooting AI insights and Ask
    • Troubleshooting estoppel statements
    • Two new registry reports
    • Who can open accounting reports
    • Write and share the minutes
    • How the Expense Category Sets Itself
    • How to Add a Vendor
    • How to Archive a Vendor
    • How to Edit a Vendor
    • How to Find a Vendor
    • How to Invite a Vendor Contact to the Vendor Portal
    • How to Request Tax Info from a Vendor
    • How to Set a Vendor's Expense Category
    • Managing Vendors from Accounting
    • Merging duplicate vendor records
    • Troubleshooting Vendor Management
    • Vendor credits
    • Vendor Management: Frequently Asked Questions
    • Where Some Settings Cards Moved
    • Previewing What Is Owed
    • Settling a Departing Owner's Balance: Overview
    • Taking the Payment
    • The Household List and "Also Leaving"
    • Troubleshooting
    • What Happens to Bills After Settlement
    • Who Can Do This
All collections

On this page

  • Read this first: four rules that decide whether your books are safe
  • Part 1: Batch states that mean something went wrong
  • Failed
  • Reversed
  • Failed against Reversed, in one line each
  • Part 2: Per-entry outcomes
  • An entry that errored
  • An entry that was skipped
  • An entry you excluded
  • An entry blocked by a closed accounting period
  • Part 3: The partial commit, where some entries posted and some did not
  • Part 4: Refusals when re-running matching or continuing over a staged batch
  • Somebody else changed the batch since you opened it
  • Another staging run is already going
  • The import already has posted entries, so it must be reversed first
  • Entries still need a decision
  • Nothing was posted: an archived vendor, or a vendor still being created
  • Nothing was posted: an account code clash
  • You no longer have permission
  • Accounting is no longer enabled, or the plan no longer covers importing
  • The batch could not be found
  • Part 5: File problems
  • The uploaded file cannot be reached, downloaded, or read
  • Part 6: Setup problems
  • The Opening Balance Equity account could not be prepared
  • The file belongs to a different property
  • Part 7: Two situations that look alarming and are not
  • A re-run that failed before clearing anything
  • The Vendors step shows no vendors at all
  • Part 8: When to stop and get help instead of retrying
  • Related articles

Use this reference when a general ledger import has failed, refused an action, or is showing an outcome you did not expect. It answers, for every case, whether any money has posted and whether your books are safe right now. For everyday tasks (resuming, discarding, reversing) read managing-import-history.md instead.

Read this first: four rules that decide whether your books are safe

  1. Nothing posts until you commit. Uploading, mapping, staging, and re-running matching never touch the general ledger. Every failure in those stages leaves your books exactly as they were.
  2. A batch never reaches Committed while any entry is in error. If even one entry failed, the batch ends Failed, not Committed. There is no state where the badge says the import finished but some of it quietly did not.
  3. A refused action changes nothing. When URBI refuses to clear or re-stage a batch, it refuses before it writes anything. The batch is identical afterwards.
  4. Retry never posts anything twice. A retry reprocesses every entry that is still part of the import and has no live journal entry: an entry that already holds one is never posted again. An entry whose earlier journal entry was voided, whether by a failed reversal or by a person, counts as having no live entry, so retry posts it again rather than skipping it. To leave such an entry out on purpose, exclude it before you retry.

The single most reliable answer to "did money post" is the Journal entries posted figure on the failure card. It counts what is live in the general ledger.


Part 1: Batch states that mean something went wrong

Failed

What you will see. The batch shows the Failed badge in Import History. Opening it shows either the Commit failed card or the N of M entries did not post card, with a Journal entries posted count, a Failed at phase value, and an Error detail message.

What it means. The commit started and stopped before every entry was posted. It is a stopped import, not an undone one.

Has money posted? Read the Journal entries posted count.

  • If it reads 0: nothing posted. The card says so directly: No journal entries were posted, so your general ledger is unchanged. Your books are safe and untouched.
  • If it reads more than 0: that many journal entries are live in your general ledger and are real. The rest are not. Your books are correct as far as they go, but this import is incomplete, so your trial balance will not yet match your source file.

What to do next. Fix whatever the Error detail names (the cases below tell you what each one means), then select Retry import. If retrying does not get you there, select Reverse and reopen. It voids what posted and sends the import back to review with your file and decisions kept, so you can fix the problem and commit again.

How to avoid it next time. Most commit failures come from something that changed between staging and committing: accounting being turned off, a plan change, a permission change, or the uploaded file being removed. Committing shortly after you finish resolving avoids nearly all of them.

Reversed

What you will see. The batch shows the Reversed badge with a Reopen for editing action. A newly reversed import goes straight back to Resolving, so this badge appears only on imports that were reversed before that behavior began.

What it means. Somebody deliberately rolled this import back. That is a decision, not a failure.

Has money posted? It did, and then it was undone. Reversal journal entries were posted against the original ones, the originals were marked void, and any fiscal periods this import locked were re-opened. Your books are safe: they are back where they were before the import, with a full record of both the import and its reversal. The one exception is an entry matched in a bank reconciliation: it is kept posted on purpose, and the reversal summary lists it.

What to do next. Nothing, unless you still need the data in. If you do, select Reopen for editing. The import returns to Resolving with your file, rows and decisions kept. URBI refuses, and names the entries, if any of its entries are still posted (This import can't be reopened while 3 of its entries are still posted ... Void them in the General Ledger, then reopen.), and refuses if a newer import was committed after it.

How to avoid it next time. Reversal is often the right answer, so there is nothing to avoid. Where it is worth avoiding, resolving carefully at Review & Balance before committing is what does it.

Failed against Reversed, in one line each

  • Failed means the import tried to post and stopped. Whatever posted before it stopped is still live, and the import is still finishable with Retry.
  • Reversed means everything the import posted has been undone on purpose, with reversal entries recorded. Your file and decisions are kept, and Reopen for editing brings it back to Resolving.

Nothing was deleted in either case.


Part 2: Per-entry outcomes

Four different things can happen to a single entry. Only the first is a problem.

An entry that errored

What you will see. The entry is listed under Failed entries and their reason on the partial-failure card, with its entry number, description, date, and its own stored reason. The Entries in error tile counts them.

What it means. URBI tried to post this specific entry and could not.

Has money posted? Not for this entry. Its money is not in your general ledger. Other entries in the same batch may have posted; the counts on the card tell you exactly how many.

What to do next. Read the reason stored against the entry, correct the cause, then select Retry failed entries. Only the errored entries are reprocessed.

How to avoid it next time. These are usually data problems in one row of the source file. Resolving the flags at Review & Balance before committing catches most of them earlier.

An entry that was skipped

What you will see. The entry counts as skipped and does not appear in the work to resolve.

What it means. One of two things. Either the entry has a line in a currency other than the property's own currency, so URBI will not convert it and guess, or somebody skipped it during review.

Has money posted? No, and it never will as part of this import. This is not an error, and your books are safe. It is a deliberate omission.

What to do next. Usually nothing. A skipped entry needs no account, vendor, or unit resolution and never blocks Commit Import. If it genuinely belongs in your ledger, post it by hand as a journal entry, or correct the currency in the source file and import again.

How to avoid it next time. Where your file mixes currencies, split the foreign-currency activity out before uploading, so you decide the treatment rather than having the rows set aside.

An entry you excluded

What you will see. The entry is counted as excluded, for example N entries excluded (closed period) on the review summary. If you excluded it in error, Include again brings it back.

What it means. You told URBI to leave this entry out. Nothing else. Excluding removes the whole general ledger entry and all of its lines, and URBI warns that the import's totals will no longer match your file. Once the import is being posted or has been posted, Exclude is refused.

Has money posted? No, by your own instruction. Your books are safe.

What to do next. Nothing, unless you changed your mind, in which case select Include again before committing.

How to avoid it next time. Row-level Exclude now asks for confirmation before it applies, so a stray click no longer removes an entry silently.

An entry blocked by a closed accounting period

What you will see. The entry appears under Held entries with a lock icon and the label Existing closed - excluded. The gate above the list reads N rows land in an existing closed period. Exclude them to continue.

What it means. The entry is dated inside a fiscal period that is already closed. URBI will never re-open a closed period by itself, so it holds the entry rather than posting into your closed books.

Has money posted? No, and the commit will not even start while these are outstanding. Your closed periods are safe: that is the whole point of the block.

What to do next. Decide what the entry should be. If it belongs in the closed period, exclude it here and handle the period through your normal period-reopening process, deliberately. If it is simply misdated, correct the date in the source file and import again. To get past this screen, every held closed-period entry must be excluded.

How to avoid it next time. Set the cutover date so that pre-cutover activity folds into the opening balance rather than arriving as dated detail inside closed periods.

These four are not the same thing. Errored means URBI tried and failed. Skipped and excluded mean the entry was set aside, by rule or by you. Closed-period means URBI is protecting books you already closed. Only errored calls for a fix.


Part 3: The partial commit, where some entries posted and some did not

What you will see. A card headed N of M entries did not post, with two tiles (Journal entries posted and Entries in error), a list of the failed entries with their individual reasons, a What happened explanation, and two buttons: Retry failed entries and Reverse and reopen.

What it means. The commit ran, most of the file went in, and some entries did not.

Has money posted? Yes, some. The Journal entries posted count is live in your general ledger and is correct accounting. The entries listed as failed are not in the ledger at all. There is no half-posted entry: an entry is either fully posted with both sides, or not posted.

What to do next.

  1. Read the stored reason on each failed entry. They are frequently all the same cause.
  2. Fix the cause.
  3. Select Retry failed entries. It reprocesses only the failed ones and never re-posts an entry that already holds a journal entry.
  4. If retrying will not clear it, select Reverse and reopen. That voids everything this import posted, including the entries that succeeded, keeps your file and decisions, and sends the import back to review so you can fix the problem and commit again.

Why the batch stays Failed rather than Committed. This is deliberate and it protects you. Committed is URBI's statement that the whole file is in your ledger. If a batch with failed entries were marked Committed, the badge would be telling you your books are complete when they are not, and the difference would surface later as an unexplained variance. Leaving it Failed keeps the discrepancy visible and keeps both Retry and Reverse reachable. It is not a bug, and you do not need to force the badge to change.

How to avoid it next time. Clear every flag at Review & Balance first, and commit when nobody else is changing the property's accounting settings.


Part 4: Refusals when re-running matching or continuing over a staged batch

These all come from the same safety step: before URBI clears a staged batch, it checks that clearing it is safe. Every refusal here happens before anything is written. In every one of these cases, no money has posted as a result of your action, nothing has been cleared, and your batch is exactly as it was.

Somebody else changed the batch since you opened it

What you will see. The action is refused, and on the mapping step the screen tells you: This batch changed somewhere else and has been reloaded.

What it means. Another person, or another browser tab of yours, changed this batch after your screen loaded. URBI will not apply your instruction on top of a version you have not seen.

Has money posted? No. Nothing at all was written. Your books are safe and the batch is untouched.

What to do next. Let the screen reload, review the current state of the batch, and repeat the action if you still want it.

How to avoid it next time. Agree who is driving an import before it starts, and avoid keeping the same import open in two tabs.

Another staging run is already going

What you will see. The re-stage or re-run does not start, and the batch remains as it was.

What it means. A staging pass for this batch is already running. URBI allows one at a time.

Has money posted? No. Staging never posts. Your books are safe.

What to do next. Wait for the run in progress to finish, then look at the result before starting another. If it appears stuck, use the guidance at the end of this article.

How to avoid it next time. Give a re-run time to finish before pressing anything again. Double-pressing is the usual cause.

The import already has posted entries, so it must be reversed first

What you will see. The message, word for word: This batch already has posted entries and must be reversed first. The panel adds: Reverse the posted entries before re-running matching. There is no Retry on this one, because retrying cannot help.

What it means. Part of this import is already in your general ledger. Re-running matching throws away the staged work and rebuilds it, which would orphan the entries that already posted. URBI refuses rather than let that happen.

Has money posted? Yes, and that is precisely why you are seeing this message. What posted is still correct and still in the ledger. Nothing has been cleared, and your books are safe.

What to do next. Choose one:

  • Retry the import instead, if you simply want to finish it. Retry works on posted batches and never re-posts what is already live.
  • Reverse and reopen the batch if the matching decisions really do need redoing. It returns to Resolving with your file kept, and Re-run matching is available again.

How to avoid it next time. Re-run matching belongs before you commit, not after. If matching looks wrong, re-run it while the batch is still Draft, Resolving, or Ready.

Entries still need a decision

What you will see. Retry is refused. The message names how many, for example: 3 entries still need a decision before this import can be committed. Open the import, decide or exclude them, then retry.

What it means. One or more staged entries have not been resolved or excluded yet, so URBI will not post the batch while an unresolved line is still inside it.

Has money posted? No. This is checked before Retry does anything. Your books are safe and the batch is unchanged.

What to do next. Open the import, decide or exclude the entries the message counts, then select Retry again.

How to avoid it next time. Clear every flag at Review & Balance before a batch is left to sit as Failed, so a later retry never runs into leftover decisions.

Nothing was posted: an archived vendor, or a vendor still being created

What you will see. A message that starts with Nothing was posted. followed by the reason, with a button to go back to the Vendors step. The reason either names an archived vendor, or reads A vendor for this import is still being created. Try again in a moment.

What it means. An import never switches an archived vendor back on, so posting stops before anything is written. The second message means a vendor you asked URBI to create has not finished yet, and posting will not go ahead without it.

Has money posted? No. The check happens before anything is written. Your books are safe and the batch is unchanged.

What to do next. For an archived accounting vendor, go back to the Vendors step and pick another vendor, or restore the vendor in the Vendor Manager. For an archived service vendor, pick another vendor. For a vendor still being created, wait a moment and commit again.

How to avoid it next time. Pick active vendors linked to this property. The vendor list only shows those.

Nothing was posted: an account code clash

What you will see. A banner on the GL accounts step that begins We stopped the import before anything was posted, with a red Code clash row and Continue unavailable.

What it means. A new account in your file has a code that another account in your chart already uses. URBI checks this when the step opens and again at commit, and stops before writing anything. Earlier, a clash discovered at commit stopped the import partway with a message like Account code 2210 is already in use by another account.

Has money posted? No. The check happens before anything is written. Your books are safe and the batch is unchanged.

What to do next. Select Change code and pick a free code, or Map to existing account to use the account that holds the code, then commit again.

How to avoid it next time. Resolve every red row on the GL accounts step; Continue will not let you past one.

You no longer have permission

What you will see. The action is refused. On a commit the Error detail reads: You no longer have permission to post journal entries for this property.

What it means. Your permission to post journal entries for this property was removed or was never granted. URBI denies by default here: if there is no explicit permission, there is no access.

Has money posted? Not from this attempt, which stopped before doing anything. If the batch had already posted entries from an earlier attempt, those are still live and still correct. Your books are safe.

What to do next. Ask an administrator to restore your permission to post journal entries for this property, then repeat the action. If the import is time-sensitive, someone who still has the permission can complete it.

How to avoid it next time. Confirm your access before starting a large import, especially just after a staffing or role change.

Accounting is no longer enabled, or the plan no longer covers importing

What you will see. One of these, word for word, in the Error detail:

  • Accounting is no longer enabled for this property.
  • The property's accounting plan no longer permits history import.
  • Could not verify the property's accounting subscription.

What it means. In order: accounting was switched off for this property; the plan the property is on does not include history import; or URBI could not check the subscription at all, and refuses to proceed on an unverified answer rather than guessing.

Has money posted? Not from this attempt. These checks run before any posting in the run. Anything posted by an earlier attempt is unaffected and still correct. Your books are safe.

What to do next. For the first two, have the property's accounting settings or plan sorted out, then select Retry import. For the third, wait a few minutes and retry. If it repeats, get help rather than retrying in a loop.

How to avoid it next time. Check that accounting is enabled and the plan is right before you upload, not after you have resolved several hundred entries.

The batch could not be found

What you will see. The action is refused with Import batch not found.

What it means. The batch no longer exists, or it belongs to a different property from the one you have open. URBI returns the same answer either way, on purpose, so nothing is revealed about another property.

Has money posted? No. Nothing happened. Your books are safe.

What to do next. Reload Import History and check you are on the right property. If the batch was discarded by someone else, it is gone and you should start a fresh import.

How to avoid it next time. Work from Import History on the property you intend, rather than from an older link or bookmark.


Part 5: File problems

The file lives in URBI's storage from the moment you upload it. Re-staging and re-running both read it again, so a file that has gone missing surfaces later, not at upload.

The uploaded file cannot be reached, downloaded, or read

What you will see. One of these on the failure card, or as the reason under it:

  • Can't find the uploaded file. It may have been removed from storage. Nothing has been cleared, and your current staged work is untouched. Upload the file again from Import History, or press Back to start a new import.
  • A reason beginning could not access source file, could not download source file, or could not stat source file (the last two carry a technical code in brackets for support).

What it means. URBI went back for the file it stored at upload and could not get it: it is gone, or storage did not answer.

Has money posted? No. This happens during staging, which never touches the general ledger. Your books are safe, and in this case your existing staged decisions are safe too: the failure happens before anything is cleared, and the screen tells you so.

What to do next. Upload the file again from Import History, or select Back and start a new import. Do not redo your matching work first: it is still there.

How to avoid it next time. Keep the source file to hand until the import is committed, and finish an import reasonably close to when you uploaded it.


Part 6: Setup problems

The Opening Balance Equity account could not be prepared

What you will see. The Commit failed card with the Error detail: Could not ensure the Opening Balance Equity (3050) account.

What it means. Pre-cutover activity folds into a single opening-balance journal entry, and that entry needs the property's Opening Balance Equity GL account. URBI could not confirm the account, so it stopped rather than post opening balances against the wrong GL account.

Has money posted? Not from this attempt: the check runs before this attempt posts anything. If an earlier attempt posted entries, the Journal entries posted tile shows how many, and those are still live and correct. Your books are safe.

What to do next. Check the property's chart of accounts for its system Opening Balance Equity account, then select Retry import. If the account is missing or has been altered, get help before retrying: this one is about your chart of accounts, not about the file.

How to avoid it next time. Leave the system Opening Balance Equity GL account alone. Renaming or renumbering system accounts is what usually breaks this.

The file belongs to a different property

What you will see. The Commit failed card with the Error detail: Import source file path does not match this property.

What it means. The stored file for this batch is not filed under the property you are committing into. URBI refuses to post one property's ledger data into another property's books.

Has money posted? No. This check runs before any posting. Your books are safe, and so are the other property's.

What to do next. Do not retry, because retrying will refuse again. Start a fresh import on the correct property and upload the file there. If you believe the file really does belong to this property, get help: this is not something to work around.

How to avoid it next time. Confirm which property is selected before uploading, particularly when you are importing several properties in one sitting.


Part 7: Two situations that look alarming and are not

A re-run that failed before clearing anything

What you will see. The failure card headed Re-run matching did not finish, with the line: Nothing has been cleared. Your current staged work is untouched. A Retry button is offered.

What it means. The re-run stopped at the very first stage, usually because the stored file could not be read, before it removed any of your decisions.

Has money posted? No, and nothing was cleared either. Every unit pick, vendor assignment, and plain mark you made is still there. Your books and your work are both safe.

What to do next. Fix whatever the reason names, most often by re-uploading the file, then select Retry. Do not start again from scratch, and do not redo the matching: the screen is telling you it is all still there, and it is correct.

For comparison, when a re-run fails after the clear, the card says something different: The decisions this batch cleared to re-run are gone, and the new staging pass did not complete. The batch stays recoverable: nothing else was changed. That one does mean the matching decisions need redoing, but still no money moved, and still nothing else about the batch changed.

How to avoid it next time. Nothing to avoid. This is the safety design working, and the wording is there so you do not throw away good work.

The Vendors step shows no vendors at all

What you will see. The Vendors step reads No vendors on this batch, with the explanation that every candidate, including entries such as system markers and reverse bank interest, is a plain ledger line, and that the batch will commit with no vendor attached to any of these lines. A Continue to Review button is offered.

What it means. URBI looked at every outgoing name in the file and concluded that none of them is a vendor. They are bookkeeping markers, reversals, or payers, and payers belong on the Units step, not here.

Has money posted? Nothing has posted yet, and nothing is missing. Every line is still in the import and will still post. A line without a vendor is a perfectly normal ledger line.

What to do next. Select Continue to Review. An empty vendor list is a finished vendor list.

How to avoid it next time. Nothing to avoid. Not making a vendor out of a bookkeeping marker just to clear a list is the correct outcome, and it is why Post to GL only exists. See choosing-vendors-and-marking-plain-ledger-lines.md.


Part 8: When to stop and get help instead of retrying

Retry is safe. It never re-posts a journal entry that is already live, so pressing it again cannot double your books. It is still the wrong move in these cases:

  • The same error detail comes back twice in a row unchanged. Nothing about the batch changed between the attempts, so a third attempt will not change it either.
  • The error names your chart of accounts or your subscription (the Opening Balance Equity account, accounting being disabled, the plan not permitting import). These need somebody to change a setting, not another attempt.
  • The error says the file belongs to a different property. Retrying will refuse forever. That import needs to be started on the correct property.
  • The stored file cannot be found and re-uploading does not fix it.
  • A staging run has been in progress for a long time and nothing is moving. Do not stack more attempts on top of it.
  • The counts do not add up to you. If Journal entries posted does not match what you expect for the file, stop and have it looked at before reversing or retrying. Both actions are recoverable, but a clear picture first is cheaper than either.

When you ask for help, quote the batch reference from the row, the Failed at phase value, and the Error detail exactly as shown. Those three identify the run precisely.

Related articles

  • managing-import-history.md
  • re-running-matching.md
  • reviewing-and-committing-a-general-ledger-import.md
  • mapping-columns-in-a-general-ledger-file.md
  • choosing-vendors-and-marking-plain-ledger-lines.md
  • deciding-who-an-incoming-payment-is-from.md

Was this article helpful?

Related articles

URBI Kore Accounting

How to Import Your Accounting History

This guide walks through a full import from start to finish. The import runs as a step-by-step wizard of 7 steps. When your property can import a trial balance only, the wizard has 5 steps: the Units...

Read
URBI Kore Accounting

How to Reverse an Import

If you imported the wrong file, mapped something incorrectly, or need to redo an import, you can reverse it. Reversing voids every journal entry and invoice the import posted, keeps the originals in...

Read
URBI Kore Accounting

Import History: Bringing Your Existing General Ledger into URBI

What it is Import History lets you bring a property's existing general ledger (its accounting history) into URBI from a CSV or Excel (.xlsx) file you export from your old system. URBI reads the file,...

Read
URBI Kore Accounting

Import History: Troubleshooting

This page covers the messages and blocks you may run into during an import, what each one means, and how to clear it. "Start an import" is replaced with a permission message What it means: Starting...

Read
All URBI Kore Accounting articlesAsk the URBI team
URBI

URBI is the Building OS, founded in Calgary in 2023. One platform with HERO AI built in, running thousands of units for property managers, condo boards and owners.

Solutions

  • All Solutions
  • For Property Managers
  • For Building Operators
  • For Owners
  • For Finance Teams
  • For Businesses

Building Benefits

  • Residential Buildings
  • Commercial Buildings
  • Education Buildings
  • Senior Living

Products

  • All Products
  • URBI Kore
  • URBI Konnect
  • URBI AI
  • URBI Accounting (Beta)

Company

  • About URBI
  • About Us
  • Milestones
  • Reviews
  • FAQ
  • CareersWe're Hiring
  • Contact

Resources

  • All Resources
  • Help Center
  • Blog
  • Releases
  • System Status
  • FAQ
  • For AI assistants

Compare

  • Compare Us to Residential
  • Compare Us to Commercial
  • Compare Us to K-12

Legal

  • Security & Privacy
  • Terms & Conditions
  • Terms of Service for Konnect

© 2026 URBI. All rights reserved.

Privacy PolicyTerms of Service

Schedule a Demo