Exports is a package of the reports that are selected in one transfer. Follow the Exports flow when developing an external integration .
For instance, if four reports from two different employees are selected to be transfered, depending on settings of the integration, these can either be sent report by report, expense by expense or grouped per employee. This is referred to as Exports groupings.
Exports flow
Below is a schematic image on the flow when reports are exported to an integration using a webhook.
- Web hook call
- Get export vouchers
- Validate and Process - In Get export vouchers there is a list of vouchers including booking/payroll information. Validate each voucher, and process it in the external system.
- Update status
Exports groupings
When the a package of reports are sent in to a custom integration, the bookkeeping information can be grouped in a number of ways, depending on the customer needs in combination with what the receiving system can process.
These are possible groupings of Exports.
Export list types | API listType |
---|---|
One voucher per report (grouped per account/salary type) | REPORT_PER_ACCOUNT |
One voucher per report | REPORT_PER_EXPENSE |
One voucher row per expense | REPORT_PER_EXPENSE_PAID |
One voucher row per report | REPORT_PER_REPORT_PAID |
One voucher row per user | USER_PER_REPORT_PAID |
One voucher per user (grouped per account/salary type) | USER_PER_ACCOUNT |
One voucher per user | USER_PER_EXPENSE |
One voucher per expense | EXPENSE |
These will be configured by Findity when setting up a new branded integration. Any of these can be selected, but all selected variants needs to be tested in the integration.