Questions, answered without the hedging.

Most landlords are collecting rent within a day. Add your properties and units, invite residents by email, and connect a bank account for payouts. Larger portfolios can import from a spreadsheet, and Pro customers get an onboarding specialist who does the migration with them.

Yes. Properties, units, tenants and active leases import from a spreadsheet, and you can upload the existing lease documents so the history lives in one place from day one.

No. The resident portal is a website that works properly on a phone. Residents pay, file maintenance requests, book amenities and vote from the browser they already have.

Fourteen days of the whole product, no card. Collect a test payment, generate and sign a lease, invite residents, post a dues run and hold a board vote before you decide anything.

Residents pay by bank transfer or card from their portal. They can set up autopay themselves, funds settle to your connected bank account, and every payment posts to that unit’s ledger — and to the books — as it clears.

Yes. Set the grace period and the rule — flat, percentage or daily — per property, and Villagely applies it to overdue balances and notifies the resident. Nothing to remember on the fifth of the month.

Bank transfers are free to you and can be absorbed or passed to the resident. Card payments carry the processor’s standard fee. Villagely does not take a percentage of the rent itself.

Owner statements show collected, fees and payout per property, generated on demand and emailed. They reconcile to the ledger because they are built from it. Owners get their own login to see them without asking you.

You void it, and the void posts an equal and opposite journal entry. The original stays visible with the reason attached. Nothing in the ledger is deleted, because a deleted entry is an unanswerable question later.

Not yet, and it is the one thing on this site that does not work today. Credit, criminal and eviction history requires a credentialed consumer-reporting partner and the compliance obligations that come with one. Today you can record an applicant and your own notes, and attach a report you obtained elsewhere to their application. What we are building.

The leasing tools apply the same criteria to every applicant and keep the record of your process. No software can guarantee compliance, but a standardised application and an audit trail make treating applicants consistently the path of least resistance.

Against the tenant and the unit, with a full history. E-signature captures who signed what and when, and the signed copy is stored rather than emailed and forgotten.

Yes, and this is the part most rental software skips. Recurring dues schedules and special assessments, violations with dated notices and fines that post to the member’s ledger, amenity reservations with approval, and board elections where each member gets one ballot and results stay sealed until voting closes. All of it ships today.

Yes — announcements, an events calendar, the governing documents and contact details on the community’s own villagely.io subdomain, served over HTTPS from the moment you create it. Bringing your own domain is still to come; we would rather say so than let you discover it.

In how they are raised, not in where they land. A dues schedule bills the whole community on a cadence; the resulting charges sit on the same ledger as rent, take the same payments and autopay, and reach the books the same way. An owner who also rents sees one balance.

No. Nobody can, including you. A tally visible mid-election influences who bothers to vote, so results are sealed until the vote closes. Quorum progress is visible; the standings are not.

Yes. Double-entry books post automatically from the rent ledger — nothing is typed twice — with a chart of accounts, income statement, balance sheet and profit and loss by property. The posting engine refuses an unbalanced entry rather than storing one.

There is a sub-ledger per beneficiary and a three-way reconciliation across the bank balance, the book balance and the sum of the beneficiaries. A disbursement larger than that beneficiary’s balance is refused outright, with the actual figure — the commonest trust violation is made impossible rather than warned about.

It produces the totals: payments per vendor per calendar year with the reportable threshold applied, so you know who needs a form. Vendor TINs are encrypted with AES-256-GCM and only the last four digits ever reach a screen.

Show them. The books are ordinary double-entry with reversals rather than deletions, and every figure traces to the ledger entry that produced it. If you hold client money under a state statute, have your accountant confirm the specifics for your jurisdiction before this becomes your system of record.

There is a read-only public API at api.villagely.io/v1 with per-key rate limiting, and keys you issue and revoke yourself. Your data is not held hostage to keep you subscribed.

Only the people you have given access. A document attached to a resident cannot be made public — not by a setting, not by mistake. Governing documents are published deliberately, one at a time.

The last four digits, and nothing else. Full account numbers are never written down.