Software by need and cost

Property Management Software Features: A Small-Landlord Checklist in 2026

Software options to compare

Property management

Buildium

Best for: Larger portfolios needing property accounting, leasing and maintenance workflows.

Trade-off: The subscription, transaction charges and optional services need a portfolio-specific cost check.

Explore plans

Choose features from the work you must finish. Check the exact plan and limits, then inspect the output with a realistic case. Keep the original record and a way to correct it. Separate payment status from bank settlement, reports from tax filing and a screening result from a tenancy decision. Confirm exports before making one system the only copy of your records.

Property management software features: a task checklist

Use this list to prepare a demo. Mark a feature required only when you can name the job it must do. Mark unclear plan access unknown, not included.

• Charges: Rent periods, due dates and traceable adjustments.
• Payments: Methods and fees; status and failed-transfer handling.
• Applications: A clear applicant route and relevant fields.
• Screening: Consent, report scope and a correction route.
• Leases: Correct versions and access to signed copies.
• Books: Property detail and bank reconciliation.
• Maintenance: Requests, approvals and completion records.
• Access: Separate permissions for each person doing the work.
• Exports: Usable records outside the account.
• Exit: A clear route for open tasks and final payments.

Property management software features for rent records

A charge records what the tenant owes for a period. A payment records money received. A bank payout records when cash reaches the landlord's account. Software should make those stages clear. A single paid flag can hide a processing transfer or an unmatched credit.

Ask for a demo with a partial payment. The original charge should remain visible and the balance should make sense. Then ask how a refund or correction appears. A ledger that only looks clear when everyone pays in full is not enough to assess the real task.

Due dates and changes

Check how rent changes take effect. A new lease amount may not update a tenant's old autopay instruction. Confirm who must change the schedule and how both sides see the result. Keep the effective date with the edit.

If a tenancy starts or ends during a period, check the charge rule. Do not assume the software's prorating option matches the lease or local requirements. You need a visible calculation and a way to record why the amount differs from normal rent.

Fees and payment methods

Keep the payer beside each method. A free landlord account can still charge the renter. A paid plan can waive bank transfers while cards remain paid. Check the selected plan rather than combining terms from several tiers.

For failed payments, inspect the return and retry sequence. Find out whether a second attempt runs automatically. You should be able to pause a reminder while checking the facts. A payment feature needs an exception route, not just a button that starts a debit.

• Current Avail plan and fee table, checked October 15, 2026.
• Rent collection process.

Applications and screening features

An application tool should ask for relevant information and show the next step. Check the applicant's view as well as the landlord's. A form that looks short on a sales page may lead into several separate tasks. Explain the report fee and payer before the applicant begins.

Do not assume a built-in screening tool produces every report. Check the exact package and coverage. A score may be different from a full credit report. A database result may require identity or court-record checks before it is useful for a decision.

Report handling and correction

Find the route for a possible error. The applicant should know which reporting firm supplied the information. Keep the original report date and package with the decision record. Do not replace the report with a copied score in an unprotected spreadsheet.

If a consumer report affects an adverse decision, notice duties can apply. Check the current official rules and the actual report supplier. A platform's notice template helps with a task; it does not guarantee the final process is compliant. Keep a person responsible for reviewing what is sent.

• FTC guidance for landlords using consumer reports, checked October 15, 2026.
• Tenant screening workflow.

Relevant criteria rather than a default cutoff

Ask whether the software can record your lawful written criteria. A default score threshold is not a reason to adopt it. Check which facts the score uses and how to handle a disputed match. Apply the process consistently while allowing the review required by applicable law.

Keep access to the report separate from general property work. A maintenance helper does not need consumer reports to handle a request. Check the selected plan's permissions before giving teammates broad access to an applicant file.

Lease and document features

A lease tool should preserve the final signed version. Check the date and parties, then the property and terms. A template can reduce typing, but the person completing it still needs to verify the facts and current local requirements.

Ask how amendments relate to the original lease. You should be able to tell which terms apply in a given period. Do not let a new draft overwrite the only signed copy. Keep the history readable outside the vendor account.

Signing limits

Check what the plan counts: signatures, envelopes or documents. Those units can differ. A feature named e-signing may have a monthly limit or a separate charge. Price the signing work you actually do rather than assuming the word means unlimited use.

Find out what evidence accompanies a completed signature. Keep the final document and the relevant completion record. A screen showing that an invitation was sent is not the same as a completed signing process. Check the result rather than the start action.

Storage and retrieval

Confirm the storage limit and file types. Ask where a document is attached. It might sit with a property or a tenancy, or link to one transaction. Those links matter when you later search or export. A folder full of files can be hard to use if it loses the context that explains them.

Open a downloaded document before relying on the system. Check that it is the signed copy and that all pages are present. Keep the original filename or a clear record label. An export should not make the relationship between a lease and its tenancy impossible to trace.

Accounting and report features

Start with the reports you need to deliver. Property-level income and costs are different from tenant balances or owner statements. Ask which plan produces each. A chart of cash flow does not replace the transaction ledger behind it.

Use a sample month with a split repair bill and a transfer between accounts. The split should keep the full bill tied to its payment. The transfer should not create rent income. Check the bank reconciliation after those entries, not just a dashboard total.

Bank feeds need review

A feed can reduce typing but can still miss or duplicate an entry. Suggested categories are a starting point. Check the purpose of the payment against the receipt. Keep a route for correcting an imported item without losing the original reference.

Ask how the software handles a fee deducted from a payout. The full rent receipt and the fee should remain traceable. A net bank deposit is not always the full income record. Keep the provider's batch detail when one deposit contains several tenants.

Reports are not filed returns

A tax-ready report can help sort the facts. It does not decide every tax treatment or submit a return. Keep the asset history and records for unusual items. Check the current IRS rules and the tax year when preparing a return.

• IRS rental property publication, checked October 15, 2026.
• Accounting software comparison.
• Tax filing software options.

Maintenance features

A request form is the start of the job. Ask how a tenant reports an urgent issue outside the portal. Check how a request becomes a work order and who assigns it. A ticket that exists in the account does not mean someone has arranged the repair.

Inspect spending approval. A contractor may need a quote before work starts. Keep the limit and the approving person clear. Check whether the platform records that approval and how a change in scope is handled.

Completion needs evidence

The system should distinguish a reply from a completed repair. Ask how it records attendance, work done and any remaining issue. Keep the invoice and relevant photos with the request. A status marked closed should have a reason you can explain.

If the tenant says the problem remains, check how to reopen it without losing history. A new ticket may be useful, but it should link to the old one. Otherwise repeated faults can look like unrelated small jobs and become harder to investigate.

• Maintenance workflow guide.
• Buildium's published feature scope, checked October 15, 2026.

Access and account controls

List the people who need access and the work each does. An owner may need full records. A bookkeeper needs the books. A repair contact needs a work order. Check whether the selected plan can keep those views separate.

Use separate logins where the service provides them. Do not solve a plan limit by sharing the main account password. Ask how to remove access when someone stops helping. Keep the work history while ending their ability to view new data or move funds.

Payment authority

Find out who can change a bank destination or approve money movement. Those controls should not be assumed from a generic teammate feature. Check whether an approval is required and where the change log appears. A broad account role can carry more authority than a helper needs.

If you use a connected app, inspect its access too. Removing a teammate may not remove an old connector. Keep a list of current connections and their purpose. Review it when the process changes rather than leaving unused routes in place.

AI and automated actions

Distinguish a fixed rule from a model-generated result. A recurring reminder uses known settings. An AI draft can add words that need checking. An agent that sends or changes records needs a defined approval boundary. Check the exact action rather than the feature name.

Use non-sensitive sample data for a demo. Include a missing fact and see whether the tool asks for review. Do not send a real screening report to an AI feature merely to test it. The AI comparison covers task limits and data questions.

Export and cancellation features

Take a sample export early. Check the full ledger and documents, then the message and work-order history you need. Open the files outside the account. A successful download does not prove the files have enough detail to rebuild a record.

Confirm access after a downgrade or cancellation. A plan can restrict a report while still storing the underlying data. Export closed periods before changing access. Keep a clear final period and handle outstanding payments under the service's terms.

A demo scorecard without a made-up score

Use three outcomes for each required feature: documented fit, documented limit or unknown. Add a source and date. Do not turn unknown into a positive checkmark. A small table of concrete outcomes is more useful than a broad score with no explainable basis.

Keep your must-have features separate from preferences. A product that misses one required export should not win because it has many unrelated tools. Compare the remaining candidates by cost and workflow only after the required task is established.

Frequently asked questions

Which feature should I choose first?

Start with the task that is failing in your current process. Name the required output, such as a checked tenant balance or property-level export. Then inspect the exact plan that produces it. A long feature list is less useful than one documented task that the software can complete in your workflow.

Does an included feature mean unlimited use?

No. Check the unit and account limits, then any monthly event allowance. Signing, storage or reports can have separate rules. A menu item can also describe a paid tier. Keep the selected plan beside the feature so a broad product claim does not become an unsupported free-plan promise.

Can I rely on software defaults?

Only after checking them against your records and rules. A default late fee can be wrong for the tenancy. A suggested category or score cutoff needs its own check too. Review the amount and purpose, then the effect on the tenant or books. A feature's availability does not establish the legal or accounting basis for using it.

What is the most useful exit check?

Open a complete sample export outside the account. Check dates and amounts, then the links to documents and rent periods. Confirm how you get the same records after a plan change. Keep a read-only closed-period copy before canceling so a future question does not depend on an active subscription.

Verdict on property management software features

Ask who can change a closed charge and whether the record keeps the old amount. That small control helps explain a balance when staff roles change or a tenant questions a correction.

Choose property management software features from required outputs and clear limits. Check a realistic case, keep a correction route and confirm the export. Do not let feature count replace fit. Use the homepage comparison to inspect platforms once you know the tasks your plan must finish.