Live
Mei checks every supplier invoice against your purchase order and against what your warehouse actually took in. Short deliveries and price differences surface line by line, while you can still do something about them.
Built for distributors, wholesalers, and food suppliers taking deliveries every day
THE LEAK
The office matches the invoice to the purchase order. The signed delivery order that says two cartons short is in a folder in the warehouse. The short delivery gets paid.
A line comes in above the agreed price. On a forty-line invoice with payment due, nobody is comparing unit prices back to the purchase order, so the increase sticks.
Weeks of delivery orders, purchase orders and invoices reconciled by hand, chasing credit notes for shortages your supplier has long since forgotten.
FEATURES
Your team confirms what arrived against the open purchase order in the FlowGo receiving app, at the loading bay, while the driver is still there.
Mei reads the invoice line by line and maps each one to your item codes, however the supplier words it. What she can't map is flagged, never guessed.
All three quantities on one row, with PO price against invoice price. Matched lines are marked matched, so a clean invoice takes seconds to approve.
Short deliveries, over-deliveries, unmapped items and prices above the agreed PO price are flagged on the line, with the difference stated and a resolve action beside it.
Deliveries against the same PO roll up: two drops of 20 read as 40, not two mismatches. Lines already billed on another invoice get flagged before you pay twice.
Mei prepares and flags, your team decides. On submit, the cleared invoice lands in AutoCount, SQL Account, QNE Optimum, QuickBooks, SAP, or Xero.
HOW IT WORKS
The lorry arrives and your team confirms what came in against the open purchase order, including partial drops and repeat deliveries.
When the supplier's invoice comes in, AI extracts every line and maps it to your item codes, pulling suppliers and items from your accounting system.
Ordered against received against invoiced, on quantity and on price. Lines that agree are marked matched; everything else becomes an exception.
Your team works the flagged lines, resolves what needs resolving, and submits. The cleared invoice posts to your accounting system.
Already using Lizzie for AP? Mei adds the receiving check before those invoices post →
PRICING
Simple, transparent pricing per company. Inventory code AI matching is included on every plan.
AI tokens are included in every plan. No metered AI usage fees, no surprise token bill at the end of the month — your document quota is the only thing you count.
Also available: extra AI rules characters S$40/month (1,000 more on Starter, 2,000 on Growth, 3,000 on Enterprise) • Accounting system / ERP integration S$40/month • AI customization S$470/day.
FAQS
It is the check that what you ordered, what you received, and what you were billed for all agree. Mei compares every line on quantity across the purchase order, the receiving record, and the supplier invoice, and on unit price between the purchase order and the invoice.
Hand-checking usually compares the invoice to the purchase order, because that is the document sitting in the office. The delivery order is in a file in the warehouse. Mei brings all three together automatically and checks every line, not just the totals or the lines someone has time to spot-check.
They open the purchase order that is already waiting for them and confirm what came in. There is nothing to type from scratch and no codes to remember, which is the whole reason receiving lives in an app rather than in a message thread.
The line is flagged with the difference spelled out: over-delivery, short delivery, unmapped item, or an invoice price above the purchase order price. Several deliveries against one order roll up first, so two drops of 20 read as 40 received rather than as two mismatches. You resolve the exception on the review screen, and nothing reaches your accounting system until you submit.
Plenty of orders get placed over the phone. Mei still reads and maps the invoice and shows it against what was received, so you keep the receiving check even when the paperwork started informally.
Yes. Every FlowGo plan includes the AI processing — tokens, model usage, all of it. There is no separate AI usage bill and no metered token charge on top of your subscription. Some tools advertise a lower monthly fee and then bill AI tokens separately, so the real cost lands well above the sticker price. With Mei, your monthly document quota is the only volume limit, and over-quota documents are billed at the published block rate.
Two things count: each goods received note (GRN) your team submits in the FlowGo receiving app, and each supplier invoice Mei reads. Purchase orders are never counted. So one delivery received in the app and matched against its invoice uses 2 documents of your monthly quota.
Nothing stops — Mei keeps matching your invoices. Extra documents are billed in blocks of 100: S$55 on Starter, S$45 on Growth. Enterprise over-quota rates are set in your custom agreement. If you are regularly over quota, moving to the next plan usually costs less.
AutoCount, SQL Account, QuickBooks, SAP Business One, Xero, and QNE Optimum, supporting both cloud and on-premise systems.
We treat your data as private and bank-grade security controls protect it. We will never share information with third parties without permission. FlowGo is also certified to ISO/IEC 27001:2022 for information security management.
Every week without the check is another invoice paid on trust. Mei matches every line before the payment goes out.
Cancel anytime • Works with the accounting system you already run
ISO 27001 certified