Job Account Setup for Acumatica
A contractor opens a job account per project on a form under your name, with the owner, general contractor, lender, property address and legal description gathered before the first load goes out. The job record is prepared for Acumatica and keyed by your team.
CreditUpdated Oct 202620 ERPs
See it work on Acumatica.
Click through the steps. Fictional data, in Acumatica’s terms; the real thing runs on Acumatica.
Hi Tom,
Before the first load goes out Thursday, here’s the job form for the Maple St duplex. It asks for the owner, the GC, the lender and the jobsite details. About five minutes on your phone.
Mike Brennan, Ridgeline Supply Co.
Harbor Point has a new duplex. The link goes to Tom; the form is under Ridgeline’s name.
Tools in this workflow.
Pieces your customers and your team use directly, on their own or inside this workflow.
The problem, as it happens in Acumatica.
A contractor calls the pro desk on Monday with a new job. The salesman opens a job under the customer record in Acumatica with the name the contractor gave it, a jobsite address off the top of their head, and the first ticket ships that afternoon. Owner, general contractor, lender, legal description: blank, to be filled in later. Later is when the job is already ninety days in.
The preliminary notice has to go out inside a window that runs from first delivery, and it needs the owner’s name and the property’s legal description. When the job record has neither, the notice doesn’t go, and the dealer finds out it needed lien rights the day the general contractor stops paying.
How it works.
- 1
The contractor opens the job on a form
A job account form under your name, sent from the pro desk or opened from the portal: job name, jobsite address, owner, general contractor, lender, estimated start and value. The contractor fills it in on a phone and signs.
- 2
Lunica completes what it can
The parcel and legal description where the county publishes them, the owner of record, the state’s notice window. Each one marked as found or still needed, so nothing is assumed.
- 3
The pro desk reviews the job
The form, the lookups and the parent account side by side: C010422, Net 30, the limit and what’s open on it. Inside sales or credit checks the jobsite address against a sales quote the pro desk already wrote, fixes what’s wrong, and approves the job.
- 4
The job record is prepared for Acumatica
Job name, jobsite address, owner, GC and lender in the shape Acumatica wants under the customer record, going back as an Acumatica API call or import scenario where one exists, or keyed by your team from what Lunica prepared. The signed form and the lookups stay on file against the job.
How it connects to Acumatica.
Lunica reads the customer record, the jobs already under it, and Acumatica’s open orders and invoices through Acumatica’s OData and REST endpoints, under a role that can only read, so a new job is checked against the parent account’s terms and limit and matched to a sales quote or a sales order the pro desk already wrote for it. The form itself is hosted under your name; the connection to Acumatica runs on one server inside your network, whether Acumatica is in the cloud or on your own server.
Nothing is written to Acumatica by Lunica and nothing is sent on its own. The job record goes back as an Acumatica API call or import scenario where one exists, or keyed by your team from what Lunica prepared, and the first delivery still ships on the ticket your team writes. The form is sent to the contractor by a person at the pro desk, or opened by the contractor from the portal.
What a week looks like.
- No first delivery to a job nobody can name the owner of.
- Owner, GC, lender and legal description gathered once, on a phone, signed.
- Every job sits under the right account, on the parent’s terms and limit.
- The notice deadline is known the day the job opens.
Questions
Does Lunica create the job in Acumatica?
Not on its own. It prepares the job record under the parent customer record, and it goes back as an Acumatica API call or import scenario where one exists, or keyed by your team from what Lunica prepared.
What if the contractor won’t fill in the owner?
The job still opens; the field is marked still needed, the pro desk sees it, and a reminder is drafted for a person to send. Many contractors don’t know the lender on day one, and that’s fine.
Where does the legal description come from?
From the county’s public records where it publishes them, matched to the jobsite address, and shown as found or still needed. A person confirms it before it goes on a notice.
Can a job go on its own terms?
Yes, if your policy allows it. The form carries requested terms; your credit manager sets them, and they are keyed into Acumatica with the job.
What about jobs that already exist?
Lunica reads the jobs Acumatica already has under each account and shows which are missing an owner, GC or legal description, so the desk can chase them before a notice is due.
Does the form need a login?
No. The pro desk sends a link, or the contractor opens it from the portal under your name. A phone and about five minutes.
Does it need a server?
Lunica runs on one server inside your network, whether Acumatica is in the cloud or on your own server, set up and maintained by Lunica. It reads Acumatica through Acumatica’s OData and REST endpoints, under a role that can only read. There is no inbound connection from outside your network.
What does Lunica read in Acumatica?
The customer record, open items and terms, purchase orders and receipts, the stock item, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to Acumatica?
Nothing lands in Acumatica without a person. What belongs in Acumatica goes back as an Acumatica API call or import scenario where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in the files attached to the record. Lunica reads them when a workflow needs one and never writes to them.
The same workflow, on another ERP.
Job Account Setup is written for every system on the list. You’re reading the Acumatica version.
See it on your Acumatica data.
Thirty minutes. We walk the workflow on Acumatica data, then map it to yours.