Introduction

RaiseNow will interact with various entities in D365 when processing donations and payments. Which entities RaiseNow creates or modifies are described in this article with details on selected properties. For API field names please refer to the entity documentation for your current version provided in our release notes. 

Account

If a company is provided in the donation form, RaiseNow will consider this donation a company donation. This will have the following impact on the donation in D365:

• The commitment will be created as pledged by an account and the account will be linked to that commitment. 
• The address information provided with the donation will be attributed to the account, not the contact. 
• A contact will be created (if it does not exist in D365) based on the provided salutation, first name, and last name. This contact will link the account as parent account to this contact. The contact will not be linked with the commitment. 

Contact

When RaiseNow creates a contact it will set both standard D365 fields as well as fields shipped with our solution. You should be aware of the following behaviour with regards to certain fields.

Language and Gender

RaiseNow will set the language field according to the language provided in the original transaction. For example, if a donor created a donation using our Tamaro form in an English version, this field will be set with the corresponding lower case 2-letter ISO code "en". 

In addition RaiseNow will set the gender code in D365. Valid choices are "male", "female" & "neutral". See our onboarding section on correctly configuring the latter option. 

Note: RaiseNow will not set a salutation. We leave this to your followup processes to set salutation values according to your organisations guidelines. 

Commitment

RaiseNow will create a msnfp_DonorCommitment for both one-off and recurring donations. 

Campaign Activities

If the RaiseNow payment records contains a parameter stored_camapign_id containing a Dynamics Campaign Activity UUID (string), the corresponding value will be written on the donor commitment:

msnfp_donorcommitments.rnw_CampaignActivityId

You can set this value either in RaiseNow Hub when configuring your solution or if you are using a custom tamaro integration on your website, you can use the javascript API of the tamaro widget to set this value. 

You must ensure that the values you set are valid Dynamics GUIDs for the Campaign Activity. Otherwise manual error resolution will be required. 

Hint: To facilitate testing you can call the widget by appending the query parameter. For example: 

https://url-to-widget.html?rnw-stored_campaign_id={valid-dynamics-uuid}

Replace "{valid-dynamics-uuid}" accordingly. 

Designations

If the RaiseNow payment records contains a parameter stored_crm_designation_id containing a Dynamics Designation UUID (string), the corresponding value will be written on the donor commitment:

msnfp_designations.msnfp_Commitment_DefaultDesignationId

If you are using a custom tamaro integration on your website, you can use the javascript API of the tamaro widget to set this value. You currently cannot set this value for solutions in RaiseNow Hub. 

You must ensure that the values you set are valid Dynamics GUIDs for the Designation. Otherwise manual error resolution will be required. 

Hint: To facilitate testing you can call the widget by appending the query parameter. For example: 

https://url-to-widget.html?rnw-stored_crm_designation_id={valid-dynamics-uuid}#widgetdebug

Replace "{valid-dynamics-uuid}" accordingly. 

Duplicates reported on commitments

If D365 reports a duplicate for either 

• an account (rnw_accountduplicatereportedbyd365)
• a contact (rnw_contactduplicatereportedbyd365)

RaiseNow will document this on the commitment. See the article regarding duplicate management for more details on this subject. 

Cover the fee

If donors selected the cover-the-fee option in the checkout, this will be reported as rnw_committedcoverthefee on the the commitment.  

Use of funds

RaiseNow supports referencing a msnfp_designation in a donation. The touchpoint (donation form must set stored_crm_designation_id with a valid Id from D365). 

Campaign Activities

If a touchpoint provides the id of a D365 campaign activity in the field stored_campaign_id this campaign activity will be referenced in the created commitment. 

Face-to-Face 

Varoius fields are set to facility face-to-face one-off and recurring donation acquisition. 

• Use stored_marketing_location_identifier in the touchpoint to provide a place of acquisition for your donation in the D365 field rnw_marketinglocation
• Provide a valid D365 contact id in stored_crm_fundraiser_id in the touchpoint to reference the fundraiser who collected the donation. 
• Provide a Url in the touchpoint in stored_dd_document_reference to set a reference to a contract document for download.
• Provide a document reference in stored_hard_copy_record_id in the touchpoint to set a reference id for your document management system. 

Please contact RaiseNow for a list of proven partners for face-to-face donation acquisition and managament. 

Please open this image in a dedicated tab to see details. 

Transaction

RaiseNow will create a msnfp_Transaction for every donation or pledge submitted. 

Considerations for accounting and payment management

A payment submitted through a donation form has to go through several stage. For electronic payment methods such as credit card, debit card PayPal and other, RaiseNow will receive a direct payment confirmation at the time of successful submission of the donation form by a donor. 

You acquiring partner will trigger a wire transfer, usually within a couple of days after the initial donation. This transfer will contain all donations submitted within a certain time frame. You acquiring partner will provide further details for this wire transfer separately, listing all donations contained in this summary payout as well as fees collected automatically by the acquiring partner. 

Depending on your region of operation, your acquiring partner and your selected RaiseNow licensing options, RaiseNow will either only submit the initial donation to D365 or update this donation with acquiring details as well. 

On the initial payment RaiseNow will set the gross amount for the payment as well as provide the payment provider in rnw_paymentprovider. The transaction will also receive a statuscode "not booked". 

If the RaiseNow reconciliation option is active, on receiving reconciliation information from your bank and your acquiring partner, RaiseNow will update the transaction with the following information. 

• acquirer
• acquirer fees
• net amount
• gross amount
• statuscode ("paid-out")
• value date 
• acquirer transaction identifier
• recipient bank account

Cover-the-fee

If the cover-the-fee option was selected in the donation process, when registering the payment the calculated amount will be shown in the field rnw_paidcoverthefee. 

Payment Slip / QR Bill

If the transaction was created initially due to a pledge, the transaction will receive a unique payment reference. This reference can be provided to the donor in the touchpoint or via backoffice process in D365 (not implemented by RaiseNow).

You can then use this reference for matching the payment when processing camt file from a receiving bank account. 

Please open this image in a dedicated tab to see details. 

Payment Schedule

For recurring payments (subscriptions in the RaiseNow terminology), RaiseNow will create a payment schedule for the corresponding commitment in D365. The payment schedule will link to the commitment. 

Successful as well as failed payments for the recurring donation will link to both the payment schedule as well as the commitment. The link to the commitment is provided via the field rnw_donorcommitmentid that is shipped with our solution. 

Please open this image in a dedicated tab to see details.