Findings

Every record, one screen.
Filter by subsidiary. Sort by impact. Fix without leaving.

Click a failing row on the dashboard and Sentry loads every affected record into a single paginated table. Element IDs link back to NetSuite. Click a subsidiary in the impact chart to scope the table to that entity. No tab-switching, no saved search exports.

← Dashboard/Rev Element Dates Off Source
Last run 08:42 PST·ARM updated 07:15 PST
Critical · Close blockerClose-readiness
Revenue Elements with Mismatched Dates
Element start/end dates don't match the source transaction's revenue period. Recognition won't post until corrected.
Revenue impact
$12.4M
Records
1,359
Subsidiaries affected
3 of 33
Concentration
92%
in top 5 subs
Proposed fix
Correct the dates directly on the element. If dates keep reverting, enable “Automatically Update Target Field Value” on the rev rec rule so changes to the source flow through.
Ranked by impactClick a row to filter
Cascade Industries
$8.2M
412
Boreal Systems
$5.1M
318
Pacific Wire & Cable
$4.8M
287
Summit Digital
$2.4M
183
Redstone Mfg
$1.6M
112
Filter
⌕
All 33 subsidiaries · showing 6 of 6
Element ▼ArrangementSubsidiaryElement startSource startDeltaAllocation
ELEM-88214RA-004281Cascade Industries2026-01-152026-02-01-17d$185,000.00
ELEM-88215RA-004281Cascade Industries2026-01-152026-02-01-17d$94,500.00
ELEM-88902RA-004455Boreal Systems2026-02-012026-03-01-28d$82,300.00
ELEM-89044RA-004512Pacific Wire & Cable2025-12-152026-01-01-17d$48,000.00
ELEM-89101RA-004612Cascade Industries2026-01-012026-02-14-44d$40,000.00
ELEM-89322RA-004701Summit Digital2025-11-012025-12-01-30d$33,200.00
← PrevPage 1 of 28Next →
Export CSVBack to dashboard
One screen, not five

The findings page is the whole workflow.

Without Sentry
With Sentry
Saved search
Results1,359 rows
Exported toExcel
open arrangement
Revenue arrangement
RA-4281$279,500
open element
Revenue element
RE-8214$185,000
Start date2026-01-15
open plan
Revenue plan
RP-4412Bal. $185,000
find the source
Source transaction
SO-1048Cascade Ind.
Rev start2026-02-01
Repeat for 1,358 more records
×No dollar impact visible
×No subsidiary rollup
×No proposed fix
×No audit trail
← Dashboard/Rev element dates off source
CriticalClose-readiness
Impact
$12.4M
Records
1,359
Subs
3 of 33
Top 5
92%
Ranked by impact
Cascade
$8.2M
Boreal
$5.1M
Pacific
$4.8M
Element ▼Arr.SourceSrc startDeltaAllocation
RE-8214RA-4281SO-10482026-02-01-17d$185,000
RE-8215RA-4281SO-10482026-02-01-17d$94,500
RE-8902RA-4455SO-10582026-03-01-28d$82,300
RE-9044RA-4512SO-10642026-01-01-17d$48,000
RE-9101RA-4612SO-10712026-02-14-44d$40,000
Page 1 of 28
Export CSVBack to dashboard
Subsidiary scoping

33 subsidiaries. One click to see just yours.

The “Ranked by impact” chart is interactive. Click Cascade Industries and the table, stat cards, and record count all re-scope to that entity. The filter persists when you navigate to other pages, and exports reflect whatever scope is active.

Click to filter
Select a subsidiary in the impact chart. The whole page re-scopes: rows, totals, record count.
Scope persists
Filter on the dashboard, drill into a finding, and the subsidiary selection carries over.
Scoped exports
CSV and XLSX include only the records visible under the current filter. Not the full population.
Proposed fix

The answer ships with the finding.

Most governance tools tell you something failed. They don't tell you what to do about it. Sentry ships a three-part narrative with every finding: what to look for in the data, why the mismatch matters for recognition, and the specific steps to resolve it.

The narrative appears on the findings page itself. You read it before you open a single record. If the fix is mechanical, like completing plans with zero remaining balance, Sentry can apply the change in bulk.

01
What to look for
The specific data pattern this finding targets
02
Why it matters
The recognition or compliance consequence
03
How to fix it
The record-level steps to resolve the mismatch
CriticalClose-readiness
Rev Element Dates Off Source
What to look for

Revenue elements where the start or end date doesn't match the corresponding date on the source transaction. Common when sales orders are amended after the arrangement was created.

Why it matters

When element dates don't match the source, revenue gets recognized against the wrong periods. There's no single source of truth for the revenue start, so the close team manually cross-references two records every time.

How to fix it

Correct the dates directly on the revenue element to match the source transaction. If dates keep reverting after amendment, enable “Automatically Update Target Field Value” on the revenue recognition rule.

See your findings on your sandbox.

30-minute walkthrough. Your subsidiaries, your data, your actual ARM records.

Book a Demo

No commitment. One business day response.