How do architecture firms handle reimbursements?

Architecture firms handle reimbursables by tying each cost to the client contract, tracking it by project and phase, applying the contracted markup and billing it back with documentation. Vergo automates the capture side, coding reimbursable costs to project and phase the moment they happen and syncing them to your accounting system.

October 28, 2026
See it with your ERP
Book Demo

Key takeaways

  • Reimbursable expenses in architecture firms are project costs incurred on behalf of clients and recovered through contractual billing, typically defined in the owner-architect agreement.
  • Effective reimbursement handling requires linking every expense to a project and phase at the point of capture, applying the correct markup, and providing documentation for client billing.
  • Vergo proposes coding by inference from your own accounting structure and history, so reimbursables are tied to the correct project and phase the moment they happen—no rule library to build, and new vendors are coded on first sight.
  • Missed reimbursables represent lost revenue—a single forgotten consultant invoice or site visit expense can cost thousands in unbilled charges.
  • Architecture firms need systems that align expense capture with project phases and billing cycles to ensure all reimbursable costs are recovered.

Where should you go next?

What are reimbursable expenses in architecture firms?

In architecture, reimbursable expenses are project costs that a firm incurs on behalf of a client and is contractually entitled to recover. They are distinct from the firm's professional fees. Common examples include reproduction and printing, travel and lodging for site visits, permit and filing fees, subconsultant fees (such as structural or MEP engineers), and model-making or rendering services.

The governing document is typically the owner-architect agreement (often AIA B101), which defines what qualifies as a reimbursable expense and the markup the firm may apply above actual cost. Some contracts cap reimbursables or require prior client approval for expenses above a threshold. Reimbursables are not a minor line item on large projects. Mismanaging them means either leaving revenue on the table or triggering billing disputes with clients.

Why reimbursement tracking matters in architecture firms

Architecture firms bill a mix of professional fees and pass-through costs, which creates accounting complexity that generic expense management tools are not designed to handle. The reimbursement process must align with project phases—schematic design, design development, CDs, construction administration—because many contracts limit reimbursables to specific phases.

For a controller at an architecture firm, this creates several practical challenges: phase-level cost allocation requires coding an employee's site visit travel to the correct project phase, not just the project. Consultant pass-through tracking demands capturing subconsultant invoices, applying the contracted markup, and billing them to the client on the appropriate cycle. Receipt documentation is increasingly required by clients for backup, especially on public or institutional projects. Markup enforcement prevents expenses from being billed at cost or overlooked entirely. Billing cutoff alignment ensures reimbursables don't slip to the next cycle or get forgotten. When reimbursements are tracked informally—through email, shared spreadsheets, or generic expense tools—firms routinely miss billable items.

A practical example: tracking site visit reimbursements

A project architect drives to a project site for a CA meeting and submits a mileage reimbursement. In an informal process, that expense is reimbursed to the employee through payroll but never linked to the project. At invoice time, the project manager doesn't know it was incurred, and the client is never billed. The firm absorbs the cost.

In a structured process, the same expense is coded to the project number and phase at submission. The controller sees it in a pending reimbursables queue, confirms it meets the contract's reimbursable definition, applies the contracted 10% markup, and includes it on the next client invoice with the receipt attached as backup. Vergo handles this by coding reimbursements to project and phase at the moment they happen, so the firm recovers the cost and keeps proper documentation for client review.

Handling subconsultant pass-through costs

Subconsultant invoices are a significant category of reimbursable expense in architecture. A structural engineering firm invoices the architect $18,000 for design services. Under the owner-architect agreement, this is reimbursable at cost plus 10%. The accounts payable team must flag the invoice as a pass-through, tie it to the correct project and phase, and make sure the $19,800 billable amount appears on the next client invoice.

Without a system to track these invoices as reimbursables at the point of entry, they often get coded as regular firm expenses or sit in accounts payable without a project link. The firm pays the consultant but never recovers the cost from the client. On a project with multiple consultants—structural, MEP, geotechnical, landscape—the cumulative unbilled amount can reach tens of thousands in lost revenue.

How Vergo handles this

Vergo is an AI-native, card-agnostic expense management platform that handles architecture firm reimbursements by coding every transaction to project and phase at the moment it happens. Employees handle everything by text message—no app to download, no portal login—and Vergo chases missing receipts itself instead of waiting for a report. Transactions are ready to code the moment they happen, with no waiting for clearing, and once they clear, they sync into your accounting or ERP software.

Vergo proposes the coding by inference from your own accounting structure and history—no rule library to build, no keyword lists to maintain, 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. 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.

Card spend, employee reimbursements and AP invoices run through one coding model—same coding, same review, one reconciliation—and payment stays on the rails you already use. Connecting your existing cards involves no card applications, no re-issuing and no banking change. Vergo integrates with Deltek Vantagepoint, Ajera, BQE Core and QuickBooks, so reimbursables reach project billing without manual re-entry.

Related questions

Frequently Asked Questions

What qualifies as a reimbursable expense under a standard owner-architect agreement?

Reimbursable expenses typically include transportation, lodging, printing and reproduction, permit fees, postage, and subconsultant charges directly attributable to the project. The agreement specifies whether a markup applies and may require prior written approval for expenses above a defined threshold.

How do architecture firms track reimbursables across multiple project phases?

Best practice is to require employees and accounts payable staff to assign a phase at the time of expense entry. Phases such as schematic design, design development and CA have different billing rules under many contracts, so phase-level tagging is essential for accurate and defensible client invoicing.

What happens when subconsultant invoices are not tracked as pass-through reimbursables?

If a subconsultant invoice is processed only as an accounts payable transaction without being flagged for client billing, the firm absorbs the cost. On complex projects with multiple subconsultants, this error compounds over a project's life, reducing realized margins well below what the contract supports.

How should architecture firms handle reimbursables that arrive after an invoice has already been issued?

Firms should establish a billing cutoff policy and communicate it to staff. Expenses submitted after the cutoff date should be held and applied to the next billing cycle. Some firms use a rolling reimbursables ledger by project to ensure late-arriving receipts are captured before the project closes out.

Can project-based finance platforms handle the reimbursement workflows specific to architecture firms?

Yes. Platforms like Vergo are built for project-based billing and code each expense to project and phase at capture, so reimbursables are ready for the billing team. Vergo also integrates with the project accounting systems architecture firms run, such as Ajera and BQE Core, keeping reimbursable data in sync.

What documentation do clients typically require for reimbursable charges?

Most institutional and public-sector clients require receipts or invoices as backup for all reimbursable line items. Private clients may accept summary documentation. Firms should retain original receipts, attach them to the corresponding expense record, and make them available for inclusion in the client invoice package upon request.

CTA Succes Clicker
Get Started

Expense & invoice automation for your ERP

Book Demo
Book Demo