constmsg="If Copy Duplicate indicator is used in the Business Application Header, it must be identical to the Copy Duplicate indicator in the business document (if the latter is present).";
constmsg="If Copy Duplicate indicator is used in the Business Application Header, it must be identical to the Copy Duplicate indicator in the business document (if the latter is present).";
constmsg="If Copy Duplicate indicator is used in the Business Application Header, it must be identical to the Copy Duplicate indicator in the business document (if the latter is present).";
constmsg="If Copy Duplicate indicator is used in the Business Application Header, it must be identical to the Copy Duplicate indicator in the business document (if the latter is present).";
//Cross Element Complex Rule : Instructed Amount And Exchange Rate 1Rule
functionInstructedAmountAndExchangeRateRule(obj){
constmsg1="If InstructedAmount is present and the currency is different from the currency in InterbankSettlementAmount, then ExchangeRate must be present.";
constmsg2="If InstructedAmount is present and the currency is the same as the currency in InterbankSettlementAmount, then ExchangeRate is not allowed.";
constmsg3="If InstructedAmount is not present, then ExchangeRate is not allowed.";
@@ -416,3 +630,19 @@ function CBPR_Instruction_Information_TextualRule(){
...
@@ -416,3 +630,19 @@ function CBPR_Instruction_Information_TextualRule(){
constmsg="If the pacs.009 is used to settle a pacs.009 Advice, the last available occurrence (of the element Instruction For Creditor Agent/Instruction Information) preceded by /UDLC/ must be used to capture the /UDLC/ (Underlying Creditor) provided in the pacs.009 Advice.";
constmsg="If the pacs.009 is used to settle a pacs.009 Advice, the last available occurrence (of the element Instruction For Creditor Agent/Instruction Information) preceded by /UDLC/ must be used to capture the /UDLC/ (Underlying Creditor) provided in the pacs.009 Advice.";
returntrue;
returntrue;
}
}
//如果结算方式等于COVE,则指示报销代理或指示报销代理必须在场。
functionSettlementMethod_COVE(obj){
constmsg="If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or InstructingReimbursementAgent must be present.";
constmsg="If 'Priority' is used in the BAH for pacs messages, the value should be identical to the one in the “Payment Type Information/InstructionPriority” if present.";
constmsg="If 'Priority' is used in the BAH for pacs messages, the value should be identical to the one in the “Payment Type Information/InstructionPriority” if present.";
...
@@ -365,5 +578,21 @@ function CBPR_Purpose_Guideline() {
...
@@ -365,5 +578,21 @@ function CBPR_Purpose_Guideline() {
returntrue;
returntrue;
}
}
//如果结算方式等于COVE,则指示报销代理或指示报销代理必须在场。
functionSettlementMethod_COVE(obj){
constmsg="If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or InstructingReimbursementAgent must be present.";
constmsg="If 'Priority' is used in the BAH for pacs messages, the value should be identical to the one in the “Payment Type Information/InstructionPriority” if present.";
constmsg="If 'Priority' is used in the BAH for pacs messages, the value should be identical to the one in the “Payment Type Information/InstructionPriority” if present.";
...
@@ -643,6 +905,22 @@ function CBPR_RemittanceInformation_TextualRule(){
...
@@ -643,6 +905,22 @@ function CBPR_RemittanceInformation_TextualRule(){
returntrue;
returntrue;
}
}
//如果结算方式等于COVE,则指示报销代理或指示报销代理必须在场。
functionSettlementMethod_COVE(obj){
constmsg="If SettlementMethod is equal to COVE, then InstructedReimbursementAgent or InstructingReimbursementAgent must be present.";
constmsg="BAH 'From' BIC must match 'Instructing Agent' BIC, except where BAH CopyDuplicate = COPY or = CODUBAH 'To' BIC must match 'Instructed Agent' BIC, except where BAH CopyDuplicate = COPY or = CODU";
constmsg="BAH 'From' BIC must match 'Instructing Agent' BIC, except where BAH CopyDuplicate = COPY or = CODUBAH 'To' BIC must match 'Instructed Agent' BIC, except where BAH CopyDuplicate = COPY or = CODU";
<!doctype html><htmllang=""><head><metacharset="utf-8"/><metahttp-equiv="X-UA-Compatible"content="IE=edge"/><metaname="viewport"content="width=device-width,initial-scale=1"/><linkrel="icon"href="favicon.ico"/><title>ISO手工拟报</title><script defer="defer"src="js/chunk-vendors.23ee7bd5.js"></script><script defer="defer"src="js/app.c9fac77d.js"></script><script defer="defer"src="js/main.59945214.js"></script><linkhref="css/chunk-vendors.77489a8d.css"rel="stylesheet"><linkhref="css/app.d2831041.css"rel="stylesheet"></head><body><noscript><strong>We're sorry but swiftiso-editor doesn't work properly without JavaScript enabled. Please enable it to continue.</strong></noscript><divid="app"></div></body></html>
<!doctype html><htmllang=""><head><metacharset="utf-8"/><metahttp-equiv="X-UA-Compatible"content="IE=edge"/><metaname="viewport"content="width=device-width,initial-scale=1"/><linkrel="icon"href="favicon.ico"/><title>ISO手工拟报</title><script defer="defer"src="js/chunk-vendors.23ee7bd5.js"></script><script defer="defer"src="js/app.c92c0280.js"></script><script defer="defer"src="js/main.59945214.js"></script><linkhref="css/chunk-vendors.77489a8d.css"rel="stylesheet"><linkhref="css/app.d2831041.css"rel="stylesheet"></head><body><noscript><strong>We're sorry but swiftiso-editor doesn't work properly without JavaScript enabled. Please enable it to continue.</strong></noscript><divid="app"></div></body></html>
<xs:documentationsource="Definition"xml:lang="EN">Code allocated to a financial institution by the ISO 9362 Registration Authority as described in ISO 9362: 2014 - "Banking - Banking telecommunication messages - Business identifier code (BIC)".</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">Unique and unambiguous identification of a financial institution or a branch of a financial institution.</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">Unique and unambiguous identification of a financial institution, as assigned under an internationally recognised or proprietary identification scheme.</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">Contains the character set of the text-based elements used in the Business Message.</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">The sending MessagingEndpoint that has created this Business Message for the receiving MessagingEndpoint that will process this Business Message.
Note the sending MessagingEndpoint might be different from the sending address potentially contained in the transport header (as defined in the transport layer).</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">The MessagingEndpoint designated by the sending MessagingEndpoint to be the recipient who will ultimately process this Business Message.
Note the receiving MessagingEndpoint might be different from the receiving address potentially contained in the transport header (as defined in the transport layer).</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">Unambiguously identifies the Business Message to the MessagingEndpoint that has created the Business Message.</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">Specifies the business service agreed between the two MessagingEndpoints under which rules this Business Message is exchanged.
To be used when there is a choice of processing services or processing service levels.
<xs:documentationsource="Definition"xml:lang="EN">Indicates whether the message is a Copy, a Duplicate or a copy of a duplicate of a previously sent ISO 20022 Message.</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">Relative indication of the processing precedence of the message over a (set of) Business Messages with assigned priorities.</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">The Business Layer deals with Business Messages. The behaviour of the Business Messages is fully described by the Business Transaction and the structure of the Business Messages is fully described by the Message Definitions and related Message Rules, Rules and Market Practices. All of which are registered in the ISO 20022 Repository.
A single new Business Message (with its accompagnying business application header) is created - by the sending MessagingEndpoint - for each business event; that is each interaction in a Business Transaction. A Business Message adheres to the following principles:
" A Business Message (and its business application header) must not contain information about the Message Transport System or the mechanics or mechanism of message sending, transportation, or receipt.
" A Business Message must be comprehensible outside of the context of the Transport Message. That is the Business Message must not require knowledge of the Transport Message to be understood.
" A Business Message may contain headers, footers, and envelopes that are meaningful for the business. When present, they are treated as any other message content, which means that they are considered part of the Message Definition of the Business Message and as such will be part of the ISO 20022 Repository.
" A Business Message refers to Business Actors by their Name. Each instance of a Business Actor has one Name. The Business Actor must not be referred to in the Transport Layer.
Specific usage of this BusinessMessageHeader may be defined by the relevant SEG.</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">Contains the character set of the text-based elements used in the Business Message.</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">The sending MessagingEndpoint that has created this Business Message for the receiving MessagingEndpoint that will process this Business Message.
Note the sending MessagingEndpoint might be different from the sending address potentially contained in the transport header (as defined in the transport layer).</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">The MessagingEndpoint designated by the sending MessagingEndpoint to be the recipient who will ultimately process this Business Message.
Note the receiving MessagingEndpoint might be different from the receiving address potentially contained in the transport header (as defined in the transport layer).</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">Unambiguously identifies the Business Message to the MessagingEndpoint that has created the Business Message.</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">Specifies the business service agreed between the two MessagingEndpoints under which rules this Business Message is exchanged.
To be used when there is a choice of processing services or processing service levels.
<xs:documentationsource="Definition"xml:lang="EN">Specifies the market practice to which the message conforms. The market practices are a set of rules agreed between parties that restricts the usage of the messages in order to achieve better STP (Straight Through Processing) rates.
A market practice specification may also extend the underlying message specification by using extensions or supplementary data of this underlying message.</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">Indicates whether the message is a Copy, a Duplicate or a copy of a duplicate of a previously sent ISO 20022 Message.</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">Flag indicating if the Business Message exchanged between the MessagingEndpoints is possibly a duplicate.
If the receiving MessagingEndpoint did not receive the original, then this Business Message should be processed as if it were the original.
If the receiving MessagingEndpoint did receive the original, then it should perform necessary actions to avoid processing this Business Message again.
This will guarantee business idempotent behaviour.
NOTE: this is named "PossResend" in FIX - this is an application level resend not a network level retransmission.</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">Relative indication of the processing precedence of the message over a (set of) Business Messages with assigned priorities.</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">Identifies the implementation specification to which the ISO 20022 message conforms.</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">Name of the implementation specification registry in which the implementation specification of the ISO 20022 message is maintained.
<xs:documentationsource="Definition"xml:lang="EN">Identifier which unambiguously identifies, within the implementation specification registry, the implementation specification to which the ISO 20022 message is compliant. This can be done via a URN. It can also contain a version number or date.
For instance, "2018-01-01 – Version 2" or "urn:uuid:6e8bc430-9c3a-11d9-9669-0800200c9a66".</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">Legal Entity Identifier is a code allocated to a party as described in ISO 17442 "Financial Services - Legal Entity Identifier (LEI)".</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">codelist containing the names of the UNICODE code block name as specified on http://unicode.org/Public/UNIDATA/Blocks.txt.</xs:documentation>
<xs:documentationsource="Definition"xml:lang="EN">35 Character Text restricted to the Usage Identifier Pattern. That is, it must be a lower case string of maximum 35 characters containing the following elements separated by period
1. Short issuer organisation (Mandatory)
2. Business context (Mandatory and Repetitive)
3. Version (Mandatory)
Each element must be an alphanumeric string of maximum 10 characters except the Version that must be exactly 2 digits.</xs:documentation>