A statement of what each customer owes

The customer asks: A statement of what each customer owes, printed and sent on a schedule

• Verdict: Ready, with limits (3)
• Door: Configure · area: Reports and data › Reports and BI
• Recipe: 4. Configure first
• Sample: none yet
• Checked: run on a sandbox 2026-10-16 · POS 2.0.0.647 · a statement for one customer with two sales rendered as a one-page PDF; with ageing on it failed; a schedule saved with no sender; not run: any send, ageing on another site

What you build

The standard Process Statement Of Accounts: pick the customers, the layout, the dates, the frequency and the sender; the site makes the PDF and can e-mail it.

Limits

• The plain statement rendered (opening, each sale, closing). With ageing switched on, the same statement stopped with a server error on this sandbox, though the receivables report ran: run it on the customer's site before you promise the ageing.
• The schedule sends through the site's e-mail queue, from the sender account chosen on the statement or else the user, so the site needs an outgoing e-mail account that is switched on (read from the code, not run: both sandbox accounts are off and no mail was tried).
• A customer with no e-mail address is skipped by the send (read from the code).

Tell the customer

Each customer's statement is a PDF made on demand, and can be e-mailed on a schedule once the shop's outgoing e-mail is set up; we have not run a send.

What next

1. Tell the customer the 3 limits above, and write them into the proposal.
2. Read the chapter: 4. Configure first.
3. Build and test it on your sandbox (request one if you have none; what is on it).
4. Check it on your sandbox as the people who will use it; where it touches a price or a total, the money kit's release gate proves it (testing and release).
5. Make the same settings on the customer's site, from the list you wrote down, through the customer's own change process.

Nothing to code: write down each setting you make on your sandbox, so it is made the same way on the customer's site.

Related needs

• A column the retailer wants on a record's list — Ready, with limits (2)
• A notification a number of days before a date on a shop's own record, such as a batch's expiry — Ready, with limits (2)
• Head-office reports and our BI tool fed with sales and stock — Ready, with limits (3)

Start a project shortlist with this need · Put it in your blueprint · Every need

This card in the kit