Accounts payable for building-supply dealers.
Lunica reads what lands in the AP mailbox, matches it to your ERP, and leaves your team the exceptions.
Accounts payableUpdated Oct 202620 ERPs
See it work.
Click through the steps. Fictional data; the real thing runs on your ERP.
Read overnight: vendor, invoice number, PO, lines, total.
The problem.
Vendor invoices arrive as PDFs, photos and the odd spreadsheet statement, and the AP desk retypes them, finds the PO in your ERP, finds the receipt, and pulls the signed delivery ticket from your document archive to staple behind. Most of them match. All of them take the same time.
The ones that don’t match are the ones that matter, and they’re buried in the pile: a quantity short on the receipt, a price off the PO, a statement line nobody can place. By the time someone emails the vendor, the discount date has passed.
How it works.
- 1
Documents come in overnight
One pass a night reads what landed in the AP mailbox: invoices, statements and credit memos, as PDFs, photos or spreadsheets. EDI invoices from your buying group’s marketplace come in the same way.
- 2
Each one is matched to your ERP
Vendor, PO, receipt and amounts, line by line against what your ERP has. Any figure your ERP can’t confirm is read twice, by two different models, and only agreement counts. A disagreement waits for a person.
- 3
The board sorts the work
Perfect matches sit in Ready to pay. Discrepancies land in Issue identified with the difference spelled out. Vendor questions are drafted; a person sends them, and the reply lands on the card.
- 4
Your team enters what’s right
Matched invoices go into your ERP the way they always have, as an import file where your ERP takes one. The signed delivery ticket is appended behind the invoice as one PDF, and a person imports or keys the voucher.
How it connects to your ERP.
Lunica reads your ERP’s open purchase orders, receipts, vendor file and AP subledger through its database or data warehouse, under an account that can only read, and the AP mailbox and scan share for the documents themselves. Each document is matched to its PO and receipt line by line. Figures your ERP can confirm are trusted; figures it can’t are read by two models and accepted only when they agree. Marketplace EDI invoices are fetched as data and matched the same way.
Nothing is posted to your ERP on its own. A matched invoice goes back as an import file where your ERP takes one, imported or keyed by your team, and your ERP matches it to the receipt as it always has. Vendor questions are drafts until a person sends them. The signed delivery ticket from your document archive is appended behind the invoice as one PDF, the file the AP desk used to assemble by hand.
What a week looks like.
- Clean invoices stop costing time.
- Every exception says what’s wrong and by how much.
- Delivery tickets attach themselves.
- Statements reconcile line by line against your ERP’s subledger.
Questions
Does Lunica post vouchers to your ERP?
No. The board tells you what’s right. A matched invoice becomes an import file where your ERP takes one; your team imports or keys it, and nothing lands in your ERP without a person.
What about EDI invoices?
Marketplace EDI invoices are fetched as structured data, never read by a model, and matched to your ERP by invoice number and PO.
Do vendor emails go out automatically?
Never. Vendor questions are drafts until a person sends them.
How accurate is the reading?
Figures your ERP can confirm are trusted. Figures it can’t are read by two independent models and only agreement is accepted; anything else waits in Issue identified for a one-click pick.
What about expense invoices with no PO?
Vendors you tag as expense skip the PO match and go straight to coding review.
What happens to the scanned delivery tickets?
They keep flowing into your document archive as before. Lunica reads them and pairs each ticket with its invoice; the archive keeps working exactly as it did.
Available for.
Each version is written in that system’s own terms: its screens, its files, its codes.
Own your AI. Own your software.
Thirty minutes with the people who build it. Bring your ERP.