Help centre
A directory, not a maze
We are pre-launch, so there is no in-product ticket queue to point you at yet. What exists is documentation written by the people building the product, and a direct line to them.
Common questions
Start with the question you actually have
Where do I start if we have never used a donor system?
Read the giving and payments pillar first, then the donor relationships pillar. Those two decide how every later obligation behaves: if the donor record and the recognition model are wrong, receipts and reporting inherit the error.
Giving and paymentsOur deposits never match our gift totals. Where does that get solved?
The reconciliation pillar describes the payout, fee and deposit model, and the month-end close guide sequences the work for a small finance team.
ReconciliationHow do you handle a gift where the payer is not the donor?
Legal donor, payer, recognition name and soft credit are separate concepts in the data model rather than one name field. The donor relationships pillar walks through household, tribute and organisation-paid cases.
Donor relationshipsCan we migrate our existing donor data?
Import and export are Release 1 scope. The migration playbook covers deduplication, recognition mapping and what to deliberately leave behind rather than importing errors.
Guides and playbooksIs Beneora running live donations today?
No. We are in a design-partner programme and several capabilities are in active build. The roadmap and capability status table are the accurate picture at any given time.
Product roadmapWho can see what inside the product?
Access is scoped by tenant and by role, and financial state changes are audited. The security page describes the mechanisms and states the limits we have not closed yet.
SecurityDocumentation
Everything we publish
Design-partner program
Build the donor-operations layer with us
We are working with a small number of US and Canadian nonprofits who feel the reconciliation and donor-data pain most acutely. Partners shape the sequence, see the honest status of every module, and are never charged for a capability that is still a prototype.