The work.
Running the month-end close for a ten-company group, and building apps for a charter yacht captain who came back three times.
Case study · 2026
Running the close for a ten-company group
The client
A group of about ten related companies on NetSuite, sharing one small accounting team. One company was still on QuickBooks.
The problem
An accountant had left. Monthly entries had stopped, payroll uploads kept failing, some companies were months behind, and the audit was coming.
The result
August and September closed for the whole group. Payroll caught up. Audit support delivered. A checklist and tools the team can run themselves.
The client is confidential. Names are changed and every number shown below is sample data. The work is real.
Month-end close, two months running
Closed August and September for the whole group. Built the company-to-company bill-backs and the eliminations, so the group's numbers tie out to zero between companies. Built monthly entries for health benefits, net revenue, inventory and accruals, and cleaned up prepaid expenses nobody had touched.
Payroll entries that post the first time
The payroll system's upload files kept failing. We built a nine-point check that catches wrong IDs, wrong offset accounts, wrong dates and entries mixing companies, before anything is posted. Then we caught up four companies on four months of payroll: 48 entries.
Credit cards and company-to-company charges
Built the monthly card entries using the controller's location rules, and found the missing company-to-company entries behind them. Every card month now includes them.
QuickBooks to NetSuite
Moved one company's books from QuickBooks into NetSuite: reviewed the months already moved, then built and posted the rest, plus the lease accounting entries.
Audit support
Pulled the support for the auditors' related-party and repair expense selections: hundreds of pages of bills and card statements, with every difference explained and the remaining gaps listed for the controller.
A close checklist and a toolkit
Mined two years of journal entries to build a month-end checklist, which found recurring entries that had quietly stopped when an accountant left. Built a set of simple tools the in-house team can run without us.
What the work looks like
Sample versions of the schedules and checks we built. Company names and amounts are made up.
Month-end close checklistSample data
September close, all companies.
- Day 2Bank reconciliations, all companiesDone
- Day 3Payroll entries, checked and postedDone
- Day 4Credit card entries + company-to-companyDone
- Day 5Bill-backs between companiesDone
- Day 5Accruals and prepaid expensesDone
- Day 6Inventory entryWaiting on vendor bills
- Day 7Eliminations + tie-outDone
Elimination between companiesSample data
What one company bills another has to cancel out for the group.
| Line | Alder Co. | Birch Co. | Elimination |
|---|---|---|---|
| Management fees billed | 48,500.00 | (48,500.00) | |
| Management fees paid | (48,500.00) | 48,500.00 | |
| Shared payroll billed back | 21,300.00 | (21,300.00) | |
| Shared payroll expense | (21,300.00) | 21,300.00 | |
| Group net effect | 69,800.00 | (69,800.00) | 0.00 ✓ |
Payroll upload checkSample data
Nine checks run on every file before it's posted.
- 1.Every company ID matches the system
- 2.Every account exists and is active
- 3.Offset account is the right one
- 4.Entry date is in an open period
- 5.Accrual reverses on the right date
- 6.One company per entry, no mixing
- 7.Debits equal credits
- 8.Locations match the company's rules
- 9.No duplicate of an entry already posted
Sample result: 212 lines checked. 3 wrong offset accounts and 1 entry mixing two companies, fixed before posting.
Where the hand-typed entries come fromSample data
Two years of journal entries, sorted. The biggest bar is the first thing to automate.
- Bank deposits88%
- Payroll5%
- Accruals4%
- Everything else3%
Payroll catch-upSample data
Four companies, four months behind.
| Company | Apr | May | Jun | Jul |
|---|---|---|---|---|
| Alder Co. | 3 ✓ | 3 ✓ | 3 ✓ | 3 ✓ |
| Birch Co. | 3 ✓ | 3 ✓ | 3 ✓ | 3 ✓ |
| Cedar Co. | 3 ✓ | 3 ✓ | 3 ✓ | 3 ✓ |
| Dogwood Co. | 3 ✓ | 3 ✓ | 3 ✓ | 3 ✓ |
48 entries, all posted.
Audit support packageSample data
Repair expense items the auditors picked.
- Items picked
- 64
- Supported
- 58
- Open, listed
- 6
Every open item comes with what’s missing and who has it, so the controller can close it in one pass.
What this means for a trades business
- • More than one company? We tie them together so nothing is counted twice.
- • Payroll entries that post right the first time.
- • Books months behind? We’ve caught up a lot worse.
- • A close checklist, so the same entries happen every month.
- • Ready for your bank, bonding company or auditor when they ask.
Apps for a charter yacht
Built for one repeat client, a charter yacht captain who came back for more. Read the full case study.
Petty Cash — AI receipt capture
$750
Crew photographs a receipt; AI extracts vendor, date, and amount, files it by department, and exports to Excel. Killed two full days a month of data entry.

Vessel Operations + AI Dry-Dock Planner
$6,500 across two phases
Inventory with per-item alert thresholds, maintenance by calendar date or engine hours with full history, and — phase two — photograph the engine room and get an AI disassembly plan that knows the AC contractor has to be booked first. Replaced a $2,400/year subscription.
