This is a design-partner working session, written up with permission and without identifying details. It is not a customer success story: Beneora is not yet running this organization's live money, and we will not describe results we have not delivered.
What we did
We walked one month of her actual close, on paper, against the Beneora object model — payouts, deposits, exceptions, close batch — and marked every point where her process needed a field the model did not have.
What we found
- Her processor deducts a monthly platform fee that belongs to no payout. We added a period-level fee adjustment.
- She receives two deposit types from one processor with different timing. Payout arrival needed to be a range, not a date.
- Her offline gifts are entered weekly in batches; the received date mattered more than we assumed.
- She keeps a private spreadsheet of accepted variances. That became the exception reason field.
“I do not need the software to be clever. I need it to remember why I accepted a difference in March when someone asks me in October.”
Honest status
Three of the four changes are in the Release 1 data model and the reconciliation workspace demonstrates them on illustrative data. None of it is yet reconciling her real bank account. That is the next milestone, and she knows the sequence.