Your suppliers confirm. Catalog checks.
The agent reads every supplier order acknowledgment and checks it against your purchase order, line by line. Your team sees only what differs, and the date the supplier confirmed reaches your ERP.
How it works
An acknowledgment arrives. The agent reads it, compares it, shows you the difference.
Your suppliers answer your purchase orders in their own format: a later date, a price up 5%, a line pushed back. Left uncontested for 48 hours, the acknowledgment usually counts as accepted.
The agent checks every acknowledgment against its purchase order, line by line.
As soon as an acknowledgment lands in the purchasing mailbox, the agent finds the purchase order, compares every line (quantity, unit price, delivery date) and flags what differs. Unreadable acknowledgments, or ones with no reference, go to action required: you pick the purchase order from a list of candidates.
- Quantities, prices and dates compared line by line
- Every acknowledgment tagged in the mailbox: received, to check, in progress
- What your team has already archived, the agent skips: no double handling
Reconciliation #58 · Cartonnages DelmasAction requiredPDF received 21/10 at 08:42, in the purchasing mailbox
Compared with the purchase order
Your team decides. The ERP gets the true date.
The agent prepares, a person decides. A quantity or a date the supplier confirmed is applied in one click and reaches the ERP. A price change goes to the buyer: the agent never changes a price and never answers the supplier on its own.
- One decision per difference, the rest of the purchase order stays as it is
- Price changes routed to the buyer, never written to the ERP
- A reply to the supplier drafted, sent by your team
Reconciliation #58 · line 2Delivery difference
Purchase order: 13/11 · Acknowledgment: 27/11 · +14 d
Features
Three things the agent does very well.
PDF · email · XLS
Every acknowledgment read
PDF, email body or spreadsheet, in the supplier’s own layout: the agent matches each one to its purchase order. When the reference is missing, it proposes the candidates and a person picks.
Differences only
Differences, nothing else
A later date, a higher price, a shorter quantity, a line pushed back: your team sees only what differs, and decides in one click.
ERP
The true date in the ERP
Once a difference is accepted, the date the supplier confirmed is written to the ERP. Planning, and the dates you promise customers, start from there.
Questions
Frequently asked questions
Do we need to connect our ERP to start?
No. The agent starts on the purchasing mailbox: it reads the purchase orders sent and the acknowledgments received, matches them and tags every confirmation. The ERP connection comes when you are ready, to write the confirmed dates: via API, webhook or flat files, with SAP, Sage, Cegid, Microsoft Dynamics, Sellsy, EBP, Divalto, AS/400 and several industry-specific or in-house ERPs.
A supplier raises a price. What happens?
The agent flags the difference on the line and sends it to the buyer. It never changes a price in the ERP and never answers the supplier on its own: the buyer accepts, disputes or renegotiates, within the 48 hours that count.
Our team already handles acknowledgments by hand. Will this get in the way?
No. The agent runs alongside your team from day one, on the same mailbox. What they archive, it skips. What it has checked carries a tag everyone can see.
What about unreadable acknowledgments, or ones with no reference?
They go to an action-required queue, with the candidate purchase orders proposed. Never a forced match.
How long does it take to go live?
The mailbox connects in a few days. The ERP integration, to write the confirmed dates, takes a few weeks.
Where is our data hosted?
Exclusively in the European Union, with no transfer outside the EEA. TLS 1.2+ in transit and AES-256 at rest, databases isolated per customer. Your emails never train AI models: that is a contractual constraint imposed on our providers. A DPA is available for signature.
Savings simulator
What does checking your acknowledgments cost you?
Six answers are enough to put a figure on what the agent changes for you. No contact details asked: the result updates as you answer.
Your situation
From a few hundred to several tens of thousands a month, depending on the company.
The whole team. For example, 4 people full-time make ≈ 140 h.
Filled in as an example: an industrial distributor receiving 5,000 acknowledgments a month, with 4 people checking them, about 140 hours a week. Replace with your own figures.
What it comes to over a year
- ≈ 60,000 acknowledgments a year, ≈ 300,000 lines to check.
- Our standards give ≈ 130 h a week to check everything, close to your figure.
Your team checks everything. It takes 140 h a week.
With Catalog, it only handles the flagged lines.
≈ 3,400 hfreed up a year≈ 77 h a week
≈ €119ka yearBetween €100k and €140k
Estimate with the ERP integration: Catalog writes the confirmed dates and quantities to your ERP.
Hours freed up
≈ 3,400 h≈ €110kChecking and ERP updates for 60,000 acknowledgments and 30,000 backorder lines: 6,160 h a year today, 2,786 h with Catalog.
Compliance disputes avoided
≈ 7.5 disputes avoided a year≈ €9kAcross 30,000 lines with a requirement, a certification that changes under the same item code often gets past a manual read. Catalog compares every line (configured properties).
Your week
Your week today and with Catalog
- Checking acknowledgments
- Backorders
The same checks, in 63 h a week instead of 140 h. The team only looks at the flagged lines.
See the agent on your own acknowledgments.
Thirty minutes on your purchase orders and your suppliers’ confirmations: we rerun this calculation with your volumes. No ERP access, no commitment.
Your ≈ 3,400 h a year can be checked on your own acknowledgments.