A vendor invoice arrives with several details your team needs to get right: who sent it, which building it belongs to, how much is due, and when payment is expected. Reading those details into software can be repetitive work. Checking whether they are right is a different job.
AI invoice extraction reads information from an invoice and proposes values for the expense record. In UnitConnect AI, those values can include the vendor, amount, invoice number, dates, and property. The software can also separate the invoices contained in a scanned batch. A person reviews and confirms the proposed information before an expense is created.
That review step is the point of this guide. AI can help with data entry; your team still decides whether the invoice belongs in the books and whether anything needs clarification.
Start with the invoice, not just the extracted fields
Keep the source invoice open while reviewing the proposed information. A set of correctly read numbers can still describe the wrong building, an already-entered bill, or a document that is only a statement.
Before checking individual fields, make sure the document is complete and readable. Confirm that you are looking at the invoice itself, including any continuation pages needed to understand the total. If the scan contains multiple invoices, check that the pages for each one belong together.
UnitConnect's expenses inbox treats an incoming invoice as an item to resolve. It can become an expense, or be marked as a duplicate, not an invoice, or rejected with a reason. The objective is not to turn every uploaded document into an expense. It is to give each item the right outcome.
Check the vendor and the property together
A familiar vendor name is not enough to identify the correct expense record. One supplier may work at a retail center, an office building, and a mixed-use property in the same portfolio.
Compare the proposed vendor with the invoice's issuer. Then check the service location or building reference against the proposed property. Pay attention when the invoice is addressed to your management company but the work was performed at a specific asset.
For example, a utilities supplier may send two invoices with the same company name and similar totals. The account or service address is what distinguishes them. Confirming the vendor without confirming the property can put a real expense against the wrong building.
If a single invoice spans multiple properties, do not assume that reading a property name settles the allocation. Have the responsible team member establish the correct treatment before completing the entry.
Match the amount and dates to the source
Check the proposed amount against the amount your team actually needs to record. An invoice may display a subtotal, tax, previous balance, credit, and amount due. Those figures are not interchangeable.
Read the context around the total rather than approving the largest number on the page. If a credit or previous payment changes the balance, resolve the difference before confirmation. A statement showing several older invoices also needs a different review from a new, individual bill.
Next, distinguish the invoice date from the payment due date and the service period. They answer different questions: when the document was issued, when payment is expected, and when the service occurred. Check each proposed date against its label on the source document. If the invoice does not provide a clear due date, follow your team's established process instead of treating a guessed date as fact.
Review the invoice number and check for an existing entry
Compare the proposed invoice number character by character with the original. A missing prefix or a letter read as a number can make the same document harder to find later.
Then check whether the invoice has already been entered. A vendor may mail a paper copy and email the same invoice. A team member may also upload a second scan while following up on an earlier submission.
Use the invoice number alongside the vendor, property, amount, and date to investigate a possible duplicate. Do not assume that different filenames mean different bills. UnitConnect's inbox supports a duplicate outcome, but the existence of that outcome does not mean every duplicate is automatically identified for you.
Resolve uncertainty before you confirm
Consider a hypothetical office-building invoice for $1,240. The scan is legible, but the proposed record points to the neighboring retail property. The vendor and total are correct. The expense is still not ready to create.
The reviewer should correct the property, compare the invoice number with existing records, and verify the dates. If the service address is unclear, ask for clarification rather than confirming the record and hoping someone fixes it later.
When a document needs follow-up, give that work an owner in your team's process. If it is rejected, record the reason. If it is not an invoice, use that outcome. Keeping an unresolved item visible is more useful than converting uncertainty into an expense simply to empty the inbox.
Keep expense creation separate from payment approval
Confirming extracted fields answers a data-entry question: is this the expense record we intend to create? It does not, by itself, answer every question about whether the work was authorized, the service was completed, or the bill should be paid.
Your internal payment controls still apply. Depending on your process, a manager or bookkeeper may need to confirm scope, resolve a disputed charge, or obtain approval before payment. UnitConnect's inbox feeds the expense workflow; it is not a reason to skip those decisions.
Once an invoice is confirmed into an expense, UnitConnect retains the invoice attachment. The Documents hub helps your team search and preview supporting files later, instead of relying on the person who originally received the email.
Make the review routine easy to repeat
Use the same short sequence whenever a team member reviews an extracted invoice:
Confirm that the source document is a complete invoice.
Match the vendor and the property to the source.
Check the amount, invoice number, and dates.
Investigate any possible duplicate or unclear information.
Confirm the expense only when the entry is ready, then follow the separate payment-approval process.
This is a review routine, not a claim that software can eliminate every error. Its value is that the next reviewer knows what to check, and an exception has a clear place in the workflow.
Where UnitConnect AI fits
UnitConnect AI is an optional, separately priced invoice-reading add-on. It proposes information and can split a batch scan into individual invoices. The expenses inbox also works without the add-on, with your team entering fields manually.
With either approach, the core control stays the same: review the source, correct anything that is off, and confirm deliberately. Nothing becomes an expense through the AI extraction workflow until a person confirms it.
Want to see how scanned invoices move from intake to review? Schedule a UnitConnect demo and ask for a walkthrough of the expenses inbox and optional AI invoice-reading workflow using an example from your portfolio.
