Processing Danish invoices with E-conomic

In addition to sending invoice data to the target system, the E-conomic integration offers specialized business logic for customers who process Danish invoices.

In addition to sending invoice data to the target system, the E-conomic integration offers specialized business logic for customers who process Danish invoices. You can use the Payment type field to automatically send the correct payment information to E-conomic and determine which field validations are performed. To leverage the full potential of E-conomic integration, use these components:

How it works

When an invoice is processed by ReadSoft Online, the payment-type field is automatically set according to the Payment type from supplier setting, which specifies whether the value is interpreted from the invoice image or taken from the supplier in E-conomic. If necessary, you can change the payment type when you verify the invoice. Changing the supplier during verification can also cause the payment type to change, if the Payment type from supplier setting is set to true. Payment fields are validated according to this table.

Payment type Required fields Ignored fields Validation
+04
  • PaymentReferenceNumber (Girostreng)
  • SupplierIBAN1 (IBAN)
  • SupplierBankCodeNumber1 (SWIFT)
  • SupplierBankClearingNumber (Regnummer)
  • SupplierAccountNumber1 (Kontonummer)
  • CashAccount (CashAccount)
Girostreng field is validated according to format in brackets and must contain:

Payment type code – “04” {N(2)}

It is also validated according to the extraction field format.

+71
  • PaymentReferenceNumber (Girostreng)
  • SupplierIBAN1 (IBAN)
  • SupplierBankCodeNumber1 (SWIFT)
  • SupplierBankClearingNumber (Regnummer)
  • SupplierAccountNumber1 (Kontonummer)
  • CashAccount
Girostreng field is validated according to the format in brackets and must contain:

Payment type code – “71” {N(2)}

It is also validated according to the extraction field format.

+73
  • PaymentReferenceNumber (Girostreng)
  • SupplierIBAN1 (IBAN)
  • SupplierBankCodeNumber1 (SWIFT)
  • SupplierBankClearingNumber (Regnummer)
  • SupplierAccountNumber1 (Kontonummer)
  • CashAccount (CashAccount)
The Girostreng field is validated according to the format in brackets and must contain:

Payment type code – “73” {N(2)}

It is also validated according to the extraction field format.

+75
  • PaymentReferenceNumber (Girostreng)
  • SupplierIBAN1 (IBAN)
  • SupplierBankCodeNumber1 (SWIFT)
  • SupplierBankClearingNumber (Regnummer)
  • SupplierAccountNumber1 (Kontonummer)
  • CashAccount (CashAccount)
The Girostreng field is validated according to the format in brackets and must contain:

Payment type code – “75” {N(2)}

It is also validated according to the extraction field format.

Bank transfer
  • SupplierBankClearingNumber (Regnummer)
  • SupplierAccountNumber1 (Kontonummer)

     

  • PaymentReferenceNumber (Girostreng)
  • SupplierIBAN1 (IBAN)
  • SupplierBankCodeNumber1 (SWIFT)
  • CashAccount (CashAccount)
The combined length of the Regnummer and Kontonummer fields cannot exceed 14 characters.

Regnummer must be 4 digits, unless  Kontonummer is 14 digits and Regnummer is empty.

If Regnummer is 4 digits and Kontonummer is less than 10 digits, then Kontonummer is automatically prefixed with zeroes so it is 10 digits long when the data is sent to E-conomic.

Entry Only
  • CashAccount
  • PaymentReferenceNumber (Girostreng)
  • SupplierIBAN1 (IBAN)
  • SupplierBankCodeNumber1 (SWIFT)
  • SupplierBankClearingNumber (Regnummer)
  • SupplierAccountNumber1 (Kontonummer)
The CashAccount field must be four digits long.

You specify a default value for the field in the Danish payment type setting.

IBAN
  • SupplierIBAN1 (IBAN)
  • SupplierBankCodeNumber1 (SWIFT)

     

  • PaymentReferenceNumber (Girostreng)
  • SupplierBankClearingNumber (Regnummer)
  • SupplierAccountNumber1 (Kontonummer)
  • CashAccount (CashAccount)

 

Validated according to extraction field format. Both fields must be filled in.
None No fields required. All payment-type fields ignored. No validation.
Tip The payment-type fields must be validated correctly. You cannot force a field to pass validation by pressing Enter.

When the invoice is posted to E-conomic, the validated payment information and other invoice data are set in the "day book" according to this table:

ReadSoft Online value E-conomic field
+04
Payment type Payment type
Giro account in Giro number Giro account
Payment ID in Giro number OCR line
+71
Payment type Payment type
Creditor ID in Giro number FI supplier no
Payment ID in Giro number OCR line
+73
Payment type Payment type
Creditor ID in Giro number FI supplier no
“Fakturanr” + invoice number Message
+75
Payment type Payment type
Creditor ID in Giro number FI supplier no
Payment ID in Giro number/“Fakturanr” + invoice number OCR/optional message
Bank transfer
Payment type Payment type
Reg Nummer + Konto Nummer Account no
“Fakturanr” + invoice number Message
Entry only
Creates a supplier invoice with Entry only as the payment type and a supplier payment with the cash account.
IBAN
Payment type Payment type
IBAN + SWIFT IBAN/SWIFT no
“Fakturanr” + invoice number Message
None
Payment type Payment type