Key takeaways
- Subconsultant invoices are usually pass-through costs billed to the client, often with a markup, so they carry billing compliance requirements a project manager alone cannot verify.
- Engineering firms split approval authority across project managers (scope), principals or department heads (commitments) and controllers (coding and billing terms).
- Multi-level review prevents overbilling, unbilled pass-throughs, scope creep and audit failures on cost-plus and government contracts.
- Manual multi-level approval causes close delays, missed billing cutoffs, misposted project costs and duplicate payment risk.
- Vergo routes invoices through the approvers you set, keeping timestamps and approver identity for audit, with project, phase and task coding proposed from your own accounting structure so reviewers confirm in seconds.
Where should you go next?
- See how Vergo works for engineering firms
- Learn more about Vergo Expense Management
- Learn more about Vergo AP Invoice Automation
- Learn more about Vergo Employee Reimbursements
Why This Happens in Engineering Firms Specifically
Engineering firms work under a layered contract structure most industries never see. When a prime firm engages a subconsultant, a geotechnical lab, a traffic engineer, an environmental specialist, that cost usually flows through to the client as a reimbursable consultant expense, often with a markup set in the prime agreement. Every subconsultant invoice therefore has billing consequences, not just cost consequences. That is fundamentally different from an ordinary vendor bill, which is checked against a PO or receipt and paid. A subconsultant invoice must be checked against the subconsultant agreement, the prime agreement's billing terms, the project manager's scope authorization and a finance review for the right project, phase and task in Deltek, BQE Core or Sage Intacct. No single person holds all of that context. Vergo proposes the coding by inference from your own accounting structure and history, with no rule library to build and no keyword lists to maintain, and new vendors are coded on first sight.
What Forces Multi-Level Review
Approval becomes multi-level because of how engineering firms are organized and what their contracts require. Project managers own scope and budget. Principals or department heads own consultant commitments. Controllers own billing compliance and project coding. Each layer exists for a reason, and bypassing any one of them leaves the firm carrying the risk. Pass-through billing terms often require subconsultant invoices to be supported by backup before the firm can bill the client, a gate finance must own. Markup checks confirm the rate applied matches what the prime agreement allows; a wrong markup on a passed-through invoice means over- or underbilling. Scope checks require the project manager to confirm billed services match the authorized task order, not just the dollar amount. Budget-to-actual review requires the invoice to hit the right project, phase and task before it posts, so earned value and unbilled reports stay accurate. Many firms also verify the subconsultant's certificate of insurance before release, a step outside the project manager's lane entirely.
The Real Impact on Engineering Firm Operations
When multi-level approval is required but the workflow is manual, with email chains, PDF attachments and shared drives, it breaks down in predictable ways. The close stretches while subconsultant invoices are still circulating when accounting needs to finalize project reports. Client invoices go out late or short when a subconsultant invoice misses the billing cutoff because it sat in someone's inbox waiting on a second signature. Costs post to the wrong phase or task because the project manager who knew the breakdown was not in the chain. Audit exposure grows on government and cost-plus contracts when invoices lack documented, sequential approval with timestamps and approver identity. Duplicate payments happen when a subconsultant resubmits an invoice and a different approver processes it without seeing its history. Vergo's approval workflows are optional and fit how you already control spend: route by GL account, by amount, or by project, or skip approval flows entirely and let policy flags catch only what breaks a rule.
A Practical Example
A geotechnical subconsultant sends an invoice for soil borings on a highway design project under a cost-plus agreement with the state DOT. It arrives by email to AP. AP forwards it to the project manager, who confirms it matches the authorized task order but does not know which phase and task the DOT's billing format expects. He replies with approval but no coding. AP asks the controller, who assigns the task but notices a 10% markup where the prime agreement allows 8%, and emails the project manager to confirm. Four days pass. The invoice is keyed after the monthly billing cutoff, the pass-through slips to next month's client invoice and cash is short for a cycle. With structured routing, the invoice moves from project manager to controller in sequence, each step documented, and posts to the ERP within a day with the right task and markup.
How Vergo Handles This
Vergo is an AI-native, card-agnostic platform that handles card spend, employee reimbursements and AP invoices through one coding model. Approval workflows are optional and fit how you already control spend: route by GL account, by amount, or by project, or skip them and let policy flags catch only what breaks a rule. When subconsultant invoices need multi-level approval, Vergo routes them through the approvers you set, with timestamps and approver identity kept for audit on cost-plus and government contracts. Vergo proposes the project, phase, task and GL account by inference from your own accounting structure and history: no rule library to build, and new vendors are coded on first sight. Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. Once approved, invoices sync into your ERP and payment stays on the rails you already use. Vergo integrates with Deltek Ajera and BQE Core.
Related Questions
Frequently Asked Questions
How many approval levels are typical for subconsultant invoices in engineering firms?
Many engineering firms use two or three levels: the project manager verifies scope and authorized services, finance checks project, phase and task coding and markup, and a controller or billing manager confirms the invoice is billable under the prime agreement. Firms with government contracts often add a compliance review.
Why can't the project manager approve subconsultant invoices alone?
Project managers have scope authority but often lack visibility into prime billing terms, markup limits, insurance status and the ERP's project structure. Single-approver sign-off creates overbilling risk, misposted project costs and audit exposure, especially on cost-plus or federally funded contracts that require documented approval chains.
How do delayed subconsultant invoice approvals affect client billing cycles?
When a subconsultant invoice misses the monthly billing cutoff because it is still routing, the firm cannot pass that cost to the client until the next cycle. Cash recovery slips by a month or more and long engagements can run project-level cash deficits.
What compliance risks come from informal subconsultant invoice approvals?
On federal, state or cost-plus contracts, informal approvals create audit findings when the firm cannot show who approved an invoice, when and on what basis. FAR-governed work and DCAA reviews expect verifiable approval trails, and undocumented approvals can lead to disallowed costs or repayment.
Can AP automation handle different approval chains for different subconsultant invoices?
Yes. With Vergo, approval routing can be set by GL account, by amount or by project, so a large invoice on a government project follows a longer chain than a small lab bill on a commercial one. Coding is proposed from your history and each approval is recorded with its timestamp.
How does subconsultant invoice approval affect project financial reporting?
Subconsultant invoices that are not approved and coded cannot post to the project, so they are missing from project cost, earned value and unbilled reports. Profitability looks better than it is until they post, and delayed approvals are a common reason project reports get reworked at month-end.
