How to Invoice Corporate Clients: Accounts Payable, POs, and Getting Paid as a Freelancer

You invoice solo clients in a rhythm: PDF out, deposit back shortly after. Then a corporate client shows up with a vendor packet, a purchase order number, a portal you've never touched, and a finance team that runs on fixed payment dates.

Corporate invoicing runs on different rails. The invoice PDF might still be fine. Where freelancers lose time is the wrapper: who touches it next, what fields AP needs, and when cash actually moves.

This guide walks you from vendor setup through submission so your first corporate invoice doesn't park in a queue while your contact says they "forwarded it."

Quick Checklist

Before sending your first corporate invoice, confirm:

• Vendor onboarding complete (W-9, banking, address)
• PO number and any required reference codes
• Legal bill-to entity name (exact match to their records)
• AP submission channel (email, portal, or upload)
• Payment terms and payment run schedule
• Required tax forms submitted

Each step is covered in detail below.

---

Why Corporate Invoicing Works Differently

With a solo client or small shop, your buyer is often your payer. One inbox, one yes.

Inside a company with finance staff, the typical flow looks more like this:

• Procurement or a project manager approves the spend against budget or a signed order
• Accounts payable (AP) validates the invoice against that approval and queues payment
• Payment runs batch approved invoices and release funds on a set rhythm

Your document has to satisfy AP, not only your daily contact. That means accurate reference numbers, the legal entity name on their books, and delivery through whatever channel they've standardized on.

Wrong or blank fields often kick the invoice back or leave it stalled. You're not necessarily being ghosted. The system often won't advance the file until the checklist is complete.

---

Step 1: Finish Vendor Onboarding Before Your First Invoice

Most firms want a vendor profile on file before they'll pay you. Typical asks:

• W-9 (US): legal name and tax ID as they'll report them
• Bank instructions: ACH or wire details in the format they specify
• Address and contacts: aligned with how your invoice letterhead reads
• COI or insurance: common in regulated or facilities-heavy industries

Treat this like a gate, not paperwork theater. An incomplete vendor record can block payment even when the invoice line items look perfect.

Ask early what the path looks like and how long it tends to take. Some teams flip you on quickly; others need several weeks if legal or procurement has to countersign.

If the tax paperwork is what slows you down, W-9 for Freelancers walks through the fields and what 1099-NEC reporting means for you.

---

Step 2: Lock In the PO and Every Reference Field

A purchase order is internal permission to pay you. When a PO is required, AP typically won't post an invoice without a valid one on it.

Before you send invoice #1, confirm:

• PO number: does one exist, and should it appear on every invoice?
• Cost center or department code: some companies route invoices internally by code
• Project or job ID: ties spend to the approved scope
• Billing legal name: character-for-character what their vendor master file uses, not a nickname on Slack

One message before the first invoice saves multiple rounds later. Here's a template you can copy:

---

Hi [Name],

Before I send the first invoice, can you confirm:

1. The correct billing legal name for invoices
2. PO number (and whether it should appear on every invoice)
3. Any cost center, department, or project codes to include
4. How to submit (AP email, portal, or other)
5. Whether vendor onboarding is complete on your end

Want to make sure invoice #1 goes through cleanly. Thanks!

---

One missing field can reset you to the back of the line. Pull this during onboarding, not after AP has already rejected a PDF.

For how POs relate to invoices and receipts, Invoice vs. Receipt vs. Purchase Order lays out the distinction.

---

Step 3: Format the Invoice So AP Can Process It

AP clerks see volume. Your file should answer their questions in the first screen.

Every invoice should show:

• Your legal business name and address (matching vendor records)
• The client's legal entity (if their system says "Acme Corp, LLC," that full string belongs in the Bill To block)
• PO and internal codes their process requires
• Invoice number in a stable, consistent format
• Invoice date and due date matching the contract term
• Line items with descriptions, quantities, and rates (not one lump labeled "services")
• How to pay: bank info, payment link, or both
• Tax where your services and jurisdiction require it

Common bounce reasons include vendor name mismatches, missing POs, and line items that read like "consulting." Specifics help: "Brand strategy workshops, April 14–16, 2026" beats a blank "consulting" bucket.

For structure and formatting detail, see How to Create a Professional Invoice. If you charge sales tax, Sales Tax for Freelancers covers when to charge it and how to add it.

---

Step 4: Submit Where They Actually Want It

Not everyone takes a forwarded email. Common submission channels:

• Dedicated AP inbox (ap@company.com, invoices@company.com)
• Supplier portals such as Coupa, SAP Ariba, Tipalti, or an in-house workflow
• Controlled uploads to shared drive folders or procure-to-pay tools

During onboarding, ask plainly: portal or email? If portal, click through once when you're calm so your first rush invoice isn't also your platform tutorial.

Portal rejections are often blunt: wrong file type, a required commodity code left blank, a missing field the portal won't skip. Each bounce can push you to the next payment cycle.

If they accept email, make the subject line do routing work:

Invoice #1047, PO #4521, [Your Business Name], due June 30, 2026

For email delivery tips, see How to Email an Invoice to a Client.

---

Step 5: Map Their Payment Calendar

Enterprise payers run schedules, not vibes.

Patterns you may see:

• Net 30: due thirty days from invoice date
• Net 45 or Net 60: common at larger enterprises and some agencies
• Batch runs: items approved by a certain day might not move until the next scheduled release

Land your file right after a run closes and you wait for the next window. When you have slack, submit early in their processing week.

If you're used to Net 15 or "due on receipt," Net 45 or 60 is a cash-flow event, not a personality conflict. Two levers to consider before work starts:

1. Deposits or milestones so you aren't floating every hour for eight or nine weeks
2. Ask about early-pay discounts (for example, 2/10 Net 30). Not every company offers them, but some shared-services teams can route the request.

For a term glossary, see Invoice Payment Terms Explained.

---

Step 6: Follow Up on Their Clock, Not Yours

A polite nudge three days after uploading to a Net 45 account rarely accelerates anything. They're still inside their own SLA.

A sequence that matches how AP operates:

• Receipt check within a few business days: "Confirming Invoice #1047 landed complete for AP."
• Status ping about a week before the stated due date if you see zero movement
• Escalation through your project sponsor if you're past due, instead of cold-emailing a CFO you don't know

Your contact can often see status in the internal tool faster than you can from the outside.

If payment is seriously late, switch playbooks: When to Follow Up on an Invoice for a timeline, and How to Politely Ask for Payment for wording that works.

---

Front-Load the Details That Protect Cash Flow

The familiar risk with corporates isn't total nonpayment. It's delay. Net 60 already means two months best case. A PO typo or wrong entity name can add another cycle on top.

Before heavy execution:

• Close vendor setup before the first bill
• Document PO, codes, and legal bill-to name in your project file
• Use their channel of record
• Time submissions to their run calendar
• Negotiate deposits or milestones on anything that ties up significant hours

For a broader pre-project checklist, see Freelance Client Onboarding Checklist.

---

Get the Process Right Once

Procedural buyers pay when the package matches their machine. Nail vendor data, mirror their references, submit through the right door, and your repeat invoices become copy-paste with new dates and amounts.

When corporate clients need PO numbers, longer payment terms, and clean records, BillerBear helps you keep those details attached to the client and the invoice instead of scattered across email threads. Add PO references in your invoice notes or line-item descriptions, set due dates that match Net 45 or Net 60 terms, and generate PDFs that AP teams can process without follow-up questions.

Set it up once. The rest is repetition.