Stop the close-time fire drills.
Catch issues before reconciliations.
Weekend postings. Stale suspense items. Duplicate journal entries. Round-number plug entries. Manual-JE concentration in one user. Mid-market finance teams burn weeks per close chasing items that a 30-second audit could have surfaced upfront. The Finance Close Audit reads your GL on your device, runs seven detector rules, and hands you a punchlist before you start the formal close. Your GL never leaves your browser. Switch off your Wi-Fi and watch it work.
FROM YOUR GL DETAIL — TO A CLOSE-REVIEW PUNCHLIST
Seven things every controller checks before close.
The audit doesn't replace your close process. It runs the spot-checks a senior reviewer would do on the raw data before signing off — the kind of pattern-match that's tedious in Excel and slow to do across a multi-million-row GL.
Weekend / holiday postings
JEs posted on Saturdays and Sundays. Outside normal close-prep this is a control-environment red flag.
Round-number anomalies
Entries that are exact multiples of $1K, $10K, or $100K. A Benford's-law-adjacent heuristic for plug entries.
Suspense / clearing aging
Items sitting in suspense, clearing, interim, or holding accounts past 30 days that should have been reclassed.
Manual JE concentration
Users posting a disproportionate share of manual JEs. Segregation-of-duties signal worth a documented review.
Period-cutoff misposts
Current-period entries with descriptions or references indicating they belong in a prior period. The classic backdating pattern.
Abnormal account activity
Accounts whose current-period activity is 3x or more above their 12-month baseline. Surfaces the items that drove the variance.
Duplicate JE candidates
Same account, same amount, within 7 days. Catches accidental double-posts before they become reconciliation pain.
Sits next to your close software, not against it.
If you already run FloQast / BlackLine / Trintech / Numeric / Workiva for your monthly close, keep using them. They manage workflow — tasks, reconciliations, sign-offs. Good at it.
This audit does the thing they don't — pattern detection on raw GL data. The seven checks above are the kind of work a senior reviewer does manually in Excel after pulling extracts. We do it in 30 seconds, on your device, and hand you a CSV punchlist.
Most controllers run this before kicking off the formal close in their workflow tool: catch the issues early, fix them before they propagate into reconciliations and sign-offs.
Nowhere. That's the whole point.
The audit runs entirely in your browser. Your file is parsed into an in-memory analytical database on your own machine and queried locally. No row of your GL is sent to our servers — or anyone else's. Close the tab and everything is gone.
This isn't a marketing claim — it's how the architecture works. The web tool loads a small SQL engine and runs SQL queries on your file inside your browser. There's no upload endpoint to send to, because we don't have one for this tool.
Things you'd reasonably ask first.
What does the Finance Close Audit actually do?
It runs seven detector rules against your general ledger or journal entry export and returns the items a Big-4 reviewer would flag before close: weekend postings, suspense / clearing account aging, round-number anomalies, duplicate JE candidates, period-cutoff misposts, manual-JE concentration by user, and accounts with abnormal activity vs their 12-month baseline.
Where does my data go?
Nowhere. The audit runs entirely in your browser using a local analytical engine. Your file is parsed into an in-memory database on your machine and queried with the detector rules. No row of your data is sent to any server — ours or anyone else's.
What file format should I export from my accounting system?
A general ledger detail or journal entry register exported as CSV, Excel (.xlsx), or JSON. Most ERPs (NetSuite, QuickBooks, Xero, Sage Intacct, Microsoft Dynamics, SAP) can produce this from their reports menu. The audit needs at minimum account, posting date, and amount columns; a posted-by or source column unlocks the manual-JE concentration detector.
Is this a replacement for FloQast / BlackLine / Numeric?
No. Those tools manage your close workflow — task lists, reconciliation tracking, sign-offs. This is a free pre-close audit you run on your raw data to surface the items worth investigating before you start the formal close process. Many teams use it alongside their close platform.
How much data can I run through it?
Practical ceiling is about 1 million journal entry lines per run — that's roughly 12 months of GL detail for a mid-sized business. Larger datasets work but get slower; very large GLs (multi-entity consolidations, multi-year datasets) are better handled with the desktop premium tier when we ship it.
What does it cost?
Free. The web tool stays free permanently — it's how we introduce ourselves. If you want us to run the actual close review on your books, schedule replays on a cadence, or get a desktop version with larger dataset support and direct ERP connectors, that's a separate paid engagement.
Run it on this month's GL.
Two minutes from "drop file" to a CSV punchlist you can walk into your next close review with.
Run the audit →