ACCOUNT

This page introduces Account imports in DJUST. It explains the overall logic, the data structure, and the expected format for creating, updating, deactivating, and deleting Accounts and their addresses.

⚙️ Introduction

This job allows the creation and management of Accounts and their shipping/billing addresses via CSV import or API Connector.

You can:

  • Create new Accounts with their addresses
  • Update existing Accounts and their addresses
  • Link and unlink addresses from Accounts
  • Deactivate an Account
  • Delete an Account

📂 Import model

CSV Structure

The CSV file must contain one row per Account. To import multiple addresses for the same Account, add one row per address.

📄

Template

You can use the following spreadsheet as a template to structure your import:

Accounts - Template


API Connector

The API Connector sends data as a JSON payload. The JSON must always be a list of objects, regardless of the operation (create, update, deactivate, delete).

Addresses can be structured in two ways depending on how they are sent by the source system:

Option A — Addresses as a nested list

[
  {
    "accountName": "string",
    "accountExternalId": "string",
    "accountManagerName": "string",
    "accountWebsite": "string",
    "companyRegistrationName": "string",
    "businessRegistrationNumber": "string",
    "customerTagExternalId": "string",
    "accountVatNumber": "string",
    "deleted": false,
    "inactive": false,
    "address": [
      {
        "addressExternalId": "string",
        "addressFullName": "string",
        "addressCountry": "string",
        "addressCity": "string",
        "addressZipCode": "string",
        "addressStreetName": "string",
        "addressLabel": "string",
        "addressAdditionalStreetName": "string",
        "addressDepartment": "string",
        "addressPhoneNumber": "string",
        "unlinkAddress": false,
        "shippingAddress": true,
        "billingAddress": true
      }
    ]
  }
]

Option B — Flat object structure

[
  {
    "accountName": "string",
    "accountExternalId": "string",
    "accountManagerName": "string",
    "accountWebsite": "string",
    "companyRegistrationName": "string",
    "businessRegistrationNumber": "string",
    "customerTagExternalId": "string",
    "accountVatNumber": "string",
    "deleted": false,
    "inactive": false,
    "addressExternalId": "string",
    "addressFullName": "string",
    "addressCountry": "string",
    "addressCity": "string",
    "addressZipCode": "string",
    "addressStreetName": "string",
    "addressLabel": "string",
    "addressAdditionalStreetName": "string",
    "addressDepartment": "string",
    "addressPhoneNumber": "string",
    "unlinkAddress": false,
    "shippingAddress": true,
    "billingAddress": true
  }
]
💡

Note

When using the nested address structure, map the parent address array first before mapping the fields within each address object.


📋 Fields

FieldDefinitionRequired for creationRequired for updateEditableDefault Value
Account NameAccount name✅✅
Account External IdUnique external identifier of the Account✅✅
Account Manager NameName of the account manager✅
Account WebsiteWebsite URL of the Account✅
Company Registration NameLegal registered company name✅✅
Business Registration NumberBusiness registration number✅✅
Customer Tag External IdExternal identifier of the customer tag✅
Account VAT NumberVAT number of the Account✅
DeletedSet to TRUE to delete the Account✅FALSE
InactiveSet to TRUE to deactivate the Account✅FALSE
Address External IdUnique external identifier of the address✅☑️ (Required when updating an address)
Address Full NameFull name associated with the address✅✅
Address CountryCountry of the address✅✅
Address CityCity of the address✅✅
Address Zip CodePostal code of the address✅✅
Address Street NameStreet name of the address✅✅
Address LabelLabel for identifying the address✅
Address Additional Street NameAdditional address information✅
Address DepartmentAdministrative department of the address (free text, e.g. 75, 2A, 971). Used to determine the applicable delivery zone.✅
Address Phone NumberPhone number associated with the address✅
Unlink Address From AccountSet to TRUE to unlink an address from the Account✅FALSE
Shipping AddressSet to TRUE to define the address as a shipping address✅TRUE
Billing AddressSet to TRUE to define the address as a billing address✅TRUE
☑️

Conditionally required

⚠️

Required Custom Fields

Any custom fields configured as required in DJUST must also be included.


🧠 Key Business Rules

  • An Account can have one or more addresses.
  • By default, an address is defined as both a shipping and a billing address.
  • An address can be associated with multiple Accounts. In this case, all mandatory address fields must be provided — not only the Address External Id.
  • It is not possible to update an existing address already associated with another Account while simultaneously linking it to a new Account.
  • Account External Id and Address External Id cannot be updated once set.
  • Address Department is optional. When absent from the import file, it stays null without raising an error; when provided, it is persisted on the address. It applies to both account and organisation addresses, in creation and update.
  • Setting Inactive to TRUE deactivates the Account without deleting it. The Account will no longer be visible or usable on the platform.
  • Setting Deleted to TRUE permanently removes the Account. This action is irreversible.
  • When unlinking an address (unlinkAddress: true), the system checks whether the address is the last billing address of the Account. If so, the unlink is rejected with an error in the import report — an Account must always have at least one billing address.
  • After unlinking, if the address is no longer linked to any Account, it is permanently deleted from the system.
  • Empty fields in standard columns do not delete recorded values.
  • Empty fields in Custom Fields delete the recorded values.
📌

Best Practices

✔️ Use the correct payload structure (nested vs flat) based on how addresses are sent by your source system.

✔️ Map the address parent array first when using the nested structure.

✔️ Map required Custom Fields before running the import.

✔️ Follow data formatting guidelines for optimal import results.


Did this page help you?