Purchase Order

Selling to a ten-person company involves no such document. The person who wants it puts a card in, and the approval is done that afternoon. The problem appears once a company grows large enough that the path money takes out of it no longer runs through that person's hands.

That's how a deal everyone verbally agreed to sits unpaid for two months. The practitioner says they've decided to use it. The team lead says they approved it. You send the invoice and nothing happens. Check, and the procurement department hasn't registered the expense yet. An unregistered expense doesn't exist inside a finance system, so resending the invoice three times produces the same nothing.

A purchase order (PO) is the evidence that the registration is done. The customer has confirmed inside their own process that this amount goes to this vendor, attached a number to it, and sent it out — which makes that number, for the seller, the signal that separates a closed deal from a promise. Everything agreed before it arrives is one human being's word, and human beings change teams and leave companies.

The template varies by company, but five fields do the work.

1. The PO number — an identifier the customer assigns by their own rules. This is the part of the document that actually functions. Your invoice, the document stating the amount billed and its breakdown, has to carry this number for the accounts payable clerk on the other side to know which expense it belongs to. An invoice sent without it gets bounced back or stops quietly in someone's queue.
2. Item and quantity — what is being bought and how much of it. For software that means the plan name and the seat count.
3. Amount — unit price and total. It has to match the quote you sent to the last unit. If you dropped the price late in negotiation, reissue the quote and take the PO against the new figure. A mismatch stops the payment process where it stands, and getting a corrected PO out takes another week.
4. Term and delivery — contract start and end dates, or the date by which delivery happens. For software this usually mirrors the subscription period rather than a shipping date.
5. Payment terms — how many days after the invoice payment is due. Thirty is common; sixty shows up at large enterprises. This field decides your own cash flow.

Seeing how it connects to the earlier documents makes its position clear. The quote proposes a number, a master service agreement (MSA) — which sets the rules applying to the whole relationship — settles the conditions, and the PO commits an actual expenditure against that number and those conditions. A second deal with a customer where an MSA already exists usually needs nothing but a PO: the rules were settled last time, so only quantity and amount are new.

The customer writes it. Unlike every document earlier in the process, this is one you receive rather than produce.

Inside the customer, the person producing it is not your contact but a procurement specialist. That person doesn't use the product and has never been in a meeting with you. They check three things: whether the approval chain is complete, whether the budget line matches, and whether the vendor is registered. None of the three has anything to do with your product, which is why nothing that worked in earlier stages is of any use here.

So when a deal stalls at this point, the cause is neither the product nor the price. It's that a business registration certificate or bank details still haven't been submitted, or that new vendor registration takes two weeks and nobody has started it.

Two parties read it. On your side, the rep checks the number and copies it onto the invoice. On the customer's side, the payment clerk later sets this document next to your invoice and compares them. Money moves when the two agree.

Which makes the sales job in this stage guidance rather than persuasion. Your contact frequently doesn't know their own company's procurement process either. Telling them when the PO has to be issued for a start this month, and which documents you need to submit first, tends to pull the timeline in by about two weeks. This final stretch of confirming signature routes and approval chains is called closing, and most of the dead time in it comes from that guidance never being offered.

"Did the PO number come through? I can't submit the invoice without it."

Checking whether the payment process is actually open.

"I left it out of this quarter's numbers. They said the PO lands next week."

The team treats this document as the marker for when a deal counts.

"The PO came in $90 under the quote."

The figures disagree, so payment will stall until someone decides which one to correct.

At Pagedeck, Sofia asks about the procurement process before negotiation is even finished with enterprise customers. Whether a PO is required, and if so how many days new vendor registration takes. Asking early takes the panic out of the last week of the quarter, because vendor registration and approval routing are both things the customer has to do, on their own calendar.

One deal last quarter skipped that question. The contact had every approval in hand, and the team found out in the final week that new vendor registration ran three weeks. The deal closed, but the revenue landed in the next quarter, and Grace has since written a procurement check into the stage criteria for enterprise deals.

A frequent mistake is treating the PO as a contract. It has amounts and dates on it and arrives stamped, so it looks like one. But nothing in this document says who is liable for what when something goes wrong. Indemnity limits, termination mechanics, how personal data gets handled — all of that lives in the MSA. Start delivering on a PO alone and there's no sentence to stand on when a problem arrives, and by then you've already provided the service, which costs you the position to negotiate from.

The other belief is that a PO means the money has arrived. An official document came through, so the rest feels like a matter of time. What actually starts here is the clock written in the payment terms. Thirty-day terms mean a month after the invoice goes out; sixty-day terms mean two. Money from a deal whose PO landed on the last day of the quarter arrives in the next one. Plan without that distinction and you end up with revenue that reconciles and a bank balance that doesn't.