WORKS WITH YOUR EXISTING SYSTEMS

Works with your existing systems

RIVQAN does not ask you to replace your accounting system. We read data the way your system allows, and return the results to you for review and approval.

DATA EXCHANGE METHODS

Data-exchange methods

No integration is shown as working unless it is built and tested.

In development Built and tested on test data

Built and running internally on test data; not commercially available yet.

In development

Excel & CSV files

Import journals, balances and transactions exported from any accounting system, with completeness, duplicate and balance checks. Built and tested on test data.

In development

Payment-gateway settlement files

Reading the settlement file to match receipts, fees and bank payouts. A direct connection to the gateway API is not built.

In development

E-invoice preparation & validation

Preparing and validating e-invoice documents. Signing and submission are planned.

Planned Planned

Not built yet; implemented per client case, and tested first.

Planned

API connection

Automated data exchange with your system through a secure API with defined permissions.

Planned

Read-only database connection

Reading data directly from your system's database with read-only access, never writing to it.

Planned

Bank APIs

Receiving bank statements automatically instead of uploading files.

Planned

Connectors for specific ERP systems

There is no live integration today with any named commercial ERP (such as SAP, Oracle, Odoo or Microsoft Dynamics). A connector is built for the client's system and tested first.

HOW IT WORKS

How the exchange works

01

We receive the data

A file, or a connection your system supports.

02

We validate it

Completeness, duplicates, balance, period and currency. Missing data is flagged as insufficient.

03

Agents do the work

Reconciliations, analysis and proposed entries under the approved rules.

04

You approve

Results and proposed entries reach you for review and approval before any use.

PRINCIPLES

Principles we keep

Your system stays the source of truth

Entries RIVQAN proposes are not posted entries in your system; posting is your decision, in your system.

Read-only by default

We read data with the least access needed and do not write to your system.

A trail for every file and figure

We keep the source file, the conversion log and the last-update date, and never resolve source, currency or period differences by guesswork.

Human approval

Nothing sensitive is approved without an authorised person, with segregation of duties.

LET'S BUILD

Tell us about your current system

We review the right data-exchange method for your system, and tell you what is available today and what is planned.