How to Match Steel Mill Invoices to Goods Received

Match a steel mill invoice by checking each invoice line against the PO line, receiving record or GRN, delivery paperwork, and the material actually received. Before approval, verify grade, dimensions, treatment or coating, billed weight, received quantity, UoM, heat or coil references when present, freight, surcharges, and partial shipment status.

That line-level detail matters because steel invoices can look financially reasonable while still being wrong. A header-level match might show the right vendor, PO number, invoice total, and receipt reference. It might still hide a gauge substitution, a billed weight that does not agree with the scale ticket, a surcharge that was not in the price agreement, or a full-order invoice sent before all bundles arrived.

AISI reported full-year 2025 steel shipments of 91,158,528, up 5.1 percent from 2024, according to AISI's revised 2025 steel shipment data. For steel service centers, metal-building distributors, and steel-buying manufacturers, invoice controls sit in the physical flow between what was ordered, what arrived, what was booked into inventory, and what the supplier is asking AP to pay.

The practical test is not "does this invoice have a receipt?" It is "does each invoiced steel line match the material and commercial terms behind the receipt?" A safe match ties the invoice line to the PO line, the receiving line, and the delivery evidence. It also leaves room for legitimate timing differences, such as material received before final billing, without treating every unmatched receipt as supplier error.

The document chain AP has to reconcile

A steel invoice match starts with the purchase order, but it should not end there. The PO shows the agreed supplier, item description, grade or specification, quantity basis, price, delivery terms, and any negotiated surcharge treatment. The mill invoice shows what the supplier is billing. The receiving record or GRN shows what the company has booked into inventory. Delivery paperwork shows what physically arrived with the truck, and it may contain details that never make it cleanly into the ERP receipt.

That distinction is where steel AP work differs from a generic receipt match. A receiving record might confirm that material arrived, while the packing slip, delivery note, or yard paperwork carries the bundle references, weights, or exceptions that explain whether the invoice line is actually payable. When heat numbers and mill test reports are part of the packet, a steel invoice MTR packet reconciliation spreadsheet can keep that evidence tied to each line. Teams that already use delivery note invoice matching for supplier paperwork need the same discipline here, with more attention to steel attributes and weight basis.

For many steel purchases, AP also needs evidence outside the invoice and receipt. A scale ticket or yard log may be the best support for received weight. A price sheet, contract, or mill agreement may be the only place where fuel, alloy, zinc, scrap, energy, or freight adjustments can be checked. If those charges appear on the invoice as separate lines, the invoice cannot be approved only because the material receipt exists.

The purchase order, invoice, and receipt still form the control backbone, as in three-way matching in manufacturing. The steel-specific layer is the extra field evidence: which material arrived, in what form, at what weight, under which price terms, and whether the receiving record captured enough detail to support the billed line.

The steel-specific field map that prevents false matches

The header fields still matter: vendor, invoice number, invoice date, PO number, ship-to or yard location, currency, payment terms, and invoice total. They identify the transaction and help prevent obvious duplicate or wrong-vendor payments. They do not prove the steel itself matches.

The match lives in the line detail. AP should compare the invoiced material against the PO and receipt using the steel attributes that define what was bought: grade or alloy, gauge or thickness, width, length, coating, galvanizing, treatment, or finish. Where the paperwork includes heat, coil, bundle, cast, or mill references, those identifiers help tie the invoice back to the material received. They are useful control fields, but the workflow should not fail simply because every supplier does not provide every identifier.

Quantity needs the same field-level treatment. Ordered quantity, received quantity, billed weight, unit of measure, unit price, and extended amount should sit in separate columns. Steel invoices often mix pieces, bundles, feet, hundredweight, pounds, tons, or kilograms depending on the product and supplier. A billed weight versus received quantity difference is not automatically an error, but it needs a traceable basis: agreed conversion, theoretical weight, actual scale weight, or another method the buyer accepts.

For spreadsheet review, each extracted invoice line should repeat the invoice number, invoice date, vendor, PO number, and source reference. That repetition looks redundant until AP has to sort by PO, filter by heat number, compare all billed weights for one receipt, or send one disputed line back to procurement without losing the invoice context.

A practical review file can use this field map:

• Header and routing: Extract vendor, invoice number, invoice date, PO number, ship-to or yard location, and payment terms. Compare them against the PO, supplier master, and receiving record to confirm the invoice belongs to the right supplier, order, location, and approval path.
• Material specification: Extract grade, alloy, gauge or thickness, width, length, coating, treatment, and finish. Compare them against the PO line, delivery paperwork, and receiver notes to catch substitutions that may not change the invoice total but do affect inventory and customer orders.
• Material identifiers: Extract heat, coil, bundle, cast, or mill reference where present. Compare them against the packing slip, mill paperwork, and yard log so the billed line ties back to the specific material that arrived.
• Quantity and weight: Extract ordered quantity, received quantity, billed weight, UoM, unit price, and extended amount. Compare them against the receipt line, scale ticket, and agreed conversion basis to separate valid unit differences from overbilling or receiving errors.
• Freight and surcharges: Extract freight, fuel, alloy, zinc, scrap, energy, and other adjustment lines. Compare them against the contract, price sheet, or freight agreement so unsupported add-ons do not pass as standard invoice detail.
• Verification trail: Extract source file, page number, receiver note, and exception reason. Keep those fields tied to the original invoice and supporting documents so AP can get back to the evidence when a line is disputed.

Invoice Data Extraction supports this line-level structure by converting invoice PDFs into Excel, CSV, or JSON with one row per payable line and separate invoice, PO, receipt, material, weight, surcharge, source file, and source page fields. In a steel AP workflow, invoice data extraction for steel AP teams prepares the field map for review; it does not decide whether a substitution, tolerance, or surcharge is commercially acceptable. For metal-building work, the same line detail can also feed a PEMB component job-cost spreadsheet once AP has separated component classes, freight, credits, and source checks.

Common steel invoice mismatches and AP actions

The matching result should drive a specific AP action. Clean matches can be approved when the invoice line, PO line, receiving evidence, and price terms agree. Lines with unsupported specifications, charges, duplicate identifiers, or unresolved quantity differences should be held. Timing gaps need follow-up with receiving or procurement before AP treats them as supplier overbilling.

• Partial or early billing: A mill may invoice the full order while only part of the material has arrived. If AP matches only the PO total to the invoice total, it can release payment as if the whole order reached the yard. Hold affected lines until AP has partial receipt detail, supplier correction, or documented approval to accrue.
• Specification mismatch: The PO may call for one grade, gauge, width, length, coating, or treatment, while the invoice line or receiving note shows a substituted product. Hold the line until procurement approval, receiver notes, a corrected invoice, or a credit note explains the difference.
• Weight difference: A difference between billed weight and received weight may come from actual scale weight, theoretical weight, rounding, moisture, packaging, scrap allowance, or a unit conversion between the supplier and the buyer. Compare the invoice to the agreed basis and receiving evidence before approving or disputing the line.
• Duplicate line or receipt risk: A duplicate invoice number is obvious; a repeated bundle reference, material identifier, freight line, or receipt match is easier to miss. Sort extracted lines by PO, receipt, bundle, and invoice number before approving.
• Unsupported surcharge: Surcharges are another common leakage point. Fuel, freight, alloy, zinc, scrap, energy, and similar charges should tie back to the contract, price sheet, or agreed adjustment method before payment.
• Short, rejected, or damaged material: If the receiver rejected bundles, noted damage, or booked a short receipt, hold the affected lines until there is a credit note, supplier correction, receiver confirmation, or documented acceptance decision.

The useful split is material exception versus timing exception. If the material has not arrived, the supplier may have billed early and the invoice should not be released as if the receipt exists. If the material did arrive but the ERP receipt is not posted yet, AP needs receiver confirmation or a receiving update. If the receipt is posted but the invoice is missing, the issue belongs closer to manufacturing GRNI reconciliation than to a supplier dispute.

Before invoices arrive, define which source controls each disputed field and which reason codes AP uses for held lines. The PO supports agreed material and commercial terms. The receiving record supports what was booked into inventory. Delivery paperwork or scale tickets support what arrived. The contract or price sheet supports surcharge logic. Held lines should use consistent reasons such as missing receipt, partial shipment, spec mismatch, weight variance, unsupported surcharge, duplicate reference, damaged or rejected material, freight duplication, or supplier correction pending.

The broader operating discipline overlaps with wholesale distribution invoice processing, but steel matching needs its own control layer because the payable amount depends on material identity, received weight, partial delivery status, and surcharge support. Standardize those checks before payment, and the team has a defensible basis for approving clean invoices while holding the lines that need supplier, receiving, or procurement action.