Approach
ERP.net offers several approaches for transitioning from BGN to EUR. Review the approaches and decide which is the best option for you. If you do not request a change, Approach A1 will automatically be applied to your database.
A1. Change in the same database (in-place)
This is the default approach. With this approach, the database remains the same, and the changes are made in place.
Advantages:
Easiest for users
Fully automatic
No duplicate data entry is required if and when changes in 2025 data are necessary
Business processes remain unchanged – everything continues seamlessly during the transition
No transfer of opening balances (and no similar data migrations required)
Disadvantages:
The most complex for the vendor to develop and support
Working with both BGN and EUR simultaneously in one database
This is the default approach and will be applied to all databases in which ALL Enterprise companies have BGN as their base currency. If you have some companies with base currency BGN and others with a different base currency, please contact our support.
A2. Creating new Enterprise Companies (EC) in the same database
With this approach, two ECs are created for each company – one up to 31.12.2025 and another for data after 01.01.2026. The drawback is that opening balances must be transferred.
It should be noted that ERP.net licensing policy in v.26 has been updated to better support this approach. Two OCs under the same Company no longer require separate EC licenses. Thus, this approach will not increase costs.
Advantages:
The change is in the same database and history is preserved
No mixing of EUR/BGN in a single EC
Disadvantages:
Two OCs must be created in the database for each real Enterprise company
Opening balances must be transferred as if for an initial implementation
Business process settings must be reviewed and reconsidered – whether some apply only to the old OC
A3. Change in a copy of the database
With this approach, a copy of the database is made, and only the new database is updated to EUR. The issue with this approach is that if and when changes need to be made in the previous year, these changes must be entered in both the new and the old database. Additionally, having both an old and a new database increases costs.
Advantages:
Easy for support to implement (though manual)
Disadvantages:
Duplication of every correction for 2025
No history of BGN transactions in the new database (must log in to the old database)
High cost (licensing two databases)
A4. Completely new database
With this approach, you start fresh in a brand-new database from 01.01.2026.
The procedure in essence
The transition to EUR in ERP.net will be carried out by converting the base currencies of all Enterprise companies currently in BGN. All base currency values in various documents and definitions will be converted to EUR.
Transition applies only to Enterprise companies with BGN as their base currency.
If the database is mixed (some ECs in BGN and others with a different base currency), you must contact support.
During the transition, all currency values (prices, amounts, totals, etc.) previously in BGN will be recalculated and rewritten in EUR.
Currency values will be recalculated from the beginning of the database’s existence – as if it had always been in EUR.
For accounting closing and preserving historical BGN values, a concept of Reporting Currency is introduced. This is a second base currency. Before converting base values to EUR, the base values in BGN will be copied into the Reporting Currency. The 2025 year-end closing will be performed in the Reporting Currency.
Process steps
Upgrade to version 2026. Must be completed by the end of October 2025.
On 01.11.2025, Reporting Currency calculation will be activated automatically. The calculation will take several days or weeks.
On 01.01.2026, default values will be automatically converted. This will take from a few minutes to a few hours.
On 16.01.2026, base currencies will be automatically converted. This is the heaviest procedure. Calculations may take from hours to dozens of hours in large databases.
Automatic mode (Default)
If all ECs in your database are in BGN, no action is required from you. The entire transition will be carried out automatically for your instance, according to the default approach and the steps listed here. No actions are required on your part.
Still, before 01.01.2026, a few things must be done:
Verify that Reporting Currency has been calculated correctly. Balances in base and reporting currency must match as of 31.12.2025.
In the Excise module, new excise rates in EUR must be entered starting 01.01.2026. The table does not have a currency field, but values for 2026 must correspond to excise amounts in EUR.
Check and adjust the “Use Base Currency” flags in payment account definitions. The flag must remain only for those accounts whose currency will be automatically switched to EUR. This does not affect already created payments.
Check and adjust the “Restrict to Base Currency” flags in GL account definitions. The flag must remain only for those accounts whose currency will be automatically switched to EUR. This does not affect already created journal entries.
If you want to customize or modify the automatic transition procedures, you need to contact support and/or review the procedures for Customizing and manual mode of the transition to euro.
Procedure in bulgarian:
ERP.net - EUR Changeover Procedure.pdf
Customizing and manual mode:
0 Comments