Sporadic hospital feeds to ERP+X12 consignment reconciliation—billing, replenishment

Overview

A healthcare supplier ran consignment programs at hospitals without a reliable way to reconcile what had been used, what remained in storage, and what to bill. Usage reports arrived sporadically in different formats, item identities did not always match, and replenishment happened on email prompts. Intelligex implemented a consignment reconciliation layer that synchronized hospital usage feeds with the supplier’s Enterprise Resource Planning (ERP) system, normalized item and location identities, and enforced billing and replenishment rules with joint approvals. Billing aligned with actual consumption, replenishment triggered on agreed thresholds, and month-end reviews shifted from disputes to exception handling.

Client Profile

• Industry: Healthcare supplies and medical devices
• Company size (range): Multi-region supplier serving acute and ambulatory facilities
• Stage: Established ERP, EDI connections with provider networks, growing consignment footprint
• Department owner: Procurement, Supply Chain & Logistics
• Other stakeholders: Sales operations, Customer service, Finance/Accounts Receivable, IT applications, Provider materials management, Operating room/point-of-use teams, Quality and regulatory

The Challenge

Hospitals consumed consigned stock from storerooms, procedure rooms, and point-of-use cabinets. Usage signals reached the supplier through a mix of EDI product activity reports, portal exports, and spreadsheets. Item identifiers varied between hospital item masters and supplier catalogs. Location references did not consistently tie to the ship-to or consignment agreement. When the supplier invoiced, providers challenged mismatches, and replenishment orders were placed without a clean view of balances.

Core platforms were not the issue. The ERP handled item masters, pricing, customer agreements, orders, and invoicing. EDI and portals connected to provider materials systems and inventory cabinets. None of these owned a shared model for consignment balances, nor did they enforce billing rules such as lot-level traceability, price effectivity, and who approves discrepancies. The result was reactive clean-up, credits and rebills, and strained conversations with hospital partners.

Why It Was Happening

Data arrived fragmented and out of sync. Providers reported usage by hospital item number, catalog number, or description; locations were free-text; and time windows for activity reports varied. Mapping to the supplier’s item and pricing records required manual crosswalks. Partial feeds missed returns or adjustments, so balances drifted from reality. Responsibility for reconciling exceptions landed wherever someone noticed a discrepancy.

Process gaps reinforced the inconsistency. Billing rules lived in contract PDFs and email trails. Replenishment thresholds were applied informally. When a new item or substitute was placed in the bin, the change did not flow to the consignment agreement or to the mapping tables. Without clear ownership and review gates, both sides spent cycles debating inputs rather than working from a common record.

The Solution

Intelligex delivered a consignment reconciliation and orchestration layer that normalized hospital usage feeds, aligned them to the supplier’s ERP records, and applied governed billing and replenishment rules. The solution ingested usage via Electronic Data Interchange (EDI) and secure files, mapped item and location identities, reconciled balances by site and bin, and generated billing proposals and replenishment orders. Exceptions flowed to a joint review queue with reason codes, and approvals were captured before invoices or replenishment releases. Item and location identities adopted standards for clarity, including Global Trade Item Numbers (GS1 GTIN) and Global Location Numbers (GS1 GLN), and product activity used common EDI messages such as the X12 Product Transfer and Resale Report.

• Integrations: Bi-directional sync with ERP for item masters, contract pricing, consignment agreements, orders, and invoicing (for example, SAP S/4HANA); ingestion of provider usage via EDI (X12 867, 852) and secure flat files; optional cabinet feeds and provider portals; identity alignment using GS1 GTIN and GS1 GLN.
• Canonical data model: Standardized attributes for item identities, units of measure, lot and expiration where applicable, provider locations, ship-to accounts, contract terms, and price effectivity dates.
• Reconciliation engine: Matching of reported usage to consignment balances by site and bin, handling returns and adjustments, and proposing billing lines and replenishment quantities based on rules and thresholds.
• Validations and guardrails: Checks for item mapping gaps, unit-of-measure mismatches, out-of-date prices, and missing lot details; prevention of billing when identities or terms are unclear; prompts to update mappings and price effectivity.
• Exception workflow: Human-in-the-loop review for mismatches and substitutes; joint approvals by supplier account teams and provider materials management; reason codes for adjustments and credits.
• Replenishment orchestration: Auto-generation of replenishment orders when balances hit thresholds; alignment to hospital appointment windows and receiving constraints; visibility to both parties.
• Dashboards: Site-level balances, open exceptions, aging of disputes, replenishment due, and trend views of usage versus plan.
• Permissions and audit: Role-based access for supplier teams and selected provider contacts; immutable logs of usage, mappings, approvals, and invoice ties.

Implementation

• Discovery: Mapped current consignment processes by hospital; inventoried usage feed formats and cadences; audited item and location crosswalks; reviewed contract terms and price effectivity; identified common exception patterns and dispute drivers.
• Design: Defined the canonical item and location model; established mapping rules and exception categories; designed reconciliation logic and replenishment thresholds; set approval matrices for joint reviews; agreed on a shared glossary for statuses and reason codes.
• Build: Implemented ERP connectors and EDI/file ingestion; configured item and location mapping tables with GTIN and GLN where available; built the reconciliation and validation engine; created the exception console, approval flow, and dashboards; enabled replenishment order creation and invoice proposal generation.
• Testing/QA: Replayed historical usage and billing cycles; validated mappings and price effectivity; exercised returns, adjustments, and substitutes; ran observe-only reconciliations while legacy processes continued; tuned thresholds and exception triggers with supplier and provider teams.
• Rollout: Piloted with a small set of hospitals and high-value lines; maintained the legacy dispute process as a fallback; enabled invoice proposal reviews and replenishment orchestration after results stabilized; expanded by region and provider network.
• Training/hand-off: Scenario-based training for supplier account teams, customer service, and Accounts Receivable; provider enablement on usage feed cadences and exception reviews; quick guides embedded in the console; transitioned operations to supply chain and finance with IT support on call.

Results

Billing and replenishment became straightforward. Usage feeds aligned to item and location identities, invoices reflected actual consumption at contracted prices, and replenishment orders flowed based on agreed thresholds. Exceptions moved through a joint review with context and reason codes, so credits and adjustments were handled intentionally rather than by default.

Relationships with hospital partners improved. Both sides worked from the same facts and timelines, backed by standardized identities and an audit trail of approvals. Month-end close no longer required broad reconciliations, and calls shifted from debating data to coordinating replenishment and handling edge cases such as substitutes or returns.

What Changed for the Team

• Before: Usage arrived in mixed formats and identities; After: Feeds were normalized and mapped to a canonical item and location model.
• Before: Billing and replenishment were triggered by email and memory; After: Reconciliation proposed invoices and replenishment based on rules and thresholds.
• Before: Disputes dragged on with unclear ownership; After: Exceptions routed to joint approval with reason codes and audit trails.
• Before: Price updates and substitutes caused surprises; After: Price effectivity and item mapping checks prevented mismatches at source.
• Before: Visibility of balances depended on spreadsheets; After: Dashboards showed site-level balances, open exceptions, and replenishment due.

Key Takeaways

• Treat consignment as a data problem: normalize usage feeds and align item and location identities before reconciling.
• Apply clear billing and replenishment rules with joint approvals so exceptions are governed rather than improvised.
• Integrate with ERP and existing EDI/portal connections; layer reconciliation, validations, and workflows without replacing core systems.
• Use standards such as GS1 GTIN, GS1 GLN, and common EDI messages from X12 to reduce mapping friction.
• Start with a few hospitals and lines, run observe-only reconciliations, then enable invoice proposals and replenishment once exception rates stabilize.

FAQ

What tools did this integrate with?
The solution synchronized item masters, consignment agreements, pricing, orders, and invoicing with the ERP (for example, SAP S/4HANA). It ingested hospital usage via EDI product activity reports (such as X12 867 or 852) and secure files, and interacted with provider portals and cabinet systems where available. Item and location identities referenced GS1 GTIN and GS1 GLN.

How did you handle quality control and governance?
We enforced validations for item mapping, unit-of-measure alignment, price effectivity, and lot/expiration where applicable. Reconciliations that failed checks routed to a joint exception queue with reason codes, and invoices were not created without approval. Mappings and rules were versioned, and all actions—ingestion, matches, overrides, and approvals—were audit-logged.

How did you roll this out without disruption?
We started in observe-only mode, running reconciliations in parallel with the legacy process and comparing outcomes. Early pilots focused on a small set of hospitals and product lines. Once mappings and thresholds were stable and users trusted the results, invoice proposal reviews and replenishment orchestration were enabled, with the legacy path available as a fallback during transition.

How were item and location mismatches resolved?
The console highlighted unmapped items and ambiguous locations with suggested matches based on GTIN, catalog number, and prior decisions. Supplier and provider stewards confirmed mappings, which were then stored for reuse. Reconciliation paused billing for those lines until mappings were approved to prevent downstream corrections.

How did replenishment align with hospital operations?
Replenishment thresholds were set by site and bin. When balances dropped below target, the system generated a replenishment order aligned to appointment windows and receiving constraints shared by the hospital. Substitutes and backorders followed exception paths, and both parties saw status and expected arrival in the same dashboard.