Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adjustments Implementation Guidelines SPS 2025 #141

Open
1 task done
simonmeyerm opened this issue Nov 28, 2024 · 1 comment · May be fixed by #143
Open
1 task done

Adjustments Implementation Guidelines SPS 2025 #141

simonmeyerm opened this issue Nov 28, 2024 · 1 comment · May be fixed by #143
Assignees
Labels
enhancement Issue requires improvements or additions to interface functionality
Milestone

Comments

@simonmeyerm
Copy link
Collaborator

simonmeyerm commented Nov 28, 2024

Contact Details

simon.meyer@six-group.com

Issue category

Refinement

Issue description

Changes with regard to adjustments to Swiss Payment Standards Implementation in Guidelines for Cash Management and Credit Transfer valid from November 2025

Issue reasoning

Compliance with Swiss Payment Standards as per release

Request

Cash Management - Account API

2.1 Adjustment to "Interest"
New element "Interest" can be introduced to represent an account interest statement.:

  • Level: Entry
  • Status: optional
  • Type: enum
  • Values: [INTE, WHLD, FCIN, OTHR]

2.2 Adjustments to "Account"
Already in place

2.3 Adjustments to "Status"
Not applicable

Credit Transfer - Payment API

2.1 Adjustment to "Use of address information
Use of address information has been revised. Hybrid structure will be introduced and unstructured address will be removed. In addition, the current "postalAddress" object does not comply to the standard. Therefore, i suggest the following changes:

  • Unstructured address will be removed
  • Hybrid structure will be introduced
  • Current "postalAddress" object does not comply to standards. The following elements could be added:
    • Department [Dept]
    • Sub Department [SubDept]
    • Building Name [BldgNb]
    • Floor [Flr]
    • Room [Room]
    • Town Location Name [TwnLctnNm]
    • District Name [DstrctNm]
    • Country Sub Division [CtrySubDvsn]
  • Impact on Account and Payment API

2.4.1 Adjustment to the element "Name" to 140 characters
For the element "Name", the restriction to 70 characters has been lifted. However, this restriction still applies for the payment type "S" (SEPA)
As the maxLength has already been adjusted on some objects only the following changes are required:

  • PaymentDebtor: Name is currently 70 und must be changed to 140
  • Description: Restriction for payment type SEPA is 70 characters

Proposed change

<<<<<<< Section As-Is

    PaymentStructuredOrUnstructuredAddress:
      title: Payment Structured or Unstructured Address
      description: Either structured or unstructured address must be set.
      type: object
      properties:
        structured:
          $ref: '#/components/schemas/PaymentStructuredAddress'
        unstructured:
          $ref: '#/components/schemas/PaymentUnstructuredAddress'

========

>>>>>>> Section To-Be

    accountTransactionInterest:
      title: Account Transaction Interest
      type: string
      description: Represents an account interest statement. Corresponds to the attribute _Intrst_ in SPS/ISO-20022
      enum: 
        - INTE
        - WHLD
        - FCIN
        - OTHR

-----------------------------------------------------------------------------------------

    PaymentAddress:
      title: Payment Address
      description: tbd.
      type: object
      properties:
        structured:
          $ref: '#/components/schemas/PaymentAddress'

    PaymentAddress:
      title: Address for Payments
      type: object
      description: Specifies the address details.
      required:
        - townName
        - country
      properties:
        streetName:
          type: string
          maxLength: 70
          description: The street name. Corresponds to the attribute _StrtNm_ in SPS/ISO-20022.
          example: Rue de la gare
        buildingNumber:
          type: string
          maxLength: 16
          description: The building number. Corresponds to the attribute _BldgNb_ in SPS/ISO-20022.
          example: '24'
        postCode:
          type: string
          maxLength: 16
          description: The post code. Corresponds to the attribute _PstCd_ in SPS/ISO-20022.
          example: '2501'
        townName:
          type: string
          maxLength: 35
          description: The town name. Corresponds to the attribute _TwnNm_ in SPS/ISO-20022.
          example: Biel
        country:
          type: string
          maxLength: 2
          description: The counterparty country. Corresponds to the attribute _Ctry_ in SPS/ISO-20022.
          example: CH
        addressLine1:
          type: string
          maxLength: 70
          description: Additional address information, which cannot be supplied in structured elements. Corresponds to the attribute _AdrLine_ in SPS/ISO-20022.
          example: Carribean At Keppel Bay
        addressLine2:
          type: string
          maxLength: 70
          description: Additional address information, which cannot be supplied in structured elements. Corresponds to the attribute _AdrLine_ in SPS/ISO-20022.
          example: 05-66
-----------------------------------------------------------------------------------------

    PaymentDebtor:
      title: Payment Debtor
      type: object
      description: The debtor of a payment.
      required:
        - name
        - postalAddress
      properties:
        name:
          type: string
          maxLength: 140
          description: The name of the debtor of a payment.
          example: Hans Muster

Affected API's

Both

Code of Conduct

  • I agree to follow this project's Contribution Guidelines
@svenbiellmann
Copy link
Contributor

svenbiellmann commented Dec 17, 2024

Meeting Notes 12.12.24

Update on following elements:

  • Element "interest" will be moved to the discussion with respect to harmonization
  • Unstructured address: One PaymentAddress object will encompass structured and hybrid address. There is no need to implement all additional elements
  • Thomas W. (bexio) asks if the AdressLine can be represented as array. Dominik will check.
  • Name in all objects will be extended from 70 to 140 characters.

@simonmeyerm will prepare the Pull Request which will be discussed on next meeting for discussion and approval.

@svenbiellmann svenbiellmann added enhancement Issue requires improvements or additions to interface functionality and removed new Newly submitted issue labels Dec 20, 2024
@svenbiellmann svenbiellmann added this to the v5.0 milestone Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Issue requires improvements or additions to interface functionality
Projects
None yet
3 participants