The export is based on the transactions shown in Overview at the time you export. This means that selected filters, date ranges, bookmarked views, and the current transaction list affect what is included in the export.
Before you start
Before you export transaction data, check that Overview shows the transactions you want to include. To do this, you can use:
Date range to select the period you want to export
Column filters to narrow down the transaction list
Sorting to organise the transaction list
Bookmarked views to return to saved filters and layouts
Show/hide columns to choose which columns are visible in Overview
Reset view to return Overview to its default layout
Some fields in the export may be empty if the information was not used, added or registered on the transaction.
Note: The export follows the current transaction list in Overview. If a filter, date range, or bookmarked view is active, the export only includes transactions that match the current view.
Export transaction data
Go to the Overview tab
Select the date range you want to export
Apply any filters you want to use
Check that the transaction list shows the transactions you want to export
Click Export:
Select the export format you want to use, for example Excel or CSV, if format options are available
Open the file in Excel or another spreadsheet tool
Use Export in Overview to export the current filtered transaction list.
Use filters before exporting
You can use filters to control which transactions are included in the export. For example, you can filter by:
Status
Recipient
Send date
Signing Id
Transaction Id
Sender
Sender’s e-mail
Updated
Reference number
Filters are applied directly in the relevant columns in Overview.
Use column filters by clicking the funnel icons next to each filter, and narrow down the transaction list before exporting.
Use bookmarked views before exporting
A bookmarked view can contain saved filters, sorting, date ranges, visible columns, column order, and column width. Use bookmarked views if you often export the same type of transaction data. For example, you can create bookmarked views for:
Failed transactions
Started transactions
Transactions from a specific sender
Transactions in a specific group
Transactions with a specific reference number
Transactions that require follow-up
Before exporting, check that the correct bookmarked view is selected.
Use bookmarked views when you often need to export the same filtered transaction list.
Reset the view before exporting
If the export does not include the transactions you expected, click Reset view and check the transaction list again. Use Reset view when:
You are unsure which filters are active
A bookmarked view may be limiting the list
Some transactions are hidden by filters or layout changes
You want to return Overview to the default layout before exporting
After resetting the view, apply the date range and filters you want to use, then export again.
Use Reset view if filters, bookmarks, or layout changes are hiding transactions from the export.
Show or hide columns before exporting
Use Show/hide columns to choose which columns are visible in Overview. This can help you review the transaction list before exporting, especially if you need to check fields such as:
Signing Id
Transaction Id
Reference number
Sender
Status
Updated
Note: The available export data may include fields that are not currently visible in Overview. Use Show/hide columns mainly to review and identify the transaction list before exporting.
Use Show/hide columns to review the fields you need before exporting transaction data.
What is a CSV file?
A CSV file is a spreadsheet file where each row represents a transaction or recipient entry, and each column represents a specific data field.
You can open the file in Excel or another spreadsheet tool to sort, filter, and review the exported data.
The contents of the CSV file
The CSV file includes the fields listed below.
The field names are exported exactly as shown. Field names should stay the same in both English and Danish articles, because they match the column headers in the CSV file.
Transaction and recipient details
Field name | Description |
RecipientId | The unique ID for the recipient in the transaction. |
Status | The status of the transaction or recipient at the time of export. |
SigningReference | The reference connected to the signing, if a reference was added. |
RecipientName | The name of the recipient. |
RecipientEmail | The recipient’s e-mail address. |
Receipt | The receipt setting used for the recipient, if applicable. |
SigningStart | The date and time when the signing started. |
SigningExpires | The date and time when the signing expires. |
SigningName | The name of the signing. |
TemplateUsed | The template used for the transaction, if a template was used. |
NotificationMethods | The notification method or methods used for the recipient. |
SigningMethod | The signing method used for the recipient. |
AuthenticationMethod | The authentication method used for the recipient. |
DistributionMethods | The distribution method(s) used for the documents. |
DistributionType | The type of distribution used for the transaction. |
LatestUpdateDate | The date of the latest recorded update. |
LatestUpdateTime | The time of the latest recorded update. |
PIN | The PIN (Personal Identification Number) value registered for the transaction, if present. |
VATIN | The VAT (Value Added Tax) identification number registered for the transaction, if present. |
Sender | The name of the sender. |
SendersEmail | The e-mail address of the sender. |
Group | The group connected to the transaction. |
SigningRecipientsCount | The number of recipients connected to the signing. |
SigningId | The unique ID for the signing. |
Credits | The total number of credits used for the transaction. |
AuthenticationPrice | The price or credit usage for authentication. |
SigningPrice | The price or credit usage for signing. |
DistributionPrice | The price or credit usage for distribution. |
NotificationPrice | The price or credit usage for notifications. |
FlowPrice | The price or credit usage for the signing flow. |
DocumentPrice | The price or credit usage for documents. |
SigningState | The current state of the signing. |
SigningType | The type of signing. |
IsPublicForm | Shows whether the transaction was created from a public form. |
If a field is empty
A field can be empty if the information was not used, added or registered on the transaction. For example, a transaction may not have a value in TemplateUsed if no template was used, or in VATIN if no VAT identification number was registered.
Empty fields do not necessarily mean that something is wrong with the transaction.
Use the export for review
You can use the exported file to review transaction data outside Addo Sign. For example, you can:
Filter transactions by Status
Search for a specific RecipientName or RecipientEmail
Find a transaction by SigningId
Review which TemplateUsed was used
Compare credit usage across Credits and price fields
Analyse transactions by sender, group, date range, or reference number
If the export does not contain the expected transactions
If the exported file does not contain the transactions you expected, check the transaction list in Overview before exporting again.
Check whether:
The correct date range is selected
A bookmarked view is active
Column filters are hiding transactions
Reset view changes the transaction list
The transactions belong to another sender, group, or account
You have access to the transactions you expect to export
The transaction list in Overview matches what you expect before clicking Export
Before contacting support
To help Addo Sign Support assist you as quickly and effectively as possible, check the following before contacting support:
Whether you selected the correct date range in Overview
Whether a bookmarked view was active when you exported the file
Whether column filters were applied before exporting
Whether you clicked Reset view and tried again
Whether the transaction list in Overview showed the expected transactions before export
Whether the field is empty because the feature was not used on the transaction
Whether you can identify the transaction using SigningId
Whether the transaction status in Addo Sign matches the value in Status
If you still need help, include:
SigningId (if known)
RecipientId (if known)
Status
RecipientName
RecipientEmail
The export format you used
Screenshot of the transaction list in Overview
Screenshot of the relevant row in the exported file
Description of the field or value you expected to see