Customer statements

A statement of what they owe, sent for you

Customers with several open invoices receive one clear statement listing each invoice, its age, anything overdue and the total owed. WhizInvoice sends it automatically every month.

Why regular customers need a statement

A one off customer gets one invoice and pays it. Your best customers are different. A property manager might book six end of lease cleans in a month, a strata committee might have you back every quarter, and a builder might send you to three sites in a week. Each job gets its own invoice, and somewhere in their accounts team one of them goes missing.

A statement puts every open invoice for that customer on a single page. Their accounts team can match it against their records, pay everything in one go and spot the invoice they never received. For you, it turns a scattered set of small debts into one number you can follow up.

Example statement for one customer

Customer
Example Property Management
INV-0518, issued 6 days ago
NZ$345.00
INV-0533, issued 2 days ago
NZ$690.00
INV-0471, issued 38 days ago, overdue
NZ$1,150.00
Total owed
NZ$2,185.00

Example only, for a fictional customer. Amounts include New Zealand GST at 15%, the rate published by Inland Revenue on ird.govt.nz, checked October 2026.

How automatic statements work

  1. Invoice as normal

    Keep sending invoices for each job. Nothing about your everyday invoicing changes.

  2. Unpaid invoices are gathered

    WhizInvoice lists each customer’s open invoices with the age of each one in days, and flags anything past its due date as overdue.

  3. The statement goes out

    Statements are emailed automatically on a regular day, such as the 1st of each month, under your business name.

  4. Payments clear the list

    As invoices are paid and marked paid, they drop off, so the next statement shows only what is still owed.

Customers who will thank you for it

  • Property managers and agents

    Agencies booking cleans, pest treatments or repairs across many rentals pay from one accounts team. A monthly statement fits the way they already work.

  • Owners corporations and strata

    Committees often meet and approve payments in batches. A statement gives them one document to approve instead of a pile of invoices.

  • Commercial contracts

    Offices, shops and restaurants on regular service often have an accounts payable cycle. A statement lands where they reconcile.

  • Builders and head contractors

    If you work as a subcontractor across several sites, a statement shows every job you are owed for in one view.

Statements and reminders do different jobs

Payment reminders follow up one invoice at a time, around its own due date. A statement steps back and shows the whole account. Used together, a customer gets a timely nudge on each invoice and a monthly summary that makes the full picture hard to ignore.

Customer statements come with Solo, Business and Multi brand. You can compare plans in the pricing section, and see how reminders work on the payment reminders page.

Questions

Good to know

What is a customer statement?

A summary of every invoice a customer has not yet paid, with the age of each one and the total owed. It helps both of you agree on the balance.

Is a statement the same as an invoice?

No, a statement lists invoices you have already sent and does not create a new charge. Each invoice on it remains the document for that job.

Do I have to remember to send statements?

No, statements are sent automatically on a regular day each month, such as the 1st.

Which plans include customer statements?

Solo, Business and Multi brand include statements sent automatically. Solo starts at US$4.99 a month or US$49 a year.

Does the statement show overdue invoices clearly?

Yes, each invoice shows how many days old it is, and anything past its due date is marked overdue.

Send statements without lifting a finger

Upgrade to Solo or above and your regular customers get a clear monthly statement, backed by a 30 day money back guarantee.

Free plan forever. No card needed to start.