FluxWorkflowsArticlesContact us
Reconciliations

What Slips Through at Month-End, and How to Catch It

Flux Team · Updated 2026-11-03 · Workflow: Reconciliations

Small items slip through, and they slip between steps. A receipt with no invoice. An invoice paid with no match. A check that never cleared. A vendor paid twice. Each one hides in a balance nobody ages. You catch them with simple tests run on every item, every month, before review. A sharper reviewer won't find them.

Why Does a Clean Close Still Miss Things?

Because a close that ties out only proves the books balance. It says nothing about whether the right vendor was paid once, for goods that arrived. Review looks at big variances, and a US$3,000 duplicate inside a US$300,000 AP balance moves nothing.

Most of what slips through is honest error. Fraud is the tail risk, and it hides in the same places. The ACFE's 2026 study of 2,402 fraud cases found a typical case ran 12 months before detection (ACFE). Tips found 43% of them. Smaller businesses had the highest median losses of any size of organization.

In the same study, more than half of all cases involved a lack of internal controls or an override of existing ones (ACFE).

Where Does Each Item Hide?

The ages and timings below are our suggested defaults. Set your own and write them down.

Item Where it hides The test that finds it When to run it
Receipt with no invoice Received-not-invoiced account, or nowhere if you don't book receipts Open receipts by vendor, over 30 days Monthly
Invoice with no receipt Bills where an approver overrode the PO match Bills paid without a three-way match, above your threshold Every payment run
Invoice paid without a control check A batch approval of 40 bills Self-approved bills, late approvals, recent bank detail changes Every payment run
Stale reconciling item The rec's outstanding list, clearing accounts Age every item; over 60 days needs a decision Monthly
Duplicate or overpayment AP debit balances, or expense counted twice Vendor, normalized invoice number and amount Before every payment run
Unused vendor credit Vendor statements Statement rec for your largest vendors Quarterly

How Do You Catch Unmatched POs?

A PO with a receipt and no invoice is a liability you haven't booked. If your system books receipts, it sits in a received-not-invoiced (GRNI) account. If it doesn't, it sits nowhere, and the cost lands in whichever month the bill shows up.

List open receipts by vendor and age. Past 30 days, someone asks the vendor for the invoice. Past 90, check for a receipt booked twice or a PO nobody closed.

The reverse case costs more: an invoice with no receipt shouldn't be paid. If approvers can override the match, review the override list every payment run.

How Do You Catch Invoices Paid Without a Control Check?

The control exists on paper. In practice the approver clicks through a familiar vendor in a batch of 40. Test the run after the fact:

The last one is the expensive one. In AFP's 2025 survey of 521 corporate practitioners, 79% said their organizations were hit by attempted or actual payments fraud in 2024 (AFP). Business email compromise was the top avenue. The control: confirm any bank detail change by calling a number you already had.

How Do You Clear Stale Reconciling Items?

A bank rec that ties with 14 stale items isn't done. It's deferred.

Age every reconciling item in every rec, every month. Anything past 60 days gets an owner and one of four decisions: chase, write off, reclass or reissue.

AFP notes that uncashed checks are among the most common sources of unclaimed property. Dormancy periods vary by state and property type, commonly one to five years (AFP).

How Do You Find Duplicates and Overpayments?

Duplicates come from three places. The same bill keyed twice with a different invoice format ("INV-0042" and "42"). One vendor set up twice in the vendor master. One bill paid by AP and again on a company card.

Before every payment run:

  1. Normalize invoice numbers. Strip spaces, punctuation and leading zeros.
  2. Match on vendor, normalized number and amount.
  3. Match on amount and a 30-day window across all vendors. This catches the duplicate vendor record.
  4. Compare bank details across vendor records. Two vendors sharing one bank account needs an answer.

Each month, review AP debit balances: money vendors owe you that nobody chases unless it's listed. Each quarter, ask your largest vendors for a statement.

What It Looks Like

Figures are illustrative.

A US$40M distributor on NetSuite closes October. Before review, the tests find this.

Item Amount (US$) Where it was Test that found it Decision
Receipt with no invoice, 47 days 18,400 Received-not-invoiced Open receipts over 30 days Invoice requested; liability stays
Bill paid with the match overridden 9,150 October 14 payment run Paid without three-way match Half the goods arrived; US$4,575 credit requested
Same bill paid twice 3,280 AP debit balance Normalized invoice number Refund requested
Vendor check outstanding 14 months 2,960 Bank rec outstanding list Items over 60 days Payee contacted; unclaimed property review if no reply
Vendor credit memo never applied 1,120 Vendor statement Quarterly statement rec Applied to next bill
Total 34,910

None of this would show up in a variance review. US$34,910 is under 0.1% of revenue. Yet US$8,975 is cash coming back, and one check may be property the company has to report.

What to Automate vs Keep With a Person

Automate (calculate or flag):

Keep with a person:

Controls That Hold Up

At year-end, your auditor will search for unrecorded liabilities. An aged open receipts list answers part of that before they ask.

How Flux Runs This

We embed with your team and learn how your close really runs, including the rules nobody wrote down. The sweep account that moves cash overnight. The vendor refund that always lands in the wrong account. Recs built from the written procedure flag the wrong things on day one.

Then we run your bank, card and balance sheet recs every period. Matching and aging are calculated in code, and every rec ties to its GL balance and the trial balance before anything is written. AI reads bank memos, card descriptions and remittance text to propose matches. It never does the math, and it never clears an item.

Anything the data can't explain becomes a flagged question with an owner. "US$2,960 check to a freight vendor, outstanding 14 months" goes on the list. It doesn't get plugged to make a rec tie.

Your team reviews, signs off and decides what to chase or write off. Each decision is kept, so once you tell us why an item sits open, it stops coming back as a question.

We work from files you export, with no system access. A mutual NDA is signed before any files are shared. It gets cheaper for us each month, and you see that as a shorter close.

FAQ

How often should reconciling items be aged? Every month, in every rec. Anything past 60 days needs an owner and a decision: chase, write off, reclass or reissue.

How do we find duplicate vendor payments? Before each payment run, normalize invoice numbers and match on vendor, number and amount. Then match on amount and date across vendors.

What happens to old outstanding checks? They can become unclaimed property under state law, after a dormancy period that varies by state. Contact the payee, then reissue it or report it. Voiding a check doesn't cancel what you owe.

If small items keep turning up after your close, send us a period you've already closed. We'll run your bank, card and balance sheet recs free, with every aged item and unmatched line flagged. Compare them line by line with your own. See how we run reconciliations.

Contact us