Every invoice is a different layout
Hundreds of suppliers, each with its own template, its own stamp and its own idea of where the total goes. Template-based capture breaks every time a supplier changes theirs.
Arakma reads every invoice the way your AP clerk would: supplier, ICE and VAT numbers, totals, line items. It matches them against the purchase order and the delivery note, and sends only the real exceptions to a person.
For finance teams, shared service centres and outsourced bookkeeping firms.
Where the time goes today
Hundreds of suppliers, each with its own template, its own stamp and its own idea of where the total goes. Template-based capture breaks every time a supplier changes theirs.
Someone opens the PO, the delivery note and the invoice side by side and checks quantities line by line. It is slow, and it is exactly where overbilling slips through.
Invoices queue until there is time to key them, late-payment terms are missed, and early-payment discounts expire before the invoice is even in the system.
How Arakma handles it
The same four steps for every document, set up with your fields, your checks and your thresholds during a pilot on your own files.
A shared mailbox, a scanner, a supplier portal export or a phone photo from a branch. PDF, image or Word, one page or forty.
Supplier, ICE, IF and VAT numbers, dates, currency, totals and every line item, in the names your ERP expects. Each field gets its own confidence score.
Lines are matched against the purchase order and the goods receipt. Totals are recomputed, VAT is checked against the rate, and changed bank details are flagged.
Anything below your threshold, or any match that fails, goes to a reviewer with the invoice open beside the field. Everything else posts directly.
What goes in
Scanned, photographed or born digital, in Arabic, French or English. If yours is not listed, it is not a special case: describe the fields and we read it.
Where it goes
Excel, CSV or JSON, laid out to match your import template. A direct connection is built when your system allows one.
What changes
Your team looks at the invoices that actually need a decision. The clean ones never reach a queue.
Quantity, price and VAT discrepancies are found before payment, not at the audit, and each one is logged with who resolved it.
Invoices are in the ledger the day they arrive, so payment terms and early-payment discounts are there to use.
Questions
Anything else, including security questionnaires, we answer before a pilot. How we handle data.
No. You define the fields once, for all invoices. A new supplier or a changed layout needs no setup on your side.
Yes. Arabic, French and English are read natively, including invoices that mix two of them on one page, and local identifiers such as ICE, IF and TRN are first-class fields.
The invoice is held with the failing check named, for example a quantity that differs from the PO. A reviewer resolves it, and the resolution is recorded against the invoice.
We run them through Arakma with your fields and show you the output, scores and review decisions in a call. If it works on yours, we scope a pilot.
Or write to contact@arakma.com. We reply within one business day.