FieldproxyAI-native field service software

Purchase orders

How do I link one customer purchase order to many jobs or sites and bill against it?

Make the purchase order its own record, not a text field typed on each job. The PO record holds the customer's PO number, the total value, the dates it is valid and the sites it covers, and every job, quote and invoice for that work points to it. The balance left is then the PO value minus what you have invoiced and minus what is scheduled or quoted but not yet billed, and each invoice prints the PO number so the customer's accounts payable team can match it.

  • A PO number typed on a job is a label. A PO record with a value, dates and covered sites is something you can bill against.
  • Track three numbers per PO: invoiced, committed (scheduled or quoted, not yet invoiced) and remaining.
  • Decide what happens at the limit before you reach it: warn at a threshold such as 80%, and stop new jobs when a job would take the PO over.
  • If a subcontractor does the work, they get your PO number, not the customer's. Keep the two linked on the job.
  • Ask the customer how they want it invoiced: one invoice per job, or one summary invoice per month listing every job.

Book your demo

A video call with our team

Number of employees

This page is about the PO your customer gives you and the matching PO you give a subcontractor. Buying parts from suppliers on a PO is a different process. The country notes summarize official pages and are not legal or tax advice.

Facts checked as of November 2026. Sources at the end of the page.

Step by step

How one PO covers many jobs or sites, step by step

Accounting systems call this a blanket order: a framework agreement with a total, and individual orders drawn from it. The same shape works for service jobs.

1. Create the PO as a record under the customer

Fields: the customer's PO number exactly as they wrote it, the billing customer, total value, currency, start and end dates, a description of the scope, and a status such as Open, Nearly used, Exhausted, Expired or Closed. Microsoft describes blanket orders the same way, as a framework for a long-term agreement between you and your customer or vendor.

2. Say which sites and which work it covers

A PO for planned maintenance at 30 named sites should not be picked by mistake for a repair at site 31. BuildOps, which has a blanket PO feature, lets you set coverage to all properties under the billing customer or to selected properties and departments. If the PO splits money between planned visits and a repair allowance, hold those as two lines with their own balances.

3. Link every job and quote to the PO

The job has a PO field that is a lookup to the PO record, filtered to the open POs that cover that customer and site. A one-off job can still carry a one-time PO number typed by hand. Keep the customer's own work order number in a separate field, because many customers send both.

4. Count committed work as well as invoiced work

A PO is spent when you invoice, but it is promised earlier, when a visit is scheduled or a quote is approved. Remaining balance = PO value, minus invoiced, minus committed. If you only subtract invoices, the balance looks healthy until a month of unbilled jobs lands at once.

5. Set rules at the limit

Three rules cover most contracts. Warn the account manager when the PO passes a threshold (e.g. 80% used or 30 days before the end date). Block a new job from being scheduled if its estimate would take the PO over. Block any job dated after the PO expires. Customer systems enforce the same thing on their side: ServiceChannel's invoice API says the invoice total must be less than or equal to the work order NTE.

6. Print the PO number on every invoice

The invoice takes the PO number from the linked record, so nobody retypes it. For customers who want one bill, group the period's jobs into a single invoice that lists each job with its site, date and amount. In accounting systems the number usually travels in a named field: NetSuite invoices have a PO# field, and Business Central uses External Document No.

7. Raise a variation before the money runs out

When the remaining balance will not cover the work left, ask the customer for a PO increase or a new PO, and record it as an amendment with its own date and value. Do not edit the original total silently, or last quarter's balance report stops matching what the customer signed.

8. Mirror it for the subcontractor

If one contractor covers all 30 sites, issue them one PO of your own with a line per site or per visit, and put your PO number on each job they receive. Their invoices come back quoting your number and are matched line by line. Accounting tools support the draw-down: in QuickBooks Online you can link multiple transactions to a single purchase order, and Xero shows the percentage and amount billed on each PO.

Why it goes wrong

Why billing against a shared PO goes wrong

These are the problems buyers described on our calls, told by trade and size, not by name.

The software assumes one PO per job

A commercial refrigeration and mechanical service firm has one contractor covering about 30 sites and wanted a single purchase order linked to all of those jobs. It had been told that one PO to many jobs is not standard, so the alternative was 30 purchase orders for one agreement.

The PO number is typed, so it is typed wrong

When the PO is a free-text box on each job, the same PO appears as 4500017733, PO 4500017733 and 450001773. Nothing can total them, and the customer's accounts payable team rejects the invoice with the typo.

The subcontractor never gets a PO number

A lift machine supplier that delivers about 1,000 maintenance visits a year through roughly 70 subcontractors asked whether the PO number can be sent to the subcontractor with the job. Without it, subcontractor invoices arrive with no reference and someone has to work out which visit each one is for.

Two reference numbers fight for one field

A facility maintenance coordinator with about 200 subcontractors wanted jobs created under the client's own work order or PO number as the job ID. That works until one PO covers many work orders. The job needs both: the customer's work order number and the PO it bills against.

The balance lives in a spreadsheet

A commercial electrical contractor doing 30 to 40 visits a day for customers with about 400 sites quotes around 8 jobs a day. At that pace nobody can keep a PO balance by hand, and the first sign that a PO is spent is a rejected invoice weeks after the work was done.

Finance approves in another system

Two of these firms push invoices to Xero as drafts so an approval step still applies before anything is issued. If the PO number is not carried into the accounting invoice as a reference, the approver cannot check it against the customer's PO.

Ways to do it

Ways to link one PO to many jobs

Six real approaches. The difference is whether the PO is only a label on the invoice or a record with a value that jobs draw down.

ApproachWhat it does wellWhere it falls short
Spreadsheet of POs plus a PO text field on each jobFree, and every field service tool has some reference field. Works for a handful of POs.The balance is updated by hand after invoicing, committed work is invisible, and typed PO numbers drift.
A reference field on the invoice (Housecall Pro, Jobber)Housecall Pro has a Customer Reference # (PO or WO number) on web invoices, up to 30 characters. Jobber's Batch Create Invoices combines a client's jobs that are ready for invoicing into one draft invoice.The number is a label. There is no PO value, no covered sites and no remaining balance. Housecall Pro says the field is web-only for now and still rolling out.
A PO field on the job plus consolidated invoices (ServiceTitan)A Customer PO # field on the job prints on the invoice. Consolidated invoices combine multiple open invoices for one bill-to customer, and the Customer PO # is filled from the underlying invoices.ServiceTitan's help pages describe the PO as a number on each job. We found no PO total or draw-down balance in them, so the balance is still tracked elsewhere.
A blanket PO record (BuildOps)One Blanket PO covers multiple jobs, quotes or invoices, with a Total Amount, effective start and end dates, and coverage by property. On a job, quote or invoice you switch Customer PO to Blanket PO and pick an active one.The help page describes monitoring spend against the total. It does not say what happens when a job would exceed it, so ask whether that is a warning or a block.
Do it in accounting (blanket orders, progress invoicing)Business Central blanket sales orders make individual orders that link back through Blanket Order No. NetSuite has blanket purchase orders for the buying side. QuickBooks Online can create multiple partial invoices from a single estimate and caps you at the remaining balance.Accounting knows what was invoiced, not what is scheduled for next week. Dispatch cannot see the balance when booking a job, and blanket orders are built for quantities of items more than visits to sites.
A PO record you define in a configurable system (Fieldproxy)The PO is a record with your own fields, linked to jobs, quotes and invoices, with invoiced, committed and remaining amounts and your own rules at the limit. The same structure serves the subcontractor's PO.It is set up for your contracts, not switched on from a menu, so you need to bring two or three real POs and say how each customer wants to be invoiced.

Vendor facts are from each vendor's own help pages, read in November 2026. Features change, so confirm on a demo with one of your real POs.

Worked example

A worked example: one PO, 30 sites, a planned line and a repair allowance

Say a retail customer issues PO 4500017733 for $96,000, valid 1 January to 31 December. It covers quarterly maintenance at 30 stores at $650 a visit, which is 120 visits and $78,000, plus an $18,000 allowance for repairs found on those visits. One subcontractor covers all 30 stores.

You create one PO record with two lines. The planned line generates 120 jobs, each linked to the PO, so the whole $78,000 is committed on day one. The repair line starts empty.

By the end of March the first 30 visits are complete and invoiced: $19,500. Six repairs have been done and invoiced for $4,300, and two more are quoted and approved for $2,100 but not yet done.

PO lineValueInvoicedCommitted, not invoicedRemaining
Planned maintenance (120 visits)$78,000$19,500$58,500$0 uncommitted
Repair allowance$18,000$4,300$2,100$11,600
Whole PO$96,000$23,800$60,600$11,600

A worked example, not a benchmark. Remaining = value minus invoiced minus committed.

The number that matters is the $11,600 left for repairs with three quarters of the year to go. Repairs are running at about $6,400 a quarter, so the allowance will run out in the third quarter. A rule set at 80% of the repair line ($14,400 used) raises that in good time to ask for a variation, not after an invoice bounces.

On the buying side you issue the subcontractor one PO of your own, for example 120 visits at $420, or $50,400, with a line per store per quarter. Each job they receive shows your PO number. The customer's PO value and your selling prices stay hidden from them.

Invoicing follows what the customer asked for: here, one summary invoice a month quoting PO 4500017733 and listing each store visited, the date, the job number and the amount.

Before you buy

What to check before you choose a tool

Good signs

  • The PO is a record with a value, dates and covered sites, and jobs pick it from a list.
  • The balance shows invoiced and committed amounts separately, per PO and per PO line.
  • You choose what happens at the limit: a warning, an approval step or a hard block.
  • One invoice can cover many jobs on the same PO and still list each job, site and date.
  • The PO number reaches the accounting invoice as a reference field without retyping.
  • A PO increase is recorded as a dated amendment, not an overwrite.
  • A subcontractor sees your PO number on the job and nothing about the customer's PO value.

Red flags

  • The only PO field is free text on the invoice.
  • One PO can be attached to one job only, so 30 sites means 30 POs.
  • The balance updates only when an invoice is paid.
  • Combining jobs into one invoice drops the per-job detail the customer's accounts payable team needs.
  • PO limits exist in a report but nothing stops a dispatcher booking past them.

In Fieldproxy

Setting it up in Fieldproxy

Fieldproxy is set up around your own records, fields and statuses, so the PO is built as a record that fits your contracts. Field names below marked e.g. are examples you would rename.

1. A purchase order record under the customer

Custom fields, e.g. PO number, value, currency, valid from, valid to, scope and status, with lines for planned work and a repair allowance, and a list of the sites it covers.

2. Jobs, quotes and invoices linked to it

Each job carries the linked PO and, separately, the customer's work order number. The PO screen lists every job, quote and invoice drawn against it, with invoiced, committed and remaining amounts.

3. POs read from the customer's document

The Document intelligence agent turns incoming PDFs, POs and work orders into jobs and line items, so a PO emailed as a PDF does not have to be keyed in. A person reviews it before the jobs are created.

4. Rules at the limit

An approval step, e.g. any job whose estimate would take the PO past its value goes to the account manager before it can be scheduled. The Watcher agent flags POs that pass a threshold or are close to their end date with work still open.

5. Recurring visits tied to the PO

Maintenance contracts create the planned visits for each site, and each visit can be created already linked to the PO line that pays for it.

6. The subcontractor's side

The subcontractor portal shows the job with your PO number. Their invoice is uploaded against that job, and prices you do not want them to see stay hidden.

7. Invoices and accounting

Invoices are raised per job or as one invoice for many jobs on the PO, with the PO number printed from the record, then synced to QuickBooks or Xero. A weekly PO balance report can be emailed by the Scheduler agent, and Command Center answers questions such as how much is left on a given PO.

By country

PO rules that change how you invoice, by country

Tax law rarely requires a PO number on an invoice. Customers and e-invoicing networks do. These are the rules worth knowing.

United States: federal blanket purchase agreements

FAR 13.303 defines a blanket purchase agreement as a simplified method of filling anticipated repetitive needs. The agreement must state a dollar limitation for each individual purchase and the individuals authorized to purchase, and it picks an invoicing method. One option is a summary invoice submitted at least monthly or upon expiration of the BPA, whichever occurs first. Many commercial customers copy this pattern.

United Kingdom: No PO, No Pay

The VAT rules in HMRC Notice 700 list what a VAT invoice must show, and a PO number is not on the list. Buyers add it themselves. NHS trusts set No PO, No Pay policies trust by trust: one says invoices without a valid PO may be returned or experience significant delays, and another says they will be returned to the supplier unpaid.

Europe and Peppol e-invoicing

In Peppol BIS Billing 3.0 the customer's PO number goes in BT-13, Purchase order reference, and BT-10 is the Buyer reference. Rule PEPPOL-EN16931-R003 says a buyer reference or purchase order reference must be provided. An e-invoice with neither breaks that rule, so the PO link has to exist before the invoice is sent.

Canada: standing offers and call-ups

Federal buyers use standing offers. CanadaBuys says a standing offer is not a contract, and a contract is established with each call-up made against it. The call-up limit is set in the standing offer document. Treat the standing offer as the agreement and each call-up as its own PO with its own number.

Australia: not a tax invoice field

The Australian government's invoicing guide lists the words tax invoice, your business name, ABN, issue date, a description with quantity and price, and the GST amount. A PO number is not on it, so whether you must quote one comes from the customer's purchasing terms.

EDI customers

Large retailers may send the PO and expect the invoice as EDI documents. In ANSI X12 the purchase order is transaction set 850 and the invoice is 810. The invoice must carry the PO number from the 850 it answers.

How switching works

How switching to Fieldproxy works

We move your data over and set the system up to the way you already work. Fieldproxy replaces the old tool; it does not run alongside it.

  1. Bring two or three real POs

    One blanket PO for many sites, one single-job PO and, if you use subcontractors, one PO you issued to them. Tell us how each customer wants to be invoiced.
  2. We build the PO record and its rules

    Your PO fields, lines, covered sites and statuses, the balance calculation, and what happens at the limit: a warning, an approval or a block.
  3. Open POs and their jobs come across

    Open POs, the jobs already done against them and what has been invoiced are loaded from your spreadsheets and exports, so balances are right on day one.
  4. Invoices go out against the PO

    The first month's invoices are raised per job or as a summary, checked against your accounting system, then synced to QuickBooks or Xero.

FAQ

Questions people ask

Can one purchase order be linked to multiple jobs, for example 30 sites?
Yes, if the PO is a record that jobs point to, not a field on a single job. BuildOps documents a Blanket PO that covers multiple jobs, quotes or invoices, and in a configurable system such as Fieldproxy the PO record is set up with the sites it covers and every job linked to it.
Can the software send a purchase order number to a subcontractor with the job?
It should. The subcontractor needs the number of the PO you issued to them, shown on the job they receive, so their invoice quotes it. The customer's PO number and its value are a separate matter and usually stay hidden from them.
Can I use the client's own work order or PO number as the job ID?
You can show it as the main reference, but keep your own job number underneath and store the customer's work order number and PO number in separate fields. One PO often covers many work orders, and a customer can reuse a work order number across years.
How do I track the balance left on a PO?
Remaining = PO value minus invoiced minus committed, where committed means scheduled jobs and approved quotes not yet invoiced. Track it per PO line if the PO separates planned visits from a repair allowance.
What should happen when a job would take the PO over its value?
Pick one rule per customer and write it down. Common choices are a warning to the account manager at a threshold such as 80%, an approval before the job can be scheduled, or a hard block until the customer issues a variation or a new PO.
Should I send one invoice per job or one invoice for the whole PO?
Ask the customer's accounts payable team. Some match each invoice to one visit. Others want a monthly summary invoice listing every job on the PO, which is one of the invoicing options the US federal rules for blanket purchase agreements describe.
Will the PO number carry through to QuickBooks or Xero?
It needs to arrive as a reference on the accounting invoice, or the approver and the customer cannot match it. Check this on a demo with a real invoice. If your invoices go to Xero as drafts for approval, the reference should already be on the draft.
Is a PO number legally required on an invoice?
Generally not by tax law. HMRC's list of what a UK VAT invoice must show does not include one, and neither does the Australian government's tax invoice list. It becomes required through the customer's terms, such as No PO, No Pay, and through e-invoicing rules such as Peppol's.

Sources

Competitor details on this page come from the vendors' own pages and documentation, checked as of November 2026. Plans and prices change, so check the vendor's current page before you decide.

See it built on your workflow

Tell us how your jobs run today. We build a demo on your stages, forms and pricing before the call.