# Submit the business EDD answers

Submits the business' answers to the EDD questionnaire. The submitted data must strictly adhere to the defined schemas and enum values to avoid validation errors. A successful submission updates the edd_data_status to successful and permits the business identification process to proceed. Completing this submission is mandatory to finalize the business identification and proceed with account creation.

Endpoint: PUT /v1/businesses/{business_id}/identifications/{business_identification_id}/edd_data
Version: 1.0

## Path parameters:

  - `business_id` (string, required)
    The unique identifier of the business.
    Example: "a9a25dc10aa74244bd0bb75d1ce6b3b5cbiz"

  - `business_identification_id` (string, required)
    The unique identifier of the business identification.
    Example: "bfc3c8465ef144ff59161dbb307ee311bid"

## Request fields (application/json):

  - `account_purposes` (array, required)
    The purposes for opening the account. Multiple selection is allowed.
    Enum: "RECEIVE_CUSTOMER_PAYMENTS", "DAILY_PURCHASES", "PAY_SALARIES", "MANAGE_EXPENSES", "PAY_SUPPLIERS_INVOICES", "PROCESSING_INTERNATIONAL_BUSINESSES", "CASH_PAYMENTS", "PAYMENT_IN_SHARE_CAPITAL", "ASSET_MANAGEMENT"

  - `incoming_transactions` (object, required)
    The expected sources and volumes of funds the business expects to receive into the account. Used to establish a transaction monitoring baseline for AML purposes.
    Example: {"reasons":["REVENUE_OPERATING_ACTIVITIES","PRIVATE_SAVINGS"],"amount_range":"10K-20K"}

  - `incoming_transactions.reasons` (array, required)
    The expected sources of incoming transactions. Select all categories that represent the funds the business expects to receive into their account. Provide at least one value.
    Enum: "REVENUE_OPERATING_ACTIVITIES", "PRIVATE_SAVINGS", "INVESTOR_FUNDS", "LOANS_AND_FINANCING", "INTRA_GROUP_TRANSFERS_OR_PARENT_COMPANY", "SALE_OF_ASSETS", "RENTAL_AND_LEASE_INCOME", "DIVIDENDS_AND_CAPITAL_GAINS", "SUBSIDIES_DONATIONS_OR_GRANTS", "TAX_REFUNDS"

  - `incoming_transactions.amount_range` (string, required)
    The estimated total annual volume of incoming transactions, expressed as a monetary range. Select the bracket that best reflects the business's expected average annual inflows.
    Enum: "0-1K", "1K-10K", "10K-20K", "20K-50K", "50K-100K", "100K-1M", "1M-50M", "MORE_THAN_50M"

  - `outgoing_transactions` (object, required)
    The expected destinations and volumes of funds the business expects to disburse from the account. Used alongside incoming transaction data to establish a complete transaction monitoring profile for AML purposes.
    Example: {"reasons":["SALARY_PAYMENT","LOAN_PAYMENT"],"amount_range":"10K-20K"}

  - `outgoing_transactions.reasons` (array, required)
    The expected categories of outgoing payments. Select all that apply to the business's expected expenditure patterns. Provide at least one value.
    Enum: "PAYMENTS_TO_SUPPLIERS_OR_SERVICE_PROVIDERS", "SALARY_PAYMENT", "RENT_OR_ADDITIONAL_COST", "TAX_OR_SOCIAL_SECURITY_CONTRIBUTION", "MARKETING_OR_ADVERTISING", "LOAN_PAYMENT", "INVESTMENT_OR_ACQUISITION_OF_FIXED_ASSETS", "TRANSFER_TO_OTHER_GROUP_COMPANIES", "DIVIDENDS_OR_PROFIT_DISTRIBUTION", "PRIVATE_WITHDRAWAL", "CASH_WITHDRAWAL"

  - `outgoing_transactions.amount_range` (string, required)
    The estimated total annual volume of outgoing transactions, expressed as a monetary range. Select the bracket that best reflects the business's expected average outflows.
    Enum: "0-1K", "1K-10K", "10K-20K", "20K-50K", "50K-100K", "100K-1M", "1M-50M", "MORE_THAN_50M"

  - `expected_revenue_next_year` (object, required)
    The projected revenue of the business for the upcoming 12 months.

  - `expected_revenue_next_year.amount_range` (string, required)
    The expected gross revenue bracket for the next year, expressed in Euros.
    Enum: "0-10K", "10K-50K", "50K-100K", "100K-500K", "500K-1M", "1M-5M", "5M-20M", "20M-49M", "MORE_THAN_49M"

  - `expected_revenue_next_year.description` (string)
    A detailed explanation of the projected revenue sources. This field is mandatory if the amount_range is set to MORE_THAN_49M.
    Example: "Expected growth due to new product launch"

  - `last_year_revenue` (object, required)
    Revenue information reported by the business for the previous fiscal year.

  - `last_year_revenue.amount_range` (string, required)
    Revenue bracket for the business's total revenue in the previous fiscal year. Must be one of the pre-defined ranges. If the business revenue exceeds 49M use MORE_THAN_49M and provide the exact figure in the description field.
    Enum: "0-10K", "10K-50K", "50K-100K", "100K-500K", "500K-1M", "1M-5M", "5M-20M", "20M-49M", "MORE_THAN_49M"

  - `last_year_revenue.description` (string)
    Exact revenue figure for the previous fiscal year. This field is mandatory if the amount_range is set to MORE_THAN_49M.
    Example: "Actual revenue details"

  - `employee_count` (string, required)
    The business's current headcount bracket. Use 0-0 for sole traders or self-employed individuals with no additional staff.
    Enum: "0-0", "1-10", "11-50", "51-100", "101-250", "251-500", "MORE_THAN_500"

  - `sales_channels` (object, required)
    The distribution channels through which the business sells its products or services.

  - `sales_channels.channels` (array, required)
    One or more sales channels the business actively uses in its operations. Provide at least one value. If WEBSITES or ONLINE_MARKET_PLACES is included, then website_urls becomes required.
    Enum: "COLD_CALLING", "WEBSITES", "ONLINE_MARKET_PLACES", "RETAIL_STORES", "OTHER"

  - `sales_channels.website_urls` (array)
    The publicly accessible URLs of the business's online sale presence. Required when channels includes 'WEBSITES' or 'ONLINE_MARKET_PLACES'. Each entry must be a valid URI.
    Example: ["https://example-business.com"]

  - `international_payments` (object, required)
    Indicates whether the business conducts payments across international borders, and if yes, provides details about the countries and the parties involved.

  - `international_payments.has_international_payments` (boolean, required)
    Set to true if the business makes or receives payments outside its country of incorporation. When true, the details object becomes required.
    Example: true

  - `international_payments.details` (object)
    A breakdown of the business's international payment activity. Required when has_international_payment is true

  - `international_payments.details.countries` (array, required)
    The countries to which the business makes or from which it receives international payments. Each entry must be a valid ISO 3166-1 alpha-2 country code (e.g., NL, DE, FR)
    Example: ["NL","DE","FR"]

  - `international_payments.details.service_type` (array, required)
    The categories of counterparties involved in the business's international payment flows. At least one value must be provided.
    Enum: "SUPPLIERS", "END_CUSTOMERS", "BUSINESS_PARTNERS", "EMPLOYEES", "SHAREHOLDERS"

  - `acting_in_own_name` (boolean, required)
    Indicates whether the business is acting on its own behalf (true) or as an agent, intermediary, or representative of a third party (false). This is used to assess the business's principal status for AML purposes.

  - `is_pep` (boolean, required)
    Indicates whether the business owner or any beneficial owner is classified as Politically Exposed Person (PEP) under applicable AML regulations. Set to true if any such association exists.

  - `cash_transactions` (object, required)
    Describes the business's involvement in cash-based payment activity, including whether cash transactions occur and the operational context in which they take place.

  - `cash_transactions.has_cash_transactions` (boolean, required)
    Set to true if the business handles cash as part of its operations. When true, the details object becomes required.
    Example: true

  - `cash_transactions.details` (string)
    A free-text description of how and why the business handles cash. Required when has_cash_transactions is true. Should describe the operational context, such as the nature of the cash activity and the business location where it occurs.
    Example: "We accept cash payments at our retail location"

## Response 200 fields (application/json):

  - `id` (string, required)
    Unique identifier for the business EDD data record.
    Example: "edd_12345678-abcd-1234-abcd-123456789012"

  - `status` (string, required)
    Status of the submitted EDD data.
    Enum: "successful", "pending"

## Response 400 fields (application/json):

  - `title` (string)
    A short, human-readable summary of the problem type.
    Example: "Validation Error"

  - `status` (string)
    The HTTP status code applicable to this problem.
    Example: "400"

  - `id` (string)
    A unique identifier for this specific occurrence of the problem.
    Example: "a95f2aaf-4e0c-4d49-8021-8a16a884ed86"

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "The request payload contains invalid data."

  - `code` (string)
    An application-specific error code.
    Example: "validation_error"

  - `details` (array)
    An optional array containing specific field validation errors. Used primarily for POST/PUT requests.

  - `details.field` (string)
    The specific field in the payload that failed validation.
    Example: "sales_channels.website_urls"

  - `details.message` (string)
    The reason the field failed validation.
    Example: "Website URLs is required when channels includes 'WEBSITES' or 'ONLINE_MARKET_PLACES'"

## Response 401 fields (application/json):

  - `title` (string)
    A short, human-readable summary of the problem type.
    Example: "Unauthorized"

  - `status` (string)
    The HTTP status code applicable to this problem.
    Example: "401"

  - `id` (string)
    A unique identifier for this specific occurrence of the problem.
    Example: "b82b1cde-7d3a-4f5b-9a12-8b17b884ec99"

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "Missing or invalid authentication token."

  - `code` (string)
    An application-specific error code.
    Example: "unauthorized_access"

## Response 403 fields (application/json):

  - `title` (string)
    A short, human-readable summary of the problem type.
    Example: "Forbidden Action"

  - `status` (string)
    The HTTP status code applicable to this problem.
    Example: "403"

  - `id` (string)
    A unique identifier for this specific occurrence of the problem.
    Example: "c93f2aaf-4e0c-4d49-8021-8a16a884ed11"

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "You do not have sufficient permissions to perform this action."

  - `code` (string)
    An application-specific error code.
    Example: "insufficient_permissions"

## Response 404 fields (application/json):

  - `title` (string)
    A short, human-readable summary of the problem type.
    Example: "Resource Not Found"

  - `status` (string)
    The HTTP status code applicable to this problem.
    Example: "404"

  - `id` (string)
    A unique identifier for this specific occurrence of the problem.
    Example: "d12f2aaf-4e0c-4d49-8021-8a16a884ed22"

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "The requested business identification could not be found."

  - `code` (string)
    An application-specific error code.
    Example: "resource_not_found"

## Response 422 fields (application/json):

  - `title` (string)
    A short, human-readable summary of the problem type.
    Example: "Unprocessable Entity"

  - `status` (string)
    The HTTP status code applicable to this problem.
    Example: "422"

  - `id` (string)
    A unique identifier for this specific occurrence of the problem.
    Example: "e55f2aaf-4e0c-4d49-8021-8a16a884ed33"

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "Business identification is not in a state that allows EDD data submission."

  - `code` (string)
    An application-specific error code.
    Example: "invalid_business_state"

## Response 500 fields (application/json):

  - `title` (string)
    A short, human-readable summary of the problem type.
    Example: "Internal Server Error"

  - `status` (string)
    The HTTP status code applicable to this problem.
    Example: "500"

  - `id` (string)
    A unique identifier for this specific occurrence of the problem.
    Example: "f66f2aaf-4e0c-4d49-8021-8a16a884ed44"

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "An unexpected internal error occurred."

  - `code` (string)
    An application-specific error code.
    Example: "internal_server_error"