Company routing
Documents are routed to the correct company file when a client runs more than one Visma company.
Home › Integrations › Visma eAccounting
What to add when Visma eAccounting's native tools fall short
Visma eAccounting already reads invoices and takes e-invoices through AutoInvoice. A pipeline only earns its place on multi-company setups, other document types and matching across systems.
Native OCR + PEPPOLVisma eAccounting already captures invoices and e-invoices on its own; the case for a pipeline is what sits outside that flow.
Region NordicsNative capture Built-in OCR for invoicesE-invoicing AutoInvoice PEPPOL access pointCategory Accounting
Capturedocument arrives by email or upload
Native OCRVisma reads standard invoices on its own
AutoInvoicee-invoices arrive via PEPPOL
Routeother docs routed to the right company
Reconcilematched across systems, exceptions flagged
What lands in Visma eAccounting
Non-invoice records
Receipts and other documents outside AutoInvoice's e-invoice flow are captured and entered too.
Cross-system match
Records are matched against data held in another system, such as a CRM or stock list.
Header fields
Supplier, invoice number, dates and totals are set on the record.
Source file
The original document is attached for the audit trail.
Exception flag
Anything uncertain is flagged for review rather than posted.
Where it gets awkward
Every system has edges. These are the ones that shape the build — better known before the pilot than during it.
Native tools cover invoices only
Built-in OCR and AutoInvoice handle standard invoices and e-invoices; other document types still sit outside that flow and need their own path in.
One company at a time
Where a client runs more than one Visma company, something still has to decide where each document belongs unless that routing is automated.
No cross-system view
Native capture does not check a document against records held in another system, such as a CRM or a stock list.
Is a custom pipeline worth it here?
Worth building
- You run more than one Visma company and documents need routing to the right one.
- You handle documents outside the invoice flow, like receipts or delivery notes.
- Invoices need matching against records held in a CRM or a stock system.
Native tools are enough
- You run a single company and only process standard supplier invoices.
- AutoInvoice covers your e-invoice volume and nothing else needs matching.
The task behind this
Solution
Invoices and receipts posted into your accounting system automatically
Supplier invoices and staff-photographed receipts posted straight into Merit Aktiva, Xero, QuickBooks and more, with exceptions sent to a review queue.
→How the stream is built
Processed in the EU. The original files and extracted data stay in your own systems; a data-processing agreement is available on request — see security and data handling.
From audit to autopilot
Step 1
Audit
We map one document or enquiry stream end-to-end, count volumes and name the systems it touches. You get a written scope and a fixed pilot price.
Free · 3 working daysStep 2
Pilot
One stream goes live on your real documents. Acceptance is measured, not felt: straight-through rate, minutes per document, exceptions.
About two weeks · fixed priceStep 3
Rollout
The remaining streams follow the proven pattern. Monthly report, support, and changes as your systems change.
Stream by streamFrequently asked questions
Does Visma eAccounting already have OCR?
Yes. It has native invoice capture, and AutoInvoice acts as a PEPPOL access point for e-invoices. For a single company processing standard invoices, that is often enough on its own.
When does a pipeline make sense on top of Visma?
It earns its place on multi-company setups, on documents outside the standard invoice flow, and where records need matching against another system such as a CRM or stock list.
What does AutoInvoice not do?
AutoInvoice is a PEPPOL access point for e-invoices. It does not route documents between multiple company files, and it does not check an invoice against data held outside Visma.
What happens to documents the pipeline is not confident about?
They go to a review queue in a tool you already use, so a person checks or approves them before anything is posted.
Where is the data processed?
Processed in the EU. The original files and extracted data stay in your own systems; a data-processing agreement is available on request.
Using Visma eAccounting? Start with the audit
Three working days, one document stream mapped end to end, a fixed pilot price on paper. No commitment.
Get a free automation audit