Vendor managed inventory and consignment stock arrangements are common in manufacturing, particularly in automotive supply chains, electronics assembly, and process manufacturing. The commercial logic is straightforward: the supplier holds inventory at the buyer's facility, replenishes it based on consumption signals, and invoices only when the buyer has consumed the material. The buyer carries less inventory risk and reduces working capital tied up in raw materials. The supplier maintains supply continuity and often a deeper commercial relationship.
The AP implication is less straightforward. Standard AP automation is built around a procurement cycle: someone creates a purchase order, goods are received against that order, a supplier invoice arrives, and the three parties are matched. VMI and consignment arrangements do not follow this cycle. There is no purchase order at the point of consumption. There is no traditional goods receipt note. The invoice reflects a consumption period or a cycle count, not a discrete delivery.
The result: VMI and consignment invoices consistently produce high exception rates in AP systems configured for standard procurement, require manual workarounds that introduce the data errors standard automation is designed to prevent, and create period-end accrual complexity that adds time to the close cycle.
How VMI and Consignment Billing Works
The mechanics vary by arrangement type, but the common patterns are:
- Cycle count billing: the supplier conducts a periodic physical count of inventory at the buyer's facility (or accesses the buyer's ERP inventory records) and invoices for the quantity consumed since the last count period. The invoice amount depends on what the count shows, not on a discrete order.
- Consumption signal billing: the buyer's ERP system generates a consumption report as material is withdrawn from the consignment stock location. The supplier invoices based on the consumption report data. The invoice amount depends on the accuracy and timing of the consumption signals.
- Replenishment-triggered billing: the supplier invoices when it replenishes the consignment stock rather than when the buyer consumes it. This is closer to a traditional procurement cycle but still lacks the discrete PO and GRN structure that three-way matching requires.
The AP Matching Problem
Standard three-way matching requires three documents: a purchase order, an invoice, and a goods receipt note. VMI and consignment billing typically provides only the invoice and a consumption or replenishment report. The purchase order as a discrete document either does not exist or is a blanket order that does not provide line-level matching data.
Without the traditional three-document match, AP automation routes every VMI and consignment invoice to the exception queue. This defeats the purpose of the automation for a billing arrangement that is typically high-frequency and high-volume. A manufacturer with 20 VMI suppliers receiving weekly consumption-based invoices can have 80 or more exception invoices per month from VMI billing alone, each requiring manual review.
Configuring AP Automation for VMI and Consignment
Replace the PO with a blanket agreement reference
The matching anchor for VMI and consignment invoices should be the framework agreement or blanket purchase order that governs the overall arrangement. The AP platform should be configured to match VMI invoices against the blanket agreement terms (agreed unit price, approved supplier, authorized product categories) rather than against a discrete PO.
This requires the blanket agreement to be structured in the AP system with the same data fields that the supplier's invoice will contain: unit of measure, unit price, product code, and billing period definition. The agreement record replaces the PO in the matching logic.
Integrate consumption data as the goods receipt equivalent
For consumption-signal and cycle-count billing, the consumption data from the buyer's ERP or WMS replaces the goods receipt note as the quantity confirmation. The AP platform must be able to ingest consumption data from the inventory system, match it against the supplier's invoice quantity, and approve the invoice when the quantities align within a defined tolerance.
This integration is the technically demanding part of VMI AP configuration. It requires a data feed from the inventory or ERP system into the AP platform, mapping between inventory system product codes and the supplier's invoice line descriptions, and tolerance rules that reflect the natural variance between cycle count quantities and precise consumption records.
Period-end accrual for consumed but unbilled inventory
At period end, VMI and consignment stock that has been consumed but not yet invoiced represents a period liability. Without an automated accrual mechanism, this liability is either missed (understating COGS) or estimated imprecisely (producing accrual reversals that distort the following period).
The accrual calculation requires the inventory system to provide a consumed-but-not-billed quantity at period end. Multiplied by the agreed unit price from the blanket agreement, this produces the accrual amount. Automating this calculation at period end, rather than relying on a manual estimate from the AP team, improves accuracy and reduces close cycle time.
Supplier Collaboration Requirements
VMI and consignment billing works as an AP automation use case only if the supplier's invoicing practice is compatible with the AP platform's configuration. This requires explicit supplier communication about:
- Invoice format: the supplier must invoice in a format that the AP system can extract cleanly. A handwritten summary of consumed quantities does not feed into automated matching regardless of how well the matching logic is configured.
- Billing reference data: the invoice must reference the blanket agreement number or a consumption report identifier that the AP system can use as a matching anchor.
- Billing period alignment: the supplier's billing period should align with the buyer's accounting period to reduce cut-off complexity at month end.
Suppliers who are resistant to format standardization are a genuine constraint on VMI AP automation. This is a commercial conversation rather than a technical one: the AP team needs procurement's support to establish the format requirements as part of the VMI commercial terms.
