Net-30 vs Net-60: Why Your First Invoice Pays Late

You submit your first timesheet on a Friday. You are told payment is net-30. Thirty days pass. No deposit. You email your recruiter. The answer: ‘we’re waiting on the prime to pay us, then we pay you.’ Welcome to your first lesson in staffing cash flow.

This isn’t a red flag by itself. It’s how the industry’s payment chain actually works — and almost nobody explains it before you sign. If you understand the chain, you can price your risk, negotiate better terms, and stop panicking every time an invoice runs long.

This piece walks the mechanics: who pays whom, when, and the one clause that determines whether an upstream delay becomes your problem.

The Payment Chain: Four Clocks, Not One

A typical staffing engagement has at least three parties between your work and your bank account: you (or your corp-to-corp entity), the staffing vendor (prime or sub), and the end client. Sometimes there’s a second vendor layer in between. Each link runs its own clock.

• Timesheet cutoff: the client’s internal deadline for approving hours, often weekly or bi-weekly, sometimes tied to a specific day (e.g., hours must be approved by the following Tuesday).
• Client AP cycle: once approved, the client’s accounts payable department pays the prime vendor on its own schedule — commonly net-30, net-45, or net-60 from invoice date, not from work date.
• Prime vendor terms: the prime invoices the client, then pays its subcontractor (your agency, if you’re on a sub-vendor’s payroll) on the prime’s own terms — which may start only after the prime gets paid.
• Your pay terms: your staffing firm pays you — W-2, 1099, or corp-to-corp — on terms set in your own agreement, which may or may not be tied to the step above.

Four clocks. If each one is net-15 to net-20, your real time-to-cash can stretch past 60 days from the day you worked the hours — even though your contract says net-30.

Where the Delay Actually Lives

Most confusion comes from conflating two different net-30 clocks: net-30 from your invoice date versus net-30 from when the client pays the prime. Read your contract for which one applies.

If you’re two or three layers down from the end client — common in large enterprise and government-adjacent engagements — your payment terms are often written as ‘net-X from receipt of funds from client,’ not ‘net-X from invoice submission.’ That single phrase is the difference between predictable cash flow and an open-ended wait.

How to Find Your Actual Terms Before You Sign

Don’t assume. Ask these questions during the offer stage, in writing:

1. What is the timesheet approval cutoff, and what happens if the client approver is late or on vacation?
2. Is my payment term calculated from my invoice date, or from the date the vendor receives funds from the client?
3. What is the client’s actual AP cycle with this vendor — net-30, net-45, net-60? (Ask directly; vendors usually know because they’ve been burned before.)
4. Is there a cap on how long a payment can be delayed before I’m owed interest or can invoice independently?
5. Who do I contact if payment is more than 10 business days late?

If a recruiter can’t answer question 2 clearly, that’s information too. Vague answers on payment mechanics often mean the firm hasn’t mapped its own cash flow either.

Net-30 vs Net-60: What Changes for You

Neither term is inherently bad. Net-60 is standard in some large-enterprise and public-sector supply chains simply because the client itself runs on net-45 or net-60 AP cycles. The problem is signing net-60 while budgeting like you’re on net-15.

The One Clause That Protects You: Pay-When-Paid vs Pay-If-Paid

This is the clause that matters most when an upstream payment slips. It usually appears in your subcontract or MSA under a heading like ‘Payment’ or ‘Compensation.’

‘Pay-when-paid’ language sets a timing mechanism: the vendor must pay you within a set window after receiving client funds, but payment is still ultimately owed to you regardless of delay. ‘Pay-if-paid’ language is different and stricter: it makes the vendor’s obligation to pay you contingent on actually being paid by the client. If the client never pays — due to dispute, bankruptcy, or contract termination — a true pay-if-paid clause can leave you unpaid with no recourse against your direct vendor.

Before signing, find this clause and ask the vendor to confirm in plain language which version applies. If the contract is silent or vague, ask for it to be clarified to pay-when-paid with a hard outer limit — for example, ‘payment due within 15 days of client receipt, not to exceed 75 days from invoice date regardless of client payment status.’ That outer cap is what actually protects your cash flow when the chain breaks.

A Quick Pre-Signature Checklist

• Confirm whether your net-term clock starts at invoice date or at vendor receipt of client funds.
• Get the client’s actual AP cycle length from the vendor, not an estimate.
• Identify whether the payment clause is pay-when-paid or pay-if-paid.
• Request a hard outer-limit cap on payment timing, independent of upstream delays.
• Build your personal cash buffer to match the longest clock in the chain, not the shortest.

None of this is about distrust. It’s about reading the mechanics of a multi-party payment chain the same way you’d read an SOW scope line — carefully, and before you sign, not after your first invoice goes quiet.

If you want a second set of eyes on a contract’s payment terms before you sign, the Josh Pros LLC team is happy to look it over. Reach out at contact@joshpros.com or visit https://joshpros.com.

#ContractorPay #NetTerms #W2vsC2C #StaffingIndustry #ITConsulting #FreelanceFinance #PayWhenPaid #ContractTechJobs #CashFlowPlanning #TechContractors #StaffingAgency #ConsultingLife

Back to all insights