Sign in to Fortress OSIntegration Partner · Utility Management
Conservice + Fortress OS
Utility billing through Conservice, connected per property, posting to the ledger in Fortress OS.
Updated · 3 min read
What is the Conservice + Fortress OS integration?
Conservice manages utility billing and recovery for property owners. Fortress OS connects to it per property, so utility charges reach the resident ledger without your team rebuilding a billing file every month. You turn it on at the sites that use it and leave it off elsewhere.
Key takeaways
You connect it per property, so mixed portfolios run Conservice only where it applies.
Utility charges reach the resident ledger without a monthly spreadsheet.
The utility line on a resident's account matches what Conservice billed.
How does Conservice work with Fortress OS?
You enable Conservice per property in Integrations Setup. That matters for real portfolios, where one region bills utilities through Conservice, another handles it in house, and a third bills no utilities at all. You switch it on where it applies and leave the rest of the portfolio alone.
What data flows between the two?
Utility charges calculated by Conservice come across to Fortress and land on the resident's ledger next to rent and other recurring charges. The resident sees one account, and your team stops maintaining a second version of the same numbers.
Who handles the setup?
Our integrations team handles documentation exchange, API keys, and end-to-end testing. Most Conservice connections go live in a few weeks. You can request a setup any time.
Why should you connect Conservice to Fortress OS?
Your team spends the same days every month moving utility charges from the system that calculated them to the system that collects them. Somebody exports the charges, somebody else reformats them, and a third person fixes the units that did not match. Posting the charges to the ledger removes all three steps.
What changes once you connect Conservice?
Same utility management tool. Different day-to-day for your team.
| Daily task | Without the integration | With Fortress OS + Conservice |
|---|---|---|
| Getting utility charges onto accounts | You export the billing file, reformat it, import it, then fix the mismatches. | Charges post to the resident ledger. |
| Explaining a utility charge | You find the month's spreadsheet and work backwards. | You read it as a line on the resident's account. |
| Running a mixed portfolio | One process for Conservice sites, another for everywhere else. | You switch the connection on per property. |
| Closing the month | Someone reconciles the utility file against what posted. | Your team closes one set of numbers. |
Tags
- Conservice
- Conservice integration
- Utility Management
- Fortress OS
- integration
- property management software
- affordable housing
Frequently asked questions
Quick answers about how Conservice and Fortress OS work together. Don't see your question? Ask us →
Is Conservice turned on for the whole portfolio at once?
No. You enable it per property in Integrations Setup, so you can run it at the sites that use Conservice and leave the rest alone.
Where do utility charges show up?
On the resident's ledger in Fortress, next to rent and other recurring charges, so the account the resident asks about is the account your team is looking at.
Do we keep our own Conservice contract?
Yes. Your Conservice agreement and pricing stay yours. The connection to Fortress OS is part of Fortress.
Can we switch it off later?
Yes. The connection is a per-property setting, so you can turn it off for a site without touching the rest of the portfolio.