The short answer: integrating property management and accounting software means your operational data reaches the general ledger without rekeying. That covers rent charges, payments, deposits, vendor bills and work order costs. There are two ways to do it. A connector syncs two separate systems on a schedule, and a single platform keeps operations and accounting on one database. Either way, decide which system owns each record, map every charge code to a GL account, and reconcile the rent roll to the ledger every month. Integration problems usually come from mapping and timing.
I work on ERP and NetSuite topics at RIOO, and I have seen both models in practice. This guide covers what has to connect and where it usually breaks.
What has to flow between the systems
| Data | Starts in | Lands in the ledger as |
|---|---|---|
| Rent and recurring charges | Lease and rent schedule | Receivables and rental income by property |
| Resident payments | Payment portal or bank file | Cash and receivables, applied to charges |
| Security deposits | Move in | Deposit liability, often in a separate bank account |
| Vendor bills from work orders | Maintenance | Payables and repair expense by property |
| Owner contributions and draws | Owner accounting | Owner equity and cash |
Connector or single platform
Connector between two systems
The property system and the accounting system stay separate. A connector sends summary or detail entries on a schedule, often nightly. This can work for small portfolios. The risks are sync failures, duplicate entries and two versions of the truth between syncs.
One platform for operations and accounting
Leases, residents, work orders and the general ledger share one database. There is no sync job to fail, and a payment posts to the ledger as it is applied. The trade off is a larger implementation up front.
Five decisions before you connect anything
- System of record. For each item (tenants, vendors, properties, charge codes), name the system that owns it. Changes happen there and nowhere else.
- Charge code mapping. Every charge code needs one GL account. "Pet rent" and "pet fee" cannot share a code if they post to different accounts.
- Detail or summary. Decide whether the ledger gets one line per charge or one total per property per day. Detail helps audits. Summary is lighter.
- Timing. Decide when entries post and what happens at month end if a sync runs late.
- Error handling. Decide who gets the alert when an entry fails, and how fast they fix it.
How a connector sync works day to day
If you go the connector route, it helps to know what actually happens each night, because that is where problems usually start.
- Pick up changes. The connector collects new and changed records since the last run: charges, payments, credits, vendor bills and new tenants or vendors.
- Translate. Each record is mapped to the accounting side. A charge code becomes a GL account, a property becomes a class or subsidiary, a tenant becomes a customer.
- Post. Entries are created in the ledger, in detail or as daily totals.
- Report. A log lists what posted and what failed. A failed record waits until someone fixes it and runs it again.
Ask three questions of any connector. What happens to a record that fails? Can it post the same entry twice if a run is repeated? Who sees the error log each morning? If nobody owns that log, failures pile up until month end.
Access and controls
Integration also changes who can touch financial data. Give the connector its own service user with the narrowest access it needs, not an administrator login. Limit who can create charge codes and GL accounts. Keep an audit trail of every posted entry with its source record, so an auditor can trace a ledger line back to the lease and the payment. If tenant bank or card details move between systems, confirm how they are stored and that your payment processor handles the card data.
Training after go live
Integration errors are often made by people. Leasing staff create a new fee without telling accounting. Maintenance closes a work order with the wrong property. Write a one page guide for each team that says which fields feed the ledger, and review the first two month end closes together.
A worked example: the month end that did not tie
Here is a fictional case. A 900 unit portfolio uses a nightly connector. On 31 March, the rent roll shows receivables of $184,300. The general ledger shows $191,650. The gap is $7,350.
The controller traces it to three causes. A sync on 29 March failed, and 14 payments totalling $5,600 never reached the ledger. A "parking" charge code had been retired on the accounting side only. So $1,200 of March parking credits were rejected by the sync and never reached the ledger. And $550 in payments was applied to the wrong unit and left as unapplied cash. Together, $5,600 plus $1,200 plus $550 is $7,350.
Each cause has a fix. Alert on any failed sync the same morning. Block new charge codes until they are mapped. Clear unapplied cash weekly, as described in unapplied cash in property accounting.
Reconcile every month
Tie the rent roll and aged receivables to the GL control account at each month end. Tie deposits held to the deposit liability and the deposit bank account. Investigate any gap before you close. The month end rent roll reconciliation walks through the checks.
Moving data when you change systems
An integration project often starts with a migration. Move open balances by tenant, not one total. Bring deposit balances with their history, and lease dates with every amendment. Agree a cutover date and reconcile both systems on that date. Our guide to the management transition data handover lists what to request.
Where RIOO fits
RIOO is built natively on NetSuite, so leases, residents, work orders and the general ledger sit on one platform. There is no nightly sync between property operations and accounting, and charges and payments post to the ledger as they happen. See how NetSuite property management works in RIOO.
Integration questions
How long does an integration take?
A simple connector can be live in weeks. A full platform implementation with migration usually takes months, depending on portfolio size and data quality.
Should we post detail or summary entries?
If you have audits or owners who ask questions by unit, post detail. Summary works for small, simple books.
Who should own the charge code list?
Accounting. Operations can request new codes, but accounting maps and approves them.
What is the first thing to check when the ledger and rent roll do not match?
Failed or late syncs, then unmapped charge codes, then unapplied cash. Those three cover the usual gaps.
