This article covers the customer's purchase-order number: the reference a municipality, school district, or corporate accounts-payable department assigns to your contract, and which they expect to see on every invoice before they will pay it. PortaPro stores it once on the customer and prints it on every invoice PDF and invoice email as PO #.
This is the customer's PO for billing *them*. It has nothing to do with Billing → Spending → Purchase orders, which are the POs *you* send to your vendors. See Purchase Orders for that feature.
---
CPO-1: Why It Matters
Government and larger commercial customers pay against a "proper invoice". Most municipal AP systems check for the vendor name, an invoice number and date, the service dates, the amount, a remit-to address, and the PO number. An invoice missing the PO number is returned unpaid, and it goes back to the end of the next claims cycle. Printing the number is the difference between being paid on the next warrant run and being paid a month later.
Pair it with the other municipal-friendly settings on the same Billing screen:
---
CPO-2: Where To Enter It
Customer profile → ⋮ → Edit → Billing → PO number. (Payment terms, PO number and Tax-exempt are always in view on the Edit Customer panel.)
Type the number exactly as the customer wrote it on their PO, including any prefix or fiscal-year suffix. Leave it blank for customers who do not use one; nothing prints when it is empty. The profile's Billing & Terms card shows the current value.
Per-site PO numbers. Some customers issue a PO per location: a builder with a PO for each lot, or a school district with a PO per school. A site carries its own PO number in Sites → Add / Edit Service Location → PO number for this site (the customer import fills it from `location_po_number`), and on per-site invoices the site's number is printed instead of the customer's. When a site has no number of its own, the customer's number is used.
---
CPO-3: Where It Prints
| Surface | What the customer sees |
|---|---|
| Invoice PDF, header block | `PO #: FY27-0142`, between Service Period and Invoice Date |
| Invoice PDF, remittance stub | `PO #:` line under the invoice number, so the returned stub carries it |
| Invoice email, Invoice Summary card | A PO number row under Customer |
| Per-site group email | One PO number row when every invoice shares the same number; otherwise each invoice line shows its own |
| Invoice detail (in the app) | A PO # row with an info icon explaining where the number came from |
Nothing changes on invoices for customers with no PO number. The line is simply absent.
---
CPO-4: Drafts Follow The Customer, Sent Invoices Keep Theirs
The rule that keeps a municipality's books and yours in agreement:
Fiscal-year rollover. Most municipalities start a new fiscal year on July 1 (some on October 1 or January 1) and issue a fresh blanket PO for it. When the new PO arrives, update the customer once. Invoices already sent stay on the old number; the next draft picks up the new one. If the customer bills in advance, be aware that a draft cut in late June for July service references whichever PO is on the customer when it is sent, so enter the new number before approving that draft, or schedule the send for the period's first day.
---