Automated e-transfer reconciliation should complete the payment, not simply identify a likely tenant. The software needs to find the correct residential or commercial account, confirm the amount due, post the payment and issue the invoice.
Key takeaways
- Use the current rent and balance before deciding whether a payment is complete.
- Finish the account update and invoice instead of stopping at a suggested match.
- Send uncertain payments to staff with the useful account information already attached.
Start with the rent actually due
Accurate reconciliation depends on current tenant, unit, lease, rent and balance information. Residential rent increases and commercial lease escalations must already be reflected in the amount expected.
Match the payment to the correct account
The sender may be the tenant, a business, a spouse or another payer. The software can use the available payer, tenant, unit, lease, payment and balance information instead of relying on the sender name alone.
Complete the payment automatically
Once the software finds a reliable match, it posts the payment to the account and issues the invoice. Moe created the first property management software to automate this entire process, with the invoice issued within five minutes of the e-transfer being accepted.
Send uncertain matches to staff
If the available information is not enough to identify the correct account, the payment stays available for review. Staff can resolve it before money is posted to the wrong tenant or lease.
Use current account data for residential N4 notices
For eligible unpaid residential rent in Ontario, the software can populate and issue an N4 notice using the current tenant, tenancy, balance and amount owed. Commercial arrears follow a separate process.
What makes e-transfer reconciliation complete?
A useful system follows the accepted payment all the way to the correct residential or commercial account, invoice and remaining balance. Matching alone leaves most of the administrative work unfinished.
| Decision area | Useful evidence | Warning sign |
|---|---|---|
| Rent due | Current residential increase or commercial escalation is reflected | The payment is compared with an old rent amount |
| Account match | Payer, tenant, unit or lease and balance agree | The sender name alone decides the account |
| Payment completion | The account is updated and the invoice is issued | The software only suggests a possible match |
| Unclear payment | Staff receive the transfer and likely account context | The closest account is chosen silently |
| Unpaid residential rent | Current balance can continue into the N4 process | Tenant and amount-owed information must be re-entered |
Example: a spouse pays the residential tenant’s rent
The sender name does not match the lease, but the amount, unit, current rent and account history may still identify the correct tenant. When those details support a reliable match, the software can post the payment and issue the invoice. When they do not, staff receive the transfer for review instead of finding it later on the wrong account.
Apply this to your software project
Bring one example of the workflow, the people involved, the bottleneck you see most often and what should improve. You do not need a finished specification.
For help with this decision, see Automation that removes repetitive work without removing control.