Expense and sponsorship requests
One request, followed from the advisor who asks to the person who pays. Each tab is a screen in the product. All names and amounts are made up, and nothing is saved.
Dana Whitfield
My requests
| Submitted | What for | Requested | From allowance | Status |
|---|---|---|---|---|
| 2026-10-14 | Hole sponsor, Lakeshore charity golf outing | $1,000.00 | — | Waiting for approval |
| 2026-10-02 | Client dinner, three prospects | $420.00 | $420.00 | Paid |
| 2026-09-18 | Ad in St. Mark's school newsletter | $600.00 | $600.00 | Paid |
| 2026-07-09 | Community 5K table sponsorship | $2,180.00 | $2,180.00 | Paid |
Scenario 4: the advisor sees the year's allowance, what has been used, and what is left, without asking. Whether the allowance is per advisor or per team, and where the production figure comes from, is decision 3. The reset on 1 January is decision 4's default.
New request
Your allowance
The approver decides how much of a request counts against your allowance.
Scenarios 2 and 3: an advisor asks to be reimbursed (a client dinner) or asks the firm to pay for something (a sponsorship). Whether these are one kind of request or two is decision 6; the switch above shows the question and changes nothing. One PDF per request is decision 11's default.
Waiting for approval
| Submitted | Advisor | What for | Requested | Allowance left | |
|---|---|---|---|---|---|
| 2026-10-14 | Dana Whitfield | Hole sponsor, Lakeshore charity golf outing | $1,000.00 | $1,600.00 | |
| 2026-10-13 | Marcus Lee | Lunch with two clients | $96.40 | $5,210.00 | |
| 2026-10-10 | Priya Shah team | Centennial name on Riverside school foundation flyer | $250.00 | $310.00 |
Scenario 5: one queue that every approver sees, so nobody has to ask who approved what. Whether either approver can approve anything is decision 8.
Dana Whitfield · $1,000.00
Request
Split the request
On the call this reads as $500.00 reimbursed now. In Jordan's demo it reads as $0.00 now.
▲ This would take Dana past this year's allowance.
QuickBooks booking
Dana's allowance
History
- Submitted by Dana Whitfield, 2026-10-14
- Waiting for approval
Scenario 1: Jordan's $1,000 example, split $500 to the allowance and $500 charged back. What is actually paid out now is decision 2, because the call and the demo disagree, so the screen shows both readings and settles neither. Try changing the two amounts: the firm's share and the allowance left update.
Scenario 6: the approver codes the booking, and the lines must add up to the request. Whether the approver or the payer picks the accounts is the check in that scenario.
Scenario 7: reject and send back are both offered, which is decision 7's default. Going past the allowance warns the approver and does not block, which is decision 5's default.
Dana Whitfield · $1,000.00
Approved split
Record the payment
Scenario 6: the payer sees exactly what to pay, what to charge back, and how to book it, then records the payment by hand. The payment methods are decision 12's default, taken from Jordan's demo. The chargeback is recorded here for the payer to apply; nothing goes to the commission system automatically.
Allowance tally, 2026
| Advisor or team | Gross production to date | Allowance (1%) | Used | Left | |
|---|---|---|---|---|---|
| Dana Whitfield | $480,000 | $4,800.00 | $3,700.00 | $1,100.00 | |
| Priya Shah team | $396,000 | $3,960.00 | $3,650.00 | $310.00 | ▲ close to the limit |
| Marcus Lee | $612,000 | $6,120.00 | $910.00 | $5,210.00 | |
| Tom Becker | $254,000 | $2,540.00 | $0.00 | $2,540.00 |
Scenario 4: the spreadsheet Jordan keeps today, kept by the workflow instead. Who enters each month's production figure, and whether teams share an allowance, is decision 3. Who besides approvers and the payer can see this page is decision 9.
Illustrative placeholder data and in-memory state only. Built from the expense reporting design spec, v0.2, whose twelve decisions are all still open.