QuickBooks Financial Signals Library
Revenue & Margin Signals
Revenue problems discovered at close are four weeks old on arrival. These four signals surface the same problems while the month is still open — when invoicing lags are fixable and pricing conversations are current.
4 signals · Last reviewed July 22, 2026
Top-line review inside the month asks different questions than the P&L answers at close: is revenue tracking the company's own pattern for this point in the month? Is the margin behind it holding? Are credits and refunds telling an operational story? And is everything that was delivered actually invoiced?
Every one of those questions is answerable from QuickBooks data that already exists. The signals below give each one a concrete review procedure.
1.Revenue dip against pattern
Revenue running below what your own weekly and monthly pattern predicts — after the seasonality you already know about is accounted for.
Why it matters
A dip discovered at close is a historical fact; the same dip discovered mid-month is an open question with fixable answers. The causes split into two categories with opposite responses: paperwork problems (invoicing running behind the work) and demand problems (fewer or smaller sales) — and the ledger can tell you which one you have.
Common causes
- Invoicing lagging behind delivered work — revenue exists, paper doesn't
- Genuine demand softening in a product or channel
- A channel or integration quietly breaking
- A lost customer nobody has noticed yet
QuickBooks records to pull
- Sales by Customer Summary and Sales by Product/Service Summary
- Invoice dates against delivery dates
- P&L month-over-month comparison
How to investigate
- Compare month-to-date revenue against the same day of month in prior periods — not against the full prior month.
- Split any gap three ways: fewer invoices, smaller invoices, or later invoices?
- If later: fix the invoicing lag this week — that revenue already exists.
- If fewer or smaller: identify which specific customers and products carry the gap.
- Route the finding to its owner — billing lag to ops, demand softness to sales — with the specific accounts attached.
False positives to rule out
- Calendar effects — five-week months, holiday timing
- One large deal that landed in this window last year and isn't recurring
Questions to ask next
- Is this timing or volume?
- Which customers and products specifically carry the gap?
- Is anything delivered but not yet invoiced?
Illustrative example — not customer data
Month-to-date revenue is 18% behind pattern on the 20th. The split: invoice count normal, average size normal — but $31,000 of completed project work simply hasn't been invoiced. The "dip" was paperwork, and it was fixed in two days.
How Flash covers this signal
Flash tracks revenue daily against the company's own patterns and flags dips in the morning brief with the composition attached — count, size, and timing — so the first hour of investigation is already done.
2.Margin compression
Gross margin percentage drifting down while revenue holds — costs rising inside stable prices.
Why it matters
Compression compounds silently: two points a quarter is eight points a year, and by the time an annual review catches it, the pricing conversation is a year late. Because revenue can grow right through it, the companies most at risk are often the ones that feel like they're doing well.
Common causes
- Input cost increases absorbed instead of passed through
- Mix shifting toward lower-margin products or customers
- Discounting creep — exceptions hardening into practice
- Miscategorized COGS making real margin unreadable
QuickBooks records to pull
- P&L with % of income columns, month over month
- Sales by Product/Service Summary with margins
- COGS account detail
How to investigate
- Run the P&L in monthly columns with % of income displayed, and track gross margin per month.
- Flag drift of more than a point or two sustained across two to three months.
- Check categorization first — an expense keyed into COGS, or COGS keyed into expenses, fakes compression in either direction.
- Decompose the real drift: price, cost, or mix, by comparing per-product margins across periods.
- Route the actual driver: pricing review, vendor renegotiation, or mix strategy.
False positives to rule out
- Mix effects from one large low-margin project passing through
- A categorization change mid-year making periods non-comparable
- Seasonal input pricing the baseline should include
Questions to ask next
- Price, cost, or mix?
- Is categorization consistent across the periods being compared?
- Which specific products or customers compress the most?
Illustrative example — not customer data
Gross margin slides from 41% to 36% across four months while revenue grows. The decomposition: freight surcharges absorbed since spring and never passed through. Growth was hiding the leak — the percentage column had been reporting it the whole time.
How Flash covers this signal
Flash watches margin trend against the company's own history nightly and flags sustained compression in the morning brief. Pricing decisions stay human; the drift stops being invisible.
Related: QuickBooks Reporting Automation
3.Refund and credit-memo cluster
Refunds and credit memos clustering — in count or dollars — above your norm, or concentrating in one product, customer, or period.
Why it matters
Credit memos are where three different problems surface first: quality issues (customers returning or rejecting work), billing accuracy (corrections walking back errors), and control gaps (concessions nobody authorized). The returns data usually knows about an operational problem weeks before the operational team formally does.
Common causes
- Quality or fulfillment issues driving returns
- Billing errors requiring correction after the fact
- Aggressive invoicing quietly walked back
- Concessions granted outside policy
QuickBooks records to pull
- Credit memos and refund receipts — Transaction List by Type
- The invoices each credit links to
- Per-customer and per-product credit totals
How to investigate
- Run credit memos and refunds for the trailing 90 days using Transaction List filtered by type.
- Compare count and dollars against your norm for a comparable period.
- Group by customer, by product, and by who created them.
- For any cluster: trace to the root cause — quality, billing accuracy, or concession practice.
- Verify authorization on the largest items individually.
False positives to rule out
- Seasonal returns — retail January looks alarming every year
- A single well-understood correction or recall event
Questions to ask next
- Is the cluster concentrated in a product, a customer, or a person?
- Is the root cause operational or billing?
- Was each large credit properly authorized?
Illustrative example — not customer data
Credit memos triple in June. Grouped, 80% trace to one product's May production batch — a quality issue the returns data identified three weeks before the ops team formally did.
How Flash covers this signal
Flash reviews credit and refund patterns nightly and flags clusters in the morning brief with the grouping already done — by product, customer, and creator. Root-cause and policy decisions stay with your team.
Related: Revenue dip against pattern
4.Billing gap: delivered but uninvoiced
Work completed or goods shipped without a corresponding invoice inside your billing cycle.
Why it matters
This is the cheapest cash improvement that exists: the work is done, the customer expects the bill, and every uninvoiced week is an interest-free loan to them. It's also a dispute risk that grows with time — invoices sent months after delivery get questioned; invoices sent days after delivery get paid.
Common causes
- A handoff gap between delivery and billing
- Milestone completion never communicated to whoever invoices
- Time and expenses accumulating unbilled in project tracking
- A billing backlog treated as harmless
QuickBooks records to pull
- Estimates and their invoice status
- Delivery or completion records against invoices raised
- Unbilled time and expense reports where used
How to investigate
- List completed work and shipments for the period from your operational source of truth.
- Match each against invoices raised in QuickBooks.
- Flag gaps older than your billing cycle.
- Invoice the backlog this week, dated honestly.
- Fix the handoff that dropped it — a recurring gap is a process problem, not an accident.
False positives to rule out
- Contractual billing schedules — the milestone genuinely isn't due yet
- Retainers that already cover the delivered work
Questions to ask next
- How many days pass between delivery and invoice, on average?
- Where exactly does the handoff drop — and who owns that step?
- What is the dollar backlog right now?
Illustrative example — not customer data
A services firm audits the quarter: $54,000 of completed project work never invoiced — three projects each "waiting on final sign-off" that clients had verbally accepted weeks earlier. The invoices went out Friday; two were paid inside a month.
How Flash covers this signal
Flash flags the patterns visible inside QuickBooks — accepted estimates without invoices, unusual gaps between sales activity and billing — as candidates in the morning brief. Work tracked outside QuickBooks still needs the operational comparison; Flash makes sure the in-ledger half never goes unwatched.
Related: QuickBooks Open Invoice Insights
Run these checks by hand — or wake up to them done
Everything above works with nothing but QuickBooks and a schedule. Flash Daily Insights runs the same comparisons nightly through a read-only connection and delivers the candidates in a morning brief — what changed, what looks wrong, what to do next. It never changes your books.