A deposit is not revenue. It is money you owe back until the day you legitimately keep it. This article explains why boards, property managers, commercial operators, and school business officials should ask every software vendor one blunt question: who is actually holding the money? It also explains how URBI answers it.
One note before we start. This article is general information, not legal advice, and rules on resident funds vary by jurisdiction. Please confirm the specifics for your properties with your own counsel.
Why does it matter who holds resident money?
When a resident pays rent, a condo fee, tuition, or an amenity deposit, that money belongs to the property or to the resident. It never belongs to the software company in the middle. Yet with some platforms, funds pass through accounts the vendor controls before they reach you. That creates questions a careful board should not leave unanswered.
Think about what a deposit is on paper. The moment you collect it, your books gain an asset and a matching liability. You are holding someone else's money against a future event: the party room gets cleaned, the equipment comes back, the booking ends without damage. Until then, you may owe every cent back. If a third party is holding that money for you, your liability does not go away. You have simply added a new risk: the risk that the third party delays, freezes, or fails.
The same logic applies to operating funds. If your rent or fee revenue sits in a vendor's pooled account for days, your cash position depends on that vendor's health, processes, and priorities. Boards have fiduciary duties. Commercial operators answer to owners. School business officials answer to auditors and their community. All of them need a clean answer to where the money sits at every step.
What should you ask every software vendor about the flow of funds?
Before you sign with any platform that touches payments, ask these questions in writing and keep the answers with your records:
- Who holds the funds in transit? Does the money move through an account the vendor owns, or through an account that belongs to your property?
- Where do deposits sit? In your account, or in the vendor's? Who earns the float, and who controls the refund?
- What happens when a refund is due? Can you return a deposit promptly, and does anyone take a cut on the way back?
- What is the record? Can you produce a complete history of every payment, refund, and decision if a resident, an auditor, or a court asks?
- Who inside your organization can see the money? Can you limit financial visibility to the people who should have it?
A vendor with a clean model will answer these quickly and in plain language. Hesitation is itself an answer. Our condo board guide to choosing building software covers the broader evaluation, but the funds flow questions deserve their own meeting.
How does URBI handle resident payments?
URBI is built so that the honest answer to "who is holding the money" is always: you are. Every property on URBI has its own connected Stripe account. When a resident pays rent, a condo fee, an amenity booking, or an event ticket, the money lands in that property's own account, then flows to the property's bank on the normal payout cycle. URBI never holds the funds and never touches them along the way.
This is not a small technical detail. It means there is no vendor pooled account between your residents and your bank. It means a question from your auditor about a specific payment traces to your own account, not to a statement you have to request from a software company. And it means that the platform's role stays what it should be: software that records, reminds, and reconciles, not a middleman standing in your cash flow.
The payment experience on top of that foundation is modern. Residents pay in the app with Apple Pay or Google Pay, or through a simple portal link with no account required. Autopay is built in, so recurring charges collect themselves. Payment reminders are first class, so the awkward chasing conversations mostly disappear. The same model runs across residential buildings, commercial properties, and schools, where the platform speaks the right language for tuition and registration deposits instead of rent and security deposits.
What happens with amenity deposits specifically?
Amenity deposits are where the liability question gets most concrete, because refunds are the normal outcome. A resident books the party room, pays a deposit, hosts the birthday, and expects the deposit back within days.
On URBI, that deposit sits in the property's own account, held like escrow until the booking resolves. If the room comes back clean, you refund it, and there is no additional fee on the refund. If there is damage, you keep what your rules allow, and the record shows why. Either way, the money never left the property's control while the question was open. We walk through the resident side of this in detail in our article on amenity booking deposits and the tenant experience.
Cancellation rules are enforced automatically, and if you close an amenity for maintenance, the system flags conflicting bookings so the manager can resolve or refund them in one flow. Fewer manual steps means fewer disputes, and fewer disputes means fewer letters from lawyers.
How do you prove what happened when someone asks?
Money questions eventually become record questions. Who charged this, who refunded that, who changed the rule, who approved the exception? URBI keeps a permanent audit trail on every action: every payment, every role change, every vote, every waiver, every check in, and every action taken by the AI. When a board member, an owner, an auditor, or opposing counsel asks what happened on a given Tuesday, the log answers in one query rather than a week of email archaeology.
Access is controlled just as deliberately. Permissions follow roles, with per person overrides for real life. A board treasurer can be granted access to financial detail while a probationary staff member is locked out of financial dashboards entirely, without inventing a new role for either of them. Who can see the money is a decision you make once and can defend later.
For operators who want the accounting to live in the same system, URBI's full accounting product is in beta, so collected payments and the ledger that explains them can eventually share one home.
Frequently asked questions
Does URBI ever hold resident funds?
No. Every property on URBI has its own connected Stripe account. Payments go from the resident to the property's account and then to the property's bank on the normal payout cycle. URBI never holds or touches the funds, so there is no vendor pooled account sitting between your residents and your bank.
Are amenity deposit refunds charged an extra fee?
No. When a booking ends and the deposit should go back, you refund it from the property's own account and there is no additional fee on the refund. The deposit sits in the property's account, held like escrow, until it is either returned to the resident or kept under your rules.
Can we limit which staff see financial information?
Yes. Permissions follow roles, and per person overrides handle the exceptions. You can give a board treasurer deeper financial access while keeping a new staff member out of financial dashboards entirely. Combined with the permanent audit trail, you always know who could see what, and who did what, at any point in time.
Do residents need an app account to pay?
No. Residents who use the app get Apple Pay, Google Pay, saved payment methods, and autopay. Anyone else can pay through a secure portal link sent by email, verified with a one time code, with no download and no account creation. Payment reminders keep both groups current without manual chasing.
If your board or your business office cannot say exactly where resident money sits tonight, that is worth fixing before it is worth explaining. Write to hello@myurbi.co and we will walk you through the funds flow for your properties, question by question.
