Statements

A statement is a summary of everything one restaurant still owes one supplier: each unpaid invoice, how much is left on it, how late it is, and the total. The supplier picks customers, checks the statement, and sends it by email, text or both. The restaurant opens a link, sees the current balance, and pays the invoices one at a time by bank transfer (ACH) or card.

A statement never changes what anyone owes. It reads the invoices; it doesn't touch them. Paying from a statement is an ordinary invoice payment.

Who uses it

• Supplier staff send statements to one customer or up to 1,000 at once, from Customers or Invoices, and look back at what was sent from a customer's page.
• Restaurants get the email or text, open the statement page, download the PDF, and pay.

A statement's life at a glance

1. Pick. The supplier clicks Create Statement on Invoices, or on Customers (the button without "(Legacy)"). Both open the same dialog, which lists every active customer with an unpaid invoice on an order that is Ready for Delivery or Delivered, and their balance. The supplier ticks customers (and, if they want, single invoices) and checks the email and phone. Creating & sending
2. Freeze. On Create & Send, each customer gets a statement with the next statement number. Its invoices, amounts, Open/Overdue labels and aging are frozen as of the Statement Date. What's on a statement
3. Deliver. A PDF is made and saved, and the email and text go out with a link to the statement page. PDF, email & text
4. Pay. The restaurant opens the link. The page shows live balances, so anything paid since is already taken off. They pay an invoice by ACH or card and come back to the page. Statement page & paying
5. Look back. The supplier sees every statement sent to a customer, with its PDF, under View Statements. Statement history

In this section

Page	Answers
Creating & sending	Every control in the Create Statement dialog, what sending does, and what to do when it fails
What's on a statement	Which invoices are included, how the amounts, Open/Overdue and aging buckets are worked out
PDF, email & text	Exactly what the restaurant receives, and when
Statement page & paying	What the restaurant sees on the link, how paying works, and what a payment changes
Statement history	The supplier's View Statements list: filters, search, sort and the saved PDF

Where it shows up

• Supplier app: Create Statement button on Customers and on Invoices; View Statements in the ⋮ menu on a customer's page.
• Restaurant: the statement email, the statement text message, the statement PDF, and the statement page at /statement/<link> on the restaurant site.
• Each invoice's own pay page (/pay/<link> on the supplier app), linked from the PDF's View & Pay.
• The Last Sent column in the Create Statement dialog.

Permissions

Action	Who can do it
Create Statement on Invoices	Admin, or a role with Full Access to Invoices. The server checks it too.
Create Statement on Customers	Admin, or a role with Full Access to Customers. See the caution below.
View Statements on a customer page	Admin, or a role with Full Access to Customers (the ⋮ button that holds it needs it). Not available while the customer is Inactive.
Open a statement link and pay	Anyone who has the link. No login.

Without the access, the button doesn't show at all. The built-in roles are Admin, Clerk, Driver, Warehouse and Sales Person; what each one has depends on how the supplier set up Roles (verify the exact permission labels in the role editor).

caution

Create Statement on Customers opens the same dialog as on Invoices (shown with full invoice access). The Customers page also keeps Create Statement (Legacy), which opens an older version that lists only invoices from orders placed before the move to the current Orders pages, so it can miss a customer's newer invoices, and whose permission is checked only in the app (the server accepts any logged-in staff member of the supplier). Use the button without "(Legacy)". See Creating & sending → Known limitations.