Skip to main content

e-conomic Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to an e-conomic location.
e_conomic_api.png

e-conomic

Create an e-conomic Destination​

  1. Click the + icon on the Nexset that will be sent to the e-conomic destination, and select the Send to Destination option from the menu.

  2. Select the e-conomic connector from the list of available destination connectors. Then, select the credential that will be used to connect to the e-conomic account, and click Next; or, create a new e-conomic credential for use in this flow.

  3. In Nexla, e-conomic destinations can be created using pre-built endpoint templates, which expedite destination setup for common e-conomic write operations. Each template is designed specifically for the corresponding e-conomic API endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    e-conomic destinations can also be configured manually, allowing you to send data to e-conomic endpoints not included in the pre-built templates or apply further customisations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common e-conomic endpoints. Each template is designed specifically for the corresponding e-conomic REST API endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Create Customer

    Creates a new customer record in the e-conomic system. Use this endpoint to push customer data from an external CRM, e-commerce platform, or onboarding system into e-conomic as part of an automated customer creation workflow.

    • No additional URL parameters are required for this endpoint. Select the Create Customer template and ensure that the Nexset being sent contains the required customer fields.

    • At minimum, the request body must include the following fields as required by the e-conomic API:

      • name — The customer's full name or company name.
      • currency — A reference object containing the ISO 4217 currency code (e.g., {'code': 'DKK'}).
      • paymentTerms — A reference object containing the payment terms number.
      • customerGroup — A reference object containing the customer group number.
      • vatZone — A reference object containing the VAT zone number.
    • Optional fields such as address, city, zip, country, email, phone, and corporateIdentificationNumber can also be included in the Nexset payload.

    Nexla sends each Nexset record as a separate JSON POST request to the e-conomic Customers API. For full details on available request body fields, see the e-conomic Customers API documentation.

    Update Customer

    Updates an existing customer record identified by the customer's unique number. Use this endpoint to synchronise customer changes from an external system (such as a CRM or ERP) back into e-conomic, keeping customer master data consistent across platforms.

    • This endpoint requires one additional parameter:

      • Customer Number — Enter the unique e-conomic customer number of the customer to be updated. This value is used to construct the API URL (PUT /customers/{customerNumber}) and must correspond to an existing customer in your e-conomic account.
    • The request body should include all customer fields that need to be updated. The e-conomic API uses a full replacement (PUT) approach, so all required fields must be present in the payload even if they are not being changed.
    • Required fields are the same as for the Create Customer endpoint: name, currency, paymentTerms, customerGroup, and vatZone.

    The Customer Number is the unique numeric identifier assigned by e-conomic when the customer is created. It can be retrieved using the e-conomic List Customers data source or found in the e-conomic user interface under the customer record.

    Create Draft Invoice

    Creates a new draft invoice in the e-conomic system. Draft invoices are the primary entry point for the e-conomic invoicing lifecycle — they must be created before they can be reviewed, edited, and ultimately booked (finalised) as legally binding invoices. Use this endpoint to automate invoice creation from order management systems, billing platforms, or project management tools.

    • No additional URL parameters are required. Select the Create Draft Invoice template and ensure that the Nexset contains the required invoice fields.

    • At minimum, the request body must include:

      • date — The invoice date in yyyy-MM-dd format.
      • currency — A reference object containing the ISO 4217 currency code.
      • paymentTerms — A reference object containing the payment terms number.
      • customer — A reference object containing the customer number.
      • recipient — An object containing the recipient name and VAT zone.
      • lines — An array of invoice line objects, each containing product, quantity, unit price, and VAT account details.

    A draft invoice can be reviewed and edited within e-conomic before being booked. To programmatically book the draft and convert it to a legally binding invoice, use the Book Invoice endpoint after the draft is created. Full field documentation is available in the e-conomic Draft Invoices API documentation.

    Book Invoice

    Books (finalises) a draft invoice by converting it into a legally binding booked invoice. Once booked, the invoice is permanently recorded in the e-conomic accounting system and generates an immutable general-ledger entry. Use this endpoint as the final step in an automated invoice creation workflow, after verifying that the draft invoice is correct.

    • No additional URL parameters are required. Select the Book Invoice template and ensure the Nexset contains a reference to the draft invoice to be booked.

    • The request body must include a reference to the draft invoice:

      • draftInvoice — An object containing the draft invoice number to be booked (e.g., {'draftInvoiceNumber': 123}).

    Booking an invoice is irreversible — once booked, the invoice cannot be deleted or edited within e-conomic. Ensure that the draft invoice has been reviewed and approved before triggering this endpoint. For full field documentation, see the e-conomic Booked Invoices API documentation.

    Create Draft Order

    Creates a new draft order in the e-conomic system. Draft orders represent sales orders in preparation that have not yet been sent to customers. Use this endpoint to push order data from an external e-commerce or ERP system into e-conomic for fulfilment and invoicing.

    • No additional URL parameters are required. Select the Create Draft Order template and ensure the Nexset contains the required order fields.

    • At minimum, the request body should include:

      • date — The order date in yyyy-MM-dd format.
      • currency — A reference object containing the ISO 4217 currency code.
      • paymentTerms — A reference object containing the payment terms number.
      • customer — A reference object containing the customer number.
      • recipient — An object containing the recipient name and VAT zone.
      • lines — An array of order line objects containing product, quantity, and unit price details.

    Additional reference information is available in the e-conomic Orders API documentation.

    Update Draft Order

    Updates an existing draft order identified by the order number, before it has been sent. Use this endpoint to synchronise order changes from an external system back into e-conomic — for example, updating quantities, delivery dates, or line items on pending orders.

    • This endpoint requires one additional parameter:

      • Draft Order Number — Enter the unique e-conomic draft order number of the order to be updated. This value is used to construct the API URL (PUT /orders/drafts/{orderNumber}) and must correspond to an existing draft order in your e-conomic account.
    • The request body should include all order fields using the same structure as Create Draft Order. Because the e-conomic API uses a full replacement (PUT) approach, all required fields must be present in the payload.

    The Draft Order Number can be retrieved using the e-conomic List Draft Orders data source or found within the e-conomic user interface under the relevant order record.

    Create Draft Quote

    Creates a new draft quote (quotation) in the e-conomic system. Quotes allow you to send pricing proposals to customers before a formal order or invoice is raised. Use this endpoint to automate quote generation from a CRM, CPQ, or sales management platform.

    • No additional URL parameters are required. Select the Create Draft Quote template and ensure the Nexset contains the required quote fields.

    • The request body structure is similar to draft orders and invoices, and should include at minimum:

      • date — The quote date in yyyy-MM-dd format.
      • currency — A reference object containing the ISO 4217 currency code.
      • paymentTerms — A reference object containing the payment terms number.
      • customer — A reference object containing the customer number.
      • recipient — An object containing the recipient name and VAT zone.
      • lines — An array of quote line objects containing product, quantity, and unit price details.

    Additional reference information is available in the e-conomic Draft Quotes API documentation.

    Create Product

    Creates a new product in the e-conomic product catalogue. Use this endpoint to synchronise product or service catalogue data from an external PIM, e-commerce platform, or ERP system into e-conomic, ensuring that product definitions are consistent across systems.

    • No additional URL parameters are required. Select the Create Product template and ensure the Nexset contains the required product fields.

    • At minimum, the request body must include:

      • productNumber — A unique identifier string for the product.
      • name — The product name or description.
      • salesPrice — The default sales price for the product.
      • productGroup — A reference object containing the product group number.
    • Optional fields include costPrice, recommendedPrice, unit, description, and stock-related fields.

    Additional reference information is available in the e-conomic Products API documentation.

    Update Product

    Updates an existing product in the e-conomic product catalogue, identified by the product number. Use this endpoint to push price changes, description updates, or stock information from an external system back into e-conomic.

    • This endpoint requires one additional parameter:

      • Product Number — Enter the unique e-conomic product number of the product to be updated. This value is used to construct the API URL (PUT /products/{productNumber}) and must correspond to an existing product in your e-conomic account.
    • The request body should include all product fields using the same structure as Create Product. Because the e-conomic API uses a full replacement (PUT) approach, all required fields must be present.

    Product numbers can be retrieved using the e-conomic List Products data source or found within the e-conomic product catalogue in the user interface.

    Create Supplier

    Creates a new supplier record in the e-conomic system. Use this endpoint to import supplier master data from an external procurement, ERP, or vendor management platform into e-conomic, ensuring that supplier records are consistent across all systems.

    • No additional URL parameters are required. Select the Create Supplier template and ensure the Nexset contains the required supplier fields.

    • At minimum, the request body must include:

      • name — The supplier's full name or company name.
      • currency — A reference object containing the ISO 4217 currency code.
      • paymentTerms — A reference object containing the payment terms number.
      • supplierGroup — A reference object containing the supplier group number.
      • vatZone — A reference object containing the VAT zone number.
    • Optional fields include address, city, zip, country, email, phone, and corporateIdentificationNumber.

    Additional reference information is available in the e-conomic Suppliers API documentation.

    Create Journal Voucher

    Creates a journal voucher (bookkeeping entry) in a specified e-conomic journal. Journal vouchers are used to post accounting transactions such as expenses, payroll, bank imports, and other general-ledger entries. Use this endpoint to automate the creation of accounting transactions from external payroll, expense management, or banking systems.

    • This endpoint requires one additional parameter:

      • Journal Number — Enter the unique number of the e-conomic journal in which the voucher will be created. This value is used to construct the API URL (POST /journals/{journalNumber}/vouchers). The Journal Number can be retrieved using the e-conomic List Journals data source.

    • The request body must include the voucher details:

      • accountVoucher — An array of voucher line objects, each specifying an account number, amount, text description, and date.
      • date — The voucher date in yyyy-MM-dd format.

    Journal vouchers must be associated with an existing journal in your e-conomic account. The Journal Number must correspond to a journal that is open for new entries. For full field documentation, see the e-conomic Journals API documentation.

Configure Manually​

e-conomic destinations can be manually configured to send data to any valid e-conomic REST API endpoint.

Using manual configuration, you can also configure Nexla to automatically send the response received from the e-conomic API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the e-conomic API from the Method pulldown menu. The most common methods for writing data to e-conomic are:

    • POST: For creating new records (customers, invoices, orders, products, suppliers, journal vouchers, quotes).
    • PUT: For fully replacing and updating existing records identified by their unique ID in the URL path.

Data Format​

  1. Select the format in which the Nexset data will be sent to the e-conomic API from the Content Format pulldown menu. The e-conomic REST API requires all request bodies to be in JSON format, so select JSON from the menu. Nexla will automatically convert the data to JSON for each API call.

API Endpoint URL​

  1. Enter the URL of the e-conomic REST API endpoint to which you want to send the Nexset data in the URL field. The base URL is https://restapi.e-conomic.com. For update operations (PUT), include the unique identifier of the resource at the end of the URL path — for example, https://restapi.e-conomic.com/customers/42 to update customer number 42.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers and corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    You do not need to include the X-AppSecretToken or X-AgreementGrantToken authentication headers in this field — these are automatically injected by Nexla from the selected e-conomic credential.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this e-conomic destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings.

Most e-conomic write endpoints accept a single JSON object per request rather than arrays. Batching is most appropriate when writing to custom or bulk-capable endpoints. Review the e-conomic API documentation for the target endpoint before enabling batching.

Response Webhook​

Optional

Nexla can automatically send the response received from the e-conomic API after each call to a new Nexla webhook data source. This option allows you to track the status of each API call and capture any information returned by the e-conomic API — for example, the newly created customer number or invoice number assigned by e-conomic after a successful creation request.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the e-conomic API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.

  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the e-conomic API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the e-conomic API using the current settings.

Save & Activate the Destination​

  • Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to the e-conomic account, open the destination resource menu and select Activate.

    The Nexset data will not be sent to e-conomic until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over when data movement begins.