Statements
View, configure, and act on student billing statements for House Account charges. Statements are generated automatically based on the billing cycle configured for your organization. They aggregate all charges that members have deferred onto their House Account during the cycle.
Audience: Administrators, center managers, and front-desk staff who configure House Account billing or settle statements with members.
On this page
- Before you begin
- Statement anatomy
- View a student's statements
- Statement statuses
- Statement aging buckets
- Wallet in House Accounts
- Add wallet balance
- Statement notifications
- Statement macros reference
- Statement lifecycle
- Bulk-charge unpaid statements from the Statements Report
- Statements after a profile merge
- Related articles
Before you begin
- Your organization must have House Accounts enabled.
- Access to the student's profile is required to view their statements.
- To send statements by email or text and to customize the statement template, you must have the Configure Statement Templates permission and the Send Statements permission.
Statement anatomy
Every statement is composed of three sections in fixed order:
| Section | Content |
|---|---|
| Header | Member name, member address, member number, statement date, billing period (start and end dates), due date, and high-level indicators (status, currency, organization name). |
| Transaction Details | One row per invoice posted during the billing period, with columns for transaction date, description, associated member name (relevant for shared accounts), and charge amount. |
| Footer (Balance Summary) | Previous balance, new charges during the cycle, payments received, wallet credits applied (shown as "Payment on Account"), late fees, Net Due, and the four-bucket aging breakdown (0 / 1 / 2 / 3+ cycles due). |
The Footer aggregates all rows from Transaction Details to produce the Net Due that the member owes for the statement period.
View a student's statements
- Open the student's profile.
- Select the Statements tab.
- Review the summary information at the top of the tab:
- House Account limit β The maximum balance allowed for the student.
- Gross Due β Total amount due before adjustments.
- Net Due β Amount due after payments and credits.
- Preferred payment type β The student's default payment method.
- Scroll down to access the statements section, which shows the Current Statement and Past Statements.
- Click View to open a statement and see the full breakdown of charges.
- Click Email to send the statement to the student by email.
Statement statuses
Zenoti uses the following statuses to reflect the payment state of each statement:
| Status | Description |
|---|---|
| Not Paid | The current open statement has no payment applied. |
| Partially Paid | A partial payment has been applied to the statement. |
| Paid | The statement is fully settled. |
| Moved | The full unpaid balance has been rolled forward to the next billing cycle. |
| Partially Moved | The remaining unpaid balance after a partial payment has been moved to the next billing cycle. |
| Processing | Payment has been initiated but not yet confirmed (for example, a pending card-on-file collection that the payment processor is still verifying). The statement remains in this state until the payment processor confirms or rejects the transaction. |
Label difference by audience for "Not Paid": Per PM verbatim β Not Paid is the status the FDO (Front Desk Staff) sees on the web version (admin portal + Roster). Guests see the same payment state as Due, and only on the Webstore. Both labels point to the same underlying status enum β the label differs by surface and audience. Use this distinction explicitly when explaining a statement status to a guest over the phone (the guest sees only "Due" on the Webstore, never "Not Paid", so referring to "Due" matches what they see).
Statement aging buckets
The Footer Balance Summary aggregates the outstanding balance into four aging buckets so staff can see how long each portion has been unpaid:
| Bucket | Meaning |
|---|---|
| 0 Cycle Due (Current) | Charges from the current billing cycle that are not yet past due. |
| 1 Cycle Due | Charges that rolled forward from the immediately prior cycle without being settled. |
| 2 Cycles Due | Charges that rolled forward two cycles without being settled. |
| 3+ Cycles Due | Charges that have rolled forward three or more cycles. Often paired with collection escalation. |
The bucket boundaries follow the configured billing cycle (typically 30/60/90 days, but the organization can configure any cadence). When a statement carries forward into the next cycle, applied late fees move from the current cycle into the corresponding aging bucket along with the unpaid principal.
Wallet in House Accounts
The House Account wallet is a prepaid balance that members can deposit into ahead of time. The wallet automatically offsets charges when a statement is generated or closed; this offset appears on the statement footer as a Payment on Account line item.
Wallet rules:
- The wallet balance cannot go negative. Once exhausted, additional charges remain on the open statement until the member pays through another method or tops up the wallet.
- Auto-apply is not optional. The wallet is applied automatically at statement generation and statement closure; there is no manual override that prevents it from being consumed.
- Wallet offsets are visible. Each deduction appears in the statement as a Payment on Account line, with the amount and date.
- Full coverage produces a zero or credit statement. If the wallet balance is greater than or equal to the Net Due, the statement reflects zero outstanding (or a small credit, if the wallet exceeds the Net Due).
- Excess payments credit back to wallet. When a member pays more than the Net Due, the excess is credited to the wallet and applied to future statements.
- Pre-generation advance payments go to wallet. An advance payment made before the statement is generated is held in the wallet. During the next statement generation, the wallet offsets the statement charges.
Add wallet balance
- Open the student's profile.
- Go to the Statements tab.
- Select Add wallet balance.
- The Point of Sale (POS) opens with the wallet top-up amount pre-populated.
- Complete the payment using the member's preferred payment method.
- Close the invoice.
The wallet balance increases by the amount paid. The new balance appears in the student's House Account summary and is applied to the next statement generation.
Statement notifications
Four notification templates fire on the statement billing cycle, in the following order within a cycle:
- Generated Statement Reminder β Sent when a new statement is generated, reminding the member that a balance is due.
- Statement Success Collection Reminder β Sent after a successful auto-collection on the statement.
- Statement Failure Collection Reminder β Sent after a failed auto-collection attempt, with guidance to update payment information.
- Statement Movement Reminder β Sent when an unpaid balance is rolled forward (moved) into the next billing cycle.
Templates are configured under Configuration > Notifications > Templates for email and text, in the House Accounts section. Channels (email, text) per template are listed in the templates configuration.
Statement macros reference
Important β Statement macros are not the same as notification macros. House Account statements use a dedicated set of macros that resolve only on statement-template rendering. Notification macros (used in Reminders, Confirmations, etc.) and form macros (used in custom forms) use different naming and resolve in different contexts. Macros from the notification or form sets do NOT render in a statement template, and vice versa. When customizing a statement template, use only macros from the table below.
| Macro | Resolves to |
|---|---|
[GuestCode] |
The member's guest code (unique identifier). |
[GuestName] |
The member's full name as on file. |
[MemberNumber] |
The member's House Account member number. |
[GuestAddress] |
The member's primary address (line 1). |
[GuestAddressLine2] |
The member's address line 2, if configured. |
[GuestCity] |
The member's city. |
[GuestState] |
The member's state or province. |
[GuestZipcode] |
The member's postal code. |
[GuestPhone] |
The member's primary phone number. |
[StatementDate] |
The date the statement was generated. |
[StatementStartDate] |
The start date of the billing period covered by the statement. |
[StatementEndDate] |
The end date of the billing period covered by the statement. |
[DueDate] |
The date the statement must be settled by. |
[StatementAmount] |
The full statement amount (new charges plus rolled-forward balance). |
[StatementAmountPaid] |
Amount already paid against the statement. |
[BalanceDue] |
Remaining unsettled balance on the statement. |
[BalanceForwarded] |
Unpaid balance from the prior cycle carried forward to this cycle. |
[GrossDue] |
Total charges before any adjustments. |
[NetDue] |
Total owed after wallet credits, refunds, and payments are applied. |
[WalletBalance] |
Current wallet balance available to offset future statements. |
[PaymentOnAccount] |
Wallet credits applied to this statement. |
[LateFee] |
Late fee charged on the statement, if any. |
[LateFeeApplied] |
Indicator (Yes/No) of whether a late fee was applied. |
[0_cycle_due] |
Amount in the current (0-cycle) aging bucket. |
[1_cycle_due] |
Amount in the 1-cycle-due aging bucket. |
[2_cycles_due] |
Amount in the 2-cycles-due aging bucket. |
[3+_cycles_due] |
Amount in the 3-or-more-cycles-due aging bucket. |
[CarriedOverCharges] |
Sum of all charges rolled forward from prior cycles. |
[Carriedover_0_cycle_due] |
Carried-over portion of the current (0-cycle) aging bucket. |
[Carriedover_1_cycle_due] |
Carried-over portion of the 1-cycle-due aging bucket. |
[Carriedover_2_cycles_due] |
Carried-over portion of the 2-cycles-due aging bucket. |
[Carriedover_3+_cycles_due] |
Carried-over portion of the 3-or-more-cycles-due aging bucket. |
[Current_Late_fees] |
Late fees applied in the current billing cycle. |
[Total_Late_fees] |
Sum of all late fees across all cycles. |
[GrossPreviousBalance] |
Gross balance from the previous statement before any current-period activity. |
[CurrentRedemptions] |
Total credits and gift cards redeemed in the current statement period. |
[PendingTransactions] |
Transactions in pending or processing state that have not yet posted. |
[PaymentsMade] |
Sum of payments received during the statement period. |
[GuestCountry] |
The member's country (resolves from the address on the guest profile). |
[CenterName] |
The center primarily associated with the member's House Account. |
[OrgName] |
The organization name. |
[OrgAddress] |
The organization address used on statement headers. |
[OrgPhone] |
The organization phone number on the statement footer. |
[CurrencySymbol] |
The currency symbol for the member's center. |
Statement labels and macro mapping
Beyond the macro list above, statements use a small set of labeled fields whose default label can be customized at the organization level. The most-edited labels:
- Maximum Allowed Balance β Alternate label for the House Account limit shown at the top of every statement.
- Last day to pay β Label for the statement's due date.
Label Customization and Macro Mapping
Custom statement labels are defined in Configuration > Notifications > Templates for email and text under the House Accounts section. Each label change resolves at statement-render time and applies to all subsequent statements without regenerating prior ones.
Statement lifecycle
Statements follow a defined lifecycle when House Accounts are enabled:
- Billing cycle β Zenoti tracks charges within the configured billing cycle. At the end of the cycle, the system prepares the statement for generation.
- Statement generation β On the configured generation date after the billing cycle ends, Zenoti generates the statement reflecting the total amount due. The wallet balance is automatically applied at this point.
- Payment β After generation, the student can pay the statement using the allowed payment methods. Zenoti updates the statement status based on the payment amount applied.
- Sweep and carry-forward β When a scheduled sweep detects a pending payment, Zenoti treats it as failed for that sweep cycle:
- The outstanding balance carries forward to the next statement.
- A late fee is applied based on configured statement rules.
- If the pending payment later succeeds, Zenoti refunds the collected amount to the student's wallet.
- Any applied late fee is also credited back to the wallet.
Bulk-charge unpaid statements from the Statements Report
Centers that want to settle multiple unpaid statements in one operation can do so through the Statements Report.
- Open the Statements Report from the Reports module.
- Filter to Unpaid or Partially Paid statements within the desired date range.
- Select the statements to charge in bulk.
- Trigger the bulk charge action β Zenoti attempts to collect each selected statement against the member's preferred payment method.
- Review the run summary for successes, failures, and statements that require follow-up.
Failed collections remain on the report for the next action; successful collections update the statement status to Paid or Partially Paid as appropriate.
Statements after a profile merge
When you merge two student profiles that have statements, Zenoti handles them as follows:
- Paid statements β Previously paid statements from both profiles are displayed together for reference.
- Unpaid statements β Unpaid statements remain separate after the merge. You can pay each one independently.
- Post-merge view β Zenoti generates a consolidated statement view for the merged profile, reflecting remaining balances from any unpaid statements.