User-defined custom columns in export settings
Use custom columns when the default export fields are not enough for your accounting workflow. This feature lets you add your own export fields for supported export formats, choose where each field is used (line, document, or both), and define whether values are free text or selected from a list.
Before you start
This feature appears only for export formats that support custom columns.
Supported formats are: Uniconta, Apskaita5, Euroskaita, Excel, CSV, XML, Json, and Pagaute Nav.
Open Default export format in settings and choose the export format first.
How to create a custom column
In Default export format, choose a supported export format.
In the custom fields table, click the + button.
Enter Name (required).
Enter Key (required). Spaces are removed automatically, unsupported symbols are removed, and the key must be unique within that export format.
Choose Where?: Line, Document, or Line and document.
Optional: click Show more fields and enable Free text if users should type values directly on documents.
Optional: in Additional fields, add extra attributes (name + key) and optional values for each attribute.
Click Confirm.
How to edit or remove a custom column
Find the column in the custom fields table.
Click the pencil icon to edit, or the trash icon to remove.
When editing, update the needed fields and click Confirm.
How the interface behaves after creation
Key display: the table shows the key without the
custom_prefix.Exported key format: when the document is exported, the key is always exported with the
custom_prefix.Line vs document: line fields are filled on invoice lines; document fields are filled on the document level; fields with Line and document can be used in both contexts.
Free text: users can type values directly in document/export tables.
Not free text: users choose values from the code list for that field and can add new values when editing documents.
Additional fields: these are shown when creating/editing code values for that custom column. If optional values are defined, users select from that list; if not, users can enter any text.
Common issues
"Field key is required": Enter a key in the Key field.
"Field with this key already exists for the exporter": Use a different key. The key must be unique for the selected export format.
Cannot edit key in edit mode: This is expected behavior. To use a different key, create a new custom column.
Additional field key must be unique: Each additional field key must be different within the same custom column.
Column not visible in settings: The currently selected export format does not support custom columns.