UBS
3 job-history rows.
1 upcoming / 2 completed
Prestige Limo Ops
Mock customer payments dashboard. Local/mock only. No payment API, bank API, notification, or Supabase write is used.
Internal Staff Dashboard — Not Customer-Facing
Use /book for customer booking requests. This page contains dispatcher, billing, payment review, and staff-only planning tools.
Total Outstanding
$4,340
Overdue
$1,020
Paid This Month
$2,570
Follow-ups Today
3
Staff folder handoff
Search the index, open the existing customer folder, then review job history context there. This handoff is staff-facing and not customer-facing.
Visible mock folders: 3
Load saved customer accounts from the guarded read path when needed.
UBS
3 job-history rows.
1 upcoming / 2 completed
Ritz Carlton
3 job-history rows.
1 upcoming / 2 completed
Individual VIP Customer
2 job-history rows.
1 upcoming / 1 completed
Read-only local guide. It does not create, save, send, assign work, or change customer records.
Internal dispatcher/admin only
Mock/local only. Not customer-facing. No Supabase save, invoice number, invoice or statement generation, notification, calendar sync, payment API, or bank API is used.
Internal dispatcher/admin only
Mock/local only. Rows reset on refresh and are not saved. No Supabase save, customer/payment record, invoice number, invoice, statement, notification, calendar sync, payment API, or bank API is used.
0 local mock booking rows.
Mock/local list filters only affect rows on this page. Nothing is saved or sent.
Showing 0 of 0 local mock rows.
Showing 0 of 0 local mock rows with All mock rows. Filter changes only visible mock rows and counts; no row data is added, removed, saved, or permanently changed. Mock quick filter only — no invoice, payment request, or statement was generated, no storage or Supabase write occurs, and no payment, PDF, notification, or network API is called.
Mock visible billing summary
0 visible of 0 local mock rows
Quick filter
All mock rows
Billing month
No visible billing month
Status count
No visible status
Mock/local only. This strip summarizes currently visible mock monthly billing rows after the local quick filter. It does not create invoice numbers, generate invoices or PDFs, send payment requests, call network APIs, write browser storage, write Supabase, permanently change row data, add rows, remove rows, update payment status, or trigger messaging or notification behavior.
Internal staff-only / read-only
0 visible of 0 local mock rows
Mock summary only — no invoice, payment request, or statement was generated. This read-only summary does not create invoice numbers, generate invoices or PDFs, send payment requests, call network APIs, write browser storage, write Supabase, change row data, add rows, remove rows, update payment status, or trigger notification behavior.
Internal staff-only / guarded read
Admin-only read. Loads safe saved booking references for the selected customer/account only. No booking write, invoice number, invoice, PDF, payment/bank action, payout, notification/calendar action, parser/debug data, contact details, internal notes, or customer price is returned.
Customer/account
Select a customer/account first.
Returned
0 saved bookings
Matched
0 recent admin bookings
Source
Guarded admin saved booking read; read-only customer folder context.
Select a customer/account, then load saved bookings from the guarded admin read path.
No saved booking references loaded yet.
Internal staff-only / mock-local
Preview-only. Not customer-facing. No invoice number, real invoice, statement, PDF, sending, Supabase save, payment API, bank API, notification, calendar sync, payment provider, or audit record is created.
Uses currently visible local mock rows.
Create a mock draft invoice preview from the currently visible local mock rows. Nothing is saved, numbered, generated, or sent.
No draft invoice preview selected yet.
Select bookings from the mock monthly billing list, then create a draft invoice preview for staff review.
Empty preview state only. No preview data, invoice number, PDF, sending, or save is active here.
Zoho Invoice-style simplicity: search first, scan the payment state, then open the customer folder.
Mock/local only. Changes reset on refresh and are not saved. No payment API, bank API, notification, or Supabase write is used.
5 mock items need account follow-up.
Total outstanding
$4,340
5 mock customer balance rows
Overdue amount
$640
1 overdue
Due soon
$3,320
3 due within 7 days
Needs follow-up
5
Mock manual follow-up only
Showing 1-5 of 5 customers
Mock controls only. Use the buttons to simulate manual payment tracking without saving records.
VIP-0003
Outstanding
$1,700
Invoice Sent
Aging
0-30
Due today
Due date
25 May 2026
Last follow-up
25 May 2026
Next action: Check expected payment
Completed job + balance due = Outstanding
Mock helper: this row updates local page state only.
UBS-0004
Monthly Account
Outstanding
$1,200
Invoice Sent
Aging
0-30
Due in 5 days
Due date
30 May 2026
Last follow-up
24 May 2026
Next action: Group for billing review
Monthly account can be grouped later into statement
Mock helper: this row updates local page state only.
UBS-0003
Monthly Account
Outstanding
$640
Overdue
Aging
0-30
3 days overdue
Due date
22 May 2026
Last follow-up
24 May 2026
Next action: Call accounts today
Due date passed + balance due = Overdue
Mock helper: this row updates local page state only.
RITZ-0004
Outstanding
$420
Unpaid
Aging
0-30
Due in 6 days
Due date
31 May 2026
Last follow-up
21 May 2026
Next action: Manual follow-up
Completed job + balance due = Outstanding
Mock helper: this row updates local page state only.
RITZ-0003
Outstanding
$380
Partially Paid
Aging
0-30
6 days overdue
Due date
19 May 2026
Last follow-up
20 May 2026
Next action: Confirm remaining balance
Partial payment keeps balance visible
Mock helper: this row updates local page state only.
Mock/local only. Follow-up changes reset on refresh and are not saved.
No notification, WhatsApp message, email, payment record, bank record, or Supabase row is created.
5 mock follow-ups need collection attention.
Mock follow-up controls only. Use the buttons to simulate collection follow-up without sending messages.
UBS-0003
Monthly Account
Payment Status
Overdue
Balance Due
$640
Next Follow-up
29 May 2026
Overdue balance needs collection follow-up
Mock helper: this follow-up updates local page state only.
UBS-0004
Monthly Account
Payment Status
Invoice Sent
Balance Due
$1,200
Next Follow-up
29 May 2026
Monthly account can be grouped into statement later
Mock helper: this follow-up updates local page state only.
RITZ-0003
Payment Status
Partially Paid
Balance Due
$380
Next Follow-up
23 May 2026
Partial payment still has balance due
Mock helper: this follow-up updates local page state only.
RITZ-0004
Payment Status
Unpaid
Balance Due
$420
Next Follow-up
23 May 2026
Unpaid balance needs collection follow-up
Mock helper: this follow-up updates local page state only.
VIP-0003
Payment Status
Invoice Sent
Balance Due
$1,700
Next Follow-up
25 May 2026
Invoice sent but balance remains due
Mock helper: this follow-up updates local page state only.
Mock/read-only only. No statement record, invoice record, payment record, bank record, notification, or Supabase row is created.
No statement is generated, sent, saved, or assigned a real statement number.
1 mock monthly account preview.
Fixed invoice prefix: UBS
Statement period: May 2026 billing cycle (mock preview)
Statement number: Not generated (mock/read-only preview)
Included invoice/reference rows
UBS-0003
Overdue
$640
Follow-up: 29 May 2026
UBS-0004
Invoice Sent
$1,200
Follow-up: 29 May 2026
Mock statement total
$1,840
Fully paid rows are excluded from this mock total.
Monthly account can be grouped into statement later. Balance due remains visible until paid. Statement preview is not generated or saved.
Open Customer FolderMock helper: preview only; nothing is generated, saved, or sent.
Mock only. No payment record, invoice record, bank record, notification, or Supabase row is created.
Mock only. No notification, WhatsApp message, email, payment record, bank record, or Supabase row is created.
Mock only. No statement record, invoice record, payment record, bank record, notification, WhatsApp message, email, SMS, or Supabase row is created.
Invoice numbers are unique and must not be reused. Once issued, invoice numbers are immutable. Changing a customer invoice prefix later requires warning/protection because it can make invoice history messy.
This dashboard does not implement real invoice generation yet; it only shows local mock examples.