NetSuite Development / Finance Controls

NetSuite Processing Health:
Did Everything That Should Happen Actually Happen?

Automated processing creates transactions. Finance still needs a way to verify what happened, investigate what is missing, and document what was reviewed. A closer look at the Processing Health dashboard inside a custom NetSuite Tenant Lease application.

(724) 816-1000 • Work directly with Jack Ring.

A scheduled process finishes. There are no obvious errors. But did every eligible lease obligation produce its expected Sales Order? Was the remaining quantity billed, and are the related recognition and deferral journals linked?

I built the Tenant Lease Processing Health dashboard to give Finance a practical way to investigate those questions through a selected accounting period.

The Tenant Lease application manages lease records, schedule lines, and related NetSuite transactions. Those relationships give us a basis for checking processing evidence. A schedule line establishes an obligation to examine. The related order, billed quantity, fulfillment, and journal links help explain what happened next.

That distinction matters when reviewing automation. A completed script execution tells us that a program finished running. Finance also needs visibility into the business records that should have resulted from that processing.

The question behind Processing Health:
For the obligations we know about through this accounting period, where does the expected processing evidence need attention?

Start with what should have happened.

A useful exception dashboard needs a defined population. Otherwise, a missing transaction may be indistinguishable from a transaction that was never expected.

Here, the review begins with active schedule lines on active Tenant Leases. The lease must have started by the end of the selected As-of Accounting Period, and the schedule line’s accounting period must fall through that same boundary.

The As-of Period is cumulative. Selecting September means examining eligible obligations through September, including earlier obligations that still have findings. It does not limit the review to September activity alone.

Give historical processing an intentional starting point.

A lease can also have a Processing Start Period. Schedule lines before that boundary are excluded from the obligation population. This is useful when a lease contains historical schedules from before the application became responsible for processing them.

For example, if a lease begins dashboard processing in September, an older schedule line from the previous year falls outside that review scope. A September line can qualify. Without a Processing Start Period, that additional lower boundary does not apply.

The dashboard displays the number of eligible leases and schedule lines so Finance can understand the population being evaluated before interpreting the exceptions.

Follow the transaction evidence.

The dashboard groups findings into categories that point the reviewer toward a specific processing question. Expanding a lease exposes its findings and supporting record links, so the investigation can continue in NetSuite.

FindingWhat needs attention
Missing Sales OrdersAn eligible schedule line has no related Sales Order, or the recorded order lacks a corroborating line tied to that schedule obligation.
Billing ExceptionsA corroborated Sales Order line has a positive remaining quantity after comparing ordered quantity with quantity billed.
Missing RecognitionFor an owned lease, a fulfillment through the selected period has no related recognition journal recorded in the application’s link field.
Missing DeferralAn owned-lease invoice through the selected period has no related deferral journal recorded in the application’s link field.
Potential Duplicate Schedule LinesMultiple eligible schedule lines share the same lease, obligation period, and item, requiring review of the intended schedule.

Each category has a specific evidentiary meaning. A blank journal link does not establish that no journal exists anywhere in the account. Finance may need to inspect a separately posted journal and determine whether the application’s relationship is missing or further action is required.

Likewise, two schedule lines sharing a lease, period, and item are a review signal. Their quantities, rates, and intended source obligations still need examination before anyone concludes that one should be removed.

Use the right unit of review.

Most findings attach to a lease schedule line. Missing Deferral is evaluated at the invoice level and can appear even without an eligible schedule line in the dashboard population. A schedule line can also have several findings, including multiple fulfillment findings.

That affects how the totals should be read. Category tiles count active, unaccepted exception rows. A single schedule line can appear in several categories, and its expanded row can contain more than one selectable finding. Adding all the tiles together would overstate the number of distinct obligations.

Put exceptions in their accounting context.

Finance needs to know whether an exception relates to current activity, an earlier open period, or a closed period. Those distinctions influence investigation and how any correction should be handled under the company’s accounting policies.

Processing Health gives earlier open-period findings and closed-period findings their own views. They classify the underlying findings rather than creating a separate set of processing failures.

The relevant period follows the evidence. Schedule findings use the schedule obligation period. Recognition findings use the fulfillment posting period. Deferral findings use the invoice posting period. A schedule row with findings in different periods can therefore appear in both the prior-period and closed-period views.

A closed-period finding makes an unresolved condition visible. It does not authorize reopening a period or changing a posted transaction. The responsible Finance team determines the appropriate disposition.

Move from the overview to a manageable review.

Category selection, lease, period, and reason filters help narrow the visible findings. The category totals retain their broader meaning even when a dropdown reduces the displayed detail. Pagination and transaction links let the reviewer work through the population without losing the connection to source records.

The page uses a snapshot of the calculated findings. Refreshing or changing the As-of Period recalculates that view. Excel exports are calculated separately, so a refreshed dashboard is the appropriate comparison when reviewing an export against the screen.

Make the review part of the application.

Finding an exception is only the beginning. Finance needs a way to inspect the evidence, determine what action is appropriate, and retain the reasoning behind that decision.

Some findings require source corrections. Others may have a supportable explanation that requires no further action. Processing Health lets Finance record acceptance of an individual finding with a required note.

  1. Inspect the finding. Expand the lease and follow the relevant schedule, order, fulfillment, invoice, or journal evidence.
  2. Determine the disposition. Correct the source records when appropriate, or establish why the detected condition requires no further action.
  3. Document an acceptance. Select the individual finding and enter a Finance note explaining the evidence reviewed and the decision.
  4. Retain the review. The application stores the finding identity, evidence snapshot, note, reviewer, and acceptance time.

Selection can span leases and pages, with up to 20 findings in one submission. Before saving an acceptance, the server recalculates the candidate findings and checks that the evidence still matches. Findings that changed or were already accepted can be skipped, with feedback to the reviewer.

Acceptance records a Finance decision. It suppresses the matching finding from the active queue. It does not create an invoice, post a journal, correct a transaction, or establish formal period sign-off.

A useful review note explains the decision well enough for someone else to understand it later. "Reviewed" provides little context. A note identifying the supporting record and why no further processing is required gives the next reviewer something concrete to evaluate.

Let changed evidence bring a finding back.

A review decision depends on the evidence available when it was made. If that evidence changes, the application needs a way to recognize that the earlier acceptance may no longer apply.

Each accepted finding is tied to an evidence-specific key. Changes to included quantities, transaction links, matching order lines, or other checked evidence can produce a new key and return a finding to the active queue.

This operates at the individual finding level. Accepting one issue on a schedule line does not clear every issue associated with that line. Each accepted finding retains its own evidence and review record.

Review History is available independently of the active queue. It distinguishes accepted findings from reviews whose evidence changed, findings no longer detected, and reviews reopened by Finance. Authorized reviewers can update an acceptance note or reopen an accepted finding with a reason, while retaining the corresponding review information.

The result is a review process that responds to changes in the application’s records. Finance can explain both the original decision and why a condition needs another look.

Be explicit about what the dashboard can establish.

The dashboard evaluates Tenant Lease records and transaction evidence already present in NetSuite. It cannot identify an upstream lease or schedule obligation that never arrived unless there is an independent comparison against the source.

For that reason, the application intentionally reports Source Completeness: Unknown. A clean exception queue does not prove that every source record reached NetSuite, that every accounting entry is correct, or that the period is ready for sign-off.

A future comparison against authoritative upstream lease and schedule data could add another control by flagging potentially missing records. That comparison is separate work and is not part of the current dashboard.

Clear boundaries help Finance interpret the results properly. The dashboard provides defined checks, accessible evidence, and documented review decisions within its stated coverage.

Build verification into the application.

The Tenant Lease example brings together several practical design decisions: define the obligations, examine related processing evidence, classify findings by accounting period, and provide a review process that can respond when evidence changes.

The same approach can inform other custom NetSuite applications. Where a process is expected to produce a business result, there is value in defining how the responsible team will inspect that result and investigate exceptions.

I build NetSuite applications with the expectation that someone will need to explain their results. That means making exceptions visible, connecting them to supporting records, and giving the responsible people a practical way to document their decisions.

Can your team explain what happened?

If your NetSuite environment relies on custom processing, a useful starting question is how your team verifies the expected results and investigates what remains unresolved.

I help companies already running Oracle NetSuite, or in the midst of an implementation, regain operational clarity, financial trust, and process control across the ERP environment.

Independent. No license reselling. No partner quotas. No layers of project management. Clients work directly with a NetSuite ERP soloist focused on how the system actually behaves inside day-to-day operations.

Jack Ring • Left Ledger Inc.
Jack@LeftLedger.com
724-816-1000

Call Jack: (724) 816-1000 Send a message