Payables Outlook for Acumatica
Every open voucher in Acumatica, by week and by vendor, with the discount date beside it and thirteen weeks of cash out against expected collections. Read from Acumatica; the paying still happens in Acumatica.
Accounts payableUpdated Oct 202620 ERPs
See it work on Acumatica.
Click through the steps. Fictional data, in Acumatica’s terms; the real thing runs on Acumatica.
Open AP, what’s due, what’s still worth paying early, what was lost. Each figure opens its vouchers.
The problem, as it happens in Acumatica.
The AP board answers one question at a time: is this invoice right? Acumatica’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 Acumatica. 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 Acumatica, 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 Acumatica 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 Acumatica.
How it connects to Acumatica.
Lunica reads Acumatica’s AP detail, vendor terms and payment history through Acumatica’s OData and REST endpoints, under a role that can only read, and the same open-item read the collections workflow uses for expected collections. Vendor terms are read as Acumatica 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 Acumatica, 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 Acumatica, as it always was.
What a week looks like.
- Every figure opens the rows behind it.
- Refresh reads Acumatica 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 Acumatica?
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 Acumatica. This page tells you what that decision costs.
Where do the collections numbers come from?
From the same read of Acumatica 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 Acumatica, 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 Acumatica again.
Can the owner see it without an Acumatica login?
Yes. The page is Lunica’s, so anyone you enrol can open it. Each person sees the same figures from the same read.
Does it need a server?
Lunica runs on one server inside your network, whether Acumatica is in the cloud or on your own server, set up and maintained by Lunica. It reads Acumatica through Acumatica’s OData and REST endpoints, under a role that can only read. There is no inbound connection from outside your network.
What does Lunica read in Acumatica?
The customer record, open items and terms, purchase orders and receipts, the stock item, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to Acumatica?
Nothing lands in Acumatica without a person. What belongs in Acumatica goes back as an Acumatica API call or import scenario where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in the files attached to the record. Lunica reads them when a workflow needs one and never writes to them.
The same workflow, on another ERP.
Payables Outlook is written for every system on the list. You’re reading the Acumatica version.
See it on your Acumatica data.
Thirty minutes. We walk the workflow on Acumatica data, then map it to yours.