action.skip

JustOn Cash Management Release Notes

Info

We regularly deliver updates to bring new features, improvements and fixes to JustOn Cash Management.

When upgrading from previously installed versions, make sure to consider the upgrade guidelines.

1.42

2024-02-07

Preview release

1.41

2024-01-31

  • Fixed entry synchronization on settlement: correctly sets payment date (PLAN-567)
  • Fixed SEPA payment run: fetches bank account from business entity for entries w/o requested bank account (PLAN-569)
  • Fixed SEPA payment run: ignores disabled bank account credentials (PLAN-575)
  • Added platform support for XRechnung 3.0.1 (PLAN-273)

2024-01-16

  • Removed restriction from picklists (PLAN-565)

1.40

2024-01-15

  • Enhanced settlement logic: added support for multiple matches (PLAN-322)

    When upgrading from a previous version, you must add the value Unmatched, multiple results to the Matching Result picklist of the Payment object in order to make the payment matching operational (see Enabling Payment Matching Results).

  • Improved error reporting: better integration of progress dialog with error reports (PLAN-435)

  • Fixed logging: prevent log overflow due of payment matching misconfiguration (PLAN-460)
  • Fixed SOQL queries: correct character escaping (PLAN-547)

1.39

2023-12-20

  • Improved EBICS-related error reporting: error reports now include response-body and response-status (PLAN-538)
  • Improved bank data retrieval: copies reference from bank statement items to payment-reference in payments (PLAN-545)
  • Improved EBICS-related error reporting: error reports now include technical-return-code, error-class and subgroup (PLAN-546)
  • Fixed bank data retrieval: removed deprecated field Payment.Amount (PLAN-550)

2023-12-12

  • Added support for automatically settling entries via API (PLAN-318)

  • Added support for handling credit balances and for applying credit balance strategy on entry cancellation (PLAN-326)

  • Extended JustOn Cash Management API: added support for additional fields on entry creation (PLAN-482)
  • Improved integration with JustOn Billing & Invoice Management: added support for invoice-entry assignment keys (PLAN-457)
  • Renamed application label: Salesforce application label correctly shows JustOn Cash Management (PLAN-525)
  • Fixed URL handling for Hyperforce (PLAN-514)
  • Fixed end-to-end ID matching: correctly considers chargebacks on bank data retrieval (PLAN-529)
  • Removed deprecated elements (PLAN-531):

    • Bank Account field from Refund object
    • Amount field from Payment object
    • picklist values Open, Pending, Reversed from Status field on Refund object

1.38

2023-12-07

  • Fixed end-to-end ID matching: correctly considers chargebacks on bank data retrieval (PLAN-529)

2023-11-16

  • Stable release for 1.37 preview release
  • Added support for SEPA payment run (PLAN-124)
  • Added support for canceling entries (PLAN-297)

    When upgrading from a previous version, you may have to add the button Cancel to the Entry detail view manually (see Enabling Entry Cancellation).

  • Improved naming of amount values on entries, entry items and payments (PLAN-145)

  • Fixed end-to-end ID matching: correctly considers original bank account (PLAN-447)
  • Fixed manual settlement: correctly involves open entries only (PLAN-456)

1.37

2023-11-15

Preview release

  • Added support for SEPA payment run (PLAN-124)
  • Added support for canceling entries (PLAN-297)

1.36

2023-10-24

  • Fixed bank access management and bank statement download: correct permission assignment (PLAN-432)

1.35

2023-10-20

1.34

2023-09-25

Preview release

  • Reworked EBICS bank access (PLAN-134)

1.33

2023-09-07

2023-08-31

  • Stable release for 1.32 preview release

1.32

2023-08-31

Preview release

  • Added support for refund handling via Adyen (PLAN-130)
  • Added support for payment run (PLAN-133)
  • Fixed bank data retrieval: payment conversion date uses correct timestamp (PLAN-156)
  • Improved SEPA direct debit/credit transfer creation: automatically uses first active payment instrument with valid money flow restriction (PLAN-246)
  • Improved error report handling: creates error report file if message exceeds field length (PLAN-255)

    When upgrading from a previous version, you must add the Files related list to the Error Report detail view manually (see Enabling Large Error Reports).

  • Fixed payment matching: considers only end-to-end IDs created by JustOn Cash Management (PLAN-257)

  • Fixed payment page behavior: shows balanced entries after successful payment (PLAN-276)
  • Fixed error handling: Salesforce-related errors (timeout, limit reached, authorization missing, validation error) will be part of the Salesforce error report (PLAN-285)
  • Fixed bank data retrieval: correctly handles queries for large numbers of bank statement items (PLAN-300)

1.31

2023-08-03

  • Added EBICS support for Sparkasse Hannover (PAY-708) and Sparkasse Leipzig (PAY-888)
  • Fixed payment link creation: no payment link with invalid entries (PAY-884)
  • Fixed error report handling: creates error report file if message exceeds field length (BASE-466)

2023-07-13

  • Fixed payment page: added missing fonts (PAY-883)

2023-07-06

  • Fixed banking data retrieval: correctly processes bank statements with proprietary bank account identifiers (PAY-882)

1.30

2023-07-04

  • Added EBICS support for VR-Bank Memmingen (PAY-873) and Sparkasse Schwaben-Bodensee (PAY-874)
  • Extended job framework to support user interactions (PAY-871)
  • Reworked SEPA XML creation: implemented Unicode character conversion (PAY-760)

    Unless specifically agreed with the bank, JustOn Cash Management uses the basic character set defined by the European Payment Council when creating SEPA payment orders. For details, see SEPA Requirements for an Extended Character Set (UNICODE Subset) - Best Practices.

  • Removed support for EBICS 2.5 (PAY-863)

  • Fixed banking data retrieval: processes bank statements with proprietary bank account identifiers (PAY-861)
  • Fixed automatic settlement: correctly handles business entity (PAY-869)
  • Fixed banking data retrieval: correctly handles amount values on bulk booking breakdown (PAY-872)
  • Fixed SEPA direct debit/credit transfer: checks for correct payment instrument assignment (PAY-875)
  • Fixed logging behavior for data mapping on payment matching: changed log level (→ debug) to reduce the log file size (PAY-879)
  • Fixed JustOn Configurator package Payment Matching Configurations (ETC-136)

1.29

2023-06-15

  • Enhanced settlement logic: displays correct matching result and matching date after manual settlement (PAY-855)
  • Added standard list views for relevant objects (PAY-856)
  • Fixed manual settlement: correctly re-associates payments to entries (PAY-857)
  • Corrected button translations in global configuration dialog (PAY-846)
  • Removed deprecated fields from package: JPAY1__AssignedAmount__c from Payment, JPAY1__LastCaptureAmount__c and JPAY1__LastSuccessfulCaptureAmount__c from Payment Instrument (PAY-842)

    When upgrading from a previous version, these fields remain in your org with the label Deprecated. If you no longer need them, you can delete the fields manually.

1.28

2023-05-30

  • Added support for handling banking data with proprietary bank account identifier instead of IBAN (PAY-824)
  • Added support for retrieving banking data from camt.053.001.04 (PAY-851)
  • Fixed payment matching: correctly supports chargebacks (PAY-794)

    When upgrading from a previous version, you must add the value Payment Id matched to the Matching Result picklist of the Payment object manually in order to make the payment matching operational (see Enabling Payment Matching Results).

  • Corrected amount value names on payment page (PAY-844)

  • Corrected settlement-related wording in UI (PAY-853)
  • Fixed manual settlement: prevent error when re-associating payment to different entry (PAY-854)

1.27

2023-05-26

  • no relevant changes

1.26

2023-05-15

  • Reworked settlement business logic (PAY-713, PAY-734)
  • Reworked manual settlement: applies new business logic (PAY-803)
  • Added EBICS support for VR-Bank Starnberg-Herrsching-Landsberg eG (PAY-823)
  • Fixed payment matching: correctly supports bank statement items w/o end-to-end ID (PAY-805), correctly supports older bank statement items w/o chargeback-related fields (PAY-815)
  • Fixed settlement: prevents timeout to complete settlement after payment matching (PAY-814)

1.25

2023-04-18

  • Added EBICS support for Volksbank Mittlerer Neckar eG (PAY-811)
  • Fixed payment matching: correctly handles bank statement items with chargebacks (PAY-813)

2023-04-11

  • Added support for chargeback handling on bank statement retrieval: reworked Bank Statement Item implementation to support payment charges/interests, added relevant amount fields (PAY-798)

    When upgrading from a previous version, you may have to add the fields Cumulated Charges, Effective Amount, Instructed Amount, Transaction Amount to the page layout of the Bank Statement Item object (see Enabling Chargeback Information Display).

  • Added support for case-sensitive search on payment matching (Entry by statement number and Account by account number reference) (PAY-687)

  • Improved job status display: shows additional job messages in Lightning UI (PAY-801)
  • Added EBICS support for DZ Bank AG (PAY-802)
  • Enhanced job status information and error reporting (PAY-740, PAY-806, PAY-810)
  • Improved banking data retrieval: Raw Entry on bank statement items includes the relevant transaction details only (PAY-427)
  • Fixed payment matching: correctly handles business entity in Payment records (PAY-807)

1.24

2023-03-06

  • Added support for SEPA batch bookings (PAY-256)

    When upgrading from a previous version, you may have to add the fields SEPA Direct Debit Batch Booking, SEPA Credit Transfer Batch Booking and Initial Payment Status to the page layout of the Bank Account object (see Enabling SEPA Batch Booking Control).

  • Added support for considering custom Entry fields on payment matching (Entry by custom field) (PAY-757)

    When upgrading from a previous version, you may have to add the value FindEntryByCustomField to the Template picklist of the Matching Configuration object manually in order to enable the new matching configuration type (see Enabling Matching Configuration Search Templates).

  • Added support for storing the last capture amount and date on payment instruments (PAY-722)

  • Added EBICS support for Volksbank Thüringen Mitte (PAY-796) and Oberbank AG (PAY-797)
  • Fixed global configuration: correctly displays editing view (PAY-792)

1.23

2023-02-10

1.22

2023-01-18

  • Added support for Adyen payment service provider (PAY-674)
  • Added support for managing tenant-specific global settings (platform integration user, tenant URI alias) (PAY-484)
  • Added support for validating IBANs on saving records (PAY-673)
  • Added EBICS support for Luzerner Kantonalbank (PAY-812)
  • Renamed test payment provider JustOn Test Payments (PAY-705)

1.21

2023-01-04

  • Reworked SEPA chargeback handling: sets status detail field (PAY-694)
  • Added EBICS support for Berliner Sparkasse (PAY-727) and Sparkasse Hannover (PAY-708)
  • Fixed Bank Statement Item object: added missing fields (PAY-668)
  • Fixed search template implementation: added prefix substitution (PAY-685)
  • Fixed payment creation: correctly sets status when created from bank statement item (PAY-688)
  • Fixed bank initialization dialog: displays available banks sorted by BIC (PAY-698)
  • Fixed SEPA credit transfer: uses correct XSD to handles payment instrument without BIC (PAY-706)
  • Fixed EBICS bank initialization: ignores bank accounts without IBAN (PAY-709)

2022-11-28

  • Added support for storing detailed information on payment statuses (PAY-693)

    When upgrading from a previous version, you can add the field Status Details manually to the page layout of the Payment object. Note that this is not required for the proper operation of JustOn Cash Management but rather a convenience option for your users.

  • Added Bank Statement Item fields Payment Conversion Date, Payment Conversion and Matching Result to hold payment matching results (PAY-668)

1.20

2022-11-03

  • Modified IBAN verification: added checksum algorithm (BASE-351)
  • Fixed EBICS key renewal (PAY-7)
  • Fixed bank statement download with batch bookings (PAY-663)

2022-10-20

  • Fixed bank statement download/payment matching for large numbers of transactions (PAY-664)

2022-10-19

  • Added support for renewing EBICS keys ("key rolling", PAY-7)

2022-10-18

  • Fixed Salesforce API integration (PAY-650)
  • Fixed payment link creation (PAY-665)

2022-10-17

  • Fixed PSP integration: correctly works with external systems (PAY-655)
  • Fixed PSP integration: correctly updates payments (PAY-662)

2022-10-10

  • Optimized webhook handler logging to prevent log outage (PAY-660)

2022-10-07

  • Added support for automatic payment matching by (configurable) data comparison (PAY-522)
  • Removed New button from bank statement and bank statement item list views (PAY-616)
  • Added lookup filter for requested payment instrument on entry (PAY-630)

1.19

2022-09-13

  • Added support for cancelling previously issued payments when creating direct debit orders or credit transfer orders (PAY-452)

    When upgrading from a previous version, you may have to add the status Canceled to the Status picklist of the Payment object manually in order to make the payment cancellation operational (see Enabling Payment Statuses).

1.18

2022-09-07

  • Fixed bank statement retrieval: added fallback support for duplicate IDs (account servicer references, AcctSvcrRef in SEPA CAMT.053) (PAY-639)

2022-09-01

  • Fixed Salesforce data retrieval: correctly handles large numbers of records (PAY-636)
  • Reworked job handling: job records include Salesforce API error information (PAY-637)

2022-08-30

  • Fixed EBICS schema validation: account holder not mandatory in HTD response (PAY-634)
  • Fixed EBICS initialization: user name visible in INI/HIA PDF (PAY-632)
  • Added relevant EBICS 3.0.2 changes (PAY-633)

2022-08-25

  • Added fallback support for inappropriate bank public key encoding (BankPubKeyDigests element in EBICS 3.0) (PAY-618)
  • Fixed payment instrument behavior: backward compatibility for Money Flow Incoming and Money Flow Outgoing fields (PAY-628)

2022-08-10

  • Added support for credit transfer (PAY-560)

    When upgrading from a previous version, you may have to add the button EBICS Credit Transfer to the Entry list view manually (see Enabling Credit Transfer).

  • Added Payment Instrument fields Money Flow Incoming and Money Flow Outgoing to explicitly allow or restrict incoming or outgoing money flow (PAY-571)

  • Fixed entry status modification: clears payment date if status is set Open (PAY-607)

1.17

2022-07-04

  • Renamed app into JustOn Cash Management (PAY-551)
  • Added support for manual settlement via external service (PAY-603)
  • Added support for creating entries and getting payment links via API (PAY-513)
  • Added support for Mollie payment service provider (PAY-239)
  • Fixed Payment data model: payment ID no longer mandatory (PAY-609)

    When upgrading from a previous version, you may have to manually deactivate the validation rule PaymentID_CheckBlanks on the payment object (see Activate Validation Rules in the Salesforce Help).

1.16

2022-05-09

  • Added button for manually creating payment link (PAY-569)
  • Added status Canceled to Payment object (PAY-570)
  • Fixed payment provider configuration flow

1.15

2022-05-04

  • Fixed manual settlement flow

1.14

2022-05-03

  • Added generic payment backend, milestone 1 (PAY-227, PAY-527, PAY-456, PAY-443, PAY-411, PAY-460, PAY-513)
  • Added generic payment provider setup, milestone 1 (PAY-464, PAY-467, PAY-468, PAY-466, PAY-469)
  • Added support for customizing payment page texts (PAY-504)
  • Added support for CMS features on payment page (PAY-483)
  • Added support for manually settling entries, milestone 1 (PAY-459)

1.13

2022-02 01

  • Fixed job polling (PAY-367)

1.12

2022-01-31

  • no relevant changes

1.11

2022-01-17

  • Added Job field External Process Id to record the EBICS order ID with direct debit operations (PAY-325)
  • Added Bank Statement Item field Full Reference to also hold reference texts with more than 255 characters (PAY-397)
  • Added Files list to Job to hold EBICS XML files (PAY-346)

1.10

2021-12-08

  • Added chargeback-relevant fields to Bank Statement Item object (PAY-444)

1.9

2021-11-16

  • Added icon to Job tab (PAY-379)
  • Added status Failed to Payment object (PAY-388)
  • Fixed direct debit: correct filter handling (PAY-426)

1.8

2021-10-18

  • Fixed direct debit flow: un-protect custom label (PAY-409)

1.7

2021-10-14

  • Added status Pending to Payment object (PAY-374)
  • Introduced Job data model (PAY-375)
  • Added support for mass direct debit (PAY-384)

    Requires a remote site setting for your Salesforce instance URL.

  • Added support for identifying data retrieval gaps (using the BankStatement.SequenceNumber field) (PAY-386)

  • Modified BankAccount.BIC field to be no longer mandatory (PAY-387)

1.5

2021-09-09

  • Added SEPA list view on entries (PAY-357)
  • Fixed callout handling in managed package context (PAY-361)

1.4

2021-09-07

  • Improved error handling for direct debit (PAY-348)
  • Fixed EBICS direct debit flow (PAY-355)

1.3

2021-08-04

  • Fixed authorization configuration (PAY-330)

1.2

2021-08-03

  • Added support for creating EBICS direct debit orders (PAY-226)
  • Enhanced Entry and Payment data models (PAY-282)

1.1

2021-05-17

  • Added Entry and Payment data models (PAY-175)
  • Added Payment Provider data model (PAY-230)

1.0

2021-02-11

  • Initial release
  • Support for managing and validating bank access
  • Support for retrieving and managing bank statements