The close is the product.
The Charter Finance Command Center is a managed month-end close and board reporting service. Controlled automation drafts the work. Your team approves everything in one review queue. The board packet lands on a fixed calendar, with proof behind every number.
Every charter school finance team runs the same loop: statements come in, reconciliations wait, card charges need receipts, entries need posting, the board packet needs building, and somewhere in there the actual month happens. When the team is two people, or one, the loop wins.
The Command Center turns that loop into a fixed calendar. Your team drops the files on Day 1. Controlled automation drafts the reconciliations, codes the card charges, prepares the recurring entries, and writes first-draft variance explanations from transaction detail instead of memory. Everything lands in one place with a single review queue. You approve what needs a human, and the board package delivers on schedule with a sign-off log behind every number.
No new systems. No credentials handed over on day one. It runs on the files your school already produces from QuickBooks, Bill.com, your bank, and your card program.
These are the design targets the service is built and measured against, reported to you on a quarterly scorecard. They are not client results; we publish those only when real closes have run on the system.
Ten days, five checkpoints, one queue.
Files in, drafts out
Your team drops bank and card statements and QuickBooks exports into a shared folder, about 15 minutes of work. Reconciliations are drafted, card charges coded by rule, and exceptions flagged the same day.
The review queue
One list of everything that needs a human: unmatched items, unclear charges, entries awaiting approval. Each item carries context and a recommended action. You answer only what needs an answer.
Entries approved and posted
Recurring journal entries arrive drafted with source references and a prior-month comparison. Nothing posts until a named person approves it, and the approval is logged.
Budget vs actual, explained
Variances over your thresholds come with a plain-English draft explanation derived from transaction detail, not memory. You edit and own the narrative; it flows into the packet.
Board packet, signed and archived
The board-ready package and CFO memo deliver on schedule. The close archives itself in a folder structure that mirrors your auditor's request list.
If your inputs arrive late, the calendar shifts day for day and the status board says so plainly. The system never fabricates a close from incomplete data.
Audit-ready by default
Every close archives reconciliations, entry support, and approvals in a folder structure that mirrors your auditor's request list. September stops being a scramble.
Built for lean teams
This is not outsourcing your finance function. Your team keeps ownership and sign-off. We supply the throughput a bigger office would have.
A human signs everything
Payments, postings, grant submissions, and board communications never happen without a named approval. The review queue is the product, not the fine print.
What this system never does without you
- Move money. No payments, no transfers, no payroll approvals, ever.
- Post a journal entry without a named human approval.
- Submit grant drawdowns to any funder portal.
- Send anything to your board, your auditor, or your authorizer.
- Make accounting policy judgments: capitalization, revenue recognition, write-offs stay human.
That list is permanent and it goes in the agreement, in writing. The day money moves without a named human is the day this stops being trustworthy, so it never will.
Start with the Blueprint. Keep the manual either way.
Close Blueprint
We map your close end to end and deliver your Close Operating Manual: every task, owner, source file, and deadline. Valuable even if we stop here, because your close finally exists outside one person's head.
The Blueprint fee is 50% credited toward Install if you decide within 30 days.
Install
We build the matching, coding, drafting, and packet assembly on your real data, then run one full close in parallel with your current process to prove it ties.
Operate
Your close runs on the calendar, month after month. Your team works a short review queue, and the board packet lands on the same day every month with a sign-off log behind it.
FY27 just started. Your first close of the year sets the tone for all twelve.