Consigned Inventory in Oracle Fusion: Where Ownership Actually Changes, and Where Healthcare Systems Get Burned

A hospital's implant consignment closet reconciles beautifully on paper. Every quarter, the physical count matches what the system says should be on the shelf. Then finance runs the month-end supplier settlement and the number is off by six figures. Nothing was stolen. Nothing was miscounted. The gap was in a place nobody was looking: when Oracle actually believed ownership changed.

What consigned inventory actually means

Consigned inventory sits on your shelf, tracked in your system, physically available to your team, while the supplier still owns it. Ownership doesn't transfer at receipt the way it does with a normal purchase. It transfers at the point of consumption, when the item is actually used. Until that moment, you're holding someone else's asset, not your own inventory value.

That distinction sounds simple until you look at where the receiving transaction, the usage transaction, and the supplier billing event actually live, often owned by three different teams who rarely talk to each other about this specific handoff.

How Oracle Fusion models the ownership change

The item and the purchasing agreement both need to be flagged as consigned before receipt, which tells the system to bring the item in as supplier-owned rather than immediately capitalizing it. The receipt itself is a physical movement only, not a financial event.

The financial event is the consumption transaction. When the item is issued, used, or otherwise consumed, that transaction is what actually changes ownership from supplier to you, and it's what generates the basis for a consumption advice back to the supplier, the document that drives their invoice. If consumption transactions aren't happening cleanly, or aren't happening at all for certain movement types, the ownership change never fires and your on-hand value quietly diverges from what's actually true.

The exact task names and setup screens for consigned item attributes and consumption advice generation have moved around across Oracle Fusion releases, so treat this as the shape of the process rather than a click-by-click guide, and confirm the current navigation against your release's documentation before configuring it.

Where healthcare systems get burned

Point-of-use capture gap. The consumption event is supposed to fire when the implant is used in a case, but if the OR's usage capture, often a separate clinical or surgical inventory system, doesn't reliably feed that transaction back into Oracle, items get physically consumed with no corresponding ownership change ever recorded.

Unit of measure mismatches. Supplier agreements are frequently priced and consumed in different units than the item is received in, especially for kits and sets. A mismatch here doesn't just cause a reconciliation headache, it changes the dollar value of every consumption advice generated off the wrong quantity.

Lot and expiry drift. Consigned implants and biologics are usually lot-controlled with expiration dates that matter clinically, not just financially. If lot consumption isn't tied cleanly to the specific unit actually used, expired or recalled lots can sit invisible inside what looks like a clean on-hand balance.

The takeaway

Don't audit consigned inventory by checking whether the shelf count matches the system count. Audit it by checking whether every consumption event that should have fired for a given period actually fired, and whether the consumption advice generated off that event matches what the supplier is actually invoicing. The shelf can look perfect and the ownership ledger can still be wrong.