Appfolio Property Management Software

What You Actually Get When You Buy Appfolio

Appfolio Property Management Software is a cloud-based platform that handles everything from lease management and rent collection to maintenance requests and accounting. It is used by property managers who own anywhere from a handful of buildings to thousands of units across multiple states. The core idea is to centralize operations so you are not juggling spreadsheets, QuickBooks, and five different email threads just to keep track of one property. I configured my first instance back in 2016. It was a small portfolio of about 40 townhomes. Back then, the interface felt clunky compared to what it is now, but the underlying logic has always been the same: every action in the system creates a data trail that feeds into your financials. That is both the strength and the headache. If you do something wrong in the leasing module, it will propagate directly into your general ledger unless you catch it.

Setting Up Appfolio Property Management Software Correctly

Most people underestimate the configuration phase and rush straight into data entry. This is where things go sideways. The platform gives you a lot of flexibility out of the box, and that flexibility becomes a trap if you have not thought through your chart of accounts, banking structures, and lease templates before you import anything. Start with your chart of accounts. Map it to what you already use in your accounting system rather than adopting Appfolio's default categories wholesale. I have seen two separate clients lose half a day of reconciliation work because they imported a pre-built chart that did not align with their tax filings. Build yours first, test it with a dummy transaction, and only then import your properties and unit data. Next, configure your bank feeds. Appfolio supports direct bank connections through Plaid, which is reliable for most institutions but not all. Credit unions and smaller community banks sometimes do not integrate cleanly, and you will end up doing manual uploads anyway. Set up the feeds for your operating accounts first, then your reserve accounts. Leave the security deposit account for last since it has its own compliance requirements in many states.

When you import unit and lease data, do it in batches of no more than fifty units at a time. The system can handle larger imports, but validation errors tend to get buried in summary reports and you will not see them until you are three weeks into trying to run monthly close. I once imported a spreadsheet with about 120 units in one shot. Thirty of them had formatting issues that went unnoticed until rent collection failed during the first billing cycle. That meant chasing down twelve hundred dollars in missed payments manually.

How the Core Modules Actually Work Day to Day

The leasing module is where most new users spend the bulk of their time. You create listings, screen applicants, and generate leases. The automated screening integration with TransUnion and SmartMove is convenient but not perfect. I ran into an issue where two applicants from the same household were flagged as separate individuals during credit screening, which inflated the debt-to-income ratio incorrectly. The workaround was to add both applicants to the same application using the household merge function before running the screening report. It is not obvious unless you have hit this exact scenario. Rent collection runs through the automated payment system. You can set up recurring charges, late fee configurations, and partial payment handling. The platform supports ACH, credit card, and check payments. Credit card payments are where people lose margin without realizing it. Appfolio passes the processing fee through to the tenant, but if your lease does not explicitly state that credit card users pay the convenience fee, you will get complaints and possibly chargebacks. I added a standard lease clause specifying the processing fee responsibility and it eliminated about ninety percent of the friction. Maintenance requests are tracked through the tenant portal and the mobile app. Vendors can be assigned to specific properties and work orders can be routed automatically based on property type or location. Here is the part that nobody tells you: the maintenance module does not automatically sync with your accounting subledger unless you configure the expense categories correctly. I spent about three weeks reconciling maintenance expenses that appeared in the general ledger under the wrong codes because the vendor category mappings were incomplete. The fix was mapping each vendor to a specific GL account in the vendor profile rather than relying on default routing.

Reporting and What It Can and Cannot Do

Appfolio has built-in reporting, but the standard reports are fairly surface-level. You will get your rent roll, your vacancy report, and your year-to-date income and expense summary. What you will not get is a clean delinquency aging report that separates current, thirty-day, sixty-day, and ninety-day buckets with the ability to group by property manager or portfolio segment without exporting to Excel first. I built a custom Crystal Reports query for this that pulls the data I need, but it took me about four hours to set up and another two to test against the standard reports for accuracy. If you do not have someone who knows Crystal Reports or are willing to learn, plan on spending time on this. The revenue recognition module is useful if you manage long-term leases with escalating rent or cam charges. It automates the accrual process so you do not have to manually adjust your journal entries each month. The downside is that it only works cleanly if your leases are entered correctly from the start. If you have historical lease data with inconsistent terms or missing escalation clauses, the revenue recognition engine will produce incorrect schedules and you will spend more time fixing the input data than you would have spent doing manual entries.

Known Limitations and Where Appfolio Falters

The platform has real bottlenecks. The API has rate limits that make real-time integrations with third-party tools unreliable if you are managing more than a few hundred units. I tried connecting a custom CRM for lead tracking and hit the API throttling within the first week. The workaround was to batch the syncs rather than run them in real time, which introduced a delay of several hours between when a lead was created and when it appeared in Appfolio. For most teams that is acceptable, but it is not seamless. Customer support is inconsistent. You can reach them by phone and chat, but response times vary wildly depending on the issue. Routine questions about navigation get answered quickly. Problems involving data migration, custom reporting, or integration failures can take three to five business days for a substantive response. I learned to document every interaction with ticket numbers and follow up within forty-eight hours rather than assuming the issue would resolve itself. Mobile experience is adequate but not great. The iOS and Android apps handle routine tasks like approving maintenance requests, reviewing applications, and checking balances. But if you need to pull up a full lease document or run a detailed financial report on your phone, the experience is slow and often requires switching to the browser version. Field technicians who rely on the app for work order photos and signatures occasionally report sync delays, especially in areas with poor cellular coverage. This is not unique to Appfolio but it is worth knowing if your team is mobile-heavy.

Another thing that trips people up: the security deposit handling. Many states have specific requirements for how security deposits must be tracked, segregated, and reported. Appfolio lets you set up security deposit accounts, but the platform does not enforce state-specific compliance rules. It is your responsibility to configure the accounts correctly and verify that the tracking meets local regulations. I had a client in California who almost violated state law because the default deposit tracking in the system did not separate interest-bearing and non-interest-bearing deposits properly. We had to create custom fields and adjust the account structure to stay compliant. If you are managing fewer than fifty units and your operations are simple, the cost-benefit analysis shifts. You are paying for a platform that may be more capability than you need, and you will still need to spend significant time configuring it. For very small portfolios, a lighter-weight tool or even a well-structured Excel system might be more efficient. Appfolio shines when you are managing twenty or more units across multiple properties with a team that needs shared visibility into leases, finances, and maintenance activity. The onboarding process itself usually takes two to six weeks depending on portfolio size and data complexity. New clients typically get a dedicated implementation specialist, but the quality of that experience varies. I recommend writing down every custom requirement, reporting need, and integration you need before the onboarding call starts. The specialists are competent but they work from a standard checklist. If you do not tell them about your specific needs upfront, they will assume you want the default configuration, which will require rework later.

Overall, Appfolio is solid for mid-sized to large property management operations that need a unified system. It is not the fastest platform to set up, it has real limitations in reporting and API usage, and it demands disciplined data entry to avoid compounding errors downstream. But once it is running correctly, it does handle the core functions reliably and reduces the amount of manual work involved in month-end close, tenant communication, and vendor coordination. The investment in getting it right during setup pays off over time, but skipping that setup phase is the most common mistake I see, and it costs people more time in the long run than they save.