Promises to Pay for Epicor Eagle
A promise made on a call or in a reply is logged against the account with the amount and the date, then watched against the payments posted in Eagle. A kept promise closes quietly; a broken one comes back to the desk with the next step drafted.
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.
We’ll have 38612 and the two smaller ones covered by the 17th, the Maple St draw is due Tuesday.
Lunica reads the amount and the date out of what Dale wrote. Nora confirms it in a click.
The problem, as it happens in Eagle.
A contractor says the check goes out Friday, and that sentence lives on a sticky note, in a column of a spreadsheet, or in the memo field on the customer file. The Business Advisor aging doesn’t know a promise was made. The next sweep calls the account again as if nobody had spoken to them, or skips it because someone remembers a conversation.
Nobody tracks which promises are kept. The customer who promises every month and pays every other month looks like the one who always pays, until the balance is large enough to matter. By then the next step is a hard call, and the record of what was promised is three people’s memories.
How it works.
- 1
The promise is logged
From a reply, a call note or the counter, Lunica reads the amount and the date out of what was said and logs it against the account: who promised, what, by when, and which invoices it covers. The person who took the promise confirms it in a click.
- 2
The calendar watches it
Each promise sits on the calendar with the account’s open items beside it. Lunica reads the payments posted in Eagle each night and matches them to the promise, by amount and by invoice. The desk sees what is due this week without asking.
- 3
Kept promises close quietly
When the payment posts in Eagle, the promise is marked kept and the account’s record notes it. Collections notes for the account pause while a promise is open, so nobody is chased for money they have said is coming.
- 4
Broken ones come back to the desk
The morning after a missed date, the promise is back on the desk with the account’s history, the pattern of kept and broken promises, and the next step drafted: a short note, a call script, or the hold your policy calls for. A person decides, and a person sends.
How it connects to Eagle.
Lunica reads Eagle’s open items, payments and the customer file nightly through the Eagle data warehouse, under a database account that can only read, and compares each open promise to what was posted: the invoices it named, the amount, the date. Promises themselves come from replies in the collections inbox, call notes keyed by your team, and anything the counter writes down.
Nothing is posted to Eagle and nothing is sent on its own. The promise lives in Lunica, beside the account, not in Eagle’s memo field, unless your team wants a note there, keyed by your team. A payment that keeps a promise is posted by your team as it always is; Lunica only reads that it happened. The note drafted for a broken promise is sent by a person.
What a week looks like.
- Every promise on one calendar, with its amount, date and invoices.
- Accounts with an open promise are left alone by the collections sweep.
- Broken promises on the desk the next morning, with the next step drafted.
- A kept-and-broken history per customer, before the next credit review.
Questions
Where do promises come from?
From replies in the collections inbox, where Lunica reads the amount and date out of what the customer wrote, and from call notes your team keys. Each one is confirmed by the person who took it.
What counts as kept?
A payment posted in Eagle that matches the promise by amount, or by the invoices it named, on or before the date. A partial payment shows as partial; the rest stays open.
Does it write to Eagle?
No. Promises live in Lunica beside the account. Payments are posted by your team as they are today; Lunica reads that they posted and closes the promise.
Does it contact the customer when a promise is broken?
No. It drafts the next step and puts it on the desk. A person decides whether to send, call, or hold the account.
Can the desk see a customer’s history of promises?
Yes. Kept, broken and partial, with dates, on the account and in the credit review.
What about a promise made at the counter?
Anyone at the yard can log one from the account page in a sentence. Lunica reads the amount and date and asks them to confirm.
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.
Promises to Pay 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.