How to Manage Subconsultant Pay Requests
Without the End-of-Phase Scramble
Subconsultant pay requests are predictable in one way — they tend to arrive all at once, right at the moments when cash flow is already under the most pressure. Here's how to build a pay request process that connects to accrued liability, moves through approval without backlogs, and never produces a cash flow surprise.
Why Pay Requests Feel Like Surprises — Even When They Shouldn't
Pay requests are not random events. They follow the project. They arrive at phase milestones, at project closeout, and at the natural billing points in a consultant's agreement.
In theory, a firm that knows its project schedule should never be caught off guard by a pay request.
In practice, most firms are caught off guard regularly — because the pay request is the first moment the firm sees the liability it has been carrying for weeks.
That is an information problem, not a timing problem.
A firm that tracks accrued subconsultant liability from the moment of client invoicing already knows what is coming before any pay request arrives. The pay request is not a surprise. It is a confirmation. The review process becomes a verification — checking the submitted amount against what the system already shows — rather than a discovery.
A firm running on AP-only tracking has no advance visibility. Every pay request is new information. When three or four arrive in the same week at a phase milestone, the firm is scrambling to reconcile obligations it should have been tracking for months.
The pay request process described here assumes the first case — that liability is already accrued and visible before any pay request lands. That foundation changes what the review process looks like and how long it takes.
If your firm is still in the second case, the first priority is accrued liability tracking. Everything else follows from that.
→ Read: Subconsultant Liability: The Cash Flow Risk Most A/E Firms Don't See Coming
A pay request should confirm what the system already knows — not introduce new information.
When liability accrues upon client invoicing, the pay request serves as a verification step. When it doesn't, the pay request is a discovery. That distinction determines whether the review process takes minutes or days.
What a Pay Request Should Include
Before reviewing a pay request, the firm needs to know what to expect in it. Inconsistent pay request documentation is one of the most common sources of processing delays and payment disputes in A/E firms.
A complete subconsultant pay request should include:
Project identification — the project name and number, clearly stated so the pay request can be matched to the correct project file without ambiguity.
Phase or scope reference — which phase of the project the pay request covers. This is the linkage that connects the submitted amount to the accrued liability on the books. Without a phase reference, the firm cannot verify the pay request against the agreement without additional research.
Period of service — the dates covered by the pay request. This matters both for verification and for timing — a pay request covering a period in which no client invoicing occurred should be flagged for review.
Amount requested — the amount being billed, broken down in a way that allows verification against the consultant agreement. For fixed-fee consultants, this is typically a percentage of the phase fee based on completion. For hourly consultants, it should include a time log or summary.
Cumulative billing to date — how much the consultant has billed in total on this project, compared to the total consultant agreement value. This prevents overpayment and immediately makes it visible when a pay request would push the cumulative total above the contracted amount.
Supporting documentation — for hourly consultants, a time log or invoice detail. For fixed-fee consultants, a completion percentage with a brief narrative is typically sufficient.
Firms that establish clear pay request requirements in the consultant agreement — and communicate them at project kickoff — receive pay requests that are easier to review and faster to process. Firms that accept whatever format the consultant provides spend significantly more time reconciling and requesting additional information.
Setting expectations upfront
The time to establish pay request requirements is at the beginning of the project, not at the first pay request review.
A brief section in the consultant agreement — or a standard kickoff communication — that outlines the required format, the expected billing cycle, and the approval timeline sets clear expectations on both sides. Consultants who know what is required submit pay requests that meet those requirements. Those who don't know default to their standard format, which may or may not include what the firm needs.
The most common cause of pay request processing delays is missing information — not workload.
A pay request that arrives without a phase reference, a period of service, or cumulative billing to date requires follow-up before it can be reviewed. That follow-up adds days to the process. Setting documentation requirements upfront eliminates most of it.
The Pay Request Review Process
Once a pay request arrives with complete documentation, the review should move through four steps.
Step 1: Match to the project and phase
Confirm the pay request is for an active project and that the phase referenced exists in the project file. This sounds obvious — but pay requests occasionally arrive for projects that have closed, phases that have been superseded, or with project numbers that don't match the firm's records. Catching these at step one prevents more complicated reconciliation later.
Step 2: Compare to accrued liability
Check the submitted amount against the accrued liability on the books for that project and phase.
There are three possible outcomes:
The submitted amount matches the accrued liability — the most common case. The consultant has billed what the system expected based on the work completed and the client's invoicing to date. Review proceeds to step three.
The submitted amount is less than the accrued liability — the consultant is billing for less than the accrued amount. This may reflect a timing difference — the consultant is submitting a partial pay request and will bill the remainder later — or a completion percentage that differs from the firm's estimate. Note the difference and proceed. The remaining accrued amount will carry forward.
The submitted amount exceeds the accrued liability — the most important case to catch. The consultant is billing for more than what the firm has accrued based on client invoicing. This could mean the consultant's completion percentage is ahead of the phase billing, that the scope has expanded without a change order, or that there is an error in either the pay request or the firm's accrual calculation. This requires investigation before approval.
Step 3: Verify against the consultant agreement
Confirm the submitted amount is consistent with the consultant agreement — the fee basis, the phase allocation, and any caps or milestones that govern when amounts are payable.
For fixed-fee consultants, confirm the completion percentage applied to the phase fee is consistent with the work performed and the phase status.
For hourly consultants, review the time log against the phase budget. Flag any billing that would put the cumulative total above the contracted amount or the NTE limit.
Check cumulative billing to date — adding the current pay request to all previous pay requests — against the total consultant agreement value. If the cumulative total exceeds the contracted amount, the pay request must be reviewed before approval, regardless of the individual line items.
Step 4: Approve and record
Once the pay request passes review, approve it through the appropriate workflow and record the payout against the project and phase.
The payout should close the loop on the accrued liability — reducing the outstanding balance by the approved amount. The remaining accrued liability on the project is the difference between total accrued and total paid — the firm's remaining consultant obligation for that project.
Who owns the approval
Pay request approval should have a clear owner — typically the project manager for the project in question, with principal review for amounts above a defined threshold.
Approval workflows without a defined owner create backlogs. Pay requests sit unreviewed because no one is certain who is responsible for them. Consultants follow up. The firm looks disorganized. Payment delays create friction in the consultant relationship, affecting future project quality.
A simple rule: the project manager who oversees the consultant relationship reviews and approves pay requests for their projects, with a defined escalation path for amounts above a threshold or for any pay request that fails step two or step three.
→ Read: Subconsultant Management for A/E Firms: The Complete Guide
When a pay request exceeds the accrued liability, something has changed — and it needs to be understood before the check goes out.
The most common causes are scope expansion without a change order, a consultant completion percentage that has moved ahead of phase billing, or an error in one of the two figures. None of these should be approved without review. All of them are easier to resolve before payment than after.
Timing Pay Requests Against Client Collections
The relationship between consultant pay requests and client collections is one of the most practically important cash flow questions in A/E firm management — and one of the least discussed.
The core tension: consultants want to be paid promptly after submitting a pay request. Firms want to pay consultants from client collections corresponding to the same phase of work. When those two timing pressures are misaligned, the firm is advancing payment to consultants from its own operating cash before the client has paid.
This is not unusual. It is an inherent feature of how A/E projects are structured. The question is whether the firm is managing the timing deliberately or discovering the gap after the fact.
The payment timing options
Some firms pay consultants on a fixed cycle — 30 days from receipt of the pay request — regardless of the client's payment status. This is simple and predictable for the consultant, but it exposes the firm to timing risk when client payments are delayed.
Some firms pay consultants only after receiving client payment for the corresponding phase. This eliminates the firm's timing risk but creates unpredictability for the consultant, requiring clear communication in the agreement.
Some firms use a hybrid — paying within a set number of days after client payment is received, with a maximum delay. This balances the interests of both parties and can be structured into the consultant agreement upfront.
There is no universally correct approach. The right choice depends on the firm's cash position, the consultant relationship, the project size, and the structure of the consultant agreement.
What matters is that the approach is deliberate and documented — not defaulted into by habit or discovered as a problem at phase closeout.
The role of retainage
Some consultant agreements include retainage — a percentage of each pay request held back until project completion. If the client contract includes retainage on the firm's invoices, structuring parallel retainage in consultant agreements protects the firm's cash position during the project.
Retainage in consultant agreements should be stated explicitly — the percentage held, the conditions for release, and the timeline for final payment — so both parties understand the arrangement from the start.
What the system should show
A firm managing consultant payment timing well can answer at any moment:
- Which approved pay requests are outstanding — approved but not yet paid?
- What is the total amount approved but unpaid across all active projects?
- For each outstanding pay request, has the corresponding client payment been received?
- Which projects have consultant obligations that are approaching or exceeding the client collections received for the same phase?
These questions require the system to connect consultant pay request data to client billing and collection data — not just track them in separate modules.
→ Read: WIP Management for Architecture & Engineering Firms
→ Read: Realization Rate for A/E Firms
Cut Your Billing Time by 60% Within 90 Days — Or We Refund Every Penny
We're so confident BaseBuilders will transform your billing process that we're putting our money where our mouth is.
BaseBuilders’ easy-to-use software is specifically designed to help small to mid-sized firms track time, manage projects, stay on top of expenses, and more. We’ll handle the invoicing for you so you can focus on growing your firm and designing wonderful spaces.