Credit Limit Reviews for Epicor Eagle
Every limit in Eagle checked nightly against the account’s exposure, pay history and growth, with a recommendation under your written policy. Your credit manager approves or holds, and the new limit is keyed into Eagle by a person.
CreditUpdated 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 | Limit | Exposure | Avg days to pay | 12-mo volume | Flag |
|---|---|---|---|---|---|
| Harbor Point Builders | $25,000 | $31,840.50 | 28 | $412,300 | Over limit |
| Pine Hollow Contractors | $15,000 | $13,210.00 | 61 | $96,400 | Slowing |
| Cedar & Stone Framing | $50,000 | $22,106.00 | 24 | $538,900 | Within |
| Westfield Masonry | $10,000 | $9,980.00 | 44 | $71,200 | Due review |
Exposure against limit, pay history and growth, for every account.
The problem, as it happens in Eagle.
A limit is set the day the account opens, from the application and a gut feel, and then it sits. Three years on, a framer is running twice the volume, pays on G · 30 DAYS FROM EOM without fail, and bumps the limit every month, so the counter calls the credit desk and the limit goes up on the phone. The customer file in Eagle says whatever was last typed into it.
The other direction nobody tracks. The account whose balance has crept to three times what it was, paying slower every quarter, still has the limit it got when it was small. The Business Advisor aging shows the balance. It doesn’t show that the exposure has quietly outgrown the policy, and nobody reviews limits until something is already past due.
How it works.
- 1
Exposure against limit, nightly
Every account’s open balance, orders released but not yet invoiced where Eagle has them, and the limit on the customer file, read each night. Pay history and twelve months of volume sit beside it.
- 2
A recommendation under your policy
Raise, hold or lower, with the reason in your policy’s words: months on terms, days to pay, utilisation, growth. The numbers decide who gets reviewed; a model only writes the explanation.
- 3
Your credit manager approves or holds
The desk opens on accounts due a review, largest exposure first. Approve the new limit, change the figure, or hold and set a date to look again. Every decision is recorded with who and why.
- 4
The new limit is keyed into Eagle
An approved limit goes back as a file Eagle imports, like AP Assist, or keyed by your team from the packet. Until a person keys it, Eagle keeps the old one, and the review stays open on the desk.
How it connects to Eagle.
Lunica reads the customer file, open items and sales history through the Eagle data warehouse, under a database account that can only read, nightly: the limit as Eagle has it, the open balance, orders released but not yet invoiced where Eagle carries them, and twelve months of invoices and payments. Terms are read per account, so an account on E · 60 DAYS FROM EOM is judged on E · 60 DAYS FROM EOM, not on a flat thirty.
Nothing is written to Eagle by Lunica and nothing is sent on its own. An approved limit goes back as a file Eagle imports, like AP Assist, or keyed by your team from the packet, and the review shows who keyed it and when. Lunica runs on one Windows server inside your network, beside the Eagle server; the recommendation and the decision live there, not in Eagle.
What a week looks like.
- Every account with exposure past its limit is on the desk by morning.
- Accounts that have earned a higher limit come up before the counter calls.
- Each recommendation says why, in your policy’s words.
- Every limit change has a name, a date and a reason behind it.
Questions
Does Lunica change limits in Eagle?
No. It recommends. Your credit manager approves, and the new limit goes back as a file Eagle imports, like AP Assist, or keyed by your team from the packet. Until then Eagle keeps the old one.
Where does the policy come from?
From you. Your credit policy is written down in plain English as a spec your admins edit, with history and revert. Each recommendation cites the lines it used.
What counts as exposure?
Open balance plus orders released and not yet invoiced where Eagle has them. The figures are read from Eagle each night and never stored.
Does it lower limits too?
It can recommend one. Lowering is a decision for a person, and nothing changes on the customer file until someone keys it.
Can we exclude house accounts?
Yes, by rule. House accounts, cash accounts and anything you name are left alone.
How often is an account reviewed?
Exposure is checked nightly. A full review comes up on the schedule your policy sets, when exposure crosses the limit, or when a person asks for one.
Which Eagle editions does it work with?
Lunica works from the Eagle data warehouse. Your edition and version are confirmed during onboarding, before anything is connected.
Does it need a server?
One Windows server or VM inside your network, set up and maintained by Lunica. It reads Eagle over the LAN; there is no inbound connection from outside, ever.
What about iNet and WebDocs?
Invoice copies come from iNet. Scanned documents keep flowing into WebDocs exactly as before; Lunica reads the scan share and never writes to it.
Can it post to Eagle if we want it to?
The standing rule is that a person does. Where Eagle takes a file, like AP Assist, Lunica prepares the file and your team imports it.
The same workflow, on another ERP.
Credit Limit Reviews 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.