FieldRepOps

For whoever chases the hospital

The PO that never came.

The case is done. The construct is in, the biologic is used, the delivery order is signed in the room, and it bills $38,400. Then nothing. The hospital's purchase order does not arrive in a week, or a month, and until it does nobody is paid: not the distributorship, not the manufacturer, and often not the rep. This is what to do about it, on a schedule, and what your record has to show when the hospital says it never got the paperwork.

Last reviewed November 8, 2026  ·  Written from running spine distributorship purchase orders, not from a textbook

The short version

  1. Without the hospital's PO, nobody gets paid. The manufacturer books the sale when the PO reaches it, so your commission waits on the same piece of paper the hospital's payment does.
  2. POs stall for boring reasons. A queue, a wrong buyer, a price that did not match the contract, a department code. Rarely a refusal.
  3. Follow up on a schedule: 15, 30, 60 days. Same document each time, to a named person, with no patient details in the message.
  4. Keep every send on record. Date, address, document, and when it was opened. That is what you show when the hospital says it never got it.
  5. Know what is owed at a glance. Every unpaid delivery order, aged, tied to its case. In spine, one stalled order is a share of the month.

What a stalled PO costs in spine

The numbers here are illustrative, not from any customer's books. A two-level fusion bills the hospital $38,400 on one delivery order. The manufacturer owes the distributorship $10,770 in commission on it, and the rep is owed $4,308 of that under their agreement. None of that moves until the hospital's purchase order exists, because the manufacturer books the sale on the PO, not on the surgery.

In a distributorship running many small cases, one late PO is noise. A spine distributorship's month is a dozen or two cases like this one. One of them stalled for sixty days is a twelfth of the month's billing sitting in a buyer's queue, and $4,308 a rep is watching for. Two of them is a cash-flow problem. That is why in spine the follow-up is not an admin task. It is the job.

Why POs stall

Almost never because the hospital will not pay. Almost always because of something small inside the hospital that nobody told you about.

  • The queue. The requisition reached a buyer who had forty of them. Yours is in the pile.
  • The wrong buyer. The delivery order went to the general procurement address and the spine buyer never saw it, or the buyer changed and nobody updated your contact.
  • The price. One line on the order did not match the hospital's contract sheet, so the buyer parked the whole order rather than raise a PO that would fail matching later. On a twenty-line order, one line is easy to get wrong.
  • The code. The case was coded to a department or cost centre the buyer does not cover, and it is waiting for someone else's approval.
  • The paperwork. The delivery order was photographed in the room, texted to the office and emailed on from there, and one of those steps did not happen.

Every one of these is found by asking, and most are fixed the same day once found. The problem is not the stall. The problem is the sixty days nobody asked.

The follow-ups: 15, 30, 60

Pick a cadence and keep it. The one we use is three dates after the delivery order first goes to procurement, each one a little firmer and a little higher up.

Day 15

Confirm and ask

To the buyer the order went to. Confirm the delivery order was received, ask for the purchase order number or the expected date. Attach the same delivery order again. Polite, short, one case per message.

Day 30

Name the price, copy the rep

To a named buyer, not an address. Reference the contract the prices came from, so a price hold can be cleared on the spot. Copy the covering rep, who will be in that hospital this week and can ask in person.

Day 60

Escalate

To the buyer's manager or accounts payable, with the dates of the two earlier sends. The rep raises it at the next case. Ask what is holding it; the answer is almost always one of the boring reasons above.

Three rules hold at every step. Send the same delivery order every time, so there is one document and not three versions of it. Send it to a person, by name, as soon as you know one. And put no patient details in the message. Procurement raises a purchase order from the case number, the date, the surgeon and the products; it does not need a patient identifier, and leaving it out of email is the simplest protection there is.

What the record shows

At day 60 the hospital says it never received the delivery order. This is the moment the whole thing turns on what you can show. If the order was sent from a system that recorded the send, the conversation is short.

One delivery order's record, illustrative
Oct 7Case covered. Delivery order signed in the room: implants and biologic for a two-level fusion, $38,400.
Oct 7Delivery order sent to procurement, buyer's address on file. Opened Oct 8.
Oct 22Follow-up 1 sent, same document attached. Opened Oct 22.
Nov 6Follow-up 2 sent to the named buyer, contract reference included, rep copied. Opened Nov 6.
Dec 6Escalated to the buyer's manager with the three dates above. Reply the same day: a price hold on one cage line. Cleared.
Dec 9Purchase order received. Payment now being followed.

Example dates and figures only. The point is that each line exists, with a date and an address, before anyone has to remember anything.

Compare that with a delivery order emailed from a rep's phone and forwarded by the office. There is a photo, somewhere. There may be a sent email, on someone's account. There is no record of what was sent to whom on which date, and so the hospital's "we never got it" cannot be answered, only argued with. The manufacturer, reasonably, pays on the PO it has. The distributorship eats the sixty days.

Do not let it hide

The last piece is seeing it. A stalled PO hides easily in a spreadsheet, because the spreadsheet is rebuilt at month end and the order was fine when the month started. What you want instead is every unpaid delivery order in one place, every day: no PO yet, or PO but no payment, aged by days outstanding, tied to the case that created it. Then the $38,400 order at day 45 is on the screen on day 45, and the follow-up goes out on day 45, instead of being discovered on the first of the next month by whoever closes the books. In spine, with the month built from a handful of large cases, that view is the difference between a cash-flow problem and a reminder email.

Straight answers

Why does the hospital's PO take so long?

Boring reasons: a buyer's queue, the wrong buyer, a price that did not match the contract, a department code. Rarely a refusal. A five-figure order needs more approvals than a small one. See why POs stall.

How often do I follow up?

On a schedule, not from memory: 15, 30 and 60 days, each a little firmer and a little higher up. Same document every time, to a named person. See the follow-ups.

What goes in the message to procurement?

Case number and date, hospital and department, surgeon, products with contract prices, total, and your contact. No patient details. Procurement does not need them to raise a PO.

What do I need when the hospital says it never got it?

The date each send went out, the address, the document, and when it was opened. With that, the conversation is about where the paperwork is inside the hospital. See what the record shows.

How do I see what is still unpaid?

Every delivery order without a PO or without payment, in one place, aged, tied to its case, current every day rather than rebuilt at month end.

What this looks like in FieldRep Ops

FieldRep Ops is the financial system of record for independent spine distributorships, and this is the method it runs. The delivery order is signed in the room, the implants at every level and the biologic on it, priced from the hospital's contract sheet. It goes to hospital procurement from the system, with no patient details in the message body, and every send is recorded with the date, the address and the message, and so is every open. Follow-ups for the purchase order, and then for payment, go out on schedule until each one lands, and a daily digest lists what is still owed.

Every unpaid delivery order sits in one place, aged and tied back to the case that created it, so what is outstanding, for how long, and where it is stuck is on the screen every day rather than pieced together from a spreadsheet at month end. Reps see the same open purchase orders on their own statements as pending, which is how the rep knows to ask about it at the next case. And because a signed delivery order is never edited in place, the document you sent on day one is the document you can show on day sixty.

Founding distributors

We are taking on a small number of founding spine distributors now, who use FieldRep Ops free while it proves itself on their books and know the price before they start. One private environment per distributorship; nothing shared with anyone.

FieldRepOps
FieldRep Ops is the operating and financial system of record for independent spine distributorships
Customer sign-in security@fieldrepops.com Updates Answers Security Privacy policy