JP2019215790A - Xml format telegraphic message creation support system, and xml format telegraphic message creation support method and program - Google Patents

Abstract

To provide an XML format telegraphic message creation support system for supporting creation of an XML telegraphic message for bank remittance which is composed as XML-format files and which satisfies items of necessary financial EDI information.SOLUTION: The present invention is directed to a system for supporting creation of an XML-format telegraphic message describing financial EDI information having information of settlement by transfer which is transmitted through all bank EDI system from a paying company to a receiving company. The system includes a settlement data input unit for inputting financial EDI information corresponding to settlement data from an accounting system, a template selecting unit for selecting, in response to destination of transmission of the XML-format telegraphic message, a template for an item information input format including items for the financial EDI information, a financial EDI information writing unit for writing respective data of supplied financial EDI information in the template for the item information input format, and an XML-format telegraphic message creating unit for creating an XML-format telegraphic message based on each of the data of the financial EDI information filled in the template for the item information input format.SELECTED DRAWING: Figure 1

Description

  The present invention provides an XML-formatted message creation support system that supports creation of an XML (Extensible Markup Language) -formatted message transmitted via a Zengin EDI (electronic data interchange) system by Zengin-Net (National Bank Fund Settlement Network). The present invention relates to an XML format message creation support method and a program.

At present, remittances between domestic companies are performed by the destination financial institution, which is the transaction bank of the paying company that is the transferor, specifying the destination financial institution, which is the transaction bank of the recipient company that is the transferee, and This is done via the Zengin system operated by the Internet. As described above, through the Zengin system, payment of merchandise between different banks is performed by online processing.
In this online processing, as shown in FIG. 11, a bank remittance telegram is sent from the paying company 201 to the receiving company 202 for each transfer, and the destination bank (financial institution) 203, the Zengin system 204 and the destination bank ( (Financial institution) 205.

  The bank remittance message is a file generated based on the settlement data output by the accounting system of the paying company 201, and is a fixed-length message having a data length determined by the Zengin System 204. As shown in FIG. 12, the bank remittance message is composed of EDI (Electronic Data Interchange) information having a data volume of 20 digits, together with information necessary for payment such as account information of the transfer source and the transfer destination, the payment amount, and the payment date. Is described.

  The financial EDI information includes items such as industry category, data category, payment notice number, payment notice issue date, invoice number, payer company code, payee company code, payment amount, tax amount, payment number, and billing address. The contact person, billing contact department, order number, order number, unit price, quantity, delivery date, product code, product name, etc.

Generally, the paying company collectively pays for a plurality of commodities on the settlement date when the merchandise is paid to the receiving company.
At this time, as described above, the bank remittance telegram has an EDI information area in which financial EDI information can be described, but since it has a fixed data capacity, sufficient information cannot be described.

Therefore, in the settlement amount, financial EDI information such as a product name, a unit price, a quantity, and a delivery date and time of the product necessary for sorting the amount is insufficient in a bank remittance message.
Therefore, at the receiving company, when the accountant clears the accounts receivable of the sold product from the information such as the amount of money received and the payment date in the bank remittance message, the settlement amount received and the order slip etc. It is necessary to check while checking information such as the product name, unit price, quantity, and delivery date of the product.

As described above, since the current EDI information area has a small data capacity, inefficient reconciliation work in the receiving company, and accordingly, the settlement amount from the receiving company to the paying company corresponds to any transaction. Inquiries such as whether or not there is inefficiency in business has been caused.
As a countermeasure against this, Zengin-Net has changed the bank remittance message from a fixed length to a variable-length bank remittance message in XML file format (hereinafter referred to as a bank remittance XML format message) so that the contents of the settlement data can be described in more detail. To be shown).

  This bank transfer XML format message is transmitted from the paying company 201 to the receiving company 202 via the Zengin EDI system 206 in FIG. Here, the Zengin EDI system 206 is a system that enables transmission of various information (payment notice number, invoice number, etc.) relating to the transfer between the financial institutions to the receiving company. It corresponds to a bank remittance XML format message written in XML format.

  By using the bank remittance XML format message shown in FIG. 13, financial EDI information such as the product name, unit price, quantity, and the delivery date and time of the product necessary for sorting the amounts can be sufficiently described. In each of the paying companies, it is possible to improve the efficiency of the settlement business for the purchase and sale of products.

Japanese Patent No. 6228651

When creating a bank remittance XML format message on the paying company side, it is necessary to generate a bank remittance XML format message from settlement data output by the accounting system, that is, a fixed-length bank remittance message format.
As shown in FIG. 13, it is necessary to write financial EDI information of items set for each payment detail of a transaction and product information and order information of an order slip corresponding to the payment details in each structured data item. There is.

However, it is possible to structure and describe payment information including financial EDI information in an XML format, but it is very difficult for a person in charge of accounting in a company to have no experience of programming in a structured language or the like. Work.
Whether or not the description of the structuring in the bank remittance XML format message is clear can be verified by debugging with an XML file creation tool. On the other hand, whether or not the financial EDI information satisfies all necessary items requires the person in charge to check the tags one by one, which requires an inefficient check operation.

  The present invention has been made in view of such circumstances, and has an XML format that is structured as an XML format file and provides support for easily creating a bank remittance XML format message that satisfies necessary financial EDI information items. An object of the present invention is to provide a message creation support system, an XML-format message creation support method, and a program.

  SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problem. An XML-formatted message creation support system according to the present invention is provided from a paying company to a receiving company through a Zengin EDI (Electronic Data Interchange) system. An XML format message creation support system for supporting creation of an XML format message in which financial EDI information in transfer settlement is transmitted, and inputs data of financial EDI information corresponding to settlement data output from an accounting system. A payment data input unit, a template selection unit for selecting a template of an item information input format in which the items of the financial EDI information are described in accordance with a transmission destination of the XML format message, and a template of the item information input format. Financial EDI information writing for writing each data of the financial EDI information supplied to If, on the basis of each of the data of the financial EDI information entered in the template of the item information input format, characterized in that it comprises a XML file creation unit that generates the XML format message.

  In the XML format message creation support system of the present invention, the template of the item information input format is set in advance for each business type or each company.

  In the XML format message creation support system according to the present invention, the template of the item information input format is a fixed format template in which items are fixed or a tag format template in which required items are described and can be arbitrarily edited. And an item setting format selection unit for selecting either the fixed format template or the tag format template.

  In the XML format electronic message creation support system according to the present invention, when the financial EDI information writing unit describes financial EDI information data corresponding to the payment data in a CSV format, the financial information writing unit uses the mapping table to execute the item information input format. In each of the items, data of financial EDI information corresponding to the item is written.

  The XML-formatted message creation support system according to the present invention is further characterized by further comprising an XML-format conversion unit for converting the XML-formatted message into a CSV format, an Excel format, and a fixed-length format message.

  According to the XML-formatted message creation support method of the present invention, a payment-side company transmits XML to a receiving-side company via a Zengin Electronic Data Interchange (Electronic Data Interchange) system, in which financial EDI information in payment settlement is described. A payment data input unit for inputting data of financial EDI information corresponding to payment data output from an accounting system, and a template selection unit. A template selecting step of selecting a template of an item information input format in which items of the financial EDI information are described according to a transmission destination of the XML format message; A financial EDI which writes data of each of the financial EDI information supplied to a template in a format. Report writing step and an XML file creating step of generating the XML format message based on each data of the financial EDI information written in the template of the item information input format. Features.

  The program according to the present invention is used to create an XML-formatted message in which financial EDI information in transfer settlement is described, which is transmitted from a paying company to a receiving company via a Zengin Electronic Data Interchange (EDI) system. A program for causing a computer to function as an XML format message creation support system to be supported, the computer comprising: a payment data input unit for inputting financial EDI information data corresponding to payment data output from an accounting system; Template selecting means for selecting a template in an item information input format in which information items are described according to the transmission destination of the XML-formatted message; and the financial EDI information supplied to the template in the item information input format Financial EDI information writing means for writing each data of Based on the data of each of the financial EDI information written in the item information input format of the template is a program for functioning as an XML file creating means for generating the XML format message.

  According to the present invention, an XML format message creation support system and an XML format message creation support system for easily creating a bank remittance XML format message that is structured as an XML format file and satisfies necessary financial EDI information items Methods and programs can be provided.

FIG. 1 is a diagram illustrating a configuration example of an XML-format message creation support system according to an embodiment of the present invention. 2 shows a configuration example of a template file table written and stored in a template database 110. It is a flowchart which shows the operation example of the generation processing of the bank remittance XML format message by the XML format message creation support system of this embodiment. FIG. 11 is a diagram showing a menu screen for setting a template file format including items of financial EDI information used when generating a bank remittance XML format message and input fields for inputting data of the items. It is a figure which shows the screen which inputs the data of the item of the transferee information including financial EDI information by a template file, and generates comprehensive transfer data. FIG. 3 is a diagram illustrating a configuration example of a fixed-length format template table corresponding to a fixed-length format template file. FIG. 4 is a diagram illustrating a configuration example of a tag format template table corresponding to a tag format template file. It is a figure showing an example of a setting screen of a mapping table which shows which item of financial EDI information in financial EDI information of a CSV file corresponds to which item of financial EDI information of a template file. It is a figure showing an example of a display screen of a reading CSV format detailed setting which edits a mapping table. It is an example of the display screen at the time of performing the process which converts each of the deposit / withdrawal transaction statement file in XML format and the transfer / receipt notification confirmation file into a table in table format. It is a conceptual diagram which shows the operation example of the Zengin system and the Zengin EDI system which the Japan Bankers Association operates. FIG. 4 is a diagram illustrating a configuration example of a bank remittance message in which the data length used in the Zengin system is a fixed-length message. FIG. 3 is a diagram showing a configuration example of a bank remittance XML format message which is an XML format message with a variable data length used in the Zengin EDI system.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing an example of the configuration of an XML-format message creation support system according to an embodiment of the present invention. In FIG. 1, the XML format message creation support system according to the present embodiment is realized by, for example, an application program installed in each server of the paying company 201 and the receiving company 202 in FIG.

  For example, as shown in FIG. 1, the XML-format message creation support system according to the present embodiment includes a payment data input unit 101, a template selection unit 102, an item setting format selection unit 103, an item editing unit 104, and a financial EDI information writing unit. 105, an XML file creation unit 106, a table format file creation unit 107, a display control unit 108, a display unit 109, a template database 110, and an XML file storage unit 111.

The payment data input unit 101 reads a payment data file (payment data file) output from an accounting system (not shown). The file format of the payment data may be a fixed-length format file, a CSV (comma separated values) format file, or an XML format file. The settlement data is, for example, data indicating the price paid (settled) by the paying company 201 as payment for the payment type such as product purchase, service, and construction from the receiving company 202, and includes the paying company 201, the settlement date, Information such as the payment amount is described.
Further, the payment data input unit 101 temporarily writes the payment data file supplied from the accounting system into the XML file storage unit 111 and stores the same.

  The template selecting unit 102 transmits the financial EDI information at the time of generating the bank remittance XML format message corresponding to the business type and the business identification information for identifying each of the business types and the businesses of the receiving company to which the settlement data file is transmitted. A template file in which items are described is searched in the template database 110. The template file selected here is a fixed-length template file and a tag template file as candidates.

FIG. 2 shows a configuration example of a template file table written and stored in the template database 110.
In FIG. 2, in each record, a fixed template file index and a tag format template file index are written and stored in advance corresponding to the business type / company identification information. The fixed template file index indicates the address where the fixed template file corresponding to the selected business type / company identification information is written and stored in the template database 110. The tag type template file index indicates the address where the tag type template file corresponding to the selected business type / company identification information is written and stored in the template database 110.

Here, the fixed-length template file invoices financial EDI information not included in the payment data file output from the accounting system, for example, each of the payment types such as purchased goods, received services, and requested construction. Items of financial EDI information uniquely specified in units are provided in advance as fixed data input fields. The types of financial EDI information items in the fixed-length template file are defined in advance by the business type or company.
In the following description, a fixed-length format template file and a tag format template file are simply referred to as a template file.

  In addition, the tag format template file includes financial EDI information that is not included in the payment data file output from the accounting system, for example, each of the payment types such as purchased goods, received services, and requested construction in billing units. Although items of financial EDI information to be uniquely specified are provided as data input fields, the user can arbitrarily edit new items by adding new items or deleting existing items. The type of financial EDI information item in the tag format template file is extracted by an arbitrary method as needed. For example, as for the types of financial EDI information items in this tag format template file, a questionnaire survey is conducted for each type of business or company, and the payment amount to be paid for each type of payment commonly used by each type of business or company is determined. Are selected by extracting items that clarify whether or not they include a billing unit.

  The item setting format selection unit 103 selects one of the fixed-length format template file and the tag format template file from the templates selected according to the business type and the company, based on the supplied format selection signal.

  The item editing unit 104 edits the items of the financial EDI information in the bank transfer XML format message in response to the operation of adding or deleting the items of the financial EDI information on the display screen of the display unit 109. Then, the item editing unit 104 writes and stores the edited tag format template file in the XML file storage unit 111 once.

The financial EDI information writing unit 105 performs a process of writing data of financial EDI information items corresponding to each financial EDI information column of the template file.
At this time, the financial EDI information writing unit 105 associates each item of the financial EDI information and the template file in the file read from the accounting system with the mapping table indicating the correspondence between the settlement data and the template file. Do. That is, if the item names used for the settlement data file output by the accounting system and the bank remittance XML format message are different even though they are of the same type, it is necessary to associate them with each other.

  Here, when the payment data is in CSV format, the financial EDI information writing unit 105 associates the number of the order in which the items are described in CSV with the item names used in each of the bank remittance XML format messages. Use the mapping table. The mapping table may be generated by a person in charge of the company, or may be generated in advance by a company that creates the application program of the present embodiment.

  The XML file creating unit 106 describes the financial EDI information data of each item input by the financial EDI information writing unit 105 as the financial EDI information data of the corresponding item in the XML format shown in FIG. Generate a bank remittance XML format message. That is, in the bank remittance XML format message, a tag of “order details” is attached to “payment information” indicating a company name, a transfer account, and the like of a payee receiving company in the settlement of the transfer, for each payment statement. Yes, subordinate to the tag of the “order details”, as items of “financial EDI information” regarding the products and the like of the details, for each request from the receiving company, “order number”, “amount”, It is classified into "units".

As described above, the bank remittance XML format message corresponds to the transfer performed on the same settlement date, and describes a plurality of different receiving companies and a plurality of statements for each receiving company.
Further, the XML file creating unit 106 writes the created bank remittance XML format electronic message into the XML file storage unit 111 and stores it.

  The tabular file creation unit 107 displays a bank remittance XML format message generated by the XML file creation unit 106 in the paying company or transmitted from the paying company in the receiving company to data such as Excel (registered trademark). Convert to a table format file of the format to be displayed as the format.

  Further, the tabular file creation unit 107 converts the bank remittance XML format message transmitted from the paying company into data that can be input to the accounting system, for example, a fixed length format, CSV format, XML format, etc. I do. At this time, the financial EDI information writing unit 105 performs an inverse conversion of the item name in the bank remittance XML format message to the item name in the payment data format that can be input to the accounting system with reference to the mapping table.

The display control unit 108 performs control for displaying a data input screen used by each unit described above on a display unit 109 described later.
The display unit 109 is, for example, a liquid crystal panel having a predetermined resolution.

FIG. 3 is a flowchart showing an operation example of a bank remittance XML format message generation process by the XML format message creation support system of the present embodiment.
Step S1:
The payment clerk of the paying company activates the XML-format message creation support system application on the server, for example.
Thereby, the display control unit 108 displays a screen for setting the format of the template file shown in FIG. 4 on the display screen of the display unit 109.

  FIG. 4 is a diagram showing a menu screen for setting the format of a template file including items of financial EDI information used when generating a bank remittance XML format message and input fields for inputting data of the items. In the menu screen of FIG. 4, a selection bar 501 displays options for selecting a template file format (type of financial EDI information template). As options, there are at least two types of template files: a fixed-length template file and a tag template file.

In this selection bar 501, the person in charge selects, for example, either a fixed-length template file or a tag template file, clicks a save button 502 with a mouse, and inputs the template file format.
In addition, the financial EDI information in the read CSV setting area 503 corresponds to the financial EDI information item in the CSV format file and the financial EDI information item in the template file.

The item setting format selection unit 103 outputs template format information indicating the format of the template file to the template selection unit 102 in response to the format selection and input operation of the person in charge.
Then, the template selecting unit 102 writes and stores the template format selected by the person in charge in the internal storage unit.

Step S2:
Next, the template selection unit 102 displays, via the display control unit 108, a screen illustrated in FIG. 5 for selecting payment data to be selected using the template file on the display screen of the display unit 109.

FIG. 5 is a diagram showing a screen for inputting data of items of transfer destination information including financial EDI information by using a template file and generating comprehensive transfer data.
A selection button group 551 including a fixed-length file read button, a CSV read button, and an XML file read button matches the file format of the settlement data output by the accounting system.
When the accounting system outputs the settlement data in the fixed-length format file, clicks the fixed-length read button. When the accounting system outputs the settlement data in the CSV format file, clicks the CSV read button. Clicks the XML file read button when the settlement data is output in the XML file format.

Step S3:
Then, the template selecting unit 102 reads the settlement data from the accounting system, and as a candidate for inputting the data of the item of the financial EDI information, stores in the area 552 each transfer destination (receiving company) in the settlement data read from the accounting system. Display the file of details of.

Step S4:
Next, the staff member clicks the detail button 553 with a mouse to select a transfer destination company to which the data of the financial EDI information is to be input.
By the above-described processing, the template selecting unit 102 refers to the template file table of the template database 110, and stores the template file based on the business type and company identification information of the receiving company (for example, the customer code 1 and the customer code 2 in FIG. 5). Search for the business type or company to read.

Step S5:
The template selection unit 102 determines whether the template format stored in its own storage unit is a fixed-length format or a tag format.
At this time, if the template format is the fixed-length format, the template selecting unit 102 advances the processing to step S6. On the other hand, when the template format is the tag format, the template selecting unit 102 advances the processing to step S8.

Step S6:
The template selecting unit 102 reads a fixed-length template file index from a record in the template file table of the template database 110 corresponding to the business type / firm identification information of the receiving company.
Then, the template selecting unit 102 reads from the template database 110 the data of the fixed-length format template file corresponding to the fixed-length format template file index.

Step S7:
The financial EDI information writing unit 105 sequentially reads the data of each item of the financial EDI information from the settlement data in the CSV format (or the fixed length format and the XML format) read from the accounting system, and uses a predetermined mapping table. Writing is performed for each item of the corresponding financial EDI information in the fixed-length format template file read by the template selecting unit 102.
At this time, the financial EDI information writing unit 105 displays, via the display control unit 108, a fixed-length template table 561 corresponding to the fixed-length template file shown in FIG. In the fixed-length format template table 561, each table corresponds to each settlement data of an invoice with the same transfer date from the transfer-destination receiving company. FIG. 6 is a diagram illustrating a configuration example of a fixed-length format template table corresponding to a fixed-length format template file.

As a result, the financial EDI information writing unit 105 generates a fixed-length format template file in which item data is written in each item column of the financial EDI information. The financial EDI information writing unit 105 writes and stores the generated fixed-length format template file in the XML file storage unit 111 once.
In the data of the financial EDI information, the data of the item of the fixed-length format template file and the data of the item whose details are not described in the settlement data file of the CSV format (or the fixed-length format and the XML format) are described. In the fixed-length format template table 561 shown in FIG. 6, the person in charge writes the data of the corresponding item manually by using a keyboard or the like with reference to the bill.

  Then, when the person in charge clicks save button 562 with a mouse, financial EDI information writing unit 105 reads the data written by the person in charge in the column of each item of financial EDI information, and reads the corresponding item of financial EDI information. The data is written in the column of No. and a fixed-length format template table is generated.

Step S8:
The template selecting unit 102 reads a tag format template file index from a record in the template file table of the template database 110 corresponding to the business type and company identification information of the receiving company.
Then, the template selecting unit 102 reads data of the tag format template file corresponding to the tag format template file index from the template database 110.

Step S9:
Then, the financial EDI information writing unit 105 displays a tag format template table 571 corresponding to the tag format template file shown in FIG. FIG. 7 is a diagram illustrating a configuration example of a tag format template table corresponding to the tag format template file.
The person in charge refers to the item of financial EDI information in the tag format table 571 on the display screen of the display unit 109, adds a column of items necessary for the receiving company or business type of the transfer destination, and adds a column of unnecessary items to the column of unnecessary items. Perform edit processing to delete.
The item editing unit 104 edits a column of each item in the tag format template table 571 in response to the above-described editing processing on the display unit 109 of the person in charge.

Step S10:
The financial EDI information writing unit 105 sequentially reads the data of each item of the financial EDI information from the settlement data in the CSV format (or the fixed length format and the XML format) read from the accounting system, and uses a predetermined mapping table. Writing is performed for each item of the corresponding financial EDI information in the tag format template table edited by the item editing unit 104.
At this time, the financial EDI information writing unit 105 displays the tag format template table 571 corresponding to the tag format template file shown in FIG. In this tag format template table 571, each table corresponds to each settlement data of an invoice with the same transfer date from the transfer destination receiving company.

Thereby, the financial EDI information writing unit 105 generates a tag format template file in which the data of the item is written in the column of each item of the financial EDI information. The financial EDI information writing unit 105 temporarily writes and stores the generated tag format template file in the XML file storage unit 111.
For data of items of financial EDI information, data of items for which details are not described in a CSV (or fixed-length format and XML format) payment data file with respect to items of a tag format template file are shown in FIG. In the tag format template table 571 shown in FIG. 7, the person in charge writes the data of the corresponding item manually using a keyboard or the like with reference to the bill.

Also, instead of obtaining a settlement data file from the accounting system, the person in charge refers to the invoice and manually enters the corresponding item in the column of each item of the tag format template table 571 shown in FIG. Data may be written using a keyboard or the like.
Then, when the person in charge clicks save button 572 with a mouse, financial EDI information writing unit 105 reads the data written by the person in charge in the column of each item of financial EDI information, and sets the corresponding item of financial EDI information. The data is written in the column of No. and a tag format template table is generated.

Step S11:
The financial EDI information writing unit 105 determines whether or not all the processing on the payment data in the area 552 on the display screen of FIG.
At this time, the financial EDI information writing unit 105 advances the processing to step S12 when all the processing on the payment data in the area 552 is completed. Here, the financial EDI information writing unit 105 displays a character string “set” in the financial EDI information column of the record of the settlement data for which the writing of the financial EDI information has been completed in the display image shown in FIG. Then, the person in charge is notified that the payment data has been written into the template file.

  On the other hand, when all the processing on the settlement data in the area 552 has not been completed, the financial EDI information writing unit 105 advances the processing to step S4. Here, the financial EDI information writing unit 105 writes the character string “unset” in the financial EDI information column of the record of the payment data for which the financial EDI information has not been written in the display image shown in FIG. Then, a notice is displayed to prompt the person in charge to write data in the financial EDI information item column. In addition, the financial EDI information writing unit 105 writes a character string “error” in the financial EDI information column of the payment data record in which the writing has been completed but data has not been written in all the item columns. Is displayed to notify the person in charge of confirming the financial EDI information.

Step S12:
The person in charge confirms the end of the data writing process for each item of the financial EDI information for all of the payment data in the area on the display screen in FIG. 5, and then performs “XML file creation” on the display screen in FIG. Click the indicated button 555 with the mouse.
As a result, the XML file creation unit 106 reads the template table (fixed-length template table or tag format template table) from the XML file storage unit 111.
The XML file creating unit 106 creates an XML bank transfer XML format message (XML file) shown in FIG. 13 based on the read template table, and stores the created bank transfer XML format message in the XML file storage unit 111. Write and store.

The mapping table used in step S7 is set as follows.
In the read CSV setting area 503 in FIG. 4, a mapping table used for each of the comprehensive transfer data, financial EDI information, and transfer destination account information is set.
In the read CSV setting area 503, a mapping table is set for each settlement data (total transfer data, financial EDI information, and transfer destination account information) of a CSV format file read from the accounting system.

For example, when the person in charge sets the mapping table of the comprehensive transfer data, the selection bar 503A of the read CSV setting area 503 in FIG. Select and click the Modify button with the mouse. Alternatively, a new creation button 503B is clicked with a mouse.
As a result, the financial EDI information writing unit 105 displays the display screen of the read CSV format common setting shown in FIG. 8 on the display screen of the display unit 109 via the display control unit 108. FIG. 8 is a diagram showing an example of a setting screen of a mapping table indicating which item of the financial EDI information in the financial EDI information of the CSV format file corresponds to which item of the financial EDI information of the template file.

  On the display screen of the read CSV format common setting shown in FIG. 8, the person in charge enters the format name input field 505 to map the financial EDI information items in the CSV format file financial EDI information to the template file items. The name of the mapping table to be used is entered, the type of template (fixed length format, tag format, etc.) is set in the input field 506, and the setting button 507 is clicked. As a result, the financial EDI information writing unit 105 sets a mapping table used to map financial EDI information items in the CSV format file for predetermined payment data to template file items.

  FIG. 9 is a diagram showing a display screen of the detailed setting of the read CSV format for editing the mapping table. The financial EDI information writing unit 105 displays the name of the mapping table entered in the input column 505 of FIG. 8 in the display column 511A of the format name in the display area 511 on the display screen of FIG. In addition, the financial EDI information writing unit 105 displays the setting of the presence / absence of a header record in the display column 511B of the format. In addition, the financial EDI information writing unit 105 fills in the entry field 503A “general transfer data” and the entry field 503B “financial EDI information” in the entry field 503 of FIG. 4 with respect to the display field 511C of the target file in the display area 511. The name of the read CSV format file described in any of the fields 503C “Transfer destination account information” is displayed. Further, the financial EDI information writing unit 105 displays the template type input in the entry column 506 of FIG. 8 in the display column 511D of the financial EDI information template type in the display area 511.

Then, on the display screen of FIG. 9, a setting area 513 is displayed in the reading CSV item setting area 512 when “fixed length format (140 digits)” is selected in the “template type” of the input field 506 in FIG. 8. Is displayed. On the other hand, in the read CSV item setting area 512, a setting area 514 is displayed when “XML tag format (cross-industry EDI specification)” is selected in “template type” in the input field 506 in FIG.
Here, the data record item is an item of financial EDI information necessary for specifying a product, a quantity, a price, and the like corresponding to an invoice from the receiving company at the transfer destination.

In the setting area 513 for setting a mapping table for specific information items necessary for specifying an invoice or the like from the receiving company of the transfer destination, the person in charge uses a “fixed-length format (140 digits)” template file in advance. The number from the head of the specific information item in the CSV format file is entered in the item number column in the same record in association with the set specific information item.
As a result, the financial EDI information writing unit 105 reads the data in the setting area 513 and associates the specific information item in the template file with the specific information item in the CSV format file. Generate

In addition, in the setting area 514 for setting a mapping table for data record items, the person in charge associates financial EDI information items set in advance in a template file of “XML tag format (cross-industry EDI specification)”. Then, the number from the head of the financial EDI information item in the CSV format file is entered in the item number column in the same record.
Accordingly, the financial EDI information writing unit 105 reads the data in the setting area 514, and associates the financial EDI information items in the template file with the financial EDI information items in the CSV format file. Generate mapping table for

As described above, after the person in charge inputs the data of each mapping table for the data record item, the save button on the display screen in FIG. 9 is clicked with the mouse.
Accordingly, the financial EDI information writing unit 105 writes data of the corresponding financial EDI information into the respective fields of the financial EDI information in the template file, Reads the mapping table set by the user. Then, the financial EDI information writing unit 105 associates the financial EDI information item in the payment data file read from the accounting system with each item in the template file by using a mapping table, and associates the financial EDI information item in the template file with the financial EDI information. A process of writing information in each item column is performed.

Then, the person in charge of the paying company transmits a bank remittance XML format message via the Zengin EDI system 206 shown in FIG. 11 (remittance instruction).
As a result, the Zengin EDI system 206 generates a conventional fixed-length bank remittance message from the bank remittance XML format message and sends it to the destination bank 203, which is the transaction bank of the paying company described in the header information. , Send bank remittance telegram. At this time, the bank remittance XML format message and the bank remittance message are associated with each other by predetermined identification information (key (key) information).
The Zengin System 204 decomposes the bank remittance message supplied from the Zengin EDI system 206 for each receiving company, and transfers each settlement target bank transfer message as a bank remittance message to transfer the settlement amount to the destination bank 205, which is the transaction bank. Send to bank.

In addition, the receiving bank 205 receives the bank remittance message for the transfer account managed by itself from the system of the destination bank 203 via the Zengin System 204, and sends the payment message from the paying company to the receiving account of the receiving company. Perform payment processing of the settlement amount.
Then, the receiving bank 205 generates each of the deposit / withdrawal transaction statement and the transfer / receipt notification confirmation based on the above-mentioned bank remittance message, adds the identification information given to the bank remittance message, and sends it to the Zengin EDI system 206. Send to.
The Zengin EDI system 206 associates the bank remittance message and the bank remittance XML format message with identification information, and generates a deposit / withdrawal transaction statement file, a transfer / receipt notification confirmation as an XML format file for a deposit / withdrawal transaction statement and a transfer / receipt notification confirmation. Each file is generated and transmitted to the receiving company 202 (transfer payment).

The receiving company 202 is provided with the XML format message creation support system shown in FIG. The following is an explanation of the process in the receiving company 202.
The payment data input unit 101 inputs the deposit / withdrawal transaction statement file and the transfer / receipt notification confirmation file from the Zengin EDI system 206, and writes and stores them in the XML file storage unit 111. The transfer payment notification confirmation file is an XML format file, in which detailed transaction data and financial EDI information are described for each payment instruction (for each transfer). On the other hand, the deposit / withdrawal transaction statement file is also an XML format file, in which detailed transaction data and financial EDI information are described for each payment instruction statement (for each transfer), and the current balance and the like are stored. Has been described.

The tabular file creation unit 107 displays a display image of the deposit transaction statement input area 581 shown in FIG. 10 on the display screen of the display unit 109 via the display control unit 108. FIG. 10 converts the XML-formatted deposit / withdrawal transaction statement file and the transfer / receipt notification confirmation file into a “CSV format file”, a “fixed length format file”, and a “tabular Excel (registered trademark) file”, respectively. It is an example of a display screen at the time of performing a process.
In the display screen of FIG. 10, the person in charge of the receiving company sets a format for converting the target deposit / withdrawal transaction statement file from the XML format in the input field 581 </ b> A of the deposit / deposit transaction entry area 581. Here, the format format indicates a variation of the file format in the “deposit / withdrawal transaction statement file”. The “deposit / withdrawal transaction statement file” includes variations in the format of deposit / withdrawal transaction statements (ordinary deposit, checking account, savings deposit) and deposit / withdrawal transaction statements (notice deposit, time deposit, and reserve time deposit).

Then, the person in charge writes the file name of the deposit / withdrawal transaction statement file in the input field 581B of the target file in the deposit / deposit transaction statement input area 581. The staff member clicks the read execution button 581C after completing the input in each column in the above-described payment transaction statement input area 581.
As a result, the tabular file creation unit 107 reads the XML file set in the input field 581B from the XML file storage unit 111, and converts the XML file into a file that can be input to the accounting system. That is, the deposit / withdrawal transaction statement file in which the file name is described is converted into the above-mentioned format formats of “CSV format file”, “fixed length format file”, and “Excel (registered trademark) file”.

  Next, on the display screen of FIG. 10, the person in charge of the receiving company sets the format for converting the target transfer notification file from the XML format in the input field 582A in the transfer payment notification input area 582. Here, the format format indicates a variation of the file format in the “transfer payment notification file”. The “transfer payment notification file” includes variations of the format A and the format B.

Then, the person in charge writes the file name of the transfer payment notification file in the target file input field 582B of the transfer payment notification input area 582. The staff member clicks the read execution button 582C after completing the input in the respective fields in the above-described transfer payment notification input area 582.
As a result, the tabular file creation unit 107 reads the XML file set in the input field 582B from the XML file storage unit 111 and converts it into a file in a format that can be input to the accounting system. That is, the transfer receipt notification file in which the file name is described is converted into the above-mentioned format formats of “CSV format file”, “fixed length format file”, and “Excel (registered trademark) file”.

  Conventionally, financial EDI information is insufficient due to the fixed length, and it is not possible to correlate the payment amount with the invoice item. When clearing accounts receivable, the payment amount must be matched with the order slip. However, according to the above-described embodiment, even a person who is unfamiliar with creating a structured file in the XML format can support generation of a bank remittance XML format message in the XML format. It is possible to easily generate a bank remittance XML format message from the settlement data output from the accounting system.

  Further, according to the present embodiment, the bank remittance XML format message transmitted from the paying company and transmitted to the receiving company is converted into a tabular file such as Excel (registered trademark) by the tabular file creating unit 107. Therefore, it is possible to easily detect whether or not there is an error in the settlement data at the receiving company.

  Further, according to the present embodiment, when the receiving company is supplied with a bank transfer XML format message as an XML structured file, the table format file such as Excel (registered trademark) is added to the table format file. Since the conversion can be performed by the creation unit 107, the receivable reconciliation process in the accounting system can be performed in accordance with any of the invoices in the financial EDI information item without having to match the amount as in the related art. Can be easily determined.

  In addition, a program for realizing the function of the XML-format message creation support system in FIG. 1 is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read and executed by a computer system. Alternatively, a process for supporting generation of a bank remittance XML format message used in the Zengin EDI system may be performed. Here, the “computer system” includes an OS and hardware such as peripheral devices.

Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used.
The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Furthermore, the “computer-readable recording medium” dynamically holds a program for a short time like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. In this case, a volatile memory in a computer system serving as a server or a client in that case, and a program that holds a program for a certain period of time are also included. The program may be a program for realizing a part of the functions described above, and may be a program capable of realizing the functions described above in combination with a program already recorded in a computer system.

  As described above, the embodiments of the present invention have been described in detail with reference to the drawings. However, the specific configuration is not limited to the embodiments, and includes a design and the like without departing from the gist of the present invention.

DESCRIPTION OF SYMBOLS 1 ... XML format message creation support system 101 ... Payment data input unit 102 ... Template selection unit 103 ... Item setting format selection unit 104 ... Item editing unit 105 ... Financial EDI information writing unit 106 ... XML file creation unit 107 ... Table format file Creation unit 108 Display control unit 109 Display unit 110 Template database 111 XML file storage unit 201 Paying company 202 Receiving company 203 Destination bank 204 Zengin system 205 Destination bank 206 Zengin EDI system

Claims (7)

Creation of an XML-formatted message that supports the creation of an XML-formatted message containing financial EDI information in the settlement of a transfer, which is transmitted from the paying company to the receiving company via the Zengin Electronic Data Interchange (EDI) system Support system,
A payment data input unit for inputting data of financial EDI information corresponding to payment data output from the accounting system;
A template selection unit for selecting a template of an item information input format in which items of the financial EDI information are described, in accordance with a transmission destination of the XML format message;
A financial EDI information writing unit for writing data of the supplied financial EDI information with respect to the template of the item information input format;
An XML file creation support system, comprising: an XML file creation unit that creates the XML format message based on each data of the financial EDI information entered in the template of the item information input format. The XML format message creation support system according to claim 1, wherein a template of the item information input format is preset for each business type or each company. The template of the item information input format is a fixed-length template in which items are fixed, or a tag format template in which required items are described and arbitrarily editable,
The XML format message creation support system according to claim 1 or 2, further comprising an item setting format selection unit that selects any one of the fixed-length format template and the tag format template. The financial EDI information writing unit includes:
When the data of the financial EDI information corresponding to the settlement data is described in CSV format, the data of the financial EDI information corresponding to the item is written into each item of the item information input format by using a mapping table. The XML format message creation support system according to any one of claims 1 to 3, wherein: The XML format according to any one of claims 1 to 4, further comprising an XML format conversion unit that converts the XML format message into a CSV format, an Excel format, and a fixed-length format message. Message creation support system. Creation of an XML-formatted message that supports the creation of an XML-formatted message containing financial EDI information in the settlement of a transfer, which is transmitted from the paying company to the receiving company via the Zengin Electronic Data Interchange (EDI) system Is a support method,
A payment data inputting step of inputting data of financial EDI information corresponding to the payment data output from the accounting system,
A template selecting step of selecting a template in an item information input format in which the items of the financial EDI information are described in accordance with a transmission destination of the XML format message;
A financial EDI information writing unit for writing data of each of the supplied financial EDI information to the template of the item information input format;
An XML file creation unit that creates the XML format message based on each data of the financial EDI information entered in the template of the item information input format. Creation support method. Creation of an XML-formatted message that supports the creation of an XML-formatted message containing financial EDI information in the settlement of a transfer, which is transmitted from the paying company to the receiving company via the Zengin Electronic Data Interchange (EDI) system A program for making a computer function as a support system,
The computer,
Payment data input means for inputting data of financial EDI information corresponding to payment data output from the accounting system;
Template selecting means for selecting a template in an item information input format in which the items of the financial EDI information are described in accordance with a transmission destination of the XML format message;
Financial EDI information writing means for writing each data of the supplied financial EDI information to the template of the item information input format;
A program for functioning as an XML file generating means for generating the XML format message based on each data of the financial EDI information written in the template of the item information input format.

Images