Sign in to Fortress OSIntegration Partner · Utility Management
MuniBilling + Fortress OS
Utility billing through MuniBilling, connected per property, posting to the ledger in Fortress OS.
Updated · 3 min read
What is the MuniBilling + Fortress OS integration?
MuniBilling is utility billing software. Fortress OS connects to it per property, so utility charges reach the resident ledger on their own. It follows the same pattern as the other utility connections: switch it on at the sites that use it, leave it off at the ones that do not.
Key takeaways
You enable it per property, so only the sites billing through MuniBilling use it.
Utility charges land on the resident ledger without a monthly import.
Your resident gets one account and your team keeps one set of numbers.
How does MuniBilling work with Fortress OS?
You enable MuniBilling per property in Integrations Setup. Portfolios rarely bill utilities the same way everywhere, so the connection is a property-level setting and not a portfolio-wide switch. Once you turn it on, utility charges flow to Fortress on their own.
What data flows between the two?
Charges calculated in MuniBilling come across to Fortress and post to the resident's ledger with rent and other recurring items. Your team stops keeping a parallel spreadsheet, because nothing is left for it to track.
Who handles the setup?
Our integrations team handles documentation exchange, API keys, and end-to-end testing. Most MuniBilling connections go live in a few weeks. You can request a setup any time.
Why should you connect MuniBilling to Fortress OS?
The effort in utility billing goes into moving numbers between the system that calculated them and the system that collects them, every month, by hand. Connecting the two takes that job off your team's calendar.
What changes once you connect MuniBilling?
Same utility management tool. Different day-to-day for your team.
| Daily task | Without the integration | With Fortress OS + MuniBilling |
|---|---|---|
| Posting utility charges | You export, reformat, import, then chase what did not land. | Charges post to the resident ledger. |
| Answering a billing question | You open MuniBilling, then the ledger, then compare. | You read the charge on the account with everything else. |
| Onboarding a property | Someone wires up a manual process for each new site. | You enable the connection on the property. |
| Month-end | Your team reconciles two systems that were never in sync. | Your team closes one set of numbers. |
Tags
- MuniBilling
- MuniBilling integration
- Utility Management
- Fortress OS
- integration
- property management software
- affordable housing
Frequently asked questions
Quick answers about how MuniBilling and Fortress OS work together. Don't see your question? Ask us →
How is MuniBilling connected?
Per property, in Integrations Setup. You enable each site that bills utilities through MuniBilling on its own.
Where do the charges appear?
On the resident's ledger in Fortress, next to rent and other recurring charges.
Can we run MuniBilling at some properties and Conservice at others?
Yes. Both are per-property settings, so a portfolio can use a different utility billing provider at different sites.
Do we need our own MuniBilling account?
Yes. You keep your MuniBilling subscription. The connection to Fortress OS is part of Fortress.