Summary
- FieldServio creates a Pending Vendor Bill when items are received on a purchase order or stock order, so field service AP on FieldServio starts at receiving, not at the supplier's invoice.
- FieldServio shows "Not all items have been picked or received" when someone invoices a job with PO items still outstanding, so a missed receipt holds up customer billing as well as supplier payment.
- The manual work sits at three handoffs: the technician's PO request, turning the packing slip into a receipt, and checking the supplier invoice against the pending bill.
- LayerNext uses FieldServio's API where one is available and its own screens where one is not, and a person steps in only for exceptions, errors and the approvals a business rule assigns.
Field service accounts payable is the work of paying the suppliers behind each job and charging every cost to the right job number. On FieldServio, most of it starts at receiving, because FieldServio builds the vendor bill from the receipt. What is left for your team sits in three places: the handoffs between documents, the invoices that do not match cleanly, and coding each bill to the right job.
This guide is for controllers and AP managers at FieldServio shops. It covers what FieldServio does on its own, where your team still does the work, which invoices pull away from a clean match, how to measure your own baseline, and what LayerNext's AP automation for field service companies takes over.
FieldServio Creates the Vendor Bill at Receiving, So AP Starts There
A parts purchase in FieldServio begins as a Job Order purchase order tied to a job, or as a Stock Order that replenishes a warehouse. When someone receives the items on the Receive Items screen, FieldServio creates a matching Pending Vendor Bill. That bill is what the supplier's invoice gets checked against.
Receiving drives a second process. FieldServio shows "Not all items have been picked or received" when someone tries to invoice a job that still has outstanding items on a PO, pick ticket or stock order. If more parts were ordered than used and the extras were never returned or deleted from the order, the job also stays at Partially Invoiced.
A receiving mistake costs twice. The supplier bill is wrong, and the customer invoice waits. For a controller that is a cash timing problem on top of an accuracy problem.
The Manual Work Sits at Three Handoffs
A parts purchase creates five documents: a work order, a purchase order, a packing slip, a vendor invoice and a vendor bill. People carry information between them at three points. The job number rides along the whole way, because it is how a job's cost reaches the books.
Handoff one: the PO number
A technician needs a part for a job and calls or texts the office. Office staff find the job in FieldServio, create the Job Order PO and send the number back. The cost is a call for every purchase and a technician waiting on the office.
At J Hansen HVAC Group, a Manitoba HVAC and plumbing contractor on FieldServio, a technician's request now reaches a PO number on a phone in under two minutes. The PO exists before the parts are collected, which gives the receipt something to match against.
Ivan Cruz
VP of Finance, CHB Group
Handoff two: the packing slip and Receive Items
The slip goes back to the office, and someone enters it on Receive Items line by line. That entry is the receipt, and it creates the pending bill, so a keying error here carries into AP. A partial delivery shows as Partial Arrived, and the remainder sits under Waiting On until someone receives it.
LayerNext accepts a photo of the slip taken in the field, alongside email, shared folders and cloud storage. It reads the slip and matches it to the open PO. At J Hansen, one photo is enough to start automated receiving. A slip that does not agree with the PO goes to the team as a task.
Handoff three: the supplier invoice against the pending bill
The clerk opens the pending bill, compares it with the supplier's invoice, corrects the reference number and dates, updates item costs that changed, adds freight and selects Approve Bill. The comparison is the clerk's eyes on two documents, for every invoice.
LayerNext runs a three-way match across the invoice, the PO and the receipt. It passes when quantity, price and PO reference agree within a tolerance your finance team sets for that vendor, written in plain English. An invoice with no PO stops as a task tagged by invoice number, supplier and issue type. A person steps in only for exceptions, errors and the approvals a business rule assigns, and every action goes to an audit trail.
This step is also where duplicate and erroneous payments get through. APQC's Open Standards Benchmarking puts the median organization at 1.5% of annual disbursements going out that way, as reported by Corpay on July 23, 2026. On $4 million of supplier spend, that median is $60,000. The figure is arithmetic on the benchmark, not a measurement of any one company.
Six Situations Pull an Invoice Away From a Clean Match
A three-way match handles the invoice that agrees with the PO. A field service shop also gets invoices that disagree for ordinary reasons. FieldServio has a documented way to handle each one, and each one still needs a person to decide something.
LayerNext does not guess on these. An invoice that falls outside tolerance stops as a task and goes to the person who owns the answer. Because tolerances are set per vendor, what reaches a person is a judgment call, not a rounding difference.
A Miscoded Bill Moves Margin From One Job to Another
Job costing works only if each supplier cost lands on the right job number. The figures below are made up for illustration. Job 4102 is a compressor replacement billed at $4,200 with $900 of labor. Job 4107 is a preventive maintenance visit billed at $600 with $180 of labor. A supplier bill for $1,850 covers the compressor.
With the wrong coding, the compressor job looks like the best work of the month and the maintenance visit looks like a loss. The next compressor quote gets priced from those numbers.
Freight adds a wrinkle. Freight on a Stock Order never goes to a job, and freight on a Job Order PO reaches the job only if the "Create Freight Job Items From PO" setting is on. Whoever configured FieldServio can tell you which way yours is set, and it changes every margin that carries freight.
The job number comes from the PO, so a bill matched to its PO is coded to the same job. LayerNext enters the bill in FieldServio with the PO and job number, through the API where one is available and through FieldServio's own screens where one is not.
Service and Subcontractor Invoices Need an Approver Instead of a Receipt
A repair or a subcontracted job leaves no packing slip, so nothing can be received. The person who knows whether the work happened has to confirm it. LayerNext routes the invoice to the manager responsible for the job, sends reminders on pending approvals and tracks how long each approver takes. Approver turnaround becomes a number a controller can read.
The routing is a business rule your finance team writes in plain English. This one is an illustration:
Invoices from mechanical subcontractors with no PO go to the service manager assigned to the job. If the amount is over $2,500, the branch operations manager approves as well.
Measure Your Own Three Handoffs Before You Change Anything
You can get a baseline without any software. FieldServio's Order Backlog Report covers parts and equipment on Job Orders, Stock Orders and Picklists, with 27 filters and 44 columns. It can be saved and exported to Excel. Export a month, pull your last 20 supplier invoices, and work out one number for each handoff:
- Minutes from the technician's request to a PO number (handoff one). The request is a call or a text, so ask five technicians how long their last five took.
- Days from PO Created Date to PO Received Date (handoff two). Both are columns on the report. Also count the orders still at Partial Arrived after their ship date.
- Days a bill sits at Pending Approval (handoff three). Search Accounts Payable by that status and read the bill dates. The oldest ones show where invoices wait.
Those three numbers are your baseline. After a pilot you measure the same three again and see whether the hours came back. The invoices that took longest are the ones to send us first. Send us your ugliest FieldServio invoices and we will show you which ones match cleanly and which come back as tasks.
Five Options for Field Service AP on FieldServio, and Where Each Stops
LayerNext's AP automation is the route we build, so here is what it changes. The slow steps in the other routes sit between a supplier document and a matched, coded bill: asking for a PO number, turning a packing slip into a receipt, and checking an invoice against both. LayerNext does those steps. Across LayerNext deployments, finance teams save 90 to 165 hours per month, with 95%+ task accuracy on defined workflows. That means fewer hours keying and chasing, less rework and fewer duplicate or erroneous payments. Your own number depends on your invoice volume and how clean your vendor data is.
Rollout Runs in Three Phases Over 12 Weeks
We start small. The first phase covers capture and approval routing, so managers get approval tasks and reminders while the AP team keeps entering bills in FieldServio. Posting is added once the team has checked enough of LayerNext's matches to trust them. Before any of that, the vendor master gets cleaned up and the workflow gets mapped, because skipped cleanup turns into weeks of avoidable exceptions.
The schedule runs discovery in weeks 1 and 2, a pilot in weeks 3 to 6, and full deployment in weeks 7 to 12. The saved hours repeat every month after that, so payback is measured in months, not years. For a worked example in FieldServio, J Hansen HVAC Group's case study shows purchasing, receiving and payables running as three connected workflows.
.webp)
FAQ
