Rent and Service Charge Notices by Email for Property Managers

Rent and Service Charge Notices by Email for Property Managers

The monthly notice nobody enjoys sending

If you manage a few buildings, you know the routine. At month end the numbers arrive from accounting: rents, service charges, utilities advances, arrears. Then someone spends a day or two turning a spreadsheet into hundreds of individual emails, copying names, flat numbers, amounts and account numbers, hoping nothing slipped by one row.

It isn't hard work. It's fragile work. One wrong paste and an owner gets their neighbour's balance, or the phone rings all morning with “why is my service charge different this month?”. Here's what a good notice contains, how to handle arrears and annual settlements, and how to send everyone exactly their own numbers.

What lands on your desk every month

Lettings, block management or an HOA, the monthly cycle has the same ingredients:

  • Rent: fixed per unit, sometimes indexed once a year.
  • Service or maintenance charges: often based on floor area or share, so every unit's figure differs.
  • Reserve fund contributions: set by the owners and charged per unit.
  • Utilities: monthly advances for water, heating or waste, reconciled later against actual use.
  • Meter readings: requests to submit them, or the readings used for the bill.
  • Arrears: outstanding balances carried over from previous months.

Multiply that by 40, 150 or 600 units and you get the real problem: the message is the same every month, but the numbers inside it differ for every recipient.

What every notice must contain

A notice gets paid on time when the recipient can act on it without calling you. Each email should answer:

  • Who and which unit: the recipient's name and the unit or flat number, plus the building if you manage more than one.
  • Which period: “November 2026”, never just “this month”.
  • The breakdown: each component on its own line (rent, service charge, reserve fund, utilities advance, arrears).
  • The total: one clear number to pay.
  • The due date: a specific date, not “as soon as possible”.
  • Where to pay: the bank account (an individual account per unit, if you use them) and the payment reference to quote.
  • Who to contact: a named person, an email address and office hours.

Skip the breakdown and you'll get replies asking why the total changed.

A sample notice with merge tags

Here is a monthly notice written once as a template. Everything in double curly braces is a merge tag, replaced with each recipient's own value at send time:

Subject: Charges for unit {{unit_number}}, {{period}}

Dear {{first_name}},

Here are the charges for unit {{unit_number}}, {{building}}, for {{period}}:

  • Rent: £{{rent}}
  • Service charge: £{{service_charge}}
  • Reserve fund: £{{reserve_fund}}
  • Utilities advance: £{{utilities_advance}}

Total due: £{{total_due}}
Due date: {{due_date}}

Please transfer the total to account {{account_number}}, quoting “Unit {{unit_number}}, {{period}}” as the reference.

Questions about your charges? Reply to this email or call Anna in our office (Mon to Fri, 9am to 5pm).

Kind regards,
Riverside Property Management

Your data file needs one row per unit and one column per tag (email, unit_number, rent, total_due and so on). Export the total from your accounting system with the rest; for a simple two-part bill the template can add it up itself, as in {{rent + service_charge}}. Note that the currency symbol sits in the template, next to the tag. The period and due_date columns simply get refreshed with each monthly import.

Arrears reminders: escalate the tone, not the volume

Most late payments are forgetfulness, not refusal. Assume good faith first and get firmer only when needed. Three steps work for most managers:

  1. Friendly reminder (around 5 days after the due date). “We haven't yet received your payment of {{arrears}} for unit {{unit_number}}. If you've already paid, please ignore this message.” Short, neutral, with the account number repeated.
  2. Firm reminder (around 14 days). The amount, the original due date and a new deadline. Mention that late payment interest or fees may apply under the lease or the association's rules, but only if they actually do.
  3. Final notice (around 30 days). Formal tone, the full outstanding balance, a final deadline and the next step (a letter of demand or debt collection). Offer a contact for agreeing a payment plan.

Two rules. First, send reminders only to units that actually owe money: keep a separate debtors list with the amount and days overdue, refreshed from your accounting data before each step. A final notice reaching someone who paid last week destroys trust. Second, stay factual: amounts, dates and next steps persuade; capital letters and threats don't. For more on timing and wording, read our guide to automated payment reminders that actually get paid.

Note: A formal demand often has to be sent by recorded or registered post to count in court. Use email for the early, friendly steps and check your lease, the association's rules and local law before relying on it for the last one.

Annual settlements without the annual headache

Once a year, utilities advances meet reality: actual consumption is compared with what was paid, and everyone gets either a refund or a balance to pay. This email triggers the most questions, so give it structure:

  • the settlement period and the meter readings used (opening and closing);
  • actual consumption and its cost;
  • advances paid during the year;
  • the difference, clearly labelled as a refund or an amount due;
  • what happens next: refund date or payment deadline, and whether next year's monthly advance changes.

The simplest approach is to split the two cases: import units with a refund into one list and units with a balance due into another, each with its own wording. Calculate the difference in the template, {{advances_paid - actual_cost}} for refunds and {{actual_cost - advances_paid}} for balances due, so the figure always matches the lines above it.

Announcements: works, outages and meetings

Lift maintenance, a water shut-off, facade works, the annual general meeting: these go to the whole building at once. Personalisation still helps. “The water meter in unit {{unit_number}} will be replaced on 14 November” gets read more carefully than “Dear Residents”.

Put the date and time in the subject line, say exactly what residents need to do (give access to the meter, move the car, attend or appoint a proxy) and keep a separate list per building. For meetings, formal notice rules often still apply, so check your governing documents for how and when notice must be given.

Privacy: one owner never sees another's data

Names, addresses, balances and debts are personal data, covered by GDPR and similar laws. The classic mistakes:

  • one email with every owner in the To or CC field;
  • a spreadsheet of the whole building's balances attached “so everyone can find their row”;
  • a list of debtors pinned to the noticeboard or posted in a residents' group chat.

The fix is structural, not extra care: every recipient gets their own email with only their own figures, generated from their own row of data. No shared spreadsheet to leak, no neighbour's balance to paste by mistake.

How MailerBit fits this workflow

MailerBit is built for exactly this: the same message every month, different numbers for every recipient.

  • Custom fields for every figure. Import a CSV from your property management or accounting software; each column becomes a custom field usable as a merge tag. Fields are typed (text, whole numbers, decimals, dates), so amounts stay numbers you can calculate with; add the currency symbol in the template.
  • Calculations in the template. A simple sum or difference such as {{rent + service_charge}}, or rounding with | round(2), is worked out at send time.
  • Recurring campaigns. Schedule the monthly notice once, on the 1st, the 20th or whatever your cycle is, and it runs automatically with fresh data from the list. Re-import the CSV to update amounts; new tenants are included in the next run.
  • One list per building. Buildings, associations and debtor lists stay apart, each with its own fields and campaigns.
  • Your own domain. Notices come from your company's address, and each send ends with a report of deliveries, opens and errors.

You'll find a full walkthrough with an example rent notice on the property managers page.

Write the notice once, refresh the numbers monthly

Take last month's spreadsheet, turn its columns into fields, write the notice once and schedule it. From then on, you just refresh the numbers. Start your free MailerBit trial and set up your first notice today.

Related articles

New in MailerBit: Clients and Payment Tracking

New in MailerBit: Clients and Payment Tracking

Sending the invoice is the easy part. Client cards with a full history, payments tied to the emails you send, a clear list of who owes what and optional automatic reminders that stop once a client pays.

Automated Payment Reminders That Actually Get Paid

Automated Payment Reminders That Actually Get Paid

Generic “please pay” emails get ignored. Here's what a payment reminder must contain, a sample with merge tags, a 5-step cadence, subject lines that work and the mistakes to avoid.

Transactional Emails That Get You Paid on Time

Transactional Emails That Get You Paid on Time

Invoices, payment reminders, statements and account notices are the emails clients actually expect. How to write and schedule them so they get read, understood and paid on time.

All articles →