Purchase Orders and Rental Billing
Large accounts do not pay slow because they are broke. They pay slow because your invoice does not match anything in their system. A plant buyer cuts a purchase order against a budget, and when your invoice lands without that PO number, or with the wrong one, it sits in a queue until somebody chases it down. For a yard renting telehandlers and frac-tanks to industrial-maintenance accounts, the purchase order is the thread that ties a phone call to a signed ticket to a paid invoice. Get the PO captured at the start, carried through the rental, and printed on the invoice, and you stop financing your customer's accounts-payable backlog out of your own cash.
Capture the PO before the iron leaves the yard
The cheapest place to fix a billing problem is the order desk, before anything rolls out the gate. When an industrial-maintenance account calls for a telehandler, the buyer almost always has a purchase order number, a cost code, or a work-order reference that has to appear on your paperwork. Ask for it on the same call you take the reservation. If the caller is a foreman who does not have it yet, write a release number and flag the order as awaiting a PO, not as cleared. Yards that let units leave on a verbal okay end up invoicing into a void weeks later, then discover the account will not pay against a missing authorization. Capturing the PO up front turns a future collections fight into a thirty-second question.
One PO, many tickets: how releases actually work
Big accounts rarely cut a fresh PO for every rental. A plant will issue a blanket purchase order covering a shutdown or a quarter, then draw against it with release numbers as crews pull equipment. Your billing has to mirror that. A single blanket PO might cover a string of frac-tanks, a telehandler, and a stack of attachments across several weeks, each pulled on a different day by a different supervisor. If you treat each pull as an unrelated rental, you lose the link back to the authorization. Track the parent PO and the individual release against every contract line, so when the buyer asks what was charged against their number, you can answer line by line instead of digging through tickets.
Match the PO to the site, not just the company
Industrial-maintenance customers are rarely one address. A single account name can cover a refinery, a compressor station, and a fabrication shop, each with its own buyer, its own budget, and its own purchase order rules. Bill the refinery's frac-tank rental against the fab shop's PO and the invoice bounces, even though the company is right. This is where account and site structure earns its keep. EquipFlow's accounts-and-sites model lets you hang each job location under the parent account with its own PO defaults, contacts, and billing address, so the right number attaches automatically when you write the order. Get the site right and the PO follows; get it wrong and you are reissuing invoices.
Print the PO on every document, every time
A PO number that lives only in your head, or buried in a notes field, does the customer's accounts-payable clerk no good. It has to be printed where their system expects it: on the rental contract, on the delivery ticket the site signs, and on the invoice itself. When all three carry the same number, the clerk can match your bill to their open purchase order in seconds and release payment. When the delivery ticket is blank, they have nothing to verify against, and your invoice goes to the exception pile. EquipFlow's billing module pulls the PO and release straight from the order onto every printed document, so the number a foreman signs for in the field is the same number that hits the invoice, with no retyping in between.
When the PO is wrong, short, or missing
Even a tight order desk will hit broken authorizations. A foreman gives an expired PO, a blanket order runs out of money mid-shutdown, or a buyer transposes a digit and the invoice rejects. Build a habit of validating the number against the account's known purchase orders at order entry, not at month-end. If a rental is running and the covering PO is exhausted, that is a conversation to have while the telehandler is still on rent, not a surprise on the statement. Keep a short list of which accounts allow work to start on a release pending a PO and which demand the number first. Knowing each customer's tolerance keeps your crews moving without leaving you holding uncollectible paper.
Key takeaways
Capture the purchase order or release number at order entry — chasing it after the iron has shipped is how large accounts end up paying late.
Blanket POs draw down through release numbers; track the parent authorization and each release against every contract line so charges reconcile by line.
Match the PO to the specific job site, not just the parent account — site-level billing defaults stop invoices from bouncing on the wrong number.
Print the same PO and release on the contract, the signed delivery ticket, and the invoice so the customer's clerk can match and pay without an exception.
Validate the PO at order entry and know each account's tolerance for starting on a pending number, so an exhausted authorization never becomes uncollectible.
Related pages
These pages cover the EquipFlow modules, equipment types, and verticals that intersect with the topic above.
Frequently asked questions
“Who on my team should own chasing a PO once the rental is already running?”
Put it on whoever opened the order, not on the bookkeeper at month-end. The order-desk person who took the call has the buyer's name and the live thread; a billing clerk weeks later is starting cold. Set a daily sweep of every order flagged awaiting a number, and have that person call the buyer directly rather than the foreman who pulled the unit. The foreman rarely controls the purchasing system, so routing the chase to him just adds a relay step.
“What do I do when the customer's accounts-payable team and their buyer disagree about which PO covers my rental?”
Stay out of their internal fight and document your side. Send the signed delivery ticket showing what left the yard, what date, and which number you were given at order entry. Let the buyer and their clerk reconcile against that record. Your job is proving the equipment shipped under an authorization someone on their side issued, not adjudicating their budget codes. A clean ticket with a number on it ends most of these arguments before they reach a credit hold.
“A buyer insists their own internal reference replaces a real PO. How do I tell the difference?”
Ask one question: will their accounts-payable system pay against this number with nothing else attached? A cost code or work-order tag often rides alongside a purchase order rather than standing in for it. If the clerk needs both, capture both and print both. When a buyer cannot say whether the number alone releases payment, treat it as a release pending the real authorization and confirm with whoever cuts the check, not the field contact.
“How close to the limit of a blanket PO should I let charges run before I stop?”
Watch the remaining balance against the units still on rent, not just the dollars already billed. If what is out there for the next billing cycle would push the order past its ceiling, raise it before that cycle closes, while you can still pull a unit or get the buyer to lift the cap. Waiting until the order is fully drained leaves equipment on hire with no authorization behind it, and that is the gap a customer points to when refusing the overage.
“My order desk says asking for a PO on every call slows them down. Is the friction worth it?”
Compare the cost on both ends. The number takes a moment at booking when the buyer has it in front of them; recovering it later means tracing a weeks-old rental through people who have moved on to other jobs. For walk-up or cash customers there is no PO to ask for, so the question only applies to accounts that demand one anyway. Build it into the reservation script so it is reflex, not a separate step.
“The number on the signed ticket does not match what the buyer later says I should have used. Who eats that?”
Lead with the ticket. Whoever signed in the field accepted the equipment under the number printed there, and that signature is your authorization to bill. If the buyer wants a different code applied, that is a reissue they request, not a write-off you owe. Keep the original ticket on the account so the correction is a relabel against a documented delivery, not a fresh argument over whether the rental happened at all.
See how EquipFlow handles this on a live yard.
Bring your fleet count and a rough sense of your current workflow. Twenty minutes covers the dispatch board live, MSA billing, and an honest answer on fit.
Book a demoStay in the loop
Yard ops notes, once a week.
Operator-written. Covers dispatch, billing, maintenance, and what we ship. No fluff.