Maintenance Change Request s3

RA Id: CR0165

CHANGE REQUEST

FOR THE UPDATE OF ISO 20022 FINANCIAL REPOSITORY ITEMS

A. Origin of the request: A.1 Submitter: Tieto A.2 Contact person: Ulrika Sjödahl, [email protected], +46104818037 Pirkko Vedenpää, [email protected], +358207257525 A.1 Sponsor: Tieto Corporation

B. Related messages: tsin.004.001.01 (FinancialInvoice)

C. Description of the change request: PhneNb (PhoneNumber), MobNb (MobileNumber) and FaxNb (FaxNumber) regular expression is now too tight. Make it simple as Max35Text. D. Purpose of the change: In a lot of the standard formats the format of phone number, mobile number and fax number is unstructured. With this very tight structure it is impossible to implement the unstructured numbers into this structure.

E. Urgency of the request: Normal.

F. Business examples: There are a lot of formats where the phone numbers and equal are handled sort of unstructured. E.g. in EDIFACT there are no rules, character string with 512 characters maximum. In Sweden the recommendation is as follows: “Preceded by the country code without plus sign. Area Code is displayed without leading zero, only numerical characters, exchanged in unedited form. Leading zeros are significant here!” maximum 15 characters. In Svefaktura the recommendation is as follows: “Contact numbers are to be given as an unedited character string, i.e. without space character, hyphen or other editing characters. They may be given in either of two formats:  As a national number, i.e. with a national prefix starting by zero. Example: 084527000

08a17edeb12dcb27631e18e27537364d.doc Produced by TIETO on 12 Mar 2012 Page 1 RA Id: CR0165

 As an international number, starting with a leading plus sign and country number, followed by the national number without its leading zero. Example: +4684527000” In CEN/BII Invoicing BiiColl004 this type of information is defined as TextType. In UBL 2.0 Invoice this type of information is defined as TextType. BGC Invoice in Sweden also uses plain text for this type of information.

G. SEG recommendation: This section will be completed in due time by the SEG(s) in charge of the related ISO 20022 messages.

Consider Timing - Next yearly cycle: 2012/2013 (the change will be considered for implementation in the yearly maintenance cycle which starts in 2012 and completes with the publication of new message versions in the spring of 2013) - At the occasion of the next maintenance of the messages (the change will be considered for implementation, but does not justify maintenance of the messages in its own right – will be pending until more critical change requests are received for the messages) - Urgent unscheduled (the change justifies an urgent implementation outside of the normal yearly cycle) - Other timing:

Comments:

Reject Reason for rejection:

08a17edeb12dcb27631e18e27537364d.doc Produced by TIETO on 12 Mar 2012 Page 2