差分

このページの2つのバージョン間の差分を表示します。

--- faq_en [2025/11/28 14:49]
crednex
+++ faq_en [2026/08/20 10:48] (現在)
crednex [Functions]
@@ 行 1: / 行 1: @@
 ===== FAQ =====
-==== Changes from the Current Platform ====
+==== Changes from the Legacy Platform ====
 === Q. Are there any changes from the current ETF creation/redemption platform? ===
-=== A. The changes are summarized below. ===
+=== A. The changes are summarized below.(bolded text: latest updates) ===
 == New features ==
-  * **Application to approval operation via API: The operation for application via API is available for AP and MM. The operation for approval via API is available for AP and AM. Please refer to the API Specification for details. (December 1, 2025: Added "AM")**
+  * Application to approval operation via API: The operation for application via API is available for AP and MM. The operation for approval via API is available for AP and AM. Please refer to the API Specification for details. (December 1, 2025: Added "AM")
-  * **Information acquisition via API: AP,MM and AM can acquire various types of information via API. Please refer to the API Specification for details. (December 1, 2025: Added "AM")**
+  * Information acquisition via API: AP,MM and AM can acquire various types of information via API. Please refer to the API Specification for details. (December 1, 2025: Added "AM")
   * Addition of cancellation request flow: AP(prop-desk) and MM can request cancellation of applications.
   * Reference and acquisition of the Issue Master: Enables file output and reference on screen of Issue Master.
@@ 行 15: / 行 15: @@
   * Application operation to AP by MM on CredNex: Commonization of application flow between MM and AP.
   * Discontinuation of CSV batch registration: Discontinued batch registration of applications using batch registration files; CredNex newly enables application registration using API.
-  * **PCF registration for cash ETFs abolished: PCF registration for cash ETFs  is abolished. Consequently, PCF designation is no longer possible when applying for cash ETFs. (Added on December 1, 2025)**
+  * PCF registration for cash ETFs abolished: PCF registration for cash ETFs  is abolished. Consequently, PCF designation is no longer possible when applying for cash ETFs. (Added on December 1, 2025)
-  * **The fields “Optional Input Field Name 1” through “Optional Input Field Name 5” and “Optional Input Field Content 1” through “Optional Input Field Content 4” are consolidated into the “Optional Input Field” (referred to as the “custom” field in the API), allowing for a maximum of 9 entries. Note that optional input fields are only available for entry on issues which the AM has enabled their use. (Added on December 1, 2025)**
+  * The fields “Optional Input Field Name 1” through “Optional Input Field Name 5” and “Optional Input Field Content 1” through “Optional Input Field Content 4” are consolidated into the “Optional Input Field” (referred to as the “custom” field in the API), allowing for a maximum of 9 entries. Note that optional input fields are only available for entry on issues which the AM has enabled their use. (Added on December 1, 2025)
 == Changes in workflow (see status definition document for details) ==
@@ 行 34: / 行 34: @@
   * Issue master file
     * Time that can be specified in the application time limit is only between 7:30 and 17:00 (added on June 10, 2025)
-  * **Statement file (cash ETFs/in-kind ETFs) (December 1, 2025: Added “in-kind ETFs”)**
+  * Statement file (cash ETFs/in-kind ETFs) (December 1, 2025: Added “in-kind ETFs”)
     * None in particular
 == Changes in output files (see each file design document for details) ==
   * Common to all files
-    * Change file name
+    * Change file name (including zip file name)
     * Changed character code to “UTF-8 with BOM”: Can be viewed without garbled characters in Excel
   * Blackout dates
@@ 行 47: / 行 47: @@
     * Item “User ID” is changed to blank.
     * <del>Item “Approximate number of units” is changed to blank for cash ETFs</del> (deleted on July 15, 2025)
-    * **Change the names of the fields “Optional Input Field Name 1” to “Optional Input Field Name 5” and “Optional Input Field Content 1” to “Optional Input Field Content 4”. Rename them to “Optional Input Field 1” to “Optional Input Field 9”. (Added on December 1, 2025)**
+    * Change the names of the fields “Optional Input Field Name 1” to “Optional Input Field Name 5” and “Optional Input Field Content 1” to “Optional Input Field Content 4”. Rename them to “Optional Input Field 1” to “Optional Input Field 9”. (Added on December 1, 2025)
-  * **Statement file (cash ETFs/in-kind ETFs) (December 1, 2025: Added “in-kind ETFs”)**
+    * **Change the number of digits for item “Approximate number of units” from 20 digits to 15 digits (Added on March 5, 2026)**
+    * **Change the number of digits for item “DVP settlement price” from 12 digits to 19 digits (Added on March 5, 2026)**
+  * Statement file (cash ETFs/in-kind ETFs) (December 1, 2025: Added “in-kind ETFs”)
     * Changed the folder structure of the calculation sheet zip file
-    * **Change the “User ID” field to blank (Added on December 1, 2025)**
+    * Change the “User ID” field to blank (Added on December 1, 2025)
+    * **Change the number of digits for item “DVP settlement price” from 12 digits to 19 digits (Added on March 5, 2026)**
   * PCF file
-    * **Change the “Fund Code” field to blank (Added on December 1, 2025)**
+    * Change the “Fund Code” field to blank (Added on December 1, 2025)
-    * **Change the “User ID” field to blank (Added on December 1, 2025)**
+    * Change the “User ID” field to blank (Added on December 1, 2025)
 == Changing permissions (for details, refer to the operation manual) ==
@@ 行 60: / 行 63: @@
 \\
-===== In Preparation for Full Go-Live =====
+==== Functions ====
-=== Q. Please provide the schedule for the full go-live. ===
-=== A. The following schedule is planned. ===
-Early December 2025: Specification documents (API/file specifications) released\\
-Early 2026: User briefing sessions\\
-Early February: Application acceptance begins\\
-February: User test details released\\
-March: User manual (reflecting features for full go-live) released\\
-March–May: User test period (test environment)\\
-May–June: User test period (holiday-test, production environment)\\
-June: Production operation begins; new applications on current ETF creation and redemption platform cease\\
-\\
-=== Q. What procedures are required for full operation? ===
-=== A. Details regarding the application procedures will be provided at a briefing session scheduled for early 2026. ===
-\\
-=== Q. What tests should users perform in preparation for the full go-live? ===
-=== A. Details regarding the user test will be announced at the briefing session scheduled for early 2026. ===
-\\
-=== Q. What tasks are required on the user side during the migration process for the full go-live? ===
-=== A. Details regarding the migration plan will be announced at the briefing session scheduled for early 2026. ===
-\\
-===== Functions =====
 === Q. Can I change my login password? ===
-=== A. Currently, CredNex does not support changing login passwords, but we plan to release a password change feature. For details, please refer to our release plan. ===
+=== A. You can change your password. For details, please refer to the CredNex operation manual. ===
-[[release_plan_and_notes|リリースノート / Release Notes]]
 \\
@@ 行 117: / 行 88: @@
 === Q. Is it possible to perform both API and GUI operations? ===
-=== A. Yes, it is possible to use both the API and GUI. For details, please refer to the application procedures. Please note that MM users cannot currently use the GUI. ===
+=== A. Yes, it is possible to use both the API and GUI. To use the API, an API usage application is required. For details, please refer to the application procedures. Please note that MM users cannot currently use the GUI. ===
 {{ :wiki:application_procedures_on_crednex.pdf |Application procedures}}
@@ 行 139: / 行 110: @@
 === Q. Is AP approval required even when AP performs the application registration? ===
-=== A. Whether you use the GUI or API, application approval is required. ===
+=== A. Whether you use the GUI or API, application approval for AP is required. ===
 \\
@@ 行 145: / 行 116: @@
 === Q. What is a cancellation request? ===
 === A. This feature allows applicants to request cancellation of an application they have already registered on CredNex. ===
-If you wish to cancel a registered application, you can perform the cancellation request operation if the status of the application is “Application in Process” or “Approved.”\\
+If you wish to cancel a registered application, you can perform the cancellation request operation if the status of the application is “Application in Process AP” or “Accepted.”\\
-If you perform a cancellation request for an application with the “Application in Process” status, the status will immediately change to “Cancelled” without requiring approval from the AP or AM.\\
+If you perform a cancellation request for an application with the “Application in Process AP” status, the status will immediately change to “Canceled” without requiring approval from the AP or AM.\\
-If you submit a cancellation request for an application with the status “Approved,” a request for approval of the cancellation will be sent to both AP and AM. The application will only transition to the “Cancelled” status if both AP and AM approve the cancellation. If either AP or AM rejects the request, the application will return to the “Accepted” status.\\
+If you submit a cancellation request for an application with the status “Accepted,” a request for approval of the cancellation will be sent to both AP and AM. The application will only transition to the “Canceled” status if both AP and AM approve the cancellation. If either AP or AM rejects the request, the application will return to the “Accepted” status.\\
-For procedures regarding application cancellations, please refer to the CredNex Business Procedures, Section 2: “Business Flow Using CredNex,” Subsection (7): “Application Cancellation.”\\
+For procedures regarding application cancellations, please refer to the CredNex Operational Procedures, Section 2: “Business Flow Using CredNex,” Subsection (7): “Application Cancellation.”\\
 Please note that registering or canceling application information without the intention of
 completing the creation/redemption, or doing so arbitrarily, is prohibited under the Terms of Use. Please refrain from engaging in such acts.
@@ 行 165: / 行 136: @@
 \\
-===== Permissions =====
+==== Permissions ====
 === Q. What permission settings are available for each user ID? ===
@@ 行 178: / 行 149: @@
-===== Others =====
+==== Others ====
 === Q. What are CredNex operating hours? ===
@@ 行 186: / 行 157: @@
 === Q. What is CredNex pricing structure? ===
-=== A. For the usage fees currently scheduled, please refer to pages 19 to 22 of the briefing materials presented at the February 2025 briefing session. Please note that the fee structure outlined in the above materials is subject to change in the future.  ===
+=== A. Please refer to the Terms of Service for the pricing structure. Please note that the ETF Creation/Redemption Platform previously provided by JSCC (the "Legacy Platform") ceased operations at the end of June 2026. However, fees related to Clearing Participants and other relevant entities, including Special ETF Clearing Participants and Registered ETF Trustee Banks, will continue to be billed by JSCC. ===
+{{ :wiki:terms_of_service_20250801.pdf |Terms of Service}}
 \\
 === Q. What is the payment procedure for service fees at CredNex? ===
-=== A. We plan to provide details at a briefing session to be held in early 2026. ===
+=== A. Please refer to page 33 of the briefing materials for the full go-live conducted in January 2026. ===
+{{ : |CredNex Briefing Session for June 2026 System Integration (TBA)}}
+\\
+=== Q. Is it possible to receive CredNex invoices using the Target ID already in use for other business operations? ===
+=== A. You must create a Target ID specifically for CredNex. ===
+We apologize for the inconvenience, but for CredNex invoices, you must use a separate Target ID distinct from the one used for other business purposes, such as exchanging transaction fee invoices. To obtain a new Target ID, please submit the {{ :wiki:ut-54_en_invoice_information_application_form.xlsx |UT-54_Invoice information}}.
 \\
@@ 行 203: / 行 182: @@
 === Q. What should I do if a system failure occurs in CredNex? ===
-=== A. For procedures during system failures, please refer to the CredNex Business Procedures, Section 3: Handling Procedures During CredNex Outages, and its appendix, Timetable of Cash ETF Clearing by JSCC in CredNex System Failure. ===
+=== A. For procedures during system failures, please refer to the CredNex Operational Procedures, Section 3: Handling Procedures During CredNex Outages, and its appendix, Timetable of Cash ETF Clearing by JSCC in CredNex System Failure. ===
-Additionally, as a change from the operation of current ETF creation and redemption platform, application information processed on CredNex prior to service suspension due to failure can be provided to AMs for reference purposes.
+Additionally, as a change from the operation of legacy platform, application information processed on CredNex prior to service suspension due to failure can be provided to AMs for reference purposes.
 \\
 === Q. Will there be any changes to file formats in the future? ===
-=== A. It is assumed that there will be basically no changes to the application file, the statement file, the blackout dates file, and the PCF file. As for the issue master file, there is a high possibility that the layout will be changed due to the expansion of the automatic approval function, etc. ===
+=== A. It is assumed that the basic file structure will not change for the application file, the statement file, the blackout dates file, and the PCF file. As for the issue master file, there is a high possibility that the layout will be changed due to the expansion of the automatic approval function, etc. ===
-\\
-=== Q. Will English versions of various documents be provided in the future? ===
-=== A. Current status is as follows. ===
-== Available now ==
-  * Terms of Use
-  * API Specification (English version only)
-  * Operation Manual
-  * Operation procedures
-== Not scheduled ==
-  * Design specifications for each file
-  * Test specifications
 \\
-=== Q. Is the clearing for cash ETFs, which will change in September 2025, only available on CredNex? ===
-=== A. It is available on both the current ETF creation/redemption platform and CredNex. ===