Treasury and transparency for residential buildings
What lands on the committee
becomes organised information.
HomeApp helps a committee see recorded activity, understand what needs review, and maintain order it can explain.
HomeApp does not hold funds or initiate payments.
Running your building shouldn’t feel like a second job.
Payments, expenses and questions arrive from every direction — and land on volunteers.
Every source tells only part of the story.
A bank file, spreadsheet, receipt and correspondence can explain the same event — but the committee has to connect them.
Information gains context — and the source remains visible.
HomeApp imports bank activity from a supported source, classifies and files it against the building, with a visible review state.
The system doesn’t guess just to look organised.
What is clear can progress. What is not stays marked for committee review.
Less chasing. A clearer picture you can explain.
The committee can see what happened, what needs review, and what to do next.
The HomeApp principle
Clear can progress.
Unclear stays visible.
Bank activity imported from a supported source is classified and filed against the building. When certainty is missing, a review state remains — not an invented answer.
A treasury memory you can trace
Don’t just see a balance. Be able to explain it.
HomeApp connects recorded activity with its context and keeps the source in view. Corrections do not erase the trail — so the committee can explain what happened later.
A product contract, not a promise wall
What is available now, in pilot, and next.
Bank activity import, classification and a visible review state.
Payment allocation to a unit and charge, retained with its source and corrections.
Owner, occupant, payer and billed recipient remain separate roles over time.
Separate Excel and Hombi migration paths, subject to pilot import validation.
Start from the building you have
Move without throwing away the history.
Import bank activity from a supported source today. Excel and Hombi migration paths are being evaluated in pilot, with assisted migration planned for paid onboarding.
From Excel
A separate self-service path is being developed for residents, balances, payments and opening data.
From Hombi
A dedicated migration path is being developed, while preserving the option to continue with an existing supported clearing arrangement.
Assisted migration
Personal guidance for opening balances, historical records and reconciliation is planned as part of paid onboarding.
Clear financial boundaries
Recorded money needs clear boundaries.
HomeApp records activity imported by the committee. It does not hold funds, initiate payments, or connect automatically to a bank account at this stage.
Before you decide
Does HomeApp move or hold funds?
No. HomeApp records activity imported by the committee; it does not hold funds or initiate payments.
How does bank activity reach HomeApp?
The committee imports activity from a supported source. There is no automatic bank connection at this stage.
What happens when a transaction is unclear?
It stays in a review state visible to the committee. The system does not guess simply to present a tidy picture.
Can we start from Excel or Hombi?
Separate migration paths are in development and will be pilot-tested before broader availability.
Is HomeApp a fit for your building now?
Currently suited to a volunteer committee for one building, with a dedicated bank account and the ability to export bank activity or a normalised CSV.
Not yet for teams seeking payment initiation, automatic bank connectivity, or full resident messaging management.