This sample mirrors the planned BustedBooks output: what looked unusual, why it matters, and what the owner or bookkeeper should check next inside QuickBooks.
| Severity | Finding | Vendor | Amount | Why flagged | Next step |
|---|---|---|---|---|---|
| High | Near duplicate payment | Acme Materials | $4,820.00 | Two payments with similar amounts were posted three days apart against the same vendor. | Confirm whether both invoices were valid and matched separate jobs. |
| Medium | Vendor spend spike | Metro Supply Co. | $12,400.00 | Current month spend is materially above the trailing baseline for this vendor. | Review supporting invoices and job allocation. |
| Review | Missing detail | Card Purchase | $1,000.00 | Round-number transaction has no memo or reference detail. | Add receipt/memo or verify category before month-end close. |
See how same-vendor and near-date payments become review candidates.
Review vendor activity against baseline spend before month-end cleanup.
Rank blank or weak transaction context by amount, vendor, and review risk.
The sample report shows plain-English review leads for duplicate payment candidates, vendor spend spikes, missing transaction detail, severity, why each item was flagged, and the next step to verify in QuickBooks.
No. Findings are review leads. The report helps owners and bookkeepers decide what to open first, but the final decision should be verified against QuickBooks records and source documents.
Yes. BustedBooks provides a sample CSV so customers can see the expected finding fields before connecting QuickBooks or paying for a scan.