Customer statements

What this does

A statement is the period's activity for one customer: opening balance, invoices, payments, credits, closing balance. Money In → Statements runs them for every customer with statements enabled on their record, holds each in a queue for you to look at, and sends the ones you approve. Nothing goes to a customer without a person approving it.

Before you start

Statements are per customer: enable them and pick a cadence on the customer record (Billing settings). An email address on the customer for sending.

Steps

Run. Statement Runs → Generate run for a Period start and Period end. One statement per eligible customer lands in the queue. The same run happens automatically on the customers' cadence; a manual run is for catch-up or a special period.

Review. Open the queue. Each row previews the statement. Approve it, Skip it (this customer, this period), or leave it. Reopen pulls an approved row back if you change your mind before it's sent.

Send. Send approved emails every approved row with the branded statement and a share link. Rows that fail to send report individually; the rest go. Sent rows are marked Sent.

Ad hoc. Generate Statement for one customer and any Date Range or As of Date, then share or email it directly. Use it for a customer who calls asking what they owe.

Share links open without a login and show the statement as of the moment it was generated.

Common problems

A customer isn't in the run. Statements are off on their record, or their cadence doesn't match the run.

The statement shows a payment as "credit_card payment". Older statements used the raw method name; current ones humanise it. Regenerate.

Sent but the customer says nothing arrived. Check the email on their record and their spam folder; resend from the queue or share the link by text.