Tax Exemption Certificates for Epicor Eagle
Every account flagged exempt in Eagle with no certificate on file, or an expired one, on one list. A request is drafted and sent by a person, the certificate the customer returns is read and checked, and the exempt flag in Eagle stays as your team sets it.
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 | Exempt in Eagle | On file | Expires | Exempt sales, 12 mo | Status |
|---|---|---|---|---|---|
| Shoreline Electric | Yes · resale | None | none | $84,200 | Missing |
| Westfield Masonry | Yes · resale | Resale cert, 2022 | Jun 30, 2026 | $41,600 | Expired |
| Mill Creek Carpentry | Yes · resale | Cert · Mill Creek Carpentry Inc | Mar 31, 2028 | $12,300 | Name differs |
| Bayview Decks | Yes · resale | Resale cert, 2024 | Dec 31, 2026 | $27,900 | Expiring |
| Oak Hill Builders | Yes · resale | Resale cert, 2025 | Dec 31, 2027 | $156,800 | Valid |
Every account Eagle flags exempt, against what is on file. Worst first.
The problem, as it happens in Eagle.
A contractor says “we’re exempt” at the counter, the exempt flag gets set on the customer file in Eagle, and the certificate is coming, they’ll bring it next time. Three years of tax-free sales later, the folder has a certificate for a different legal name, one that expired, and nothing at all for a third of the accounts Eagle says are exempt.
Nobody tracks the gap until the auditor pulls the exempt sales report and asks for the paper. Every exempt sale without a certificate is tax the dealer owes, with interest, on a customer who may be out of business. The flag was set in a minute; the certificate behind it was nobody’s job.
How it works.
- 1
Exempt accounts against the file
Every customer file flagged exempt in Eagle, read nightly, against the certificates on file: none, expired, expiring, wrong legal name, wrong state for where the goods ship. A list, worst first, with the exempt sales behind each one.
- 2
A request is drafted
A short note to the customer asking for the certificate, with the state’s form linked and a page under your name to upload it. A person sends it. Reminders are drafted on a schedule, each one sent by a person.
- 3
The certificate is read and checked
What the customer returns, by upload, email or photo, is read: state, certificate number, exemption type, expiry, legal name and address against the customer file. Each check is shown as a pass or a question, for a person to accept or send back.
- 4
Filed against the account
The accepted certificate, its expiry and who accepted it, on the account. The exempt flag in Eagle stays as your team sets it; where a certificate fails, the list says so and a person decides what to do with the flag.
How it connects to Eagle.
Lunica reads the customer file, its tax status and ship-to addresses, and the exempt sales by account through the Eagle data warehouse, under a database account that can only read, nightly. Certificates already scanned into iNet are read where you point Lunica at them, so the first list starts from what you have, not from zero.
Nothing is written to Eagle by Lunica and nothing is sent on its own. The request and every reminder are drafts until a person sends them. An accepted certificate is filed against the account on the Lunica server, on one Windows server inside your network, beside the Eagle server. Where the expiry is kept on the customer file, it is keyed by your team, and the exempt flag is set or cleared only by your team.
What a week looks like.
- Every exempt account with nothing valid on file, on one list, worst first.
- Requests go out in your words, sent by a person, with a page to upload to.
- Each certificate checked for state, number, expiry and legal name before it is filed.
- Expiries come up before they pass, not at the audit.
Questions
Does Lunica change the exempt flag in Eagle?
No. It shows which exempt accounts have no valid certificate. The flag on the customer file is set or cleared by your team.
Does it validate the certificate with the state?
It checks the certificate’s format, expiry, exemption type and the legal name against the customer file. Where a state offers a public lookup, the result is shown beside the certificate for a person to confirm. The state’s rules are still yours to apply.
What about multi-state and drop shipments?
The ship-to address on each exempt sale is read from Eagle, so a certificate for one state doesn’t cover goods shipped to another, and the list says which state is missing.
Do customers get reminders automatically?
No. Reminders are drafted on the schedule you set, and each one is sent by a person. The schedule is a spec your admins edit.
Where does the certificate live?
On the Lunica server, against the account, with its expiry and who accepted it. Certificates already in iNet stay there and are read where you point Lunica at them.
Can it handle resale certificates and direct-pay permits?
Yes. Resale, direct pay, government, nonprofit and the exemption types your states use are each read for what they require, and the account carries which one it holds.
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.
Tax Exemption Certificates 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.