The "Invoice Approval Map" for Mid-Market Clients

You’ve done the work. The project manager loves it. And your invoice is sitting in a queue somewhere between the department VP, the finance controller, and an AP clerk who runs payment batches on Wednesdays. Nobody is avoiding you. The invoice is just navigating a system you’ve never seen.

The Mid-Market Approval Stack

Mid-market companies, 50 to 500 employees, have enough process to route invoices through multiple approvers, but not enough automation to make it fast. The typical stack:

1. Project manager, confirms the work was completed
2. Department head or VP, approves the budget spend
3. Finance controller, checks vendor compliance, W-9, insurance requirements
4. AP clerk, schedules the payment in the next payment run (often weekly)

Each step adds 2–5 days. An invoice that enters the stack on a Thursday may not reach AP until the following Wednesday’s payment run, that is 12 days for a process that takes 20 minutes of total human attention.

The 5-Question Invoice Approval Discovery

Run this discovery during contract kickoff, ideally in the same conversation where you discuss scope and timeline.

Question 1: “Who needs to approve my invoices before payment releases?” This names the chain. Write down every person they mention.

Question 2: “What information does your AP system require on an invoice?” Some companies require a PO number. Others require a vendor ID, a cost center code, or a specific billing address. Missing any of these fields can send your invoice back to start.

Question 3: “Do you use a vendor portal like Coupa, Ariba, or Tipalti?” If yes, you must register before your first invoice. Email submission often bypasses the system entirely and gets lost.

Question 4: “Should I CC anyone when I send an invoice?” Often the project manager wants a copy. Sometimes the controller does. Knowing this means your invoice lands in the right inboxes on the first send.

Question 5: “What is your standard payment cycle, weekly, bi-weekly, monthly?” This tells you when to follow up. If payment runs are on the 1st and 15th, an invoice received on the 16th waits nearly a month. Timing your invoice submission to arrive 3–5 days before the payment run improves your position in the queue.

These five questions take four minutes to ask and routinely recover 10–14 days of collection time on every invoice you send to that client.

Building Your Approval Map Document

Keep a one-page reference for each mid-market client that includes: the approval chain by name and title, the required invoice fields, the vendor portal URL and login, the payment run schedule, and the primary AP contact email.

Update it when contacts change, finance teams have high turnover. Before every invoice, spend 30 seconds checking whether anyone on the chain has left the company.

The PO Number is Non-Negotiable

If a client uses purchase orders, your invoice must include the PO number in the exact format their system expects. An invoice that says “PO 1234” when the system expects “PO-1234-2026” may fail automated matching and go back into the human review queue.

Ask for the exact PO number format during the 5-question discovery, and ask for a new PO number at the start of every project or fiscal year. Many companies issue new POs annually.

When to Escalate vs. When to Wait

Use this timing framework after an invoice is submitted:

• Day 5: Confirm receipt with the project manager by email. Brief, not accusatory.
• Day 14 (before due date): Check in with AP contact or the person who told you the payment cycle.
• Day 3 after due date: Send a formal reminder with the invoice attached. Include the PO number and the approval chain member names.
• Day 10 after due date: Escalate to the VP or budget owner, not AP. Frame it as a process question, not a complaint: “I want to make sure this hasn’t gotten stuck somewhere in approval.”

Never skip straight to the budget owner, exhaust the AP contact first. But do not wait past 10 days overdue before escalating up the chain.

The Approval Map Advantage Over Time

After your first payment cycle with a mid-market client, you have a map. The second invoice goes through faster because you know the format, the portal, and the cycle. By the third invoice, you have optimized submission timing and are rarely chasing payment.

Freelancers who skip the discovery question every time start over with every new client. Freelancers who build and maintain approval maps get paid faster with less friction on every subsequent invoice.