Statements and Invoices for Epicor Eagle
Statements on the first or the fifteenth and a weekly invoice email built from Eagle’s own iNet invoice copies, with the signed delivery ticket behind each one, sent once, to the customers you enroll.
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.
| Invoice | Date | Amount | Job | POD | Send |
|---|---|---|---|---|---|
| 39102 | Oct 13 | $4,218.40 | Lot 14 · Birchwood | Signed | Selected |
| 39118 | Oct 14 | $1,960.00 | Lot 14 · Birchwood | Signed | Selected |
| 39141 | Oct 16 | $7,304.25 | Lot 16 · Birchwood | Signed | Selected |
| 39160 | Oct 17 | $612.80 | Counter | None | Skipped |
Cedar & Stone’s week, by job.
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 prints the statement. The day after it goes out, the phone rings: can you send invoice 38666 with the signed ticket, and the credit memo from last week. Somebody opens iNet, prints the copy, digs the ticket out of WebDocs, and emails it. For every customer who asks.
Project accounts want invoices weekly, by job, with the AP clerk copied. Eagle has one statement cycle and one address on the account.
How it works.
- 1
Monthly statements
On the 1st or the 15th, pushed past a weekend, each statement covering the previous month, built from Eagle’s open items, with a pay-online code. Only to customers you enroll.
- 2
The weekly invoice email
First business day of the week: one PDF holding each invoice from the week just ended, followed by its proof of delivery, in date order. Only to the customers you enroll.
- 3
Any set of invoices, on demand
On the customer page, pick the invoices, choose To and Cc, attach delivery tickets and credit memos, preview the email as it will read, send.
- 4
Sent once
A ledger of what went to whom. A delivered customer is never emailed the same invoice twice; a credit memo rides once, with the next email.
How it connects to Eagle.
Lunica reads Eagle’s open items and the iNet invoice copies, including the signature the driver captured on the invoice, read-only through the Eagle data warehouse. The delivery ticket is paired from the scan share. Terms and balances on the statement are Eagle’s.
Nothing is written to Eagle. Statements go on the first or the fifteenth, pushed past a weekend, only to customers on the roster. The weekly invoice email goes on the first business day with one PDF, each invoice followed by its proof of delivery. A ledger records what went to whom; a delivered customer is never emailed the same invoice twice, and a credit memo rides once with the next email.
What a week looks like.
- Statement questions stop, because the ticket came with the invoice.
- Project customers get their week’s invoices by job, AP copied.
- Any set of invoices sent from the customer page in four clicks.
- Every send logged: who, what, when.
Questions
Who gets a statement?
Only customers on the roster, a per-customer switch your team controls. Everyone else gets what Eagle sends today.
Are the invoice copies the same as Eagle’s?
They are Eagle’s: the iNet invoice copy, signature capture included.
What about credit memos?
Attached once, with the next invoice email, and recorded so they don’t go twice.
Can we send to more than one address?
Yes. To, Cc and Bcc per send, with defaults per customer.
Does it change the statement cycle in Eagle?
No. Eagle keeps doing what it does. Lunica sends to the customers you enroll, on the day you choose.
The same workflow, on another ERP.
Statements and Invoices 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.