Independent IFS Cloud practice · Procurement
The purchase order you received, and the line that never closed
The goods arrived, the receipt matched, and every quantity on the line is accounted for. The order line stays open, because closing it was a separate action that nobody took. Depending on your setup, nothing closes it automatically, so it remains on the open purchase order list, keeps a met commitment on open-order reports, and makes the period harder to close.
Key takeaways
- A purchase order line received in full can stay in an open or received state instead of closed. The quantity is right, so nothing looks wrong, yet the line keeps reporting as outstanding work.
- A line left open after a short receipt still expects a remainder. Here the received quantity equals the ordered quantity, nothing more is coming, and the line is ready to close.
- No extra quantity came in, unlike an over-receipt. The status lags the receipt, and the lag is the finding.
- A monitor cannot know why a line was left open, for example a final invoice or a price check still pending, so it lists candidates for the buyer to review. The SCM Automation Pack runs no such rule today; it would be an additional rule built to order.
- The ordered quantity, the received quantity and the line state are recorded in IFS Cloud (worth confirming the exact projections in your environment), so a read-only monitor can list lines received in full that are still open and hand them back for closing.
1.How a finished order stays open
Receiving and closing are two steps. A receipt records that the goods came in against the line. Closing the line, or the order, tells IFS Cloud that no more activity is expected and the commitment can be retired. The first step happens because the warehouse needs the stock. The second depends on someone, or on a setting such as automatic closing after the final invoice (worth checking in your environment), going back to the order and finishing it.
Where nothing forces the close, a line received to the full ordered quantity can stay in a received state, waiting on a final invoice, a price check, or a habit that never formed. Weeks later it is still there, indistinguishable at a glance from a line that has work left to do.
The open status is a true record of a step that was never taken, listed next to lines where the same step still matters, with nothing marking which is which.
2.Which open lines are finished
An open purchase order line is normal while goods are still due. The review separates a line that is still working from one that is finished and only looks busy.
| What you see | What it can point to |
|---|---|
| Received quantity equals ordered quantity, line still open | A finished line that was never closed: on reports that count open lines rather than open quantity it inflates commitment, and it clutters every open-PO report. |
| Line fully received and fully invoiced, still not closed | Nothing left to do at all, yet the order stays open and blocks a clean period close. |
| Order header open while every line is received in full | The whole order is done and only the final close is missing, so it lingers as apparent work in progress. |
| Received line open for far longer than your normal close cadence | An age signal: the longer a fully received line stays open, the less a final invoice or check explains it. |
When the goods are in and the supplier is paid, the only thing keeping the order alive is its status, and on reports that count open lines it distorts the commitment at month-end. A buyer scanning the open list line by line cannot easily tell it apart from outstanding orders. Comparing received with ordered across every open line lists the finished ones.
3.Finding finished lines that are still open
The ordered quantity, the received quantity and the line state are recorded in IFS Cloud and can be read through OData projections without touching a record (the exact projections are worth confirming in your environment). Detection runs on a schedule, with the first scan after you have set the close cadence, compares the two quantities against the status, and looks at two things:
- Received equals ordered, still open - where a line has taken in everything it was meant to and is not yet closed, so lines with no work left are listed before they pile up on a report.
- Age past the close cadence - how long a fully received line has stayed open against your normal closing rhythm, so a line that missed its close is separated from one shut on schedule.
Because it is a read-only monitoring pattern, it runs beside purchasing and writes nothing back to IFS. It adds no object inside the client system, so a release update leaves nothing of ours in your IFS to retest. Before each release I check that the standard projections it reads still match, as part of the subscription. It gives the buyer a list of orders that are finished but still open, and the decision to close, hold for an invoice, or investigate stays with the person who owns the order.
4.Rolling it out without noise
- Time it to the close - the pain lands at period end, so run the check before month-end when finished-but-open lines distort commitment.
- Dry-run first - in the first week the rule only logs which lines it would have listed, and nothing reaches a buyer.
- Exclude pending invoices - hold back lines that wait on a final invoice for a period you set, so only lines past that period are listed.
- Read only, no footprint - standard OData reads, nothing written back, no new object inside IFS Cloud.
Related reading
5.Frequently asked questions
Does IFS Cloud close a purchase order once it is fully received?
Whether IFS Cloud closes a fully received purchase order line depends on your setup, which is worth checking. Receiving and closing are separate steps: a receipt records the goods against the line, and moving the line or the order to a closed state is its own action, done by hand or triggered by a setting such as invoice matching. Where neither happens, a line received in full stays open, and comparing received with ordered across the status lists those lines.
How does the monitor tell a finished line from one that still has work?
It compares the received quantity with the ordered quantity and checks the line state and age. A line where received equals ordered and the line has stayed open past your close cadence is listed as a candidate. The monitor cannot know whether a final invoice or a price check is still pending, so the buyer who owns the order decides whether to close it, hold it, or investigate.
Does the SCM Automation Pack check this today?
No. The SCM Automation Pack runs three rules today: unconfirmed purchase orders, late deliveries, and stock below minimum. A rule that lists lines received in full and still open would be an additional rule built to order, and a 30-minute call checks whether it fits your data.
Does this monitoring write anything to IFS Cloud?
No. The ordered quantity, received quantity and line state are read through OData projections and compared outside IFS. Nothing is written back, so there is no upgrade footprint and no new object inside the client system. Closing the line stays a human decision.
6.About the author
Dariusz Myśliwiec brings 18 years hands-on with IFS (Apps 7.5–10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Based in Kraków, delivering remotely across Europe and globally as an independent practice, so you talk to the consultant who builds it.
Selected clients: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
Close the finished orders before they distort the period
Tell me how your open purchase order list looks at month-end. On a 30-minute fit call we check whether a rule that compares ordered and received quantities with line status fits your data. The SCM Automation Pack runs three rules today (unconfirmed purchase orders, late deliveries, stock below minimum), so this would be an additional rule built to order, with a dry-run week before anything reaches a buyer.

Deutsch (Deutschland)
Polski (PL)