Automated Resolution · Now live in Sentry

Fix ARM findings without leaving Sentry.

Click a finding, pick a route, preview every period change, hit Confirm. Sentry runs the fix through NetSuite's APIs and writes the audit trail. The same governance you'd do by hand, in four seconds instead of forty minutes.

netsuite.com/app/site/hosting/scriptlet.nl
Fictional data
Dashboard›Date mismatch: element vs source
Date mismatch: element vs sourceHigh
Revenue element dates don't match the source transaction. Plans derived from these elements recognize over the wrong period.
5
mismatches
$318K
total plan value
3
subsidiaries
Affected records
PlanItemElement datesSource datesDelta
RP-48291
Cascade Industries
CloudSync Platform LicenseJan – Dec 2026Mar 2026 – Feb 20272 mo earlyResolve
RP-48305
Cascade Industries
CloudSync Support AnnualJan – Dec 2026Mar 2026 – Feb 20272 mo earlyResolve
RP-49012
Boreal Systems
DataVault EnterpriseFeb 2026 – Jan 2027Apr 2026 – Mar 20272 mo earlyResolve
RP-49200
Pacific Wire & Cable
Network Monitor ProJan – Nov 2026Jan – Dec 20261 mo shortResolve
RP-50010
Summit Digital GmbH
SecureCloud BaseMar 2026 – Feb 2027Apr 2026 – Mar 20271 mo earlyResolve
Resolve date mismatch
RP-48291 · CloudSync Platform License · Cascade Industries
Fix
Mark expected
RP-48291 redistributed · awaiting approval
The loop, before and after

Close work is loops inside loops inside NetSuite.

The manual version is find it, open it, check the source, fix it, re-run ARM, log it. Five screens and a spreadsheet. Sentry collapses that loop into one surface, with the audit log written for you.

Today

The loop between finding and fix

1Run a saved search to find mismatches6 – 15 min
2Open the plan in NetSuite2 min per record
3Check the source transaction in another tab3 min per record
4Hold recognition, update dates, release hold5 min per record
5Re-run ARM to confirm it posted10 min + wait
6Log it in a spreadsheet for the binderper record
For 50 findings: ~ 14 hours of manual work across multiple screens. Then someone has to review it.
With Sentry

Same loop. One surface. Audit-ready.

1Check run surfaces every mismatch with dollar impactinstant
2Click the row, review source vs. element side by side5 sec
3Pick a route, preview every period change10 sec
4Confirm. Snapshot, hold, save, release, audit. All automatic2 – 4 sec
5Row updates to Resolved with the full audit trailinstant
For 50 findings: ~ 25 minutes from open to audit trail. Reviewer signs off on the log.
The catalog

Date mismatch is one check. The catalog grows with every close.

Every time we find a new failure pattern during an engagement, it becomes a check. Some checks only surface the issue. Others come with a one-click fix. The ones below have automated resolution built in.

High severity

Element dates drift from the source transaction

The problem

Revenue recognized over the wrong period because the element's start/end dates don't match the sales order or invoice they came from.

What Sentry does

Redistribute the plan to the source dates. Recognized periods stay locked; remaining balance redistributes with an adjustment line inserted where recognition has already posted.

Date mismatch3 affected
PlanDeltaAction
RP-482912 mo earlyRedistribute
RP-490122 mo earlyRedistribute
RP-500101 mo earlyRedistribute
One-click resolve · Preparer/Reviewer loggedApply 3
More resolution routes are added as new checks ship. The ones above are live today.
Under the hood

What Sentry actually does when you click Confirm

The fix runs through NetSuite's own SuiteScript APIs. No middleware, no external service. Every step is replayable from the audit record.

Snapshot
Plan state serialized to audit record
Hold recognition
Prevents the 3-hour ARM job from racing the save
Save end date
Isolated call so End Date Change Impact rule fires
Rewrite schedule
Unrecognized lines updated; adjustment line inserted where needed
Release hold
Plan returns to live
Audit entry
Before/after snapshot, user, timestamp
Typical runtime
2 – 4 sec
Concurrency
Single-record, serialized per plan
Failure mode
Full rollback, FIX_FAILED audit entry
The audit trail

Every action lands in the audit log before the next one fires.

Preparer and reviewer are separate entries with separate timestamps. System actions are separate from user actions. Export the log to CSV for the close binder. Filter by plan, by user, by date.

User actions and system actions logged separately
Before / after snapshot attached to every fix
Preparer and reviewer must be different users
Exportable as CSV, filterable by record or user
customrecord_vcg_sentry_audittail -f
14:32:07PreparerSarah M.CONFIRMEDRP-48291 redistribute
14:32:08SystemSentrySNAPSHOT_SAVEDPlan state serialized
14:32:08SystemSentryHOLD_ONholdrevenuerecognition=true
14:32:09SystemSentryEND_DATE_SAVEDec 2026 → Feb 2027
14:32:10SystemSentryLINES_UPDATED9 modified, 1 adj inserted
14:32:11SystemSentryHOLD_OFFholdrevenuerecognition=false
14:32:11SystemSentryFIX_APPLIEDException → REVIEWED
15:18:44ReviewerLeon P.APPROVEDRP-48291 redistribute
Governance

Automation that your controller, auditor, and CFO can all live with.

Every fix Sentry runs respects the same controls a human would. Snapshot, hold, serialize, release, audit. If any step fails, nothing persists. If any step succeeds, every detail is on the record.

Snapshot before every change
Sentry serializes the plan's state into the audit record before the first write. If something goes sideways, the before state is there to compare to.
Preparer / Reviewer separation
The person who clicks Resolve is the preparer. The exception moves to Reviewed, awaiting a second person's approval. One user can't fix and approve their own work.
Rollback on failure
Any save error, governance limit, or locked period triggers a full rollback. The hold is released, a FIX_FAILED entry goes into the audit, and the plan stays in its original state.
Locked periods respected
If any target period falls in an AR-locked accounting period and the user doesn't have override, Sentry flags it before the preview renders. The fix button stays disabled until the period is unlocked.
Concurrent edit detection
If another user touched the plan between when you opened the panel and when you clicked Confirm, Sentry re-reads the plan, sees the drift, and aborts with a message to reopen.
Dismiss path for intentional overrides
Not every finding needs a fix. Custom deal terms, source wrong and fixed separately, under investigation. Mark it expected with a reason and a comment. It moves to Reviewed, not deleted.
Ready when you are

See what Resolve looks like against your own data.

We install Sentry in your sandbox, run the checks against your ARM records, and walk you through a live fix. 45 minutes. No commitment.

Runs inside NetSuite · No external servers · Installed in 20 minutes