Can companies continue to write their invoices with Excel? Or is there soon a duty to certified, cloud-based billing software that automatically and seamlessly issues invoice numbers? Such statements are plausible, but they mix several different rules. This article separates invoice number, e-bill, GoBD, cash security and future reporting systems – and shows what follows for TabellenFaktura.

Short answer with stand 25. August 2026

There is currently no general obligation to create invoices exclusively with certified or cloud-based software. Invoice numbers must be assigned once; a complete sequence of numbers is expressly not required. Excel is not prohibited as a tool for invoicing. However, the entire sequence, the mandatory information, the required e-invoice format, the comprehensible recording and the unchanged storage are decisive. A freely variable Excel file alone does not automatically meet these requirements.

What concerns are actually communicated?

In official notices, specialist information and introductory checklists, the focus is not on the question "Excel or Cloud?". Rather, it is discussed whether the entire accounting process is still complete, comprehensible and verifiable years later. The Federal Tax Advisors' Chamber explicitly describes the e-bill as more than a format change: it changes input and output processes and increases the requirements for integrity, storage, technical and organizational controls.

The recurring concerns can be condensed to four core questions:

  • Is the final bill clear? Invoice number, content, consignee and shipping must not be confused or used twice.
  • Is the original preserved? A invoice sent must not be overwritten, deleted or replaced by a new version, without the change being recognisable.
  • Do visible and structured data match? For ZUGFeRD or other hybrid formats, the PDF must not contain any amount, tax rate or recipient other than the machine-readable data.
  • Can the procedure be explained and checked later? Responsibilities, number circles, corrections, archiving, data backup, software versions and interfaces must fit the actual procedure.

In addition, there are future issues: How are new e-invoice rules introduced? How can data from a discontinued program be exported? How is a future reporting system connected? And who can continue to work if the Internet, cloud providers, PC or storage fail? These are real risk issues. However, this does not follow a general product certification or a duty to run the billing program in a cloud. The legislator requires a proper process, not a specific business model.

Worry 1: Will certified billing software be mandatory?

For ordinary invoicing programmes there is currently no state seal of quality which must be acquired before use. GoBD of the Federal Ministry of Finance even say explicitly that the financial administration does not grant general positive states for hardware or software. Certificates or testates of private third parties can help in selecting, but do not bind the financial authority.

The reason is practical: whether a procedure is correct does not only depend on the program. Settings, user rights, updates, entered data, work instructions, controls, data backup and actual use are also crucial. Even an excellently developed software can be used incorrectly; vice versa, a simple local process with appropriate protective measures can be arranged in a comprehensible manner.

Where does the talk of "certified software, " come from?

Often four different things are confused:

  • Technical safety device for cash registers: Electronic cash registers and cash registers are subject to specific provisions of the Cash Guarantee Regulation. Cash However, electronic accounting programs expressly exclude from their scope. Therefore, a normal accounting program does not require a certified TSE solely because of its accounting function. If it also contains a cash register system, this cash register function must be assessed separately.
  • Private GoBD tests: Such certificates may provide guidance but are not state approval and are not a guarantee for the specific operation.
  • Technical E-invoice test: A validator can determine whether a XRechnung or ZUGFeRD file meets technical and professional rules, which is important, but not certification of the entire billing and archiving process.
  • Future reporting systems: Planned electronic messages to financial management require structured data and reliable processes. This does not automatically lead to a cloud obligation.

Sorrow 2: Do invoice numbers have to run without any gap?

§ 14 VAT law requires a consecutive number with one or more number series, which is awarded once for the identification of the invoice. The decisive purpose is the clarity: The same invoice number cannot be awarded twice in the respective number circle.

The current VAT Application Release, section 14.5, clarifies: A complete sequence is not mandatory. Several meaningfully demarcated number circles, for example by year, period, location or organizational area, are also permitted. They must be clearly assignable and each number must remain unique within the number circle.

However, this does not mean that gaps are meaningless. In an audit, it should be possible to explain why a number is missing – for example, by a rejected draft, a cancellation or a technical cancellation. More importantly, an invoice already sent is not simply deleted and its number is used again. Corrections and cancellations must show the original process.

ProcedureClassificationUseful protection
2026-001, 2026-002, 2026-004The gap alone does not make the sequence invalidDocument the reason for the missing number
The same number for two invoicesNot allowed because the number is not uniqueCentral duvet check and blocked numbers
Separate circles such as RE-2026-... and GU-2026-...Basically possible if the circles are clearDescribe the number logic in the procedural documentation
Overwrite the invoice sentDangerous Retraceability and UnchangeabilityOriginal received and working with storno or correction

Worry 3: Do accounting programs need to be cloud-based soon?

There is no such general requirement. The GoBD explicitly consider their own hardware, cloud systems and combinations from it. The decisive factor is whether the procedure used meets the tax requirements. Locally installed software is not automatically unsuitable as a cloud application is automatically correct.

The law also does not require a specific route for the transmission of an e‐invoice. E‐Invoice-FAQ of the Federal Ministry of Finance e-mail, interface, common memory, USB stick or download portal are among others eligible. Since 2025 a company has to be able to receive e-invoices; an e-mail mailbox is sufficient for this.

The cloud can offer practical advantages: central updates, cross-device use, automatic backups, rights management and interfaces. It also brings with it dependencies on providers, Internet access, contract model, data location and export possibilities. Legally crucial is not "cloud or local, but whether data is complete, correct, comprehensible, protected, machine-evaluable and available over the retention period.

What really comes: e-invoice and digital reporting system

Since 1 January 2025, an e-invoice has been defined as an invoice in a structured electronic format that allows electronic processing. A simple PDF is now classified as an ‘other invoice’. Transitional periods apply to issuing invoices: Issuers may continue to use other invoices until the end of 2026. Businesses whose previous annual turnover did not exceed EUR 800,000 can generally use this option until the end of 2027. Exceptions include many transactions with private individuals and certain VAT-exempt transactions.

After that, the structured e-bill for the recorded domestic B 2B transactions becomes the normal case. Formats such as XRechnung and ZUGFeRD can meet the specifications, provided that the specific file complies with the applicable technical and content rules.

Germany also plans a system for timely, transaction-based reporting of certain invoice data. The Federal Ministry of Finance explicitly states that the necessary legislative changes have yet to be proposed. At European level, the ‘VAT in the Digital Age’ package adopted in 2025 provides for digital reporting of cross-border B2B transactions from 1 July 2030 and gradual alignment of national systems by 2035.

The trend is clear: invoice data are more structured, interfaces are more important and processes are more automated. However, parts of the concrete German reporting architecture are still open. Deriving a general obligation to use cloud accounting software from this digitalization trend would currently be speculation.

Can you write long-term invoices with Excel?

Yes, Excel is not prohibited at all. However, the crucial question is not with which tool a design is created, but how this design becomes a proper invoice and a comprehensible business incident.

A Excel workbook can represent calculations, design, article data and individual processes excellently. However, it has typical weaknesses as a sole accounting solution:

  • Cells, formulas, master data and invoice numbers can be overwritten afterwards.
  • A manually guided number can be accidentally double assigned.
  • Several file copies create uncertainty about which version was actually sent.
  • Deleted or renamed files do not leave a reliable history without additional logging.
  • A PDF generated from Excel does not contain structured e-invoice data.
  • A normal file folder alone prevents neither unnoticed changes nor loss.

Therefore, Excel can remain an appropriate recording and design tool. However, it should be integrated into a controlled process that generates, checks, registers, retains unchanged and makes changes comprehensible.

Three levels that are often confused

LevelWhat is it about?What a converter can do alone
Invoicing content and formatMandatory information, correct amounts, one-off invoice number, ZUGFeRD or XRechnungApply data, create format and check technical rules
Process and recordingCompleteness, correctness, timely recording, controls and comprehensible correctionssupport checks; the business workflow remains a decisive factor
Storage and testingGet original, log changes, secure, deploy and keep readable dataPreparing for export; a permanent archive is an additional task

This separation is important for every purchase decision. A technically valid e-bill can come from a poorly documented process. Conversely, a good archive does not make a proper calculation of a wrong invoice.

Other critical thoughts that often come too short in software selection

Questions about certification, invoice number and cloud are only the visible part. Further technical and organizational risks are at least as important for the future security of a solution.

Critical pointSpecific riskPrepared for a solution
Validation is not content checkAn XML file can be technically valid and still contain a wrong IBAN, performance, address, VAT ID or control calculationPlausibility checks, master data reconciliation and understandable clearance before dispatch
PDF and XML contradict each otherMan sees a different billing content than the receiving accounting system processedAutomatic matching of both displays and blocking in case of deviations
Design and original are confusedAn unfinished or later modified Excel file is considered internally as a shipped versionClear status "Design, "released, "sends, "cancelled, and distinctive original file
Simultaneous processingTwo persons or two copies of files assign the same next invoice numberCentral or nomadic number reservation and dublette examination
Manual formulas and acquisitionsHidden lines, rounding errors, false tax rates or copied old values get into the invoiceControl amounts, mandatory field verification, warnings and comprehensible calculation rules
Shipping is not equal to accessAn email ends up in spam, a portal address is wrong or the recipient does not accept a transmission routeShipping protocol, addressable receiving channels, error status and re-delivery without new invoice
Local data lossDefect, theft, ransomware or a faulty update destroy originals and journalMulti-stage backup, restoration test and orderly total export
Cloud and provider dependencyPrice increase, termination, failure or product adjustment make access and further work difficultComplete export in open formats, documented data structure and emergency plan
Confidentiality and allowancesCustomer, bank and performance data are accessible to unauthorized personsRoles, access protection, encryption, logging and clear data protection agreements with service providers
Overdated standardsA previously valid format version or check rule is no longer accepted by the recipientMandatory rule updates, version display and pre-generation check
Unclear correctionsA new file replaces the original without reference to the original or correctionLinked proofs and complete process history
Future reporting systemA completed software architecture cannot supplement required transmission routesModular interfaces, updateable rules and separation of local core and reporting adapter

The responsibility cannot be completely outsourced to software

Another critical point concerns the expectation of the product itself. According to the GoBD, the company remains responsible for the regularity – even if tasks are outsourced to a cloud, a data center or other service provider. A manufacturer can provide good controls but does not decide whether the correct invoice has been released during operation, a backup has been verified or a correction has been fully documented.

Technically valid does not automatically mean correct

The Federal Ministry of Finance recommends the validation of an e-bill, but does not refer to it as an immediate requirement for tax recognition. This makes the limit clear: A validator examines format rules and logical relationships, but does not necessarily know the actual contract, the performance performed, the correct customer address or the correct bank connection. Future-proof software must therefore distinguish between technical audit and operational approval.

The visible invoice can also be the source of error

People often check PDF views while accounting systems process the structured XML part. Therefore, an automatic synchronisation is important, especially for hybrid invoices. An optically correct PDF does not help if the structured data contains a different amount or tax rate. Nor is a correct XML file sufficient if supplementary information relevant to taxation is only in one attachment and is not properly carried.

Future security is also economic independence

A cloud solution can facilitate updates and backups, but it creates a permanent dependency point. A purely local solution protects against this provider access, bears the risk of device failure, faulty backups and outdated software. Both models therefore need a complete, documented export in open formats. Invoices, journals, protocols and process information must remain usable even after a provider or system change.

What do the GoBD require of a digital billing process?

The GoBD refer above all to traceability and verifiableness, completeness, correctness, timely recording, order and immutability. Changes must not render the original content unrecognizable. Protection of the data, controls, data backup and a process documentation that is appropriate to the actual process are also included.

For small companies, scope and concrete design are assessed according to the actual circumstances. "Small, therefore, does not mean "regulatory, but can justify an appropriate, less complex process. An individual entrepreneur usually does not need a multi-stage release organization like a group. He must nevertheless be able to show which invoice was created and sent when, how corrections are made and where the original files are backed up.

What file must be stored when an e-invoice is sent?

The structured data part is crucial for an e-invoice. It must be preserved in its original form and be machine-evaluable. In case of an XRechnung this is typically the XML file. In case of ZUGFeRD, the structured XML is in a PDF/A3 file; here too, the structured content must not be lost.

In accordance with § 14b VAT law, invoices issued and received must be kept for a period of eight years. The deadline begins with the end of the calendar year in which the invoice was issued. Other documents or legal reasons may trigger different or longer deadlines. Therefore, the specific retention should be coordinated with tax advice and the accounting or archive system actually used.

What does this mean for TabellenFaktura today?

TabellenFaktura follows a fundamentally sustainable approach: The familiar Excel template remains the working tool, while it creates a structured ZUGFeRD file or XRechnung locally. Mandatory information and technical rules can be checked before output. Billing data does not have to be uploaded to a foreign online converter for this processing.

TabellenFaktura therefore addresses an important part of the problem: converting individual Excel fields into a standardised e-invoice format. This does not mean that the entire business process is automatically ‘GoBD-certified’ or legally compliant in every configuration. No software vendor alone could responsibly provide such a guarantee.

In the current orientation, TabellenFaktura is mainly a creation, verification and conversion tool. Accounting organization, booking, unchanged long-term storage, data backup and process documentation must play together with the rest of the process.

Can a local solution that works closely with Excel be viable in the long term?

In principle: yes. There is no legal rule that excludes a local Excel close solution solely because of its technology. ZUGFeRD and XRechnung are designed to exchange structured billing data independently of a particular manufacturer platform.

Whether a specific software version and the overall process thus organized meet the applicable requirements must always be assessed on the basis of the current legal status, the actual purpose of the application and the operational organisation. Therefore, a general future guarantee cannot be given for a local application or a cloud product.

A practical checklist for Excel invoices

  • Clearly described numbering range with one-off allocation of each invoice number.
  • Sensible storage of rejected numbers, stornos and corrections.
  • No silent change of an invoice already sent in the same file.
  • Control of all mandatory information and the conformity between visible invoice and structured data.
  • Keeping the e-bill actually sent in the original structured format.
  • Determined responsibilities for release, error correction and proof of dispatch.
  • Protect the files from loss and unauthorized modification including tested recovery.
  • Appropriate documentation of the process and update of changes.
  • Regular control of format updates, legal transition periods and the development of the German reporting system.
  • Coordination of archiving and transfer of accounts with accounting and tax advice.

Conclusion: Future-proof means controlled – not necessarily cloud

The future of the invoice is structured, machine-readable and more connected. However, it is not necessarily cloud-based according to today's law. Nor do companies need to buy a generally "certified billing software. Billing numbers must be unique and unique, not completely mauvematic.

Excel can therefore remain part of the invoicing process in the long term. However, the workbook alone is not enough. Long-term reliability depends on correct e-invoices, controlled numbering, traceable corrections, unaltered retention, backups and a documented workflow working together.

Information on TabellenFaktura is available in the Documentation and Pricing and licence.

Sources and legal notice

The basis for this classification is § 14 and § 14b UStG, section 14.5 of the current VAT application release, which FAQ of the Federal Ministry of Finance about e-invoiceThe GoBDThe Cash guarantee regulationThe E‐invoice-FAQ of the Federal Tax Advisory ChamberThe Introduction checklist of the IHK Köln and the information of the Commission on VAT in the Digital Age. As of 25 August 2026. This article explains general requirements and does not replace legal or tax advice for individual cases. Future German requirements for the reporting system should continue to be monitored.

FAQ

Frequently asked questions

Does billing software have to be certified in Germany?

No, there is currently no general state certification requirement for ordinary billing software. The financial management does not grant general positive state for software. Private certificates can help with the selection, but do not bind the tax office. The decisive factor is the concrete system, its settings and the actual process.

Do invoice numbers have to be continuous?

No. Invoice numbers must be assigned uniquely and uniquely in the respective number circle. The VAT application release expressly states that a complete sequence is not mandatory. Missing numbers should nevertheless be explained and documented in a comprehensible manner.

Will cloud-based billing programs be mandatory?

According to the legal status of 25. August 2026 there is no general cloud obligation. GoBD-compliant procedures can be operated on own hardware, in a cloud or combined. Also e-invoices may be transmitted for example via email, interface, USB stick or download portal.

Can I continue to write bills with Excel?

Excel is not prohibited at all and can continue to be used for collection, calculation and design. However, a changeable Excel file alone is not sufficient automatically. Mandatory information, e-invoice format, unique numbers, comprehensible corrections and unchanged storage must be ensured throughout the process.

Is a PDF created from Excel an e-invoice?

A simple PDF has been a legal invoice since 1. January 2025 is not an e-invoice, but a different invoice. A e-invoice requires a structured electronic format, for example XRechnung or ZUGFeRD, which allows electronic processing.

How long must e-invoices be stored?

Under section 14b of the German VAT Act (UStG), issued and received invoices must generally be retained for eight years. For e-invoices, the structured original data in particular must remain unaltered and machine-readable. Other documents or legal requirements may trigger additional or longer retention periods.

Is TabellenFaktura GoBD certified?

There is no generally binding GoBD certification for billing software. TabellenFaktura can support a GoBD-oriented accounting process technically, but does not only make the entire operational process proper. Settings, number organization, archiving, data backup, controls and process documentation remain decisive.

Can TabellenFaktura be used in the long term in accordance with the law?

Local and close to Excel solutions are not legally excluded. Whether a concrete version and the overall process thus organized meet the applicable requirements depends on the respective legal status, purpose, the recruitment and the operational organization. A flat-rate future guarantee is therefore not possible.