Late Fees Configuration

Late fees are a policy decision before they're a software setting. Decide your grace period, your fee structure, and who's exempt — then configure the system to enforce it consistently.

Updated 16 hours ago 3 views configuration billing reservations late-fees

Late Fees Configuration

Late fees are an unpleasant but necessary part of long-stay billing. Done well, they incentivize timely payment without making customers feel nickel-and-dimed. Done poorly, they generate disputes, hurt retention, and consume hours of staff time arguing over $25.

Suprata applies late fees automatically: you configure the rules (grace period, fee amount, whether they recur), and the system charges them to overdue accounts on schedule. The hard part isn't setting it up — it's deciding the policy.

When you'd use this

Configure late fees when:

  • You have long-stay tenants who pay on a recurring schedule (monthly, weekly, seasonal).
  • A fair number of tenants pay late with no consequence currently.
  • Your existing late-fee process is manual, inconsistent, or non-existent, and that's costing you money or causing disputes.

Skip late fees if:

  • You only do transient bookings paid in full at booking — there's nothing to be late about.
  • Your tenant base is small enough that personal communication beats automated penalties.

The late-fee setup screen — define the rules Suprata applies to overdue balances

The mental model

A late-fee rule has four parts:

  1. What it applies to — which asset types or reservation types this rule covers.
  2. The grace period — how many days past due before the fee triggers (e.g., 5 days).
  3. The fee structure — flat amount ($25), percentage of balance (5%), or whichever-is-greater.
  4. Recurrence — does the fee apply once, or every N days the balance stays overdue?

Suprata runs nightly, looks at every overdue balance, checks each rule, and applies the fee if the rule says so. The fee shows up as a line item on the customer's next invoice.

Designing your policy

Think this through before opening the configuration screen.

The grace period

Most operators land on 5–10 days. Recommended starting point: 5 days.

  • Less than 5 days is aggressive. A customer whose autopay glitched on the 1st gets hit with a fee on the 4th — that's a customer-service problem.
  • More than 10 days is so lenient it doesn't change behavior. A tenant who's never going to pay isn't going to pay sooner because there's a fee 14 days out.

The fee amount

Two common patterns:

  • Flat fee — $25 or $50. Simple, predictable, easy to explain.
  • Percentage of balance — 5% or 10% of the overdue amount. Scales with the rent.

Recommended: $25 flat for monthly tenants under $500/month, 5% of balance for tenants above that. Either way, publish the amount on the lease and on the invoice. Surprise fees generate disputes; published fees generate compliance.

Some operators use "$25 or 5%, whichever is greater" — a fine compromise that scales for large tenants without nickel-and-diming small ones.

Recurrence

Two options:

  • One-time fee — applied once when the bill goes overdue, regardless of how long it stays overdue. Easy to understand. Best for shorter cycles.
  • Recurring fee — applied every N days (often every 30 days) the balance is overdue. Pressures chronically late tenants to act.

Recommended: one-time for monthly tenants who occasionally slip; recurring (monthly) for chronic late-payers. You can configure two rules — a default one-time fee and an escalating monthly fee — and they stack on chronic cases.

Who's exempt

Some tenants shouldn't get late fees automatically:

  • Long-time tenants in good standing who had a one-time bank glitch. Reverse the fee manually if it triggers.
  • Tenants on payment plans with explicit written terms.
  • Disputed balances — don't pile fees on a balance the tenant is contesting.

You can override the late-fee rule on a single reservation for cases like these. Use it sparingly and always leave a note explaining why.

Configuring a rule — the typical flow

  1. Open the late-fee setup screen.
  2. Create a new rule with:
    • Name (descriptive: "Standard 5-day, $25 flat").
    • Grace period (5 days).
    • Fee amount (flat $25, percent, or whichever-is-greater).
    • Recurrence (one-time or every 30 days).
    • Which asset types or reservation types it applies to.
  3. Set as default if it should apply broadly.
  4. Test the rule on a single reservation first. Manually overdue a test reservation, wait for the next nightly run, and verify the fee applies correctly with the right note. Don't enable this rule property-wide until you've seen it work on one reservation.
  5. Communicate to tenants before the rule starts billing. A 30-day notice on the new policy is fair and reduces disputes.

Recommended defaults

  • Grace period: 5 days.
  • Fee: $25 flat for tenants under $500/mo, 5% above that.
  • Recurrence: one-time for first occurrence; second monthly application for balances overdue 60+ days.
  • Document the policy on the lease and on every invoice's footer.
  • Review the late-fee report monthly. If a lot of fees are being applied, the more likely problem is that your invoices aren't reaching tenants on time — not that all your tenants are bad.
  • Reverse fees manually for first-time, in-good-standing tenants as a customer-service gesture. Don't reverse for repeat offenders.

Common mistakes

  • Setting the fee too high. A $100 fee on a $300 site rent feels punitive and damages tenant relationships. Stay proportional.
  • Setting the grace period too short. Inviting customer-service calls from tenants whose autopay was processed on the 3rd instead of the 1st.
  • Not communicating the policy. Tenants who didn't know about the fee dispute it; tenants who did sign off rarely do.
  • Letting the rule go live before you've reviewed the first batch of fee applications. A misconfigured rule can apply 100 fees before you notice. Always test on one reservation first.
  • Using late fees as a primary revenue source. They're a behavioral incentive, not a profit center. If 30% of your tenants pay late, your billing process is broken, not your tenants.
  • Stacking too many rules. "Late fee for 5+ days, escalation for 30+ days, second escalation for 60+ days, third for 90+ days" becomes unmanageable. Two rules max in most cases.
  • Not exempting tenants on payment plans. If you've explicitly agreed to a payment schedule with a struggling tenant, the system shouldn't override that agreement with automated fees.
  • Forgetting that fees show up on customer invoices. The customer's first hint that they're late is typically the invoice with the fee on it. That's usually fine, but ensure your email process delivers it reliably or you'll get "I never knew" complaints.

Related articles