Defining the purpose of a payment is done for each of your forms. Look to the relevant form and scroll to the area Purposes, where it is possible to set up one ore more purposes.
A purpose can be fixed, hidden or visible in the form – or you can make it possible for the member/donor to select the purpose themselves.
Define the purpose
For each purpose created in a form, the following settings are configurable:
1. Name in form
Provide the name of the purpose in Name in form. This name is visible to the donor/member filling out the form, provided Purposes are visible to them.
2. Payment rules
It is possible to configure a couple of things regarding the payment in Payment rules:
- Payments are tax deductible: If you check this setting it means that the payment will be marked as tax deductible. This information is available to you via a file export or an API (e.g. a CRM-integration). This information is not visible to the donor/member unless you provide the information in the confirmation text.
- Payment are required in dunning: Check this setting if an agreement with legal claim is created based on the payment.
If payment is required the subscription wille be stopped automatically after a period of inactivity. A subscription is considered inactive if donor/member rejects the payment contiuously. The time period is dependent on the payment method:
- Betalingsservice stops after 18 months of inactivity
- MobilePay stops after 15 months of inactivity
- Payments by card are charged immediately, hence they cannot be rejected by donor/member. Because of this subsriptions with card as payment method will not be stopped even if payment are set to required.
3. Default amount
If the payment amount is fixed for the purpose in question, you can define this in the Default amount. The donor/member will not able to override the amount using this approach. If the donor/member should be able to pick from multiple amounts, or if donor/member should be able to define the amount themselves, keep this field empty and define the options when settings up the transactional fields of the form. For instance, you can define the field Amount with multiple options (read about configuring form fields here).
4. Success landing page
Provide a URL for the page which donor/member is to be redirected to once they have submitted a form. The URL is provided in Success landing page (also referred to as confirmation page). The URL is most likely a reference to a site on your organisation's domain, e.g. yourwebsite.com/thank-you.
It is not mandatory to provide a success landing page. If it is omitted the confirmation message will be displayed on the same site which the form is embedded on.
In Communication you select the confirmation message which was created beforehand for either the purpose or the form i general.
6. Accounting code
Provide the Purpose Accounting Code in the field Accounting Code. The Purpose Accounting Code is relevant information for accounting, especially regarding bookkeeping efforts.
Personal or Shared Agreement?
If you are using a so-called shared agreement you can configure this in Choose shared agreement to overrule. If a shared agreement is selected, all of the above described settings will be defined via this agreement.
If the agreement is personal you need to provide Personal agreement name and Personal agreement description.