Jortt: Send sales orders to Jortt

This setting has no effect for Jortt. When APIcenter sends an order to Jortt, it looks up the customer by email address and creates the customer in Jortt when it does not exist yet. There is no guest customer in this process, so you can leave this setting as it is. Off by default.

The email address of the customer in Jortt that APIcenter uses when Enable use of default debtor is on and the order contains no customer email address (or always, when Force the usage of the default debtor is on). APIcenter then looks up this email address in Jortt. When no customer with this email address exists, APIcenter creates a new customer in Jortt with the data of the order. Use a valid email address, otherwise the order fails with an error.

This setting has no effect for Jortt. The standard data mapping does not send a price list group to Jortt, so this value is not used. You can leave the field as it is; the default value ***** is not used for Jortt.

This setting has no effect for Jortt. APIcenter always looks up the customer in Jortt by email address. When the customer does not exist, APIcenter creates it in Jortt, instead of falling back to a default customer.

Turn this on to send a send method with every invoice that APIcenter creates in Jortt, so you decide whether you or Jortt sends the invoice to the customer. You enter the value in Specify how you to handle the invoicing of your customers: self or email. Without a value, sending the order stops with an error. On by default.

This setting has no effect for Jortt, because Jortt has no customer group field and the standard data mapping to Jortt does not send a customer group. Leave it off: when you turn it on without a value in Value to use as default customer group, sending orders stops with an error. 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. Leave it off (default).

Turn this on to use a default customer in Jortt for orders. For Jortt only the email address counts: enter it in Default debtor email address. With Force the usage of the default debtor you choose whether every order uses it or only orders without a customer email address. If this is on but no email address (or ID) is filled in, orders fail with an error. Off by default.

This setting has no effect for Jortt. Jortt has no customer group field and the standard data mapping to Jortt does not send a customer group, so there is nothing to force. You can leave it off. Off by default.

When on, APIcenter replaces the email address of the customer on every order with the one from Default debtor email address, so every invoice is booked on that one customer in Jortt. When off (default), the default email address is only used when the order contains no customer email address. This only works when Enable use of default debtor is on and the customer with that email address exists in Jortt.

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 for Jortt. The Jortt flows do not use a price list group: the standard data mapping does not send one to Jortt. 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. 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 a value from the other application into the send method of the Jortt invoice: self (you send the invoice yourself) or email (Jortt sends the invoice to the customer by email). The table is only used when the source sends a value, and it is ignored as long as Force the value used for the send method is on, which is the default for Jortt. Turn that setting off to use the mapping table. 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.

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).

By default APIcenter sends the prices of the order lines to Jortt excluding VAT. Turn this on to send prices including VAT for private customers instead; for companies the prices stay excluding VAT. A customer counts as private when the order has no company name, or when the customer is registered in Jortt as a private customer (an existing Jortt customer without that information is treated as private). Off by 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.

This setting has no effect for Jortt. APIcenter looks up customers in Jortt by email address, not by an ID, so this value is not used. Use Default debtor email address instead.

This setting has no effect for Jortt. Jortt has no customer group field and the standard data mapping to Jortt does not send a customer group, so 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.

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.

This setting has no effect for Jortt. Jortt has no administration field and the standard data mapping to Jortt does not send an administration, so you can leave this field empty.

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.

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

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

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.

The code APIcenter puts on the extra order line for payment costs. This field is required when Add order line for payment costs is on; without it the order fails with an error. Jortt does not use item codes and APIcenter does not look this code up in Jortt. The code is only used as the description of the line when you leave Description to use for the order line for payment costs empty.

The code APIcenter puts on the extra order line for billing costs. This field is required when Add order line for billing costs is on; without it the order fails with an error. Jortt does not use item codes and APIcenter does not look this code up in Jortt. The code is only used as the description of the line when you leave Description to use for the order line for billing costs empty.

The code APIcenter puts on the extra order line for commission. This field is required when Add order line for commission is on; without it the order fails with an error. Jortt does not use item codes and APIcenter does not look this code up in Jortt. The code is only used as the description of the line when you leave Description to use for the order line for commission empty.

The code APIcenter puts on the extra order line for shipping costs. This field is required when Require order line for shipping costs is on; without it the order fails with an error. Jortt does not use item codes and APIcenter does not look this code up in Jortt. The code is only used as the description of the line when you leave Description to use for the order line for shipping costs empty.

Text that APIcenter places in front of the order number, for example WEB- turns order 1001 into WEB-1001. This helps you recognise orders from a specific source in Jortt, or keep order numbers unique when you have several stores. The prefix is only added when the data mapping of the order number uses the micro-function for the order prefix; the standard data mapping to Jortt does not use it.

Text that APIcenter adds to the end of the order number, for example -NL turns order 1001 into 1001-NL. This helps you recognise orders from a specific source in Jortt, or keep order numbers unique when you have several stores. The suffix is only added when the data mapping of the order number uses the micro-function for the order suffix; the standard data mapping to Jortt does not use it.

This setting has no effect with the standard data mapping to Jortt. The VAT percentage of the extra invoice line for billing costs comes from the amounts of the order. When the percentage cannot be determined, APIcenter uses Default tax rate billing costs. The tax class is only used when you map it yourself in the data mapping of the flow.

This setting has no effect with the standard data mapping to Jortt. The VAT percentage of the extra invoice line for commission comes from the amounts of the order. When the percentage cannot be determined, APIcenter uses Default tax rate commission. The tax class is only used when you map it yourself in the data mapping of the flow.

This setting has no effect with the standard data mapping to Jortt. The VAT percentage of the extra invoice line for payment costs comes from the amounts of the order. When the percentage cannot be determined, APIcenter uses Default tax rate payment costs. The tax class is only used when you map it yourself in the data mapping of the flow.

This setting has no effect with the standard data mapping to Jortt. The VAT percentage of the extra invoice line for shipping costs comes from the amounts of the order. When the percentage cannot be determined, APIcenter uses Default tax rate prices. The tax class is only used when you map it yourself in the data mapping of the flow.

The text APIcenter puts on the extra invoice line for billing costs, for example Invoice costs. If you leave it empty, APIcenter uses the item code from Default item code for billing costs as the description of the line. Jortt needs a description on every invoice line.

The text APIcenter puts on the extra invoice line for commission, for example Commission. If you leave it empty, APIcenter uses the item code from Default item code for commission as the description of the line. Jortt needs a description on every invoice line.

The text APIcenter puts on the extra invoice line for payment costs, for example Payment costs. If you leave it empty, APIcenter uses the item code from Default item code for Payment Costs as the description of the line. Jortt needs a description on every invoice line.

The text APIcenter puts on the extra invoice line for shipping costs, for example Shipping costs. If you leave it empty, APIcenter uses the item code from Default item code to use for shipping cost order line as the description of the line. Jortt needs a description on every invoice line.

Determines what APIcenter creates in Jortt for each incoming order. Jortt only supports Sales Invoice (default), so leave it on that value. With any other choice the Send Sales Order flow fails with an error saying that Jortt only supports sending orders as Sales Invoice.

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.

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. The data that APIcenter sends to Jortt for an order has no shipping method field. To get shipping costs on the Jortt invoice, use Require order line for shipping costs instead. Leave this setting off (default).

This setting has no effect for Jortt. The data that APIcenter sends to Jortt for an order has no shipping method field, and the standard data mapping does not send one. Leave it off (default).

This setting has no effect for Jortt. The data that APIcenter sends to Jortt for an order has no shipping method field, so there is nothing to map. Leave it off (default).

This setting has no effect for Jortt. The data that APIcenter sends to Jortt for an order has no shipping method field, so this value is not used. Leave the field empty (default).

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

• Use default (default): APIcenter uses Value to use as the default shipping 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, because the data that APIcenter sends to Jortt for an order has no shipping method field.

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

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

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

This setting has no effect for Jortt. The data that APIcenter exchanges with Jortt has no warehouse field, so this value is not used. Leave the field empty (default).

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

• Use default (default): APIcenter uses Value for the default warehouse id, if the default warehouse 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 warehouse field.

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.