{"id":1106,"date":"2026-10-27T12:16:55","date_gmt":"2026-10-27T15:16:55","guid":{"rendered":"https:\/\/www.smartservices.com.ar\/casos-de-uso\/purchase-order-to-stock\/"},"modified":"2026-10-27T12:21:07","modified_gmt":"2026-10-27T15:21:07","slug":"purchase-order-to-stock","status":"publish","type":"use_case","link":"https:\/\/www.smartservices.com.ar\/en\/use-cases\/purchase-order-to-stock\/","title":{"rendered":"From Purchase Order to Stock Receipt"},"content":{"rendered":"
\n

In brief.<\/strong> This use case consists of assessing how to: capture invoice and delivery note, match them to the order, compare quantities and prices, record matching receipts, and separate discrepancies.<\/p>\n

\n

How it works today<\/h2>\n

Purchasing issues an order; the supplier sends an invoice; the warehouse receives goods and a delivery note. Finance compares quantities and prices before updating the ERP.<\/p>\n<\/section>\n

\n

Where time is lost<\/h2>\n

A mismatch appears after receipt: purchasing, warehouse, and finance hunt for three versions of one transaction.<\/p>\n<\/section>\n

\n

What can be automated<\/h2>\n

Capture invoice and delivery note, match them to the order, compare quantities and prices, record matching receipts, and separate discrepancies.<\/p>\n<\/section>\n

\"Possible<\/picture>
Illustrative workflow; exceptions still need review.<\/figcaption><\/figure>\n
\n

How a workflow could work<\/h2>\n

A practical flow takes inputs from the relevant sources, checks them against agreed rules, performs routine actions, and sends uncertain cases to a person.<\/p>\n<\/section>\n

\n

What still needs a person<\/h2>\n

Purchasing or warehouse staff confirm partial receipts and resolve price, quantity, or quality discrepancies.<\/p>\n<\/section>\n

\n

Systems that may be involved<\/h2>\n

Email, PDFs, purchase orders, ERP, and inventory system.<\/p>\n<\/section>\n

\n

When it is worth assessing<\/h2>\n

When receiving and invoice volume makes manual matching a bottleneck for reliable inventory updates.<\/p>\n<\/section>\n

\n

What not to assume<\/h2>\n

Integration and automatic posting depend on the data and access available in each ERP.<\/p>\n<\/section>\n

\n

How Smartservices approaches it<\/h2>\n

We map the existing process, verify data and system access, define controls and a human review point, then scope an integration or automation around the actual workflow.<\/p>\n<\/section>\n