Lien Notice Deadlines for Kerridge K8
Lunica reads the first delivery on every job from K8’s invoices, counts the state’s notice window from it, and drafts the notice with the owner, GC and lender from the job account. A person reviews, sends or files it, and the sent notice is on file against the job.
CreditUpdated Oct 202620 ERPs
See it work on K8.
Click through the steps. Fictional data, in K8’s terms; the real thing runs on K8.
| Job | Customer | First delivery | State window | Days left | Job account |
|---|---|---|---|---|---|
| Maple St duplex | Harbor Point Builders | Oct 16 | 20 days | 6 | Complete |
| Lot 14 Birchwood | Pine Hollow Contractors | Oct 13 | 20 days | 3 | Owner missing |
| Route 9 warehouse | Granite Peak Builders | Oct 3 | 45 days | 26 | Complete |
| Elm Ridge phase 2 | Cedar & Stone Framing | Sep 30 | 20 days | Sent Oct 9 | Complete |
Every open job with a notice due, soonest first, counted from the first delivery.
The problem, as it happens in K8.
The window for a preliminary notice runs from the day the first load hits the jobsite, and that day is on a delivery ticket in K8, not on anyone’s calendar. Twenty days in one state, forty-five in the next, a notice of furnishing somewhere else. The credit desk finds out a job started when the first invoice for it shows up on the aged debt report, which on a short-window state is after the window has closed.
Nobody tracks the jobs that never got a notice. They look fine until the general contractor stops paying at ninety days, the owner has already paid the GC, and the dealer’s only remedy on a two-hundred-thousand-dollar job is a collection call. The notice that would have protected it cost a stamp.
How it works.
- 1
First deliveries read from K8
Every job’s first invoice or delivery ticket, read nightly, becomes the start of its clock. The state comes from the jobsite address on the job account, and the window from that state’s rule.
- 2
The calendar, by deadline
Every open job with a notice due, soonest first: days left, owner, GC, lender, and whether the job account has what the notice needs. A job missing an owner or a legal description is flagged before the deadline, not after.
- 3
The notice is drafted from the job account
Owner, GC, lender, property description, the first delivery date, a description of the materials and an estimate of the value from K8’s invoices, in the state’s form. A rule refuses any figure that isn’t on an invoice.
- 4
A person reviews, sends or files it
Your credit manager reads it, fixes anything, and sends it certified or hands it to your notice service. The sent notice, the date and the proof of mailing are filed against the job.
How it connects to K8.
Lunica reads invoices, delivery tickets and the jobs under each customer account through a read-only login to the K8 database, nightly: the first invoice date per job, the jobsite address, the materials and the running value supplied so far. The owner, GC and lender come from the job account form, or from what your team keyed on the job in K8.
Nothing is written to K8 by Lunica and nothing is sent on its own. Every notice is a draft until a person sends it, and the sent notice, with its date and proof of mailing, is filed against the job on the Lunica server, on one server inside your network, or beside KCS’s hosted K8. Where your team notes the notice date on the job in K8, it is keyed by a person.
What a week looks like.
- Every job with a notice due is on one calendar, soonest first.
- The clock starts from the first delivery K8 invoiced, not from memory.
- Each notice is drafted in the state’s form with the owner and GC already in.
- The sent notice and its proof of mailing are on file against the job.
Questions
Does Lunica send the notice?
No. It drafts it and keeps the calendar. A person reviews the notice and sends it, certified or through your notice service, and records that it went.
How does it know which state’s rule applies?
From the jobsite address on the job account. The windows and forms by state are a spec your admins can read and change, with history and revert. The rule you run is the one you approved.
What if the job account is missing the owner?
The job is flagged on the calendar as soon as its clock starts, with what’s missing. A request to the contractor is drafted for a person to send.
Where does the first delivery date come from?
From the first invoice or delivery ticket on the job in K8. Where a job isn’t set up as a job in K8, Lunica matches by jobsite address and shows the match for a person to confirm.
Does it write the notice date back to K8?
No. The notice and its date are filed against the job on the Lunica server. If you keep the date on the job in K8, your team keys it.
What about the lien deadline itself?
The same calendar carries the later dates where the state has them, counted from the last delivery K8 invoiced. A notice of completion is entered by a person when one arrives.
Does it need a server?
Lunica runs on one server inside your network, or beside KCS’s hosted K8, set up and maintained by Lunica. It reads Kerridge K8 through a read-only login to the K8 database. There is no inbound connection from outside your network.
What does Lunica read in K8?
The customer account, open items and terms, purchase orders and receipts, the product record, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to K8?
Nothing lands in K8 without a person. What belongs in K8 goes back as a K8 import where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in K8’s document management. Lunica reads them when a workflow needs one and never writes to them.
The same workflow, on another ERP.
Lien Notice Deadlines is written for every system on the list. You’re reading the K8 version.
See it on your K8 data.
Thirty minutes. We walk the workflow on K8 data, then map it to yours.