See the product
Annotated examples of the review workflow using fictional demo-company data—so you can see what authorizing QBO access is for before you connect a client file.
These panels illustrate shipped UI patterns. They are not live screenshots of a customer ledger.
Example data · Demo company
1. Line recode after review
Changed After Review exception with an explicit category shift:
Exception · Changed after review
Bill #4821 · Acme Office Supply
Category: Office Supplies → Owner Draw
Amount: $1,200.00 → $1,200.00
Total unchanged—amount-only checks would miss the reclass.
Example data · Demo company
2. Closed-period edit
Bill dated on or before the synced QBO closing date was edited:
Closed-period signal · Demo Co
Closing date synced: Aug 31, 2026 · Bill txn date: Aug 14, 2026
Amount: $1,200.00 → $12,000.00
BillGuardRail does not lock the period; it surfaces the bill edit for review.
Example data · Demo company
3. OCR-aware possible duplicate
Create-time Possible duplicate—not an automatic block or fraud finding:
Possible duplicate · Review prompt
New bill
Doc INV9083
Vendor: Chevron Inc
$1,250.00 · Aug 4
Prior bill
Doc INV-9082
Vendor: Chevron #401
$1,250.50 · Aug 3
Near doc number + normalized vendor + near amount/date cleared the fuzzy ladder.
Example data · Demo company
4. Per-vendor duplicate ignore
Settings → Alerts → Vendor overrides (future new bills only):
Landlord LLC
Threshold ($) · 20000
☑ Ignore duplicate matching
Skips duplicate scanning for this vendor going forward; amount, edit, and closed-period monitoring remain.
Example data · Demo company
5. Multi-company Bookkeeper queue
One workspace attention list across connected client companies (ledgers stay separate):
- River Dental · Possible duplicateINV-2201
- Northside Cafe · Changed after reviewCategory shift
- Oak Property Mgmt · Threshold$18,400 bill
Next
Read exact boundaries on How detection works, then start a trial when you are ready to connect via Intuit OAuth.