When a reviewer approves a document, Docupath generates outbound XML and sends it through the configured delivery integrations. By default, a data export template generates the XML to be delivered. However, under Settings → Destination format & APIs, you can select a tenant or global Atlas format for each document type. Global formats are maintained by Docupath and include formats such as Peppol BIS Billing 3.0.
Docupath sends Atlas the document's data in its canonical document format, the Docupath Internal Format (DIF). Atlas converts the data using the selected format's outbound leg and validates the output against any XSD and Schematron attached to that format. XSD checks the document structure; Schematron checks business rules. A validation failure blocks delivery.
Prerequisites
Atlas enabled for your tenant by Docupath. When enabled, an Atlas entry appears in Settings and in the user menu, and Destination format & APIs shows one row per document type instead of a single format list. Atlas is available to tenants in the EU region only.
An Atlas format of the document type, with an active version and an active outbound leg.
Read access to Destination format & APIs to open the page, and write access to change it.
Steps
Choose Atlas for a document type
Open Settings → Destination format & APIs.
Under Outbound destination format, find the document type's row. The table lists each document type enabled for your tenant, 10 per page, with the columns Document type, Source and Format.
In Source, select Atlas. Docupath immediately saves the selection with the first compatible Atlas format, with global formats listed first. The toast Destination format selections updated appears.
Note: Changing Source or Format requires write access to Destination format & APIs. Without it, both are disabled with the tooltip You do not have the required permissions to do this action.
To use another format, open Format and choose one under Global Formats or Tenant specific. The list includes formats of that document type with an active version. The selection is saved automatically.
To go back, select Template. The row switches to your tenant's active template if it covers the document type, otherwise to the first template that does, and saves. If no template covers the document type, the row stays on Atlas.
Check the output on a document
Open a pending document of that type and select the Destination tab. Docupath asks Atlas for the output each time the tab loads, so the viewer, titled destination.xml, shows what approving would deliver.
If the output failed validation, read the panel above the XML. It is headed Document cannot be delivered! and groups the findings under an Error heading and a Warning heading, each with a count (the headings turn plural when there is more than one).
A business rule finding is headed by its rule id, such as BR-03.
A structural finding is headed by the element's name and, when the error is one of four kinds, a title: Missing required element, Invalid value, Unexpected element or Element not allowed. For example, the heading InvoiceTypeCode · Unexpected element comes with the message Expected one of: IssueDate.
When Atlas refused the output without findings, the panel reads This document could not be validated, so it cannot be delivered.
Correct the captured data, save it with Save Changes, and open Destination again until the panel is gone. If the failing element comes from the format's outbound leg rather than the document's data, fix the leg in Atlas, or switch the document type back to Template.
Click Approve, Reject or Validate. Each of the three saves your edits first, then gets the output from Atlas. If Atlas refuses the output or cannot be reached, the action fails and the document stays pending.
Expected Outcome
At each decision, Docupath stores the Atlas output with the document. After an approval, your delivery integrations send that stored XML. After a rejection, Docupath sends the rejection email. After approval or rejection, the Destination tab shows the stored output, without calling Atlas again and without a validation panel.
Common Issues
Issue | Cause | Resolution |
Approve, Reject or Validate opens a Validations failed dialog with no details, and the document stays pending | All three render the Atlas output first. The output failed the target format's validation, or Atlas refused the request for another reason | Open the Destination tab, where the validation panel lists the findings. Fix the data, or switch the document type to a template under Destination format & APIs. If the tab shows an empty viewer, see the last row |
A message says Document could not be delivered because the Atlas transformation service is unavailable. | Atlas could not be reached, or the chosen format has no active outbound leg | Try again. If it keeps happening, check in Atlas that the format's outbound leg has an active version, or choose another format |
A rejection rule, a duplicate check or Auto Review left a document pending | Automatic rejections and Auto Review approvals are skipped when the Atlas render fails, and nothing tells the reviewer why | Check the document's Destination tab, correct the data, and approve or reject it yourself |
Atlas is disabled in Source, with the tooltip No formats available for this document type in Atlas | No Atlas format of that document type has an active version, or the list has not finished loading | Wait for the page to finish loading. If the tooltip stays, activate a version of a format of that document type in Atlas |
Format shows Unavailable format followed by the start of an id | The format saved for this row is no longer among the Atlas formats with an active version for this document type | Choose another format, or switch the row to Template |
The Destination tab shows an empty viewer and no message | Docupath could not get the output from Atlas | Reload the tab, and check that the format has an active outbound leg in Atlas |
Notes
Each document type has one source at a time, a template or an Atlas format. A document type with no saved choice uses your tenant's active template.
A row that uses a global format picks up Docupath's updates from the next render. A forked copy does not.
Through the Docupath API, an approved document returns the stored Atlas output, and a pending or validated one returns the placeholder
<!-- delivered via Atlas -->instead of XML.Warnings reach the panel only when the output was refused. When the output passes, Docupath receives only the XML, and the panel stays hidden.
The panel lists at most 50 findings.
Empty critical fields and failed custom validations block only Approve and Validate. A failed Atlas render also blocks Reject, because every decision renders the output first.
The Docupath platform has no download for the Atlas output. The Destination tab offers COPY, and Download in the document list returns the original uploaded file.
Atlas cannot be switched off while any document type uses an Atlas format. The message lists those document types by id. Switch them to Template first.