CAM reconciliation
Backed by lease evidence. Reviewed by people.
Pick up any saved CAM reconciliation. Search by property or tenant name to filter the list.
One guided path from the rent roll to an approved reconciliation.
What the app means by the words it uses about leases and their documents.
Approvals, undelivered statements, tenant requests.
In the app and by email: always, right away. These can’t be turned off.
An extraction needs checking, an estimate looks stale. Always kept in your inbox.
A run finished, a batch is done. Never a push.
Holds “Worth a look” email and push until quiet hours end. “Needs you” always comes through.
Set your timezone so quiet hours work. Until then nothing is held back.
Pick up where you left off.
Pick a project, enter the year's actual expenses, and the app computes each tenant's share. You review, add a note, and approve — the app never finalizes on its own.
Question 1 of 3
The year splits on this date. Each owner reconciles its own days.
Question 2 of 3
Question 3 of 3
Using the workbook replaces the Tenant Charges report on file. If you switch by mistake, that report has to be uploaded again.
Your reports stay private.
They're held in a private, access-controlled store under an anonymous key and used only to build this reconciliation — never shared or made public.
Pick the building you are reconciling, or start a new one from its rent roll.
We’ll read the building’s name from it, so there is nothing to type first.
The Rent Roll builds the Tenant Roster.
The rent roll gives TrueUp the building name, the tenant roster (vacant spaces included) and the pro-rata denominator, so there's nothing to type first.
Excel or CSV is best: figures are read exactly from the cells. A PDF works, but it's read by AI and takes longer.
Your reports stay private: held in a private, access-controlled store under an anonymous key and used only to build this roster, never shared or made public.
We read the project name from the Rent Roll — confirm it, correct it, or pick one you already manage. It groups all of this project's tenants together.
Review what was read from each lease — the CAM terms, and the lease language each one came from.
Open each lease and check its extracted CAM terms against the lease itself. Show in lease, on each term, opens the lease at that wording with the PDF page beside it.
Upload many leases at once. Stage a folder or a set of files, then say what each PDF is (lease, amendment, commencement letter…) and which tenant it belongs to — a tenant's documents become one lease, analyzed on our servers. Nothing uploads until you review the list and confirm.
Add the leases. Choose files, pick a folder or drag them in, as many times as you like — every pick adds to the list, so leases sitting in different folders (or different SharePoint sites) all end up in one batch. Nothing is uploaded until you review the list and confirm.
Every lease attached to a property, in one place — add an amendment, replace the abstracted lease, or fix a tenant's name, suite, or square footage. Nothing is re-analyzed until you ask.
Nothing uploads until you review and confirm.
One PDF, a pile of files or a whole folder. Say which tenant each belongs to and it is filed under this property.
Every pick adds to the list, so leases from different folders end up in one batch.
Reads inside the lease documents themselves and opens the page it found.
Line up extracted leases side by side to spot where the CAM methodology diverges.
The reconciliation delivery deadline for each tenant's lease — the date the landlord must deliver the CAM statement (missing it can bar recovery) — pulled from every extracted lease and counted down from today, soonest first.
Occupancy and lease rollover across the project — a project can hold several buildings, and each is shown as its own stack. It builds itself from the leases you've already uploaded: every suite is a block, sized by leased area and colored by time to lease expiry. Drag the timeline to see who's rolling and when.
Build a rent roll straight from your lease documents — one step at a time, so there's less on screen at once. Add your leases, optionally attach accounting reports, generate the rent roll, then cross-check it against a stacking plan.
Upload your leases here, then pick them once they’re analyzed. Base rent, square footage, suites and dates are read from each lease. Already analyzed some in the Lease Reader? Use those instead.
Bought a property and inherited the seller’s completed CAM reconciliation? Upload their workbook and we’ll re-run the math independently, tie out the workbook’s own totals, and cross-check each tenant’s caps, base year, and gross-up against the leases — so you know whether it was reconciled correctly before you rely on it. Read-only; nothing is approved.
Upload the prior owner’s CAM reconciliation from an Excel
(.xlsx) workbook. It’s read privately in your browser. We check the math
to make sure it was calculated correctly. To see whether it followed the lease language, upload the
leases in the Lease Reader first.
Shown at the top of the exported findings report.
Your executed leases, abstracted into a searchable, cited database — with a portfolio risk score and prioritized findings. Every term links to its lease language, and nothing is treated as reviewed until you confirm it.
Leases
Select a lease to review its abstracted terms and citations.
Prioritized by severity and estimated financial impact. Acknowledge, resolve, or dismiss each as you work it.
Settings and back-office work that isn’t part of running a reconciliation.
What is waiting on you in Admin.
Create a secure invite for an owner to accept the NDA and upload their leases. Nothing is analyzed automatically — you run extraction when you’re ready to review, and it lands in Operational Intelligence.
Create an intake invite
All-time, across every analyzed lease and accounting bundle.
Loading…
Calibrating what the app assumes. Reviewed periodically — when we change a behaviour, the answers about it come back for a second look.
The app never refuses to reconcile. When a number is missing it substitutes something sensible-looking and carries on, so a reconciliation with a gap in it looks exactly like a complete one. For each number below: when it’s missing, is what we do what you would do? Answers save as you go and are shared with the team.
Which general-ledger accounts belong in a CAM reconciliation, decided by the account’s description — account numbers differ by owner. First matching rule wins; team rules outrank the defaults. Lease language then carves costs out per tenant.
Things leases can say that TrueUp does not fully handle yet, worst first, and how many of your leases say each one. You can only read this list; the TrueUp team keeps it up to date. “Create issue” sends the item to the people who build TrueUp.
Admins can see every team’s projects and use this Admin section. Anyone with an @intelligentbuildings.com or @stiles.com account can still sign in — this only decides who is an admin. A person appears here after they sign in once.
Allow private storage and automatic reading of vendor agreements once for a workspace. Property exceptions apply within that workspace.
An org decides which skin its members see: colours, type, corners and brand assets. It changes appearance only. It does not change what anyone can open, and it never changes a calculation. A person with more than one org chooses their primary in their profile menu.
Adding a new skin. Hand the design brief to whoever builds the package (for example Claude Design).
It lists every colour role, asset and contrast rule, and what comes back installs as skins/<id>/ with
no guessing. Check the result with npm run lint:skin-contract, then preview it from your profile menu
before assigning it to an org.
Check a skin package. Choose the .zip from the designer. TrueUp checks it and tells you what to fix.
A package that passes can be sent for review as a pull request; nothing goes live until a person reviews, merges and deploys it.
Pick a property to load it as a Sample project. Made-up data, left out of every real figure.
What the lease library actually contains, and how much of it is solid enough to rely on. Read-only — nothing here changes a reconciliation.
Is beyondbricks.ai working, are requests being answered, and is anything about to run out? Read-only — nothing here changes the website.
A shared record of who contributed what, with the evidence, for discussion with counsel.
Price the managed CAM reconciliation service for a customer — nothing here changes a charge, a reconciliation or billing.
A ninety-second interactive story for owners. Make a personal link for each person you show it to, see what they looked at, and withdraw it any time. A concept draft for discussion.
Fictional examples only. Keep it inside the team until Stiles has approved it in writing.
The public address shows only a holding page. The story opens only through a link made above.
Same building listed twice? Review a pair and merge it. Nothing merges without your confirmation, and the other copy is archived, never deleted.
Diagnostics for whoever is checking the numbers. Nothing here changes a reconciliation.
“Show the math” — full detail
“Show the math” — the step-by-step breakdown of a tenant’s lease-driven adjustments — is always visible to managers on Step 5 · Lease terms per tenant; nothing here controls that. This turns on an additional, full-detail layer nested inside it (every mechanism including ones that don’t apply, unrounded figures, and a copy-to-clipboard snapshot for a bug report). Nothing here changes a reconciliation. While it’s on, every screen shows a small “Show the math” badge in the nav.