Skip to main contentSkip to footer

IFS Cloud Implementation Rescue: Diagnose, Decide, Recover

IFS Cloud implementation rescue for stalled projects: a diagnostic, a keep, repair or rebuild decision per area, and a dated recovery plan.

IFS Cloud implementation rescue · Independent IFS Cloud practice A stalled IFS Cloud project needs a diagnosis, a decision per area and dated gates The go-live…

Read more

IFS Cloud Reporting Tools: Quick Reports to Lobbies

IFS Cloud reporting tools in six layers: Quick Reports, Business Reporter, Lobbies, Power BI, Analysis Models and OData, and when to use each.

Independent IFS Cloud practice · Reporting From the weekly Excel export to a Lobby your team opens first Key takeaways IFS Cloud reporting tools fall into six…

Read more

Goods Received but Not Put Away in IFS Cloud

Stock booked in but still sitting in receiving counts as on hand in IFS Cloud, yet no one can pick it. Here is how the gap forms and how to see it.

Independent IFS Cloud practice · Warehouse Received stock that no picker can reach yet A receipt against a purchase order does two things that people treat as…

Read more

The Sales Quote That Expired While Nobody Followed Up

A sales quotation in IFS Cloud has a validity date. When it lapses with no order and no follow-up, revenue leaks. How to flag expiring quotes in time.

Independent IFS Cloud practice · Sales The sales quote that expired while everyone assumed it was still live A sales quotation in IFS Cloud carries a validity…

Read more

The Won Quote That Never Became an Order in IFS

The customer accepted the quote, but nobody turned it into a sales order. Agreed demand never reaches planning, and the win stalls on an admin step.

Independent IFS Cloud practice · Sales The deal the customer already said yes to, still not an order The quotation went out, the customer accepted it, and…

Read more

Customer Order Holds That Never Get Released in IFS Cloud

A customer order goes on hold for a good reason, the reason passes, and the hold stays. The order sits shippable but blocked, and revenue waits.

Independent IFS Cloud practice · Sales & order management The order held for a reason that has since passed A customer order gets a hold placed on it. A…

Read more

Blocked Customer, Open Sales Orders in IFS Cloud

A customer is blocked or on stop, yet sales orders raised earlier keep moving to picking and delivery. The block guards new entry, not the backlog.

Independent IFS Cloud practice · Sales The customer you blocked, and the orders still shipping You block a customer for a reason: a payment problem, a dispute,…

Read more

Customer Over Credit Limit but Not Blocked in IFS Cloud

A customer can pass their credit limit in IFS Cloud while their orders keep flowing, unblocked. How to surface unchecked credit exposure daily.

Independent IFS Cloud practice · Sales & Credit The customer over their limit whose orders were never stopped A credit hold in IFS Cloud is the visible case:…

Read more

Customer With No Credit Limit Set in IFS Cloud

A customer with open exposure can have no credit limit set, so a credit check has nothing to test. Find the blank limits before the receivable goes bad.

Independent IFS Cloud practice · Sales & Credit The customer with open orders and no credit limit to check them against The account looks active and healthy,…

Read more
Abstract illustration on a navy background with the article title: “Consignment Stock That Never Reconciles in IFS Cloud”

Independent IFS Cloud practice · Inventory

The stock in your racks that the books say you do not own yet

Consignment stock sits on your floor and behaves like yours. You can see it, pick it, build with it. What is different is who owns it. Title and the payable move only when the stock is consumed or drawn down, and that transfer depends on a transaction firing at the right moment. When the consumption is not reported, or the ownership move does not post, the consignment balance drifts away from reality. You are either holding value you should already have paid for, or you have used value that never became a liability. Either way, the number nobody is watching is wrong.

Key takeaways

  • Consignment stock changes ownership on consumption, not on receipt. That single difference is what makes it drift silently, because the physical move and the financial move are separate events that can fall out of step.
  • This is not goods received not invoiced. There the stock is yours and the liability already exists, waiting for an invoice. In consignment the liability is not supposed to exist yet, so the risk is the transfer that should have fired and did not.
  • It is also not a stale reservation. A reservation locks availability. A consignment mismatch misstates ownership and value, which reaches the balance sheet, not just the plan.
  • Consignment stock that never gets consumed is a second trap: it looks free because you have not paid for it, so it escapes the usual slow-moving and obsolete reviews and ages unseen.
  • The on-hand consignment balances and the consumption transactions both live in IFS Cloud, so a read-only monitor can compare them and surface the positions that stopped reconciling.

1.Why a consignment position drifts without anyone touching it

Consignment is a good deal precisely because ownership sits with the supplier until you use the stock. That deal depends on the moment of use being captured. When a part is issued to a job, or picked for an order, the system is meant to record the consumption and move title, which creates the payable. If the issue is reported against the wrong stock, if consumption is entered late, or if the ownership move fails to post, the physical stock has gone but the consignment record still says it is there and still says the supplier owns it.

The reverse happens too. Stock arrives on consignment, gets counted, and then simply sits. It does not show up in a spend report, because you have not spent anything. It does not trip the usual value alarms, because on your books it carries no owned value. It is real stock taking real space, invisible to the reports that would normally question why it has not moved.

So the leak is not a broken posting rule. Consignment works as designed. What is missing is the periodic reconciliation: nothing compares what the consignment balance says against what was physically consumed and asks where the two stopped agreeing.

2.Where the cycle from consumption to payment stalls

A healthy consignment position turns over: stock comes in, gets used, ownership transfers, the supplier gets paid. The value is in finding the positions where that cycle stalled.

What you see What it usually points to
Consumption recorded, but no matching ownership transferA stock you have used and owe for, still sitting on the books as the supplier's, so the payable never formed.
Consignment on hand with no consumption for a long periodStock aging outside every value review because it carries no owned cost, quietly filling space.
A consignment balance that no longer matches the physical countA reporting gap between what was drawn down and what the record shows, growing every cycle it is not checked.
Own stock placed on consignment at a customer, with usage reports laggingRevenue you have earned but not recognised, because the customer's consumption has not reached your records.

The first row is the one that reaches finance. The stock is gone, the job is built, and the obligation to the supplier is real, but nothing on your books shows it until a reconciliation or a supplier statement forces the question. Read across many parts and sites, that is a liability you are carrying without seeing.

3.Reconciling consignment balances against consumption, read-only

The consignment on-hand balances and the consumption transactions are both available through standard OData projections, so they can be read without touching a record. Detection looks across consignment stock and checks two things:

  1. Consumption without a transfer - where stock was issued or picked but no ownership move followed, so the payable that should exist is surfaced before a supplier statement finds it.
  2. Balances that stopped moving - consignment on hand with no consumption over a period you set, so stock aging off the books is seen the same way owned stock would be.

Because it is a read-only monitoring pattern, it runs beside inventory and writes nothing back to IFS. It adds no object inside the client system, and 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 inventory and finance owners a short list of consignment positions to reconcile, and the correcting entry stays with the people who own the books.

4.Rolling it out without noise

  • Start with your largest suppliers - reconcile the consignment agreements that carry the most value first.
  • Dry-run first - log which positions would have been flagged across a full period before anyone acts on a line.
  • Separate consumption from idle stock - keep the list of consumption with no transfer apart from the list of balances that have gone quiet.
  • Read only, no footprint - standard OData reads, nothing written back, no new object inside IFS Cloud.

See the SCM Automation Pack Book a 30-minute fit call

5.Frequently asked questions

Does IFS Cloud not keep consignment ownership straight on its own?

Ownership moves when a consumption transaction posts correctly, so the risk lives in the events around it: consumption reported late, issued against the wrong stock, or an ownership move that does not fire. When that happens the consignment record and the physical stock disagree, and comparing consignment balances against consumption is what shows the drift.

How is this different from goods received not invoiced?

Goods received not invoiced is owned stock: the liability already exists and is waiting for the supplier invoice. Consignment is the opposite starting point. The stock is not yours until you use it, so the risk is a transfer that should have created the liability on consumption and did not. One is a missing invoice against a known debt, the other is a debt that never got recorded.

Why does unused consignment stock matter if we have not paid for it?

Because it takes real space and can obsolete like any other stock, but it hides from value-based reviews. Slow-moving and obsolete reports usually key off owned cost, and consignment carries none on your books, so it ages unseen. Watching consumption rather than value brings it back into view.

Does this monitoring write anything to IFS Cloud?

No. The consignment balances and consumption transactions are read through standard OData projections and compared outside IFS. Nothing is written back, so there is no upgrade footprint and no new object inside the client system. Any correcting entry is made by your own team.

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.

Know what you owe before the supplier statement does

Tell me which consignment agreements carry the most value and where consumption tends to go unreported. On a 30-minute fit call we check whether a rule comparing consignment balances with consumption 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 your team.

Book a 30-minute fit call

ROI Calculator

Calculate your return on investment

Input Values

€
€
€

Results

Annual Savings
€ 0
Payback Period
0 months
ROI
0%
Monthly Savings
€ 0

Get Detailed Report

Enter your details to receive a detailed ROI report.