
NGO Partnership Delivery Formats: Five Scoped Contributions for Energy Vendors
Compare five NGO partnership delivery formats for clean energy vendors, with defined outputs,...

Reconcile partner referrals with an event-to-payment ledger for source history, duplicate decisions, conditional rewards, approval evidence and actual payouts.
A partner referral event-to-payment ledger lets a contractor trace an introduction through attribution review, earned-fee approval and actual payout. Partner attribution answers two separate questions: where an opportunity came from and whether a fee has been earned. A campaign link can help with the first. It cannot resolve the second without agreed program rules and a reliable project record.
Give each submission a reference number. Record the submitting partner, timestamp, customer request, permission evidence and related property or organization. Link it to the sales opportunity rather than overwriting an existing contact’s history.
Keep the original source and later influences separately. If a roofer introduces a building owner who later attends a webinar, both facts can matter. Do not automatically award the commission to whichever campaign was clicked last.
Document the rule for an existing customer, an already active project and two partners referring the same building. Assign disputed referrals to a reviewer. Preserve both submissions and the decision reason instead of silently deleting the losing record.
For an explicitly hypothetical example, Partner A introduces a facility manager in March; Partner B submits the same planned retrofit in April. A program might credit the first accepted introduction within its agreed window. That is an example rule, not a universal entitlement.
Partners often need to know whether a referral was accepted, needs more information or reached the agreed payment milestone. They rarely need the customer’s bills, detailed financing or every sales note.
Explain customer-data sharing at intake. The privacy commissioner’s guidance emphasizes making purposes and recipients understandable. Configure access so a partner cannot see another partner’s referrals. Test this with separate sample accounts before using real records. Privacy guidance.
Use separate fields for estimated commission, approved amount and paid amount. Link approval to the agreement’s actual trigger and evidence, such as completed installation or collected customer payment. A “closed won” label alone may be too early.
Automation can prepare a finance task, but a person should resolve exceptions and confirm payment details. Reconcile the referral ledger with invoices and cancellations before closing the period.
Review missing source records, duplicate disputes and unpaid approved amounts regularly. These measures reveal whether the process is trustworthy without relying on an invented benchmark for referral growth.
For this fictional example only, the agreed reward is $300 after a completed project and collected customer payment. The exact terms and evidence would govern a real programme.
| Event | Record | Effect on payment status |
|---|---|---|
| Partner A submits an introduction. | Referral R-024 linked to opportunity O-051, source and contact evidence retained. | No earned amount yet. |
| Partner B later submits the same project. | Both submissions preserved; reviewer applies the agreed attribution rule. | Disputed attribution awaits a documented decision. |
| Attribution decision recorded. | Relevant rule version, evidence and decision reason linked. | Expected reward identified, still conditional. |
| Project completes and customer payment is confirmed. | Required milestone and finance evidence linked. | Finance reviews whether the trigger is satisfied. |
| Authorized fee approval. | $300 approved with responsible reviewer and date. | Approved, not yet paid. |
| Payout reconciled. | Payment reference, date and approved amount matched. | $300 recorded as paid. |
Compare approved amounts with payments and unresolved disputes at the period close. An estimated commission should not appear as paid, and a signed contract should not replace a later trigger required by the agreement.
If a cancellation or correction occurs, add an event and the reviewed consequence. Preserve the earlier approval and payment evidence rather than deleting a record to make the totals reconcile.
Share only the status the partner needs under the actual arrangement. Internal finance evidence and customer details can remain controlled while the partner receives an understandable decision and route for questions.

Compare five NGO partnership delivery formats for clean energy vendors, with defined outputs,...

Use co-marketing templates for clean energy partners to document the brief, landing-page...

Analyze clean energy sales delays with defined intervals, decision dependencies, open-case age...