Business need : There are no reliable tables within Invantive to get to the right level of detail and reliability to make the bookings in our ERP. We’ve checked all tables and the one with debit/credit (JournalRunResults > JournalRunResultsByJournalRunId) doesn’t have the right level of detail (PayrollComponent_key and PayrollComponent_Description are empty). Other tables with PayrollRun data haven’t got the right level of reliability to be sure which ledger to take and whether it’s debit or credit.
The CSV currently can not be generated without using NativeScalarRequests.
The specific Loket API is essentially a wrapper around another specification. This specification is forwarded to the Loket server using the X-ReportInput header.
Calculating and setting the specification is currently not available with Invantive’s Loket driver. There are currently no plans to support it as part of the standard support. Through consulting support it could be implemented on a fee basis outside of standard support.
An alternative would be that Loket provides a meaningful default implementation. For that, Loket suggests to register it as an idea on the ideas section of Loket support portal (#213465). The same holds for automated documentation and API-generation (#213461).
After consultation with your national team we have reached out to a specialized Invantive partner and Loket. I hope they can be of assistance.