Visma Horizon is one of the best-known enterprise resource planning (ERP) and accounting systems developed in Latvia, owned by the international Visma group. It is chosen by mid-sized and large companies, as well as public-sector organisations, for which a basic invoicing and bookkeeping package is no longer enough — businesses that need finance, multiple warehouses, purchasing, payroll and production working inside a single system.
What Visma Horizon is and what it covers
Horizon is a full ERP-class system. Unlike software intended purely for issuing invoices and filing tax returns, an ERP connects operational areas so that an event in one department immediately updates the others: receiving goods into a warehouse updates inventory valuation on the balance sheet, a manufacturing order reserves raw materials, and a sales invoice generates ledger entries and e-invoice workflows automatically.
In practice, a typical Horizon deployment brings together four core blocks:
- Financial accounting: sales and purchase invoices, general ledger, bank and cash operations, fixed assets, budgeting, Latvian VAT and VID reporting, as well as structured e-invoices (mandatory for B2G transactions in Latvia since 2025 and becoming mandatory for B2B from 01.01.2028).
- Logistics and warehouse management: multi-warehouse stock tracking, batch and expiry-date control, serial numbers, stock reservations, purchasing and sales workflows.
- HR and payroll: employee records, leave and sick-leave tracking, work schedules, payroll calculation and HR document flows.
- Production and projects: bills of materials, raw-material write-offs, cost calculation and revenue/expense tracking across projects or analytical dimensions.
Because each company selects its own module set, the exact feature list and licensing structure are best verified directly on the vendor's website.
How Horizon differs from a plain accounting package
The fundamental difference lies in how deeply the system manages daily operations rather than merely recording transactions after the fact.
| Criterion | Plain accounting software | ERP system (Visma Horizon) |
|---|---|---|
| Core question answered | "Which documents and taxes do we have?" | "What is happening in the business right now with cash, stock and costs?" |
| Warehouse support | Single warehouse or none | Multiple warehouses, transfers, batches and reservations |
| Cost analytics | Basic income and expense accounts | Dimensions, projects, departments, production costing |
| User roles | Mainly 1–3 accountants | Finance, warehouse, sales, management, HR |
| Implementation timeline | A few days | Several weeks to several months |
That is why Horizon is typically adopted once a company operates more than one warehouse, runs manufacturing or assembly, or sells through multiple channels that all must feed a single set of books.
When Horizon is the right choice — and when it is not
The system earns its keep when a business meets at least two of the following conditions:
- A flow of goods or materials too complex to track reliably in spreadsheets or lightweight accounting tools.
- Manufacturing, kitting or service costing, where accurate unit costs, material consumption and lead times drive margins.
- Multiple sales channels running in parallel: an online store, a B2B wholesale portal, physical retail locations and direct sales.
- Continuous management visibility, with profitability broken down by project, branch or product category rather than waiting until quarter-end.
Conversely, if a company only needs to issue a few dozen service invoices per month and submit standard tax filings, an ERP-class platform will be heavier than necessary, requiring more budget and implementation time than the business can justify.
Why integration becomes a practical bottleneck
Even a capable ERP system does not cover 100 % of a company's digital stack. Customer-facing tools — an online store, B2B ordering portal, mobile app, CRM or parcel-locker/courier services — almost always live outside Horizon.
Without an automated connection between these environments, teams fall back on manual retyping: staff copy web orders into Horizon by hand, update prices manually and reconcile stock levels at the end of the day. As a result, accounting lags behind reality, online stock counts drift from what is actually on the shelf, and manual entry errors creep into invoices and waybills.
What integration with Visma Horizon means in practice
Integration is a reliable, automated bridge that moves data between Horizon and your external systems according to clear business rules. In a typical e-commerce or B2B portal integration, four data flows are connected:
- Product catalogue and pricing (Horizon → Store): product names, SKUs, descriptions, VAT rates, base prices and customer-specific B2B discount tiers.
- Inventory levels (Horizon → Store): available stock (net of reservations) synchronised every 5–15 minutes or in near real time.
- Orders and invoices (Store → Horizon): paid or confirmed orders automatically create sales documents in Horizon, including shipping lines (Omniva, DPD, courier) and discount coupons.
- Customers and payments (Bidirectional): creating new customer records with registration/VAT number checks without duplicates, plus matching payment statuses.
Technically, the connection is built via Horizon's REST API or XML data-exchange interfaces. If a company runs an older or heavily customised setup without direct API access to a specific module, the viable integration path is scoped during a dedicated technical discovery step.
Technical approaches to integrating Visma Horizon
When connecting Visma Horizon with an online store or B2B portal, teams typically choose among three integration architectures, each with different cost, speed and resilience trade-offs.
| Approach | How it works | Advantages | Best suited for |
|---|---|---|---|
| Direct REST API | Middleware communicates with the Horizon API on schedule or near real time | Officially supported data exchange, structured error diagnostics | Modern online stores, B2B portals and CRM platforms |
| XML / file-based exchange | Scheduled export and import of documents and product feeds | Easier to adopt in older setups without full API coverage | Low order volumes or end-of-day batch synchronisation |
| Dedicated sync middleware | Standalone service with a message queue, cache and data mapping layer | Protects Horizon from traffic spikes and retries failed jobs automatically | Large catalogues (10,000+ SKUs), multiple warehouses and high order volume |
Practical scenario: a wholesaler with an online store and two warehouses
Consider a Latvian distributor selling building materials or spare parts both wholesale (B2B) and direct-to-consumer online. The catalogue holds 8,000 SKUs split between a Riga warehouse and a supplier depot. Without integration, sales staff check stock manually every morning and accounting retypes web orders two days later.
Once a Visma Horizon integration is in place: - every 10 minutes the storefront receives available stock from both locations and displays accurate delivery lead times; - a B2B buyer logging into the portal immediately sees their contract-specific discount tier from Horizon; - as soon as an order is paid by card or bank link, Horizon automatically creates the sales document, links the payment and prepares structured e-invoice data.
This eliminates 15–25 hours of manual work per week and prevents overselling out-of-stock items.
What to check before starting a Horizon integration
Before writing integration code, four practical decisions largely determine whether the project runs smoothly:
- Start with the biggest bottlenecks. Automate order transfer and stock sync first — where manual hours hurt most — before adding secondary reporting flows.
- Clean and align master data. Both systems must share identical SKU codes, VAT rounding rules and customer identifiers prior to launch, or sync will generate duplicates.
- Design for failure recovery. The bridge should include a retry queue, idempotency checks (so a network timeout never creates duplicate invoices) and clear error logs with alerts.
- Use a staging database. Always validate the integration against a Horizon test database before switching on live accounting.
Summary
Visma Horizon is a robust ERP and accounting platform from the Visma group that delivers the highest return for businesses with multiple warehouses, production or multi-channel sales. In practice, its weak point is rarely the software itself, but being disconnected from the rest of the company's tools. A well-engineered integration unlocks Horizon's full value while eliminating manual data entry. Learn more about our approach on the Visma Horizon integration page.
