Skip to content
Data & documents

Annual financial statements: the groundwork due in December

Preparing annual financial statements: which deadline applies to which legal form and which five tasks in December cut the follow-up questions in January.

20 min read JahresabschlussOffene PostenDatenqualitätDatenintegration

In many businesses, January is when the search begins. The tax adviser asks for the list of open items, for missing supplier invoices, for contracts that run across the turn of the year, and for an explanation of why revenue in the ERP system does not match revenue in the ledger. Every one of these questions can be answered, but in January each answer takes time that is actually needed for preparing the statements. And the clock is already running: as a rule, corporations have to prepare their annual financial statements within the first three months of the new financial year (German Commercial Code, Section 264 para. 1). December is the month in which many of these questions can be settled before anyone asks them. This article describes which deadline applies to which legal form, which five tasks can be done before the reporting date and how preparation turns into a routine that takes noticeably less effort in the second year. It is about data and workflows, not tax planning: valuation and accounting policy stay with the tax adviser. How we record such a workflow inside a business is described on the process analysis page.

Key takeaways

  • Corporations prepare their annual financial statements within the first three months of the new financial year, small corporations within six months at the latest (German Commercial Code, Section 264). With a calendar financial year, that means 31 March and 30 June.
  • For sole traders and commercial partnerships with a natural person as fully liable partner, the Commercial Code names no number of months: the statements have to be prepared within the time consistent with orderly business (German Commercial Code, Section 243).
  • Claims are usually time-barred after three years, counted from the end of the year in which they arose (German Civil Code, Sections 195 and 199). Matching open items in December reveals old claims from 2023 while there is still time for a legal review.
  • Accruals and provisions depend on knowledge outside accounting, such as maintenance that is made up within the first three months of the following year (German Commercial Code, Section 249). A fixed survey per department in early December collects it.
  • ERP system, bank and ledger are reconciled by count and total per document type, not document by document. Every difference becomes a case with an owner, and the closing pack is produced as a repeatable report from the same data.

Which deadline applies to which legal form

The obligation to prepare annual financial statements starts with the merchant. For the end of each financial year, a merchant has to prepare a balance sheet and a profit and loss account, which together form the annual financial statements (German Commercial Code, Section 242). Sole traders with no more than 800,000 euros in revenue and 80,000 euros in net income on two consecutive reporting dates are exempt (German Commercial Code, Sections 241a and 242 para. 4). For everyone else, the statute sets the timing in two steps. First comes the general principle: the annual financial statements have to be prepared within the time consistent with orderly business (German Commercial Code, Section 243 para. 3). That sentence does not contain a number. For sole traders and for commercial partnerships in which at least one natural person has unlimited liability, it is the governing rule. The exception is very large businesses that have to report under the German Disclosure Act (Publizitätsgesetz): they prepare their annual financial statements within the first three months of the financial year (German Disclosure Act, Section 5 para. 1). How long orderly business may take in a particular company is a question for the individual case and belongs in a conversation with the tax adviser, not in a rule of thumb.

For corporations, the deadline is set explicitly. The annual financial statements and the management report have to be prepared by the legal representatives within the first three months of the financial year for the previous financial year (German Commercial Code, Section 264 para. 1). Small corporations do not need a management report and may prepare the statements later if this is consistent with orderly business, but within the first six months (German Commercial Code, Section 264 para. 1). With a financial year that matches the calendar year, those dates are 31 March and 30 June. The same rules apply to a general or limited partnership in which no natural person has unlimited liability, typically the GmbH & Co. KG (German Commercial Code, Section 264a).

Legal formDeadline for preparationBasis in the German Commercial Code
Sole trader above the thresholds of Section 241aTime consistent with orderly business, no number of monthsSection 243 para. 3
OHG or KG with a natural person as fully liable partnerTime consistent with orderly business, no number of monthsSection 243 para. 3
GmbH & Co. KG without a natural person as fully liable partnerLike a corporation of the same size classSection 264a with Section 264 para. 1
Small corporationLater if consistent with orderly business, six months at mostSection 264 para. 1 sentence 4
Medium-sized and large corporationThree months, followed by an audit by a statutory auditorSection 264 para. 1 sentence 3 and Section 316 para. 1

Whether a corporation counts as small is decided by three criteria, at least two of which must not be exceeded: 7,500,000 euros in total assets (German Commercial Code, Section 267 para. 1), 15,000,000 euros in revenue in the twelve months before the reporting date (German Commercial Code, Section 267 para. 1) and an annual average of fifty employees (German Commercial Code, Section 267 para. 1). The legal consequences only take effect if the criteria are exceeded or undercut on the reporting dates of two consecutive financial years (German Commercial Code, Section 267 para. 4). For preparation, one detail matters more than it seems: the average number of employees is formed from the headcounts on 31 March, 30 June, 30 September and 31 December, excluding apprentices (German Commercial Code, Section 267 para. 5). These four figures come from HR and not from accounting. They therefore belong on the same list as everything else that is requested in December.

The size class also determines the steps after preparation. The annual financial statements of corporations that are not small have to be audited by a statutory auditor, and without an audit they cannot be adopted (German Commercial Code, Section 316 para. 1). Disclosure follows: companies that are not capital-market oriented submit the documents to the body that keeps the company register no later than one year after the reporting date (German Commercial Code, Section 325 para. 1a); for capital-market oriented companies, the period is shorter. Missing that deadline risks administrative fine proceedings by the Federal Office of Justice; for these companies, the fine is at least 2,500 and at most 25,000 euros (German Commercial Code, Section 335 para. 1). For planning purposes, this means that audit and disclosure extend the chain, but they only begin once the statements have been prepared. Time lost there is lost for every step that follows.

Preparation does not replace tax advice

This article describes workflows and data states. Which provision is recognised at what amount, how receivables are valued and which tax deadlines apply is decided by the tax adviser or auditor together with management. The groundwork makes sure these decisions are taken on complete data and not on whatever state can be found in January.

Why December decides the year-end close

The financial statements show the position on the reporting date. Stocks, account balances and open items as of 31 December can only be determined after 31 December. Many conclude from this that little can be done beforehand. That is true for the figures, but not for the work behind them. Many of the questions in January are not about the reporting date but about transactions during the year: a payment from May that has not been matched to any document, a credit note from August that was not offset against the invoice, a maintenance contract whose invoice arrived in December for the entire following year.

These transactions are already known in December. Whoever settles them then works with people who still remember, with suppliers who can still be reached and with systems whose data has not yet been frozen for the close. In January, exactly these conditions are often missing: holidays around the turn of the year, the stocktake, the year-end changeover in the ERP system and ongoing monthly bookkeeping tie up the same people. The inventory side is covered in our article Preparing the stocktake: choosing a method that fits. This article deals with everything else the close needs.

The groundwork can be traced back to five areas: open items, documents, accruals and deferrals, reconciliation between the systems and the reports handed over at the end. Each area has a question that should be answered in December and an owner who must be fixed beforehand. Anyone who only decides in December who reviews the open items loses part of the month agreeing on how to agree. The following sections go through the areas in turn.

Matching open items

Assets and liabilities, and therefore receivables and payables, have to be valued individually as of the reporting date (German Commercial Code, Section 252 para. 1). Added to this is the prudence principle: foreseeable risks and losses that arose up to the reporting date have to be taken into account even if they only become known between the reporting date and the preparation of the statements (German Commercial Code, Section 252 para. 1). In practice, this means the tax adviser needs a list of open items they can trust, plus information on the items where doubts exist. Neither comes from the accounting software alone.

A reliable list comes from matching three views. Accounting knows the open balance per customer and supplier. The ERP system knows the invoice, the order and often the dunning level. The bank knows the payment, but often not its purpose. Wherever these three views diverge, that is where the groundwork for the close lies. Typical cases are:

  • Incoming payments without a match, sitting on a clearing account and not settling the open item
  • Credit notes and invoice corrections that were posted but not offset against the original invoice
  • Cash discount and rounding differences that remain open as tiny amounts for months
  • Duplicate payments to suppliers or from customers that have to be reclaimed or refunded
  • Customers with credit balances and suppliers with debit balances, pointing to a mix-up or a missing invoice
  • Old receivables for which neither a payment nor a reminder has been recorded in the system for months

The last point carries particular weight in December. The standard limitation period is three years (German Civil Code, Section 195) and usually begins at the end of the year in which the claim arose and the creditor became aware of the relevant circumstances and the identity of the debtor (German Civil Code, Section 199 para. 1). A claim from 2023 can therefore become time-barred when 31 December 2026 ends. Whether and how the limitation period is suspended in an individual case is a legal question. The process question that comes first is simpler: is there a list of open receivables by year of origin, and does anyone look at it in November? How a dunning run keeps this list short on an ongoing basis is described in Automating dunning: reach the money in the bank sooner.

Many differences do not arise in December but continuously, because payments are matched by hand and the payment reference does not fit the document. If matching is handled by a connection between bank and accounting, the work shifts from year-end into day-to-day operations, and in December only the cases that genuinely need a decision remain. How such connections are built and monitored is described under integrations.

Making documents complete

The Fiscal Code requires bookings and other required records to be made individually, completely, correctly, in a timely manner and in an orderly fashion; cash receipts and cash payments have to be recorded daily (German Fiscal Code, Section 146 para. 1). In everyday operations, completeness rarely fails in accounting itself but on the routes by which documents enter the business. A supplier invoice lands in the personal inbox of a project lead, a credit card statement contains items without a receipt, an invoice for an online order only exists in the customer account at the supplier.

In December, the gap can be measured instead of guessed. The starting point is the bank transactions and card statements of the year: every expense without a matched document is an open case. The second check runs through the ERP system: goods receipts without an invoice and invoices without a goods receipt show where documents are missing or recorded twice. The article Invoice checks automated: order, goods receipt, invoice describes this principle for day-to-day operations; at year-end, a list of open cases with amount and owner is enough.

Personal inboxes

Invoices sent to employees instead of the central invoice address. A central incoming mailbox with a forwarding rule narrows this gap.

Card statements

Consolidated statements with individual items whose receipt sits in a bag, in a vehicle or in a customer account at the merchant.

Goods received without invoice

Delivered goods whose invoice has not yet arrived. On the reporting date, they are still a liability that has to be known and on a list.

Ongoing contracts

Rent, leasing, maintenance and licences paid by direct debit. The contract supports the individual debit, but it has to be findable and up to date.

Orders in customer accounts

Invoices that are only available for download in a supplier portal and do not arrive by email. They stay missing until someone downloads them deliberately.

Cash and cash receipts

Daily records, receipts and internal vouchers. If something is missing here, it can hardly be reconstructed in January because memories have faded.

Whoever completes documents in December should file them straight away so they survive the retention period. Annual financial statements, inventories and commercial books have to be kept for ten years, accounting vouchers for eight years (German Commercial Code, Section 257 para. 4); the Fiscal Code provides the same eight years for accounting vouchers (German Fiscal Code, Section 147 para. 3). The period begins at the end of the calendar year in which, for example, the annual financial statements were adopted or the voucher was created (German Commercial Code, Section 257 para. 5). What matters for digital filing is covered in GoBD-compliant storage: immutability and evidence; how paper documents become a searchable record is described under document digitisation.

Clarifying accruals early

The annual financial statements assign expenses and income to the year they belong to, regardless of when payment was made (German Commercial Code, Section 252 para. 1). Two instruments put this into practice. Prepaid expenses and deferred income capture payments before the reporting date that represent expense or income for a specific period afterwards (German Commercial Code, Section 250). Provisions capture uncertain liabilities and impending losses from pending transactions (German Commercial Code, Section 249 para. 1). These expressly include maintenance expenses omitted in the financial year that are made up within three months in the following financial year, as well as warranty work performed without a legal obligation (German Commercial Code, Section 249 para. 1).

For preparation, what matters is where the knowledge sits. Accounting sees the payment for the maintenance contract, but not that it runs until the end of June. It sees no complaint being handled in sales and no order to the roofer that was postponed to February because of the weather. This knowledge sits in purchasing, sales, the workshop, facilities and management. It cannot be pulled from a system, but it can be collected in a structured way, every year with the same questions.

Insurance, maintenance, licences, rent and subscriptions are listed with payment date and service period. Anything that extends beyond 31 December is a candidate for a deferral.

The effort for this survey falls mainly in the first year. After that, it is a template with fixed questions and fixed recipients that goes out on the same date every year. Collecting the answers in a form instead of emails leaves a table rather than an inbox at the end, and the tax adviser receives a list that can be worked through directly.

Reconciling ERP system, bank and ledger

In many businesses, an invoice is created in the ERP system or the online shop and transferred to accounting through an interface or an export. Payments arrive through the bank and through payment service providers. Over the course of a year, each of these connections can lose, duplicate or alter transactions: an export that did not run on one day, an invoice cancelled after the handover, a consolidated payout whose fees were not posted anywhere. In the close, this shows up as a difference whose cause nobody remembers.

Year-end reconciliation therefore does not work document by document but with control totals. For each connection, it is defined what is counted and totalled on both sides and which difference is acceptable. If something deviates, the period is narrowed down until the month, the week and finally the individual transaction is found. In its simplest form, such a reconciliation list looks like this:

year-end-reconciliation.txt
Check                            Side A                Side B                 Tolerance
Outgoing invoices, count         ERP system            Ledger                 0
Outgoing invoices, total         ERP system            Ledger                 0.00 EUR
Credit notes and cancellations   ERP system            Ledger                 0.00 EUR
Bank account, month-end balance  Bank statement        Bank account ledger    0.00 EUR
Payment provider payouts         Provider statement    Bank receipt           Fees
Goods received without invoice   ERP system            Supplier invoices      List
Open customer items              Ledger                Dunning status         List

Each line needs two things: a person responsible when a deviation occurs, and a query that delivers the figure without manual work. The second is a typical task for data integration: the figures are already in the systems, they only need to be counted by the same rules. If reconciliation runs monthly rather than annually, the January search for errors becomes a short check at month-end. Duplicate transfers found by such a reconciliation often share the same cause; how to prevent them at the source is described in Preventing duplicate postings: idempotency explained.

First the rule, then the search

A difference is only a finding if it has been defined beforehand what must match. Without a fixed counting rule, two lists stand against each other in January, and in the end whichever was opened last wins. The rule belongs in writing with every connection, along with an owner and a tolerance, so that a deviation triggers a decision and not a debate.

Preparing the closing pack as a report

Preparation ends with a handover: a collection of lists and evidence that the tax adviser or the auditor can work with. In many businesses, its content is largely the same every year. Even so, the pack is often assembled from scratch every year, out of exports, spreadsheets and emails. That is exactly where the biggest lever of the groundwork lies: whatever looks the same every year can be produced as a report from the existing systems. A typical closing pack contains:

  • Trial balance as of 31 December with the bank accounts reconciled to the bank statements
  • Open items for customers and suppliers with year of origin, dunning level and a comment on doubtful cases
  • List of contracts with a term beyond the reporting date as the basis for deferrals
  • Results of the department survey on reasons for provisions, with references
  • Stocktake result with valuation and a list of differences from inventory management
  • Additions and disposals of fixed assets with invoice and commissioning date
  • Employee headcount on the four quarterly reference dates from HR
  • Reconciliation list for the interfaces with results and open cases

How such a report comes about is described in Generating reports automatically instead of by hand: first the definition, then the technology, one leading system per field and a data state per source that is written into the report. The closing pack adds one requirement. The state must be freezable so that a late posting in February does not quietly change the list handed over in January. We build such reports under metrics and reporting, from the systems that are already running in the business.

A schedule from December to preparation

With a financial year equal to the calendar year, the framework follows from three dates: the reporting date of 31 December, 31 March as the end of the three-month deadline for corporations and 30 June as the outer limit of six months for small corporations (German Commercial Code, Section 264 para. 1). Counting backwards, a medium-sized company has the first quarter for the actual preparation, during which the audit also has to be prepared. The groundwork is therefore sensibly spread out as follows:

  1. Early December: send the department survey, update the contract list and fix the date for the handover to the tax adviser.
  2. By mid-December: review open items by year of origin, settle unmatched payments and have old receivables from 2023 checked.
  3. By the last working days: request missing documents, complete card statements and run the reconciliation list for January to November.
  4. First week of January: secure the balances as of 31 December, take over the stocktake result and run the reconciliation for December.
  5. By the end of January: hand over the closing pack, answer follow-up questions and deliver the headcounts for the four quarterly reference dates.
  6. February and March: preparation, by 31 March for medium-sized and large corporations; the audit follows, then adoption and disclosure within the one-year period.

The annual financial statements and the management report are to be prepared by the legal representatives within the first three months of the financial year for the past financial year.

German Commercial Code, Section 264 para. 1 sentence 3 (unofficial translation)

In the second year, the picture changes. The contract list, the survey and the reconciliation list already exist and only need updating. Anyone who also runs the reconciliation monthly only finds the cases of the current month in December. A year-end project turns into a routine spread across the year that creates little extra work in December.

Where starting pays off most

Not every business needs all five tasks to the same depth. A trading business with an online shop and many small payments usually has its biggest gap in reconciling shop, payment provider and accounting. A trade business with building sites tends to have it in receipts from card payments and in deferrals for work in progress. A service provider with framework agreements has it in the contract list. Anyone unsure where to start can begin with the question of which follow-up question from the tax adviser stayed open longest last year.

That is where our work begins. We record where the data for the close is created today, where it gets lost and which connection between the systems replaces the largest share of manual work. The result is a list of reconciliations and reports that we implement through data integration and metrics and reporting. For a first conversation before the turn of the year, the contact page is enough. If you want to sort out retention and deletion at the same time, the periods and the process are described in Retention periods digitally: schedules, holds, deletion runs.

Sources and legal basis

This article is based on data from: German Commercial Code (Sections 241a, 242, 243, 249, 250, 252, 257, 264, 264a, 267, 316, 325 and 335), German Fiscal Code (Sections 146 and 147), German Civil Code (Sections 195 and 199) and German Disclosure Act (Sections 1, 3 and 5), each as published on gesetze-im-internet.de. For a financial year that differs from the calendar year, the dates mentioned shift accordingly. The description covers workflows and does not replace tax or legal advice in an individual case.

Related Articles

Law, security & funding

Packaging reporting driven by the item master

Which field is missing on the item, how packaging weights per variant and shipping carton are maintained, and how delivery note quantities become a defensible reported tonnage per material type.

16 min read
Law, security & funding

Preparing the stocktake: choosing a method that fits

Four methods, one inventory: how far the counting day may sit from the closing date, which deadlines apply and which data work has to happen first.

17 min read
Law, security & funding

Data Act: using machine data from September 2026

From 12 September 2026 new connected products must release operating data by default. Which deadlines apply, who is exempt and what to prepare now.

17 min read