FY26_FINAL_v3_ACTUAL_FINAL.xlsx, carefully type the ending balance of every account into the opening row of a new blank tab, change the year in the header, and pray that nobody needs to add a late transaction to the prior year for the next six weeks.
Then someone asks if the board fund ending balance is correct. You open three versions of the file to compare. Two of them agree. The third is off by $47. Nobody knows which version the board meeting minutes referenced.
This is the ritual we built ledger periods to retire.
Bookkeeping systems that treat your ledger as one infinite stream of entries look simple and work well for a month. They stop working the first time you have to answer "how did we do last fiscal year?" with certainty.
Without a real boundary:
The spreadsheet ritual is a coping mechanism for this. Copying the file and freezing a version is how treasurers manually impose a boundary that the tool itself does not enforce. The work is real; the method is fragile.
A ledger period is a span of time — typically a fiscal year, sometimes a season, occasionally a calendar quarter — during which ledger entries can be written. Exactly one period is active at a time. When a treasurer closes the active period, two things happen automatically:
Day-to-day bookkeeping resumes immediately in the new period. Settlement payouts, scholarship disbursements, fund transfers all keep working. If you close without creating a replacement, writes to the ledger fail with a clear error until a new period starts — the system refuses to let you write with no period to write to.
Your year-end numbers stop moving. Once FY 2025 is closed, the total in the General Fund at the end of that year is permanent. Pull that number six months later and it matches the board minutes. Pull it six years later and it still matches. The books are closed.
Corrections are honest. You cannot backdate an entry into a closed period. If you discover an error in last year's settlement, the fix is a corrective entry in the current period with a note explaining what you're correcting. The original entry stays intact. This is how accountants have done corrections for centuries, and it is the only way an audit trail actually holds up.
Transitions are clean. When a treasurer hands off to a successor, the boundary between regimes is obvious. The outgoing treasurer closes the period on their last day. The incoming treasurer sees a fresh, named period. Nobody wonders whether a messy entry belongs to the old regime or the new one.
990 prep gets easier. Fiscal-year boundary lines up with filing boundaries. The numbers in your IRS filing match the numbers in the period you close — no reconciliation between your books and your return.
There is no rule about when to close. Some orgs we work with close once a year, aligned with their fiscal year-end. Others close per season — a booster club that runs only football concessions from August through November might close the period in December, then open a new period in August when football starts up again. Some orgs run a single long-lived period forever and only close when a specific event forces it: a treasurer change, a CPA engagement, a merger.
The right cadence is whatever matches the natural rhythm of your org. Closing too often creates busywork. Closing too rarely defeats the purpose. One close per fiscal year is the default for a reason.
We deliberately did not build:
Ledger periods is live on StandShare today. If you're running a fiscal year that ends June 30, now is a good time to try closing your first period in a low-stakes way: wait until your last May settlement posts, confirm every family balance looks right, close the period, and hand the successor a clean new one named FY 2026–27. When June 1 hits, you are already in next year — and last year's totals are locked in, for good.
The spreadsheet ritual served a real purpose. It doesn't need to anymore.
]]>The job hasn't changed in decades. What has changed is the number of places it lives.
The paper part is always the same:
The tablet has the volunteer portal open in one browser tab and the settlement tool open in another. The personal phone has the family group chat, which is where most of the late changes actually happen — a mom asking if her college-age son can swap in for his sister, two families coordinating a ride share to a game that moved to a different diamond.
Between arrival and first pitch, the coordinator does each of these at least once:
The game starts. The coordinator works the line for twenty minutes. The phone rings.
It is a family asking why they were charged a no-show fee last month when their daughter did work the event — she just worked a different stand than what was printed. Nobody updated the system. The coordinator promises to look into it and doesn't quite mean it, because looking into it means opening the settlement from six weeks ago, figuring out which stand the worker actually worked at, and hoping the audit log captured the shift.
The old version of StandShare reflected this reality too faithfully. The event list was a grid. Clicking a row expanded an inline panel with workers and stands. Editing an event took you to a separate page. Settlement was its own page. Check-in was its own page. Roster editing was its own modal. Each of them worked. None of them were the same place.
A coordinator running an event touched five different screens to do the one job.
We rebuilt the event workflow around a single question: if a coordinator clicks a concession event, what should they see?
The answer is now the Event Detail page. Click an event from the Events Hub — which is itself just two tabs, List and Calendar — and you land somewhere that holds everything that concerns that event:
The coordinator still has the cardboard folder. That is a real choice, and some things really do belong on paper. But the number of screens between the folder and the truth has dropped from five to one.
A few smaller changes compound into the feel of the new flow:
12 / 20 workers and means it.None of this is glamorous. It is the slow, boring work of noticing that a coordinator is switching tabs five times to do one job, and then not making them do that anymore.
We deliberately kept:
Open the Events Hub the next time you have an event coming up. Click into the event. Notice the drawers. You will not need all of them in a single session, but when you do need one — a late swap, an uncovered stand, a last-minute "who is bringing the float?" — they are all right there on the same page you started on.
The cardboard folder can stay. It is a good folder.
]]>They were managing all of it with spreadsheets.
At the start of each season, the outgoing treasurer handed over a folder. Inside:
The new treasurer, Maria, was a former accountant. She could read a spreadsheet. What she couldn't do was understand why the same family appeared in three different tabs with three different balances, or why some settlement rows had a dollar figure and others had a formula that referenced a cell in a different file that no longer existed.
It took her six weeks to feel confident that the numbers she was working with were correct.
After each concession event, the coordinator ran a reconciliation process that took an average of 3.5 hours:
Three coordinators burned out during this process in a four-year span. The fourth, James, stayed — but he described the role as "a second job I don't get paid for."
The organization moved to StandShare at the start of the following season. The migration itself took two sessions: one to import family account data and opening balances, one to train the coordinator and treasurer on the interface.
The coordinator uses the StandShare mobile-friendly interface to check in families as they arrive. At the end of the event, she marks it closed. Credits are calculated and posted automatically based on the credit schedule the treasurer configured at the start of the season.
Total coordinator time per event: 25 minutes, covering check-in, drawer count entry, and event close. No spreadsheet, no formula review, no email queue.
The most immediate feedback from the first season: families stopped emailing the treasurer to ask about their balances. They logged into the family portal, saw their current balance and full transaction history, and that was enough.
Maria estimated this saved her 45 minutes per week during the active season — time she had previously spent fielding balance inquiries and cross-checking the ledger before replying.
When a family disputed a no-show charge in October, James pulled up the transaction in StandShare. It showed the check-in record (no entry), the system-generated no-show credit deduction, the timestamp, and his username as the coordinator who closed the event. He forwarded the screen to the family. The dispute was resolved in one reply.
Families submit required forms through a link in StandShare. When a form is received and processed, the family's compliance status updates automatically. At any point, the treasurer can see exactly which families are compliant, which have pending items, and which are blocked from scholarship consideration.
The school district compliance report that previously required a manual export and 90 minutes of formatting now takes three clicks.
| Metric | Before | After |
|---|---|---|
| Coordinator time per event | 3.5 hours | 25 minutes |
| Balance inquiry emails per week (active season) | ~18 | ~2 |
| Compliance gaps identified at season-end | 6 | 0 |
| Annual 990 prep hours | 12-14 | 3 |
| Family disputes escalated beyond first contact | 4-6 | 0 |
The scholarship fund, which previously required a manual audit of the family ledger before each award cycle, now draws directly from verified account data and compliance status. The committee reviews applications, not spreadsheets.
James is still coordinating. He described the change simply: "I can do this without it taking over my weekends."
If your organization is running a similar stack — multiple spreadsheet files, manual reconciliation, family balance inquiries filling your inbox — StandShare was built for exactly this situation. The migration is straightforward and the first season tends to pay for itself in recovered volunteer hours.
]]>Here are the five things every treasurer privately wishes they had — and what those things actually look like in practice.
Imagine if, at the end of every concession event, the credits were calculated automatically.
No more manually looking up each family's shift length, cross-referencing it against the credit schedule, and entering the result one row at a time. No more wondering whether you remembered to apply the partial-credit rule for the family who left 30 minutes early. No more re-checking your math the next morning because you weren't sure you saved the right version of the file.
Automated settlement means the coordinator checks in families as they arrive, marks the event closed when it ends, and the credits post. The treasurer reviews a summary instead of building one.
For an organization running 20+ events per season, this is the difference between a manageable volunteer role and a part-time job nobody signed up for.
Imagine if families could check their own balance without emailing you.
"What's our current account balance?" is the most common question a treasurer receives. It is also the most time-consuming to answer accurately, because the answer requires opening the spreadsheet, finding the right row, making sure you're looking at the current version, and composing a reply.
Multiply that by 80 families, some of whom ask multiple times per season, and you have a material chunk of the treasurer's volunteer hours going toward balance lookups.
A self-service portal means families log in and see their balance, their transaction history, and their compliance status. They don't need to wait for a reply. You don't need to send one.
Imagine if you could see, in one place, which families had submitted their required forms and which hadn't.
Signed liability waivers. Concession certifications. Fundraising participation agreements. These documents matter — some organizations require them before a family's account can be used for scholarship applications, and some school districts require them for audit purposes.
In a spreadsheet system, compliance tracking is a column that somebody has to update manually every time a form comes in. Forms arrive by email. The column gets missed. When scholarship season comes and a family's eligibility is in question, there's no clean record to refer to.
Integrated document management means forms are submitted digitally, compliance status updates automatically, and the treasurer can pull a compliance report in seconds rather than hours.
Imagine if every transaction had a timestamp, a user, and a reason — and you could look it up in 10 seconds.
Family disputes about account balances are not pleasant. They are, however, inevitable. Someone believes they showed up for an event and didn't get credit. Someone thinks their balance is higher than what the treasurer has on record. Someone's scholarship application is on hold because their account shows a compliance issue they don't recognize.
Without an audit trail, resolving these disputes requires reconstructing a history from email threads and spreadsheet version histories. With an audit trail, you look up the transaction, show the timestamp and the user who entered it, and the conversation is brief.
An audit trail is also the right answer when the school district asks how the funds were managed.
Imagine if generating a seasonal financial report took four clicks instead of four hours.
End-of-season reporting is one of the tasks that pushes treasurers not to return for a second year. It requires pulling data from multiple tabs, verifying totals, formatting for the school district's preferred template, and double-checking everything against the original receipts.
For nonprofits with 990 filing requirements, the stakes are higher. The numbers need to be right, and they need to be traceable.
One-click reports mean the treasurer exports a formatted summary whenever it's needed — for the school district, for the board, for the 990 preparer. The data is already clean because it was captured correctly the first time.
StandShare was built around these five things. Automated settlement math, a family self-service portal, integrated document management, a full audit trail, and financial reporting that takes minutes. If any of these sound familiar, it might be worth a look at what StandShare does.
]]>_FINAL_v3_USE-THIS-ONE.xlsx. And somewhere between columns AQ and BW, last year's settlement math stopped adding up.
This is not a technology problem. It's a coordination problem that technology made worse.
When a booster club is small — a dozen families, five events per season — a shared Google Sheet works fine. Someone sets up the initial tracker in an afternoon. Families email in their hours. The treasurer does the math. Done.
Then the organization grows. Now there are 80 families, 22 home games, multiple concession windows, and a scholarship fund that needs its own accounting. The spreadsheet grows with it, one tab at a time, until nobody is quite sure what's canonical anymore.
Here's what a realistic event reconciliation looks like for a mid-sized organization:
A coordinator arrives at 7 AM for a 10 AM game. After the event, she needs to:
Total time: roughly 4 hours, performed by someone who volunteered to run a concession stand, not to be an accountant.
Multiply that by 22 events and you have 88 hours of coordinator time per season spent on spreadsheet maintenance alone.
When a family disputes their balance — and they will — the spreadsheet becomes a liability.
"You charged us for a no-show on October 14th, but my daughter was there."
Now the coordinator is digging through Tab 22, checking timestamps on email threads, and trying to remember who entered what. There is no timestamp. There is no record of who changed cell D47. There is only a number and a memory.
Financial disputes without audit trails are uncomfortable. When they involve scholarship decisions — where a family's compliance record affects their eligibility for several hundred dollars in tuition relief — they become genuinely serious.
A typical booster club's operational data lives in:
None of these systems talk to each other. When a family asks "what's our current balance?", the answer requires pulling data from at least three sources and doing arithmetic that may or may not be current.
School districts and state athletic associations have paperwork requirements. Families need to submit signed liability waivers, concession certifications, or fundraising acknowledgments before their accounts are considered compliant.
In a spreadsheet system, compliance tracking looks like a column marked "Y/N" in Tab 18. The N entries get highlighted in red. Every year, some families slip through because someone forgot to check the column, the filter was accidentally cleared, or the form was submitted but the Y was never entered.
Booster clubs have high turnover by design. Families cycle in as their kids join programs and cycle out when they graduate. Every few years, the treasurer or coordinator role changes hands.
When that handoff happens, the incoming coordinator gets a file. Maybe a folder of files. And a 30-minute meeting where the outgoing coordinator explains what all the tabs mean.
The institutional knowledge that makes the spreadsheet work — the comment cells, the unwritten rules, the lookup formulas that reference cells three sheets away — doesn't transfer. It just gradually stops working until someone rebuilds it.
Organizations managing fundraising accounts, concession credits, and compliance documentation are increasingly moving away from general-purpose spreadsheet tools toward purpose-built software that handles scheduling, settlements, and compliance in one place.
The shift is less about features and more about reliability. When the reconciliation math happens automatically, when families can check their own balances, when every transaction has a timestamp and an author, the 4-hour-per-event coordinator tax drops to something closer to 20 minutes.
The spreadsheet was always a workaround. The question is how long the workaround is worth maintaining.
]]>