Final Demand Letters for Paladin
Every account past your final notice, with its balance in Paladin, its lien deadlines and any guaranty on file. The collection file assembled from the record, the demand letter drafted, and the referral decided and tracked by your credit manager.
Collections & ARUpdated Nov 202620 ERPs
See it work on Paladin.
Click through the steps. Fictional data, in Paladin’s terms; the real thing runs on Paladin.
| Customer | Balance | Beyond terms | Final notice | Lien deadline | Guaranty |
|---|---|---|---|---|---|
| Summit Ridge Homes | $27,415.80 | 84 days | Sep 13 | Nov 9 · 18 days | Signed |
| Copper Creek Exteriors | $11,660.25 | 82 days | Sep 15 | Passed Oct 1 | Signed |
| Ferry St Renovations | $4,870.00 | 71 days | Sep 26 | None open | Signed |
| Delgado Tile & Stone | $2,140.00 | 63 days | Oct 4 | None open | None |
Every account whose final notice date has passed, with lien deadlines and guaranties beside the balance.
The problem, as it happens in Paladin.
The account is ninety days out, the dunning letters have gone unanswered, and the decision to send it to collections gets made on a Friday by whoever is angriest. The file an agency or an attorney needs is in four places: the signed credit application and guaranty in a drawer, the invoices in Paladin’s invoice history, the signed tickets in a scan folder, the letters in someone’s sent mail.
So the account sits at ninety days for another ninety while the file waits, and the lien deadline on its biggest job passes in the meantime. Once an account is placed, nobody tracks it: what the agency collected, what it kept, and whether the balance was written off in Paladin, and by whom.
How it works.
- 1
Accounts past the final notice
Every account whose final notice date has passed without payment, with the balance, the days beyond Net 30, the lien deadlines open on its jobs and whether a guaranty is on file, nearest deadline first. Who is on the list is set by your policy, never by a model.
- 2
The collection file is assembled
The signed credit application and any personal guaranty, each open invoice from Paladin’s invoice history with its signed delivery ticket, every statement and letter sent with its date, and the history of payments and promises. One indexed PDF, ready for an agency or an attorney.
- 3
The demand is drafted
A formal demand naming the invoices, the balance, the notices already sent and a date to pay by, addressed to the business and to the guarantor where there is one. A rule refuses any figure that isn’t on the customer account. Your credit manager reviews it and sends it.
- 4
The referral is decided and tracked
When the date passes, your credit manager chooses: refer to your agency, refer to your attorney, file the lien, or propose a write-off. Each placement is tracked to what was recovered and what it cost. A write-off goes to the controller with the file and is posted in Paladin by your team.
How it connects to Paladin.
Lunica reads Paladin’s open items, payments and the customer account through Paladin’s database, under an account that can only read, confirmed at onboarding, with invoice copies and signed tickets from Paladin’s invoice history. The credit application and guaranty come from the application on file, signed online or scanned from paper; the letters come from the dunning log, promises from the collections desk and lien deadlines from the notice calendar.
Nothing is written to Paladin and nothing is sent on its own. The demand letter is a draft until a person sends it, and the file goes to an agency or an attorney only when a person sends it. A hold, a write-off or a note on the account is entered in Paladin by your team. Each placement, recovery and fee is recorded against the account in Lunica.
What a week looks like.
- Every account past its final notice on one list, nearest lien deadline first.
- The collection file assembled in minutes: application, invoices, tickets, letters.
- Demand letters that name the guarantor and every invoice, checked against the record.
- Each referral tracked to what it recovered, what it cost and what was written off.
Questions about final demand letters on Paladin.
Does Lunica send accounts to collections?
No. It assembles the file and drafts the demand. Your credit manager decides whether to refer the account and to whom, and sends it.
What goes in the collection file?
The signed credit application and any personal guaranty, each open invoice with its signed delivery ticket, the statements and letters sent with their dates, payments and promises, and the notes on the account. One indexed PDF.
Does the demand letter name the guarantor?
Where the credit application on file carries a signed personal guaranty, yes, and the guarantor gets a copy. Where there is none, the letter doesn’t mention one.
What about lien rights?
Open lien deadlines on the account’s jobs sit beside the balance, and the account with the nearest one is first on the list, so the lien decision is made before the deadline, not after.
What does the letter say about legal action?
Only what your policy allows and your team intends to do. The wording is a spec your admins edit, with history and revert, and your attorney can review it before it is used.
Does it write off the balance in Paladin?
No. A write-off is proposed to the controller with the file and the reason, and posted in Paladin by your team. The decision is recorded against the account.
Can we see what our agency recovers?
Yes. Each placement records who it went to, when, the amount placed, what has been recovered and the fee, from the remittances your team keys.
Does it need a server?
Lunica runs on one Windows server inside your network, beside the Paladin server, set up and maintained by Lunica. It reads Paladin through Paladin’s database, under an account that can only read, confirmed at onboarding. There is no inbound connection from outside your network.
What does Lunica read in Paladin?
The customer account, open items and terms, purchase orders and receipts, the inventory record, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to Paladin?
Nothing lands in Paladin without a person. What belongs in Paladin goes back as keyed by your team in Paladin from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in Paladin’s invoice history. Lunica reads them when a workflow needs one and never writes to them.
The same workflow, on another ERP.
Final Demand Letters is written for every system on the list. You’re reading the Paladin version.
See it on your Paladin data.
Thirty minutes. We walk the workflow on Paladin data, then map it to yours.