The lockbox file lands. Someone opens it, reads each check and remittance, and keys the cash against open invoices one line at a time.
CFO and back office
Bring the close into focus.
It runs inside your ERP and the spreadsheets your team already keeps. Every payment ties to the cent, and a person signs before a single entry posts.
The reality
A person keys checks by hand all morning, then starts on the bank rec.
A payment covers six invoices and shorts one. Finding which one, and why, is a person squinting at a remittance PDF.
The bank statement comes in. Every line gets matched to the ledger by hand, and the unmatched ones sit until somebody chases them.
Month end starts, and the same people who applied the cash now key the accruals, then rebuild the board pack from numbers they hope still tie.
Until it's one button.
What the button does.
Apply the cash.
Your files go in. Posted entries come out. Nothing moves to a new platform.
Lockbox filechecks and remittances
Bank statementthe daily feed
Your ERPNetSuite, your ledger of record
One clickApply the cash
Posted entries and exceptionsevery match traced to the invoice
It reads the lockbox file, matches each payment to the open invoices, applies the cash in your ERP, and lists the ones it could not tie. A second pass rederives every match before anything posts. You review and sign.
One button, four jobs
The work it takes off the desk.
01
The lockbox file lands with the morning's checks and remittances.
Reads every check and remittance, matches each payment to the open invoices, applies the cash in your ERP, and flags the ones it could not tie.
02
The bank statement comes in for the day.
Reconciles every line against the ledger and surfaces each unmatched item on its own, so your team works the breaks instead of the whole feed.
03
Month end starts and the accruals are due.
Drafts the accruals and the roll forwards with the working shown, and traces every figure back to the entry it came from.
04
The board wants the pack.
Drafts the reporting from numbers already tied out in the close, so the pack sits on figures that reconcile instead of a fresh keying pass.
Proof
25 of 25Matchable bank lines paired correctly on the messy set, every run. The other 6 were held as breaks
9 of 9Planted problems caught on the messy bank reconciliation, every run, including an unrecorded 9,860.00 wire
0Payments matched to the wrong line or invoice, across 18 runs
Sample data test, Oct 2026. Invented files, not client results. Our own free packs, run in Claude Opus 5, three runs per set, scored against an answer key written before the first run.
We ran our own free packs on invented files built to be awkward: a bank statement and ledger with a duplicate payment, a transposed amount, an unrecorded wire and timing items, and a lockbox file with a short pay, an overpayment, invoice number typos and a duplicate record. We wrote the answer key first, ran each set three times, and scored every run. On bank reconciliation it matched every line correctly and caught every planted problem, every time. On cash application it never put a payment on the wrong invoice, but it did not get the exact split right on an overpayment in any run or on a short pay in two of three. It flagged those for a person instead. That is where your team still looks. Download the files and run them in your own Claude.
Explore the underlying builds
Related workflows available in the Consultance build library.
Cut Your Month End Close to One DayMatches the bank feed, books the accruals with the working shown, and traces every entry back to its source, so the close drops to something the board can audit line by line. Free to run.Statement Matching and ReconciliationMatches scanned bank, custodian, and brokerage statements to your ledger and returns only the breaks, on your own machine. Free to run.Board Variance Bridge Second ReadRuns a second read on the board variance bridge, splits the miss into price, volume, and mix, and writes the one line of commentary a CFO would sign.Built to be reviewed
What you keep.
- It runs in your tenant. Your ledger and bank data never leave your environment.
- Every entry ties to the cent, back to the invoice or statement line it came from.
- A second pass rederives the match, and the output blocks until the two agree.
- You own the code. No subscription, no seat you rent back from us.
- No new login. It works inside the ERP and spreadsheets your team already opens every morning.
Built for the controller who would rather review exceptions than key checks.
The manual version is free
Try it on a static file first.
The packs below run the same read on a statement or a close you paste in, in your own Claude, today. Free to pull down and keep. The installed version is the one wired into your ERP, running the second the lockbox file lands. Run the manual one this week. If it saves the morning, the build is wiring it in properly.
Cut Your Month End Close to One DayStatement Matching and ReconciliationBoard Variance Bridge Second Read
Explore the library Put your own lockbox file in front of it.
The audit is 30 minutes. You show us the close work that burns the most hours, we put a dollar number on it and tell you straight whether this moves it. No pitch deck.
Or grab a time for the audit