Credit holds and releases for building-supply dealers.
Lunica puts every hold and every release request in one queue, so the decision is made once, by the right person, with a note.
CreditUpdated Oct 202620 ERPs
See it work.
Click through the steps. Fictional data; the real thing runs on your ERP.
| Customer | Balance | Beyond terms | Promise | Orders waiting | Asked by |
|---|---|---|---|---|---|
| Northline Drywall | $31,240.15 | 38 days | $12,300 by Oct 30 | 2 | Mike Brennan |
| Oak Hill Builders | $18,620.40 | 12 days | $18,620 by Oct 24 | 1 | Counter · Main St |
| Pine Hollow Contractors | $13,210.00 | 52 days | none | 1 | No request |
| Ferry St Renovations | $4,870.00 | 71 days | none | 0 | No request |
Every account your ERP has on hold, with the balance, the promise and who is asking.
The problem.
The counter rings up a framer who’s on hold, your ERP throws the hold message, and the salesman calls whoever picks up at the credit desk. Release it, they’re good for it, the truck’s loaded. The hold flag on the customer file gets flipped by whoever answered, and the reason lives in that phone call.
Nobody tracks which holds were released, by whom, on what promise. The account released on a promise to pay Friday is still on the list the following Friday, released again. The aging report shows the balance growing. It doesn’t show that the hold was lifted four times.
How it works.
- 1
Every hold in one queue
Accounts your ERP has on hold, read each night and again when a person asks: the balance, days beyond Net 30 EOM, the open orders waiting, and the last promise to pay. Nothing is on the list that your ERP doesn’t say is held.
- 2
A release request comes in from the floor
The counter or inside sales asks from the queue, not the phone: which order, how much, what the customer said. The request lands on the account with the name of who asked.
- 3
Your credit manager releases or declines
Each request with the balance, the promise and the history beside it. Release this order, release the account, or decline, with a note the requester sees. Every decision is recorded.
- 4
The hold flag in your ERP is changed by a person
A release goes back as an import file where your ERP takes one, or keyed by your team from what Lunica prepared. The hold flag on the customer file is cleared or set by your team, and the queue shows who did it and when.
How it connects to your ERP.
Lunica reads the hold flag on the customer file, open items, open orders and the terms per account through its database or data warehouse, under an account that can only read, each night and on demand from the queue. Days beyond terms are figured on the account’s own terms, Net 30 EOM or Net 60 EOM, not a flat thirty. Promises to pay logged in collections show up beside the hold.
Nothing is written to your ERP by Lunica and nothing is sent on its own. A release or a new hold goes back as an import file where your ERP takes one, or keyed by your team from what Lunica prepared; the flag on the customer file changes when your team changes it. A note to the customer about the hold is a draft until a person sends it.
What a week looks like.
- Every hold on one list, with the balance and the promise behind it.
- Release requests arrive with who asked, which order and what was said.
- The decision is made by the credit manager, once, with a note.
- Every release and every hold has a name and a date against it.
Questions
Does Lunica put accounts on hold or release them in your ERP?
No. It keeps the queue and records the decision. The hold flag on the customer file is changed by your team, and the queue shows who did it.
Can the counter release an account?
Only if your policy says so. The queue takes the request from the floor; who can approve it is a rule your admins set.
Where do promises to pay come from?
From the collections workflow, where a reply is logged against the account with a date, or typed in by the person who took the call.
Does the customer get notified?
Only if a person sends the note. A draft is prepared when an account goes on hold or comes off; nothing goes out on its own.
What about a release for one order?
A release can be for one order, up to an amount, or for the account. The queue records which, and the order is released in your ERP by your team.
Does it work across branches?
Yes. A request from Route 9 and one from Main St land in the same queue, each with its branch, and the credit manager sees both.
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.