e-conomic publishes extensive measures for protecting its service and customer data. An independent e-conomic data backup adds dated copies that a business can use when data is deleted, overwritten or incorrectly changed. DataRavn provides an automated e-conomic backup for supported data, a self-hosted MySQL option, several recovery levels and logs for backup and restore activity.

How e-conomic data recovery differs from platform security

Visma e-conomic documents encryption in transit, restricted access, firewalls, vulnerability scanning and penetration testing. It also reports an annually reviewed ISAE 3402 statement covering its IT operations, including security, reliability and availability. These measures protect the e-conomic service and the data held within it.
Operational recovery addresses a different event. An invoice draft may be deleted. A VAT account may be changed. A customer or supplier record may be overwritten. The service can remain available throughout, while the accounting team still needs an earlier version of the affected data.
An independent backup provides that separate recovery point. DataRavn is listed in the e-conomic app market as a backup service that keeps dated versions and supports hosted or self-hosted storage.

1. Is the backup independent?

A useful backup should exist separately from the live e-conomic account. When a record changes in the accounting platform, a dated copy should remain available for recovery.

DataRavn connects to e-conomic through its official API after authorisation. The connection is read-only during backup, and no plugin is installed in e-conomic. Backups then run to the agreed schedule while the accounting team continues its work.

Independence also needs to be documented. Ask which credentials DataRavn uses, who can change the backup scope and what happens when an API job fails. DataRavn reports failed jobs in its logs and retries them.

2. Where is the backup stored?

Storage location affects internal IT requirements, data residency reviews and access policies.

DataRavn supports a self-hosted MySQL backup for e-conomic. Backup data is written to a MySQL database within infrastructure managed by your organisation. DataRavn-hosted and isolated environments are also available under other plans, but self-hosting gives teams a route for keeping the database within their managed environment.

Before selecting self-hosting, agree who is responsible for database availability, patching, access, encryption, monitoring and protection of the MySQL database itself. The result should be a written division of duties between your team and DataRavn.

3. How often does the backup run?

Backup frequency determines how much recent work may sit between the latest stored copy and an incident.

DataRavn currently provides:

  • Weekly automated backup with the Standard plan

  • Daily automated backup with the Gold plan

  • A custom frequency with the Enterprise plan

The right interval depends on transaction volume and the hours in which changes occur. A company posting a small number of entries may accept a weekly copy. A bookkeeping firm working across many e-conomic agreements may need daily runs or a schedule agreed around posting periods and reporting deadlines.

Write the frequency into the backup policy. “Automatic” is too broad for an internal review. “Daily at an agreed time, with failed jobs retried and reported” gives the team something it can check.

4. How long are dated versions kept?

Retention should reflect how long an error can remain undiscovered.

DataRavn lists seven-day retention for Standard, 14 days with extension options for Gold, and a custom period for Enterprise. If an incorrect change may only be found during a monthly review, a seven-day history may be too short. The chosen period should cover the likely gap between a change and its discovery.

Accounting practices may need different periods for different customer groups. Retention should therefore be agreed alongside reporting timetables, internal review cycles and any contractual commitments made to customers.

Retention for recovery should also be separated from statutory record keeping. A dated backup history supports the return of earlier data. Long-term accounting records and supporting documents may be subject to separate legal and contractual requirements.

5. Which e-conomic data is included?

A statement such as “your e-conomic data is backed up” needs a coverage list behind it.

DataRavn backs up supported entities exposed through the e-conomic API. Its published coverage includes:

  • Accounts, VAT accounts, VAT types and VAT zones

  • Customers, customer groups and customer contacts

  • Suppliers and supplier groups

  • Invoices, orders and quotes

  • Products, product groups and units

  • Employees and employee groups

  • Payment terms, currency settings and delivery locations

Each supported entity is versioned. DataRavn states that standard objects available through the main e-conomic product are covered. Paid add-ons can introduce further objects, so coverage for those modules should be confirmed during a technical review.

This review is especially important for accounting firms. A service that covers the usual records for one customer may need an adjusted scope for another customer using additional e-conomic modules.

6. What can be recovered?

Recovery should match the size of the incident.

DataRavn supports the return of:

  • A single record

  • A specific object type, such as VAT accounts

  • Selected entities

  • The full dataset when required

This range allows a team to return the affected data while preserving later entries that are still valid. Each restore is role-based and logged, including the user and time. That record helps reviewers match a recovery action to the request that authorised it.

A product demonstration should include a recovery test. Ask the provider to show how a dated version is found, who can approve the action, what will be changed in e-conomic and where the result is recorded.

Where manual exports fit

e-conomic provides export routes for accounting data and documents. Its support guidance describes these exports as a way to retain required material when ending an e-conomic agreement.

Exports support archival and handover needs. Scheduled, dated backups support day-to-day recovery. A manual export taken last quarter will have limited value when the team needs the version of a VAT account from last Tuesday.

Many organisations need both: an archive process for long-term record keeping and a backup process for returning changed or deleted data.

A six-point review for your e-conomic account

Before choosing a backup service, record the answer to each question:

  1. Is the copy separate from the live e-conomic account?

  2. Will the backup use self-hosted MySQL or provider-hosted storage?

  3. Does the schedule match the volume and timing of accounting work?

  4. Does retention exceed the likely time before an error is found?

  5. Are all required e-conomic entities and add-on modules covered?

  6. Can the team return one record, selected entities or the full dataset, with an activity log?

These answers turn “we have backup” into a process that finance, IT and auditors can examine.

See DataRavn for e-conomic

DataRavn provides independent backup and recovery for supported e-conomic data. It includes automated schedules, dated versions, self-hosted MySQL, several recovery levels, role-based permissions and activity logs.

Start with one e-conomic agreement. Confirm the entity list, select a schedule and retention period, decide where the MySQL database will run, and test a recovery before extending the process further.

Review DataRavn for e-conomic or start a 14-day trial. For an accounting practice or a company with additional modules, ask for a technical review of coverage and hosting responsibilities before purchase.