Skip to content

Configuring SEPA Credit Export

Your organization's business may require to export bank transfer orders for invoices. These payment orders can then directly be used by banks for triggering the corresponding payment operations.

JustOn supports two common implementations of (interchangeable) bank transfer orders:

For invoices whose payment method is either Bank Transfer or Direct Debit, you can produce SEPA XML files for debits and credits using the invoice export mechanism.

Configuring the SEPA Credit export comprises the following tasks:

Info

For information about executing payment exports, see Exporting Bank Transfer Orders.

SEPA Credit Concepts

JustOn exports SEPA Credit orders for invoices if

  • the payment method is either Bank Transfer or Direct Debit, and
  • the invoice's open amount is less than 0.

Before executing the export, JustOn validates the SEPA payment information. The validation succeeds if the following conditions are true:

  • The invoice refers to a tenant.
  • The following fields of the tenant are set:

    IBAN

    Company

  • The following fields of the invoice are set:

    Bank Account

    Bank Account Owner

  • When using a CBI export format, the Member ID field of the tenant contains the ABI code of the bank.

  • If Credit IBAN and Credit BIC are set for the tenant, JustOn uses these values instead of IBAN and BIC.

Info

JustOn checks the format and structure (length, allowed characters, etc.) of the IBAN and BIC according to the definitions in the SEPA Credit Transfer Schemes.

The result of the validation is written to the SEPA Validation Error field. The bank transfer order for an invoice is exported if the SEPA Validation Error field is empty.

Generated Payout Balance

If the user has selected the option Create Payments upon exporting the bank transfer orders, JustOn creates payment balances according to the exported credit data. The balance field values are set as follows:

Field Value
Account value of Account of the invoice
Amount inverted value of Next Payment Due of the invoice
Date value of Next Payment Due Date of the invoice
Payment Method Bank Transfer
Reference string as defined in PaymentReference of the invoice template, with the placeholders resolved using invoice data
Type Payout

Defining Export Settings

Depending on your organization's requirements, you must define an export configuration for SEPA Direct Debit exports.

  1. In Setup, open Custom Settings.

    In Salesforce Lightning, navigate to Custom Code > Custom Settings.

    In Salesforce Classic, navigate to Develop > Custom Settings.

  2. Click Manage in the row of Export Settings.

  3. Click New.
  4. Specify the details as necessary.

    Field Possible Values Description
    Name SEPA Credit A unique name for the custom setting record, will be selectable when exporting invoice data.
    Active true | false Determines whether the configuration is available in the UI.
    SEPA: Booking per Transaction true | false Determines whether to override SEPA batch booking (consolidated payment, default). If true, forces an individual SEPA transaction per payment. Produces a corresponding <BtchBookg> element in the SEPA XML.
    CUC 3121975D The unique CBI code that identifies all parties in the CBI community (clients, banks and network access points). Required when using a CBI format string, is applied for and registered by the access bank.
    Create Payments true | false Determines whether to create payment balances on the invoices upon exporting, which sets the credits Settled.
    Users can overwrite this option manually when starting the export.
    Format XML CCT pain.001.003.03 Creates a XML file in the format CCT (Core Credit Transfer, pain.001.003.03).
    XML CCT pain.001.001.03 Creates a XML file in the format pain.001.001.03 (valid for Austria and Netherlands)
    XML CCT CBIPaymentRequest.00.04.00 Creates a XML file in the format CBIPaymentRequest.00.04.00 (CBI format for Italy)
    Select Condition Date__c = THIS_YEAR Specifies a condition (SOQL WHERE clause) to restrict the set of included records. If empty, matches all invoices in the list.
    For details, see SOQL SELECT Syntax in the Salesforce Help.
    Use ASCII Encoding Scheme true | false Determines whether to perform a phonetic replacement of the contents of the resulting CSV or XML file.
    For XML exports, all required replacements for the SEPA format are performed. For details, see SEPA Requirements for an Extended Character Set (UNICODE Subset) - Best Practices.
    Target Export Specifies the name of a file distribution target for the exported files.
    For exports to cloud storage services, the file distribution target must be the one set up as the storage location with the use case Export and the backend AmazonS3 or GoogleDrive.
    If left empty, the file will only be available on Salesforce's Files tab as of JustOn 2.49.
    Allowed Currencies EUR,SEK Specifies a comma-separated list of currencies that are allowed for ISO 20022 XML formats. Defaults to EUR, which is the only allowed currency for SEPA.
    ISO20022: Service Level Code SEPA Specifies the pre-agreed level of service between the parties. For SEPA, defaults to SEPA. For non-SEPA payments, contact your bank.
  5. Click Save.

Configuring SEPA Payment Fields

Exporting payment orders for SEPA Direct Debit requires a number of fields to be set on the invoice. The required data is taken from the tenant and, usually, from the account. Your business may, however, require to allow for exceptions: You may need to generate an invoice, and consequently, a payment order, with banking data that differs from that on the account. In this case, you need the corresponding data on the source object from which you create the invoice - either the subscription, the opportunity) or the source object for arbitrary object billing.

Tenant Fields

The following fields of the tenant must be set:

Field Description
Company The name of the tenant's company.
IBAN The IBAN (International Bank Account Number) of the tenant.

Depending on your business requirements, you may have to define the following optional fields, too:

Field Description
Member Id ABI code of the bank, required when using a CBI export format.
Organization Identification An organization ID according to ISO 20022. Required for some banks.
For SEPA, leave this empty.
Scheme Name Code A data source scheme, related to the organization ID according to ISO 20022. Required for some banks.
For SEPA, leave this empty.

Account Fields

The following fields of the account must be configured:

Field Data Type Description
ON_BankAccount String (34) The International Bank Account Number.
ON_BankAccountOwner String (255) The name of the owner of this bank account. Defaults to Account Name if empty.
ON_BankCode String (11) The bank identifier code.
With an IBAN as bank account number, the bank code (BIC) is not required.
ON_PaymentMethod
or
ON_InvoicePaymentMethod
Picklist The payment method that is preferred for paying invoices of this account.
Use ON_PaymentMethod to fill the corresponding invoice field when creating invoices. Use ON_InvoicePaymentMethod to fill the corresponding subscription field when building subscriptions, out of which you then create invoices.

Source Object Fields

You may need to generate an invoice, and consequently, a payment order, with banking data that differs from that on the account. In this case, you need the corresponding data on the source object from which you create the invoice - either the subscription, the opportunity or the source object for arbitrary object billing.

Note that the subscription fields are available by default. When using opportunities or other source objects, you must create these fields as ON fields. For help about creating fields, see Managing Object Fields.

Info

The fields on the source object overwrite the values set on the account.

Note

Be aware that all bank data fields on the account are ignored if there is a corresponding subscription field set.

Field Data Type Description
BankAccount
ON_BankAccount
String (34) The International Bank Account Number.
BankAccountOwner
ON_BankAccountOwner
String (255) The name of the owner of this bank account. If empty, defaults to Legal Account Name if available, otherwise defaults to Account Name.
BankCode
ON_BankCode
String (11) The bank identifier code.
With an IBAN as bank account number, the bank code (BIC) is not required.
InvoicePaymentMethod
ON_InvoicePaymentMethod
Picklist The payment method that is preferred for paying invoices of this account.

Invoice Fields

The invoice fields are copied from the account or, if set, from the source object.

Field Data Type Description
BankAccount String (34) The International Bank Account Number.
BankAccountOwner String (255) The name of the owner of this bank account. If empty, defaults to ON_BankAccountOwner if available, otherwise defaults to Account Name.
BankCode String (11) The bank identifier code.
With an IBAN as bank account number, the bank code (BIC) is not required.
PaymentMethod Picklist The payment method that is preferred for paying invoices of this account.

Configuring Payment Reference Text

Depending on your organization's requirements, you specify a string that is to be written as the payment reference for SEPA payments. To do so, you configure the template field Payment Reference.

  1. Open the template to be edited.
  2. In the Payment Information section, double-click the Payment Reference field and modify the information as required.

    Modify the default value [InvoiceNo] - [InvoiceDate] as necessary.

  3. Click Save.

Info

You can use the placeholders that are available for the invoice context.