Independent IFS Cloud practice · Supply Chain
The supplier you blocked is still receiving your orders
Someone puts a supplier on hold. A quality problem, a payment dispute, a compliance flag. The block feels like a full stop. It is not. It governs new purchasing, and unless someone acts on them, the orders already out there keep their own dates and their own path to receipt. Open purchase lines keep their promised dates, receipts keep arriving at the dock, and the business keeps taking goods from a supplier it decided to stop dealing with. The decision was made. The exposure stayed open.
Key takeaways
- A supplier block is a status on the supplier record. The purchase orders and receipts already in flight against that supplier are separate records, so someone has to read the two together.
- This is not the same as a shift in supplier behaviour you are trying to detect. Here you already made the call to stop; the gap is that open commitments do not stop with it.
- The risk is concrete: goods you no longer want are received and become on hand, and the receipt can move straight toward an invoice you did not intend to pay.
- Nobody sees the pattern because the block lives on the supplier record while the exposure lives on scattered order lines. The two are never read together.
- The supplier’s blocked status and the open order lines are both in IFS Cloud, so a read-only monitor can cross-reference them and surface every open line against a blocked supplier on the first scan after the block goes on.
1.Why a stop on the supplier does not stop the orders
A supplier block is a forward-looking control, aimed at new purchase activity against that supplier. The unstated assumption is that stopping new orders is the same as stopping the relationship. It is not. Every order raised before the block is its own record, with its own promised dates and its own path to receipt and invoice.
So the supplier record says stop, while a dozen order lines say carry on. A delivery already in transit arrives and is received. A receipt already booked flows toward matching and payment. The person who set the block assumes the system now protects the business from that supplier. What the block is aimed at is the next order, not the last twenty.
Closing a live order is a business decision, not a side effect of a status change on the supplier. The supplier record on its own does not show that those live commitments and the block now contradict each other.
2.Open lines behind a block that carry real exposure
A block set an hour ago on a supplier with a handful of routine open lines is a housekeeping task. The value is in separating that from exposure that is about to turn into received goods or a paid invoice you cannot easily reverse.
| What you see | What it points to |
|---|---|
| Open PO lines against a blocked supplier | Live commitments the block never touched: goods still expected from a source you chose to stop. |
| A receipt booked after the block went on | Goods you no longer wanted are now on hand, and the reason to reject them is already recorded on the supplier. |
| An invoice matching a post-block receipt | Payment heading out to a supplier under dispute or hold, which is the exposure the block was meant to prevent. |
| A blocked supplier that is also sole source on a part | A stop with no alternative in place, which turns a control into a coming shortage if nobody plans around it. |
A receipt-to-invoice match after the block costs real money. The block was set to hold payment or protect quality, and a receipt-to-invoice match quietly walks around it. Read across the whole open book, that contradiction is exactly what a buyer clearing one order at a time cannot see, because the block and the order line never appear on the same screen.
3.Reading the blocked status against the open book
The supplier’s blocked status and the open purchase lines are standard data in IFS Cloud and can be read through OData projections without touching a record, and the moment a block appears is dated by the first read that sees it. Detection joins the two things a person never joins by hand and looks for:
- Open lines against a blocked supplier - any purchase line still open, or any receipt booked, after the supplier was placed on hold, so the contradiction surfaces the day the block goes on rather than at month end.
- Post-block movement toward payment - a receipt or an invoice match that happened after the block went on, which is the exact exposure the block was set to stop and the costliest to unwind.
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 an R1 or R2 release 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 hands the buyer a short list of open lines to cancel, hold, or re-source, and the decision on each one stays with procurement, where it belongs. It sits next to two checks the Pack already runs: unconfirmed purchase orders and late deliveries.
4.Rolling it out without noise
- Start with suppliers on hold today - clear the open lines behind existing blocks before watching new ones.
- Dry-run first - log what would have been flagged across the current open book before a single alert reaches a buyer.
- Open lines first, payment movement second - list every open line against a block, then the receipts and invoice matches that moved toward payment after it.
- Read only, no footprint - standard OData reads, nothing written back, no new object inside IFS Cloud.
Related reading
5.Frequently asked questions
If I block a supplier in IFS Cloud, why can open orders still be received?
Because a supplier block is a status on the supplier record, not an instruction to close what is already in flight. Purchase lines raised earlier are separate records, so a delivery already in transit can still arrive and be received unless someone acts on those lines. Closing a live order against a blocked supplier is a separate business decision.
How is this different from detecting a change in supplier behaviour?
Detecting a behaviour change is about spotting a supplier drifting before you decide anything. This is the opposite end: you have already decided to stop, and the gap is that your open commitments did not stop with the decision. The monitor reads the block you set against the orders still open behind it.
What is the worst case if this goes unnoticed?
Goods you rejected the supplier for are received and counted as on hand, then a receipt-to-invoice match sends payment to a supplier under dispute or hold. Reversing a receipt and clawing back a payment costs more effort than cancelling the open line would have, which is why the exposure is worth catching the day the block is set.
Does monitoring this require writing to IFS Cloud?
No. The supplier’s blocked status and the open purchase lines are read through standard OData projections and analysed outside IFS, and the date a block first appears is tracked by the monitor. Nothing is written back, so there is no upgrade footprint and no new object inside the client system.
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 exposure the block left open
Tell me which suppliers you have on hold and why. On a 30-minute fit call we check whether a rule comparing supplier blocks with your open purchase book 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.