> For the complete documentation index, see [llms.txt](https://solutions.fundraisingbox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solutions.fundraisingbox.com/platform-solutions-integrations/salesforce-nonprofit-cloud-npc/extended-data-model.md).

# Extended Data Model

The Connector is based on the Salesforce Nonprofit Cloud data model. The objects from the standard data model highlighted in green in the diagram are used by the connector to store data from FundraisingBox, establish relationships, and apply the logic embedded in the data model.

In order to enable the full use of FundraisingBox functions via the Connector, the Salesforce Nonprofit Cloud data model has been extended with additional key objects.

<figure><img src="/files/1BMEybATjJjkPl72h2MV" alt=""><figcaption></figcaption></figure>

When a donation occurs, the FundraisingBox Nonprofit Cloud Connector transfers structured records into Salesforce, including:

* **Person Accounts** for private donors
* **Business Accounts** for organizational donors
* **Gift Transactions** for each single donation
* **Payment Instruments** for payments with bank details
* **SEPA Mandate (FundraisingBox object)** for SEPA direct debit details
* **Gift Commitments** for recurring donations
* **Gift Commitment Schedules** with amount, frequency and timing details of the recurring donation
* **Campaigns** for FundraisingBox P2P fundraising campaigns
* **Gift Designations** for donation purposes
* **Gift Refunds** for refund information linked to the initial gift transaction
* **Payouts (FundraisingBox object)** for reconciliation data of e.g. stripe batch payouts
* **FundraisingBox Connector Errors (FundraisingBox object)** for validation error notification

At the same time, relevant updates from Salesforce are synchronized back to FundraisingBox, enabling a consistent and unified data experience.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://solutions.fundraisingbox.com/platform-solutions-integrations/salesforce-nonprofit-cloud-npc/extended-data-model.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.