Skip to main content

e-conomic Integration

This guide explains how to set up the e-conomic integration, allowing you to automatically include payment links on invoices using our payment platform and generate journal drafts in e-conomic when payments are received.

Important:
To use payment links, you must configure an AppConnection.
To create journal drafts (for invoices or webshop transactions), you must create the corresponding InvoiceConfig or TransactionConfig entries.
Without these, the integration will not be able to handle payment links or create journal drafts.

1. What the integration offers​

  • Adds secure payment links to your e-conomic invoices.
    Every invoice you create can automatically include a payment link. Customers can pay directly through our payment platform, reducing manual work and streamlining the payment experience.
    Payment links are only available when an AppConnection has been configured.

  • Creates journal drafts automatically.
    When an invoice is paid or a webshop transaction is completed, the service generates the corresponding journal draft inside e-conomic. This keeps your bookkeeping accurate without manual entry.
    Journal drafts are only created when matching InvoiceConfig or TransactionConfig entries exist and the AppConnection mode is set to "INSTANT"

2. How to configure​

There are two main setup steps:

3. Backoffice setup​

The app has the following permissions: Bookkeeping, Sales and Project employee

3.1 Install the integration​

  • Click the installation URL.
  • Copy the agreement token into the backoffice. The token uniquely identifies your e-conomic agreement.
  • Then fill out the pointOfSaleId, apiKey, webhookToken and mode.
  • Payment links cannot work without an AppConnection, because the static fields in the payment link come from this configuration.
  • You can create multiple AppConnections if needed, each AppConnection represents a separate point of sale, allowing you to manage different payment flows independently.

3.2 Configure invoice​

  • Define how paid invoices should be journaled.
  • If you invoice in multiple currencies, create one InvoiceConfig per currency.
  • Journal drafts for invoices are only created if you configure InvoiceConfig entries.

3.3 Configure webshop transaction​

  • Define how completed transactions from your webshop should be journaled.
  • Create separate TransactionConfig entries for each currency if needed.
  • Journal drafts for transactions are only created if TransactionConfig entries exist.

3.4 Automatic journaling is controlled by mode​

  • Configurations (InvoiceConfig / TransactionConfig) are active as soon as they are created.
  • Whether a journal draft is automatically created after payment depends on the Mode field on the associated AppConnection:
    • INSTANT - journal drafts are created automatically when payments complete.
    • MANUAL - journal drafts are not created automatically.
  • Use the AppConnection Mode to control automatic vs manual journal creation for all configs that reference that AppConnection.

4. e-conomic setup​

Add this payment link to your invoice template.
Use the example that matches your account language.

Danish example:
https://economic-integration.epay.eu/public/invoice?invoiceNumber=[FakturaNr]&amount=[TotalBeloebKroner][TotalBeloebOere]&currency=[Valuta]&debitorNumber=[KundeNr]&pointOfSaleId=your_point_of_sale_id&testMerchant=is_test_merchant&accountId=your_account_id

English example:
https://economic-integration.epay.eu/public/invoice?invoiceNumber=[InvoiceNo]&amount=[TotalAmountPounds][TotalAmountPence]&currency=[Currency]&debitorNumber=[CustomerNo]&pointOfSaleId=your_point_of_sale_id&testMerchant=is_test_merchant&accountId=your_account_id

A button to generate this link will soon be available in the backoffice.

If your account uses a different language, open the Template Designer, insert these fields using the dynamic field tool, and copy the exact field names as they appear in your language.

Important:
Dynamic field names must match the language of your e-conomic account exactly.
e-conomic does not accept field names in any language other than the one your account was originally set up with.

4.2 Dynamic fields (4 required)​

These four placeholders must be included in the link, and must match the language of your e-conomic account:

  • invoiceNumber = [InvoiceNo] / [FakturaNr]
  • amount = [TotalAmountPounds][TotalAmountPence] / [TotalBeloebKroner][TotalBeloebOere]
  • currency = [Currency] / [Valuta]
  • debtorNumber = [CustomerNo] / [KundeNr]

Supported dynamic fields:

4.3 Static fields (3 required)​

These values do not come from the invoice, they come from your AppConnection:

  • pointOfSaleId = your_point_of_sale_id
  • testMerchant = is_test_merchant
  • accountId = your_account_id

Note:

  • These fields are taken directly from the AppConnection.
  • accountId and testMerchant are assigned automatically when the AppConnection is created (based on your login session).
  • You do not enter these two values manually.
  • If you need to look them up later, you can find them in the Backoffice under AppConnections.
  • These names never change; they are the same regardless of your e-conomic account’s language.

5. How configuration matching works​

Each configuration represents one specific currency, and you can have multiple configurations, both for invoices and for webshop transactions.

Examples:

  • One invoice configuration for DKK
  • One invoice configuration for EUR
  • One invoice configuration for USD
  • And the same applies for transaction configurations.

This means:

  • All invoices issued in DKK use the DKK invoice configuration.
  • All invoices issued in EUR use the EUR invoice configuration.
  • All webshop transactions in DKK use the DKK transaction configuration.
  • And so on.

When a payment is completed, the system reads the currency from the paid invoice or from the webshop transaction and selects the configuration with the same currency. Only that configuration is used to create the journal draft.

If there is no configuration for the currency of the payment, or no configuration created at all, no journal draft is created.

This ensures that each currency is journaled correctly according to your defined accounts.