Invoice processing overview
Brikly's invoice processing engine takes the tedium out of cost management. Instead of manually keying line items from every delivery, you upload (or capture) an invoice and let Brikly do the heavy lifting - extracting data, matching ingredients, and updating your costs automatically.
The end-to-end flow
Every invoice follows the same four-stage pipeline:
- Ingest - Drag-and-drop a file into Brikly, drag it from a supplier portal into the Chrome extension, forward it to your Invoice Inbox email address, or snap a photo with Quick Capture.
- AI extraction - Brikly's AI reads the document and pulls out the supplier name, invoice number, date, line items, quantities, prices, and VAT.
- Matching - Extracted line items are matched to the ingredients already in your system. The supplier is identified and linked as well.
- Price update - Matched prices flow through to your recipes and dishes as soon as the invoice is processed, so your costings stay current. There is no separate confirm step to hold them back, so if an invoice was read wrongly, correct its lines or delete it rather than leaving it unreviewed. A line's price waits while Brikly still has a question about it (a pack size, for example), and an invoice older than the price already on file never replaces it.
Ingest ──▶ AI Extraction ──▶ Matching ──▶ Price Update
(upload, (supplier, (ingredients (recipes &
extension, line items, & supplier) dishes
inbox, VAT, totals) updated)
Quick Capture)
Invoices that did not come from a manual upload show a small Email, Gmail, Extension or Quick Capture badge in the invoice list, so you can see where each one came from.
Not every invoice is a food delivery. During extraction, Brikly also classifies the document - energy bills, service charges, equipment purchases, rent, and other non-food invoices skip the matching stage and are marked as expense invoices instead, ready to submit to your accounting platform. Each expense bill is also compared with earlier bills on the same supplier account, so a changed rate or a new charge shows on the invoice, and the larger changes on Home too. Supplier credit notes are recognised as their own document type too - they reduce what you owe and net off your supplier spend, but never touch your ingredient prices, costings, or stock.
Archiving completed invoices
When you are done with a completed invoice, click the archive button on its row in the Completed tab to move it to the Archived tab. Archiving only tidies the list:
- An archived invoice still counts in your spend, supplier figures and the negotiation brief.
- It stays locked like a completed invoice: no new lines, no change to the invoice number, and no re-reading, reclassifying or recategorising until you restore it.
- The restore button on its row in the Archived tab brings it back to Completed.
Only completed invoices can be archived, and not while Brikly is re-reading one. Owners, admins and members can archive and restore; viewers see the Archived tab without the buttons.
If Brikly can't read an invoice
While Brikly reads an invoice, the list shows AI processing.... If it hits a temporary problem, it keeps showing that while Brikly tries again, and only shows AI failed if the retries fail too. An AI failed invoice keeps its file: open it and click Re-extract to read it again. If reading stopped part way through (for example during an update), the invoice says "Processing stalled before reading finished. Tap Re-extract to read it again."
Re-extract reads the file again from scratch. Owners, admins and members can use it. It is greyed out on an archived invoice (restore it first) and once its bill has been sent to your accounting platform: hover over it to see why. If the new read cannot improve the invoice, because it does not recognise an invoice or finds no invoice data, Brikly keeps the data you already had and says so. If a re-read cannot start at all, the invoice is left exactly as it was and you are asked to try again in a moment.
When the invoice has matches you chose or price and size reviews you answered, Brikly asks first and says how many: "Re-running extraction will replace the current data, discard 3 confirmed matches and this invoice's recorded prices, then recalculate affected recipes. This can't be undone." After the re-read:
- Matching starts again from what other invoices taught Brikly. A re-read takes back only what this invoice's own matches taught, so a line you matched by hand on this invoice alone may need matching again.
- Skipped lines. Delivery and other charges you skipped are set aside again. A product line is set aside again only if you have also skipped it on another invoice from the same supplier. If this invoice was the only one, it comes back for review, so press Skip on it again if you still want it set aside.
- Anything a re-read adds for you is shown again in the review panel, even if you had reviewed the earlier read, see Reviewing what was added.
How it learns over time
Brikly is not a static tool. Every invoice you process teaches the system a little more about your suppliers and their products. Early on you will confirm matches manually; after a handful of invoices from the same supplier, the system handles most items automatically. Read more about this in The learning system.
Time savings
| Task | Manual approach | With Brikly |
|---|---|---|
| Key in a 30-line invoice | 8–12 minutes | ~30 seconds of review |
| Match items to ingredients | 5–10 minutes | Automatic (once trained) |
| Update recipe costings | 10+ minutes | Instant |
For a busy kitchen receiving dozens of deliveries a week, that adds up to hours saved - and far fewer transcription errors.
Supported formats
Brikly accepts the most common invoice formats:
- PDF - standard supplier invoices, statements, and credit notes.
- PNG / JPEG - photos of printed invoices or screenshots from supplier portals. GIF and WebP images are accepted too.
For the best extraction accuracy, upload the original PDF rather than a photo whenever possible. PDFs with selectable text are processed faster and with higher confidence than scanned images.
What happens next?
Explore the rest of this section to learn how each stage works in detail: