When integrating IAMD. ERP with Octopus to manage accounting processes, the question arises whether entries sent from IAMD. ERP are sent to Octopus can be automatically marked as "to be checked" in Octopus. This article clarifies the possibilities and limitations of status changes of entries in Octopus via the link with IAMD. ERP.
Accounting automatically 'verifiable' in Octopus?
Unfortunately, it is not possible to check bookings written by IAMD. ERP in Octopus to be automatically marked as 'to check'. This limitation is based on the nature of the integration between the systems and decisions made by Octopus.
Octopus has indicated that bookings coming in via an API link are assumed to be correct. This is in contrast to entries coming from UBL files, whose origin may vary (such as OCR) and which are not always 100% reliable. Therefore, such bookings should be checked.
The Octopus API does not provide a way to enable "check" status for bookings received via this method. This is a deliberate choice by Octopus, based on confidence in the accuracy of bookings sent via API links.
Bookings sent from IAMD. ERP to Octopus will be approved immediately. This is a direct result of Octopus choosing to consider bookings via API links as correct. While this means there is no direct way to automatically mark these bookings as "to be checked," it underscores the efficiency and confidence in the data integrity provided by these systems.
For users of IAMD. ERP who want to accurately track their entries in Octopus, it is important to recognize that this automatic approval is part of the designed workflow. Should there be a need for a verification process, this should be organized separately within the organization.