Promises to Pay for Paladin
A promise made on a call or in a reply is logged against the account with the amount and the date, then watched against the payments posted in Paladin. A kept promise closes quietly; a broken one comes back to the desk with the next step drafted.
Collections & ARUpdated Oct 202620 ERPs
See it work on Paladin.
Click through the steps. Fictional data, in Paladin’s terms; the real thing runs on Paladin.
We’ll have 204317 and the two smaller ones covered by the 17th, the Maple St draw is due Tuesday.
Lunica reads the amount and the date out of what Dale wrote. Nora confirms it in a click.
The problem, as it happens in Paladin.
A contractor says the check goes out Friday, and that sentence lives on a sticky note, in a column of a spreadsheet, or in the memo field on the customer account. The Accounts Receivable aging doesn’t know a promise was made. The next sweep calls the account again as if nobody had spoken to them, or skips it because someone remembers a conversation.
Nobody tracks which promises are kept. The customer who promises every month and pays every other month looks like the one who always pays, until the balance is large enough to matter. By then the next step is a hard call, and the record of what was promised is three people’s memories.
How it works.
- 1
The promise is logged
From a reply, a call note or the counter, Lunica reads the amount and the date out of what was said and logs it against the account: who promised, what, by when, and which invoices it covers. The person who took the promise confirms it in a click.
- 2
The calendar watches it
Each promise sits on the calendar with the account’s open items beside it. Lunica reads the payments posted in Paladin each night and matches them to the promise, by amount and by invoice. The desk sees what is due this week without asking.
- 3
Kept promises close quietly
When the payment posts in Paladin, the promise is marked kept and the account’s record notes it. Collections notes for the account pause while a promise is open, so nobody is chased for money they have said is coming.
- 4
Broken ones come back to the desk
The morning after a missed date, the promise is back on the desk with the account’s history, the pattern of kept and broken promises, and the next step drafted: a short note, a call script, or the hold your policy calls for. A person decides, and a person sends.
How it connects to Paladin.
Lunica reads Paladin’s open items, payments and the customer account nightly through Paladin’s database, under an account that can only read, confirmed at onboarding, and compares each open promise to what was posted: the invoices it named, the amount, the date. Promises themselves come from replies in the collections inbox, call notes keyed by your team, and anything the counter writes down.
Nothing is posted to Paladin and nothing is sent on its own. The promise lives in Lunica, beside the account, not in Paladin’s memo field, unless your team wants a note there, keyed by your team. A payment that keeps a promise is posted by your team as it always is; Lunica only reads that it happened. The note drafted for a broken promise is sent by a person.
What a week looks like.
- Every promise on one calendar, with its amount, date and invoices.
- Accounts with an open promise are left alone by the collections sweep.
- Broken promises on the desk the next morning, with the next step drafted.
- A kept-and-broken history per customer, before the next credit review.
Questions
Where do promises come from?
From replies in the collections inbox, where Lunica reads the amount and date out of what the customer wrote, and from call notes your team keys. Each one is confirmed by the person who took it.
What counts as kept?
A payment posted in Paladin that matches the promise by amount, or by the invoices it named, on or before the date. A partial payment shows as partial; the rest stays open.
Does it write to Paladin?
No. Promises live in Lunica beside the account. Payments are posted by your team as they are today; Lunica reads that they posted and closes the promise.
Does it contact the customer when a promise is broken?
No. It drafts the next step and puts it on the desk. A person decides whether to send, call, or hold the account.
Can the desk see a customer’s history of promises?
Yes. Kept, broken and partial, with dates, on the account and in the credit review.
What about a promise made at the counter?
Anyone at the yard can log one from the account page in a sentence. Lunica reads the amount and date and asks them to confirm.
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.
Promises to Pay 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.