The Interface will transfer all Supplier Accounts, along with any subsequent modifications, from Opera into Zahara.
The Interface will automatically create the Zahara "Nominal Codes" utilising the Opera Supply Codes.
Zahara for familiarity, allow fields to be renamed to match the equivalent fields in Opera.
The Interface will transfer all the VAT Codes available in Opera into the Zahara Tax Codes List on the first sync - and subsequently any amendments.
Sync from Opera into Zahara
The ZaharaO3 interface, extracts all necessary static data from Opera 3/Opera SE and updates Zahara. This includes Suppliers, Supplier Codes, VAT Codes, Cost Centres and Advanced Nominal Fields - to be available automatically in Zahara.
If utilised in Opera, the Interface will transfer all the Cost Centres from Opera into Zahara creating Cost Codes in Zahara. Again the default Zahara field name can be changed to mirror the Opera field description.
The Interface will transfer all the Projects from the Opera Nominal Ledger into Zahara so you have immediately all the projects available to be added to your Purchase Orders. The list of projects is automatically updated with any changes or new records added in Opera.
Once purchase transactions have been processed using the extensive features of Zahara the Interface will transfer all selected invoices to the relevant suppliers account in the Opera purchase Ledger.
Opera then does what is does best in managing the settlement of Invoices.
Sync from Zahara into Opera
When the Manual Exporting of Invoices option is enabled within the Business Settings of the Zahara Unit, the system displays an EXPORT button which is only available for the authorised users. These users are able to select which invoices have to be exported and after clicking on the Export button the Zahaara O3/SE Interface transfers the data into Opera and automatically creates the Invoices in the Purchase Accounts.
Opera - Zahara
As an additional feature to accommodate any existing coding structure within Opera – perhaps if both the advanced nominal fields are utilised - the ZaharaO3 integration tool also allows you to map Opera fields to any of the Zahara analysis codes.
This provides the flexibility to accommodate most devised coding structures in Opera.
As an example, it may be necessary to map the Zahara Division to the Opera Cost Centre.
The latest release of Zahara now allows for the purchase order fields to be renamed to reflect the naming convention used in Opera making data entry more familiar.