How does multilingual invoice processing work with Queli Makra?

Queli Makra reads invoices and operational documents from email, PDFs, scans, or a shared folder, extracts and checks the fields that matter, and prepares a structured ERP draft with exceptions attached. A finance reviewer remains responsible for the final treatment.

From a foreign PDF to a reviewable record

The process begins with the document as it arrives, not with a promise that every supplier will use one template. Makra reads the invoice, identifies the relevant business fields, and checks them against the configured rules and available context. The output can include the supplier, invoice number, dates, line items, amounts, tax information, classifications, and any unresolved issue that needs a person.

The original file stays connected to the extracted record. A reviewer can inspect the evidence behind a field instead of opening a separate trail of email, PDF, and spreadsheet by hand. If a field is missing, ambiguous, or outside the agreed rule set, the workflow surfaces an exception rather than writing a confident-looking guess into the destination system.

An automotive workflow in daily use

One automotive parts company receives invoices from suppliers across the European Union. The documents arrive in German, French, Italian, Czech, Polish and English, often with different layouts and supplier-specific rules. Manual entry took four to five minutes per invoice.

Makra now reads each document, applies the rule for that supplier and prepares the ERP draft with the original PDF attached. The finance team sees the extracted fields, line items and any exception that needs attention. The company reports a 98% reduction in processing time, with the prepared workflow taking about five seconds per invoice.

The result is a reviewed ERP draft, not an invisible posting. Finance still decides how to treat an exception, while the repeated reading and retyping happen before the document reaches the reviewer.

Setting up the workflow

Queli and the customer agree the ERP field schema, source systems, permissions, review role and exception rules. They also decide the model provider or customer-hosted option, data region and retention policy for that workload.

The first test uses the customer’s own invoice mix. It measures preparation time, corrections and exceptions against the existing process. Supplier rules can then be added as the system encounters real documents, so the workflow improves around the company’s invoices instead of forcing every supplier into one template.