Visma Horizon integration
We connect your online store, CRM or warehouse system to Visma Horizon so invoices, orders and stock levels move automatically — with no double entry and no errors that come with it.
What integration with Visma Horizon does in practice
Visma Horizon is an accounting and business management system used by many companies in Latvia. If your online store, CRM or warehouse system runs separately from it, orders, invoices and stock levels have to be reconciled by hand every day.
Integration means the systems exchange data themselves: an order from the store becomes an invoice in Horizon, stock levels are synchronised, and documents reach accounting without a manual step in between.
We build these connections to order — both between popular platforms and between your own systems. The scope depends on the number of processes and on how unusual the data flow is.
Which processes can be automated
As with other accounting systems, it makes sense to start with the processes that currently consume the most manual work, and add the rest gradually.
- Orders from the online store automatically become sales documents with the correct customer, products and prices.
- Stock levels are synchronised between the store and Horizon in both directions.
- New customers from the store are created in Horizon as well; existing ones are not duplicated.
- The product and service list is maintained in one place so prices and names match in both systems.
- Incoming payments are matched to the corresponding documents.
- Data is prepared so it can also be used for reporting and analysis, not only for accounting.
What it changes in day-to-day work
When data is not entered twice, most of the sources of error disappear and the time spent reconciling data every week drops noticeably.
Accounting works with current data rather than information that has to be collected from several places. That means less manual checking at month-end closing.
For management it means seeing turnover and stock closer to real time, because the data no longer lags a week or two behind.
When integration matters most
Integration matters when order volume is growing, when several sales channels are used at once, or when stock data has to be reconciled with accounting daily.
If volume is still small, you can start with a narrower connection — for example, just moving orders and invoices — and expand it when the need appears.
What determines the scope and the timeline
The main factor is how ready both systems are for data exchange. If an API is available, the connection can be built directly and predictably.
If there is none, a solution is still possible — through data export, intermediate files or at the database level — but the scope and risks then need closer assessment as a separate research step.
Synchronisation frequency, data volume, whether historical data must be migrated, and the number of edge cases all matter as well.
What's included?
Review of both systems and the data flow
Agreeing the synchronisation scenarios before development starts
Building and configuring the connection
Error handling and retry logic
Protection against duplicating records
Testing on real data before launch
Reconciling products, customers and opening stock balances
A written explanation of what to do if synchronisation stops
Why choose us?
Full cycle
Development, design, hosting, email, maintenance — all in one place. No need to coordinate multiple vendors.
Own infrastructure
Client projects run on our servers with 24/7 monitoring. We catch issues before your visitors do.
Clear pricing
A development plan before work starts and a fixed project price. No upfront payment for small jobs.
Direct contact
You talk directly to the developer, not a project manager. Faster decisions, fewer misunderstandings.
How we work
1. Research
We review both systems, the data structure and which processes are currently done by hand.
2. Plan
We define which data is synchronised, in which direction and how often, and agree on the scope.
3. Development
We build the connection, respecting the logic and limits of both systems.
4. Testing
We check typical and difficult cases: returns, partially paid invoices, multiple warehouses.
5. Launch
We start with a small volume, watch the result, and then switch on the full flow.
Frequently asked questions
Is integration possible with any online store?
Yes, if the system offers a way to exchange data — an API, a data export or database access. If it does not, a solution is still possible, but it has to be assessed separately.
Will data be lost if synchronisation is interrupted?
We build the solution so failed operations are retried and it is always visible what has been synchronised and what has not.
What happens to data that already exists?
Before launch we reconcile the opening state of customers, products and stock levels so both systems start from the same point.
Can only part of the processes be connected?
Yes. We often start with orders and invoices, and add stock synchronisation later.
Does anything need to change on the Horizon side?
Usually not. The connection works with what the system already provides. If a specific process needs changes, we agree that separately before work starts.
Who maintains it after launch?
After launch you can maintain it yourself, or take out a maintenance agreement under which we track changes in both systems.
How long does it take?
The timeline is set by the research step. We give a firm timeline after the research, not before.
Other services
You may also be interested in
Ready to start your project?
Get in touch today for a free consultation.