Key topics
Related public pages
If you need the product, API or operations page rather than only the article, start with these VPOS.am sections.
Rent payment should be connected with lease period
One amount without contract, property and period does not explain which month and unit tenant paid for.
In rent and property management, payment belongs to contract, property, tenant, period, deposit, utility charge or penalty. If payment link is sent as simple amount, operator later finds payment purpose manually.
Practical model creates tenant invoice or payment request from CRM/ERP: lease id, property id, tenant id, invoice period, amount, currency, due date and request id are fixed before payment. Period status changes only after verified payment.
- connect payment request with lease id;
- store property id, tenant id and invoice period;
- do not close period from payment screenshot;
- separate rent, deposit, utilities and penalty lines.
Deposits, utilities and late fees need rules
Deposit, utility charge and late fee have different basis, timing and refund logic.
Security deposit, rent, utilities, maintenance fee and late fee should not be stored as one paid amount. Each charge has its reason, period, contract basis and possible refund path. Late fee or penalty should not be applied automatically without contract rules and current review.
If recurring charge is not confirmed by provider and contract, safer approach is scheduled invoices, payment links and reminders. Manual adjustments should enter audit log so tenant, manager and accounting see one history.
- store line type and contract rule version;
- do not promise auto-charge without provider support;
- late fee needs basis and review path;
- deposit refund should not delete original payment.
Reconciliation should show debt and overpayment
Property manager should see paid, overdue, partial, refund and overpayment by every property and period.
For property management, bank statement is not enough. Team needs tenant ledger: which period is closed, where partial payment exists, where overdue remains, where overpayment exists, which deposit was refunded and which charges wait for review.
Reconciliation compares tenant invoices, verified payments, refunds, overpayments, CRM tasks, ERP export and provider report. Payment layer stores ids and statuses, while contract documents and personal data stay in CRM/ERP with restricted access.
- show balance by tenant/property/period;
- partial payment should not close whole period;
- overpayment is stored as separate ledger event;
- reconcile provider reference with ERP/accounting export.
FAQ
Can rent be paid by payment link?
Yes, if payment link is connected with lease id, tenant id, invoice period, amount and expiration, and status appears after server-side verification.
How should tenant deposit be recorded?
Store deposit as separate ledger line with contract basis, date, amount and refund path. Deposit refund should not delete original payment.
Can rent be charged automatically every month?
Only if provider, contract and business rules support recurring charge. Otherwise use scheduled invoices, payment links and reminders.
