Use case

Automatic document reading with AI

Invoices, freight bills (CT-e), contracts and receipts arrive by email or upload, and the AI extracts the data, checks it and posts it to the ERP. The team only reviews what the AI flags as doubtful.

The scenario

How it works today, without automation.

Dozens of PDFs arrive by email every day. Someone opens them one by one, copies the tax ID, amount, due date and items into the ERP, and checks again at month-end, when the books don't add up.

  1. 01Hours every week spent typing what is already written in the document.
  2. 02A typo in an amount or due date turns into a fine, interest or a wrong charge.
  3. 03Documents sit in the inbox waiting for someone to have time.
  4. 04Nobody knows for sure which documents have already been posted.
How it works with AI

The flow, step by step.

  1. 01

    Document arrives

    By email, upload, shared folder or WhatsApp.

  2. 02

    AI reads and extracts

    Identifies the document type and extracts the fields: tax ID, amounts, dates, items.

  3. 03

    Checks the data

    Compares it with the order, the supplier and the company's rules.

  4. 04

    Posts to the ERP

    Creates the entry, the payable or the right record in the system.

  5. 05

    A person reviews exceptions

    Only what doesn't match goes to review, with the reason shown.

Sample proposal

What would be delivered.

Deliverables

  • Reading of invoices, freight bills (CT-e), contracts, bank slips and receipts.
  • Checking rules against orders, suppliers and amounts.
  • Automatic posting to the ERP or finance system.
  • Review queue for exceptions and a history of every document read.
// connected systems
  • Email
  • Google Drive or OneDrive
  • ERP
  • Finance
  • SEFAZ (NF-e and CT-e XML)

Stages

  1. Discovery

    Document types, required fields and checking rules.

    2 to 3 days
  2. Reading and rules

    Extraction models, checks and ERP integration.

    2 to 3 weeks
  3. Testing with real documents

    We run documents from recent months and measure accuracy.

    1 week
  4. Go-live and tuning

    Production launch with the review queue active.

    1 week
Typical timeline
3 to 5 weeks

The final timeline is set in the proposal, after discovery.

Frequently asked questions

Questions about this use case.

Can the AI read scanned documents or photos?

Yes. Digital PDFs, scanned documents and legible photos. When the invoice XML exists, it is used first because it is more accurate.

What if the AI gets an amount wrong?

The checking rules compare the document with the order and the supplier. Anything that doesn't match is not posted: it goes to a person for review.

Does it work with my ERP?

It works with ERPs that have an API or file import. During discovery we confirm how to post to your system.

Which documents can be automated?

Invoices, freight bills (CT-e), bank slips, payment receipts, contracts, purchase orders and other documents with a similar structure. Freight bills can also be checked against the freight table and quote before posting.

Want to see how it would work in your company?

You explain the problem. We build the solution. A straight answer, no generic proposal.