Skip to content
part of the groupApertiaDraivix

01Finance and accounting · module

EDI document exchange with partners

Maps and converts business documents in JSON, CSV and XML with full exchange tracking

Core available, part in progressBook a consultation
  • EDI provider profile
  • EDI partner
  • EDI document mapping
  • EDI exchange document
10
capabilities
4
record types
0
automations
1
integration and AI tool

02What the module does

Less routine. More value.

The EdiIntegration module tracks electronic document exchange with trading partners: partners, provider profiles, document mappings and records of every exchange with confirmation. Your company can convert documents into JSON, CSV or XML files to match partner requirements and load incoming files for preview.

  • EDI partners in one placeManage your EDI trading partners for electronic document exchange in Draivix. Each partner has its own record, keeping all exchanges with them together in one place.
  • Profile with a verified schemaImport a reviewed provider profile with a schema hash so you always know which schema version you are working with.
  • Mapping for each directionCreate separate document mappings for export and import so rules for outbound and inbound documents never get mixed up.
  • New formats without codingAdding a new layout in JSON, CSV, or XML requires no coding, letting you adapt to partner requirements through configuration.
  • See what is missing before going liveReadiness checks across the partner, profile, and mapping show what is still missing, giving you a clear checklist before launch.
  • Incomplete setup cannot go liveA placeholder endpoint or unreviewed schema blocks live execution, preventing incomplete configurations from reaching production.
  • Every export has a recordConvert a record into a file and save an exchange record on live runs. Every exchange is documented, while the file is handed over to the partner manually or outside Draivix.
  • Preview inbound files firstImport an inbound file into a preview and save an exchange record on live runs, so you can inspect the contents before processing them further.
  • Acknowledgements with hash verificationAn acknowledgement from a partner or provider is logged against the exchange and the system verifies file hashes, confirming it matches the exact file.
  • Dry run before every operationEvery live operation starts with a dry run so you can review the output and fix errors without affecting production data.

What is currently in progress

  • The module does not transfer files on its own; there is no built-in AS2, SFTP, or API client. Transfers take place manually or externally.
  • Conversion is verified for JSON, CSV, and XML. EDIFACT and X12 formats are not verified in this version.
  • An import saves an exchange record. Creating a business document from it is not verified.
  • Users with a finance role can edit the status and timestamps of an exchange record directly, bypassing control services.

03How it works

How it works step by step.

  1. Partners, profiles and mappings

    For each partner, you create a record and import a verified provider profile with its endpoint, schema and schema hash. Then you set up a document mapping for export or import. Adding a new layout in JSON, CSV or XML requires no programming.

    Read in detail

    A profile covers invoices, purchase orders, delivery notes, receipt confirmations, product catalogs and remittance advices. A readiness check shows what is still missing; placeholder endpoints and unverified schemas block live runs.

  2. Export and import

    An export converts the source record into a file based on the mapping, and a live run saves an exchange record with the status exported. An import reads an incoming file and converts it into a preview based on the mapping; a live run saves an exchange record with the status received, mapped or imported. Operations are triggered by the system administrator via command and run as a dry run first.

  3. Exchange confirmation

    An acknowledgement from a partner or provider is recorded on the exchange record. The system verifies file hashes and updates delivery and retry details. File transfer to the partner takes place manually or outside Draivix, and a transfer receipt is recorded in the system. This module never modifies the general ledger directly.

04What runs automatically

Connected to the outside world.

External integrations

  • Files exchanged with partners and providersYou exchange files with trading partners and EDI providers manually or outside the system. Draivix keeps the exchange record, acknowledgement, and proof of transfer.

05Frequently asked questions

Does Draivix send EDI messages to partners automatically?

No. It prepares the file and logs the exchange. The transfer takes place manually or through an external provider, and its acknowledgement is recorded in the system.

Which file formats does the module support?

JSON, CSV, and XML. EDIFACT and X12 formats are not verified in this version.

Do I need a developer to onboard a new partner?

Not for a new layout in JSON, CSV, or XML. All you need is a partner, a reviewed profile, and a document mapping.

Does importing an inbound file create a business document?

The import saves an exchange record with a data preview. Creating a business document from it is not verified in this version.

Which document types can be exchanged with partners?

The provider profile covers invoices, orders, delivery notes, receipt confirmations, product catalogs, and remittance advices. A separate mapping is created for each document type and direction.

06Related modules

Modules that work great together.

All modules in Finance and accounting

Let’s start together

Tell us how your business works.

We will show you what a system that takes over part of that work could look like.

Book a consultation