Velion
Document automation integrations

Connect document automation to your business systems

Turn incoming documents into structured, validated information and deliver it where your business needs it. Connect RIV4 to existing software, or use it as the processing backend of your own application.

Explore native integrations for ERP, CRM, DMS and TMS, or connect your existing applications through APIs, webhooks and configurable data exchange.

Explore integration optionsBook a demo

One document engine.
Two ways to integrate.

Two integration models

Whether you are enhancing an existing business system or building your own software, RIV4 fits into your application architecture.

Integrate

Connect your existing software

Deliver document data to the ERP, CRM, DMS or TMS your teams already use, through an existing integration or a configured delivery route.

  • Native integrations
  • API
  • Webhooks
  • File exchange
Software

Build

Embed RIV4 into your applications

Use RIV4 as the document-processing backend of your software. Your application controls the experience; RIV4 handles document intelligence and returns the results.

  • API-first
  • Orchestration
  • Structured results
API-first

Powered by the RIV4 DEEP Pipeline.

  • Detect
  • Extract
  • Enrich
  • Push

The same processing engine underlies both models; its detailed workflow is explained on Features.

Discover how DEEP works

Choose how data reaches your systems

Connection methods

For software already supported by RIV4, use the available integration. For custom applications, enterprise environments and project-specific implementations, configure the appropriate interface.

Webhook · JSON push

Send structured results to an HTTPS endpoint after document processing.

For event-driven systems and integration layers.

REST API · pull

Retrieve processing status, results and available artifacts from your application.

For app-controlled workflows and middleware.

File exchange · FTP/SFTP

Deliver configured output files for scheduled imports and batch processes.

Standard exports: XLSX, CSV, XML and TXT.

Email delivery

Route an output file to designated recipients or an agreed email-based process.

For controlled operational hand-offs.
The receiving system’s data import or write-back behavior depends on its configuration and the integration project.

Explore the software in our integration ecosystem

Software ecosystem

Browse ERP, CRM, DMS and TMS products. Existing native integrations and configurable connection routes are identified separately; exact versions, modules and prerequisites are confirmed for each project.

  • ERPBlusys

    Mistral

    ERP for order processing, commercial operations and administration.

    Native integration
  • ERPAzerouno

    Concept ERP

    ERP for metal fabrication, quotations, production and warehousing.

    Native integration
  • ERP

    Integro 360

    Modular ERP/CRM for manufacturing, planning and business operations.

    Native integration
  • ERPNTS

    NTS Business Experience

    ERP for administration, logistics, manufacturing and customer processes.

    Native integration
  • ERP

    SAP

    Enterprise ERP for supply chain, production, finance and procurement.

    Native integration
  • ERPMicrosoft

    Microsoft Dynamics 365 Business Central

    ERP for finance, sales, purchasing and operations; connection via agreed APIs or integration middleware.

    API / middleware route
  • ERP

    Edison

    Management software for installers and field-service companies.

    Native integration
  • ERPBoostar

    Venus

    ERP for energy and gas sales and back-office operations.

    Native integration
  • ERPZucchetti

    Mago

    Modular ERP family for accounting, sales, purchasing, warehousing, logistics and manufacturing.

    Scope to confirm
  • ERPLinfa Srl

    Linfa

    Italian vertical ERP for retail chains and organised distribution: sales, logistics, accounting and point of sale.

    Scope to confirm
  • CRM

    SuiteCRM

    Customer relationship management for sales, marketing and support.

    Native integration
  • DMSCanon

    Therefore

    Document management and business workflow environment.

    Native integration
  • DMS

    Adiuto

    Document management and workflow platform.

    Native integration
  • DMS

    Globe

    Document intelligence and information-management platform.

    Native integration
  • TMS

    TIR ELITE

    Transport management for road operations, fleet and administration.

    Native integration
  • TMS

    Holos

    Transport and logistics management for operators and freight forwarders.

    Native integration
  • TMSMAX Software

    SpeedyWEB

    Management software for freight forwarders, shipping agencies and warehouses, with quotations, invoicing and web tracking.

    Scope to confirm

Connect RIV4 to SAP and Microsoft Dynamics 365 Business Central

International ERP

Use APIs and/or the integration middleware in your environment to connect document automation to your ERP processes. RIV4 prepares structured data without asking you to replace the ERP that runs your business.

SAP

SAP environments

Connect RIV4 document workflows to your SAP architecture through the relevant supported interfaces or your existing middleware. Confirm the SAP environment, objects, permissions and mappings for the project.

Discuss your SAP workflow
Microsoft Dynamics 365 Business Central

Dynamics 365 Business Central

Prepare document data for Business Central through agreed APIs, webhooks or a customer-managed integration layer. Define the data mapping and receiving-side operations with your team.

Discuss your Business Central workflow

Build document-powered
applications with RIV4

RIV4 API-first

Integrate RIV4 as the intelligent document-processing backend of your own software. Use its APIs to supply documents, follow processing and retrieve structured results, with configured webhook delivery when needed.

Built for development teams, system integrators and software vendors.
Discuss API integration
  1. Your applicationUpload or supply documents
  2. RIV4 APIOrchestrate the configured workflow
  3. DEEP processing engineDetect · Extract · Enrich · Push
  4. Structured resultsJSON · results · optional webhooks
Discuss API integration

What your IT team needs
to get started

For IT teams & integrators

An initial integration discussion can start with three concrete inputs—not a lengthy architecture exercise.

A representative document

An actual order, invoice, delivery note or other recurring document, including a relevant exception.

The receiving system

The target application and the operation you want to enable—for example creating a draft or supplying an import flow.

The expected data exchange

The required fields and line structure, plus an API, webhook, middleware or file specification if available.

From there, we agree mappings, checks, access requirements and validation cases with the project team.

Discuss your integration architecture

Choose the deployment model with your architecture in mind

Deployment options

Plan connectivity, access and infrastructure together with the integration design.

Cloud

Managed SaaS

Velion manages the hosted RIV4 environment. Connectivity, endpoint access and account permissions are set up for the specific project.

Dedicated

Single tenant

A dedicated installation can run on premises or in a private cloud. Network access and processing components are defined for the chosen setup.

Explore deployment optionsDiscuss dedicated deployment

Connect your systems. Or build with .

Show us a document, your destination application and the preferred connection method. We can review the workflow and the data your system needs.

Book a demo