Statements and invoice emails for building-supply dealers.
Lunica sends statements and invoice copies the way your best AR clerk would, and never sends the same invoice twice.
Collections & ARUpdated Oct 202620 ERPs
See it work.
Click through the steps. Fictional data; the real thing runs on your ERP.
| 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.
Statements go out once a month from your ERP, and the questions start the next day: can you send me that invoice, with the signed ticket, and the credit memo you mentioned. Someone pulls each copy from your document archive, finds the ticket in the scan folder, and emails it by hand.
Project accounts want their invoices by job. Some want them weekly. Some want accounts payable copied. Your ERP has one statement cycle and one address on the customer file.
How it works.
- 1
Monthly statements
On the 1st or the 15th, pushed past a weekend, each statement covering the previous month, built from your ERP’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 your ERP.
Lunica reads your ERP’s open items, the customer file and the invoice copies in your document archive through its database or data warehouse, under an account that can only read. A statement is built from the open items as your ERP has them on the day it runs; an invoice email carries your ERP’s own invoice copy, with the signature capture where the driver collected one. Terms and the statement address come from the customer file.
Nothing is posted to your ERP by Lunica. A statement or the weekly invoice email goes only to a customer your team enrolled, on the schedule your team set; any other send is picked, previewed and sent by a person. Every send is logged against the account. A payment made from a statement’s pay-online code comes back to your ERP as an import file where your ERP takes one, or keyed by your team from what Lunica prepared, and a person posts it.
What a week looks like.
- Statement questions drop, because the ticket came with the invoice.
- Project customers get their invoices by job, weekly.
- Every send is logged: who, what, when.
- Credit memos reach the customer the first time.
Questions
Who gets a statement?
Only customers on the statements roster, a per-customer switch your team controls.
Where do invoice copies come from?
From your ERP’s own invoice copy in your document archive, including the signature capture where the driver collected one.
Can we send to AP and the project manager?
Yes. To, Cc and Bcc per send, and defaults per customer.
What about customers who want paper?
Leave them off the roster. Nothing changes for them; your ERP prints their statement as it always has.
Does it write to your ERP?
No. Lunica reads the open items and the invoice copies and sends the email. The statement run in your ERP is yours to keep or retire, and a payment made from a statement is posted by your team.
Can a customer pay from the statement?
Yes. Each statement carries a pay-online code that opens a payment page under your name. The payment comes back as a remittance your team posts.
Available for.
Each version is written in that system’s own terms: its screens, its files, its codes.
Own your AI. Own your software.
Thirty minutes with the people who build it. Bring your ERP.