How do I add a PO number to a proposal or invoice?

Corporate, government, and other institutional clients often issue a purchase order to authorize a spend, and require that PO number on your paperwork before their accounting department can pay. Check Cherry has a PO Number field on every booking. You can type it in yourself, or have the client give it to you while they book.

Adding a PO number to an invoice

No setup required. Every invoice header already has a PO Number row.

Open the booking and go to its Invoice tab.
Find the PO Number row in the header. If nothing is set yet, it reads Not included.
Click it, enter the number, and save.
Not included is only visible to you. Your client's copy leaves the PO Number row off entirely until a value exists, so it never prints as a blank line.

Collecting it from the client

If corporate work is a regular part of your business, turn on the PO Number extra question instead of chasing the number down later.

ManageBooking EngineExtra Questions
Go to Extra Questions.
Find PO Number in the list and enable it.
Choose whether the customer answers it during checkout, or whether it is internal only and your team fills it in.
Decide whether to make it required.
Think twice before marking it required. Only a slice of your clients will ever have a PO number, and a required field stops everyone else from finishing checkout.

Once enabled, the field appears in the Additional Info section of a lead, proposal, or booking, so you can enter or edit it there at any point. It also carries across when a lead converts, so a number captured on an inquiry follows the client through to the booking. See how to collect more information during the booking process for more on extra questions.

Where it shows up

  • In the header of proposals and invoices, on every proposal theme.
  • In automated messages, as the po_number token. It works in lead, proposal, and booking messages.
  • As a PO Number column in the Events and Bookings reports.

Was this article helpful?

Thanks for your feedback!

Sorry to hear that. Want to chat with our support team?

Chat with us

Last updated August 21, 2026 17:39