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.

Administration · Document capture

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.

Book a meeting See the agent in detail

No typing · No double entry · No transcription errors

Invoice receivedInsumos Norte S.A.

Legal nameInsumos Norte S.A.
CUIT30-71234567-9
TypeFactura A
Document0003-00012456
Issued28/07/2026
Due27/08/2026
Items3 lines
Payment termsOn account · 30 days
IVA and percepciones$ 222,900
Total$ 1,284,900

Input

It comes in however it reaches you.

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

PDF
Image
Email
WhatsApp

One single process

Purchase documents

Supplier: Insumos Norte S.A.
Document: A 0003-00012456
Total: $ 1,284,900
Entry channel: PDFImageEmailWhatsApp

Fictional demo data.

PDF
The file exactly as the supplier issues it.
Image or photo
A photo taken with a phone is enough.
Email
The inbox where documents are received is processed.
WhatsApp
The document is forwarded to the agent number.

Every format enters the same process: same checks, same record, same traceability.

The process

One document, four seconds of human work.

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

Invoice receivedInsumos Norte S.A.

Legal nameInsumos Norte S.A.
CUIT30-71234567-9
TypeFactura A
Document0003-00012456
Issued28/07/2026
Due27/08/2026
Items3 lines
Payment termsOn account · 30 days
IVA and percepciones$ 222,900
Total$ 1,284,900

CUIT
Invoice no.
Items and quantities
Total

Purchase documents

Supplier: Insumos Norte S.A.
Document: A 0003-00012456
Due: 27/08/2026
Items: 3
Total: $ 1,284,900
PO: #314

The invoice received is read field by field — CUIT, document number, line items and total — and each value is dropped into the ERP row, which ends up recorded and matched to purchase order #314.Fictional demo data.

The agent does not produce an intermediate file or a spreadsheet: it writes the invoice straight into your management system.

Extraction

What it reads from every document.

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

Hover over each group to see it marked on the document.

Legal name, CUIT (the Argentine tax ID), IVA registration status and address — street, number, city and province — for both parties. The CUIT is validated against its check digit.
Sales point and number, issue date, payment due date, CAE (the AFIP electronic authorization code) and its expiry, currency and exchange rate.
Supplier's item code, description, quantity, unit of measure, unit price, discount, subtotal, IVA rate and amount, and the total for each line.
IVA (Argentine VAT) broken out by rate — 27%, 25%, 21% and 10.5% — Impuestos Internos, and every levy on its own: IVA percepciones, which are amounts collected at source, Ingresos Brutos, municipal rates, funds and trusts.
Document class and letter — Factura A, B, C or M, credit note and debit note — terms of sale and payment method, the remito, or delivery note, that the invoice references, and anything written by hand on the paper about a shortage.
With this data the agent builds the complete record: header, detail and the posting of each tax to the box it belongs in, following the rules you configured.

Invoice receivedInsumos Norte S.A.

01Legal nameInsumos Norte S.A.
01CUIT30-71234567-9
05TypeFactura A
02Document0003-00012456
02Issued28/07/2026
02Due27/08/2026
03Items3 lines
05Payment termsOn account · 30 days
04IVA and percepciones$ 222,900
04Total$ 1,284,900

Fictional demo data.

Control

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.

01
It finds the open document
Among that supplier's open purchase orders, notas de pedido and remitos, it locates the one that corresponds to the invoice received.
02
It identifies each item
It translates the code the supplier uses for the product into the item in your catalog, and stores that equivalence in the item's record for the next invoice.
03
It compares line by line
It checks the quantity invoiced against the quantity still pending delivery, and the price invoiced against the price on the document.
04
It records the invoice and marks the receipt
When everything matches, it records the invoice, links it to the document and marks it as a full or partial receipt.
05
It raises an alert if there is a difference
When something does not match, the invoice does not reach the ERP: it is held for review with the exact difference, item by item.
06
It lets you decide when there is doubt
If more than one document matches, it does not pick by elimination: it shows them with their number, their date and their items so a person can decide which one it goes against.

Comparison against PO #314 · Insumos Norte S.A.

Mockup of the comparison between the invoice and the purchase order, item by item.
Item	Quantity on PO	Quantity invoiced	Status
200 cc container	5,000	5,000	Match
500 mm stretch film	240	240	Match
70×40 self-adhesive label	2,000	2,180	Difference · +180 units

Alert raised for the purchasing team

Fictional demo data.

Alerts

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.

Price different from the one agreed

A line was invoiced above the price on the linked document. The alert names the item, the agreed price and the invoiced price.

Quantity does not match

What was invoiced exceeds what was still pending delivery on the linked document.

Goods shortage

The remito for the delivery shows a higher quantity than the invoice, or the paper carries a handwritten note that something did not arrive.

No supporting document

There is no open purchase order or remito from that supplier matching the invoice.

Several possible documents

More than one document matches and none is clearly the right one: recording it against the wrong one would consume an order that is still open.

Supplier not registered

The CUIT that issued the invoice does not exist as a supplier in the ERP.

Unidentified item

One or more lines could not be matched to any item in the catalog, or the new item could not be created.

Duplicate document

There is already an invoice recorded with that same sales point and number.

Payment terms not stated

The invoice does not state whether it is cash or on account, and that determines how it is posted.

The invoice does not add up

Subtotal, IVA amounts and the remaining items do not add up to the printed total, not even after re-reading the document.

Nothing is left hanging: every reading is logged with how it ended — recorded, under review, not recorded or failed — and for what reason.

Result

Three controls that stop depending on memory.

No duplicate or misposted invoices

Every document is recorded once, posted the way your rules say it should be.

Receiving checked against the invoice

What arrived is checked against what was invoiced, and the difference is documented.

Full traceability on every purchase

From the purchase order to the recorded invoice, with the history of what was done and when.

Every action the agent takes is audited inside the platform: which document, which rule was applied and at what moment.

Limits

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.

See security and data

Keep exploring

What connects to this.

Administración

Agente administrativo

What it reads and what it writes in your ERP, price updates, alerts and queries over WhatsApp.

Soluciones

Compras

The purchase orders the agent later checks each invoice against, generated and controlled on their own.

Cómo funciona

Integración con tus sistemas

How we connect the agent to your ERP and what happens if the connection does not exist yet.

Next step

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.

Agendar reunión Chat on WhatsApp

Victoria AI · Córdoba, Argentina

From invoice to ERP, with no typing.

It comes in however it reaches you.

One document, four seconds of human work.

What it reads from every document.

01Issuer and recipient

02Document identification

03Line by line detail

04Taxes and percepciones

05Terms and supporting documents

Every invoice, checked against its supporting document.

It finds the open document

It identifies each item

It compares line by line

It records the invoice and marks the receipt

It raises an alert if there is a difference

It lets you decide when there is doubt

Comparison against PO #314 · Insumos Norte S.A.

Ten reasons an invoice is not recorded on its own.

Price different from the one agreed

Quantity does not match

Goods shortage

No supporting document

Several possible documents

Supplier not registered

Unidentified item

Duplicate document

Payment terms not stated

The invoice does not add up

Three controls that stop depending on memory.

No duplicate or misposted invoices

Receiving checked against the invoice

Full traceability on every purchase

What happens when something does not add up.

What happens if the invoice has no purchase order?

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

And if the document arrives unreadable?

What difference does it tolerate?

Can everything be reviewed before it reaches the ERP?

Can it be tested without touching the ERP?

Where do the original documents end up?

What connects to this.

Agente administrativo

Compras

Integración con tus sistemas

Bring one of your own invoices to the meeting.