Splitsteward
A review-first allocation workspace that matches one observed bank deposit to its constituent receipts, proposes fund and accounting dimensions, enforces amount invariants, writes only an approved version, and reconciles provider acknowledgment with the destination ledger and bank statement.
Volunteer treasurers and small nonprofit finance teams can receive one bank deposit that combines gifts or receipts assigned to several funds. The supplied research confirms bank-data, ledger and accounting write surfaces and did not find a surgical nonprofit split-deposit product. That is a researched gap, not proof of no alternative. Splitsteward remains deliberately narrower than a fund-accounting suite. It links an observed deposit to candidate constituent receipts, preserves donor or payer evidence, proposes but never decides restriction or accounting treatment, verifies that allocations plus fees and adjustments equal the observed amount, routes the exact posting for authorized approval, records provider acknowledgment and reads back the destination ledger before marking reconciliation complete. Bank observation, receipt identity, donor intent, restriction classification, fund assignment, accounting entry, provider receipt, ledger state and bank reconciliation are separate. The product cannot infer legal restrictions from memo text, manufacture missing receipt evidence, auto-post low-confidence matches, change closed periods or certify the books. Accountants retain chart, fund, class, project, period and correction authority. An unidentified difference remains an exception rather than being forced into a balancing fund.
A nonprofit treasurer, bookkeeper or finance manager handling combined deposits across restricted and unrestricted funds in an existing accounting system.
A recent community pain report and confirmed interfaces support a current window without creating a hard deadline.
Matching, allocation proposals and reconciliation scale through software, with exceptions and accounting review adding variable cost.
One cross-reference and two inbound connections support moderate convergence.
A verbatim workflow pain, confirmed data and write surfaces and a narrow amount-preserving mechanism make the first job easy to test.
The buyer and budget remain broad, provider semantics must be verified, restriction classification needs accounting authority and incumbents can plausibly add the missing workflow.
Discussion
No comments yet — be the first to weigh in.
