CAM Reconciliation Software: Build or Buy at Your Lease Mix
The decider is not square footage, it is how many of your leases carry genuinely negotiated exclusions, caps and gross-up terms.
On this page
The decider is not square footage, it is how many of your leases carry genuinely negotiated exclusions, caps and gross-up terms. If your portfolio runs largely on one template with a straightforward pro rata share, the recovery module inside Yardi Voyager Commercial or MRI Commercial Management calculates that correctly and a build is waste. Most landlords sit there. The build case starts when exclusions, caps and base year methodology differ tenant by tenant, which in practice means a negotiated portfolio above roughly 8 million square feet and a first release of $80,000 to $180,000.
When is off the shelf genuinely the right call here?
Buy if your leases run largely on one template with a straightforward pro rata share and no negotiated exclusions, caps or gross-up variations. Yardi Voyager Commercial and MRI Commercial Management already own your general ledger, rent roll and billing, and their recovery calculation handles that shape correctly. A custom engine is an expensive way to arrive at the same answer.
Look hard at Datex Footprints before pricing anything custom if you are retail focused. It was designed around retail recovery mechanics specifically and covers more of the anchor, cap and pool structure than most packaged products, which means a chunk of what you would otherwise be paying an engineer to encode is already there.
Accruent Lucernex sits on the lease abstraction side rather than the calculation side, and if your immediate problem is that nobody knows what the leases say, that is a different purchase from a recovery engine and usually the one to make first.
And there is a real answer below all of that. If your portfolio is small enough that a competent lease administrator with a good workbook is genuinely sufficient, which is most operators below a few hundred thousand square feet, discipline matters more than software. Buy nothing, write the methodology down, and keep the workbook backed up.
When does a custom build actually pay off?
The argument for building here is evidential, not computational. The calculation is not hard. Producing, on demand, a statement in which every figure traces to a lease clause and a general ledger transaction is hard, and that is what turns a tenant audit from a negotiation into a closed conversation.
Four signals matter. First, your leases contain negotiated exclusions, caps and gross-up terms that differ tenant by tenant, so your administrators compute pieces of the reconciliation in spreadsheets sitting alongside the system. Second, you have lost a tenant audit or settled one you believed you should have won, which almost always means the trace took longer to assemble than the negotiating position could hold.
Third, you cannot reproduce a base year calculation from five years ago, because the base year was stored as a typed figure rather than as a computed result with its methodology preserved. Fourth, your reconciliations are late often enough that a waiver clause is a live risk, and a waived shortfall is money you never even argued about.
Add one more that decides it for asset managers rather than accountants. Nobody in your business currently knows the gap between uncounted uncapped entitlement and capped billable across the portfolio, because it has never been computed. That figure changes how the next renewal gets negotiated, and it is a recurring benefit rather than a one off recovery.
How do they compare on the things that matter in commercial property?
On the ledger, the rent roll and monthly billing, the packaged systems win outright and you are keeping them. Nothing about accurate recovery requires owning the general ledger, and landlords who scope an accounting replacement into this project multiply the number for no recovery benefit.
On the pro rata share, the difference is provenance. Packaged systems hold a share percentage or compute one from a selected denominator method. They struggle to hold a different denominator definition per lease and to show, on a statement, the exact areas and dates used. So the share gets computed outside and typed in, and it then survives unchanged for a decade with no explanation attached.
On exclusions, packaged recovery is a configured method with parameters, applied as an adjustment. A build applies exclusion rules against ledger detail at the account and sometimes the transaction level, which is precisely what an audit firm asks to see.
On caps, cumulative and compounding variants depend on the entire history of capped and uncapped amounts, not on last year's billing. That history has to be stored permanently per lease, and it is frequently lost when a property changes owners or systems.
On gross-up, packaged systems support it. What they do not hold well is a per lease variability classification and the base year methodology as evidence attached to the base year figure.
On reporting, the packaged tools produce competent statements and struggle at the audit response pack, because that pack is a demand for underlying detail rather than a formatted summary. And on portability, a recovery configuration built inside one vendor's module does not travel. The clause rules you encoded are expressed in that vendor's parameters, so a platform change means encoding them again, whereas rules held as your own data move with you.
What does total cost of ownership look like at your portfolio size?
Your Yardi or MRI renewal is not the comparison, because you keep paying it either way. Run the build against recovery leakage instead, using your own numbers.
A first release covering clause level recovery rules, pool and exclusion logic against ledger detail, share computation from dated areas, gross-up, caps with permanent history, base year handling and a traceable tenant statement runs $80,000 to $180,000 over 12 to 18 weeks. A full platform adding estimates and monthly billing with true-up, capital amortisation schedules, audit response packs, budget to actual variance and portfolio analytics runs $200,000 to $500,000 phased over 6 to 12 months. A 214 tenant office and retail portfolio taking both phases lands near $330,000, which is $66,000 a year over five years plus $50,000 to $73,000 running at 15 to 22 percent of build cost.
Lease abstraction is the largest single line and the one landlords underestimate. In that worked portfolio it is $38,000 of a $178,000 first release, more than the caps and base year modules combined, because every negotiated exclusion and cap variant has to be read out of a document by someone qualified before an engineer encodes anything.
On the current cost side, count three things. Lease administrator time in reconciliation season, which for 214 tenants built in Excel per property is measured in weeks. Audit settlements, meaning concessions given because assembling the trace took too long. And late statements where a waiver clause applies.
What does the hybrid look like, and when is it the honest answer?
In this category the hybrid is not a compromise, it is the correct architecture, and almost every landlord who builds should build it this way.
Keep the platform. Yardi Voyager or MRI Commercial Management stays as the general ledger, the rent roll and the billing engine. The recovery engine you build reads ledger detail from it and, in phase two, writes charges back. Everything about accurate recovery happens in a layer above accounting rather than inside it.
Then thin the layer further. Encode the 40 leases that carry every structure you own rather than all 214, prove the engine against them, and run the remainder as data entry against a proven model instead of as discovery. Ship one property type first, retail caps if that is where your disputes are or office base year stops if that is where the money sits.
Defer the parts that already work. Estimates and monthly billing sit at $34,000 in phase two for good reason: the annual reconciliation is where recovery leaks, and monthly estimate billing already runs in your existing system. Charge writeback at $32,000 belongs early in phase two rather than late, because until it exists somebody keys results back in by hand.
And accept manual entry for prior year capped amounts rather than commissioning a reconstruction project. Type in what you can evidence, flag the rest as unverified, and let clean history run forward from this year.
Which should you choose, by portfolio size and stage?
Under a few hundred thousand square feet, one property type, template leases: no software project. A competent administrator with a documented workbook is genuinely sufficient and any spend here is vanity.
Template leases at any size, straightforward pro rata share: configure the Yardi or MRI recovery module properly and stop. If you are retail focused, evaluate Datex Footprints first, because it may close the gap without a build.
Negotiated portfolio under roughly 8 million square feet, disputes rare, statements on time: stay packaged, but fix the underlying data. Get a professional clause level abstraction done. It is the largest cost lever you control if you ever do build, and it improves your position immediately either way.
Negotiated portfolio above roughly 8 million square feet, anchors with bespoke structures, audits settling rather than closing: build the first release at $80,000 to $180,000. Budget the parallel run at around $10,000 and treat it as mandatory, because reproducing last year's reconciliation tenant by tenant is how you find out whether your encoded rules match what the office has actually been doing. Expect differences, and expect some of them to be the old workbook being wrong.
Multi property type portfolio assembled by acquisition, with lost cap history and reconstructed base years: the full platform at $200,000 to $500,000 is proportionate, phased across 6 to 12 months. Time the go live against your reconciliation calendar and finish the parallel run a full cycle ahead of statement deadlines. Launching three weeks before statements are due is how a working system gets blamed for a bad quarter.
If you would rather someone argued with your brief than agreed with it, Digital Heroes writes a product requirements document before any code exists, so the scope is fixed and priced rather than discovered later at a day rate. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Gartner estimates RPA can eliminate up to 25,000 hours of avoidable rework caused by human errors in the finance function each year, equating to savings of roughly $878,000 for an organization with 40 full-time accounting staff (based on interviews with more than 150 corporate controllers and chief accounting officers). Source: Gartner (2019) →
- Deloitte reports that modern ERP implementations aim to deliver reduced manual effort, greater transparency, a single source of truth, and increased productivity, but many organizations do not capture the full expected benefits (a significantly lower ROI) without disciplined strategy, change management, and data readiness. Source: Deloitte (2024) →
- The average developer spends more than 17 hours a week dealing with maintenance issues such as debugging and refactoring, and about four of those hours on 'bad code' - waste that equates to nearly $85 billion annually worldwide in opportunity cost. Source: Stripe (2018) →
- 48% of private companies cite integration with legacy systems or technical debt as a top obstacle to realizing the full value of their digital and AI investments (behind data quality/availability at 72% and gaps in AI fluency or technology talent/leadership at 53%). Source: Deloitte (2026) →
Frequently asked questions
Is the Yardi recovery module really not enough for a negotiated portfolio?
It is enough where the lease is enough. Yardi Voyager Commercial and MRI Commercial Management both express recovery as a configured method with parameters, which is correct for leases written on one template with a plain pro rata share, and they calculate that accurately.
The limit is per lease variation. When exclusions, cap variants and gross-up occupancy figures differ tenant by tenant, the difference gets absorbed by spreadsheets sitting alongside the system, and that labour is what you are actually pricing against.
What does it cost to switch, given we are keeping our accounting system?
You are not switching platforms, which is the point. The ledger, the rent roll and the billing stay in Yardi or MRI, and the recovery engine reads from them and later writes charges back at around $32,000 for that integration.
The real switching cost is abstraction. Recovery rules have to come out of the lease documents, roughly $38,000 across a 214 tenant portfolio, and it has to happen before any engineer encodes anything.
What happens if our property accounting vendor raises prices or changes terms?
It affects you either way, because in every sensible version of this you keep the accounting platform. Building a recovery engine does not reduce your exposure to that renewal and nobody should sell it as though it does.
What it does change is the connector economics. A recovery layer that reads ledger detail through a documented interface is portable in a way that deep configuration inside one vendor's recovery module is not.
How long does a first release take?
Twelve to 18 weeks. Abstraction paces the schedule rather than engineering, so a portfolio with clause level abstractions already done sits at the shorter end and one where the rules live in inherited workbooks sits at the longer end.
Timing matters more than duration. Finish the parallel run at least a full reconciliation cycle ahead of your statement deadlines rather than going live into them.
Should we look at Datex Footprints before building?
If you are retail focused, yes, and seriously. It was designed around retail recovery mechanics including anchor structures and cap variants, so it closes more of the gap than a general property accounting recovery module will.
Where it will still not reach is a portfolio that spans office base year stops, retail caps and industrial net leases at once, because those are three different rule families and you would be maintaining three dialects regardless.
Can we build only the caps and base year handling and leave the rest?
You can, and for some landlords it is the right scope. Caps with permanent year by year history sit near $20,000 and base year handling that stores methodology and underlying detail rather than a typed figure sits near $16,000 in a worked portfolio.
The caution is that both need the share engine and the pool and exclusion logic underneath them to produce a defensible number, so the genuinely minimal build is smaller than the full first release but not by as much as it looks.
What is the parallel run and can we skip it?
Around $10,000, and no. You reproduce last year's completed reconciliation tenant by tenant and explain every difference, which is the only way to learn whether your encoded rules match what your office has actually been doing.
Expect differences and expect some to be the old workbook being wrong. Finding those before a tenant's auditor does is most of the value of the exercise.
What is the ongoing cost, and what decays if we ignore it?
Budget 15 to 22 percent of build cost annually, so $50,000 to $73,000 on a $330,000 platform. Compute is a small part, because the engine runs hard for a few weeks a year and idles otherwise.
The line that decays is abstraction of new leases and renewals into rules. If nobody owns that, the system drifts back toward the workbooks you left behind, and you will notice it first as a tenant statement that needs a manual adjustment.
How many developers does it take to build accounting software?
The standard Digital Heroes team is 4 to 6 people: a backend developer, a frontend developer, a QA engineer, a part-time designer, and a project lead who owns the accounting logic. A single-workflow automation can ship with two people, while multi-entity platforms with payroll can need eight. Headcount matters less than having one named person accountable for the books balancing.
What does it cost to keep custom software running after launch?
Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.
How do I migrate years of QuickBooks data into a custom system?
Use a staged migration: export full history through the QuickBooks API or backup files, load it into the new system, then run both systems in parallel for at least one full closing cycle before cutting over. Expect cleanup work, because books older than three years almost always contain miscategorized transactions that surface during import. Digital Heroes schedules migration as its own project phase with its own sign-off, never as a launch-week task.
What can custom accounting software do that QuickBooks, Xero, and FreshBooks can't?
It encodes your actual business rules: progress billing tied to project milestones, revenue recognition for your specific contract types, landed cost tracking, or approval chains that match your org chart. Off-the-shelf tools handle generic bookkeeping well but force every business into the same chart of accounts and workflow. FreshBooks, for example, is built around freelancer-style invoicing, so inventory or multi-entity accounting means leaving the product entirely.
What happens to my accounting software if the agency shuts down?
If you own the repository, the hosting accounts, and the documentation, another team can take over within weeks, usually before a missed closing cycle does real damage; if the agency owns any of those, you have a hostage situation. Before signing, confirm the code sits in your GitHub or GitLab organization, hosting bills to your card, and a written deployment runbook exists. A competent agency agrees to all three without friction, and hesitation is itself the answer.
Who owns the code when an agency builds my accounting software?
You should, outright, and the contract must say so with an explicit IP assignment clause rather than a usage license. Insist that the code lives in a repository you control from day one, so nothing, including the ledger schema and migration scripts, can be held back at the final invoice. Third-party libraries and any framework the agency reuses stay under their own licenses, and a clean contract lists exactly which those are.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
Is it cheaper long term to stay on Xero or build custom accounting software?
Xero stays cheaper as long as its workflows fit your business, since even its top plan costs around $1,000 a year and custom development starts around $25,000. The math flips once you stack add-ons: companies Digital Heroes scopes after they have bolted inventory, job costing, and approval apps onto Xero are usually paying more for the app stack and the labor of keeping five tools in sync than for Xero itself. Custom wins when the real cost is that labor and its errors, not the license fee.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
Who can build a custom accounting software system?
Digital Heroes builds custom accounting software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other accounting software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .
