Case studies

Case studies

Real processes we've automated that are running in production, described by industry, process and country.

Cases are anonymous for confidentiality. Company names are published only with authorization. Impact figures are reference estimates derived from each automated process.

Automated flow
Purchase order by email
AI extraction
Validation and unit conversion
Exceptions with their cause
Order created in SAP

Consumer goods

Customer order entry

Context
A consumer goods company that receives its customers' purchase orders by email, each customer with its own format.
Before
Every order was keyed into SAP by hand. Every material, quantity or price error was paid for later, in shipping and billing.
Solution implemented
The automation receives the document from the channel where it arrives, extracts the data with AI without relying on fixed templates, handles the conversion between units and cases, and creates the order in SAP.
Exceptions and controls
Customer, material, price and quantity are validated against master data before the order is created. Whatever doesn't validate is set aside with its cause in an actionable report, without holding up the rest of the batch.
Result
Roughly 90% less operating time per order, with fewer entry errors and a shorter Order-to-Cash cycle.

Case implemented in production. Impact figures are reference estimates derived from the automated process and vary with volume.

See Sales and order management
Automated flow
Pending DUS in the portal
Settlement PDF reading
Matching with open DUS
Conversion date in SAP
Mismatch stops the submission
IVV filed in the portal

Foreign trade · Chile

Export settlement: DUS and IVV

Context
An export operation in Chile that must close its DUS (Documento Único de Salida, the export declaration) and file the IVV (Informe de Variación del Valor, the value variation report) with Chilean Customs.
Before
Closing required matching SAP, the settlement PDFs and the Customs portal by hand, document by document. Volume was concentrated in a few days, and a mistyped value went straight into the declaration.
Solution implemented
The automation detects pending DUS in the portal, extracts the currency, period and transport from the documents, reconciles that information with the open DUS, sets the conversion date in SAP using the Chilean business-day calendar logic, and downloads the valued report.
Exceptions and controls
It compares the settled return value against the gross sale value, and only then files the IVV in the portal. If it detects a difference, it stops that filing, logs the cause and moves on to the other DUS.
Result
From about 12 manual minutes per DUS to under 1 unattended minute, with values traveling from SAP to the portal without passing through a keyboard, and a report per DUS with its status: processed, pending or error.

Case implemented in production. Impact figures are reference estimates derived from the automated process and vary with DUS volume.

This case responds to Chile's regulations and portal. We don't offer it as a product that installs the same way in any market: what carries over is the ability to automate complex customs processes that combine an ERP, unstructured documents and portals with no API.

See Logistics and foreign trade

Let's talk about which processes we can automate at your company

You don't need a fully defined project. Once we understand how the process works today, we can tell you whether it can be automated and where to start.

Let's talk about your process

Or email us at [email protected]