Collections for Epicor Eagle
Your Eagle book graded every night on days beyond each account’s own terms code, a personal note drafted for each customer that needs one, and a person deciding what goes out.
Collections & ARUpdated Oct 202620 ERPs
See it work on Eagle.
Click through the steps. Fictional data, in Eagle’s terms; the real thing runs on Eagle.
| Customer | Grade | Balance | Beyond terms | Terms | Last contact |
|---|---|---|---|---|---|
| Northline Drywall | D | $31,240.15 | 38 days | G · 30 DAYS FROM EOM | Sep 2 |
| Westfield Masonry | C | $12,980.00 | 19 days | E · 60 DAYS FROM EOM | Sep 30 |
| Pine Hollow Contractors | B | $8,415.60 | 6 days | G · 30 DAYS FROM EOM | — |
| Cedar & Stone Framing | A | $22,106.00 | 0 days | G · 30 DAYS FROM EOM | — |
Every customer on days beyond its own terms. Who gets a note is decided by the numbers.
Tools in this workflow.
Pieces your customers and your team use directly, on their own or inside this workflow.
The problem, as it happens in Eagle.
Eagle’s aging report puts a G account, thirty days from end of month, and an E account at sixty in the same thirty-day bucket. The report is right and useless at the same time: the customer who looks sixty days late may be exactly on terms.
So collections runs on a printout and whoever has Friday afternoon. The note is a template. The reply goes to one inbox. The promise to pay is remembered until it isn’t, and the house accounts get called by mistake.
How it works.
- 1
The book is graded overnight
Every customer scored on days beyond its own terms as Eagle has them, not a flat aging bucket. Who gets contacted is decided by the numbers, never by a model.
- 2
One note per customer, drafted
A short, personal note that states the balance, the invoices and the ask, with the payment link minted at send. A rule refuses any figure that isn’t on the customer file.
- 3
A person reads it and sends
The desk opens on the notes waiting for a decision, worst account first. Edit, send or skip. Nothing goes out on its own, and nobody is contacted twice in a sweep.
- 4
Replies land in one inbox
Every reply threads back to its note, is categorised, and comes with a proposed response. A promise to pay is logged against the account, with the date.
How it connects to Eagle.
Lunica reads Eagle’s open items and customer terms nightly through the Eagle data warehouse, read-only, and ages every invoice on its own terms code: G thirty days from end of month, E sixty, net-10, whatever the account carries. Aging figures are computed each night and never stored. House accounts and anything you exclude by rule are left alone.
Nothing is written to Eagle and nothing is sent on its own. A note is drafted per customer with the ask and the invoices taken from the record; a rule refuses any figure that isn’t on it. A person reads it, edits it, sends it or skips it. The payment link is minted at send and opens a payment page under your name, and the payment posts to the account.
What a week looks like.
- The right accounts, in the right order, on their real terms.
- One note per customer, never two in a sweep, never again inside the cooldown.
- Replies thread back to the note and come with a proposed response.
- Promises to pay logged against the account, not remembered.
Questions
Does anything go out automatically?
No. Every note and every reply is a draft until a person sends it.
How does it know our terms codes?
It reads them from Eagle, per account, and ages on them. An account on G ages from end of month plus thirty, not from the invoice date.
What about house accounts and disputed invoices?
Excluded by rule. The rules are a spec your admins edit in plain English, with history and revert.
Can customers pay from the note?
Yes. The link opens a payment page under your name: card or bank transfer, posted to the account.
Does it store our aging?
No. Aging is computed nightly from Eagle and never persisted.
Can we change the tone?
Yes, per customer or across the book, in the same spec your admins edit.
The same workflow, on another ERP.
Collections 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.