Skip to content
Invogi Docs

What Invogi does

Invogi checks supplier invoices before they are paid. It looks for duplicates, changed bank details, unusual amounts, purchase-order mismatches and e-invoicing errors, then gives each invoice a decision your AP team can act on.

Invogi is not an accounting system. It sits next to the one you already use: invoices come in from uploads, email, your ERP or the API, and the result goes back to the people who approve payments.

How an invoice is checked

Section titled “How an invoice is checked”
  1. Intake. An invoice arrives as a PDF, an image, a structured e-invoice (UBL, CII, Factur-X/ZUGFeRD, XRechnung, KSeF), a spreadsheet row, an ERP bill or an API call.
  2. Extraction. Invogi reads the supplier, invoice number, dates, amounts, currency, bank details, purchase order and line items into one standard invoice format.
  3. Checks. The invoice is compared with your supplier, invoice, payment and purchase-order history. Structured e-invoices are also validated against their technical rule set.
  4. Decision. Every check that fires creates a finding with its evidence. The findings decide the invoice’s outcome: PASS, REVIEW or BLOCK.
  5. Review. Your team works through open findings, marks each one as a confirmed issue, a false positive or an accepted risk, and pays the invoice or stops it.

Decisions are rules, not guesses

Section titled “Decisions are rules, not guesses”

Invogi uses AI only to read documents. Whether an invoice passes, needs review or is blocked is decided by fixed rules and your workspace’s policy, and every decision records the rule and policy versions used to make it, so the same invoice always gets the same answer and you can show an auditor why.

See Decisions and Finding types.

Where to go next

Section titled “Where to go next”