NetSuite rejects imbalanced transactions; persistence = integration logic broken on the calling side.
At a glance
Transaction Imbalances is a gl health metric tracked from NetSuite data. It surfaces operational signal so you can spot regressions, opportunities, and structural patterns. Cross-reference the sibling cards below for the full diagnostic picture.
| What it counts | NetSuite rejects imbalanced transactions; persistence = integration logic broken on the calling side. |
| Sample type | Backend API data from NetSuite, refreshed on the standard data refresh. |
| Why it matters | The metric appears in the GL Health category and complements the sibling cards listed below. Track movement over time to identify regressions or opportunities. |
| Reading the value | Compare the current period to the prior period to read direction. Cross-reference siblings to triangulate cause. |
| Format | number |
| Time window | RT |
| Alert trigger | >0 |
| Sentiment key | erp_journal_imbalance_count |
| Roles | owner, finance, engineering |
Calculation
Calculated automatically from your NetSuite data on the standard refresh. See the At a glance summary for what it tracks and the worked example below for a typical reading.Worked example
A representative reading of Transaction Imbalances for a typical NetSuite account. The card reports the current value alongside a comparison against the previous period — direction matters. When it moves outside the expected range, cross-reference the siblings below to find the cause; use Vortex Mind to trace upstream causes and Ask Viq for natural-language exploration.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
ns_manual_journal_pct | GL Health sibling: Manual Journal Entries as % of Total. |
ns_suitescript_error_count | GL Health sibling: SuiteScript Execution Errors (24h). |
ns_saved_search_timeout_rate | GL Health sibling: Saved Search Timeout Rate (24h). |
ns_journals_by_type | GL Health sibling: Transactions by Type. |