Invoice copy requests for building-supply dealers.
Lunica reads the request, pulls the documents and drafts the reply, so the AR desk sends instead of searching.
Customer serviceUpdated Oct 202620 ERPs
See it work.
Click through the steps. Fictional data; the real thing runs on your ERP.
Hi, can you send a copy of 204317, the September statement, and the signed ticket for the Lot 14 Birchwood delivery on 9/24? We need them before we can release payment.
An email to ar@ is read for what’s being asked. The sender is matched to the account by domain.
The problem.
Every AP department sends the same email: a copy of 204317, the September statement, and the signed ticket for the Maple St delivery, or they can’t pay. Answering it means finding the account in your ERP, opening your document archive for the invoice, reprinting the statement, and hunting the ticket by delivery date.
The request sits until someone has the time, and the invoice doesn’t get paid until it’s answered. Next month the same customer asks again, nobody remembers what was sent, and the days beyond terms on that account are really days waiting on a copy.
How it works.
- 1
The request is read
Mail to ar@ or the AR clerk’s inbox is read for what’s being asked: which invoices, which statement period, which delivery. The sender is matched to the customer file by email domain and account name.
- 2
The documents are found
Each invoice is pulled from your document archive, the statement is built from your ERP’s open items for the period, and the signed ticket is found by order number and delivery date. Anything missing is flagged, not guessed.
- 3
The reply is drafted
A short reply listing what’s attached and the balance on the account, addressed to the person who asked. The attachments are the documents found, nothing else.
- 4
A person sends, and it’s logged
The AR clerk opens the draft, checks the attachments and sends. The request, what went and when are logged on the account, so the next one is answered with a glance.
How it connects to your ERP.
Lunica reads the customer file, open items and invoice history through its database or data warehouse, under an account that can only read, and the invoice copies and signed tickets from your document archive and the scan share. The model reads the request email and the documents it attaches, nothing more.
Nothing is written to your ERP by Lunica and nothing is sent on its own. The reply is a draft with attachments until a person sends it. The log of what was sent lives on the account in Lunica; if you want a note on the customer file, it is keyed by your team.
What a week looks like.
- Copy requests answered the same morning, with the right documents.
- The sender matched to the account, so the balance in the reply is the balance on it.
- Every request logged on the account with what went and when.
- Fewer invoices waiting on a copy before they’re paid.
Questions
Does it send the reply itself?
No. The reply is a draft with the documents attached until a person reads it and sends.
Where do the invoice copies come from?
From your document archive, the same copies your ERP already produces. Statements are built from open items for the period the customer asked about.
What if the signed ticket can’t be found?
The reply says so and the request is flagged. Nothing is attached that wasn’t found, and a model never fills in a document.
Does it write to your ERP?
No. It reads the account and the documents. The request log is kept in Lunica; a note on the customer file is keyed by your team if you want one there.
Can it answer from a shared mailbox?
Yes. It reads ar@ or whichever mailbox you point it at, and leaves the draft in the same thread so the reply comes from your address.
What does the model see?
The request email, the account it matched, and the documents it attaches. Not the rest of your mailbox and not the rest of the book.
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.