Billing History Filters and Audit Workflow

Summary

History view is your audit layer. This guide explains efficient filtering and incident-grade transaction review. For operators, this page should be used as a decision surface, not only as a UI form. Always pair page actions with downstream validation in the relevant live workflow.

What this page is for

• Investigate financial anomalies quickly.
• Separate deposit vs fee behavior.
• Produce reliable audit notes.

Before you start

• Know incident time window.
• Identify impacted bot(s) if subscription-related.
• Prepare expected transaction type and status.

Step-by-step workflow

1. Open History tab in /dashboard/billing.
2. Set status filter (all/pending/completed/failed).
3. Set type filter (deposit/subscription/fee/adjustment).
4. Use search query to narrow results.
5. Inspect amount direction (+/-) and timestamps.
6. Export findings into incident notes.

Key states and error handling

• History pagination can hide older records unless page changes.
• Status filtering is essential during payment incident triage.
• Direction (in/out) clarifies cashflow quickly.

Best practices

• Start broad, then narrow filters progressively.
• Cross-check suspicious entries with recent operational events.
• Keep screenshot evidence with visible filters.

Troubleshooting

• If expected record is missing, reset filters and page index.
• If amount looks incorrect, verify mills-to-USD interpretation.
• If data seems stale, refresh billing queries and retry.
• If issue persists after one clean retry, capture exact toast/banner text, selected bot, and timestamp before escalation.

UI reference (what each control does)

• Overview tab shows wallet balance and funding controls.
• Subscriptions tab applies plan changes per bot.
• History tab supports status/type filtering for financial audits.
• Information tab provides policy context and operational reminders.
• Top-up validation enforces minimum amount requirements.
• Auto-recharge requires payment method readiness and explicit settings save.
• Displayed plan pricing is visible in UI and should guide operator expectations.
• Billing toasts are primary diagnostics for top-up and subscription failures.

Operator checklist (before shipping changes)

• Keep wallet above safety margin before high-volume campaigns.
• Validate bot selection before changing subscription tier.
• Use preset top-up values when rapid funding is required.
• Enable auto-recharge only after payment method is confirmed.
• Review history filters weekly for anomaly detection.
• Re-test Bots/Fan Inbox behavior after major billing actions.

Real-world scenario

AI actions stop during a high-traffic period. The operator finds low wallet balance, tops up using a preset amount, confirms subscription health per bot, and verifies inbox composer availability returns immediately.

1. Identify the exact scope (bot, period, module) before any change.
2. Apply one targeted correction based on observed UI state and messages.
3. Validate outcome in the live operational flow linked to this page.
4. Document the final state so future incidents can be solved faster.