Skip to content

Configuring Bank Statement Import

Banks can provide end-of-day statement files (CAMT.053 format, as individual XML files or bundled in ZIP archives) outside the EBICS channel. JustOn Cash Management can import these files, storing the information in bank statements and bank statement items for further processing, as described in Bank Statement Import.

Configuring the bank statement import involves the following tasks:

Enabling Bank Account for Bank Statement Import

Bank accounts intended for the bank statement import must use the access method File Import.

Note

You cannot use the same bank account for both the EBICS-based data exchange and the bank statement import.

To enable a bank account for file import:

  1. Open an existing Bank Account record or create a new one.
  2. Click next to the Access Method field, then select File Import.

  3. Click Save.

    This enables the selected bank account for the bank statement import (and disables the EBICS-based access).

Access method File Import not available?

If you have upgraded JustOn Cash Management from a pre-1.75 version, you may have to manually add the value File Import in the Access Method picklist of the Bank Account object. To do so:

  1. Click to enter Setup, then navigate to the object management settings of the Bank Account object (JPAY1__BankAccount__c).
  2. Click Fields & Relationships.
  3. Click the name of the Access Method field.

  4. In the Values section, click New.

    Add the new access method File Import.

  5. Click Save.

    This saves the new access method File Import for bank accounts.

Enabling Bank Statement Import

For users to be able to import bank statement files (XML or ZIP), you must add the Import Files button to the Bank Statements list view.

  1. Navigate to the object management settings of the Bank Statement object.
  2. Click List View Button Layout.
  3. In the List View row, click , then select Edit.

  4. Under Custom Buttons, move Import Files to the Selected Buttons column.

    column_select

  5. Click Save.

    This adds the button Import Files to the Bank Statements list view, enabling users to import bank statement files.

Enabling Bank Statement Import From Salesforce Files

JustOn Cash Management supports two channels for importing CAMT.053 files:

To enable the Salesforce Files library from which to import bank statements:

  1. Click to access the App Launcher, and select Setup Cash Management.

  2. Open the Global Configuration tab.

    Users who intend to access the global configuration must be assigned the System Administrator profile and explicitly allowed accessing the Global Configuration dialog.

  3. Click Edit.

    This launches a screen flow that shows the global configuration input fields.

  4. In the Bank Statement Download section, select the Import From Salesforce Files checkbox.

  5. Click Save to save your settings, then Finish to complete the screen flow.

    This creates the library Bank Documents - Import, enabling the bank statement import from Salesforce Files for your org.

Enabling Structured Bank Document Storage

JustOn Cash Management imports CAMT.053 statements as individual XML files or from ZIP archives. It can store the processed files in Salesforce Files in a dedicated library/folder structure grouped by BIC and IBAN.

For details on how to enable the structured bank data storage for your org, see Globally Enabling Structured Bank Document Storage.

Configuring Automatic Bank Statement Import

JustOn Cash Management can automatically import bank statement files from the inbox library in Salesforce Files on a regular basis.

To this end, JustOn Cash Management provides the dedicated Apex class BankStatementFileImportJob, which is to be scheduled using the standard Salesforce Schedule Apex functionality.

The automatic bank statement import requires the following settings:

Note

The scheduled job runs with the permissions of the user who has scheduled it. This user must have read and write access to the library Bank Documents - Import.

If the user has no access to the library, the job does not find any files. It then finishes without importing anything and without displaying an error message.

  1. Click to enter Setup, then navigate to Custom Code > Apex Classes.
  2. Click Schedule Apex on top of the list.

  3. Specify the details as required.

    • Job Name, like Bank Statement File Import Job
    • Apex Class: BankStatementFileImportJob

    • Frequency: Weekly or Monthly (with an according day of week or day of month setting)

      Choose the interval according to how often your bank or your integration places new statement files in the inbox library – usually daily (Weekly with every day selected).

    • Start

    • End

      Required, so if you want it to run virtually forever, select a date far in the future.

    • Preferred Start Time

      Select a time after the new statement files are usually available in the inbox library.

  4. Click Save.

    This sets up the bank statement import to be executed automatically at the specified time.

Processing specifics

On each run, the scheduled job processes the files in the library Bank Documents - Import as follows:

  • It considers all XML and ZIP files with a maximum size of 12 MB. Other files are ignored and remain in the inbox library.
  • If the inbox library holds no such files, the job ends without starting an import.
  • Otherwise, it starts the import as an asynchronous job, which creates the bank statements and bank statement items and executes the payment matching, just like the manual import.
  • Successfully processed files are removed from the inbox library and stored as described in Import Structure.
  • Files that cannot be processed remain in the inbox library, and a warning listing the affected files and the errors is added to the job log. These files are processed again on each subsequent run, so fix the cause or remove the files from the inbox library. For details, see Import Errors.
  • Statements of existing bank accounts with a different access method (like EBICS) are skipped, and a warning is added to the job log.

A single run can process a maximum of 200 files. If the inbox library holds more than 200 XML and ZIP files, the import is not started, and no error message is displayed. Make sure that the inbox library does not accumulate more files, for example by choosing a sufficiently short interval.

Info

As an alternative to Schedule Apex, you can start the import from Salesforce Files using a flow, for example a schedule-triggered flow. To do so, JustOn Cash Management provides the Apex action Execute import bank statements.

Controlling Bank Account Creation on Data Retrieval

For IBANs that do not yet exist in Salesforce, JustOn Cash Management automatically creates new Bank Account records during the bank statement import by default. If required, you can disable this behavior to prevent the automatic creation of new bank accounts.

For details on how to control the automatic bank account creation in your org, see Controlling Bank Account Creation on Data Retrieval.

Automatic bank account creation and structured file storage

For new bank accounts created automatically on data retrieval, no library/folder structure will be created during the data retrieval process. Processed files related to new bank accounts detected on import will be stored under the users' Owned by Me.

To create the library/folder structure, disable structured file storage and re-enable it once the new bank accounts are available.