From invoice to ERP, with no typing.

It arrives as a PDF, a photo, an email or a WhatsApp message. The agent reads it, matches it to the purchase order and records it in under 2 minutes.

No typing · No double entry · No transcription errors

It comes in however it reaches you.

Nobody has to ask the supplier to change the way they invoice.

One document, four seconds of human work.

You forward the invoice. The agent does the rest inside your system.

What it reads from every document.

The five groups of data the ERP needs in order to record the invoice without anyone typing.

Every invoice, checked against its supporting document.

Depending on how your company buys, the invoice is checked against the purchase order — the nota de pedido already loaded in the ERP — or against the remito for the goods received. And before confirming anything, it compares line by line.

Ten reasons an invoice is not recorded on its own.

When any of these checks fires, the invoice does not reach the ERP: it is held for review, with the reason written out and the document in view, and a person decides. Each check is switched on or off per company.

Three controls that stop depending on memory.

What happens when something does not add up.

The agent does not complete a record with data it did not read. When an exception comes up, it hands the whole case over.

What happens if the invoice has no purchase order?

The agent does not record it on its own. It is held for review, with the alert and the document in view, and handed to the person in charge so they can decide how to post it.

And if an item on the invoice is not in your catalog?

It depends on how you configure it. If you enabled automatic item creation, it creates the item with its description, its price, its IVA rate and its supplier. If you would rather it did not, the invoice is held for review until someone approves the new item. Either way, the code that supplier uses for it is stored in the item's record: the next invoice recognizes it on its own.

And if the document arrives unreadable?

It marks the document as not processable, replies through the same channel it arrived on and asks for it to be sent again. It never fills fields with estimated data: without a readable issue date, for example, the invoice does not reach the ERP under any circumstances.

What difference does it tolerate?

Rounding does not stop a document from being recorded: price differences against the document are tolerated up to a small margin, and above that the invoice is not recorded on its own. What you do define is which check stops a document: each alert — price, quantity, shortages, duplicates, payment terms — is switched on or off per company.

Can everything be reviewed before it reaches the ERP?

Yes. You can leave the agent in proposal mode: it prepares the complete record and holds it until a person confirms it.

Can it be tested without touching the ERP?

Yes, and that is how every implementation starts. In test mode the document goes through the whole process — reading, item identification, matching and validation — and at the end everything is rolled back: nothing is written. You get the log of every simulation so you can review what would have happened.

Where do the original documents end up?

The original file stays attached to the record in your management system, so the document and its entry are always together.

What connects to this.

Bring one of your own invoices to the meeting.

We process it with you live, against your own posting rules, and show you how the record ends up in your system.