What AP Teams Want on an Invoice, Field by Field
· 5 min read
An accounts payable clerk opens your invoice, glances at the header, scans for a PO number, checks the billing entity, and decides in about fifteen seconds whether it goes into the pay run or the exception pile. The exception pile is where 50-day-old invoices live. If you want to stay out of it, your invoice has to answer every question AP will ask before they have to ask it.
Here is what AP teams want, and why, based on how their workflow actually runs.
Match the billing entity to the one on the PO, exactly
If the PO says "Acme Holdings UK Ltd" and your invoice says "Acme Ltd", the invoice will sit. AP cannot pay an entity that does not match what procurement approved. This is the single most common reason invoices bounce back, and it has nothing to do with the work you did.
The fix is not to guess. Ask your contact for the exact legal entity and registered address before you issue, or let the client correct it themselves on the invoice. A tool that supports letting your customer edit their own invoice turns this from a three-email loop into a thirty-second amendment. The recipient updates the billing entity, you get notified, and the invoice is now payable.
Put the PO number on the invoice, in a place AP will find it
Most AP systems index invoices by PO number. No PO, no match, no payment. Put it in the header near the invoice number, not buried in the line item description. If your client uses PO numbers and you do not have one yet, do not send the invoice. Send an email asking for it first, or use a PO number format checker to confirm the value you were given even looks right for that client's system.
If you regularly forget this step, read why a missing PO number quietly kills your invoice. It is the cheapest fix in the entire AR process.
Address the invoice to AP, not your day-to-day contact
Your project sponsor is not the person who pays you. They approve the work, then forward the invoice to AP, often days late, sometimes never. If you can capture the AP email address up front and put it on the invoice, you remove a handoff. Better: send the invoice somewhere both the project contact and AP can see it, so the project contact can approve and AP can process in parallel.
Include the line items AP needs to code the expense
AP codes invoices to general ledger accounts and cost centers. They cannot do that from a line that says "Consulting services, $12,000". Break work into items that map to what was ordered: "Phase 2 discovery workshop, 3 days" or "April retainer, senior developer, 40 hours". If the PO has line items, mirror them. If it has a single value, match the total exactly.
For hourly work, show the rate and hours, not just the extended total. AP will check the math. So will the project sponsor when they approve.
State the payment terms and the due date as a calendar date
"Net 30" alone is ambiguous. Net 30 from issue? From receipt? From month-end? Put both the term and the resolved date: "Net 30, due 14 May 2025". An invoice due date calculator will resolve this in a second. If you want context on why this matters more than people think, see why Net 30 invoices pay late.
Give complete remittance details, currency first
AP needs to know what currency to pay in and where the money goes. For domestic payments that usually means account number and routing or sort code. For international, IBAN and SWIFT/BIC, plus the beneficiary name exactly as it appears on the bank account. Mismatches between the invoice name and the bank account name will get the payment returned. If you take payments in multiple currencies, issue the invoice in the currency the client agreed to, not yours.
Make the invoice number unique, sequential, and legible
AP enters your invoice number into their system as the duplicate-payment guard. If it collides with something you sent last quarter, they will reject it. If it has slashes or spaces their system does not accept, they will reject it. Pick a format and stick to it. Set a numbering scheme once and let it auto-increment so you cannot accidentally reissue 2024-0142.
Quote first, invoice second, and keep them linked
If the work started from a quote, reference the accepted quote on the invoice. AP loves this because it ties their three-way match together: PO, receipt of goods or services, invoice. A tool that handles quotes that the client accepts by signing their name gives you a clean paper trail when AP asks where the price came from.
Make it easy to request changes without restarting
Sometimes AP needs a small tweak: different billing address, currency they actually pay in, payment terms they negotiated company-wide. If your process is "void the invoice and reissue", you have just bought yourself another approval cycle. A better process lets AP propose the change in place, you approve or decline, and the invoice updates with a tracked version. The original is still there. The audit trail is intact. Every edit becomes a version you can revert, which is what auditors want anyway.
Send it as a link, not just a PDF attachment
Email attachments get lost, get the wrong revision attached, and create the back-and-forth loop where nobody knows which PDF is current. A shared link points to one source of truth. AP can forward it internally, the project sponsor can approve, and you can see when it was viewed. If you want to stop sending attachments entirely, create your next invoice as a link and never email a PDF V3_final_FINAL.pdf again.
Before you hit send on the next one, run through the list above. Entity matches the PO. PO number in the header. Line items code cleanly. Due date is a calendar date. Bank details match the beneficiary name. Invoice number is unique. If all six are true, you have removed almost every reason AP would have to slow you down.