QuickBooks Financial Signals Library

Close & Data Integrity Signals

Every other signal in this library assumes the books beneath it are sound. These four signals test that assumption — and they're the ones auditors check first for the same reason.

4 signals · Last reviewed July 22, 2026

Data-integrity problems are quiet multipliers: an unreconciled account hides duplicates, an uncategorized pile makes every report wrong by its size, and a plug journal entry makes a real break invisible. None of them announce themselves; all of them are cheap to check on a schedule.

If review time is limited, this family comes first. Signals read from unsound books aren't signals — they're noise with confidence.

1.Reconciliation backlog

Bank or credit-card accounts going unreconciled past their statement cycle — or reconciliations completing only with growing adjustment plugs.

Why it matters

Reconciliation is the only process that proves the books match external reality. When it slips, everything downstream degrades at once: duplicates stop being catchable, feed errors accumulate, and the oldest unmatched items age toward unfindable. A reconciliation "completed" with a forced difference is a break recorded as a success.

Common causes

  • Staffing gaps or cadence loss during busy periods
  • Bank-feed breakages accumulating unmatched lines
  • Differences written off instead of investigated
  • New accounts never added to the reconciliation routine

QuickBooks records to pull

  • Reconciliation history and reports per account
  • The bank register
  • Bank-feed connection status and unmatched lines

How to investigate

  1. Review the last-reconciled date for every bank and card account.
  2. Flag any account more than one full statement cycle behind.
  3. Open recent reconciliation reports and look for forced adjustments or unexplained differences.
  4. Work the oldest unmatched items first — they're the ones about to become unreconstructable.
  5. Restore the cadence before relying on any other signal from that account.

False positives to rule out

  • Closed or dormant accounts — exclude them explicitly rather than skipping them silently

Questions to ask next

  • How many statements behind is each account, really?
  • Do recent reconciliations contain adjustment entries plugging differences?
  • Is the bank feed connected and healthy, or silently broken?

Illustrative example — not customer data

A card account last reconciled in March carries 210 unmatched feed lines by July. Inside them: two duplicate charges and a canceled-service autopay still drafting — $1,140 nobody caught, because "the feed does it automatically."

How Flash covers this signal

Flash watches last-reconciled ages and unmatched-line accumulation nightly and flags backlog before it compounds. The reconciliation itself — and the judgment in it — stays with your team.

Related: Month-end close: the daily review

2.Uncategorized transactions accumulating

Transactions piling up in Uncategorized Income, Uncategorized Expense, or ask-my-accountant style holding accounts.

Why it matters

Every report is wrong by the size of the pile — margins, spend by vendor, tax categories, all of it. Worse, the pile is where other problems hide: duplicates, personal charges on company cards, and misc errors all end up uncategorized, exempt from every review that filters by category.

Common causes

  • Bank-feed lines accepted without categorization
  • Uncertainty parked as uncategorized "for now" — permanently
  • Import and integration defaults dumping to holding accounts

QuickBooks records to pull

  • P&L and Balance Sheet uncategorized and suspense lines
  • QuickReports on each holding account
  • Bank-feed rules

How to investigate

  1. Run the P&L and Balance Sheet and note every uncategorized or suspense balance.
  2. QuickReport each holding account to see the transactions inside.
  3. Categorize oldest-first — the context needed to classify a transaction decays fast.
  4. Create bank rules for the recurring sources feeding the pile.
  5. Track the balance weekly, targeting near-zero at close.

False positives to rule out

  • Small transient balances mid-week — the signal is accumulation and age, not existence

Questions to ask next

  • Is the pile growing or shrinking week over week?
  • Which recurring source feeds it — and can a rule stop that?
  • Is anything inside it actually a duplicate or a personal charge?

Illustrative example — not customer data

Uncategorized Expense holds $12,400 across sixty transactions at close. Inside: one duplicate vendor payment, two personal charges on the company card, and $9,000 of ordinary spend that made three months of reports quietly wrong.

How Flash covers this signal

Flash monitors uncategorized and suspense balances nightly, flags growth and aging, and lists the largest uncategorized items in the morning brief. Categorization decisions stay with whoever knows the business.

Related: Daily QuickBooks review checklist

3.Unusual period-end journal entry

Manual journal entries appearing at period end — particularly round-number entries, entries touching cash or revenue, or entries posted by unexpected users.

Why it matters

Most journal entries are legitimate close mechanics: accruals, depreciation, documented corrections. But the manual period-end JE is also the classic mechanism for making a problem disappear instead of explaining it — which is why auditors read the journal first. A plug entry that forces agreement doesn't fix the underlying break; it just deletes the evidence that one exists.

Common causes

  • Normal recurring close entries — the common case
  • Late corrections of genuine errors
  • Balancing plugs posted to "make it tie"
  • Rarely: intentional manipulation of results

QuickBooks records to pull

  • The Journal report, filtered to manual entries
  • The audit log for preparer and timing
  • Supporting schedules and memos

How to investigate

  1. Run the Journal report for close week, filtered to manual journal entries.
  2. For each: confirm the preparer, the purpose, and that a supporting schedule or memo exists.
  3. Give extra attention to round numbers, entries touching cash or revenue, and reversals of previously flagged items.
  4. Verify recurring close entries — depreciation, accruals — still match their schedules.
  5. Treat any plug entry as an open item: investigate the underlying break it papered over.

False positives to rule out

  • Standard recurring close entries with documentation
  • Accountant-prepared adjustments with full support attached

Questions to ask next

  • Who posted it — and is that person expected to post entries?
  • Where is the supporting schedule?
  • Does any entry make a problem disappear rather than explain it?

Illustrative example — not customer data

Close week includes a $15,000 round-number entry crediting COGS, memo: "adjustment." No schedule attached. It made gross margin match forecast. The underlying break — a miscounted inventory receipt — surfaced in the next physical count, a quarter later and harder to unwind.

How Flash covers this signal

Flash reviews new journal entries nightly against the company's own entry patterns and flags off-pattern entries — unusual accounts, unusual timing, round numbers — as candidates for review. Judgment on every entry stays with your accountant.

Related: QuickBooks anomaly detection: a practical guide

4.Negative balance where none belongs

A balance running negative where the account's nature says it shouldn't — negative AR for a customer, negative AP for a vendor, negative inventory, negative undeposited funds.

Why it matters

Impossible balances are bookkeeping smoke detectors. Each one traces to a specific mechanical error — a payment applied to no invoice, a bill payment with no bill, inventory sold before it was received — and each error makes a set of reports unreliable until fixed. Some also carry a customer-relations cost: dunning customers who already paid because their payment was never applied.

Common causes

  • Customer payments recorded without being applied to invoices
  • Bill payments recorded without bills
  • Inventory sold in the system before being received in the system
  • Deleted transactions leaving orphaned links

QuickBooks records to pull

  • Balance Sheet, scanned for sign anomalies
  • A/R and A/P aging reports — negative rows
  • Customer and Vendor Balance Detail
  • Inventory valuation where applicable

How to investigate

  1. Scan the Balance Sheet for balances with the wrong sign for their account type.
  2. Run A/R and A/P aging sorted ascending — negatives float to the top.
  3. For each: open Balance Detail and find the unapplied or orphaned transaction.
  4. Apply payments to their invoices and bills — or investigate why no matching document exists; sometimes the answer is a duplicate payment.
  5. For inventory negatives, fix receipt timing and quantities rather than adjusting the count blind.

False positives to rule out

  • Legitimate customer prepayments and deposits — cleaner in a liability account, but not errors
  • Vendor credits correctly awaiting the next bill

Questions to ask next

  • Prepayment or error?
  • Which specific transaction is unapplied or orphaned?
  • Does the negative trace back to a duplicate or a deletion?

Illustrative example — not customer data

Three customers show negative AR totaling $7,700. Two are payments never applied to their invoices — invoices that still show open and are being dunned, annoying customers who already paid. The third is a genuine prepayment that belongs in a deposit liability.

How Flash covers this signal

Flash scans for sign anomalies across AR, AP, and balance accounts every night and flags each with the underlying record attached. Fixes are applied by your team, in QuickBooks, with full context.

Related: Overpayment or unapplied vendor credit