This guide is for anyone who wishes to import data from their own system into OnlineFundraising.
Below you will find explanations for the different columns.
You can download our template at the bottom of this guide.
⚠️ Important: Please do not create hidden fields, calculations, or anything else that is not part of the template.
If we need to adjust the document, we will invoice separately for the time spent.
Column Explanations
Contact – Contact Information (with examples)
contactName
Full name
firstName
First name
lastName
Surname
companyName
Company name
birthDate
Date of birth without personal ID (CPR). Must be entered as a date, not text.
Format: YYYY-MM-DD
nationalId
Date of birth with personal ID (CPR). Must be entered without a dash.
businessCode
Company registration number (CVR).
address
Street name
address2
Street name line 2
postCode
Postcode
city
City
countryCode
Country code, e.g. DK
msisdn
Phone number including 45, but without the ‘+’ sign.
Format: 4511223344
email
Example: email@email.dk
externalId
Optional field – can be used as a customer/member number or in CRM integration.
externalLink
Optional field, e.g. CRM link
Agreement – What Is Being Paid?
agreementName
Name of the payment agreement (e.g. Membership, Donation).
amount
Amount without comma, e.g. 100
Pence/øre can be included: 100.20
taxDeductable
Is the amount tax-deductible?
Enter: true or false
paymentRequired
Indicates whether payment is mandatory for the donor (true) or optional (false). This is used later for payment collection and communication.
If paymentRequired is set to true for a Betalingsservice automatic withdrawal, and the donor cancels in their online banking, we will still send a payment slip if you are on the Betalingsservice Total solution.
If set to false, the subscription becomes inactive and no payment slip is sent.
Even if set to false, you can still contact the donor by viewing their inactive subscription.
Enter: true or false
Schedule – When Will the Agreement Be Collected?
In 99.99% of cases, it is sufficient to fill in scheduleType and nextDueDate (found under subscription).
Other columns are for special requirements — please contact us if needed.
scheduleType
Accepted values: Monthly, Quarterly, Halfyearly, Yearly, Custom
scheduleBaseTier
Based on what is set in scheduleCalendarUnit, specify which month, week, or day.
Example: 1–12 if scheduleCalendarUnit is Month, or 1–52 if Week.
scheduleFixedDay
If the collection is set to a specific day of the month, enter that day here (1–28).
scheduleEveryOther
For every-other collection.
Example: scheduleEveryOther = 2 and scheduleCalendarUnit = Month → billed every second month.
scheduleCalendarUnit
Accepted values: Month, Week, Day
scheduleSelectedSet
Use "[ ]" for specific collection months.
Example: If June should be excluded, enter: [1,2,3,4,5,7,8,9,10,11,12]
purposeAccountingCode
Optional code indicating the purpose.
Max. 32 characters, numbers and letters only.
communicationCollectionGuid
Unique ID for the communication linked to the agreement.
You can find this by opening the communication in OnlineFundraising and checking the URL.
Leave blank if unsure.
externalId
Optional – can be used as customer/member number or in CRM integration.
Subscription – Additional Information for Payment
startDate
When does the agreement start?
Format: YYYY-MM-DD
originTs
Original timestamp of the agreement in another system.
expiresAfterDate
If the agreement should expire, enter date here.
Format: YYYY-MM-DD
nextDueDate
Next scheduled collection date.
Format: YYYY-MM-DD
externalId
Optional – can be used as customer/member number or in CRM integration.
externalLink
Optional – e.g. CRM link
Payment Method – How Is It Paid?
paymentMethodType
Accepted values: Card, MobilePaySingle, MobilePaySubscriptions, Betalingsservice, FIK, SMS
EAN numbers are not supported.
paymentGatewaySubscriptionToken
Used for card extractions/MobilePay.
paymentMethodAccountingCode
Not supported — leave blank.
bsSendAsPaymentSlip
Indicates whether a payment slip should be sent.
Enter: true or false
bsMandate
Unique number per agreement defined by Betalingsservice.
Contact Betalingsservice if unsure.
bsCustomerNumber
Unique number defined by your organisation (membership or customer number). Provided to Betalingsservice.
bsSortCode
Leave blank unless otherwise agreed.
bsAccountNumber
Leave blank unless otherwise agreed.
bsGuid
Leave blank.
Data Set – Additional Information to Store
Optional field.
dataset_{{key1}}
Replace {{key}} in the column name and insert the value.
How to Upload
Name your file with your organisation’s name and the date, e.g.:myorganisation-12_19.xlsx
Upload the file to our encrypted server here: upload.onlinefundraising.dk
⚠️ Important: You must notify us after uploading, as we do not receive an automatic alert.
Frequently Asked Questions
Where do I set an EAN number?
Not supported.
If a contact has multiple agreements
Create one row per agreement.
What if the data is not available?
Leave the field blank.
What to enter if a payment slip should be sent?
If you have the Total solution and a payment slip should be sent, leave the Mandate field empty.
If you still have questions, contact us at support@onlinefundraising.dk