Denmark's Digital Bookkeeping Act (Bogføringsloven) Requirements

Denmark's Bookkeeping Act (Bogføringsloven, Act No. 700 of 24 May 2022) requires every Danish business to conduct bookkeeping through a digital system that meets three core technical standards: immutable transaction records that cannot be altered or deleted after entry, SAF-T export capability for standardized tax reporting, and backup storage within the EU or EEA. Compliance is phased by business size. Companies filing annual reports under accounting Classes B, C, and D must comply from July 2024 or January 2025, depending on their class. Sole proprietorships with annual turnover above DKK 300,000 face a January 2026 deadline.

Denmark's Digital Bookkeeping Act is arguably the most expansive digital bookkeeping mandate in Europe. Where most EU member states have focused narrowly on e-invoicing or tax reporting formats, Denmark has legislated the entire bookkeeping process from data entry through storage and export. The law doesn't just require businesses to send invoices digitally; it dictates how every financial transaction must be recorded, preserved, and made available to authorities.

Oversight falls to the Erhvervsstyrelsen (Danish Business Authority), which maintains the official registry of approved bookkeeping systems, monitors compliance, and holds enforcement powers that extend to compulsory dissolution of non-compliant companies. The Erhvervsstyrelsen's role is not passive. It actively evaluates and registers bookkeeping software, sets technical standards, and can investigate businesses that fail to meet their obligations.

The Act replaced Denmark's previous 1999 Bookkeeping Act and entered into force on 1 July 2022, with compliance deadlines staggered over a multi-year rollout. Its requirements span seven key dimensions that together define what compliant digital bookkeeping looks like in Denmark:

Registered bookkeeping systems — a unique approval framework requiring businesses to use software formally registered with the Erhvervsstyrelsen
Transaction immutability — strict rules preventing alteration or deletion of recorded entries
SAF-T export obligations — standardized audit file generation, including the upcoming SAF-T 2.0 format
Digital storage — requirements for how long records must be kept and where backup data must physically reside
E-invoicing capability — the ability to send and receive electronic invoices in structured formats
Penalties — consequences for non-compliance, ranging from fines to forced company dissolution
Foreign company obligations — how the Act applies to businesses registered abroad but operating in Denmark

Each of these dimensions carries specific technical and procedural requirements that affect system selection, internal processes, and ongoing compliance monitoring.

The Three-Phase Compliance Timeline

Denmark's digital bookkeeping mandate did not arrive as a single deadline. The Danish Business Authority (Erhvervsstyrelsen) structured the rollout in phases, giving different business categories staggered compliance dates based on size, reporting obligations, and system type. Several of these deadlines have already passed.

The timeline below covers every major milestone from the initial provider requirements through the projected e-reporting mandate.

Date	Milestone	Who It Affects
1 February 2023	Digital standard system requirements took effect for software providers	Bookkeeping system vendors
31 October 2023	Registration deadline for providers of standard bookkeeping systems	Bookkeeping system vendors
1 July 2024	Phase 1: Mandatory use of a registered digital bookkeeping system	Companies in Classes B, C, and D already using a registered system
1 January 2025	Phase 2: Mandatory digital bookkeeping for companies using non-registered or custom systems	Companies in Classes B, C, and D using custom or non-registered systems
1 January 2026	Phase 3: Digital bookkeeping requirements extend to smaller businesses	Sole proprietorships and partnerships with net turnover above DKK 300,000 for two consecutive years
1 July 2026	Extended Phase 3 deadline for Class A businesses on custom in-house systems	Class A businesses running proprietary bookkeeping software
1 January 2027	SAF-T 2.0 becomes mandatory for registered digital bookkeeping systems	All registered system providers and their users
~2028 (projected)	E-reporting expected to become mandatory for all businesses	All Danish businesses

Does this apply to you right now? The answer depends on your company's classification under the Danish Financial Statements Act (Årsregnskabsloven). Denmark groups companies into four classes based on size thresholds:

Class A: The smallest businesses — sole proprietorships and certain partnerships not required to file annual reports. These fall under Phase 3 (1 January 2026), provided their net turnover exceeded DKK 300,000 in each of the two preceding fiscal years. Class A businesses running custom in-house systems have until 1 July 2026.
Class B: Small companies that exceed at least two of three thresholds (balance sheet total DKK 4 million, net revenue DKK 8 million, average 12 full-time employees). These were covered by Phase 1 or Phase 2, depending on whether they were already using a registered system.
Class C: Medium and large companies, subdivided into C-small and C-large, with progressively higher thresholds. Covered by Phase 1 or Phase 2.
Class D: Listed companies and state-owned public limited companies. Covered by Phase 1 or Phase 2.

For Classes B through D, the relevant deadline has already passed. If your organization falls into one of these categories and has not yet transitioned to a compliant digital bookkeeping system, you are already operating outside the legal requirement. Class A businesses still have limited time before their obligations take effect.

Denmark is not acting in isolation. Several Nordic countries have moved toward mandating digital financial record-keeping standards — Sweden's SIE accounting data standard is one example of a neighboring country formalizing how businesses must structure and exchange accounting data electronically. Denmark's approach is distinctive in requiring government registration of bookkeeping systems, but the broader regional direction is consistent: paper-based and unstructured digital bookkeeping is being phased out across Scandinavia.

Registered Bookkeeping Systems: Denmark's Unique Approval Framework

Denmark stands alone among European countries in requiring bookkeeping software to be formally registered with the Danish Business Authority (Erhvervsstyrelsen) before it can be marketed for bookkeeping purposes. No other EU member state operates an equivalent government-maintained approval framework for accounting software. For companies selecting or evaluating systems for Danish operations, this registry requirement fundamentally shapes the compliance landscape.

The Two-Track Compliance Model

The Bookkeeping Act creates a practical fork in compliance responsibility depending on whether a business uses a registered or non-registered system.

Registered system track. When a business adopts a Denmark registered bookkeeping system, the software provider has already demonstrated to the Danish Business Authority that the system satisfies all technical mandates. The provider bears ongoing compliance responsibility for maintaining those standards. This substantially reduces the individual business's burden — the company does not need to independently prove that its software handles immutable transaction recording, SAF-T export, digital storage, or e-invoicing correctly. The provider has done that work as a condition of registration.

Non-registered or custom system track. Businesses that use proprietary, custom-built, or unregistered software carry the full compliance burden themselves. They must independently demonstrate that their system meets every technical requirement the Act imposes:

Immutable transaction recording with complete audit trails
SAF-T export capability in the format specified by the Danish tax authorities
Digital storage with automated backup to a server located within the EU or EEA
E-invoicing capability supporting the required standards

This second track is not prohibited, but it demands significant internal documentation and technical validation. For organizations running bespoke ERP configurations or legacy platforms, the gap between current system capabilities and Danish requirements can be substantial.

The NemHandelsregisteret

The NemHandelsregisteret serves as the public registry where both businesses and system providers can verify a bookkeeping system's registration status. Before committing to a platform for Danish operations, compliance officers and IT managers should confirm the system appears in this registry. Registration status is binary — a system either meets the Danish Business Authority's requirements and is listed, or it is not.

For multinational organizations evaluating Denmark approved bookkeeping systems, this registry check should be an early step in the procurement process rather than an afterthought during implementation.

Why Registration Matters in Practice

The significance of this two-track model is most pronounced for small and medium-sized businesses. Organizations without dedicated compliance teams or in-house technical auditing capability reduce their exposure considerably by selecting a registered system. The provider has already invested in meeting the Danish Business Authority's technical standards, and the burden of proving ongoing compliance with software-level requirements shifts away from the business.

Larger enterprises running custom ERP deployments face a different calculus. If the system is not registered, internal teams must build and maintain documentation proving compliance across all four technical pillars. That ongoing obligation persists for as long as the business operates under Danish bookkeeping rules — it is not a one-time certification exercise.

Transaction Immutability Under Danish Law

Denmark's Bookkeeping Act establishes one of the most explicit immutability mandates in European financial regulation. The core principle is unambiguous: once a transaction has been posted in a registered bookkeeping system, the system must make it technically impossible to edit or delete that record. This is not a guideline or a best-practice recommendation. It is a system-level mandate that the software itself must enforce.

The distinction between a system-level mandate and a procedural policy requirement is critical. Many jurisdictions ask businesses to maintain unalterable records, but leave the mechanism to the organization's internal controls. Denmark does not. A company cannot satisfy the requirement by writing an internal policy that forbids employees from editing posted transactions. The bookkeeping software must architecturally prevent modification, regardless of user permissions, administrative access, or database-level intervention.

How corrections work under immutability. When an error is discovered in a posted transaction, the original record must remain exactly as it was entered. Corrections are made exclusively through new reversing entries that offset the original and, where applicable, a subsequent correcting entry that records the accurate figures. This approach preserves a complete, chronological audit trail where every action is visible and verifiable. Auditors and tax authorities can trace each correction back to its origin without ambiguity about what was originally recorded, when the error was identified, and how it was resolved.

Denmark vs. Germany: System Mandate vs. Principles-Based Compliance

The contrast with Germany's GoBD digital record-keeping framework illustrates what makes Denmark's approach distinctive. Germany's GoBD similarly requires that bookkeeping records be verifiable, traceable, and unalterable. However, GoBD achieves this through principles-based requirements. Businesses must maintain procedural documentation, implement access controls, and describe their processes in sufficient detail to demonstrate that records have not been tampered with. The emphasis is on the organization's compliance processes rather than on a specific technical capability of the software.

Denmark takes the harder line. The software itself must enforce immutability as a technical constraint. A system that relies on access controls, audit logs, or administrative procedures to prevent modification does not meet the Danish standard if it remains technically possible for any user or administrator to alter a posted record. This distinction matters significantly for compliance officers evaluating whether a single bookkeeping platform can satisfy requirements in both jurisdictions. A system that passes GoBD scrutiny through strong procedural controls may still fail Denmark's test if the underlying architecture permits record modification.

Implications for system selection. Off-the-shelf bookkeeping systems that carry registration with the Danish Business Authority handle immutability by design. The registration process itself verifies that the system meets this requirement, among others. The complexity arises with custom-built solutions or systems developed outside the Danish market. These must independently demonstrate that posted transactions cannot be altered at any level, including direct database access. For organizations running non-registered systems, meeting the immutability requirement may demand significant technical modifications to the application layer and data storage architecture, or it may necessitate replacing the system entirely with a registered alternative.

SAF-T Requirements and the SAF-T 2.0 Transition

Denmark takes a distinctive approach to SAF-T (Standard Audit File for Tax) reporting. Unlike Portugal, which mandates monthly SAF-T submissions, or Lithuania, which requires regular periodic filings, Denmark operates on a purely on-demand model. Companies are not required to file SAF-T data on any recurring schedule. Instead, Skattestyrelsen (the Danish Tax Agency) requests SAF-T files during audits, reviews, or specific compliance checks. The obligation is readiness: your bookkeeping system must be capable of producing a complete, valid SAF-T export at any time, without delay.

This always-ready requirement has implications that go beyond simply having export functionality available. The data itself must be structured correctly before an export is ever triggered, which brings us to the most critical preparatory step.

Standardkontoplan Mapping

Every business operating under Danish bookkeeping rules must map its internal chart of accounts to Denmark's official Standardkontoplan (standard chart of accounts). This mapping ensures that SAF-T exports use uniform account categorization across all businesses, regardless of how a company structures its internal ledger.

This mapping is a prerequisite for producing valid SAF-T files. Without it, an export will either fail validation or produce data that Skattestyrelsen cannot interpret in a standardized way. For companies with complex or highly customized account structures, establishing and maintaining this mapping requires deliberate effort, particularly when accounts are added, merged, or restructured over time.

Financial controllers should treat Standardkontoplan mapping as an ongoing data governance task rather than a one-time setup exercise. Each time the internal chart of accounts changes, the corresponding SAF-T mapping must be verified and updated.

Current Submission Channels

When Skattestyrelsen requests a SAF-T file, businesses can submit through three accepted channels:

TastSelv Erhverv — the business self-service portal on skat.dk, suitable for manual uploads
Web services via REST APIs — for automated or system-integrated submissions
Secure FTP — for batch file transfer

Email submission is explicitly not accepted. Businesses should confirm that their bookkeeping system supports at least one of these channels and that the technical configuration (API credentials, FTP access) is tested before a request arrives. Discovering connectivity issues during an active audit is an avoidable problem.

The SAF-T 2.0 Expansion

The current SAF-T specification covers a defined but limited reporting scope. SAF-T 2.0, with a draft published in early 2026, represents a substantial expansion that fundamentally changes what systems must be capable of exporting.

Key changes under SAF-T 2.0 include:

Full transaction-level data becomes mandatory, providing Skattestyrelsen with granular visibility into individual postings rather than summarized account balances
Mandatory master files must accompany transaction data, including customer, supplier, and account master records
19 ledgers required — a significant increase from the current specification's scope, covering areas that many systems do not currently export in SAF-T format
Mandatory for all registered digital bookkeeping systems from 1 January 2027, meaning system providers must build SAF-T 2.0 export capability into their certified platforms by that date

The technical specifications for SAF-T 2.0 are published on the Danish Business Authority's GitLab repository at git.erst.dk, giving system vendors and in-house development teams direct access to schemas, validation rules, and implementation guidance.

For businesses, the impact of SAF-T 2.0 is threefold. First, data architecture must support the extraction of 19 distinct ledger categories, which may require changes to how transactions are recorded and categorized. Second, master data quality becomes directly auditable, meaning incomplete or inconsistent customer and supplier records will surface as compliance gaps. Third, the volume and detail of exportable data increases substantially, which has implications for storage, processing time, and data validation workflows.

Nordic SAF-T in Context

Denmark is not alone in adopting SAF-T, but each Nordic country implements the standard differently. Norway, for example, has its own SAF-T mandate with distinct scope and submission requirements. Understanding Norway's SAF-T compliance requirements alongside Denmark's framework is essential for businesses operating across Nordic borders, as the differences in required ledgers, submission triggers, and file formats mean that a single SAF-T configuration will not satisfy multiple jurisdictions. Each country's implementation must be addressed independently within your bookkeeping system's export capabilities.

Digital Storage and E-Invoicing Capability Requirements

The Bookkeeping Act imposes specific obligations on how and where businesses store their financial records digitally, and requires that registered bookkeeping systems support electronic invoicing through recognized standards. These requirements affect infrastructure decisions, vendor selection, and ongoing compliance monitoring.

Digital Storage Obligations

All bookkeeping records must be stored digitally within the registered bookkeeping system for the full five-year statutory retention period. This applies to the complete range of bookkeeping material: transaction records, supporting documentation, invoices, receipts, and any other documents that form part of the accounting trail.

The five-year period runs from the end of the financial year to which the records relate. A transaction recorded in the fiscal year ending 31 December 2026, for example, must remain accessible in the system until at least 31 December 2031. Businesses cannot satisfy this obligation by exporting records to offline archives or external storage and then removing them from the bookkeeping system itself.

Mandatory EU/EEA Backup

One of the most operationally significant provisions is the automated backup requirement. Registered bookkeeping systems must provide automatic backup of all bookkeeping data to a server located within the EU or EEA. Several characteristics define this obligation:

Automation is mandatory. The backup must occur without requiring any action from the business user. A system that offers manual export or user-initiated backup does not satisfy the requirement. The software provider bears responsibility for building this capability into the system.
Server location is specified. The backup server must be physically located within the EU or EEA. This is a hard geographic constraint, not a question of which legal entity controls the data.
This is a system-level requirement. The obligation falls on the bookkeeping system provider, not on individual businesses. However, businesses are responsible for selecting a system that meets the requirement, which means verifying backup arrangements during procurement.

For businesses using cloud-based bookkeeping systems, this means confirming that both the primary storage location and the backup server reside within EU/EEA territory. A system hosted on servers in the EU but backing up to a data center in the United States would not comply.

Data Location Rules

Bookkeeping material can be stored outside Denmark, but it must remain within the EU or EEA unless the Danish Business Authority (Erhvervsstyrelsen) grants a specific exemption. Exemptions for storage outside the EU/EEA are not routinely granted and require a formal application demonstrating that the data will remain accessible and secure.

This means:

Storing data in another EU member state such as Germany, Ireland, or the Netherlands is permissible without any additional authorization.
Storing data in an EEA country (Norway, Iceland, Liechtenstein) is equally acceptable.
Storing data in the United Kingdom, the United States, or any other non-EU/EEA jurisdiction requires prior approval from the Danish Business Authority.

Companies operating multi-country cloud infrastructure should map their data flows carefully. It is not sufficient to know where the vendor's headquarters is located. What matters is the physical location of the servers that hold the bookkeeping data and its backups.

E-Invoicing Capability Requirements

Registered bookkeeping systems must support sending and receiving electronic invoices using recognized standards. This is a capability requirement on the system itself. The Act does not mandate that every business transaction use e-invoicing, but the system must be capable of handling e-invoices when required.

Two e-invoicing standards are relevant under the current framework:

OIOUBL is Denmark's national e-invoicing standard, mandatory for business-to-government (B2G) transactions since 2005. The planned successor format, OIOUBL 3, was cancelled by Danish authorities in January 2026, removing what had been an anticipated migration path for system providers and businesses alike. OIOUBL 2.1 remains the operative national standard with no announced replacement timeline.

Peppol BIS 3.0 is the pan-European e-invoicing standard operated through the Peppol network. It enables cross-border e-invoicing across participating countries and is increasingly used for both B2G and B2B transactions throughout Europe. Denmark is a Peppol member country, and the standard is widely adopted for transactions involving Danish public sector entities as well as private sector trading partners across the EU.

With the cancellation of OIOUBL 3, the two operative standards going forward are OIOUBL 2.1 and Peppol BIS 3.0. Registered bookkeeping systems must support these formats to maintain their approved status. For businesses evaluating or switching systems, confirming support for both standards should be a non-negotiable item on the procurement checklist.

Penalties for Non-Compliance

Denmark's enforcement framework for the Bookkeeping Act carries consequences that range from moderate fines to an outcome most businesses would consider existential: forced dissolution. Understanding the full spectrum of these penalties is essential for any company subject to the Act's requirements.

Fine Structure

Violations of the digital bookkeeping requirements carry fines ranging from DKK 10,000 to DKK 1,500,000 (approximately EUR 1,350 to EUR 200,000). The severity depends on the nature of the violation, its duration, and whether it reflects a pattern of non-compliance. According to KPMG Denmark's overview of the digital bookkeeping requirements, Denmark's digital bookkeeping law imposes fines up to DKK 1.5 million for violations of digital bookkeeping requirements, with phased compliance deadlines requiring companies filing annual reports to comply from January 2025 and sole proprietorships with turnover exceeding DKK 300,000 to comply from January 2026.

These are not theoretical maximums. The Erhvervsstyrelsen (Danish Business Authority) has clear statutory authority to impose fines at the upper end of this range for serious violations, particularly where a business has failed to respond to prior compliance orders.

Forced Dissolution

The most severe enforcement mechanism available under the Act is one that has no direct equivalent in most other EU jurisdictions: the Erhvervsstyrelsen holds the legal authority to dissolve a company for serious or persistent non-compliance with bookkeeping requirements.

In most European countries, bookkeeping violations result in fines, administrative orders, or in extreme cases, director disqualification. Denmark goes further. Where a business repeatedly fails to meet its obligations under the Bookkeeping Act, or where the violations are sufficiently serious, the Erhvervsstyrelsen can initiate dissolution proceedings through the Danish courts. This reflects the Danish legislature's view that proper bookkeeping is not merely an administrative formality but a fundamental condition of operating a registered business.

The Act's graduated enforcement structure positions dissolution as the culmination of escalating interventions. Compliance orders and fines precede it, and the power targets cases of sustained or egregious non-compliance rather than first-time oversights. But the legal authority exists, and its presence elevates the risk profile well beyond what businesses accustomed to other EU regulatory environments might expect.

Enforcement Process

The Erhvervsstyrelsen operates a graduated enforcement approach:

Compliance checks. The Authority conducts reviews of businesses and registered bookkeeping system providers, assessing whether they meet the Act's requirements for digital storage, transaction immutability, and SAF-T export capability.
Compliance orders. Where deficiencies are identified, the Authority issues formal orders specifying what must be corrected and within what timeframe.
Fines. Failure to comply with orders, or violations identified as sufficiently serious on first detection, results in financial penalties within the DKK 10,000 to DKK 1,500,000 range.
Dissolution proceedings. For the most serious or persistent cases, the Authority initiates court proceedings to dissolve the non-compliant entity.

Provider vs. Business Liability

The Act creates distinct liability tracks depending on whether non-compliance originates at the system level or the business level.

Registered bookkeeping system providers face penalties for system-level failures. If a provider's registered system does not properly implement immutability controls, fails to support SAF-T export in the required format, or otherwise falls short of the technical standards set by the Erhvervsstyrelsen, the provider bears direct regulatory exposure. In severe cases, a system's registration can be revoked, which has cascading consequences for every business relying on that system.

Businesses are liable for their own compliance regardless of the system they use. A company that chooses a non-registered system, or that uses a registered system improperly, bears the full weight of potential penalties. The Act does not allow businesses to shift blame to their software provider if the business itself has failed to maintain compliant bookkeeping practices.

Active Enforcement Timeline

The phased rollout of the Act means penalties are not a future concern for most businesses. Companies required to file annual reports with the Erhvervsstyrelsen have been subject to enforcement since July 2024 (Phase 1) and January 2025 (Phase 2). Sole proprietorships with annual turnover exceeding DKK 300,000 fall under enforcement from January 2026 (Phase 3).

For businesses already within scope, the window for remediation without penalty exposure has closed. The Erhvervsstyrelsen's compliance monitoring is operational, and the full enforcement toolkit is available for use against non-compliant entities.

How the Bookkeeping Act Applies to Foreign Companies

The Bookkeeping Act's territorial reach extends beyond Danish-incorporated entities. Any business conducting commercial activities in Denmark falls within its scope, regardless of where the parent company is headquartered. The determining factor is not nationality of ownership but presence and activity on Danish soil.

Danish subsidiaries incorporated under Danish company law (ApS, A/S, or other Danish legal forms) are treated identically to any domestic business. They must comply with every provision of the Bookkeeping Act in full, including use of a registered bookkeeping system once their revenue exceeds the applicable threshold. The fact that a Swedish, German, or American parent company owns the subsidiary is irrelevant to the compliance obligation.

Danish branches (filialer) of foreign companies registered with the Erhvervsstyrelsen carry the same bookkeeping obligations for their Danish operations. A branch is not a separate legal entity, but the Bookkeeping Act still requires that transactions attributable to Danish commercial activity be recorded, stored, and reported according to Danish rules. The branch must maintain books that can be audited independently of the parent company's home-country records.

Foreign companies without a formal Danish presence but generating revenue through Danish operations should assess whether their activities constitute a taxable presence (fast driftssted). If Danish tax authorities determine that a permanent establishment exists, bookkeeping obligations follow.

Can Foreign Companies Use Their Home-Country Systems?

This is the most common practical question for international groups. The answer is conditional: a foreign bookkeeping system may be used for Danish operations only if it satisfies every Danish requirement. That means the system must support transaction immutability with sequential numbering, SAF-T export in the Danish-specific format, digital storage with backup within the EU or EEA, and e-invoicing capability for Nemhandel transactions.

Many enterprise ERP platforms used by multinational corporations can be configured to meet these requirements through Danish localization modules. However, configuration alone is not the same as compliance. The system must actually enforce immutability rules as defined by Danish law, not merely offer an optional audit trail.

If the home-country system cannot be adapted, the foreign company has two paths:

Adopt a registered Danish bookkeeping system for its Danish operations, which provides the reduced compliance burden and regulatory certainty that registration confers.
Maintain a parallel compliant system solely for Danish transactions, feeding data back to the group's consolidated reporting as needed.

The first option is typically simpler for small to mid-sized Danish operations. The second may suit large multinationals that prefer a unified global platform but must overlay Danish-specific controls.

Multi-Jurisdictional Considerations

Denmark's digitization requirements do not exist in isolation. Norway mandates SAF-T reporting. Sweden enforces its own Bokföringslag with digital archiving rules. Germany's GoBD imposes strict immutability and retention requirements. Companies operating across Nordic and EU jurisdictions face overlapping but non-identical obligations in each country.

This convergence makes it worth evaluating financial document processing tools that handle multi-jurisdictional requirements from a single workflow, rather than maintaining entirely separate compliance stacks per country. The cost of managing four or five distinct bookkeeping environments, each with its own retention rules, export formats, and audit requirements, often exceeds the cost of consolidating onto platforms designed for cross-border financial operations.

Foreign companies entering the Danish market should budget compliance setup time accordingly. Registering a branch, selecting or configuring a compliant bookkeeping system, establishing SAF-T export capability, and connecting to the Nemhandel network are not tasks that can be completed in a single week. Starting the evaluation process well before the first Danish invoice is issued avoids the risk of operating outside compliance from day one.