Property management accounting. Not your general ledger.
Fortress runs operations. Sage Intacct runs the books.
Two systems. One set of numbers.
A property management system that also tries to be a general ledger forces your investment, management, and construction entities into a box that doesn't fit. So we didn't build one.
Everything that happens at the property
- Rent roll and resident ledgers
- Charges, payments, and deposits
- Move-ins, move-outs, and transfers
- Compliance and certifications
- CAM estimates and reconciliation
Fortress OSEverything your CFO signs their name to
- The general ledger
- Financial statements
- Vendor payments and bills
- Budgets and consolidations
- The chart of accounts
Sage Intacct today. Your call tomorrow.When the software does not connect cleanly to accounting, your team quietly becomes the integration.
Nobody applied for that job.
Your Systems Work. The Gap Between Them Doesn't.
Somebody Types It Twice
The deposit posts in one system, then a person re-keys it into the other. The work isn't hard. It's just the same work, done again, by someone who already did it.
Two Systems, Two Answers
Operations says one number, accounting says another, and the meeting turns into an argument about which screen to believe instead of what to do next.
The Ledger Module Doesn't Fit
A ledger built only for property data has nowhere to put your investment, management, and construction entities. So they get forced into a shape that was never meant to hold them.
Month-End Runs on Nerve
Export a trial balance from the property system, reformat it, then re-key it into the ledger, all before the close deadline hits. If the numbers don't match, someone spends the rest of the day hunting for the one line that's off.
Move-Outs Go Quiet
A resident leaves, the final account statement says a refund is owed, and it waits on someone to notice and walk it over to accounting.
CAM Runs on Last Year's Guess
Estimates were set months ago, the real spend lives in the general ledger, and nobody reconciles the two until a tenant asks a question you can't answer yet.
Where the Numbers Come From
The rest of Fortress writes to the same ledger the accounting sync reads.
AP & Procurement
Invoices get approved against the property they belong to, then go to the accounting system to be paid. The approval trail stays where the work happened.
See AP & ProcurementPayments
Rent, deposits, and fees post to the resident ledger as they land, which is what the deposit journal entries are built from in the first place.
See PaymentsReporting
Occupancy and collections read from the same ledger that feeds the accounting sync, so the operational report and the financials stop disagreeing.
See Reporting
They already liked their accounting system. That was the point.
A Miami investment group runs affordable, conventional, mixed-use, and commercial property in one portfolio. Their old system fought their accounting setup. Fortress connected to Sage Intacct, the system their team already preferred, and left the books exactly where they were.
What Actually Moves Between the Two
Start With the Books You Already Keep
Fortress connects to the accounting system your team already picked, so nothing has to be migrated, rebuilt, or argued about first.
See every integrationA Deposit Posts. The Entries Follow.
Post a deposit and the journal entries go to Sage Intacct on their own, with the reference numbers sitting right there on the deposit.
See the Sage Intacct integrationClose the Period, Not the Books
Fortress closes the operational month once the deposits, move-ins, and work orders are all accounted for, and the month's entries go with it.
Move-Outs Settle Themselves
A final account statement nets the deposit against what is owed, then the refund goes to accounting to be paid instead of onto somebody's list.
Then the Data Comes Back
For CAM, Fortress reads the real balances out of the general ledger, so the reconciliation runs on what was actually spent.
No more messy, manual bullsh*t
soooo, what makes Fortress OS different?
Fortress OS6 / 6Built for affordable housing
Other tools make you bend to fit them. We built Fortress around how affordable housing actually runs. Every program. Every quirk.
Fortress OSYour systems finally talk to each other
Payments, compliance, maintenance, messages. All in sync. No double entry. No copy-paste tax. No swivel chair.
Live in 90 days, not next year.
Most switches drag on the better part of a year. Ours runs on a set 90-day plan, with a dedicated rep and dates your team can hold us to.
...and of course:
Does Fortress OS include accounting?
Yes, the part that happens at the property. Rent roll, charges, payments, deposits, resident ledgers, month-end close, and CAM all live in Fortress. Sage Intacct's own documentation splits accounting the same way. Subledgers hold the transaction detail. The general ledger holds the summary, with a link back to the detail when you need it. Fortress is the subledger. Sage is the ledger. What Fortress doesn't include is the general ledger itself, on purpose.
Why doesn't Fortress have a general ledger?
Because a ledger built into a property management system is only built for property data. Most operators are not just one property company. You've got investment entities, management entities, and sometimes a construction entity, and each one can run its own chart of accounts. A CPA firm that studies real estate portfolios sees this constantly. Entities picked up at different times often carry different account structures, which turns consolidation into a manual exercise every reporting period. Real accounting platforms already solve that. Fortress connects to one instead of building a worse copy.
Which accounting systems does Fortress connect to?
Sage Intacct for larger groups and QuickBooks Online for smaller ones. Sage Intacct is the one most of our multi-entity operators run, and it is the integration this page walks through. See the Sage Intacct integration or the full list on our integrations page.
What data moves between Fortress and Sage Intacct?
Four things. Deposit journal entries post once a deposit is made, with the reference numbers shown right on the deposit. Daily and monthly entries move over at month-end close. Final account statements for prior residents go over too, so refunds can be paid. And for CAM, Fortress reads general ledger balances back out to work out estimates, actuals, and the reconciliation.
Does the data sync both ways?
Yes, and Sage backs that up too. Fortress's own listing on the Sage Intacct Marketplace says it plainly: real-time financial data feeds into Fortress from Sage Intacct. Most of that flow runs from Fortress into your accounting system, since that's where the operational activity starts. CAM runs the other way. Fortress pulls the real balances out of your general ledger, so the reconciliation is built on what was actually spent, not an estimate somebody set back in January.
What happens to our books if we switch to Fortress?
Nothing. That is the point. Your general ledger, your chart of accounts, and your financial reporting stay exactly where they are, and your accounting team keeps working the way they already do. What changes is that the property-level numbers arrive on their own instead of being re-keyed. See how integrations work.
Who should not use Fortress for accounting?
If you want one vendor to own operations and the general ledger together, Fortress is the wrong pick, and we'd rather say so now than three months into an implementation. Fortress is built for operators who already run a real accounting platform and want it fed properly. If your books are a mess today, fix them first. A clean sync won't clean up dirty data. It will just move it faster.