Auto-Pay report (v1)
Deprecated: This report is based on Version 1 (V1) reporting. Zenoti began phasing out V1 reports on July 31, 2025, and no longer accepts requests for enhancements or clarifications related to them.
Migrate to Version 2 (V2) as soon as possible. Contact your Customer Success Manager or Zenoti representative for the V2 equivalent.
Audience: Accountant, center manager
The Auto-Pay report shows every auto-pay transaction recorded at the selected center over a date range, with the authorization, capture, and refund status of each. Use it to confirm successful captures, work the queue of pending and failed transactions, and reconcile auto-pay activity against invoices.
This is a legacy report available under the classic reporting framework. The Auto-Pay report is enabled by setting Show Old Reports on the Reports configuration page.
Authorization vs. Auto-Debit: An authorization is the bank's confirmation that the guest's card has sufficient funds and the merchant may charge it later. Auto-Debit is the actual capture of those funds when the invoice closes. The report shows both halves so you can see where in the lifecycle each transaction sits.
Data refresh: Real-time on Refresh. Values reflect the latest transaction status returned by the credit-card processor at the moment of click.
On this page
- Before you begin
- Run the report
- Filter reference
- Column reference
- Authorization status values
- Auto-Debit status values
- Work the failed and pending queues
- Tips
- Troubleshooting
- Related articles
Before you begin
- Your organization must have a credit-card processor that supports auto-pay enabled. The report returns no rows for processors that do not support pre-authorization.
- The org-level setting
RestrictAutoPaycontrols whether auto-pay is restricted to members only. When enabled, the report excludes non-member transactions.
Permission: This classic report is controlled by View Admin Reports in the Administrator section of the security role (Configuration > Security > Security roles > the role > Permissions). Select the report-area action that applies to this report (for example Sales, Collections, Revenue, or Accounting). Classic report permissions are independent of the Reports(V2) permissions. See Report permissions and customization.
Run the report
- Select the center for which you want to run the report.
- Navigate to Reports > Admin.
- Open the Auto-Pay report (display order 136 in the Admin category).
- Set the date range and any additional filters from the Filter reference.
- Click Refresh.
To export the report, click the Excel or CSV icon.
Note on date range: The date filter anchors on the Authorization Date (the date the bank returned an authorization response), not the appointment date or the invoice close date. A guest whose appointment is on Jan 10 but whose card was pre-authorized on Jan 9 appears in the Jan 9 row.
Filter reference
| Filter | Values | Description |
|---|---|---|
| Date range | From / To dates | Filters by Authorization Date (the date the bank returned an authorization response). |
| Report Status | Authorized / Capture pending / Captured / Released / Voided / Failed / All | Each option maps to a bitmask value that the report passes to the underlying query; choose one or All to widen the result set. See Authorization status values for the meaning of each. |
| Invoice Status | Open / Closed / All / Open and no partial payment | Limits to invoices in the chosen state at report run time. |
| Processor | Configured credit-card processors | Limits to transactions captured through a specific processor. The dropdown lists only processors with SupportAutoPay = 1. |
Column reference
| Column | Type | Description |
|---|---|---|
| Invoice Number | Identifier | The invoice on which the auto-pay transaction was raised. |
| Invoice Status | Enum | Open, Closed, or No partial payment at the moment of report run. |
| Guest Code | Identifier | The unique guest code that identifies the cardholder. |
| Guest Name | Text | First name + last name of the guest. |
| Sale Date | Date | The date the invoice was created. |
| Card Info | Text | The last four digits of the card used for the transaction (from LastFour). Full PAN is never stored or displayed. |
| Base Amount for Authorization | Currency | Pre-authorization amount excluding tip and additional charges (TransactionAmount β TipAmount β AdditionalAmount). |
| Default Tip Amount for Authorization | Currency | The tip portion of the pre-authorization. |
| Additional Amount for Authorization | Currency | The buffer amount pre-authorized for additional product or service purchases. The unused portion is released once the invoice closes. |
| Total Authorization Amount | Currency | Base Amount + Default Tip + Additional Amount. The full amount the bank reserved against the card. |
| Authorization Date and Time | DateTime | Timestamp when the authorization response was received from the bank. |
| Authorization Status | Enum | Outcome of the pre-authorization call. See Authorization status values. |
| Actions | Button | Retry is offered for rows in Capture pending status; otherwise the column is blank. |
| Auto-Debit Status | Enum | Outcome of the capture call (the actual charge). See Auto-Debit status values. |
| Base Amount for Auto-Debit | Currency | Captured base amount (excludes tip; TransactionAmount β TipAmount on the capture record). |
| Tip Amount for Auto-Debit | Currency | Captured tip amount. |
| Total Auto-Debit Amount | Currency | Base Amount + Tip Amount. The actual amount charged to the guest. |
| Comments | Text | Processor message returned with the most recent transaction attempt. Useful for diagnosing declined or failed captures. |
Authorization status values
The Authorization Status column is derived from the credit-card-processor transaction status code.
| Status | Underlying code(s) | Meaning |
|---|---|---|
| Success | 1, 2, 4, 32 | The bank approved the pre-authorization. The amount is reserved against the card; capture follows when the invoice closes. |
| Released | 8 | The pre-authorization was released (the reserved amount is no longer held). Typical when an invoice is voided before capture. |
| Voided | 16 | The pre-authorization was voided by the processor. |
| Failed | -1 or null | The pre-authorization was declined by the bank or no response was received. |
Auto-Debit status values
The Auto-Debit Status column is derived from the same transaction status code as Authorization Status, but with a different mapping that focuses on capture state.
| Status | Underlying code(s) | Meaning |
|---|---|---|
| Pending | 1 | The authorization succeeded; capture has not yet been attempted. Common for open invoices. |
| Success | 2, 32 | The capture call succeeded; funds have moved from the guest's card to the merchant account. |
| Released | 8 | The authorization was released before capture (matches Authorization Status = Released). |
| Failed | 4 | The capture call failed (typical causes: bank declined at capture time, insufficient funds at capture, processor timeout). |
| NA | 16, -1, null | Not applicable (Voided, never-authorized, or no transaction record). |
Work the failed and pending queues
The Auto-Pay report is primarily a working queue, not a passive report. Most users open it to act on specific transactions.
For each Failed capture (Auto-Debit Status = Failed):
- Open the invoice referenced in the row.
- Review the Comments column for the processor's reason (insufficient funds, card declined, expired card, etc.).
- Contact the guest to update their card on file, or process a manual payment.
- The row stays in
Faileduntil the invoice is re-attempted or closed by another payment method.
For each Capture pending row (Auto-Debit Status = Pending) that you expected to capture:
- Confirm the invoice is
Closed(capture only fires on invoice close). - If the invoice is closed but the row is still
Pending, click the Retry button in the Actions column. - Refresh the report. If the retry fails, follow the
Failedworkflow above.
Tips
- Export weekly for reconciliation. Set the date range to the previous calendar week and export to Excel. Match Total Auto-Debit Amount against the bank deposit for the same period.
- Use the Released status to catch over-authorization. Released rows with non-zero Authorization amounts but no capture indicate authorizations that didn't convert. Recurring patterns may point to invoice-close delays or guests cancelling after the authorization runs.
- Look at the Comments column first when triaging. The processor's verbatim message is usually more diagnostic than the status code.
Troubleshooting
| Issue | Cause | Resolution |
|---|---|---|
| Report shows no rows | The selected processor does not support auto-pay, or no transactions exist in the date range. | Confirm the Auto-Pay setup is complete for the chosen processor (see Auto-Pay configuration β if available β otherwise contact your processor administrator). |
RestrictAutoPay is set; member transactions appear but non-member rows are missing |
The org-level setting RestrictAutoPay excludes non-member transactions from the Auto-Pay flow. |
This is expected. To include non-member transactions, the org admin must disable RestrictAutoPay (see Organization settings). |
| Authorization Status = Success but Auto-Debit Status = Pending after the invoice closed | Capture did not fire automatically. Possible causes: processor timeout, network blip during invoice close, or a manual hold placed by an admin. | Click Retry in the Actions column. If retry fails, capture manually from the invoice and add a Comment for audit purposes. |
| The report is not listed on the Reports Dashboard | The role lacks the classic report permission (View Admin Reports in the Administrator section of the security role). | Grant the report-area action in the security role. See Report permissions and customization. |