All about jortt
Jortt: Get payments from Jortt
Get paid invoices from Jortt as payments, for example to mark the order as paid in your webshop.
Updated November 9, 2026
This flow gets the invoices that are paid in Jortt and passes them on as payments to another application. For example, a webshop can then mark the order as paid.
How it works
- APIcenter gets the invoices from Jortt that have the status paid. Invoices that are not paid are not passed on.
- Each paid invoice is passed on as a payment to the other application of the integration.
- By default, APIcenter passes on four fields: the invoice number as reference, the status of the invoice, the creation date and the amount. The amount is filled from the amount due that Jortt shows on the invoice. Check under Data mapping that this is the amount your other application expects. The invoice total, with and without VAT, is also available.
What you need first
- Jortt is connected. See Connect Jortt to APIcenter.
- The target application must support receiving payments.
Tips
- The invoice number is the reference of the payment. Check that the other application can link this reference to the right order. Does it need another value, for example the customer reference? Change it under Data mapping. See Data mapping.
- Is a payment missing in the target system? Check in Jortt that the invoice has the status paid.
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.
Stop flow when mapping of fields fails
Datamapper SettingsDetermines what happens when a field in the data mapping cannot be mapped, for example because the value has the wrong type or format. When on (default), the flow stops with an error in the activity log, so nothing incomplete is passed on. When off, the flow continues and the field that could not be mapped is skipped; a note is added to the flow results. For Jortt this setting is available in the Get Payment flow.
Used by file-based connections, such as CSV files on an SFTP server, where the column headers of a file are translated with a mapping table. Jortt connects through its API and not through files, so this setting has no effect for Jortt. Leave it at the default (Use default).
Enable URL Encoding of data in the endpoints of the source application
General flow settingEncodes 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.
Enable URL encoding of data in endpoints
General flow settingUse administration mapping table
General flow settingThis 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).
What to do with a value that cannot be mapped using the mapping table
General flow settingDecides 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.
Notifications Email address
NotificationsNotifications Slack webhook
NotificationsNotifications frequency
NotificationsReceive Notifications
NotificationsAmount to process
Run behaviourThe maximum number of customers or invoices APIcenter retrieves from Jortt per run. The default is 10. A higher number clears a backlog faster but makes each run take longer. In the Get Payment flow this number does not limit how many payments are retrieved in a run.
Last execution time
Run behaviourMaximum number of pages to retrieve
Run behaviourThe 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.
Offset
Run behaviourAPIcenter keeps track of where the flow stopped in the list of customers or invoices in Jortt, and uses this number to continue in the next run. APIcenter updates it automatically after each run, so you normally do not change it. The default is 0, which starts at the beginning of the list. Only change it when APIcenter support asks you to.
Run at specific times
Run behaviourUse last modify date
Run behaviourThis setting has no effect for Jortt. APIcenter retrieves customers and paid invoices from Jortt page by page (see Offset and Amount to process) and does not filter on a date. Changing the date does not make the flow retrieve older or newer records, so leave it at its default.
Use page size
Run behaviourThe 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.