The export and import of data between DATEV and SAP Business One was at the top of the tax consultants' wish list as SAP B1 became more widespread. This was the starting point for the Versino Financial Suite and continues to be one of the reasons for SAP Business One users and their tax consultants to look into the subject.
DATEV financial accounting the standard per se
DATEV Financial Accounting is a proven solution for medium-sized companies and tax consultants to map their clients' accounting. Companies that use SAP Business One already have many of the financial management functions, but often choose to transfer their bookings to DATEV Financial Accounting.
SAP Business One & DATEV - Standard is not enough
Although SAP Business One has its own standard DATEV interface, this can only partially fulfil the growing requirements of SAP Business One users and the tax consultants involved. Both sides often complained about many hours of troubleshooting and reworking to check, synchronise and transfer data.
Added value for SAP Business One users and tax consultants
The development of the Versino Financial Suite began several years ago as an interface to DATEV Finance. Initially, we implemented our own extended export function, before later creating the option of importing the data or posting batches generated from DATEV into SAP Business One.
The DATEV interface was implemented early on as a bidirectional interface. This ensures a 100% synchronised database in both systems.
The development of the export from SAP Business One for DATEV was the starting point for further innovations. Once we had perfected the export and import process, we implemented further functionalities. In close contact with DATEV, we focussed on how we could improve communication between SAP Business One users and tax consultants using DATEV.
DATEV logic as early as the journal entry in SAP Business One
We also improved the handling of the base data Customer, vendor, G/L accounts and tax definitions. We have also ensured that SAP Business One already takes the DATEV logic into account for journal entries in SAP Business One. This ensures a smooth import into the DATEV financial system at the tax consultant
We developed special logics for this import. A distinction can be made between journal entries and journal vouchers in the data to be imported. This allows you to selectively import only journal vouchers initially.
Detailed checks when importing into SAP Business One
It is also possible to import data from DATEV Accounting or Wages & Salaries into SAP Business One. Before importing the data, the software first checks whether all the required accounts are available, whether the corresponding posting period is open and whether cost centres to be posted to exist. If this is not consistently the case, the software generates warnings. If everything is in order, the system accepts each line of the import file and triggers a corresponding posting in SAP Business One.
Complex logic for the generation of documents
If the import file contains Revenue account to customer, a journal entry is not simply imported into SAP Business One from DATEV, but the software creates an outgoing invoice.
If the file contains an expense account to vendor, a incoming invoice is created. Or, depending on the debit indicator, an incoming or outgoing credit memo is created instead of an invoice. If in the line to be imported "Bank to creditor" the system posts an incoming payment and vice versa, if Vendor to Bank, an outgoing payment. The software also checks reference fields to see whether an invoice number is specified. If so, the system actually posts against the invoice and automatically clears the invoice. In this case, the software acts as if a specialist were manually posting incoming or outgoing payments.
However, if no document can be found or no document number is specified, the software posts an incoming or outgoing payment, but then as a payment on account. All other cases that go from account to account lead to the creation of a Journal entry.
More end-to-end processes in DATEV AND SAP Business One
In this way, the system ensures a consistent flow of information. This is because documents, for example, are often entered as invoices in SAP Business One, but the payments are then only entered as journal entries by the tax consultant in DATEV. If the payment file is then returned for import, the payments have been lost and everything has to be reconciled again. The Financial Suite system identifies an invoice and invoice number and posts the corresponding payment against it.
Optimisation of exports from SAP Business One
However, we have also optimised or expanded the export from SAP Business One compared to the SAP standard. For example, unlike the SAP standard, the system exports cost units. The handling of taxes, general reversal and cancellation of the automatic function have also been significantly enhanced. In addition, the software does not export zero postings and transfers gross values instead of net values.
Much more in the Versino Financial Suite
The DATEV interface is just one, albeit important, component of the Versino Financial Suite for SAP Business One. Our customers, but also their tax advisors, are often surprised at the additional and helpful functions that can be found in the extension package for financial accounting. In combination with DATEV and SAP Business One Import and Export, both users and tax consultants have a great deal of potential for simplifying work and minimising costs. Optimisation.