What’s owed, what’s worth paying early, thirteen weeks out.
Lunica turns your ERP’s open payables into the page the controller carries around all week.
Accounts payableUpdated Oct 202620 ERPs
See it work.
Click through the steps. Fictional data; the real thing runs on your ERP.
Open AP, what’s due, what’s still worth paying early, what was lost. Each figure opens its vouchers.
The problem.
The AP board answers one question at a time: is this invoice right? Your ERP’s open AP report answers another: what’s due. Nobody answers the ones the controller carries around all week. What is owed and when. Which discount dates are still worth money. What was lost last month and why. Whether what’s coming in covers what’s going out.
Those answers exist in your ERP. Getting them means exporting the open AP, pivoting by due date, remembering which vendors give one percent by the tenth, and doing it again next week.
How it works.
- 1
Open AP, by week
Every open voucher from your ERP, laid out by when it’s due, by vendor, with the discount date beside it.
- 2
Discounts still worth taking
Which invoices still carry an early-pay discount, what it’s worth, and the day it expires.
- 3
What was lost, and why
Discounts missed last month, by vendor, with the reason: paid late, paid on time to the wrong date, never on the terms you thought your ERP had.
- 4
Thirteen weeks of cash
Payables due against expected collections, week by week, with the controller’s own liquidity figure as the one thing the page lets you type. Paying is still done in your ERP.
How it connects to your ERP.
Lunica reads your ERP’s AP detail, vendor terms and payment history through its database or data warehouse, under an account that can only read, and the same open-item read the collections workflow uses for expected collections. Vendor terms are read as your ERP has them, so a vendor on one percent by the twentieth of the following month is tracked to that date, not to a generic net.
Nothing is written to your ERP, and nothing is paid, approved or sent from the page on its own. It reads and organises; the one thing it stores is the controller’s own liquidity figure, on the Lunica server. Which vendors get paid this week is decided and keyed by your team in your ERP, as it always was.
What a week looks like.
- Every figure opens the rows behind it.
- Refresh reads your ERP now, not last night.
- Any table exports to CSV for the people who still want the spreadsheet.
- Benchmarks are labelled as benchmarks.
Questions
Does it write anything to your ERP?
No. It reads and organises. The one thing it stores is the controller’s liquidity figure, on the Lunica server.
Can it pay vendors or approve payments?
No. The team decides what to pay in your ERP. This page tells you what that decision costs.
Where do the collections numbers come from?
From the same read of your ERP as the collections workflow: open items aged on each invoice’s own terms.
Does it see vendors paid by check?
Yes. Payment history is read from your ERP, so paid late and paid to the wrong date both show up with the discount they cost.
How current is it?
As of the last read, shown on the page. Refresh reads your ERP again.
Can the owner see it without an your ERP login?
Yes. The page is Lunica’s, so anyone you enrol can open it. Each person sees the same figures from the same read.
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.