In this post I will try to give a short overview of the two accounting models that are used in Reviso, the differences, and what this means for an integration partner.
All countries are running with the model called International Ledgers as the default option. This means that all new agreements are created with this model. Spain and Italy are only using this model, while the other countries are transitioning from Classic Journals to International Ledgers. Currently, this transition happens on a voluntary basis, with agreements running Classic Journals having the option of migrating to the other model.
International Ledgers are being actively developed, while no new features will be added to Classic Journals. Similarly, the REST API is being actively developed, while the SOAP API will not get any new features.
There are no specific plans on when the Classic Journals and SOAP API will be fully retired, but it is continously being evaluated.
The differences between the two model are found in these areas:
- Vouchers and invoices data model
- UI Layout
- API support
- Support going forward
The data model is different, as Classic Journals works with a daybook (or cashbook) and the entries that forms a voucher is put into that daybook, and then the daybook can be booked. The logic for what entries that form a voucher is basically that they have the same voucher number and that they are in the same accounting year.
In International Ledgers vouchers are specific entities that are created as such. Thus, the entries are created specifically as lines on a voucher. There is no notion of daybook, but instead each voucher is attached to a number series, making it possible to segregate the vouchers using the number series.
The two models are using a different UI, both in the way the menus and navigation are handled, and for the editing of vouchers.
The REST API supports the International Ledgers model using the vouchers module. Daybooks are not exposed through the REST API hence it is not possible to create vouchers in the Classic Journals model using the REST API.
The SOAP API supports the Classic Journals model using the different Cashbook methods. These methods are blocked for agreements that run International Ledgers.
Both apis can be used to handle other data entities, such as accounts and customers.
As an integration partner this has a couple of consequences. If you integration is not creating vouchers, nor invoices – the impact is relatively low, as these scenarios still work for both SOAP and REST.
If you are creating vouchers you will have to consider how to best approach it:
- If you already have a SOAP based integration it will work for now for agreements running Classic Journals, but it is going to be tricky for you to acquire more users, as no new agreements will be able to use it.
- If your customers are running International Ledgers you will need to implement you integration using REST. This integration will not be able to target customers using Classic Journals then.
- If your customers are running Classic Journals you will not be able to write any vouchers logic using REST.
If you have any questions or concerns, do not be afraid to contact us at email@example.com.