Seven reports worth a second look
Every expense audit is three questions: is there a receipt, is it within limits, is it business. May asked all 38 reports, flagged seven, and holds 8,440.00 until someone with a name answers.
◆ The sweep, Maythree checks, seven holds.
| Result | Reports | Held |
|---|---|---|
| Clean | 31 | 0.00 |
| Missing a receipt | 4 | 6,840.00 |
| Over the meal limit | 2 | 1,290.00 |
| Personal charge found | 1 | 310.00 |
| The sweep | 38 | 8,440.00 |
The population is the expense page’s own 38, swept whole. The holds stay small because the sweep is standing: the personal charge got caught in its first month rather than at year end, and the receipt chasers know by Tuesday. Flags clear by name, never by aging out. Sample values are illustrative, never client data.
◆ The control twinthe payables side runs the same play.
This page is the expense edition of the match-exception sweep on the supplier side: whole population, few flags, every hold owned. Controls earn trust by clearing things, and both pages measure themselves by what leaves the list.
◆ The owned answerthree checks as three queries.
On landed report lines from the module star, a missing receipt is a null, a limit breach is a comparison, and a personal category is a code. The sweep is the same three queries nightly, and the partition above is their kept monthly result.
- sweep
- The same checks over the whole population, not a sample.
- hold
- Flagged money waiting on a named answer.
- meal limit
- The per-day policy cap a line can breach.
- aging out
- Clearing a flag by ignoring it; banned here.