Payment Verification & Approval
Recorded vs verified payments, roles, and why revenue can differ from expectations.
Verification is how TatTool separates recorded money from trusted money for reporting.
If your staff registers offline payments (cash, terminal, bank transfer), verification is the control step that keeps reporting reliable.
Fast rule
Only verified payments (minus verified refunds) count as revenue in TatTool.
Recorded Vs Verified
Payments have three operational states:
- Recorded
- Verified
- Deleted (voided)
Only verified payments are included in revenue insights.
Deleted (voided) payments are removed from operational views and revenue, but remain in the audit trail.
Who Can Verify Payments
By default, these roles can verify payments:
- Owner
- Admin
- Manager
Members and receptionists can create payments but cannot verify them unless your organization enables auto-verification for specific payment types.
Auto-Verification Settings
In Payment Settings, you can configure:
- Online payments to be verified automatically (recommended)
- Offline payments to require manual verification (recommended)
See: Payment Settings
Daily Payment Verification Page
Under Finance → Payment verification, you can:
- View payments grouped by day
- Verify payments throughout the day
- Ensure everything is approved before it affects reports
Editing Or Correcting Verified Payments
Only recorded payments can be edited. If a payment is already verified:
- Unverify it (a reason is required)
- Make the needed edits
- Verify it again
If a recorded payment should not exist at all, delete (void) it with a reason instead of editing it into something different. If it was already verified and money actually happened, use a refund instead.
See: Editing, Deleting & Audit Trail
How Verification Affects Revenue
If a payment is recorded but not verified, it will not count as revenue. This is the most common reason "revenue does not match" when teams are first adopting verification workflows.