All about jortt

Jortt: Send customers to Jortt

Send customers from your webshop or CRM to Jortt. APIcenter creates new customers or updates existing ones.

Updated November 9, 2026

This flow sends customers from another application, such as a webshop or CRM, to Jortt. APIcenter creates them as a customer in Jortt, or updates them when they already exist.

How it works

  • Every customer needs an e-mail address. Without it, the customer is not sent.
  • APIcenter looks for the customer in Jortt by e-mail address. When Jortt finds exactly one customer, APIcenter uses that one. When it finds several, APIcenter picks the one with the same chamber of commerce number or e-mail address.
  • Is the customer not found? Then APIcenter creates it.
  • Is the customer found? Then APIcenter updates it, but only when Update existing customer accounts is switched on in the connection and integration settings. The name of the customer is only updated when Update name of existing customer accounts is on. The first and last name of the contact person are only updated when Update name of existing contacts is on.
  • A customer with a company name is created as a company. The name you send then becomes the contact person. A customer without a company name is created as a private person.
  • The date of birth is sent as a date.
  • After creating or updating, APIcenter reads the customer from Jortt again.

What the data mapping covers

By default, APIcenter sends the name, company, e-mail address, phone number, billing address, date of birth, chamber of commerce number, VAT number, website and reference. Other Jortt fields are available under Data mapping, such as the invoice language, the payment term, the payment method for invoices, the salutation, extra information and VAT shifted. See Data mapping.

What you need first

  • Jortt is connected. See Connect Jortt to APIcenter.
  • The other application of the integration can send customers, with at least an e-mail address.

Tips

You find all settings for this flow below, each with its own explanation.

Settings

The settings you see in the dashboard, with what each one does.

When on, APIcenter always uses the default payment term from default payment terms id, even if the data from the source already has one. When off (default), the default is only used when the data has no payment term. This only has effect when Make use of a default payment terms id is on. For Jortt, the payment term is only sent when APIcenter creates a new customer in Jortt from an order.

This setting has no effect with the standard data mapping to Jortt, which does not send a payment method from the order. It only has an effect when you map the payment method yourself in the data mapping of the flow. Off by default.

When on, APIcenter always uses the value from Specify how you to handle the invoicing of your customers as the send method of the invoice, even if the source sends another value. When off, that value is only used when the order contains no send method. This only works when Enable the send method setting is on, and only for sending sales orders: the Jortt customer data has no send method, so it has no effect when sending customers. On by default.

This setting has no effect with the standard data mapping to Jortt, which does not send a payment method from the order. Leave it off unless you map the payment method yourself: when you turn it on without a value in Value for the default payment method id, sending orders and customers stops with an error. Off by default.

Turn this on to use the payment term from default payment terms id when the data from the source contains none. Use Force the usage of the default payment terms if APIcenter must always use it. For Jortt the payment term is only sent when APIcenter creates a new customer from an order (Send Sales Order flow). Off by default.

Decides who sends the invoice to your customer. Use self (default) when you send the invoice yourself. Use email when you want Jortt to send the invoice directly to the email address of your customer. The value is sent to Jortt as the send method of the invoice when APIcenter sends a sales order; when sending customers it has no effect.

This setting has no effect for Jortt in the standard configuration. The standard data mapping does not send a payment method to Jortt, so there is nothing to map. Leave it off (default).

Use a mapping table to translate the payment term from the other application into the payment term that Jortt expects, a number such as 14 or 30. In the Send Sales Order flow it is only sent when APIcenter creates a new customer in Jortt; existing Jortt customers are not changed. The standard data mapping of the Send Customer flow does not send a payment term. Values that are not in the table are handled by What to do with a value that cannot be mapped using the mapping table. Off by default.

This setting has no effect for Jortt. The Jortt flows do not use a price list group: the standard data mapping does not send one to Jortt, so there is nothing to map. Leave it off (default).

This setting has no effect with the standard data mapping to Jortt, which does not send a payment method from the order. The value only reaches Jortt when you map the payment method yourself in the data mapping of the flow. Otherwise you can leave this field empty.

Decides what happens when the payment terms mapping table has no row for a value from the incoming data.

  • Use default (default): APIcenter uses default payment terms id, if Make use of a default payment terms id is on; otherwise the field stays empty.
  • Use value: the original value is sent to Jortt unchanged.
  • Ignore value: the field stays empty.

Decides what happens when the price list group mapping table has no row for a value from the incoming data.

  • Use default (default): APIcenter uses Default price list group, if that default is switched on; otherwise the field stays empty.
  • Use value: the original value is passed on unchanged.
  • Ignore value: the field stays empty.

This has no effect for Jortt, because the standard data mapping does not send a price list group to Jortt.

Decides what happens when the payment method mapping table has no row for a value from the incoming data.

  • Use default (default): APIcenter uses Value for the default payment method id, if that default is switched on; otherwise the field stays empty.
  • Use value: the original value is passed on unchanged.
  • Ignore value: the field stays empty.

This has no effect for Jortt in the standard configuration, because the standard data mapping does not send a payment method to Jortt.

default payment terms id

Customer Settings

The payment term APIcenter uses as default when the data from the source has none. Enter it as a number, for example 14 or 30. In the Send Sales Order flow the standard data mapping puts it on the Jortt customer, so it is only sent when APIcenter creates a new customer; existing Jortt customers are not changed. The standard data mapping of the Send Customer flow does not send a payment term: map it yourself to the Jortt field payment_term if you need it there. The value is only used when Make use of a default payment terms id is on.

Encodes values in request URLs when this flow retrieves data from Jortt. These requests only contain page numbers, invoice statuses and Jortt customer ids, so you rarely need this. Only works when Enable URL encoding of data in endpoints is on as well. Off by default.

Use administration mapping table

General flow setting

This setting has no effect for Jortt. The data that APIcenter exchanges with Jortt has no administration field, so there is nothing to map. Leave it off (default).

Decides what happens when the administration mapping table has no row for a value from the incoming data.

  • Use default (default): APIcenter uses Default administration id, if that default is switched on; otherwise the field stays empty.
  • Use value: the original value is passed on unchanged.
  • Ignore value: the field stays empty.

This has no effect for Jortt, because the data that APIcenter exchanges with Jortt has no administration field.

This setting has no effect for Jortt. Jortt has no sales VAT code field on customers and the standard data mapping to Jortt does not send one, so you can leave this field empty. The VAT percentage of an invoice line comes from the amounts of the order.

This setting has no effect for Jortt, because Jortt has no sales VAT code field on customers and the standard data mapping to Jortt does not send one. Leave it off: when you turn it on without a value in Default customer sales vat code id, sending orders and customers stops with an error. Off by default.

This setting has no effect for Jortt. Jortt has no sales VAT code field on customers and the standard data mapping to Jortt does not send one, so there is nothing to force. You can leave it off. Off by default.

This setting has no effect for Jortt in the standard configuration. The standard data mapping does not send a customer sales VAT code to Jortt, so there is nothing to map. Leave it off (default).

Decides what happens when the customer sales VAT code mapping table has no row for a value from the incoming data.

  • Use default (default): APIcenter uses Default customer sales vat code id, if that default is switched on; otherwise the field stays empty.
  • Use value: the original value is passed on unchanged.
  • Ignore value: the field stays empty.

This has no effect for Jortt in the standard configuration, because the standard data mapping does not send a customer sales VAT code to Jortt.

Decides what happens when a payment journal mapping table has no row for a value: Use default (default) uses the default journal if that default is switched on, Use value passes the original value on unchanged and Ignore value leaves the field empty. The Jortt flows do not use payment journals, so this setting has no effect for Jortt. Leave it at the default.

Notifications frequency

Notifications

Receive Notifications

Notifications

The maximum number of pages APIcenter reads when it repeats a request to get a list in several pages. The Jortt flows read one page of customers or invoices per run (see Offset), so this setting has no practical effect for Jortt. The default is 20; you do not need to change it.

Use page size

Run behaviour

The number of records per page when APIcenter requests a list in several pages. The requests that the Jortt flows send for customers and invoices do not contain a page size, so this setting has no practical effect for Jortt. The default is 50; you do not need to change it.

This setting has no effect for Jortt in the standard configuration. Jortt gets the VAT percentage of each order line, not a tax class (VAT code), and the standard data mapping does not send a tax class. Leave it off (default).

This setting has no effect for Jortt in the standard configuration. Jortt gets the VAT percentage of each order line, not a tax class (VAT code), and the standard data mapping does not send a tax class. Leave it off (default).

This setting has no effect for Jortt in the standard configuration. Jortt gets the VAT percentage of each order line, not a tax class (VAT code), and the standard data mapping does not send a tax class, so there is nothing to map. Leave it off (default).

This setting has no effect for Jortt in the standard configuration. Jortt gets the VAT percentage of each order line (rounded to a whole number), not a tax class (VAT code), and the standard data mapping does not send a tax class. Leave the field empty (default).

Decides what happens when the VAT mapping table has no row for a value from the incoming data.

  • Use default: APIcenter uses Value for the default tax id (exclude '%'), if that default is switched on; otherwise the field stays empty.
  • Use value: the original value is passed on unchanged.
  • Ignore value (default): the field stays empty.

This has no effect for Jortt in the standard configuration, because the standard data mapping does not send a tax class to Jortt.

Still need help?

Ask the support assistant in your dashboard or create a support ticket.

Go to support