The Fundamental Problem With How Most Firms Track Consultant Costs

Architecture and engineering firms rely on subconsultants for nearly every project of meaningful size. Structural engineers, MEP engineers, civil engineers, landscape architects, geotechnical consultants, surveyors — the list varies by project type, but the financial management challenge is consistent.

Every dollar of consultant work you oversee creates a liability — an obligation to pay the consultant for that work. The question is not whether the liability exists. It is whether your firm knows about it before the consultant submits a pay request.

Most A/E software tracks consultant costs through accounts payable. A pay request arrives. You enter it. Now you have a liability.

That is the wrong moment to discover the obligation.

The liability was created the moment you billed your client for work that included consultant services. A portion of that invoice — based on your consultant agreements — was never fully yours. Whether the consultant has asked for it yet is irrelevant to the financial reality. The committed funds are sitting in your account, looking like available cash, right up until the pay request lands.

This is not a minor accounting nuance. It is a cash flow problem that repeats on every project, at every phase milestone, for every firm that carries significant consultant spend.

The solution is not better spreadsheets. It is a system that accrues liability at the time of client invoicing — not at the time of consultant billing.

→ Read: Subconsultant Liability: The Cash Flow Risk Most A/E Firms Don't See Coming

How Subconsultant Liability Actually Works

Understanding how liability accrues — and when — is the foundation of everything else in subconsultant management.

The moment liability is created

When you sign a consultant agreement for a project, you create a conditional obligation — contingent on the work being performed. When the work is performed and you bill your client for a phase that includes that consultant's work, the obligation becomes real. The consultant has earned their fee. Whether they have submitted a pay request is a billing timing question, not a liability question.

The liability exists at the moment of client invoicing. That is when it should appear in your books.

The AP-only blind spot

Most A/E software records consultant liability when a pay request is submitted — not when the client is invoiced. This means the system only knows what consultants have told it. Work that has been billed to the client but not yet invoiced by the consultant is invisible.

For a firm invoicing $400,000 to clients in a billing cycle with 30% consultant spend, $120,000 of that revenue is already committed — and completely invisible in an AP-only system. That $120,000 appears as available cash until pay requests arrive. When they arrive in clusters at phase milestones — as they routinely do — the firm is suddenly managing obligations it should have anticipated weeks earlier.

What accrual-based tracking shows instead

When liability accrues at the time of client invoicing, the picture changes entirely.

The moment a client invoice goes out, the system calculates and posts the portion attributable to each consultant based on the agreement tied to that project phase. The accrued liability is visible immediately — before any pay request arrives.

At any moment, the firm can see how much has been accrued in consultant obligations across all active projects, how much of the current cash position is genuinely available after those obligations are accounted for, and where the largest liability exposures sit across the portfolio.

No spreadsheets. No phone calls. No surprises.

The Four Components of Complete Subconsultant Management

Subconsultant management is not a single workflow. It is four interconnected processes that need to work together for the firm to have an accurate picture of its consultant financial position at any time.

1. Accrued Liability Tracking

The foundational layer. Every client invoice that includes consultant work should trigger an automatic calculation of the associated consultant obligation — posted as a liability the moment the invoice goes out.

This requires consultant agreements to be linked to project phases, so the system knows which consultant is tied to which phase and at what rate or percentage. When that linkage is in place, liability calculation is automatic. When it is not, the firm is tracking liability manually — or not at all.

The questions accrued liability tracking should answer at any moment:

• What is the firm's total accrued consultant liability across all active projects?
• Which projects carry the largest outstanding obligations?
• For each project, what is the spread between accrued liability and pay requests received?

→ Read: Subconsultant Liability: The Cash Flow Risk Most A/E Firms Don't See Coming

2. Pay Request Management

When a consultant submits a pay request, the firm needs to review it against the accrued liability already on the books, verify it against the consultant agreement and the project phase it covers, approve it through the appropriate workflow, and record the payout against the project.

A clean pay request process does not create accounting surprises — because the liability was already known. The pay request is confirmation of an obligation that was already visible, not a new piece of information.

The most common pay request problems in A/E firms:

• Pay requests that exceed the accrued liability for a phase — often because scope expanded without a corresponding consultant change order
• Pay requests that arrive without sufficient documentation to verify the phase and amount
• Pay request backlogs that accumulate when the review and approval process lacks a clear owner
• Timing mismatches between when pay requests are approved and when client payments are received — leading to cash flow pressure at phase closeout

The right system handles all of these by connecting pay requests to the accrued liability already recorded, making it immediately visible when a submitted amount is out of alignment with what the system expected.

→ Read: How to Manage Subconsultant Pay Requests

3. Pass-Through and Markup Billing

When a client pays for consultant work, there are two ways to structure how that cost appears on the invoice — and the choice has meaningful implications for revenue recognition, margin reporting, and the firm's apparent financial performance.

Pass-through billing records consultant costs as a direct pass-through to the client. The firm invoices the client for the consultant's fee at cost, collects that amount, and pays the consultant the same amount. No markup is added. The revenue and expense net to zero from the firm's perspective — the consultant cost is not the firm's revenue, and paying the consultant is not the firm's expense.

Markup billing adds a percentage to the consultant's fee before billing the client. The markup represents the firm's coordination fee — compensation for managing the consultant relationship, reviewing their work, and carrying the liability between client invoicing and consultant payment. The markup portion is the firm's revenue. The consultant's base fee remains a pass-through.

Both approaches are legitimate. The choice depends on the firm's fee structure, the client relationship, and how the work was presented in the proposal.

What matters most is consistency — applying the same approach across all consultant billing on a project, documenting the method in the proposal and contract, and making sure the billing system reflects the agreed approach clearly on every invoice.

The financial reporting implications are significant. Firms that bill consultant costs as pass-throughs will show lower total revenue than firms that mark them up — even if both firms are doing identical work with identical underlying fees. When evaluating firm performance using total revenue as the basis, this difference distorts comparisons across projects, across years, and against industry benchmarks. Net revenue — which excludes pass-through consultant costs — is the accurate basis for financial performance analysis.

→ Read: Pass-Through vs Markup: How to Bill Subconsultant Costs to Clients

→ Read: Stop Measuring Profit the Wrong Way

4. Payout Tracking

The final layer — the record of what has actually been paid to each consultant, against each project phase, in each billing cycle.

Combined with accrued liability and pay requests received, payout tracking gives a complete financial picture of the firm's consultant position on any active project:

• Accrued liability — what is owed based on client billings
• Pay requests received — what consultants have submitted
• Payouts made — what has actually been paid
• Outstanding balance — the difference between accrued liability and payouts made

That outstanding balance is the firm's true remaining consultant obligation on the project — the amount that will need to be paid before the project can close without a financial surprise.

How Consultant Agreements Drive Everything Downstream

Subconsultant management starts before the first invoice is sent. It starts when the consultant agreement is structured and linked to the project.

The agreement determines three things that drive every downstream calculation:

The fee basis — is the consultant paid a fixed fee for a defined scope, hourly against a budget, or as a percentage of the project fee? Each structure requires different tracking and creates different liability profiles.

The phase linkage — which project phases does the consultant's work correspond to? When consultant phases are linked to project phases, liability can accrue automatically as client invoices go out for each phase. When they are not linked, accrual tracking is impossible without manual calculation.

The billing method — is the consultant cost billed to the client as a pass-through, with markup, or included within the firm's fee? The billing method needs to be established in the agreement and reflected consistently in every invoice that includes consultant work.

Firms that structure consultant agreements clearly — with defined phases, defined fees, and a defined billing method — have subconsultant management that largely runs itself. Firms that use vague or informal consultant arrangements create manual work and financial uncertainty on every project that consultant touches.

What Your Software Should Be Tracking — and What Most Platforms Miss

Not all A/E software handles subconsultant management the same way. The differences between platforms matter more than most buyers realize before they've been caught off guard by a liability blind spot.

The questions worth asking before committing to any platform:

Does liability accrue at time of client invoicing or time of pay request receipt?

This is the most important question. AP-only tracking records liability when a pay request arrives. Accrual-based tracking records it the moment the client invoice goes out. For firms carrying meaningful consultant spend, this difference directly determines whether the firm's cash position is visible in real time or only after the fact.

Are consultant phases linked to project phases?

Without this linkage, automatic liability accrual is not possible. The system cannot know what portion of a client invoice is attributable to each consultant unless the consultant's scope is mapped to the project phase being billed.

Can you see the full spread between billed, accrued, received, and paid?

The complete picture requires four numbers: what has been billed to clients for consultant work, what has been accrued as consultant liability, what pay requests have been received, and what has actually been paid. Platforms that only show one or two of these leave the firm working with an incomplete picture.

How are pass-throughs and markups handled on client invoices?

The system needs to support both approaches, apply them consistently, and reflect them correctly in revenue reporting. Platforms that treat all consultant costs the same way regardless of billing method create reporting distortions that compound over time.

Both Monograph and BQE Core track consultant costs through accounts payable — meaning liability is recorded when a pay request is submitted, not when the client is invoiced. For firms with straightforward consultant arrangements and low consultant spend, the gap may be manageable. For firms carrying significant subconsultant spend across multiple active projects, the blind spot is a recurring cash flow risk.

→ Read: How to Evaluate A/E Software for Subconsultant Management

→ See: BaseBuilders vs Monograph

→ See: BaseBuilders vs BQE Core

How BaseBuilders Handles Subconsultant Management

In BaseBuilders, subconsultant phases are linked directly to project phases. When a client invoice goes out for a phase, the system immediately calculates and posts the associated consultant liability — based on the consultant agreement tied to that phase.

At any moment, any principal in the firm can see the complete picture for every active project:

• Accrued liability — what is owed to consultants based on client billings, whether or not pay requests have arrived
• Pay requests received — what consultants have submitted
• Payouts made — what has actually been paid
• Pass-throughs — consultant costs billed directly to the client at cost or with markup

The result: the firm always knows how much of its billed or collected revenue is genuinely available — and how much is already committed to subconsultants.

No spreadsheets. No phone calls. No surprises at phase closeout.

Subconsultant Management Deep Dives

These articles break down each component of subconsultant management — with practical guidance for applying them to real A/E projects.

Subconsultant Liability: The Cash Flow Risk Most A/E Firms Don't See Coming
‍Why AP-only tracking creates a dangerous blind spot — and what accrual-based tracking looks like in practice.

How to Manage Subconsultant Pay Requests
‍How to review, approve, and process pay requests without surprises — connected to the liability you've already accrued.

Pass-Through vs Markup: How to Bill Subconsultant Costs to Clients
‍How to decide between pass-through and markup billing — and how each choice affects revenue, margin, and financial reporting.

How to Evaluate A/E Software for Subconsultant Management
‍The questions to ask before committing to a platform — and why the answers matter more than most buyers realize.

How Subconsultant Management Connects to the Rest of the Firm

Subconsultant management is not a standalone function. It connects to billing, financial metrics, project management, and proposals — and when it is handled correctly, it improves the accuracy of every downstream report and decision.

Billing — the way consultant costs are tracked and billed directly affects invoice accuracy, realization rate, and how write-offs are avoided. Pass-throughs handled incorrectly inflate apparent revenue without adding margin. Markup not applied consistently understates the firm's true earnings.

Financial metrics — net revenue calculations, operating profit margins, and project-level profitability all depend on consultant costs being accounted for correctly. A firm that includes pass-through consultant fees in its revenue base is comparing itself against a distorted benchmark.

Project management — phase-level budget tracking only works when consultant costs are linked to phases. A project that looks on budget may be over-committed to consultants if those obligations aren't visible against the phase budget.

Proposals — how consultant costs are structured in the proposal determines how they should be tracked throughout the life of the project. A proposal that includes consultant work as a pass-through requires a different billing setup than one that includes a markup. Getting this right at proposal time prevents reconciliation problems at billing time.