Skip to main content

Atlas

How Atlas maps document formats, compiles mappings into converters, and validates document output

The Atlas visual mapping editor for an invoice format's inbound leg, with the format's fields and their sample values on the left, the canonical format's fields on the right, and lines between mapped fields: solid green for approved rows, dashed amber for proposed ones. The Describe a mapping change bar and the Activate version button sit above the editor

Atlas is an intelligent XML mapping engine that converts documents between structured formats, such as XML exported by an ERP or an e-invoicing format. Import the formats you need and map them directly to each other or through Docupath's canonical document format, the Docupath Internal Format (DIF).

Atlas uses AI to propose mapping rows. Review the rows before activating a mapping leg or compiling a project. Atlas transforms documents using a converter compiled from the mappings. Document transformation does not use AI.

Atlas opens from the Docupath platform and is currently available to tenants in the EU region only.


How It Works

Canonical format

Direct mappings between every pair of formats require a separate mapping for each direction. For example, connecting five formats in both directions requires 20 mappings; adding a sixth requires 10 more. With the canonical format, each format uses one inbound and one outbound mapping, so a sixth format adds two mappings. Docupath provides a canonical format for each document type. Canonical formats cannot be edited in Atlas.

Two mapping legs per format

A format's two mappings are its legs: the inbound leg (format to canonical format) and the outbound leg (canonical format to format). Turning format A into format B runs A's inbound leg, then B's outbound leg.

Formats

A format describes one structured layout. Tenant formats are the ones your tenant imports with Import format, from XML samples or an XSD. Docupath maintains global formats, such as Peppol BIS Billing 3.0, and shares them with every tenant. They are read only, and Fork to tenant makes a copy you can change and use in projects.

Generating, reviewing, and activating mappings

A leg is a list of mapping rows. Each row writes one field, usually from one source field, and can change the value on the way, for example by reformatting a date or translating codes with a lookup table.

Atlas generates mapping proposals from the format page or during project setup. Generated rows have the status Proposed. You can approve, edit or reject them in the mapping list or visual editor. For a draft leg, use Describe a mapping change to request changes in natural language.

Activating a leg or compiling a project creates the converter used for document transformations. Before activating a leg, approve or reject every Proposed row and approve any Modified row you want to include. If any row remains Proposed, activation automatically approves all unapproved rows, including Rejected rows.

Projects

A project pairs a source format with a target format and is where you transform documents. On Setup you choose a mapping mode. Via canonical goes through the canonical format and reuses the legs the two formats already have. Direct maps the source straight to the target. XSLT compiles the mappings into the converter, an XSLT stylesheet (XSLT is the standard language for transforming XML), and Transform runs documents through it.

A format's legs are shared by every Via canonical project and every document type in the Docupath platform that uses the format, so activating a new version of a leg, or compiling one of those projects, changes the mapping for all of them. A Direct project compiles its own mapping for that source and target pair and does not change the formats' legs.

The Atlas Projects page with a New project card and three project cards, each showing its status, source format, target format and creation date

Validation on two levels

Atlas checks documents against the validation files attached to a format:

  • XSD validation checks structure. An XSD defines the permitted fields, their order, and which fields are required.

  • Schematron validation checks business rules, such as whether the line amounts add up to the invoice total. A document can pass XSD validation and fail Schematron validation.

Atlas checks the source document against the source format's files before a transform and the output against the target format's files after it, and an error fails the run. The target format's approved validation rules, which you manage on a project's Rules stage, then run on the output.

Output from the Docupath platform

Documents in Docupath are already in the canonical format, so producing another format needs only that format's outbound leg. Under Settings → Destination format & APIs, each document type takes its output from a Template or from Atlas.

Approving, rejecting or validating such a document first produces its output through Atlas and checks it against the format's XSD and Schematron. If the check fails, the action does not go through and the document stays pending.

Opening Atlas

Atlas is enabled per tenant. When enabled, an Atlas entry appears in Settings and in the user menu. Either entry opens Atlas in a new browser tab, signed in with your Docupath session. The menu on the left contains Projects, Formats, Back to Docupath and SHOW TOUR, which replays the page's tour.


Supported Configurations and Options

What you configure

Where

What it covers

Tenant formats

Formats, Tenant

Your own formats, which you can edit, version, disable and remove

Global formats

Formats, Global

Maintained by Docupath and read only. Fork one to use it in a project

Mapping legs

A format's page

Inbound and outbound, reviewed row by row and activated as versions

Projects

Projects

A source format, a target format and a mapping mode, Via canonical or Direct

Validation rules

A project's Rules stage

Your own checks, with the severity ERROR, WARNING or INFO

Document output

Settings → Destination format & APIs in the Docupath platform

Template or Atlas for each document type, and which format. The format needs an active version and an active outbound leg


Other Technical Specifications

Item

Detail

Region

EU only

Document types

Invoice and Purchase Order

Document format

XML. A format can also be imported from a single JSON sample

XML size and nesting

Up to 10 MB and 200 levels of nesting when a document is validated

Transform uploads

Files you preview or transform on a project's Transform stage can be up to 5 MB each

Refused XML

Any XML that contains a DOCTYPE or ENTITY declaration

Where AI is used

Proposing mappings and validation rules, detecting a new project's document type, and plain-language mapping edits. Transforms never use AI


Notes

  • Atlas must be enabled by Docupath for your tenant first. Ask Docupath to enable it.

  • Atlas cannot be switched off while a document type still uses an Atlas destination format. Switch those document types to a template under Settings → Destination format & APIs first.

  • Without a Docupath session, Atlas shows Sign in to continue instead of the app. Sign in to Docupath and open Atlas from Settings again.

  • Incoming documents are not routed through Atlas.

  • A project treats every file you give it as its source format. Atlas does not work out which format a file is.

  • There is no API for sending documents to Atlas from your own systems.

Did this answer your question?