CASE STUDY 02 · Purchasing and inventory

Make purchasing exceptions easy to explain

A purchase order, a delivery and an invoice can disagree. Without a clear exception path, teams may approve an invoice before they understand whether the quantities and price match.

Independent, AI-assisted portfolio project · Fictional data · Demonstration, not a client delivery

STEP 1Purchase order
STEP 2Receive goods
STEP 3Compare invoice
STEP 4Match or hold

My contribution

I shaped this portfolio exercise around a business problem, explicit acceptance rules and reviewable exceptions. The implementation and documentation were developed with AI assistance. It demonstrates an approach; it is not a record of a former employer's delivery.

The approach

The lab follows one synthetic purchase order through partial receipts and invoice matching. It keeps quantities and exception reasons visible so a business reviewer can explain the decision.

Decisions and tradeoffs

Support partial deliveries

The process reflects goods arriving in more than one receipt.

Reject invalid or repeated receipts

Whole-unit validation, unique receipt identifiers and overreceipt checks protect the sample inventory state.

Explain the hold

Quantity and unit-price differences produce visible review reasons instead of a generic failure.

What to try

These scenarios are acceptance checks you can inspect in the demo and its tests.

ScenarioExpected behavior
Receive part of the orderReceived and remaining quantities update consistently.
Repeat a receipt identifierNo second inventory movement is recorded.
Receive more than orderedThe excess receipt is rejected.
Invoice quantity or price differsThe invoice shows a hold reason for review.

What you can inspect

An interactive receiving and matching exercise, validation rules, automated tests and downloadable audit and executive summaries.

What this demonstrates

A working example with explicit rules and repeatable checks. No client outcome, cost saving or production performance claim is inferred from this exercise.

Moving toward a real implementation

For a real engagement: map purchasing roles, approval thresholds, units, taxes and currencies; agree exception owners; validate with finance and warehouse users before ERP configuration or integration.

Resumen en español

Este caso explica entregas parciales y diferencias entre pedido, recepción y factura. Las excepciones quedan claras para revisión. No registra movimientos en un ERP real ni ejecuta pagos.