Scheduled financial reports: automate the numbers your team needs

Scheduled financial reports are reports you set up once and have delivered automatically, usually by email, on a fixed schedule such as every Monday morning or the first working day of the month. They replace the routine of logging in, filtering, exporting and emailing the same numbers every week, and they make sure the right people see the figures even when the person who normally prepares them is on leave.

This guide covers which reports are worth scheduling, how often, who should receive them, and the controls that keep financial data safe once it's leaving your system by email.

Why schedule reports instead of running them by hand?

• Consistency. The same filters, columns and date ranges every time, so trends are comparable.
• Timeliness. A collections report that lands at 7am on Monday is acted on that morning; one someone remembers to run on Wednesday is less useful.
• Less key-person risk. The report still arrives when the bookkeeper is on leave.
• Fewer ad hoc requests. Managers stop asking "can you send me the numbers?" when the numbers already come to them.

The trade-off is that a scheduled report can be ignored in an inbox. Keep each one short and relevant to the person receiving it.

Which reports to schedule

Start with reports that someone needs regularly and acts on. A typical set for a small or mid-sized business:

For what each revenue report should contain, see revenue reports for small businesses. For the measures worth tracking over time, see payment KPIs for finance teams.

Setting up a scheduled report: a checklist

1. Build and save the report first. Get the filters, columns and sort order right, and check the numbers against your books once.
2. Use relative date ranges. "Last 7 days" or "previous month", not fixed dates, so the report stays current.
3. Choose the schedule. Pick a time when the data is complete. A monthly report sent at 00:05 on the 1st may miss late postings; mid-morning on the first working day is often safer.
4. Choose the format. CSV for importing into other tools; XLSX for people who'll open it in Excel. Keep formats consistent so recipients' own spreadsheets don't break.
5. Pick recipients deliberately. Only people who need the data and are allowed to see it.
6. Add context in the email. A one-line description of what the report is and what to do with it helps new recipients.
7. Review quarterly. Remove reports nobody opens and recipients who've changed roles.

Timing and South African calendars

A few local details affect scheduling:

• Public holidays. A "first working day" report is more useful than "the 1st" when the 1st falls on a public holiday or a weekend.
• Debit order runs. If you collect by debit order, schedule the unpaids report for after your provider has returned unpaid results for the run, not the morning of the collection.
• Month-end timing. Bank statements and gateway settlements for the last days of the month may only arrive after the 1st. Consider a "flash" report on the 1st and a final version after reconciliation.

Security and POPIA considerations

Scheduled reports send data out of your system, often to inboxes you don't control. Treat them with the same care as the system itself:

• Minimise personal information. A collections summary rarely needs customer ID numbers or bank account details. Leave out what isn't needed.
• Restrict who can create schedules. Use roles so only authorised staff can set up reports that email customer data.
• Send to work addresses only, not personal email accounts.
• Keep an audit trail of who created or changed a scheduled report.
• Remove leavers promptly from recipient lists.

If a report containing personal information goes to the wrong person, that may be a security compromise under POPIA. Section 22 requires notifying the Information Regulator and affected people as soon as reasonably possible, and since 1 April 2025 reports to the Regulator go through its eServices portal. Designing reports to carry the minimum data needed reduces that risk.

Common pitfalls

• Too many reports. Five focused reports beat twenty that nobody reads.
• Fixed dates in filters, so the report keeps showing last quarter.
• No owner. Every scheduled report should have someone responsible for keeping it accurate.
• Silent changes. If you change a report's definition, tell recipients, or the trend line will suddenly jump without explanation.

How CentraPoint helps

CentraPoint includes standard reports and a report builder. You can save a report with its filters and columns, schedule it for email delivery, and choose CSV or XLSX export. Roles and permissions (admin, staff, viewer and custom roles) control what each team member can access, and audit logs keep a record of account activity. Because invoices, payments across your enabled gateways, debit order batches and reconciliation all live in one system, a scheduled report reflects the same data your team sees on screen. See features for more.

Frequently asked questions

What are scheduled financial reports?

They're saved reports that run automatically on a set schedule and are delivered, usually by email, to chosen recipients, so nobody has to run and send them manually.

Which format is best for emailed reports: CSV or XLSX?

XLSX suits people who open reports in Excel; CSV is better for importing into other systems. Pick one per report and keep it consistent.

How often should financial reports be scheduled?

Weekly for operational reports such as collections and unpaid invoices, and monthly for management summaries like revenue and fees.

Is it safe to email financial reports?

It can be, if you include only the data recipients need, send to work addresses, restrict who can create schedules and review recipient lists regularly.