Set up your account

Create the account hierarchy that represents your business structure organized around tax IDs.

Setup sequence:

Create an organization and assign products.
Add companies (one per tax ID).
Add branches (optional - only if needed)
Add users and assign user roles to them.

Account structure

Organizations contains one or more companies, each mapped to a tax ID. Companies use products to process documents.

Organization → Company → Product


Account element	Required	Description
Organizations	Yes	Top-level account entity. Holds product subscriptions and contains companies. One contracting entity typically has one organization.
Company	Yes	Represents a legal entity with tax registration. Each company corresponds to one tax ID.
Product	Yes	Electronic invoicing solution for a specific country and operation. Examples: pl_Faktura__2.0, pl_Faktura_Polling_2.0.
Branch	No	Sub-division within a company when multiple physical locations share the same tax ID.

Account structure

The following table describes each element in the account structure hierarchy and whether it's required to set up Compliance Network.

Account elements


Account element	Required	Description
Organization	Yes	Holds product subscriptions and contains companies. It's the top-level account entity. One contracting entity typically has one organization .
Company	Yes	Represents a legal entity with tax registration. Each company corresponds to one Tax Registration Number (TRN) or tax ID.
Product	Yes	E-invoicing product ID names follow a three-part pattern: `[country-code]_[product-name]_[version]`, for example: `fr_invoice_inbound_1.0`. Represents the electronic invoicing solution for a specific country and operation.
Branch	No	Represents an optional sub-division within a company when multiple physical locations share the same tax ID.

Understand e-invoicing product IDs

The following table describes each part of a product ID name.


Product ID part	Description	Examples
country-code	A two-letter lowercase ISO country code.	`fr` (for France), `hr` (for Croatia), or `pl` (for Poland).
product-name	The document type and direction, with words separated by underscores. Some product names use lowercase (invoice_inbound), while others use title case (UBLInvoice).	`invoice_inbound` or `UBLInvoice_Polling`.
version	The major.minor version number.	`1.0`, `2.0`.

Product ID format exceptions

Belgium uses an uppercase country code: BE.
France and Poland e-invoicing products have a double underscore before the version number: fr_Report__1.0 and pl_Faktura__2.0.

Create an organization

Create an organization to group your companies and manage product subscriptions from a single account.

An organization is the top level of your account. It holds your companies, controls which products are available to them, and sets the default configuration that companies inherit unless you override it.

You can add a company to your organization using the Compliance Network web UI (for manual setup) or using Indirect Tax API (for automated workflows).

Important:

Only workspace administrators can create organizations.

Set up in Compliance Network

You must have workspace administrator permissions to create an organization.

Click the Settings icon.
Go to Organization on the navigation menu.
Click Create organization.
Enter the organization name and a brief description.
Click Save.

Set up using API

You need workspace administrator permissions to create an organization.

Send a POST request to /v2/configurations/organizations.
In the request body, include the name field with your organization name.
Request body:
```
{
  "name": "{organization-name}"
}
```
Important:
name is a required field. It can't be empty. No character limit.
Confirm the response returns a 200 status and an organization ID.
Response body:
```
{
  "id": "{organization-id}",
  "name": "{organization-name}",
  "createdAt": "{timestamp}",
  "createdBy": "{user-email}",
  "isDeleted": false
}
```
Important:
If you get a 400 or 409 HTTP status code, make sure you have entered a unique organization name.
Save the id value from the response. You need this for all subsequent API calls.

Assign products to an organization

Assign products to your organization to define which countries and operations are available for document processing.

Products define which countries and operations (inbound or outbound) are available to your organization.

Set up in Compliance Network

Click the Settings icon.
Go to Organizations on the navigation menu.
Click the organization name under the Name column.
Go to Products.
Click Add product.
Under Search products, search and select one or more products from the list.
Click Confirm.

Set up using API

Use the API to assign products to your organization and define which inbound and outbound operations are available.

You need workspace administrator permissions to create an organization.

Assign products at organization level to reduce administrative overhead. Companies inherit all products by default. If you need a subset of products for specific companies, you can override this with an API call per company.

Send a PUT request to /v2/configurations/organizations/{organizationId}/products.
In the request body, include the productId and set the allowedProcessTypes values for inbound and outbound processing.
Request body:
```
{
  "productId": "{product-id}",
  "allowedProcessTypes": {
    "inbound": false,
    "outbound": true
  }
}
```
Confirm the response returns a 200 status and a product ID.

Add companies to your organization

Add a company to your organization via Compliance Network web UI and Indirect Tax API.

Companies represent legal entities with tax registrations. Each company corresponds to one tax ID. Companies allow:

Granular configuration per tax ID.
Restricted user access per specific tax IDs.
Organized transactional data by legal entity.

You can add a company to your organization using the Compliance Network web UI (for manual setup) or using Indirect Tax API (for automated workflows)

Set up using Compliance Network

Click the Settings icon.
Go to Organizations on the navigation menu.
Select an organization's name under the Name column.
Go to Companies.
Select New company.
Enter the company details and company address, then Save.

Set up using API

Use the API to add a company to your organization by providing its tax registration details and assigned products.

Send a POST request to /v2/configurations/organizations/{organizationId}/companies.

In the request body, include the following required fields for your company:

Request body:


                    
                {
  "taxId": "{tax-id}",
  "legalName": "{legal-entity-name}",
  "dba": "{business-name}",
  "products": [
    {
      "productId": "{product-id}",
      "allowedProcessTypes": {
        "inbound": false,
        "outbound": true
      }
    }
  ]
}

Check the complete list of parameters:


Parameter	Type	Required	Description
`taxId`	string	Yes	Tax registration number of your company's tax ID. Validates for country-specific format
`legalName`	string	Yes	Official legal entity name. It can't be empty
`dba`	string	Yes	"Doing Business As" registered name. It can't be empty
`products`	array of strings	Yes	Array of products with process types
`country`	string	No	Country code (ISO 3166-1 alpha-2, for example: "FR", "PL")

Note:

If the products list is left empty, the created company will acquire all the products assigned to the organization.

Confirm the response returns a 200 status.

Response body:


                {
  "id": "{company-id}",
  "taxId": "{tax-id}",
  "legalName": "{legal-entity-name}",
  "dba": "{business-name}",
  "country": "{country-code}",
  "products": [...],
  "createdAt": "{timestamp}",
  "isDeleted": false
}

Save the id (company ID) for future API calls.

After successfully adding a company, the Indirect Tax API returns a JSON object containing the company details and their assigned company ID.

Note:

Always save the company ID value from the response when creating a company. You will need the company ID value in future API calls. To find it, look for the ID value in the samples.

Edit a company

Edit a company to keep the information of your company up to date.

You can edit the following information of your company: legal name, DBA, and country after creation. You can't change the tax ID. If you need to update the tax ID of a company, you need to create a new company.

You can edit a company using the Compliance Network web UI (for manual setup) or using Indirect Tax API (for automated workflows).

Set up using Compliance Network

Click the Settings icon.
Go to Companies on the navigation menu.
Click the Settings icon from a company:
Select Edit Company.
After editing, click Save.

Set up using API

Use the API to update a company's legal name, DBA, and country.

Send a PATCH request to /v2/configurations/organizations/{organizationId}/companies/{companyId}.

In the request body, include the fields you want to update.


Editable parameters	Type	Required	Description
`legalName`	string	Yes	Official legal entity name
`dba`	string	Yes	"Doing Business As" registered name
`country`	string	No	Country code (ISO 3166-1 alpha-2, for example: "FR", "PL")

CAUTION:

You can't change the tax ID. If you need to update the tax ID of a company, you need to create a new company.

Confirm the response returns a 200 status and the following response data structure with your updates:

Response body:


                {
  "id": "{company-id}",
  "taxId": "{tax-id}",
  "legalName": "{legal-entity-name}",
  "dba": "{business-name}",
  "country": "{country-code}",
  "products": [...],
  "updatedAt": "{timestamp}",
  "isDeleted": false
}

Add branches

Add branches to manage multiple physical locations of your company that share the same tax ID as separate, independently configured entities.

Adding branches is an optional step in your setup account process. Branches represent multiple company physical locations or business sub-divisions sharing the same tax ID but needing independent configurations or document numbering. A branch in Sovos has the following capabilities:

Independent document numbering sequences
Branch-specific configurations (rendering, distribution, credentials)
Separate audit trails per branch

Important:

Branches add management complexity. Only add a branch when each location needs its own configuration.

Use cases

When to use branches

Your company has the same tax ID but different physical locations (retail stores, bank branches, regional offices).
Each location needs independent document numbering or separate configurations.

When not to use branches

Each company location has different tax IDs. Create separate companies instead.
Single location per tax ID. Branches not needed.

Set up using Compliance Network

Placeholder

Set up using API

Use the API to add a branch to your company.

Send a POST request to /v2/configurations/organizations/{organizationId}/companies/{companyId}/branches.

In the request body, include the required and optional fields for your branch.

Sample request data:

{
  "branch": "{branch-identifier}",
  "description": "{branch-description}"
}


Parameters	Required	Type	Description
`branch`	Yes	string	Branch identifier. Must be unique within the parent company. It can't be empty
`description`	No	string	Free-text description
`metadata`	No	object	Flexible JSON object for country-specific data

Request parameters:

Important:

You can't edit the branch identifier after creating the branch. You can only edit the description and metadata fields.

Confirm the response returns a 200 and the following response data structure:

{
  "id": "{branch-id}",
  "companyId": "{company-id}",
  "branch": "{branch-identifier}",
  "description": "{branch-description}",
  "isActivated": true,
  "createdAt": "{timestamp}"
}

Save the id (branch id) value from the response for future API calls.

Understand the configuration scope

Understand the configuration scope to manage which organizations, companies, branches, and operations a setting applies to.

After creating your organization and companies, you configure settings for your products (credentials, workflow options, notification preferences).

Scope levels

Organization level: Applies to all companies
Product level: Applies to all companies using this product
Company level (Tax ID-specific): Applies to one specific tax ID
Branch level: Applies to specific branch within company
Operation level: Applies to specific operation type (inbound/outbound)

Scope parameters in API settings

orgId - Organization
productId - Specific product
taxId - Specific tax ID
branch - Specific branch
operation - Operation type (Only available in select markets)

Scope precedence

Most granular configuration wins. Settings with more scope parameters specified take precedence over settings with fewer scope parameters.

Examples:

Setting A: orgId + productId (applies to all tax IDs using this product)
Setting B: orgId + productId + taxId (applies to one specific tax ID)

Result: Tax ID uses Setting B, all other tax IDs use Setting A.

Best practices

Configure at the highest level possible (Organization or Product) to minimize administrative overhead.
Only use granular scopes (Company, Branch, Operation) when business requirements justify separate configurations.

How can we help?

Set up your account

Account structure

Account structure

Account elements

Create an organization

Set up in Compliance Network

Set up using API

Assign products to an organization

Set up in Compliance Network

Set up using API

Add companies to your organization

Set up using Compliance Network

Set up using API

Edit a company

Set up using Compliance Network

Set up using API

Add branches

Use cases

Set up using Compliance Network

Set up using API

Understand the configuration scope

Best practices

sovos-footer