Non-PO Invoice Processing: What It Is and PO vs Non-PO

A non-PO invoice is a supplier bill that arrives without a matching purchase order, so your accounts payable team cannot just match it and pay it. Someone has to figure out what it was for, apply the right general ledger code, and find the person who can approve it. That manual coding and routing is where non-PO invoices eat AP hours and create most of the exceptions in a typical month. This guide covers what a non-PO invoice is, the difference between PO and non-PO invoices, real examples, how to process one, the journal entry, why they are harder, and how to automate the slow parts. The first slow step is almost always retyping the bill, so if you want clean line items to code from, drop your PDF or scanned invoices into the converter at the top of this page and get them back as Excel or CSV rows in seconds.

What is a non-PO invoice?

A non-PO invoice is a vendor invoice that is not tied to a purchase order. It comes from a purchase made outside the formal procurement process, so there is no PO to check it against. AP has to capture the invoice data, assign the correct expense account and cost center, and route it to an approver before it can be paid.

These are sometimes called expense invoices, and they are common for indirect spend: the small, recurring, or one-off costs a business runs up without raising a purchase order first. Because nothing was pre-approved, the work of validating and approving a non-PO invoice happens after the bill arrives instead of before the order was placed.

What is the difference between PO and non-PO invoices?

The difference between a PO and a non-PO invoice is whether a purchase order exists before the invoice arrives. A PO invoice references a purchase order, so it is effectively pre-approved and can be matched and paid with little manual review. A non-PO invoice has no purchase order, so AP must code it, find an approver, and approve it manually.

That single difference drives almost everything else. With a PO invoice, the buyer already agreed on the vendor, items, quantities, and prices, so AP just confirms the invoice agrees with the PO (and often the receiving report) and releases payment. You can read the document-level breakdown in our guide to the difference between a purchase order and an invoice. With a non-PO invoice, none of that pre-work exists, so the invoice cannot run through standard two-way or three-way matching. It has to be handled on its own.

What is a non-PO invoice example?

A non-PO invoice example is a monthly utility bill, a software subscription renewal, a legal or consulting fee, an employee expense reimbursement, or an office supply order placed without a purchase order. These are typically indirect or low-dollar purchases that recur or come up on short notice, where raising a PO first would slow the business down.

Common non-PO invoices include:

Utilities such as electricity, water, gas, and internet service
Software and SaaS subscription renewals
Professional services like legal, accounting, and consulting fees
Employee expense reimbursements and travel costs
Rent, insurance, and other contracted recurring payments
Small or urgent office and facilities purchases

Employee expense spend is a big slice of this category, and a lot of it is receipt-driven rather than invoice-driven. If your team digitizes those, you can turn receipts into clean rows with a dedicated receipt data extraction tool before coding them like any other non-PO cost.

How do you process a non-PO invoice?

You process a non-PO invoice by capturing its data, coding it to the right account, routing it to the correct approver, and posting it for payment once approved. Because there is no PO to match against, the coding and approval steps are manual, which is what makes non-PO processing slower than PO-based processing.

A typical non-PO workflow runs in five steps:

Capture the invoice. Pull the vendor, invoice number, date, amount, and line items off the PDF or scan and get them into your system. Manual keying is the slowest part, so most teams extract the invoice data to Excel or straight into their AP tool instead.
Code the invoice. Assign the general ledger account, cost center, and any tax or department codes. This is judgment work on a non-PO invoice because there is no PO to copy the coding from.
Route for approval. Identify who requested or benefits from the purchase and send the invoice to them for sign-off, plus any spend-threshold approvers.
Review and resolve. Handle anything missing or questionable, like an unclear description or a charge no one recognizes, before it moves forward.
Post and pay. Once approved, post the invoice to the ledger and schedule it for payment in line with the vendor terms.

The accuracy of step two depends on how clean step one is, so pulling correct line-item detail off the invoice up front saves rework later.

What is the journal entry for a non-PO invoice?

The journal entry for a non-PO invoice debits the expense account the purchase belongs to and credits accounts payable for the same amount. When you later pay the invoice, you debit accounts payable and credit cash or your bank account to clear the liability.

For example, a $1,200 consulting invoice with no PO would post as a debit to Consulting Expense of $1,200 and a credit to Accounts Payable of $1,200 when you record the bill. When you pay it, you debit Accounts Payable $1,200 and credit Cash $1,200. The reason coding matters so much on non-PO invoices is that this first entry is where the expense account gets chosen, and there is no purchase order steering it to the right place.

Why are non-PO invoices harder to process?

Non-PO invoices are harder to process because they carry no pre-approved purchase order, so AP has to determine the coding and the approver after the fact and often with incomplete information. They generate more exceptions, take longer to approve, and have more room for error than PO-based invoices.

Three things make them slow. First, the purchase details that a PO would normally supply are missing, so AP cannot simply copy them. Second, routing is unclear because the invoice does not say who ordered the work, and non-PO invoices often land in an individual's inbox rather than a central AP queue. Third, the manual coding step invites mistakes, which is why non-PO invoices show up so often in invoice exception reports. Getting the coding right the first time is the single biggest lever on speed here.

When should you use a non-PO invoice?

You should use a non-PO process for low-risk, low-dollar, or time-sensitive purchases where raising a purchase order first would add cost without adding control. Recurring utilities, subscription renewals, and contracted services are good candidates because the spend is predictable and a PO adds little protection.

For larger or higher-risk purchases, a PO is usually worth the extra step because it locks in price and quantity before the money is committed and lets AP match the invoice automatically. Many finance teams set a dollar threshold above which a PO is required, and treat everything below it, plus a defined list of indirect categories, as non-PO.

How do you reduce the number of non-PO invoices?

You reduce non-PO invoices by raising PO coverage: set a spend threshold above which a purchase order is required, route common indirect categories through a simple buying process, and educate budget owners to request a PO before they commit. The goal is to move predictable spend onto POs so AP can match it instead of coding it by hand.

You will never get non-PO invoices to zero, and you should not try. Some spend genuinely cannot wait for a PO. The realistic target is to push routine, repeatable spend onto purchase orders so your team only handles non-PO invoices where they truly make sense, which keeps the manual coding workload small.

How do you automate non-PO invoice processing?

You automate non-PO invoice processing by capturing the invoice data automatically, applying coding rules based on the vendor and history, and routing the invoice to approvers through a workflow instead of by email. Automation cuts the manual data entry and standardizes the coding, which is exactly where non-PO invoices lose time.

Start with capture, because it is the step that touches every invoice. Converting each PDF or scan into structured rows removes the retyping and feeds clean data into the coding and approval steps. From there, automating the data entry and using invoice processing software to apply coding rules and route approvals turns a slow manual chain into a mostly hands-off flow. Teams that do this consistently report a real drop in cost per invoice. Non-PO invoices also tend to arrive scattered across individual inboxes, so a tool that can parse invoices out of email helps you pull them into one place before coding, and an accounts payable automation platform can carry them from approval through to payment.

Non-PO invoices are not going away, but the manual grind around them can shrink a lot. The fastest win is to stop retyping: convert every non-PO invoice to clean Excel or CSV rows with the invoice converter at the top of this page, then spend your time on the coding and approval decisions that actually need a person.