It is possible to create or update some of Fenerum entities in bulk by importing csv or excel file. In this article we will cover the required format for these files and show you how to perform the actual import in your Fenerum app.
Right now we support imports of the following object types (click on the type to download an example file in given format):
Below we discuss the details for each one. The required fields (columns) are signified with bold font. Fields marked with *
are meaningful only if you have a corresponding "extra" feature enabled, otherwise you shouldn't include them in the import file.
If you wish to update obejcts which don't have a code attribute you must provide additional id column with the object uuid.
UI
To import data simply head to the Import data section of settings. There you'll find a simple form. Choose what kind of object you want to import and provide your file. You'll get detailed response in case of problems with parsing your file otherwise the objects will be created and you'll see a success message stating how many objects were created.

File requirements
General
For csv file delimiter should be a comma.
We are currently supporting only creating of new objects, you can't use files to update already existing objects.
Account
company_name
code (eg. ID from external system)
language (
en/es/da
defaults toen
)legal_address
legal_zipcode
legal_city
legal_country
ean_invoicing* (
yes/no
defaults tono
)ean_number*
legal_vat_number
billing_same_as_legal (
yes/no
defaults toyes
)billing_address
billing_zipcode
billing_city
billing_country
erp_id (if you have an object corresponding to this account in your ERP system provide it's id here to avoid creating dupliacte entries)
Note that ean_invoicing and ean_number fields are only applicable if you have an EAN feature enabled.
See an example file.
Recipient
account (here you need to provide related account's
code
(external id) value)name
email
receive_invoice
receive_payment_confirmation
receive_subscription_notifications
See an example file.
Payment Card
account (here you need to provide related account's
code
(external id) value)brand
card_number (first twelve digits must be masked eg. XXXXXXXXXXXX1234 or you can provide only the last 4 digits)
month
year
name
payment_gateway (name of your PSP. We currently support
stripe_new,
quickpay
ordibs
)payment_gateway_id (unique identifier of the card in your PSP system [note that for QuickPay it will be a subscription ID])
See an example file.
Plan
name
code (ID from external system)
collect_vat (
yes/no
defaults toyes
)vat_type (
physical/services/unknown
)description
See an example file.
Plan Terms
plan (here you need to provide related plan's
code
value)interval_type (
day/month/year
)interval_count
price
currency
backwards_charging (
yes/no
defaults tono
)revenue_group*
See an example file.
Subscription
account (here you need to provide related account's
code
value)terms (here you need to provide related plan terms'
uuid
value)start_date (eg.
2019-12-01 12:00
, if not provided will be set to the current time)end_date
quantity (defaults to
1
)collection_method (
payment_card/invoice/direct_debit
)group_on_invoice (
yes/no
defaults tono
)payment_terms (defaults to
0
)pre_renewal_invoicing (
yes/no
defaults tono
)po_number
invoice_supplement
See an example file.