Architecture Bookkeeping Fractional CFO
Leaving BQE Core: What Small Architecture Firms Actually Move To
Published October 12, 2026 by Invisible LLC Team · 8 min read
You're a principal, not a systems administrator. You didn't go to architecture school to develop an opinion about where your general ledger lives. But here you are, three weeks into evaluating platforms, because something about the current setup has stopped working — the phase invoices take a Sunday instead of an hour, nobody logs time until the 5th, and when a client asks why a consultant markup looks the way it does, you go hunting.
So you start looking at what else is out there. And the search results are almost all written by the vendors you'd be switching to.
Key takeaways: Firms leaving BQE Core land in one of four places, and the four are not interchangeable — two of them replace your accounting system, one of them sits on top of a ledger you have to supply, and one of them isn't an accounting tool at all. The question that sorts them is where the general ledger ends up afterward. And the most common expensive mistake isn't picking the wrong vendor; it's splitting an all-in-one into two tools without resourcing the reconciliation that split creates.
First, be precise about what you're actually leaving
This matters more than it sounds, because half the bad outcomes in this category come from replacing a platform with something that only does part of its job.
BQE Core sits in the all-in-one camp: phases, time, expenses, and billing alongside core accounting — accounts receivable, accounts payable, and the general ledger — in one platform. It can be your system of record. Whatever the reason you're leaving, that's the shape you're leaving, and if the thing you move to doesn't carry that shape, you aren't replacing it. You're replacing part of it and sourcing the rest somewhere else.
A note on the public conversation: a lot of what gets written about this category treats user frustration as product fact. We're not going to do that. What we can say is what we hear from principals: cost at the seat count the firm has grown into, the time-entry adoption problem, and reporting that doesn't answer the question the principal is actually asking. Those are all legitimate reasons. They also all have different right answers, which is the point of the rest of this post.
The four places firms actually land
1. Another all-in-one: Deltek Ajera
Deltek positions Ajera as a project-based ERP for small-to-midsize US architecture and engineering firms — project management plus full accounting, including the general ledger, AP, AR, and payroll. It is the books. Adopt it and QuickBooks goes away.
What you trade: depth for weight. This is the deepest project accounting in the category and the most complete AIA-style billing support, and implementation is a project with a timeline, not an afternoon. It wants someone in the firm who owns it.
Who it fits: firms with consultant-heavy, multi-phase work, real AIA billing complexity, and either an office manager or a bookkeeper who will live in the system.
2. Split the stack: project accounting on top of QuickBooks Online
Monograph takes the opposite approach and documents it plainly: Monograph handles project accounting — budgets, time, expenses, consultant bills, invoicing, project profitability — while QuickBooks Online manages the general ledger and firm-wide books, with data syncing between the two. Monograph does not include the general ledger. That's by design, not an omission.
What you trade: one system of record for a much better chance that your team actually logs time. Adoption is the quiet reason this shape wins in small studios. The cost is a sync boundary — two systems that have to agree, and a monthly reconciliation that belongs to someone.
Who it fits: studios whose ledger is fine and whose real problem is project visibility and getting hours entered.
If you've already narrowed to these first two, that head-to-head is its own post: Deltek Ajera vs. Monograph for small architecture firms covers the structural difference and the switching sequence that matters.
3. QuickBooks Online plus a time-and-billing layer
The least-discussed destination and, for a four-to-eight-person practice, often the most defensible. QuickBooks Online carries the ledger. A time-and-billing tool — Harvest is one commonly used option — carries time entry, expenses, and invoicing. Project tracking happens in QuickBooks using its customer-and-project structure, with a studio-shaped chart of accounts underneath.
What you trade: purpose-built A&E features for simplicity and a dramatically smaller learning curve. You will not get phase-level fee forecasting out of this. You will get clean invoices, a ledger your CPA recognizes, and project margin that's actually computable — if the chart of accounts is right.
Who it fits: firms whose billing is phase-based but not AIA-contract-complex, and whose consultant pass-throughs are manageable in volume. We've written the mechanics of making this shape work in job costing in QuickBooks for architecture studios and the studio chart of accounts.
4. Staying on BQE Core
This belongs on the list, and leaving it off would be dishonest. If the problem is that nobody configured phases, rate tables, or reimbursable handling properly in the first place, you will pay to migrate and then recreate the same problem in a new platform within a year. We've watched it happen. A configuration review is cheaper than a migration, and it's the only option on this list where the answer arrives in weeks.
The question that sorts all four: where does the general ledger live afterward?
Ajera and BQE Core include it. Monograph does not and says so. Harvest isn't an accounting system at all. QuickBooks Online is one.
Ask it out loud before you compare features, because the answer determines what else you have to buy, who reconciles what, and what your month-end close looks like for the next five years. If a vendor's answer to "where does my general ledger live after this?" isn't immediate and unambiguous, you're talking to the wrong person at that company.
(Vendor status verified October 2026: Deltek, BQE, Monograph, and Harvest are all independent, actively sold products. We don't quote prices in this category — seat and module pricing changes often enough that any figure here would be wrong within a quarter. Ask each vendor for current pricing at your seat count and module mix.)
What the all-in-one was quietly doing for you
This is the part nobody warns you about, because it isn't a feature anyone markets. An all-in-one platform does three things for free that a split stack makes you do deliberately:
- AR aging that already knows about phases. In one system, "who hasn't paid" and "which phase was that" are the same query. Split the stack and your aging report lives in the ledger while the phase context lives in the project tool.
- Consultant commitments sitting next to the project budget. When the sub's invoice and the project fee are in the same database, over-commitment is visible. When they're in two systems, it's visible at close — which is a month late.
- No sync to reconcile. The cost of the split shape isn't the second subscription. It's the recurring monthly question of whether the two systems still agree, and that question needs an owner with a name.
None of this argues against splitting. It argues for pricing the split honestly.
The three ways this goes wrong
- Buying a planning tool to solve an accounting problem. If your actual pain is that you can't tell which projects made money, a beautiful project-planning interface will not produce that answer. The number comes from labor cost loaded correctly against phases, and that's a ledger-and-setup problem in every one of these four destinations.
- Splitting the stack without naming the owner. The layered shape is often the right call. It fails when nobody is assigned the monthly reconciliation and the two systems drift for a quarter.
- Migrating at a bad boundary. The middle of a fiscal year, with four projects mid-CD and a consultant commitment half-invoiced, is the most expensive possible time to change systems. The sequencing for this — including the balances that are genuinely hard to move — is in the Ajera-versus-Monograph post; don't re-derive it under deadline.
Where this leaves you
If you want one system of record and someone will own it, look hard at Ajera and re-evaluate BQE Core alongside it rather than assuming you need to leave the category. If your ledger is fine and the pain is visibility and time entry, look at the layered shape. If you're a small practice with phase billing but not AIA-contract complexity, QuickBooks plus a time-and-billing layer is a real answer, not a compromise. And if nobody ever configured what you have, fix that before you buy anything.
For the wider field — including the tools we haven't covered here because they aren't where BQE Core refugees usually land — see accounting software for architecture firms.
Whichever shape you pick, the platform won't produce project margin by itself. It produces the raw material; someone still has to load labor cost correctly, land consultant invoices against the right phase, and read the result. That's the work we do for studios — the invoicing, the reconciliation, the monthly statements with project-level margin in them. See how we run studio books and the reporting we build on top, or read what we do for architecture practices.
If you'd rather talk it through than read another vendor comparison page, tell us where you're starting from. We'll be honest if the answer is "stay where you are and fix the setup."