Invoice Logs report (v1)
Deprecated: This report is part of the classic reporting framework. It remains available for organizations that have not yet migrated to the modern reporting platform.
Audience: Center manager, auditor
The Invoice Logs report is the audit trail of every action taken on an invoice in a date range β applies, updates, removes, closes, refunds. Use it to investigate disputes, audit front-desk corrections, or detect unusual edit patterns.
This is a legacy report available under the classic reporting framework.
Action coverage. Each invoice action falls into one of four categories: Add/Apply (memberships, discounts, packages, coupons, campaigns, commissions, comments, payments, gift cards), Update (item price/quantity/sold-by, sale date, payment type, commission, tips, SSG, etc.), Remove/Unapply (item, membership, package, coupon, payment, commission, gift card, undo benefit transfer), and Other (split tips, refund, void, close, print, email). The full enumerated list is documented in product configuration.
On this page
- Before you begin
- Run the report
- Filter reference
- Column reference
- Understanding missing log entries
- Tips
- Related articles
Before you begin
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
- Click the Reports icon.
- Search for and select Invoice Logs.
- Set the date range and filters.
- Click Refresh.
Filter reference
| Filter | Values | Description |
|---|---|---|
| Date range | From / To | Anchors on action timestamp. |
| Center | Configured centers | Limits to actions performed at the chosen center. |
| Invoice No. | Free text | Filters to a specific invoice for forensic audit. |
| Modified By | Active / terminated employees | Filters to actions performed by a specific employee. |
| Action | Any of the catalogued action types | Limits to a specific action class. |
Column reference
| Column | Description |
|---|---|
| Date/Time | Timestamp of the action. |
| Invoice No. | The invoice the action was performed on. |
| Action | The action name (Apply Membership, Update item - price, Refund payment, etc.). |
| Item | The item the action affected, if applicable. |
| Original Value | Field value before the action. |
| New Value | Field value after the action. |
| Modified By | Employee who performed the action. Blank for online (Webstore) sales. |
| Invoice Source | Origin of the invoice (Front Desk, Webstore, Customer Mobile App, etc.). |
Understanding missing log entries
The Invoice Logs report records actions that pass through the Zenoti interface. Actions originating from the system or through the API may not produce a row in this report.
This means that if an invoice shows a status β such as voided β but no corresponding entry appears in the log, that absence is not evidence that no action occurred. It indicates the action was taken through a route other than the interface, such as an automated system process or a direct API call.
If you see an invoice in an unexpected state with no matching log entry:
- Check with your Zenoti administrator whether any API integrations or automated workflows are configured for your organization that could affect invoice status.
- Review the Invoice Source column on the invoice itself β a source value other than Front Desk may indicate the action originated outside the interface.
- For API-originated changes, contact your integration team or Zenoti Support to trace the specific API call and its timestamp.
Do not treat a missing log entry as confirmation that an action did not happen. Use the log as one signal alongside the invoice's current state and any integration activity logs available to your team.
Tips
- Track unusual edit volumes per employee. Filter by Modified By and watch for outliers in action counts; high volumes may indicate a process gap or training issue.
- For dispute investigations, filter by Invoice No. to see the full action history for a single invoice.
- Pair with Invoice Source. When a log entry is missing, check the Invoice Source column on the invoice record to determine whether the originating channel bypasses the interface log.