Advosys

Advosys integration lets users send documents from Epona365 Web straight to the Advosys financial system, matched to the document's matter via the Epona matter code (Epona matter code = Advosys matterId). Two independent context-menu actions ship behind separate feature flags:

• Send to financial system (advosys-finance) — uploads the document as a financial document in Advosys.
• Attach to EAN invoice (advosys-ean-invoice) — attaches the document to the matter's open Advosys invoice draft.

The two features share the same Advosys connection but are licensed and toggled independently — enabling one does not enable the other.

Requirements

• The document belongs to a matter whose matter code maps to an Advosys company.
• The relevant feature flag is enabled for the organization — see Configuration.
• The Advosys connection (API URL, subscription key, tenant id) is configured — see Configuration.
• For Attach to EAN invoice, exactly one open invoice draft must exist for the matter in Advosys.
• Attach to EAN invoice additionally requires the Advosys installation to be version 5.22 or later, with the "Advosys API Partner access" module enabled.

Usage

Send to financial system

1. Right-click one or more documents in the document list.
2. Select Send to financial system.
3. A progress dialog is shown during upload.
4. On success, a toast confirms completion. On failure, a blocking popup shows Advosys' own error reason — click OK to dismiss.

Notes:

• The action is greyed out when the document isn't linked to a matter, or the matter has no Advosys company mapping.
• Advosys converts the uploaded file to PDF automatically (PDF, DOCX and XLSX are all supported as source files).
• The financialDocumentId Advosys returns is not stored by Epona365.
• Documents over 350 MB are rejected up front with a clear error, before anything is sent to Advosys.

Attach to EAN invoice

1. Right-click a document.
2. Select Attach to EAN invoice.
3. A progress dialog is shown during upload.
4. On success, a toast confirms completion. On failure, a blocking popup shows Advosys' own error reason — click OK to dismiss.

Notes:

• The action is greyed out when the matter has no company mapping, or no invoice draft exists for it.
• If multiple open invoice drafts exist for the matter, the action stays enabled but refuses on click, telling the user to fix this in Advosys — only one draft should be active per matter at a time.
• There is no client-side file-type check. Unsupported file types are rejected by Advosys itself and surfaced through the same error popup as any other Advosys error.
• Documents over 350 MB are rejected up front with a clear error, before anything is sent to Advosys.

Configuration

1. Within DMSConfigurationCenter

The Advosys API URL and REST API tenant id are configured the same way as the existing Advosys/Time Registration settings — see DMSConfigurationCenter — Advosys. Both new features reuse this connection; no separate connection setup is needed per feature.

2. Epona365 portal — Organization Settings

1. Open the Epona365 portal and navigate to Organization → Settings.
2. Enable Send to financial system and/or Attach to EAN invoice as needed — these are independent toggles.
3. Select the DMS configuration the connection belongs to, and enter the subscription key provided by Advosys support.

The subscription key is stored in Key Vault and the field is write-only — there is no way to read back the stored value through the portal. To rotate it, enter the new value and save again.

Note: Advosys' documented file-type support for the EAN invoice attachment is Txt, PDF, Word, RTF, HTML, Excel, GIF, JPEG, PNG and TIF.