AP stall tactics: what they look like from the collection side

Every collector hears the same lines. After years of working software and technology receivables, certain phrases arrive so predictably that they've become a kind of vocabulary—a set of signals that tell you, with reasonable accuracy, what's actually happening on the other side of the phone and what the realistic timeline to payment looks like.

This article is written for the other side of those conversations: the CFOs, controllers, and AR managers at software companies who are hearing these phrases from their own customers and wondering what they actually mean. Understanding AP delay from the inside makes the appropriate response much clearer.

“It’s in the queue” / “It’s being processed”

What it means: The invoice exists in the AP system. It has not been approved for payment. "In the queue" is a true statement that reveals almost nothing about when payment will occur.

When it's legitimate: Large enterprise AP departments run on batch processing cycles. Some pay weekly, some bi-weekly. An invoice that arrived on day 12 of a 14-day cycle may genuinely be 12 days from payment. This is most common and most legitimate in enterprise accounts where you have a good payment history.

When it's a stall: When "in the queue" is followed by the same response two weeks later, and again two weeks after that. Legitimate queue processing resolves in one to two cycles. Three weeks of "in the queue" means the invoice has been flagged, held for approval, or deprioritized—not that it's moving through a normal workflow.

Appropriate response: Ask for a specific payment date. A real queue has a timeline; a stall cannot produce one.

“We need a new W-9” / “You’re not in our vendor system”

What it means: A documentation requirement has surfaced that is blocking payment processing. This is one of the oldest delay tactics in enterprise AP, and it works because it shifts the burden to the vendor to provide documentation before payment can proceed.

When it's legitimate: New vendor onboarding genuinely requires W-9 and sometimes additional documentation. If this is the first or second invoice with a customer, this may be real process.

When it's a stall: When a customer who has been paying you for 18 months suddenly needs a new W-9. Your information hasn't changed; their motivation has. This tactic surfaces when a customer is buying time—often because payment approval is delayed internally—and it buys them 2–4 weeks while "vendor verification" proceeds.

Appropriate response: Provide the document immediately and confirm in writing the date you sent it and the commitment to pay within X days of receipt. The documentation removes their excuse; the written confirmation creates accountability.

“Awaiting approval from [executive / procurement / legal]”

What it means: The invoice has been escalated to someone with authority, and that person has not yet acted on it. This is sometimes true. It is also frequently invoked as a delay tactic because it introduces a vague third party who is hard to verify or contact.

When it's legitimate: Large invoices, new vendors, or invoices that exceed AP authority thresholds genuinely require executive approval. If your invoice is above the customer's standard AP authorization limit, this is expected process. It typically resolves in 1–3 weeks.

When it's a stall: When the executive in question changes—"now it needs to go to the CFO" replacing "now it needs procurement sign-off"—or when the approval has been "pending" for more than 30 days. Legitimate approvals don't take a month. A rotating series of unnamed approvers is a classic delay architecture.

Appropriate response: Ask for the approver's name and contact information. A legitimate approval process has a real person attached to it. If the AP contact can't or won't provide a name, the approval isn't real.

“We dispute the invoice”

What it means: The customer is claiming the invoice amount is incorrect, the work wasn't performed, or the service wasn't delivered as contracted. This is the nuclear option in AP delay tactics because it suspends the payment obligation (from their perspective) and shifts the conversation to a dispute resolution process that can run indefinitely.

When it's legitimate: Genuine billing errors exist. Usage overcharges happen. Service delivery failures occur. A customer who raises a specific, documented dispute with evidence deserves a response and a resolution process.

When it's a stall: When the dispute is vague ("we're reviewing the charges"), when it arrives after the invoice has been outstanding for 45+ days, when the customer cannot specify which line items they dispute or why, or when it follows a pattern—disputes tend to surface at payment-critical moments for the customer (end of quarter, budget reset) rather than at invoice receipt. A customer with a legitimate dispute raises it promptly; a customer stalling raises it when you escalate.

Appropriate response: Request the dispute in writing, with specific line items and the basis for disagreement, within 10 business days. Offer to provide usage documentation. If no written dispute materializes, it wasn't a real dispute—it was a tactic—and you can treat it accordingly in your escalation process.

“We’re going through a system migration” / “We just changed AP platforms”

What it means: A technology transition is being cited as the reason payment cannot be processed on the normal timeline. ERP migrations are real; they do occasionally delay AP cycles for 4–8 weeks during cutover.

When it's legitimate: Major ERP migrations (SAP, Oracle, NetSuite implementations) are 12–18 month projects with real transition periods. If a customer's migration is visible—they've mentioned it previously, it's referenced in their public communications, it's consistent with their company size—the delay may be genuine.

When it's a stall: When the migration has been ongoing for 4+ months, when it doesn't affect other vendor payments (only yours), or when you've never heard about it until you escalated an overdue invoice. System migrations don't stop all payment processing—they create selective delays in specific workflows. If your invoice is the only one affected, it's not the migration.

What the pattern of stalls tells you

One stall tactic, one time, on one invoice, from a customer with a good history: normal business process, handle internally.

Two different stall tactics across two consecutive invoices: elevated monitoring, senior escalation internally.

Three or more contacts resulting in different delay explanations with no payment: this account needs external escalation. The customer has made a decision—conscious or institutional—not to prioritize your payment. Internal escalation will not change that; it will only cost you time while the account ages.

We recover accounts from customers who are fluent in all of these tactics. The reason we can is that we've heard them enough times to know exactly what each one means, what follow-up produces movement, and when to stop negotiating and start enforcing. The cost of learning that pattern yourself is months of aging receivables.