差分
このページの2つのバージョン間の差分を表示します。
| 両方とも前のリビジョン 前のリビジョン 次のリビジョン | 前のリビジョン | ||
|
faq_en [2025/11/28 14:51] crednex |
faq_en [2026/04/13 09:30] (現在) crednex [Changes from the Current Platform] |
||
|---|---|---|---|
| 行 4: | 行 4: | ||
| === Q. Are there any changes from the current ETF creation/ | === Q. Are there any changes from the current ETF creation/ | ||
| - | === A. The changes are summarized below. === | + | === A. The changes are summarized below.(bolded text: latest updates) |
| == New features == | == 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 " |
| - | | + | * 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 " |
| * Addition of cancellation request flow: AP(prop-desk) and MM can request cancellation of applications. | * 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. | * 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. | * Application operation to AP by MM on CredNex: Commonization of application flow between MM and AP. | ||
| * Discontinuation of CSV batch registration: | * Discontinuation of CSV batch registration: | ||
| - | | + | * PCF registration for cash ETFs abolished: PCF registration for cash ETFs is abolished. Consequently, |
| - | | + | * 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) == | == Changes in workflow (see status definition document for details) == | ||
| 行 34: | 行 34: | ||
| * Issue master file | * 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) | * 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/ |
| * None in particular | * None in particular | ||
| == Changes in output files (see each file design document for details) == | == Changes in output files (see each file design document for details) == | ||
| * Common to all files | * 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 | * Changed character code to “UTF-8 with BOM”: Can be viewed without garbled characters in Excel | ||
| * Blackout dates | * Blackout dates | ||
| 行 47: | 行 47: | ||
| * Item “User ID” is changed to blank. | * Item “User ID” is changed to blank. | ||
| * < | * < | ||
| - | | + | * 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/ | + | * **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)** | ||
| + | | ||
| * Changed the folder structure of the calculation sheet zip file | * Changed the folder structure of the calculation sheet zip file | ||
| - | | + | * 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 | * PCF file | ||
| - | | + | * Change the “Fund Code” 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) == | == Changing permissions (for details, refer to the operation manual) == | ||
| 行 60: | 行 63: | ||
| \\ | \\ | ||
| - | ===== In Preparation for Full Go-Live | + | ==== In Preparation for Full Go-Live ==== |
| 行 76: | 行 79: | ||
| \\ | \\ | ||
| - | === Q. What procedures are required for full operation? === | + | === Q. What procedures are required for the full go-live? === |
| - | === A. Details regarding | + | === A. For details on the application procedures, please refer to the Application Procedure Guide. === |
| + | {{ : | ||
| \\ | \\ | ||
| === Q. What tests should users perform in preparation for the full go-live? === | === Q. What tests should users perform in preparation for the full go-live? === | ||
| - | === A. Details regarding | + | === A. For an overview of the user testing, please refer to page 25 of the briefing |
| + | {{ : |CredNex Briefing Session for June 2026 System Integration (TBA)}} \\ | ||
| + | The user test specification document detailing the user test will be provided in February 2026. | ||
| \\ | \\ | ||
| === Q. What tasks are required on the user side during the migration process for the full go-live? === | === Q. What tasks are required on the user side during the migration process for the full go-live? === | ||
| - | === A. Details | + | === A. For the details |
| + | {{ : |CredNex Briefing Session for June 2026 System Integration (TBA)}} | ||
| \\ | \\ | ||
| + | |||
| + | |||
| + | === Q. Are there any changes to the file design documents from the initial go-live to the full go-live? === | ||
| + | === A. The following changes have been made to the file design documents. === | ||
| + | |||
| + | == Common to all files == | ||
| + | * Addition of a new " | ||
| + | * Correction of typographical errors | ||
| + | |||
| + | == Issue Master Registration File == | ||
| + | * Addition of new fields (3 fields) | ||
| + | * No.38 " | ||
| + | * No.43 " | ||
| + | * No.47 " | ||
| + | |||
| + | == Blackout Dates Batch Registration File == | ||
| + | * No changes. | ||
| + | |||
| + | == Statement Registration File == | ||
| + | * Addition of in-kind ETF statement | ||
| + | |||
| + | == PCF Registration File == | ||
| + | * Addition of PCF | ||
| + | |||
| + | == Issue Master Output File == | ||
| + | * Addition of new fields (effectively 8 fields added) | ||
| + | * No.38 " | ||
| + | * No.43 " | ||
| + | * No.47 " | ||
| + | |||
| + | == Blackout Dates Output File == | ||
| + | * No changes. | ||
| + | |||
| + | == PCF Output File == | ||
| + | * Addition of PCF | ||
| + | |||
| + | == Application Output File == | ||
| + | * Changed the names of the fields " | ||
| + | * Change in number of digits | ||
| + | * No.13 " | ||
| + | |||
| + | == Statement Output File == | ||
| + | * Changes to cash ETF statement | ||
| + | * No.2 "PCF Number" | ||
| + | * Addition of in-kind ETF statement | ||
| ==== Functions ==== | ==== Functions ==== | ||
| 行 117: | 行 169: | ||
| === Q. Is it possible to perform both API and GUI operations? === | === 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. === |
| {{ : | {{ : | ||
| 行 139: | 行 191: | ||
| === Q. Is AP approval required even when AP performs the application registration? | === 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 |
| \\ | \\ | ||
| 行 145: | 行 197: | ||
| === Q. What is a cancellation request? === | === Q. What is a cancellation request? === | ||
| === A. This feature allows applicants to request cancellation of an application they have already registered on CredNex. === | === 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, | + | If you wish to cancel a registered application, |
| - | 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 |
| - | 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, | + | For procedures regarding application cancellations, |
| Please note that registering or canceling application information without the intention of | Please note that registering or canceling application information without the intention of | ||
| completing the creation/ | completing the creation/ | ||
| 行 186: | 行 238: | ||
| === Q. What is CredNex pricing structure? === | === Q. What is CredNex pricing structure? === | ||
| - | === A. For the usage fees currently scheduled, please | + | === A. Please |
| + | {{ : | ||
| \\ | \\ | ||
| === Q. What is the payment procedure for service fees at CredNex? === | === Q. What is the payment procedure for service fees at CredNex? === | ||
| - | === A. We plan to provide details at a briefing | + | === A. Please refer to page 33 of the briefing |
| + | {{ : |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, | ||
| \\ | \\ | ||
| 行 203: | 行 263: | ||
| === Q. What should I do if a system failure occurs in CredNex? === | === Q. What should I do if a system failure occurs in CredNex? === | ||
| - | === A. For procedures during system failures, please refer to the CredNex | + | === A. For procedures during system failures, please refer to the CredNex |
| Additionally, | Additionally, | ||
| 行 209: | 行 269: | ||
| === Q. Will there be any changes to file formats in the future? === | === 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 |
| \\ | \\ | ||
| 行 217: | 行 277: | ||
| == Available now == | == Available now == | ||
| - | * Terms of Use | + | * Terms of Service |
| * API Specification (English version only) | * API Specification (English version only) | ||
| - | * Operation Manual | + | * CredNex |
| - | * Operation | + | * Business |
| == Not scheduled == | == Not scheduled == | ||
| 行 230: | 行 290: | ||
| === Q. Is the clearing for cash ETFs, which will change in September 2025, only available on CredNex? === | === 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/ | === A. It is available on both the current ETF creation/ | ||
| + | |||