Skip to content

Rohlik Group · Invoice reconciliation

How Rohlik protected €3.5M by fixing inbound invoice errors at the source.

€3.5M/yr

protected across revenue and margin

18 → 3.4 hrs/day

disponent workload compressed

The challenge

The invoice said the goods arrived. They hadn't.

At Rohlik scale, a supplier delivery note that does not match the PO, goods received, or invoice is not a clerical issue. It blocks inbound, ties up working capital, creates fresh-category waste risk, and can leave AP clearing invoices for goods that never physically arrived. Across five markets, the expensive part was not just finding the mismatch. It was tracing the root cause and fixing the data so the same error did not come back on the next delivery.

How DUVO improved the workflow

From signal to verified outcome.

Each step runs autonomously. Every action is logged, traceable, and reviewable.

01

Matches and Classifies

Duvo reads each supplier DESADV against the PO and goods-received record, then classifies the delta across unit of measure, missing fields, wrong item IDs, quantity, or price.

02

Traces Root Cause

The agent works out whether the break came from supplier data, the PO, or Rohlik master data so the fix lands in the right place.

03

Resolves Clean Cases

Clear mismatches move through automatically. Large or ambiguous cases route to a human queue with the specific delta already highlighted.

04

Builds Dispute Evidence

When the supplier caused the issue, Duvo assembles the DESADV, PO, receiving record, photos, and timestamps into a defensible dispute trail.

05

Writes Master Data Back

When master data caused the break, Duvo writes the correction back at source so the next delivery does not repeat the same error.

06

Logs the Audit Trail

Every resolution keeps the source records, rationale, timestamp, and write-back visible for finance, supply chain, and supplier conversations.

The difference

Before and after DUVO.

Before

  • Inbound mismatches handled one exception at a time
  • Master-data errors patched in-flight, then repeated
  • Supplier disputes rebuilt manually from documents and receiving records
  • AP risked clearing invoices for goods not physically received

After DUVO

  • DESADV, PO, goods received, and invoices checked continuously
  • Master-data corrections written back at source
  • Supplier disputes packaged with source-linked evidence
  • High-value mismatches routed to humans with the delta already isolated

Systems involved

SAPSupplier EDI/DESADVInternal supply-chain platformsMaster dataReceiving records

The difference DUVO makes

  • €2.1M per year of revenue protected
  • €1.4M per year of margin protected
  • €1M phantom-inbound incident caught before the mistake moved further
  • Disponent workload compressed from 18 to 3.4 hours per day
  • Live across all five Rohlik markets
  • 100% source-linked audit trail for supplier disputes and internal review

Quote

Without this, that's €1M of goods inbounded that aren't physically here.

Joshua Balazs

Rohlik Group

See it in your operation

Start with one process. See it run.

Pick the workflow that keeps slipping. We'll show you what changes when it actually runs.