QuickBooks Financial Signals Library
Accounts Payable & Vendor Signals
The payables side is where errors and fraud have the same fingerprint: money moving to the wrong place for plausible-looking reasons. These four signals separate the plausible from the verified.
4 signals · Last reviewed July 22, 2026
AP review answers two different questions at once. The control question: is every payment going to a real vendor for a real obligation at the right amount? The operating question: is the payables position — aging, concentration, terms — one you chose, or one that happened to you?
Both questions are answerable from standard QuickBooks reports. The signals below cover the four patterns most worth a scheduled look.
1.Vendor spend spike
Spending with one vendor jumping meaningfully above that vendor's own history.
Why it matters
A spike is a bundle of possibilities that all deserve different responses: a keying error you can fix in minutes, a duplicate bill you can dispute, a price increase nobody approved, scope creep nobody signed, or a legitimate project. The only wrong response is not opening the bundle — and disputes get harder with every week of delay.
Common causes
- A price increase applied without notice
- Quantity or scope creep on an ongoing service
- Duplicate invoices inside the period
- A keying error on amount
- A legitimate one-time project or purchase
QuickBooks records to pull
- Expenses by Vendor Summary, period over period
- The bills behind the spiking vendor
- Contracts, quotes, and receiving records
How to investigate
- Run Expenses by Vendor Summary for this period against the trailing average.
- Flag vendors meaningfully above their own norm — 50% is a workable starting line to tune.
- Open the bills behind each spike.
- Verify pricing against the contract or quote, quantities against receipts, and scan for duplicates inside the spike.
- Dispute, correct, or approve — explicitly, so the new level is a decision rather than a drift.
False positives to rule out
- Known seasonal vendors — shipping in Q4, landscaping in spring
- Planned projects and one-time purchases
- New vendors ramping with no history to compare against
Questions to ask next
- Is there a contract or quote supporting the new level?
- Are there duplicate bills inside the spike?
- Who approved the increase — or did anyone?
Illustrative example — not customer data
A janitorial vendor at roughly $900 a month bills $2,700 in June. Inside it: June's bill, May's bill re-sent as "unpaid per our records" (already paid), and a rate increase that was never announced. Two of the three were disputable — for about three more weeks.
How Flash covers this signal
Flash compares each vendor's activity against their own history every night and flags spend spikes in the morning brief with the underlying bills attached. Disputes and approvals stay with your team.
2.New vendor, large first payment
A vendor record created recently whose first — or early — payment is large by your company's standards.
Why it matters
Vendor onboarding is where payment fraud actually happens: fake-vendor schemes and bank-detail manipulation both depend on a new or newly-edited record receiving money before anyone looks closely. It's also where honest duplicates begin, when an existing vendor gets re-created instead of found. Most new vendors are legitimate; the point of the signal is that verifying takes one phone call, and skipping the call is how the exceptions get through.
Common causes
- A legitimate new relationship — the common case
- A fake or manipulated vendor record directing funds outward
- An existing vendor re-created as a near-duplicate record
QuickBooks records to pull
- The vendor list with record-creation dates
- Bills and payments for recently created vendors
- Onboarding documents — W-9, bank details, approvals
How to investigate
- List vendor records created in the last 30–60 days.
- Flag those whose early payments exceed your materiality line.
- For each: verify onboarding documents exist, and that the person who requested the vendor and the person who approved payment are different people.
- Check the new record isn't a near-duplicate of an existing vendor.
- For any bank-detail change on an existing vendor, verify by a known-good phone number — never by replying to the email that requested the change.
False positives to rule out
- A new legal entity of an existing relationship — rebrand, acquisition
- Genuinely urgent onboarding with the paperwork following
Questions to ask next
- Who created the record, who approved the payment, and are they different people?
- Were bank details verified through an independent channel?
- Is this actually an existing vendor under a new name?
Illustrative example — not customer data
A vendor created on the 3rd receives $9,200 on the 9th. Documents exist, but the requester and approver are the same person, and the remittance address matches nothing public about the company. This one was legitimate — a phone call proved it in five minutes. The cases that aren't legitimate look identical until that call.
How Flash covers this signal
Flash flags new-vendor and first-payment patterns nightly in the morning brief so the verification call happens before the exposure grows. It reads the records; it cannot hold or release payments.
Related: Duplicate vendor records
3.AP aging past terms
Your own payables aging past vendor terms — the mirror image of AR aging, read from the vendor's side of your books.
Why it matters
Late AP costs real money — late fees, lost early-payment discounts, and eventually worse pricing and prepayment demands from vendors who've repriced you as a risk. When the lateness isn't a deliberate cash decision, it signals process breakdown: bills stuck in approval, lost invoices, unresolved disputes aging in place.
Common causes
- Deliberate cash preservation — fine when it's explicit
- Bills stuck in an approval step nobody is watching
- Invoices entered late, aging instantly on arrival
- Disputes that were never resolved, just abandoned
QuickBooks records to pull
- A/P Aging Summary and Detail
- The bill approval queue
- Vendor statements
How to investigate
- Run A/P Aging Summary.
- Separate strategic lateness — chosen and known — from process lateness that nobody decided.
- Drill into 31-plus-day items: approval status, dispute status, statement match.
- Reconcile against vendor statements quarterly; the same pass catches missing bills and duplicate bills at once.
- Pay or schedule each item explicitly, so the aging position becomes a decision again.
False positives to rule out
- Disputed bills correctly held pending resolution
- Renegotiated terms that were never updated in QuickBooks
Questions to ask next
- Is this lateness chosen or stuck?
- What are late fees and lost discounts actually costing per month?
- Which vendor relationships are being repriced by our payment behavior?
Illustrative example — not customer data
The 31–60 bucket doubles across a quarter. Nobody decided to pay slower — a new approval step quietly added four days per bill, and the two largest vendors have started requiring prepayment. The books recorded the drift in real time; nobody was reading that page.
How Flash covers this signal
Flash watches AP aging against terms nightly, separates the trend by vendor, and flags fee exposure and aging drift in the morning brief. Payment decisions remain entirely yours.
Related: QuickBooks AP & AR Aging Insights
4.Vendor concentration
A large share of operating spend flowing through one or a few vendors.
Why it matters
Concentration hands pricing power to the vendor and concentrates operational risk in their continuity. The cash dimension is the sharp one: if a dominant vendor moved you from net-45 to prepayment tomorrow — after an acquisition, a credit review, a bad quarter on their side — the working-capital hole arrives on their schedule, not yours.
Common causes
- Single-sourcing for convenience that compounded over time
- Niche dependencies with no developed alternative
- Vendor consolidation nobody revisited
QuickBooks records to pull
- Expenses by Vendor Summary, trailing twelve months
- Contracts and current terms
How to investigate
- Run Expenses by Vendor Summary for the trailing twelve months.
- Compute each top vendor's share of total spend, judging structural categories like rent separately.
- Flag single-vendor shares above roughly 20–25% of operating spend.
- For each flagged vendor: document the switching cost, a validated alternative, and the cash impact if terms changed to prepay tomorrow.
- Revisit quarterly — concentration is a drift metric.
False positives to rule out
- Structural vendors — landlord, insurer — where concentration is the nature of the category
Questions to ask next
- What happens to the cash calendar if this vendor required prepayment tomorrow?
- Is there a validated alternative, or only a theoretical one?
- When were these terms last actually negotiated?
Illustrative example — not customer data
One distributor carries 38% of spend on net-45 terms. Their acquisition closes next quarter; the acquirer's standard is net-10. Same vendor, same goods — and a five-week working-capital hole arriving on a schedule you don't control.
How Flash covers this signal
Flash computes vendor share of spend nightly and flags threshold crossings and trend in the morning brief, so concentration is reviewed on a schedule instead of discovered in a crisis.
Related: Payroll-window liquidity squeeze
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.