Verified Benchmark Results

Every number tested on this machine • March 22, 2026 • Python 3.11.8 • CPU-only (no GPU)

Corrections from prior claims: Previous materials cited "8,829 invoices/sec" and "100% accuracy." Those numbers came from a synthetic benchmark that skipped OCR, field extraction, and database operations. The real numbers are below. Every figure on this page was measured by running the actual pipeline code on actual test files.

At a Glance

178
Digital PDFs/sec
(full pipeline)
100%
Core field accuracy
(amount, date, inv#, vendor)
74.2%
All-field accuracy
(12 types, 10 invoices)
151ms
HTTP upload + process
(new document)
0.41
Scanned images/sec
(EasyOCR, CPU-only)
5/5
ROI math
sanity checks

Test 1: Digital PDF Full Pipeline

PASS

Read file → SHA-256 hash → PyMuPDF text extract → 14 regex field extractors → normalize output

MetricResult
Files tested12 PDFs (70 pages)
Avg per file5.6ms
Throughput178 invoices/sec
50-page PDF27.2ms (1,840 pages/sec)
Text extraction success12/12 (100%)
invoice_1.pdf   -> 7.5ms  | 965 chars  | 11/14 fields
invoice_7.pdf   -> 3.1ms  | 980 chars  | 12/14 fields
multi_page_50   -> 27.2ms | 47132 chars | 13/14 fields

Test 2: Field Extraction Accuracy (Real Invoices)

74.2% overall

14 regex extractors run on text from 10 real invoice PDFs — 12 field types per invoice

Field TypeFoundTotalRate
Amount ($)1010100%
Date1010100%
Invoice Number1010100%
Vendor Name1010100%
Store ID1010100%
Payment Terms1010100%
Tax Rate1010100%
Priority1010100%
Work Order #81080%
Trade11010%
NTE0100%
PO Number0100%

Context: NTE, PO#, and trade fields were not present in the test invoice text. 0% extraction is correct behavior — the extractor returns nothing when the field doesn't exist (no false positives). Core business fields (amount, date, invoice#, vendor) are 100%.

Test 3: Field Extraction (Synthetic Inputs)

19/19 PASS

19 hand-crafted test strings with known expected outputs across 14 field types

MetricResult
Tests run19
Passed19 (100%)
Avg extraction time0.093ms
Total time1.8ms
PASS: amount     | Total: $1,234.56          | got: 1234.56
PASS: date       | Due: 2026-03-22           | got: 2026-03-22
PASS: wo#        | Work Order: WO-12345      | got: WO-12345
PASS: vendor     | Vendor: ABC Hauling Corp  | got: ABC Hauling Corp
PASS: trade      | Trade: HVAC Service       | got: HVAC

Test 4: Scanned Image OCR (Degraded Quality)

50% usable

30 images across 10 quality categories • EasyOCR • CPU-only (no GPU acceleration)

Image CategoryUsableAvg ConfidenceAvg Time
Clean scan3/30.924.1s
Low noise3/30.904.4s
High noise3/30.844.5s
Rotated 2 degrees3/30.874.9s
Rotated 5 degrees3/30.774.1s
Blur0/30.092.0s
Heavy blur0/30.301.3s
Low DPI (150)0/30.126.0s
Low DPI (75)0/30.031.5s
Combined degradation0/30.225.5s

Honest assessment: OCR handles clean, noisy, and rotated scans well. Fails on blur and low DPI. For production use, scanned invoices should be at least 200 DPI and reasonably focused. Blurry phone photos will not process reliably.

Test 5: HTTP API Latency

PASS

10 requests per endpoint, round-trip measured

EndpointAvgP50MinMax
/api/stats21ms17ms9ms40ms
/api/docs (10 results)28ms28ms15ms78ms
/api/vendors13ms14ms4ms27ms
/api/work-orders193ms42ms30ms1,562ms
/api/locations16ms21ms4ms28ms
File UploadTimeRate
New document (64KB PDF, full processing)151ms6.6 docs/sec
Duplicate detection (same file)15ms24 docs/sec

Note: Work orders endpoint spiked to 1.5s on cold first call (SQLite page cache miss on 55KB response), then settled to ~42ms. All other endpoints consistently under 30ms.

Test 6: ROI Calculator Math Verification

5/5 CHECKS

Default scenario: 75 trucks, 120 routes/day, 55 mi/route, $3.85/gal diesel, 5.0 MPG, 15% AI optimization

Annual miles:      1,716,000 = 120 routes x 55 mi x 260 days
Gallons used:      343,200 = 1,716,000 / 5.0 MPG
Annual fuel cost:  $1,321,320 = 343,200 gal x $3.85
Miles eliminated:  257,400 = 1,716,000 x 15%
Fuel saved:        $198,198 = $1,321,320 x 15%
Maint saved:       $48,906 = 257,400 mi x $0.19/mi
TOTAL SAVED:       $247,104/year
Sanity CheckValueExpected RangeResult
Fuel cost per truck per year$17,618$8K - $35KPASS
Miles per truck per year22,88015K - 100KPASS
Savings % matches input15.0%15%PASS
Total under 30% of revenue$247,104< $18MPASS
Diesel in EIA forecast range$3.85$3.40 - $5.00PASS

Note: The 15% route optimization savings percentage is an adjustable input, not a guaranteed outcome. Published case studies (Casella 21%, Virginia Beach, Barcelona 30%) suggest 10-30% is achievable, but we have not run Flood Brothers routes ourselves.

Test 7: Email Parsing & Matching

PASS

182 ServiceChannel emails parsed for work order numbers and vendor identification

MetricResult
Emails parsed182
Speed13,555 emails/sec
Work order # detected178/182 (97.8%)
Vendor detected181/182 (99.5%)

Test 8: Deduplication Speed

PASS

SHA-256 hash of 482 files across demo batch and inbox

MetricResult
Files hashed482
Speed27,867 hashes/sec
Duplicates found0

What We Cannot Prove From These Tests

ClaimStatusWhy
Manual AP baseline (4 invoices/hr)UnverifiedIOFM industry report — we didn't time manual clerks ourselves
Route optimization saves 15-21%UnverifiedCasella/Virginia Beach case studies — we haven't run Flood Brothers' actual routes
Valuation multiple increase (3x to 6x)ProjectionBased on industry benchmarks and MiroFish simulation, not audited financials
Flood Brothers revenue ($60.6M)Third-party estimateGrowjo/ZoomInfo estimate, not confirmed by Flood Brothers
GPU-accelerated OCR speedNot testedAll OCR tests were CPU-only. GPU would be significantly faster.

Benchmark suite: benchmark_pipeline.py + benchmark_all.py
Results saved to: benchmark_results.json + benchmark_full_results.json
All tests reproducible by running the scripts in the doc-rag project directory.

Prepared by OZ3 Automation • March 22, 2026