Architecture Bookkeeping Small Business

Deltek Ajera vs. Monograph for Small Architecture Firms (and What to Do If You're Leaving BQE Core)

Published September 25, 2026 by Invisible LLC Team · 9 min read

You're a principal, not a systems integrator. But sooner or later someone on a forum tells you Ajera is the serious choice, someone else says Monograph is the one that doesn't feel like 2004, and you're staring at two demo calendars trying to work out which one stops the Sunday-night invoicing.

Here's the thing nobody says on the demo: Ajera and Monograph aren't two versions of the same product. One of them replaces your accounting system. The other sits on top of the accounting system you already have. Every other difference — the dashboards, the timesheet UI, the phase budgets — is downstream of that one structural fact. Get that straight and the decision usually makes itself in about ten minutes.

Key takeaways: Deltek Ajera is a project-based ERP that includes the general ledger, AP, and AR — adopting it means replacing your accounting system. Monograph is project accounting that syncs with QuickBooks Online, which keeps the general ledger where it is. If you're leaving BQE Core, you're leaving an all-in-one platform, so the real question is whether you replace it with another all-in-one or split the job into two tools. And whichever you pick, the platform doesn't produce project margin on its own — somebody still has to set up phases, rates, and cost categories and keep them current.

The structural difference, in one paragraph

Deltek positions Ajera as a project-based ERP for small-to-midsize U.S. architecture and engineering firms, combining project management with full accounting — general ledger, accounts payable, accounts receivable, payroll. It is the books. If you adopt it, QuickBooks goes away.

Monograph takes the opposite approach and says so plainly in its own documentation: Monograph handles project accounting — budgets, time, expenses, consultant bills, invoicing, project profitability — while QuickBooks Online manages the general ledger and firm-wide books, with invoices, expenses, consultant bills, and clients syncing between the two. Monograph is explicit that the general ledger, accounts payable, and firm-wide financial statements stay with QuickBooks. It is a layer, not a replacement.

BQE Core sits in Ajera's structural camp: phases, time, expenses, and billing alongside full accounting — AR, AP, and general ledger — in one platform.

So the honest framing of "Ajera vs. Monograph" is not a feature bake-off. It's this: do you want one system that does everything, or two systems that each do one thing well?

Which shape actually fits a small studio

There's no universally right answer, but there are reliable tells.

The all-in-one shape (Ajera, BQE Core) tends to fit when:

You run payroll for a meaningful internal team and want it inside the same system as project labor, so labor cost hits the project without a bridge.
You bill in phases against AIA-style contracts and want the billing engine and the ledger to be the same engine, with no sync to reconcile.
You have someone — in-house or outsourced — who will own the system. An ERP rewards an owner and punishes a studio where nobody quite owns it.
You're at the size where a real audit trail across GL and projects matters to a lender, a landlord, or a prospective partner.

The layered shape (Monograph + QuickBooks Online) tends to fit when:

Your accountant, bookkeeper, and CPA all already work in QuickBooks, and moving off it means retraining everyone who touches your money.
Your pain is project-side: you can't see which phases are underwater, principal time isn't captured, consultant bills aren't landing against the right project. The ledger itself is fine.
You want principals and project architects to actually log time. Adoption is a real variable, and a tool people avoid produces worse data than a simpler tool people use.
You'd rather keep the ability to change one half of the stack later without changing both.

The trap is picking the all-in-one because it sounds more serious. An ERP that nobody maintains produces exactly the same black box you have now, except you paid more for it and it's harder to leave. As we wrote in our broader shortlist of accounting software for architecture firms, the tool is the easy half of this decision.

If you're leaving BQE Core, here's the sequence that matters

Switching off an all-in-one is different from switching between two project tools, because the ledger is coming with you. A few studios have learned this the expensive way: they picked the new platform first and discovered the migration constraints second.

1. Decide the shape before you decide the vendor. If you replace BQE Core with Monograph alone, you have not replaced it — you've replaced half of it, and you need QuickBooks Online underneath. That's a legitimate choice, and often the right one. It's just a different project than swapping one ERP for another.

2. Cut at a fiscal boundary. Migrate effective the first day of a fiscal year or, at minimum, a clean quarter. Mid-year cutovers mean two systems of record for one tax year and a painful year-end. This single decision saves more hours than any feature on any comparison chart.

3. Inventory the balances that are hard to move. Transactions migrate reasonably well. These don't, and they're the ones that bite:

Unbilled work in progress by project and phase. If WIP doesn't land correctly, your first month in the new system will show a profitability picture that isn't real. (If WIP is fuzzy today, fix that first — here's how we think about studio WIP.)
AR aging by invoice, not just a total. You need the detail to keep collecting through the transition.
Retainer and deposit balances held against future phases. These are liabilities, and they're the most commonly mangled item in an A&E migration.
Open consultant commitments — subs engaged, not yet billed.
Historical project data you actually intend to use. Be honest here: most studios say "all of it" and use three years.

4. Rebuild the chart of accounts deliberately, don't import it. A migration is the one moment when redesigning your chart of accounts is nearly free. Carrying over fifteen years of accumulated one-off accounts is how a fresh system starts life already messy.

5. Run parallel for one full billing cycle. One month. Both systems. Compare the invoices before you send them. It is tedious and it is the cheapest insurance in the whole project.

6. Don't migrate a broken phase structure. If your current phases don't map to how you actually bill — schematic, DD, CD, CA, with reimbursables and markup handled consistently — the new platform will faithfully reproduce the confusion at a higher monthly cost.

The questions to ask on the demo

Demos are optimized to show you a beautiful dashboard populated with perfect data. Ask these instead, and ask them in this order:

"Where does my general ledger live after this?" The answer should be immediate and unambiguous. If it isn't, you're talking to the wrong person at that vendor.
"Show me a phase-billed invoice with reimbursables at markup, generated live." Not a screenshot. Live, from the demo data, with an expense marked up.
"How does consultant cost land against the project?" Sub-consultant handling is where A&E platforms quietly differ.
"What exactly syncs, in which direction, and how often?" For any layered setup, ask what happens when a record is edited on the other side. Sync conflicts are the recurring maintenance cost of the two-tool model, and you should know the shape of that cost before you sign.
"What does implementation actually require from us — in hours, from whom?" The honest answer is always more than the sales answer.
"How do I get my data out?" Ask at the beginning of a relationship, not the end. You're asking it right now about BQE Core; you'll ask it again someday about whatever you choose next.
"Who sets up my phase templates and labor rates — you, or me?" This is the question that determines whether the thing works in month two.

We deliberately aren't quoting prices here. Pricing in this category is quoted per firm, changes without notice, and any number in a blog post is stale the week after it's published. Get it in writing from the vendor, for your seat count, with implementation broken out separately.

What no platform will fix

Every vendor in this category sells "project profitability." None of them manufacture it. Project margin is an output of four inputs, and all four are yours:

Phases set up the way you bill. If the contract has five phases and the system has one, nothing downstream can be right.
Labor rates that reflect true cost. Not billing rates. Cost — salary plus the loaded burden. Get this wrong and every project looks more profitable than it is.
Time entered on time. A week-late timesheet is a week-late margin number, and margin you learn about in arrears is history, not management.
Reimbursables captured and marked up consistently. The single most common leak we see in studio books, and the one principals feel most viscerally.

Configure those four and QuickBooks alone can answer most of the questions. Skip them and a six-figure ERP will confidently return the wrong number. If you want the underlying mechanics, our guides on job costing in QuickBooks for studios and project margin vs. firm margin cover the setup that has to exist regardless of the platform you land on.

So: Ajera or Monograph?

If you want one system of record and you have — or will hire — someone to own it, look hard at Ajera, and evaluate BQE Core alongside it rather than assuming you need to leave the category. If your ledger is fine and your problem is project visibility and getting people to log time, look at Monograph on top of QuickBooks Online, and budget for the sync discipline that model requires.

And if you can't tell which camp you're in, that's usually a sign the answer is neither yet — that what you actually need is your current books set up correctly, which is a much smaller project than a migration.

That's the work we do. We run studio books in QuickBooks with project tracking, phase billing, reimbursables, and margin reporting that answers "did we make money on that one?" — and when a studio genuinely has outgrown that setup, we'll tell you, and we'll help you move.

Tell us what your studio is running today and we'll give you a straight answer about whether you need a new platform or a better setup. If you want the wider view first, start with our comparison of accounting software for architecture firms, or see how we work with architecture and design studios and what custom reporting looks like once the data underneath it is clean.