From CRM or Accounting Export to Individual Client Emails

From CRM or Accounting Export to Individual Client Emails

Your data already exists. Your emails just don't use it.

Your accounting software knows exactly how much VAT each client owes this month. Your school management system knows every student's attendance. Your property software knows each tenant's rent and service charge. And yet, on the 20th of the month, someone in the office opens a spreadsheet and types those numbers into forty emails by hand.

That gap between the system that holds the data and the email that should carry it is where the mistakes happen: a figure copied into the wrong row, last month's amount sent again, a client who never got their email because they were skipped. This guide shows how to close the gap with the tool you already have: a CSV export.

The core idea: every value your client needs to see (amount, due date, reference, account number, document) already sits in one of your systems. Export it once a month, import it into your contact list, and let one template turn it into individual emails.

Step 1: decide what each email needs

Before you export anything, write down which values the email will show. Group them like this:

  • Identity: name, email address, client or student number.
  • Amounts: amount due, VAT, income tax advance, balance, rent.
  • Dates: due date, billing period, date of the next lesson or meeting.
  • References: invoice number, bank account, transfer title.
  • Documents: the invoice or statement PDF for that client.

Export only what the email needs. A notice about a tax payment needs the amount, the deadline and the tax account; it doesn't need the client's full financial history. Less data means fewer mistakes and less exposure under GDPR.

Choose the right field type

Each value becomes a field on your contact list. MailerBit has five field types: text, whole number, decimal, date and file. A few practical rules:

  • Bank account numbers, IBANs and client numbers are text, not numbers. Otherwise leading zeros and spaces get lost.
  • Amounts you want to calculate with are decimals. The template adds the currency, for example {{vat_due}} PLN.
  • Amounts that must look exactly like on the invoice, with a thousands separator such as 1 234,50 zł, are best exported as text, already formatted.
  • Dates are dates, which keeps them valid and consistent.
  • Per-client documents go in a file field and are sent as that client's attachment.

Step 2: export a clean CSV

Most accounting, CRM and school management systems can export a client list to CSV or Excel. Whatever your system, aim for this shape:

  • One row per client and one header row.
  • Two required columns: email and name.
  • Other column names match your field identifiers, for example vat_due or due_date. Upper or lower case doesn't matter.
  • Comma, semicolon or tab as the separator. MailerBit detects it automatically, so a semicolon-separated export from a European Excel works as it is.
  • UTF-8 encoding, so names with accents and diacritics survive the trip.
  • Decimals with a dot (1234.50) in decimal fields, and dates as YYYY-MM-DD.

A monthly tax notice export might look like this:

email;name;client_no;pit_due;pit_due_date;vat_due;vat_due_date;tax_account

anna@example.com;Anna Nowak;K-0142;620.00;2026-11-20;1840.00;2026-11-25;PL61 1090 1014 0000 0712 1981 2874

Not sure what the headers should be? Download the sample CSV from your contact list: it already contains the right column names.

Step 3: import, then refresh every month

The first import creates your contacts. Rows with an invalid email address, a missing name or a value of the wrong type (text in a number field, an invalid date) are reported with their row number, so you can fix them in the source and import again.

From then on, refresh the data before each run. Import the new export with the option to update existing contacts switched on: contacts are matched by email address, and their values are replaced with the new ones. Two things to remember:

  • Export all columns every time. An updated row replaces the contact's field values with the ones in the file, so a refresh with only one column would leave the others empty.
  • Remove clients who have left. A refresh adds and updates; it doesn't delete. Former clients should come off the list, both for accuracy and for GDPR.

Step 4: handle exceptions without touching the source

Sometimes one client needs a different value for this month only: a corrected amount, an extended deadline. You don't need to change your accounting data for that. In the campaign wizard, the Variables step lets you override a value for a single recipient for this send. For many changes at once, download the variables as CSV, edit them and import the file back; only values that differ from the originals become overrides. In the Recipients step you can exclude individual clients, and the Preview step shows the finished email for each of them.

Step 5: put the fields into a template

Every field becomes a merge tag. A tax notice template might read:

Hi {{name}}, your taxes for this month: income tax advance {{pit_due}} PLN, due by {{pit_due_date}}, and VAT {{vat_due}} PLN, due by {{vat_due_date}}. Please pay to your tax account {{tax_account}}.

Tags can also do one simple calculation: {{vat_due + pit_due}} shows the total, and {{net_amount * 1.23 | round(2)}} adds 23% VAT to a net amount. Each tag supports one operation, so for anything more complex, calculate the value in your source system and export it as its own column. The guide to custom fields and merge tags covers the details.

Organise by client situation, not by system

A CRM tracks where each client stands. Use that to decide which email they get, with one list and one template per situation:

  • All active clients: monthly statements or tax notices.
  • Invoices issued, not yet due: a friendly heads-up before the deadline.
  • Overdue: a reminder with the exact amount and how to pay. The payment reminder guide has a full cadence.
  • New clients: account details, contact person and what to expect each month.
  • Clients who are leaving: the final statement and what happens next.

Common pitfalls

  • Stale data. A scheduled send uses whatever is on the list at that moment. Import the fresh export before the send date, not after.
  • Decimal commas. 1234,50 is rejected in a decimal field. Switch the export to a dot or use a text field.
  • One email address, two clients. Each address appears once per list, so a parent with two children at your school needs both children in one row (for example child_1 and child_2 fields) or two separate lists.
  • Column names that don't match. A column whose header doesn't match a field identifier is ignored. Check the headers against the sample CSV.

How MailerBit fits in

MailerBit doesn't have built-in connectors to specific CRMs or accounting programs. CSV is the bridge, which means it works with any system that can export a spreadsheet. On the MailerBit side you get unlimited custom fields per contact list, CSV import with updates by email address, per-send overrides, and recurring sends on the day your process needs. The accounting offices page shows a complete example, from the export to a scheduled send on the 20th.

Your systems already know what each client needs to hear. Start your 7-day free trial, import your first export and send each client their own figures without typing a single number.

Related articles

How to Choose a Tool for Per-Recipient Client Emails

How to Choose a Tool for Per-Recipient Client Emails

Reminders, statements and fee notices need a tool built around per-recipient data, not one message for everyone. A practical checklist of what to look for before you choose.

Why Per-Recipient Reminders and Statements Get Acted On

Why Per-Recipient Reminders and Statements Get Acted On

A reminder that shows the client's own amount, due date and account number gets paid; a generic one gets postponed. Why individual emails work, and how to send them without extra work.

The Complete Guide to Data-Driven Client Emails

The Complete Guide to Data-Driven Client Emails

How to use per-recipient fields, merge tags and recurring schedules to send statements, reminders and fee notices that are individually correct for every client, every month.

All articles →