Payables Outlook for Epicor Eagle
Every open voucher in Eagle, by week and by vendor, with the discount date beside it and thirteen weeks of cash out against expected collections. Read from Eagle; nothing written back.
Accounts payableUpdated Oct 202620 ERPs
See it work on Eagle.
Click through the steps. Fictional data, in Eagle’s terms; the real thing runs on Eagle.
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 Eagle.
Eagle knows what you owe. It just doesn’t tell you in the shape the controller needs: the open AP by week, the vouchers still inside a discount window, the ones that slipped past it last month, and whether what’s due covers what’s coming in.
So the open AP report gets exported, pivoted by due date, and someone remembers which vendors give one percent by the tenth and which by the twentieth. Next week it gets done again.
How it works.
- 1
Open AP, by week
Every open voucher from Eagle, 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 Eagle 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 Eagle.
How it connects to Eagle.
Lunica reads Eagle’s AP detail, vendor terms and check history through the Eagle data warehouse, read-only, and the same open-item read the collections workflow uses for expected collections. Terms codes are read as Eagle 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 Eagle, and nothing is worded as if it were. The page reads and organises. The one thing it stores is the controller’s own available-liquidity figure, on the Lunica server. Paying is still done in Eagle.
What a week looks like.
- Open AP by week, every figure a door to its vouchers.
- Discounts still capturable, with the day each expires.
- Discounts lost last month, by vendor, with why.
- Thirteen weeks of cash out against cash in, refreshed from Eagle on demand.
Questions
Does it change anything in Eagle?
No. It is read-only on Eagle. The only write is the controller’s liquidity figure, kept on the Lunica server.
Can it build a pay list or approve payments?
No. The team decides what to pay in Eagle. This page shows what each choice costs.
Where do expected collections come from?
From Eagle’s open items, aged on each invoice’s own terms code, the same read the collections workflow uses.
Does it see vendors paid by check?
Yes. Check history is read from Eagle, 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 Eagle again.
The same workflow, on another ERP.
Payables Outlook is written for every system on the list. You’re reading the Eagle version.
See it on your Eagle data.
Thirty minutes. We walk the workflow on Eagle data, then map it to yours.