Reconcile payment transactions
Reconciliation matches your payment processor payouts to your bank deposits and confirms that every settled payment has reached the bank. Use the reconciliation report to investigate mismatches, mark batches as reviewed, and document unresolved discrepancies.
Important β one-period lag. The current week's transactions are reconciled in the following week (current month's in the following month). The lag exists because processor payouts must settle to the bank before they can be matched. The fastest possible time-to-detection for a payout discrepancy is one period (one week or one month, depending on your settlement frequency).
Audience: Finance staff and organization or center administrators responsible for verifying that processor payouts match bank deposits.
On this page
- How to reach the reconciliation report
- Workflow overview
- Set reconciliation preferences
- Read the reconciliation summary
- Reconcile a period
- Reconciliation batches list
- Reconciliation statuses
- Reading the mismatch columns
- Common bank-comparison challenges
- When a mismatch can't be explained
- Chargeback handling on reconciliation
- Refund-tip reversal effect on MyZen Wallet
- Reconciliation features
- Processor reports
- Tips
- Troubleshooting
Before you begin
Permission: Reconcile Payments (under Payments) β Required to access the reconciliation report and review batches.
Availability: Reconciliation depends on processor settlement report imports. Adyen and Stripe settlement reports are processed for reconciliation.
Who can do this. Org-level finance/admin and center-level admin roles with the View permission. Approval (in Auto-Approve mode) is gated by the same permission; for stricter separation of duties, configure approvers in your role administration.
- Processor settlement data must have been imported for the selected period. The system automatically imports settlement reports from configured processors on the processor's reporting schedule.
- Adyen requires the Adyen integration to be enabled for the Reconciliation Report to appear in the Configuration menu.
How to reach the reconciliation report
The same Reconciliation report can be opened from two entry points; the data is identical and the page filter governs scope.
| Entry point | Notes |
|---|---|
| Reports > Zenoti Payments > Reconciliation | Use this when you start from the Reports module. |
| Configuration > Payments > Process payments > Reconciliation | Embedded view. Use the org-level/center-level scope filter at the top to switch between organization view and center view. |
Both entry points open the same report.
Workflow overview
Use this section to plan your reconciliation cadence before configuring preferences.
- Imports. The processor (Adyen, Stripe, etc.) settles a payout to your bank and emits a settlement report. Zenoti imports the report and assigns the period.
- Match. Zenoti matches the imported processor payouts against the bank deposits available for the period.
- Review. A finance staff member opens each batch, compares amounts, and either marks it Reconciled / Reviewed (acknowledging that the bank deposit and the processor payout match for this batch) or flags discrepancies for follow-up.
- Approve. When Automatic Approval is enabled, matched batches auto-approve. When disabled, an approver must explicitly approve each Reviewed batch.
The four reconciliation states a batch can be in are described under Reconciliation statuses.
Set reconciliation preferences
Configure the cadence and approval mode before starting routine reconciliation.
- Open Configuration > Payments > Process payments > Reconciliation.
- Open Preferences.
- Set Settlement frequency:
- Weekly β payouts within a week roll into one reconciliation batch; reconciliation occurs in the following week.
- Monthly β payouts within a month roll into one batch; reconciliation occurs in the following month.
- Set Automatic Approval:
- On β Matched batches auto-approve once Reviewed.
- Off β An explicit Approve action is required after Review.
- Select Save.
Tip. Choose Weekly for high-volume centers where catching mismatches quickly outweighs the per-period review effort. Choose Monthly for low-volume centers where weekly reconciliation creates more administrative overhead than the early-detection benefit justifies.
Read the reconciliation summary
The summary sits at the top of the reconciliation report and gives you the size of the review before you open any batch.
- Select the period in the period selector. If your organization has more than one payment processor configured, select the processor as well.
- Read the matched count and amount. These are the processor payouts that Zenoti matched to a bank deposit for the period. A high matched share means the remaining review is small.
- Read the unmatched count and amount. This is the work queue for the period β each unmatched row needs a reason, a note, or an escalation. Use it to decide whether the period can be closed in one session or needs to be split across days.
- Read the orphan charge count. An orphan charge is a charge with no corresponding invoice in Zenoti, so it never enters the payout-to-deposit comparison and will not clear through the batch review. Investigate orphan charges separately β see Manage orphan charges.
Reconcile a period
- Open the reconciliation report.
- Select the period. The system shows the current and recent eligible periods; the very latest period is unavailable until the one-period lag rule passes. If your organization has more than one payment processor configured, select the processor as well.
- The list shows reconciliation batches with status and action buttons. See Reconciliation statuses.
- Select Start on a Pending batch (or Review on an in-progress batch) to open the review and reconcile view.
- Compare the Payout amount with the Bank deposit for the period. Use the Common bank-comparison challenges section below if amounts do not match cleanly.
- For each mismatch row, review the Reason column. The system fills the reason where it can determine the cause β for example, processing fee deduction, partial refund, chargeback, currency-conversion delta, or refund-tip reversal. When the system cannot determine a cause, the row shows the placeholder "unable to determine the exact reason for the discrepancy".
- Use Add Notes on any mismatch row that requires explanation for audit purposes.
- Select Mark as Reconciled for batches where the comparison checks out. The status moves to Reconciled / Not Reviewed; an approver action moves it to Reconciled / Reviewed.
Worked example. Your center uses Weekly settlement. On Monday of week 3, you open the reconciliation report and see a batch for week 2 in Reconciliation Pending status. The processor payout shows $4,820.00 and the bank deposit shows $4,793.50. The mismatch table shows one row with a Reason of "processing fee deduction" for $26.50. You add a note β "Adyen processing fee per weekly statement" β and mark the batch Reconciled. The status moves to Reconciled / Not Reviewed until your finance manager approves it.
Reconciliation batches list
The batch list is the working view for the selected period. Each row is one reconciliation batch.
| Column | Description |
|---|---|
| Period | The settlement period the batch covers β a week or a month, depending on your Settlement frequency preference. |
| Payout amount | The total processor payout amount assigned to the batch for the period. |
| Status | The batch's workflow state. See Reconciliation statuses. |
| Action | The action available for the batch's current state β Start, Review, Payout Details, or Collection Details. See Reconciliation statuses. |
Reconciliation statuses
The reconciliation report shows one of four states per batch.
| Status | Meaning | Action button |
|---|---|---|
| Reconciliation Pending | The batch has not yet been opened. Imports are complete; processor payouts are identified; bank deposits are available. | Start |
| Not Reconciled / Not Reviewed | The batch was opened but mismatches remain unresolved. | Review |
| Reconciled / Not Reviewed | All rows in the batch are matched (or marked reconciled with notes). Awaiting reviewer approval. | Review then approve |
| Reconciled / Reviewed | The batch is closed. Use Payout Details and Collection Details for drill-down. | Payout Details / Collection Details |
Note β these are workflow states. Internally, individual transaction rows track a status string returned by the processor. The four labels above are workflow-derived states applied at the batch level so finance staff can manage progress through the period. The labels do not enumerate every possible per-row status.
Reading the mismatch columns
Each unmatched row shows:
| Column | Description |
|---|---|
| Bank deposit reference | The reference for the deposit on the bank side of the comparison. |
| Processor payout ID | The identifier of the processor payout the row belongs to. |
| Amount | The amount on the row. |
| Reason | Why the row is mismatched. The system populates this where it can determine the cause; otherwise it shows "unable to determine the exact reason for the discrepancy". Common causes include processing-fee deduction, partial refund, chargeback, currency-conversion delta, and refund-tip reversal. |
Common bank-comparison challenges
The "compare two amounts" step is rarely as clean as it sounds. Use these scenarios to plan your investigation.
| Scenario | What to check |
|---|---|
| The bank groups multiple days of deposits into one entry. | Compare the bank's grouped amount against the sum of processor payouts for the same days. The Payout Details drill-down shows per-day payouts. |
| The bank's deposit date is one or two days after the processor payout date. | Match by amount within a 1β2 day window. Processing delays vary by bank and payment rail. |
| The bank's deposit amount is lower than the processor payout because the bank deducted fees separately. | Document the fee deduction in Notes for audit; the difference is a bank fee, not a Zenoti or processor mismatch. |
| The payout is lower than the gross transaction total by more than the standard processing fee. | Check whether your center is on the Surcharge on IC+ billing model, which records a per-transaction secondary markup fee that is deducted before payout. Compare the batch against the Markup Fee and Secondary Markup Fee columns in the Digital Payments report. See Surcharge on IC+ (Secondary Markup) Billing Model. |
| Refund or partial refund reduces the day's net payout. | The Mismatch table's Reason column should show "Refund" or "Partial refund". |
| Chargeback hit during the period. | Look for Chargeback or Chargeback Reversed rows. See Chargeback handling on reconciliation. |
| A charge appears on the processor side with no matching invoice in Zenoti. | This is an orphan charge and will not clear through batch review. See Manage orphan charges. |
When a mismatch can't be explained
When the Reason field shows "unable to determine the exact reason for the discrepancy" and your manual investigation does not surface a cause:
- Use Add Notes on the row to capture what you investigated and the residual unexplained amount.
- Mark the batch Reconciled if the unexplained amount is within your business's tolerance for routine reconciliation noise β for example, fractional currency-conversion deltas.
- Escalate to Zenoti Support and to your processor's support team if the unexplained amount is material. Include: the batch period, the row's bank reference and processor payout ID, the unexplained amount, and the steps you took to investigate.
- Re-open the batch later if information arrives that explains the difference. The Notes field captures the audit trail.
Chargeback handling on reconciliation
Chargebacks affect reconciliation timing because disputes can take weeks or months to resolve. The reconciliation report surfaces two chargeback states on individual rows:
- Chargeback β the chargeback occurred and reduced a payout in the current period.
- Chargeback Reversed β the chargeback was overturned and the disputed amount is being returned to your account.
A chargeback that occurs after the original transaction's reconciliation period appears in the period during which the chargeback was settled, not retroactively in the original period. So a previously Reconciled / Reviewed period does not revert when a new chargeback hits a transaction from that period; instead the new chargeback shows up as a row in the period it is settled.
Pair this view with Defend payment disputes to track each chargeback's defense status independently.
Refund-tip reversal effect on MyZen Wallet
When an invoice is fully refunded inclusive of provider tips, the tip-payout details reflect the adjustment as a deduction from the employee's MyZen Wallet balance. On the reconciliation report, this appears as a negative line item against the original payout's tip portion. The employee's MyZen Wallet balance is updated automatically; no separate action is required in the Wallet workflow. This is a meaningful financial event β flag it in Notes when reconciling so that the employee's wallet balance change has a documented audit trail.
For the employee mobile wallet and earnings, see the MyZen category.
Reconciliation features
These features are available throughout the reconciliation workflow, not as sequential steps.
| Feature | Use |
|---|---|
| Add Notes | Per-row free-text notes for mismatch explanation, escalation pointers, or audit context. |
| Download | Export the current view (per-period or per-batch). |
| Floating Panel | Drill-down into a specific batch without losing context of the parent list. |
| Manage Columns | Show/hide columns to focus on the fields you use during a review session. |
Processor reports
Behind the scenes, the system processes settlement reports from configured processors:
- Adyen β Settlement detail reports, activity reports.
- Stripe β Activity reports, network cost reports, fee reports.
Reports are queued for processing and the results feed into the reconciliation view. The system logs all processor report requests and responses for audit purposes.
Tips
- Reconcile weekly even if your settlement frequency is monthly. Opening the report weekly lets you spot import failures or missing bank deposits before the end-of-month close, when the volume of rows to investigate is much larger.
- Read the summary before opening a batch. The unmatched count tells you how much review the period needs, and the orphan charge count tells you how much of the difference will never clear through batch review.
- Use the Floating Panel for side-by-side comparison. Drill into a batch's Payout Details in the Floating Panel while keeping the batch list visible, so you can cross-reference multiple batches without navigating back and forth.
- Add Notes proactively, not only for unexplained mismatches. Even when the Reason column is populated, a brief note β for example, "confirmed with bank statement line 14" β creates an audit trail that speeds up future reviews and external audits.
- Align your settlement frequency with your bank's reporting cycle. If your bank consolidates deposits weekly, choose Weekly settlement frequency so the batch boundaries match and you avoid artificial multi-day grouping mismatches.
Troubleshooting
The current period does not appear in the batch list. The one-period lag rule means the current week (or month) is not available for reconciliation until the following period begins. If the previous period is also missing, check whether processor settlement data has been imported. Contact Zenoti Support if imports appear stalled.
A batch is stuck in Reconciliation Pending with no action button. This can occur when the processor settlement report has not yet been received or processed. Verify that your processor integration is active and that the settlement report for the period has been emitted by the processor. Payout speeds vary by processor; allow the processor's standard settlement window before escalating.
The Reason column shows "unable to determine the exact reason for the discrepancy" for every row in a batch. This typically indicates that the processor's settlement report does not include enough transaction-level detail for Zenoti to map individual rows. Export the batch using Download and compare against your processor's detailed settlement report directly. If the pattern persists across multiple periods, contact Zenoti Support to review the settlement report import configuration for your processor.
The unmatched amount will not reduce no matter how many rows you review. Check the orphan charge count in the summary. Orphan charges have no matching invoice in Zenoti, so they never resolve through batch review and must be handled separately β see Manage orphan charges.
A previously Reconciled / Reviewed batch now shows a chargeback row. This is expected behavior. A chargeback that is settled after the original transaction's reconciliation period appears in the period in which the chargeback is settled, not retroactively. The original batch remains Reconciled / Reviewed. Review the new chargeback row in the current period and use Defend payment disputes to track the dispute.