Processing Swedish 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 Swedish invoices.

In addition to sending invoice data to the target system, the E-conomic integration offers specialized business logic for customers who process Swedish 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:

  • Swedish document type with these fields:
    • PaymentReferenceNumber (OCR)
    • SupplierIBAN1 (IBAN)
    • SupplierBicSwiftNumber (SWIFT)
    • SupplierBankClearingNumber (Clearingnummer)
    • SupplierBankCodeNumber1 (Kontonummer)
    • SupplierAccountNumber2 (Bankgiro)
    • SupplierAccountNumber1 (Plusgiro)
    • CashAccount (CashAccount)
  • E-conomic target system service.
  • The Payment type validation must be enabled in the Validation service and in the Rules tab in the Document type dialog.
  • Master data that defines these values for the payment-type field:
    • Bankgiro
    • Plusgiro
    • Bank transfer
    • Entry only
    • IBAN
    • None

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 Enabled fields Info Sample value Validation E-conomics field mapping
Bankgiro
  • SupplierAccountNumber2 (Bankgiro)
  • PaymentReferenceNumber (OCR)
  RSO Bankgiro: 991-2346 (normally 7 or 8 numbers with dash in middle)

RSO OCR: 1234475 (numbers of various lengths)

Validated according to the extraction field format. OCR field is optional.
  • SupplierAccountNumber2 (Bankgiro) >> "BankGiro no"
  • PaymentReferenceNumber (OCR) >> "OCR Line"
  • If RSO field OCR is empty, use PaymentTemplate >> "OCR Line"
Plusgiro
  • SupplierAccountNumber1 (Plusgiro)
  • PaymentReferenceNumber (OCR)
  RSO Plusgiro: 4176503-3 (normally 8 numbers with dash before last number)

RSO OCR: 1234475 (numbers of various lengths)

Validated according to the extraction field format. OCR field is optional.
  • SupplierAccountNumber1 (Plusgiro) >> "Plusgiro no"
  • PaymentReferenceNumber (OCR) >> "OCR Line"
  • If RSO field OCR is empty, use PaymentTemplate >> "OCR Line"
Bank transfer
  • SupplierBankClearingNumber (Clearingnummer)
  • SupplierBankCodeNumber1 (Kontonummer)
Clearingnummer + fill with zeros + Kontonummer

If Clearingnummer is 5 chars long, the last one should be removed.

The total number of characters should be 16 (filled with zeros in middle).

  Validated according to the extraction field format.

ClearingNo + Kontonummer should not exceed 17 characters.

  • Combination of (Kontonummer) and (Clearingnummer) >> "Account number"
  • PaymentTemplate >> "Message"
Entry only CashAccount     No validation. CashAccount >> CashAccount
IBAN
  • SupplierBicSwiftNumber (SWIFT)
  • SupplierIBAN1 (IBAN)
The Swedish E-conomic version does not support automatic payments for foreign invoices, so this information is not used.   Validated according to the extraction field format. Both fields must be filled in.
  • A combination of SupplierIBAN1 (IBAN) and SupplierBicSwiftNumber (SWIFT), with slash as separator, is put into >> "IBAN/SWIFT no"
  • PaymentTemplate >> "Message"
None No fields required.     No validation.  
Tip The payment-type fields must be validated correctly. You cannot force a field to pass validation by pressing  Enter.