Hospital procurement software: connect the indent, receipt and invoice

A ward requests 120 boxes. Stores can issue 30, so procurement orders 90. The supplier delivers 80, of which five await inspection. The purchase dashboard says “received”, while the ward still needs stock and finance has an invoice for all 90.

Hospital procurement software should connect those records without collapsing their meanings. The department's indent records demand; the purchase order records an approved commitment; the receipt records custody; acceptance and invoice review add separate decisions.

Make the quantities explain one another

In this illustrative transaction, 120 boxes of demand are covered by a 30-box internal issue and a 90-box purchase. Of the purchase, 80 boxes have arrived and ten have not. Within the 80, 75 are accepted and five remain under review. No quantity disappears because a screen uses one completion flag.

The example assumes an acceptance process supplied by the provider’s responsible item-category owner. It does not define inspection criteria or clinical equivalence. In the software demonstration, an invoice alone should not create the acceptance event that this agreed process requires.

Compare modules using the same unfinished purchase

oeHealth's procurement documentation describes quotations, approvals, receipt tracking and invoice matching. These capabilities establish useful demonstration topics, but the buyer needs evidence from the proposed implementation.

First test the hospital's existing HIS purchasing module. Can it link the indent, stock issue, order, receipt and invoice line? Can it retain partial and restricted quantities? If it can, configuration may be more practical than introducing another application.

A separate procurement layer is one option when the existing module cannot demonstrate the required handover. Compare supported interfaces, identifier and unit mappings, correction behaviour and reconciliation ownership. Keep any unproven integration as a selection dependency rather than an assumed capability.

Give the open quantities an owner

The stores team follows the five boxes awaiting review. Procurement follows the ten not delivered. Finance holds or routes the invoice difference under its approved rules. The department sees what is available to fulfil the indent, rather than assuming all received stock can be issued.

The exception queues should preserve the original documents and comments. Closing an order for convenience must not silently convert an undelivered quantity into a receipt. Record who approved a short closure and how the outstanding departmental need will be handled.

Run a bounded evaluation

Ask the evaluator to open the example from each team's starting screen. From the ward indent, can they find the 30-box issue and the linked 90-box order? From the delivery, can stores explain the 75 accepted and five pending boxes? From the invoice, can finance find that same acceptance evidence without retyping the quantities? An exported total without these references is a report connection, not the complete purchase trail being evaluated.

Use missing references as selection evidence. A module that handles the whole trail may need configuration; a module that loses identity between receipt and finance may need a supported integration. Purchase approval design addresses who may commit the order, while AP matching addresses which invoice lines are ready for finance review. Keep those later decisions separate from this module-selection question.

Choose one site and a routine item category with agreed handling rules. Capture item and supplier IDs, units, indent and order versions, receipt lines, acceptance decisions and invoice references. Avoid starting with every specialist category at once.

Test partial delivery, rejection, an invoice before receipt, a changed pack size and a repeated import. The integration should either produce one supported business event or put the case in an owned exception queue. During an outage, use the agreed manual reference and reconcile it before resuming automated writes.

Measure open quantities, exception age and re-entry effort across the agreed sample. Do not report the whole order as complete while inspection or delivery remains unresolved. The useful procurement improvement is a handover that each team can explain.

Next actions

1. Trace one unfinished purchase through stores, procurement and finance.
2. Demonstrate its partial receipt and correction in the existing module and proposed alternative.
3. Agree ownership, interface support and exception acceptance before selecting the system.

Topics: hospital procurement software · hospital purchase management · hospital procurement ERP · indent to purchase order