This page renders the illustrative sample findings report that a zero-day scan produces. Every figure, finding and vendor name is made up for demonstration. No customer data is used.
The report has eight sections, each modelled on the output the scan writes when your read-only connections are live and the initial verification baseline has run.
01. Coverage table
The coverage table is the first page of the report. It shows what the scan reached, what it could not reach, and how the landed data ties to your source trial balance.
| Entity | Period | Module | Source | Landed | Tie-out | Notes |
|---|---|---|---|---|---|---|
| Apex Logistics US | Jan 2024 | NetSuite AP invoices | 1,247 | 1,221 | Tied | 1,221 landed; 18 parked, 8 excluded |
| Apex Logistics US | Jan 2024 | NetSuite AP payments | 983 | 983 | Tied | Payment register reconciled |
| Apex Logistics US | Jan 2024 | NetSuite Vendor master | 312 | 312 | Tied | All vendors mapped |
| Apex Logistics US | Jan 2024 | NetSuite Purchase orders | 1,089 | 1,089 | Tied | All purchase orders landed |
| Apex Logistics US | Jan 2024 | NetSuite GL | 3,891 | 3,891 | Tied | Trial balance reconciled |
| Apex Logistics US | Jan 2024 | Stripe | 412 | 412 | Tied | Gross sales to bank to ledger |
| Apex Logistics US | Jan 2024 | Bank (Operating bank) | 2,417 | 2,417 | Tied | Daily reconciliation complete |
| Apex Logistics US | Jan 2024 | NetSuite AR | 2,103 | 0 | Blocked | AR module not in scope for this scan |
| Apex Logistics US | Jan 2024 | Bank (second account) | None | None | Unavailable | Connector not yet configured |
Illustrative. The entities, modules, record counts and statuses above are made up for this example.
How to read the coverage table
- Source: the record count the connector reports from the source system for the in-scope period.
- Landed: the record count that passed through Mapping Studio and was accepted into Rever's canonical book.
- Tie-out: Tied means journal counts and debit/credit totals agree by entity, period and account. Blocked means the module was excluded from scope. Unavailable means the connector is not configured or the source system did not respond.
- Notes: records any inaccessible modules, missing periods or unavailable totals, as the zero-day scan procedure requires.
02. Landed populations
This section breaks down what landed by population type, with the source identifiers preserved.
| Population | Source count | Landed count | Parked | Excluded | Unverified |
|---|---|---|---|---|---|
| AP invoices | 1,247 | 1,221 | 18 | 8 | 0 |
| AP payments | 983 | 983 | 0 | 0 | 0 |
| Vendor master | 312 | 312 | 0 | 0 | 0 |
| Purchase orders | 1,089 | 1,089 | 0 | 0 | 0 |
| GL journal lines | 3,891 | 3,891 | 0 | 0 | 0 |
| Bank lines | 2,417 | 2,417 | 0 | 0 | 0 |
| Stripe settlements | 412 | 412 | 0 | 0 | 0 |
Illustrative. Counts are made up for this example. Parked records carry a reason (mapping discrepancy, duplicate source ID, invalid date) and an accountable next step; approval is never inferred to obtain a clean tie-out.
03. Trial balance reconciliation
The scan reconciles the source trial balance to the canonical book and performs functional-currency restatement checks, stating the source, rate, date and attribution basis.
| Account | Source TB (USD) | Landed TB (USD) | Difference | Status |
|---|---|---|---|---|
| 1010 Cash, operating bank | 2,847,192.41 | 2,847,192.41 | 0.00 | Tied |
| 1200 Accounts Receivable | 1,456,823.17 | 1,456,823.17 | 0.00 | Tied |
| 2000 Accounts Payable | (892,311.56) | (892,311.56) | 0.00 | Tied |
| 2100 Accrued Expenses | (234,187.92) | (234,187.92) | 0.00 | Tied |
| 3000 Equity, retained earnings | (3,189,861.77) | (3,189,861.77) | 0.00 | Tied |
| 4000 Revenue, freight | (4,123,456.78) | (4,123,456.78) | 0.00 | Tied |
| 5000 Cost of Freight | 3,012,345.67 | 3,012,345.67 | 0.00 | Tied |
| 6000 Operating Expenses | 1,123,456.78 | 1,123,456.78 | 0.00 | Tied |
Illustrative. The trial balance ties. In a real scan, any difference identifies the source, account, entity, period and reason, or the remaining uncertainty.
04. Initial verification baseline
Once the data ties out, the scan launches the approved initial verification and control baseline, attributing each specialist's work to its owner.
| Agent | Procedure | In-scope population | Findings raised | Status |
|---|---|---|---|---|
| Matcher | Three-way match (PO, receipt, invoice) | 1,221 AP invoices | 10 | Complete |
| Spend Guard | Duplicate invoice & payment detection | 1,221 AP invoices, 983 payments | 5 | Complete |
| Entitlement | Rebate & credit calculation | 47 vendor agreements | 2 | Complete |
| Sentinel | Vendor bank change & approval splitting | 312 vendors, 983 payments | 0 | Complete |
Illustrative. The agents above are the ones in the initial verification baseline. Each finding carries its evidence and is attributed to the specialist that raised it. The findings shown here are a selection of the 17 findings raised; the honesty ratio total reflects only the findings shown.
05. Findings with evidence: two columns
This is the core of the report. Every finding appears in two columns: Value identified (a supported opportunity that still needs validation or action) and Value recovered (verified cash received or a credit applied). Rever keeps them apart and reports the honesty ratio: value recovered divided by value found.
Duplicate payments (Spend Guard)
| Finding | Vendor | Invoice(s) | Amount | Evidence | Identified | Recovered |
|---|---|---|---|---|---|---|
| DUP-001 | Metro Forwarding | INV-4421, INV-4421 (dup) | $12,450.00 | Identical invoice number, date, amount; both paid on 15 Jan | $12,450 | $0 |
| DUP-002 | Beta Transport | INV-8891, INV-8891 (dup) | $8,720.00 | Same PO, same receiver, duplicate payment 3 days apart | $8,720 | $0 |
| DUP-003 | Gamma Freight | INV-1103, INV-1103 (dup) | $3,100.00 | Different vendor IDs (GAM-01, GAM-02) for same entity | $3,100 | $0 |
Illustrative. Vendor names, invoice numbers and amounts are made up for this example. Each finding links to the source documents in Records and the Inbox task for your approval.
Price drift (Spend Guard)
| Finding | Vendor | PO | Invoice | Drift | Evidence | Identified | Recovered |
|---|---|---|---|---|---|---|---|
| DRIFT-001 | Delta Haulage | PO-9834 ($5,000) | INV-6643 ($5,347) | $347 | Amendment B2 adds $275 fuel levy; $72 unexplained | $0 | $0 |
| DRIFT-002 | Epsilon Logistics | PO-3310 ($12,000) | INV-6678 ($12,650) | $650 | Rate increased 5.4% vs PO; no change order found | $650 | $0 |
Illustrative. In a real scan, Investigator traces each difference to the transaction, party or timing cause and recommends the correction for your approval. The $72 unexplained in DRIFT-001 appears in the unresolved line in Section 07.
Unclaimed rebates (Entitlement)
| Finding | Vendor | Agreement | Eligible base | Rebate rate | Identified | Recovered |
|---|---|---|---|---|---|---|
| REB-001 | Zeta Carriers | Vol rebate ≥$500k = 2% | $1,200,000 | 2% | $24,000 | $0 |
| REB-002 | Eta Freight | Early pay 10 days = 1.5% | $340,000 | 1.5% | $5,100 | $0 |
Illustrative. Entitlement calculates the contractual benefit, substantiates it and prepares a supported claim. A claim goes out only after your team approves it in the Inbox.
Three-way match exception (Matcher)
| Finding | Vendor | PO | Receipt | Invoice | Gap | Evidence | Identified | Recovered |
|---|---|---|---|---|---|---|---|---|
| 3WM-001 | FreightCo | PO-1884 ($4,502) | Short shipment ($180) | INV-7721 ($4,812) | $310 | A2 adds $240 fuel surcharge; $250 no document | $0 | $0 |
Illustrative. This is the freight case worked as a workpaper: from mismatch to approval, with tolerances you set and the cause read from documents. The $240 surcharge less the $180 short shipment explains $60, so $4,562 is supported and matched. The other $250 has no document and stays open (not accrued, not plugged).
06. Honesty ratio summary
Rever tracks value identified and value recovered in separate columns and reports the honesty ratio.
| Category | Value identified | Value recovered | Honesty ratio |
|---|---|---|---|
| Duplicate payments | $24,270 | $0 | 0% |
| Price drift | $650 | $0 | 0% |
| Unclaimed rebates | $29,100 | $0 | 0% |
| Three-way match exceptions | $0 | $0 | Not calculable |
| Total (findings shown) | $54,020 | $0 | 0% |
Illustrative. The honesty ratio is value recovered ÷ value found. At the time of the zero-day scan, no claims have been submitted or settled, so recovered is $0. The ratio updates as claims progress through your Inbox to verified cash or credit. The total above reflects the findings shown in Section 05, which are a selection of the 17 findings raised in the initial verification baseline.
07. Gaps, parked records and blocked procedures
The scan publishes what it landed, parked, excluded and could not verify. Missing sources and blocked procedures stay visible.
| Gap type | Count | Description | Next step |
|---|---|---|---|
| Parked AP invoices | 18 | Mapping discrepancy: vendor ID in invoice not in vendor master | Map vendor IDs in Mapping Studio; Inbox task assigned |
| Excluded AP invoices | 8 | Pre-period invoices (Dec 2023) outside scope | No action; will land in next period's scan |
| Blocked module | 1 | NetSuite AR not in scope | Add to scope for next scan or Proof of Value |
| Unavailable connector | 1 | Second bank account not configured | Configure connector when ready |
| Unresolved price drift | 1 | DRIFT-001: $72 unexplained difference | Investigator traces; query vendor if needed |
| Unresolved match gap | 1 | 3WM-001: $250 with no document, query to FreightCo | Investigator traces; Inbox approval required |
Illustrative. The zero-day scan never assumes an approval to get a clean tie-out. Parked and excluded records remain in the population with their reason and next step. Unresolved items stay separate from identified value.
08. Rerun history (after relevant syncs)
The scan repeats the tie-out after later syncs and remaps, preserving earlier results and showing whether a condition was resolved, changed or reopened.
| Rerun | Trigger | Landed change | Tie-out change | Findings change |
|---|---|---|---|---|
| 1 (initial) | Mapping approved | 10,325 records | All tied | 17 findings raised |
| 2 | Jan 15 Stripe sync | +12 settlements | Still tied | 0 new, 0 changed |
| 3 | Jan 20 NetSuite AP sync | +47 invoices, 3 parked resolved | Still tied | 2 new duplicates, 1 drift resolved |
Illustrative. Each rerun preserves the earlier completion summary and shows whether a condition was resolved, changed or reopened.