Klicke hier um unsere neue Seite zu besuchen
The shop system Shopify and its POS do not fulfill all requirements of the GoBD. There are nevertheless ways to make your online shop GoBD compliant, as you will learn in this article.
Erstellt in E-Commerce, Shopify am 20 Feb 2017
This is just a concept and not a finished app. If you are interested in funding the development of the app, please contact us.
The shop system Shopify (affiliate link) and the checkout system Shopify POS – as well as about all shop systems at the moment, by the way – don't fulfill the requirements of the GoBD. Furthermore, it still remains unclear whether Shopify themselves are interested in implementing an according solution or adaptation to the German market. Yet there are ways to make your online shop GOBD compliant, and these we want to present to you here.
You have, up until now, not yet looked into the new requirements? Better read this article to the end, or it could get expensive.
The abbreviation "GoBD" stands for Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern, Aufzeichnungen und Unterlagen in elektronischer Form sowie zum Datenzugriff (en. Rules of orderly bookkeeping and storage of business records in electronic form and of data access) and were consolidated by the German financial administration from the former GoBS (Grundsätze ordnungsgemäßer DV-gestützter Buchführungssysteme - en. Rules of orderly data processing-based bookkeeping systems) and GDPdU (Grundsätze zum Datenzugriff und Prüfbarkeit digitaler Unterlagen - en. Rules for data access and verifiability of digital business records). As of January 1, 2015, the GoBD are legally effective, and as of January 1, 2017, they are mandatory for all checkout systems.
For further general information we refer you to an article by the law firm Limberger Fuch Koch & Partner mbB or the GoDB-Leitfaden by the law firm Peters, Schönberger & Partner mbB.
Every system which processes data subject to book- and record-keeping - and this includes the popular shop system Shopify - has to comply with the requirements and conditions posed by the GoBD. Shop owners are therefore generally liable to comply with these conditions.
Even if bookkeeping is outsourced to an external service provider, you, as a shop owner, are liable to make sure that they comply with these rules. Auch wenn die Buchführung an einen externen Dienstleister ausgelagert ist, bist du als Shopbetreiber in der Pflicht, zu überprüfen, ob diese die Regelungen einhalten. To quote the GoBD-Leitfaden sourced above:
Die Verantwortung für die Ordnungsmäßigkeit elektronischer Bücher und sonst erforderlicher elektronischer Aufzeichnungen einschließlich der Verfahren trägt allein der Steuerpflichtige. Dies gilt auch bei einer teilweisen oder vollständigen organisatorischen und/oder technischen Auslagerung von Buchführungs- und Aufzeichnungspflichten auf Dritte (Outsourcing).
The liability for compliance of electronic books and other required electronic records, including the procedures, lies with the taxable person. This also applies in the case of a partial or complete technical outsourcing of book- and record-keeping duties to a third party.
Yes. The "Grundsätze" apply in general, not only for an online shop, but also for all complementary systems which work together with an online shop and with the same data. This applies, for example, also to the POS system, as the GoBD-Leitfaden states:
Die GoBD rekurrieren sowohl auf das Haupt(buchführungs)system als auch auf etwaige Vor- und Nebensysteme. Explizit aufgeführt sind Finanzbuchführungssystem, Anlagenbuchhaltung, Lohnbuchhaltungssystem, Kassensystem, Warenwirtschaftssystem, Zahlungsverkehrssystem, Taxameter, Geldspielgeräte, elektronische Waagen, Materialwirtschaft, Fakturierung, Zeiterfassung, Archivsystem, Dokumenten-Management-System einschließlich der Schnittstellen zwischen den Systemen. Dabei kommt es nicht auf die Bezeichnung des jeweiligen Systems an, sondern auf die Frage, ob in einem System buchführungs- oder aufzeichnungspflichtige Daten erfasst, erzeugt, empfangen, übernommen, verarbeitet, gespeichert oder übermittelt werden.
The GoBD apply to the main (bookkeeping) system as well as to any possible upstream or auxiliary systems. Explicitly mentioned are financial bookkeeping systems, assets accounting, payroll accounting systems, checkout systems, enterprise resource planning, payment transaction systems, taximeters, gambling machines, electronic scales, materials administration, invoice processing, (work) time tracking, archiving systems, document management systems, including interfaces between the systems. What matters here is not the name of the specific system but the question of whether a system records, produces, receives, carries over, processes, stores or transmits data subject to book- and record-keeping.
Furthermore, all movements of goods have to be recorded. Whenever a stock is changed it must be clear by which cause.
We have compiled an infographics for you inwhich you can find a summary of the conditions:
A further listing can be found at VeR.
When it comes to an announced tax audit, or an unannounced turnover tax look-up, the examiner has authorization to access the data and the systems. Here, three access modes (Z1, Z2 and Z3) are distinguished. The examiner can decide for one or more of these access modes. That means you have to be prepared for all three:
In the case of immediate data access, the examiner gets access to all tax-relevant data processing systems (DP system) in order to inspect bookkeeping data, master data and linkages. This also includes the use of evaluation programs for filtering and sorting tax-relevant data.
In other words, the examiner gets access to the accounting department. Im Grunde bekommt der Prüfer also Zugriff auf den Arbeitsplatz der Buchhaltung, where provisions must be made that he has read-only-access to tax-relevant data.
In the case of mediate data access, the shop owner has to let the examiner evaluate the tax-relevant data electronically. Here, facilities for evaluation may only be demanded for such a timespan as the extant DP systems allow for. Furthermore, the shop owner or the company, respectively, are obligated to support the examiner in the process.
For the case of storage medium handover, a storage medium (for example DVD or USB flash drive), containing the data in a compliant format, must be made readily available to the examiner at any time. The storage medium must contain all relevant data (for example all orders with reference to the customer etc.) – even in the case, as with Shopify, where the data are stored by a third party. The data must be readily available for access, to be examined on the examiner's laptop directly on-site.
Here a short technical outline on the GoBD data format. The
Hier noch ein kleiner technischer Ausreißer zu dem GoBD-Datenformat. The data format favoured by the tax office for storage medium handover is not a single format. Rather, the following files must be present on the medium:
Further information on the description standard can be requested at audicon.net free of charge.
There is no requirement for certifications to confirm compliance with the GoBD. Rather, such certificates are used as marketing instruments at this point in time, and may therefore be helpful in choosing a system. From 2020 on, however, such certificates will become mandatory.
In the case of non-compliant bookkeeping, the financial administration may add as much as 20% in estimated revenue, and sadly such cases actually happen.
In most cases probably not. Even if the ERP system in and of itself is GoBD-compliant it may be that through interaction with auxiliary systems compliance no longer ensured. You may check the following in order to determine whether your ERP system is really compliant:
Especially the cooperation of the systems is important, since the data must be recorded complete and without gaps at all times. Without gaps means that, for example, the orders throughout the combination of the checkout system, the ERP and the online shop always have a consecutive ID, i.e. without gaps. In the "Leitfaden" the following is mentioned about this:
Geschäftsvorfälle sind vollzählig und lückenlos aufzuzeichnen (Grundsatz der Einzelaufzeichnungspflicht). Dies erfordert eine vollzählige und lückenlose Erfassung sämtlicher Sachverhalte. Dabei kommt insbesondere einer Transaktionskontrolle und Konsistenzprüfung eine besondere Bedeutung zu. Die vollständige und lückenlose Erfassung und Wiedergabe aller Geschäftsvorfälle ist bei DV-Systemen durch ein Zusammenspiel von technischen (einschließlich programmierten) und organisatorischen Kontrollen sicherzustellen [...] Die Einzelaufzeichnungspflicht gilt grundsätzlich auch für Bargeschäfte.
Business transactions are to be recorded complete and without gaps (Principle of "Einzelaufzeichnungspflicht" [en. single record obligation]). This requires a complete and gapless record of all transactions. Especially transaction double-checks and consistency checks are important here. The complete and gapless record and replay of all business transactions is to be ensured through a combination of technical (including programmed) and organizational checks [...] The "Einzelaufzeichnungspflicht" is generally applicable to cash sales as well.
In order to tackle the problem we are currently working on an app that steps in exactly where Shopify does not comply with the requirements. Our app will have the advantage – vis-à-vis the detour over an ERP – that all data from Shopify, the POS system and further auxiliary systems can be recorded at once. In this way, the requirements on completeness are solved elegantly.
In order to fulfill the requirements for data access modes Z1 to Z3, we are working on a corresponding backend with read-only access and synchronize the data directly onto your flash drive, so that it is readily available to the examiner.
Therefore we see in our app the cleanest and most elegant solution. It might be possible that further auxiliary systems can be covered automatically within this solution. If you are affected and interested in our solution then simply send an email to hello@jumplink.me or call us directly. Perhaps we can also integrate support for additional auxiliary systems that you are using. Our work builds directly on the problem situations of our customers, and we are happy to let yours flow directly into our programming as well.
Pascal Garber
Founder, Entwickler, Designer
Hi, ich bin Pascal und habe schon als Vierzehnjähriger mit dem Programmieren begonnen. Damals nur aus reiner Neugierde und aus Spaß meine Lieblings-Videospiele nachzuprogrammieren. Ich habe es geliebt Dinge zu "erschaffen" und das hat sich bis heute nicht geändert. Inzwischen stehen Qualität und Schönheit in Kombination mit feinem Design ebenfalls im Fokus der Programmierung.
Berufswunsch: Erfinder
Angaben gem. § 5 TMG
JumpLink ist ein Netzwerk aus selbstständigen Designern und Programmierern.
Mitglied der Initiative "Fairness im Handel".
Informationen zur Initiative: fairness-im-handel.de