AI Agents for Open Purchase Order Cleanup
The open purchase order list is a record of everything that was ever ordered and never formally finished. Most of it is noise, and the noise hides the accrual.
- Open purchase orders accumulate because closing one requires somebody to confirm nothing further is coming.
- Small residual balances from partial receipts and price rounding make up most of the line count and none of the value.
- Received not invoiced balances are where the accrual lives, and a cluttered list makes that balance impossible to trust.
- Commitment reporting is only useful when the list reflects real future spend rather than historical intent.
- ChatFin classifies every open order by evidence, proposes closures, and produces a commitment position with reasons attached.
Every purchasing system carries a list of open orders that nobody has looked at properly in years. Orders fully received but never closed, orders with a few units outstanding that will never arrive, orders for projects that finished.
The list matters for two reasons that people underestimate. It drives the received not invoiced accrual, and it is supposed to tell the business what it has already committed to spend.
This page covers why the list grows, what a stale list does to the accrual, and how a governed agent can classify the whole population and propose closures with evidence.
Why the list only grows
Opening a purchase order is a routine transaction. Closing one is a judgment: is anything else coming, will the supplier invoice the remainder, does the requester still need it.
Nobody is measured on closing orders, so the judgment never gets made and the line stays open indefinitely.
What a stale list does to the accrual
The received not invoiced position is calculated from this data. When the list contains orders that will never be invoiced, the accrual is overstated and the reversal shows up as a favourable variance later.
That variance then gets explained as good cost control, which is worse than being wrong, because it hides the underlying data problem behind a positive story.
Cleaning the list makes the accrual real and makes the following month's variance analysis honest, which is why this is a close problem and not just a procurement housekeeping task.
Receipts, invoices and intent
Open orders sit in the purchasing module, receipts in the warehouse system and invoices in payables. Whether an order is genuinely open is a judgment about all three plus whether anybody still wants the goods, which no report answers.
What the agent needs to see
Ledger detail from the ERP, plus open purchase order listings taken from the source they arrive in, read through the API surface your ERP already exposes rather than the database.
What it should be allowed to do
Prepare a closure proposal and a commitment schedule and leave it for the procurement controller to approve. Reading widely and writing narrowly is the line that keeps this safe.
That division matters more than which model sits underneath. An agent that can read open purchase order listings, receipt and invoice history and requisition records while posting only through the validated path a person uses gives you the coverage without handing over the ledger, and ChatFin works that way on every ERP it connects to.
What the agent classifies
The agent tests each open order against its receipt history, invoice history, age, requester and supplier activity, then assigns a status with a reason.
Most orders fall into obvious categories. The value of the exercise is that the small remaining set gets human attention instead of the whole list being ignored.
Classify by evidence
Fully received and invoiced, partially received and abandoned, awaiting delivery, or genuinely open.
Propose closures
Recommend closing orders with no realistic remaining activity, with the evidence for each.
Rebuild the accrual
Calculate received not invoiced from the orders that actually have goods received and no invoice.
Produce the commitment view
Report real future spend by category and requester, excluding the noise.
Commitment reporting that means something
Budget holders often see spend to date and not commitments, which is why budgets get overrun by orders placed weeks earlier.
Once the list reflects reality, a commitment view is genuinely useful: what has been ordered, what is expected to land in which period, and what remains uncommitted.
An accrual you can defend
Received not invoiced derived from real activity rather than from a list that never gets closed.
Visible commitments
Budget holders seeing what has been ordered as well as what has been spent, in time to act on it.
Closures are proposed in batches
Closing an order can affect a supplier relationship or a project commitment, so nothing closes automatically. Proposals arrive grouped by reason with the receipt and invoice history attached, which lets a reviewer approve in batches rather than one line at a time.
The record kept against open purchase orders is deliberately plain: the open purchase order listings the agent read, the reasoning it applied, the draft it produced, what the procurement controller changed, and the moment it posted. That is the trail an auditor asks for, and it is assembled while the work happens rather than reconstructed afterwards.
The wider argument for that design sits in what human in the loop really means and how to test a finance agent before you trust it.
A is prepared, reviewed and approved before it posts, and every step is logged from the source document to the entry. closure proposal and a commitment schedule
How ChatFin runs the cleanup
Every open order is classified by evidence into fully complete, abandoned, genuinely awaiting delivery or unclear, with the reason stated. The received not invoiced accrual is then rebuilt from real activity, which usually moves it and makes next month's variance explainable.
It connects to the ERP, the purchasing module and the receiving system through the interfaces those systems already expose, which keeps the security review short and the setup measured in days rather than quarters.
Classify by evidence
Receipt history, invoice history, age, requester and supplier activity tested per order.
Propose closures in groups
Orders with no realistic remaining activity batched by reason for approval.
Rebuild the accrual
Received not invoiced derived from orders with goods received and no invoice.
Report real commitments
Future spend by category and requester shown once the noise is removed.
A first run is usually read only against a period you have already closed, so you can compare what the agent found against what your team found before anything is trusted with a closure proposal and a commitment schedule.
Adding the workflow after this one costs no second integration, because NetSuite, SAP Business One, Acumatica and the other supported systems are already connected on the same terms.
Opening a purchase order is a transaction. Closing one is a judgment, so it never happens.
ChatFinFrequently Asked Questions
Can it close purchase orders automatically?
It proposes closures with the evidence behind each one and groups them so a reviewer can approve in batches. Closing is a procurement action that stays with a person, particularly where a supplier relationship is involved.
How does it tell an abandoned order from a slow one?
By looking at receipt history, supplier activity, requester status and age together. An order with partial receipt and no supplier activity for a year behaves differently from one on a long lead time, and the reason is stated on each proposal.
Does this change our accrual materially?
Frequently yes, and usually downward, because stale orders inflate received not invoiced. The important part is that the resulting number is derived from real activity, so the following month's variance is explainable.
Classify every open order and rebuild the commitment position.
ChatFin tests each open purchase order against its receipt and invoice history, proposes closures with evidence, and rebuilds the received not invoiced accrual from real activity.
What remains is a commitment view budget holders can use rather than a list everybody has learned to ignore.
Book a DemoSee your open order list classified with reasons.
Bring your open purchase order listing with receipt and invoice history. We will show the classification, the proposed closures, and the accrual rebuilt from real activity.