Frequently asked (answered honestly).

The volunteer parent who ended up holding the spreadsheet, the Venmo handle, and a stack of reimbursable receipts. Not built for accounting firms or league directors with payroll departments, built for the volunteer who wants their Sunday back.

About 10 minutes for a 15-player roster. Create a team, add players with one or two parent contacts each, add coaches with their per-event amount. You're ready to record your first event.

No. No debits, credits, journal entries, or chart of accounts. The product is designed around what a TM actually does, record an event, log a payment, send reminders, not around general-ledger conventions.

Not in the MVP, manual entry only for v1. CSV import is on the v1.x roadmap; if it would unblock you, mention it on the contact form and we will prioritise it for pilot teams.

No. We're a record-keeping ledger. Parents pay you directly via cash, check, Venmo, Zelle, or bank transfer; you record what came in. We never move money, no card-processing fees, no PCI scope, no settlement waits.

For player payments: cash, check, Venmo, Zelle, or Other. Coach payouts add Bank Transfer for direct deposits you arrange from your own bank. Each entry stores the method and an optional notes field. TeamLedger never moves money, you record transactions you have already settled.

Delete the original payment and re-record the actual amount received once the parent makes you whole. The deletion lands in the audit log with timestamp and TM identity, so the history of "recorded then reversed" is preserved, TeamLedger never silently rewrites a payment row.

Cent-perfect, every time. Each player's share rounds down to the nearest cent, then the remainder is distributed one cent at a time in last-name-ascending order until the total matches the event amount exactly. Same algorithm runs across events, fundraisers, and redistributions.

Click Cancel Event on the event detail page. TeamLedger lists every parent who paid into it and converts those amounts to credits on each player's ledger. Unpaid charges zero out. The event stays in the list with a Cancelled badge, no payment record is ever deleted.

Email and SMS, configurable per parent contact. Each contact has independent email and SMS toggles, a household can receive one channel, both, or one parent can opt out entirely while the other stays subscribed.

Yes. Every player supports up to two parent contacts, each with their own email, phone, and channel preferences. Both receive every reminder, payment confirmation, and new-charge notification independently, no forwarded emails, no co-parent-as-gatekeeper.

On the due date, then weekly until the player's balance reaches zero. A 7-day cooldown per (parent contact, team) prevents double-pinging a parent with two kids on the same team. The Send all reminders button on the dashboard bypasses the cooldown for end-of-season collection drives.

No. One consistent reminder voice for every parent, every cycle. Tone tiers were considered and explicitly cut from the MVP, one professional, factual tone keeps the product simple and the parents on-side.

During the pilot, on SolGuruz infrastructure that the engineering team controls directly. Post-launch, the production stack runs on AWS, encrypted at rest on RDS PostgreSQL, encrypted in transit with TLS 1.3, daily backups. The full target architecture is documented in the SRS for any pilot team that wants the deep dive.

Your records stay for as long as you keep your team active. The audit trail is append-only at the database level, the application role itself lacks UPDATE and DELETE on the audit log, so records cannot be silently rewritten. Export everything as CSV any time you want a copy on hand.

Yes. Every report, Master Event List, Coach + TM Payment Summary, Player Balance List, Per-Player Statement, Audit Trail, exports as PDF and CSV. CSV is what you hand to a bookkeeper or auditor; PDF is what you email to a parent.

Data is retained for 30 days in case you change your mind, then deleted unless you have requested an export. Full CSV export is available at any time before deletion, no quotas, no per-export fees.

Free and Pro: one active team per account. League: unlimited active teams under one org, with cross-team reporting. See the pricing page for the full comparison.

Not in the MVP. Phase 1 is a single Team Manager account per team. If your league treasurer setup needs co-manager access, mention it on the contact form, we are tracking demand, and it is a near-term roadmap item.

Yes, explicitly supported. The TM-as-parent dual role runs throughout the product: your child's ledger is managed identically to any other player's, including reminders to the email and phone you list as the parent contact.

There isn't one. Free is genuinely forever for one team up to 15 players, with every core workflow, events, payments, fundraising, cancellations, dashboard, reports. SMS, audit-trail CSV, and emailable per-player statements sit on Pro because they cost us money to deliver. Everything else is included.

Pilot pricing locks in for at least their first full season for participating teams. v1.x roadmap covers CSV import, co-manager access, and a few smaller QoL wins, but MVP scope is deliberately what ships at launch. We'd rather do less, well.