Setting Due Date and Paid Date on a Payment

Every payment in Landager records two distinct timestamps to build a complete accountability trail.

Due Date

The Due Date represents the day rent was contractually expected.

• This is typically your globally configured Rent Due Day (e.g., the 1st of the month).
• You set this field to reflect the expectation, regardless of when the tenant actually paid.

Example: If rent is due on the 1st of every month, and you're logging March rent, the Due Date is March 1, 2026.

Paid Date

The Paid Date represents the day you actually received the money.

• If the tenant paid on time: the Paid Date might also be March 1.
• If the tenant was late: the Paid Date might be March 8.
• If the tenant pre-paid: the Paid Date might be February 28.

Why Track Both?

1. Late Payment Documentation

Looking at a single payment record, if the Due Date is March 1 and the Paid Date is March 8, you have irrefutable proof the payment was 7 days late. This is essential evidence if you need to justify applying a Late Fee or making arguments during an eviction hearing.

2. Collection Efficiency Analysis

Over time, the gap between Due Dates and Paid Dates across all your tenants reveals your portfolio's payment reliability. If most tenants pay within 1-2 days of the due date, your portfolio is healthy. If the average gap is 7-10 days, you might need to implement stronger late fee policies.

3. Cash Flow Accuracy

Your bank balance reflects when money actually arrived, not when it was expected. By recording the Paid Date accurately, Landager's financial reports align with your actual bank statements, not just your theoretical expectations.

Best Practice

Never backdate the Paid Date to match the Due Date simply to "make the records look clean." Honest date tracking is the entire point of having a digital system. If a tenant handed you a check on March 8th, the Paid Date is March 8th—period.