Design-partner program · Core donor operations in active build

See the roadmap
Skip to content
Beneora
Designed: The workflow is specified and drawn. Implementation has not started.Release 2 — not yet built

For companies and foundations

The funder side of the same lifecycle

Employee giving, matching queues, sponsorships and grant payments are the other end of the contribution Beneora already models. Prototypes exist; this is deliberately Release 2 work.

What the week looks like today
  • TodayMatching requests arrive by email, are approved in a spreadsheet, and reach the nonprofit as an unexplained lump sum.
  • The gapThe nonprofit cannot tie the payment to the employee gifts it matched, so soft credit is guesswork.
  • The opportunityIf both sides share the object model, matching reconciles itself.
Finance · ReconciliationTrace GFT-10482

Gift received

Recurring · Winter Shelter (restricted)

$250.00

Processor fee

2.9% + $0.30 · card

−$7.55

Net to payout

Payout PO-2261 · settles T+2

$242.45

Bank deposit

Matched batch of 21 gifts

$4,812.90

Fund allocation

Winter Shelter · restriction honoured

$242.45
MatchedReceipt issued v2Audit trail 6 events
Illustrative data · product surface in active build

What changes

The specific difference, not a benefit list

Each card names the operational change, not an outcome we cannot prove for you.

  • What changes

    Matching that arrives explained

    A matched payment references the employee gifts it matches, so soft credit and receipting are correct on arrival.

  • What changes

    Sponsorship and grant payments as commitments

    Modelled as pledges with schedules, so both sides see what is owed and what has arrived.

  • What changes

    Impact reporting the funder can read

    The same evidence chain the nonprofit publishes, scoped to the funder's contributions.

The same week, twice

How a companies & foundations week runs before and after

Left is the week as this seat describes it today. Right is the same week once the record carries the terms. Nothing on the right is claimed as available — the status badge above governs that.

Today

  1. TodayMatching requests arrive by email, are approved in a spreadsheet, and reach the nonprofit as an unexplained lump sum.
  2. The gapThe nonprofit cannot tie the payment to the employee gifts it matched, so soft credit is guesswork.
  3. The opportunityIf both sides share the object model, matching reconciles itself.

Prepared

  1. 1Matching that arrives explainedA matched payment references the employee gifts it matches, so soft credit and receipting are correct on arrival.
  2. 2Sponsorship and grant payments as commitmentsModelled as pledges with schedules, so both sides see what is owed and what has arrived.
  3. 3Impact reporting the funder can readThe same evidence chain the nonprofit publishes, scoped to the funder's contributions.

Described state, governed by the status label on this page.

Where you work

The surfaces you would live in

  • Company dashboard

    Employee giving, matching queue and sponsorship commitments.

  • Matching queue

    Requests with the employee gifts they reference.

Not ready yet

What we cannot do for you today

  • This is Release 2. Company and foundation surfaces exist as labelled prototypes on illustrative data.
  • Grant compliance management is explicitly out of scope.

Metrics this seat owns

  • Match completion rate
  • Time from request to matched payment
  • Correctly attributed soft credits

The funder side of the same lifecycle

Employee giving, matching queues, sponsorships and grant payments are the other end of the contribution Beneora already models. Prototypes exist; this is deliberately Release 2 work.

Matching requests arrive by email, are approved in a spreadsheet, and reach the nonprofit as an unexplained lump sum.

Companies & foundationsRelease 2 — described, not yet built.

Design-partner program

Tell us what companies & foundations needs first

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.