Accounts payable · Video & transcript
AI invoice investigation: what do you actually owe?
Billie follows an amendment and accepted-delivery evidence to explain a disputed invoice and a reviewed correction.
Full narration available
Article · Accounts payable
A practical review brief for project invoices, purchase orders, cost codes, receiving and approved budget changes.
Construction invoice review needs more than a supplier and an approval button. Link each charge to the project, cost code, order or authorized scope, acceptance evidence and responsible budget owner. Keep the project’s financial picture current without treating an invoice approval as proof that every budget condition is satisfied.
Start with the information the project team will need to explain the charge: project identifier, supplier, contract or order, cost code, billing period and relevant delivery or progress evidence. If an invoice spans projects or cost codes, preserve the line-level allocation and its basis.
Make missing context visible immediately. Sending an uncoded invoice through several approvers creates movement without resolving the issue. The person who knows where the work belongs should have a specific task, such as confirming the project or explaining an allocation, before the financial approval proceeds.
A budget expresses an approved plan. An order or subcontract can represent committed work. An invoice, credit and posting affect the actual transaction record according to the organization’s process. These views answer different questions and should not be collapsed into one reassuring green number.
An illustrative example: a project manager sees a $10,000 supplier invoice against a $50,000 order. That does not alone show whether the project is within budget. Previous invoices, open commitments, approved changes and the remaining scope may change the answer. Define which values the review uses and when each was last updated.
The project manager may confirm scope, progress or accepted quantities. Procurement may resolve order terms. AP may verify invoice identity, coding and prior credits. The budget owner decides within the company’s spending authority, while accounting controls the posting and period. One person may hold several roles in a small team; the responsibilities still need to be explicit.
For a non-PO invoice, define the permitted exception route rather than inventing an order after the event. A documented explanation and the appropriate approval can preserve the history of what actually happened.
A change order may affect scope, price, timing or the project budget. Link its approved version to the invoice review and show any unresolved change separately. A supplier’s request for additional payment should not be presented as an approved budget increase.
Partial delivery also needs a continuing record. Keep accepted work, invoiced work and the outstanding commitment visible. When a credit or allocation correction changes the accounting record, verify the effect in both the ledger and any connected project view rather than assuming that the handoff completed.
Use an anonymized project containing a split-coded invoice, partial delivery, unapproved change, non-PO charge and failed posting. Ask the vendor to show the owner, evidence, decision and resulting budget view for each case.
Proper’s AP films illustrate intake, exceptions and a supported invoice investigation. Project budgets, committed spend, cost-code mapping and change-order integrations need their own product proof. Treat this article as a workflow design brief, not a claim that every construction requirement is included in every Proper offering.
They can be related but represent different decisions. Define the authority required for the charge and for any change to the approved project budget.
Use actual project structures and anonymized examples covering split costs, changes, partial delivery, exceptions and acknowledged posting. Confirm the available project-system integration and refresh behavior.
Bring your records, exceptions and the decisions that matter to your team.