Skip to main content

How to Download Transactions as a CSV-file

This article explains how to download your transaction overview as a csv as well as what a csv file is, how it's used nad how to interpret the data in the csv file.

Updated over 2 weeks ago

How to Download a CSV-file

You can download a CSV file containing transaction data directly from the Overview page.

Step-by-step guide

  1. Go to Overview

  2. Apply the filters you want (for example: group, sender, recipient, status)

  3. Set the time period you want to export

    • By default, Addo Sign shows the last 30 days

  4. Click Download CSV

How Filtering Works Before Downloading

When you download a CSV file, it will always contain the same 35 columns.
These columns cannot be removed or hidden. However, you can control which transactions are included in the file by search using filters in the Overview.

Date period filter

To the left of Download CSV, you can filter by date:

  • The left date sets the start date

  • The right date sets the end date (defaults to today)

Only transactions within this period will be included in the CSV file.

Filtering by specific values

You can filter transactions by entering values in the available filters.
For example:


Filter by Credits to export only transactions with a specific credit cost

Only transactions matching your filters will appear in the Overview and be included in the downloaded CSV.

“My signings”

If multiple users share the same account, you can enable My signings to only export:

  • Transactions you have created or sent yourself

What Is a CSV File?

A CSV file (Comma-Separated Values) is a spreadsheet file where:

  • Each row represents one transaction

  • Each column represents a specific attribute (for example: status, sender, or signing method)

We recommend opening CSV files in Excel, as it makes sorting, filtering, and reading the data much easier.

The Contents of the CSV File

Below is the exact column order and meaning as they appear in the CSV file.

Transaction and recipient details

  1. RecipientId
    Unique ID for this recipient entry in the transaction.

  2. Status
    Status of the recipient’s signing process (for example: Started, Signed, Completed).

  3. SigningReference
    Reference value set by the sender (optional).

  4. RecipientName
    Name of the recipient.

  5. RecipientEmail
    Email address of the recipient.

  6. Receipt
    Indicates whether a receipt was sent to the recipient (Yes / No).

  7. SigningStart
    Date and time when the signing request was sent.

  8. SigningExpires
    Date and time when the signing request expires.

  9. SigningName
    Name of the signing flow.

  10. TemplateUsed
    Name of the template used.

  11. NotificationMethods
    Notification channels used (for example: E-mail, SMS)

  12. SigningMethod
    Method used to sign (for example: Touchscreen, MitID).

  13. AuthenticationMethod
    Authentication method used by the recipient.

  14. DistributionMethods
    How documents or receipts are distributed to recipients of copy.

  15. DistributionType
    Specifies whether recipients of copy receive documents or receipts only.

  16. SignerAuthentication
    Indicates additional signer authentication details.

  17. LatestUpdateDate
    Date of the most recent update to the transaction.

  18. LatestUpdateTime
    Time of the most recent update to the transaction.

  19. PIN
    Personal identification number of the signer.

  20. VATIN
    VAT identification number of the signer.

  21. Sender
    Name of the sender.

  22. SendersEmail
    Email address of the sender.

  23. Group
    Group the sender belongs to.

  24. SigningRecipientsCount
    Number of recipients involved in the signing flow.

  25. SigningId
    Unique ID for the entire signing flow. All recipients in the same flow share the same SigningId.

  26. Credits
    Total number of credits spent on this recipient.

  27. AuthenticationPrice
    Credits spent on authentication.

  28. SigningPrice
    Credits spent on signing.

  29. DistributionPrice
    Credits spent on distribution.

  30. NotificationPrice
    Credits spent on notifications.

  31. FlowPrice
    Credits spent on flow-related actions.

  32. DocumentPrice
    Credits spent on document handling.

  33. SigningState
    Overall state of the signing flow (for example: Started, Completed).

  34. SigningType
    Type of transaction (for example: Signing, Form, Safe file transfer).

  35. IsPublicForm
    Indicates whether the form link is public. Only relevant for forms.

Did this answer your question?