JP7717005B2 - Fund settlement support system, method and program - Google Patents

Description

The present invention relates to a fund settlement support system, method, and program that centrally manages fund settlements associated with commercial transaction activities. More specifically, the present invention relates to a fund settlement support system, method, and program that automatically executes fund settlements associated with commercial transaction activities when predetermined conditions are met.

Commercial transactions, also known as the flow of commerce, are carried out by a variety of trading entities (companies, individuals, local governments, etc.). In connection with commercial transactions, trading entities carry out financial settlements such as deposit and withdrawal processes. For example, a company that manufactures a certain product will make a deposit schedule based on information about when and how much will be received from a trading partner to whom it has sold the product, and will then process the deposit once the deposit is actually received. Alternatively, a company will make a remittance schedule based on information about when and how much a payment must be made to a trading partner from whom it has purchased raw materials, and will then process the withdrawal while checking the account balance.

Patent No. 3029421

Due to the large number of products and counterparties handled by some trading entities, they were unable to fully grasp the scale and schedule of fund settlements. For example, at some trading entities, only a small number of people had a grasp of the situation, or no one had a grasp of the whole picture, and only some people had a grasp of each part of the business.

In addition, although the trading entity receives invoice data from its counterparty and therefore knows the purpose, amount, and remittance destination of the funds, it still has to manually request a withdrawal process after receiving a deposit from another counterparty, making the process cumbersome.

However, there were no known systems capable of workflow management of fund settlement procedures, and no known systems capable of grasping the full picture of fund settlements associated with the commercial trading activities of each trading entity.

The present invention was made to solve these problems, and aims to provide a funds settlement support system, method, and program that centrally manages funds settlement procedures based on workflow technology and enables an overall understanding of funds settlement associated with commercial transaction activities.

The fund settlement support system according to one aspect of the present invention comprises:
In response to obtaining deposit information for the entity's account, extracting a first funds transfer identifier associated with the deposit information;
determining whether the first funds transfer identifier is present in a payment terms list;
If it is determined that the second funds transfer identifier exists, read one or more second funds transfer identifiers associated with the extracted first funds transfer identifier from the payment condition list;
and generating a remittance request based at least on the retrieved one or more second funds transfer identifiers.

This invention enables trading entities to centrally manage fund settlement procedures based on workflow technology, and also enables them to grasp the overall picture of fund settlements associated with commercial transaction activities.

A more detailed understanding of the embodiments disclosed herein can be had from the following description, taken in conjunction with the accompanying drawings, in which:
1 is a configuration diagram of an entire system according to an embodiment of the present invention. 1 is a system configuration diagram of a fund settlement support system 10 according to an embodiment of the present invention. FIG. 2 is a diagram showing an example of a data structure of a trading entity master 106 according to an embodiment of the present invention. FIG. 2 is a diagram showing an example of a data structure of a trading partner master 107 according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a data structure of a commercial distribution management DB 108 according to the embodiment of the present invention. FIG. 2 is a diagram showing an example of a data structure of a payment condition list 109 according to an embodiment of the present invention. FIG. 10 is a flowchart illustrating a process for registering data in a commercial distribution management DB 108 according to an embodiment of the present invention. FIG. 10 is a flow diagram illustrating a payment condition generation process according to an embodiment of the present invention. FIG. 10 is a flow diagram illustrating an automatic execution process for fund settlement according to an embodiment of the present invention. FIG. 1 is a diagram showing an example of an input screen 1000 according to an embodiment of the present invention. FIG. 11 is a diagram showing an example of a payment condition specification screen 1100 according to an embodiment of the present invention. FIG. 12 is a diagram showing an example of a fund settlement schedule performance display screen 1200 according to an embodiment of the present invention.

(Overall structure)
Figure 1 is a configuration diagram of an entire system including a fund settlement support system 10 according to an embodiment of the present invention, a user terminal 11, a bank system 12, and a crypto asset management device 13. The fund settlement support system 10 is connected to the user terminal 11, the bank system 12, and the crypto asset management device 13 so that they can communicate with each other. Although only one user terminal 11, one bank system 12, and one crypto asset management device 13 are shown in Figure 1, there may be multiple of these.

The financial settlement support system 10 stores information on the planned and actual financial settlements associated with commercial transaction activities, and stores information on the deposit specifications that are prerequisites for remittance processing and the conditions for performing remittance processing. In this specification, the terms "commercial transaction activities" and "commercial flow" are used interchangeably.

The financial settlement support system 10 can receive and store financial settlement schedule information, actual performance information, and information on the conditions for financial settlement execution from the user terminal 11. Alternatively, the financial settlement support system 10 can receive financial settlement schedule information and actual performance information from other systems (such as billing systems or banking systems).

The planned and actual fund settlement information includes planned and actual information on deposits and withdrawals made with domestic or overseas counterparties. The planned and actual fund settlement information can also handle information on fund transfers within the trading entity's group companies. The fund settlement support system 10 can handle not only Japanese yen, but also foreign currencies and cryptocurrencies. The information on the fund settlement execution conditions includes an identifier that identifies the prerequisite information for executing a remittance (for example, after confirming the deposit from XX company scheduled for XX month △ day, execute the remittance process to △△ company, etc.).

The financial settlement support system 10 can provide one or more pieces of graphic information to the user terminal 11 based on planned and/or actual information on financial settlements associated with commercial transaction activities. The one or more pieces of graphic information visually provide the financial settlement planned and/or actual information to the transacting entity (user). In response to pressing any icon or arrow in the graphic information, the financial settlement support system 10 can display the desired information and provide an editable screen to the user terminal 11.

The fund settlement support system 10 can generate a fund transfer request based on information on the fund settlement execution conditions and send it to the bank system 12 and/or crypto asset management device 13. The fund transfer request can include information such as the sender's account information, the recipient's account information, the transfer amount, and the transfer date. The sender's account information and the recipient's account information can be information on any bank account (e.g., bank code, branch code, deposit type, account number) or information on the destination (address) of any crypto asset.

The user terminal 11 is any type of device capable of operating in a wired or wireless environment and is a terminal used by a trading entity. The user terminal 11 can access the fund settlement support system 10 via a network and perform operations as described herein.

The bank system 12 is equipped with an accounting system and is capable of performing transfer or remittance processing based on a fund transfer request received from the fund settlement support system 10. The bank system 12 is capable of providing account balance information and deposit information to the fund settlement support system 10 based on a balance inquiry request and a request to obtain deposit information from the fund settlement support system 10, respectively. In one embodiment of the present invention, the bank system 12 is capable of receiving a balance inquiry request and a request to obtain deposit information via the bank's API service and providing balance information and deposit information.

The cryptocurrency management device 13 is a device that stores transaction records for any type of cryptocurrency. Transactions include payment source information and payment destination information, and are incorporated into the blockchain after their authenticity is verified (approved).

(System configuration)
Figure 2 is a system configuration diagram of a fund settlement support system 10 according to an embodiment of the present invention. As shown in Figure 2, the fund settlement support system 10, like a general computer, comprises a control unit 101, a main memory unit 102, an auxiliary memory unit 103, an interface (IF) unit 104, and an output unit 105, all interconnected by a bus 120 or the like. The fund settlement support system 10 also comprises, in the form of a file/database or the like, a trading entity master data 106, a trading partner master data 107, a commercial flow management DB 108, and a settlement conditions list 109.

The control unit 101, also known as the central processing unit (CPU), controls each component of the payment support system 10 and performs data calculations. It also reads various programs stored in the auxiliary storage unit 103 into the main storage unit 102 and executes them. The main storage unit 102, also known as the main memory, stores various received data, computer-executable instructions, and data after calculations based on those instructions. The auxiliary storage unit 103 is a storage device such as a hard disk drive (HDD) and stores data and programs for the long term.

The embodiment in Figure 2 describes an embodiment in which the control unit 101, main memory unit 102, and auxiliary memory unit 103 are provided inside the same computer, but in another embodiment, the financial settlement support system 10 can be configured to achieve parallel distributed processing by multiple computers by using multiple control units 101, main memory units 102, and auxiliary memory units 103. Also, in another embodiment, multiple servers can be installed for the financial settlement support system 10, and the multiple servers can share a single auxiliary memory unit 103.

The IF unit 104 acts as an interface when sending and receiving data with other systems and devices, and also provides an interface for accepting various commands and input data (various masters, tables, etc.) from the system operator. The output unit 105 provides a display screen for displaying processed data and printing means for printing that data.

The trading entity master 106 stores information on trading entities (companies, individuals, local governments, etc.) involved in commercial transaction activities. Figure 3 is a diagram showing an example of the data structure of the trading entity master 106 according to an embodiment of the present invention. The trading entity master 106 may include a trading entity ID 301, authentication information 302, trading entity information 303, and account information 304, but is not limited to these data items and may also include other data items.

Transaction entity ID 301 is an identifier identifying the transaction entity. Authentication information 302 indicates authentication information used by the transaction entity when using the payment support system 10. The payment support system 10 according to the present invention can provide two-step authentication and/or two-factor authentication functions to transaction entities. For example, a transaction entity can enter an ID and password via a PC, and then enter a security code via a smartphone or select whether or not to log in via an app. For example, in addition to a regular password, a transaction entity can use a one-time password issued by the payment support system 10 or other information known only to the transaction entity for authentication.

Transaction entity information 303 indicates information such as the name, location, and contact information of the transaction entity. Account information 304 indicates the bank account and/or cryptocurrency account (also called the destination or address) used by the transaction entity for fund transfers.

Returning to Figure 2, the explanation will be made. The trading partner master 107 stores information about trading partners associated with trading entities. Figure 4 is a diagram showing an example of the data structure of the trading partner master 107 according to an embodiment of the present invention. The trading partner master 107 may include a trading entity ID 301, a trading partner ID 401, trading partner information 402, and fund transfer destination information 403, but is not limited to these data items and may also include other data items.

The trading partner ID 401 is an identifier that identifies the trading partner associated with the trading entity (trading entity ID 301). The trading partner information 402 indicates information such as the trading partner's name, location, and contact information. The fund transfer destination information 403 indicates the trading partner's bank account and/or cryptocurrency account to which the remittance will be sent.

Returning to Figure 2, the explanation will be made. The commercial flow management DB 108 stores deposit and withdrawal information for each commercial flow management unit. Figure 5 is a diagram showing an example of the data structure of the commercial flow management DB 108 according to an embodiment of the present invention. The commercial flow management DB 108 can include a trading entity ID 301, a commercial flow management ID 501, a commercial flow management unit 502, a funds transfer ID 503, a trading partner ID 401, a deposit/withdrawal classification 504, a currency type 505, involved account information 506, a planned deposit/withdrawal date 507, a planned deposit/withdrawal amount 508, an actual deposit/withdrawal date 509, and an actual deposit/withdrawal amount 510, but is not limited to these data items and can also include other data items.

The commercial flow management ID 501 is an identifier that identifies commercial flow management, and the commercial flow management unit 502 indicates the commercial flow management unit. The commercial flow management unit is a concept that indicates the relationship between the flow of funds associated with a trading entity, and can indicate, for example, sales revenue associated with the monthly production of a certain product, the amount paid for raw material costs, and the respective trading partners. Other examples of commercial flow management units include the current month's deposits and withdrawals associated with a current account at Bank A's XX branch and their associated trading partners, or the current month's deposits and withdrawals by department within the company and their associated trading partners, and the units that trading entities wish to manage can be set.

The funds transfer ID 503 is an identifier that identifies individual funds transfers between the trading entity and the trading partner. The deposit/withdrawal category 504 indicates whether it is a deposit or withdrawal from the trading entity's perspective. The currency type 505 indicates the type of currency being deposited or withdrawn (e.g., Japanese yen, US dollars, euros, any cryptocurrency, etc.). The involved account information 506 indicates the account information from which the deposit/withdrawal is made; for example, if a deposit is made to the trading entity's account, it indicates the trading entity's account information 304, and if the trading entity remits funds to the trading partner, it indicates the account information 304 of the trading entity that is the sender and the funds transfer destination information 403 of the trading partner that is the recipient.

The planned deposit/withdrawal date 507 indicates the planned date on which a deposit/withdrawal is to be made, and the planned deposit/withdrawal amount 508 indicates the planned amount to be deposited/withdrawn. The actual deposit/withdrawal date 509 indicates the date on which a deposit/withdrawal was actually made, and the actual deposit/withdrawal amount 510 indicates the amount actually deposited/withdrawn.

Returning to Figure 2, the explanation will be given below. The settlement conditions list 109 stores the conditions for executing fund settlement, i.e., information on remittance prerequisites and subsequent processing. Figure 6 is a diagram showing an example of the data structure of the settlement conditions list 109 according to an embodiment of the present invention. The settlement conditions list 109 may include a trading entity ID 301, a commercial flow management ID 501, a prerequisite fund transfer ID 601, and a subsequent processing 602, but is not limited to these data items and may also include other data items. The trading entity ID 301 and the commercial flow management ID 501 are associated with a set of multiple prerequisite fund transfer IDs 601 and subsequent processing 602.

The prerequisite funds transfer ID 601 indicates the funds transfer ID 503 that will trigger the subsequent payment processing. For example, if a certain deposit processing triggers the execution of a subsequent transfer processing, the prerequisite funds transfer ID 601 is set to the funds transfer ID 503 that indicates that deposit processing.

In addition, the prerequisite funds transfer ID 601 can add conditions other than those of the funds transfer ID 503. For example, it is possible to define additional conditions such as executing a subsequent transfer if the account balance at the time of deposit is XXX million yen or more.

Subsequent processing 602 stores the fund transfer ID of the fund transfer processing that is executed when the fund transfer indicated by the prerequisite fund transfer ID 601 occurs (and when additional conditions are also met). Subsequent processing 602 may include one or more fund transfer IDs.

For example, if a deposit of 10 million yen (funds transfer ID = xxxx1) is made from Company A, and a transfer of 5 million yen to Company B (funds transfer ID = xxxx2) and a transfer of 3 million yen to Branch C (funds transfer ID = xxxx3) is made, "xxxx1" will be set in the prerequisite funds transfer ID 601, and "xxxx2" and "xxxx3" will be set in the subsequent processing 602.

(Processing flow: Data registration process in the commercial distribution management DB 108)
7 is a flow diagram illustrating the process of registering data in the commercial distribution management DB 108 according to an embodiment of the present invention. As a prerequisite for executing this process flow, it is assumed that data has been registered in the trading entity master data 106 and the trading partner master data 107.

At S701, the payment processing system 10 performs authentication processing of the transaction entity in response to access from the user terminal 11. When the authentication processing is successfully completed, the payment processing system 10 can provide the user terminal 11 with an input screen 1000 such as the example shown in FIG. 10. The input screen 1000 is a screen for creating a new commercial distribution management unit and inputting a payment schedule, and for retrieving and updating information from the commercial distribution management DB 108 using an existing commercial distribution management unit as a search key. In one embodiment of the present invention, the system may be configured to create only the commercial distribution management unit, and input the payment schedule separately or generate data based on invoice data.

The trading entity enters an arbitrary name ("Product A, December 2021" in the example of Figure 10) in the commercial distribution management unit input field 1002 on the input screen 1000 via the user terminal 11 and presses the generate management unit button 1003. In response to the press of the generate management unit button 1003, the payment support system 10 assigns a commercial distribution management ID 501 and stores the new data in the commercial distribution management DB 108.

At S702, the trading entity inputs the deposit schedule associated with the commercial distribution management unit into the deposit schedule field 1004 via the user terminal 11. As illustrated in FIG. 10, the information entered for each trading partner is the amount, currency, date, and amount to be deposited into which account. In response to pressing the deposit schedule registration button 1005, the payment support system 10 stores the information entered into the input screen 1000 in the commercial distribution management DB 108.

In an embodiment of the present invention, by associating the commercial distribution management ID 501 and/or commercial distribution management unit 502 when generating invoice data (e.g., by adding the commercial distribution management ID 501 to the summary field), expected deposit data can be automatically generated. Alternatively, the payment support system 10 may be configured to receive invoice data associated with the commercial distribution management ID 501 and commercial distribution management unit 502, extract data corresponding to data items in the commercial distribution management DB 108 from the received invoice data, and store the data in the commercial distribution management DB 108. Based on the data entered via the input screen 1000 of FIG. 10 or the data extracted from the invoice data, expected deposit information for each trading partner (i.e., funds transfer ID 503, transaction ID 401, deposit/withdrawal category 504, currency type 505, involved account information 506, expected deposit/withdrawal date 507, and expected deposit/withdrawal amount 508) is generated and stored in the commercial distribution management DB 108.

At S703, the payment support system 10 is configured to obtain deposit information from the bank system 12 and store corresponding performance data in the commercial distribution management DB 108 based on the deposit information. More specifically, the payment support system 10 queries the commercial distribution management DB 108 based on information such as account information, deposit date, deposit amount, invoice identification number (including, for example, the commercial distribution management ID 501 in the summary field), and remittance source indicated by the deposit information, and identifies the corresponding scheduled deposit data. The payment support system 10 can associate the identified data with actual deposit information and store it in the commercial distribution management DB 108.

As is known to those skilled in the art, there are conventional techniques for identifying the sender from the account number of the deposited funds (Patent Document 1), and for identifying the sender based on the identification information added to the summary field. The fund settlement support system 10 may be configured to obtain deposit information from the bank system 12 using the API services of each bank.

(Process flow: Data registration in payment condition list 109)
8 is a flow diagram illustrating the payment conditions generation process according to an embodiment of the present invention. In S801, the payment support system 10 provides a payment conditions specification screen 1100 to the user terminal 11. The payment conditions specification screen 1100 displays the name of the transaction entity that is the logged-in user in a transaction entity display field 1101. The payment support system 10 reads out the commercial flow management ID 501 and commercial flow management unit 502 associated with the transaction entity ID 301 from the commercial flow management DB 108.

When a trading entity selects a commercial flow management unit 502 associated with the trading entity (logged-in user) from the commercial flow management unit selection field 1102 via the user terminal 11, the payment support system 10 reads data associated with the selected commercial flow management unit 502 from the commercial flow management DB 108, generates first graphic information based on the read data, and displays it on the payment conditions specification screen 1100.

Figure 11 shows an exemplary payment conditions specification screen 1100. In the example of Figure 11, the commercial distribution management unit "December 2021 Product A" shown in Figure 10 has been selected, and arrows on the screen indicate that payments to the trading entity, Company A (head office), will be made from Company B, Company C, and Company D, and arrows also indicate that transfers or transfers will be made from Company A (head office) to Company E, Company F, and Company A (branch office). The payment conditions specification screen 1100 also has a payment conditions field 1106 and a registration button 1109, and the payment conditions field 1106 further has a prerequisites field 1107 and a subsequent processing field 1108.

At S802, the trading entity registers the settlement conditions via the user terminal 11. First, the trading entity associates the arrow 1103 from Company B to Company A (head office) with the preconditions field 1107 by dragging and dropping or other methods. This operation causes "Deposit of 10 million yen from Company B (aaaaaa)" to be displayed in the preconditions field 1107. The displayed text is generated by the funds settlement support system 10 based on the data in the commercial flow management DB 108 associated with the arrow 1103. "aaaaaa" indicates the funds transfer ID 503 (precondition funds transfer ID 601). While the above describes associating the arrow 1103 with the preconditions field 1107 by dragging and dropping, any other method that allows for association may be used.

Next, the trading entity associates arrows 1104 and 1105 with subsequent processing column 1108 by dragging and dropping, etc. As a result of this operation, "Transfer 5 million yen to Company E (bbbbbbb)" and "Transfer 3 million yen to Company A (branch) (cccccc)" are displayed in subsequent processing column 1108. These displayed words are also generated by funds settlement support system 10 based on the data in commercial distribution management DB 108 associated with arrows 1104 and 1105, respectively. "bbbbbbb" and "cccccc" indicate the funds transfer ID 503 that is the target of subsequent processing.

In response to pressing the register button 1109, the payment support system 10 sets the funds transfer ID in the prerequisites column 1107 to the prerequisite funds transfer ID 601, and sets one or more funds transfer IDs in the subsequent processing column 1108 to the subsequent processing 602, and stores the data in the payment conditions list 109.

In one embodiment of the present invention, the prerequisite funds transfer ID 601 can include additional conditions in addition to the funds transfer ID 503. For example, additional conditions may be defined such as executing a subsequent remittance if the account balance at the time of deposit is XXX million yen or more, or executing a subsequent process resulting from a second prerequisite funds transfer ID 601 after the subsequent process resulting from a first prerequisite funds transfer ID 601 is completed, and the subsequent process may be executed if the additional conditions are also met.

(Process flow: Automatic execution of fund settlement)
9 is a flow diagram illustrating the automatic execution process of fund settlement according to an embodiment of the present invention. At S901, the fund settlement support system 10, upon receiving deposit information for a trading entity's account from the bank system 12 or crypto asset management device 13, queries the commercial distribution management DB 108 and extracts the fund transfer ID 503 associated with the deposit information. More specifically, the fund settlement support system 10 queries the commercial distribution management DB 108 based on information such as the account information, deposit date, deposit amount, invoice identification number (including, for example, the commercial distribution management ID 501 in the summary field), and remittance source indicated by the deposit information, and identifies the fund transfer ID 503 associated with the corresponding scheduled deposit data.

In one embodiment of the present invention, the fund settlement support system 10 may be configured to obtain deposit information from the cryptocurrency management device 13, and, as described above, query the commercial flow management DB 108 to identify the fund transfer ID 503.

At S902, the funds settlement support system 10 queries the settlement conditions list 109 and determines whether a prerequisite funds transfer ID 601 matching the identified funds transfer ID 503 exists in the settlement conditions list 109. If a matching prerequisite funds transfer ID 601 exists, processing proceeds to S903; on the other hand, if a matching prerequisite funds transfer ID 601 does not exist, this processing flow ends because there is no subsequent processing to be performed.

At S903, the payment support system 10 reads one or more funds transfer IDs 503 included in the subsequent process 602 that are associated with the prerequisite funds transfer ID 601, and generates a remittance request based on the read funds transfer IDs 503. More specifically, the payment support system 10 searches the commercial flow management DB 108 based on the read funds transfer ID 503, obtains the involved account information 506 associated with the read funds transfer ID 503, and generates a remittance request by identifying the transaction entity's account information 304 and the transaction counterparty's funds transfer destination information 403 included in the involved account information 506. The remittance request includes at least the transaction entity's account information 304, the transaction counterparty's funds transfer destination information 403, and information on the remittance amount.

At S904, the fund settlement support system 10 sends the generated remittance request to the bank system 12 or cryptocurrency management device 13 associated with the account information 304. The bank system 12 executes the transfer process or transfer processing based on the received remittance request. The cryptocurrency management device 13 generates a transaction for the remittance process from the trading entity's cryptocurrency account to the trading partner's cryptocurrency account, and after approval, incorporates it into the blockchain.

(Other processing)
12 is a diagram showing an example of a fund settlement schedule and actual performance display screen 1200 according to an embodiment of the present invention. The fund settlement schedule and actual performance display screen 1200 can display second graphic information generated based on the schedule information and actual performance information of fund settlement associated with commercial transaction activities. The fund settlement schedule and actual performance display screen 1200 includes a trading entity display field 1201, a commercial flow management unit selection field 1202, and the second graphic information.

The payment support system 10 can read multiple corresponding deposit and withdrawal information from the payment management DB 108 based on the payment management ID 501 and/or payment management unit 502 specified in the payment management unit selection field 1202, generate second graphic information based on the read deposit and withdrawal information, and provide it to the user terminal 11. The second graphic information visually provides the transaction entity (user) with planned and actual payment information. In response to pressing any icon or arrow on the second graphic information, the payment support system 10 can display the desired information and provide the user terminal 11 with a screen on which the information can be updated. For example, when arrows 1203 and 1204 are selected, the payment support system 10 can provide the user terminal 11 with a screen on which the planned and actual payment information associated with the selected arrows 1203 and 1204 can be updated. This allows the transaction entity (user) to modify planned and actual payment data via the user terminal 11.

The optional icons may be configured to represent, for example, a trading entity or each of multiple trading counterparties. The optional arrows may be configured to represent the flow of funds from a trading entity to a trading counterparty (remittance) or the flow of funds from a trading counterparty to a trading entity (deposit). The fund settlement support system 10 can display each arrow differently based on the planned and actual fund settlement information. For example, an arrow representing the flow of funds where a deposit was made as scheduled may be displayed differently from an arrow representing an unscheduled deposit (e.g., due to a discrepancy in the amount, a delay, etc.) (e.g., one may be displayed as a solid line and the other as a dotted line, one may be displayed in a first color and the other in a second color, etc.).

The financial settlement support system 10 can explicitly show in the graphic information of Figure 12 financial settlements where deposits and withdrawals have not been made as scheduled due to discrepancies in amounts, delays, etc., and/or can notify the transacting entity that such financial settlements are occurring.

The principles of the present invention have been described above with reference to exemplary embodiments, but those skilled in the art will understand that various embodiments that vary in configuration and detail can be realized without departing from the spirit of the present invention. In other words, the present invention can be embodied as, for example, a system, device, method, program, or storage medium.

REFERENCE SIGNS LIST 10 Fund settlement support system 11 User terminal 12 Bank system 13 Crypto asset management device 101 Control unit 102 Main memory unit 103 Auxiliary memory unit 104 Interface (IF) unit 105 Output unit 106 Trading entity master 107 Trading counterparty master 108 Commercial flow management DB
109 Payment conditions list 1000 Input screen 1100 Payment conditions specification screen 1200 Funds payment schedule actual display screen

Claims (9)

In response to obtaining deposit information for the entity's account, extracting a first funds transfer identifier associated with the deposit information;
determining whether the first funds transfer identifier is present in a payment terms list;
If it is determined that the second funds transfer identifier exists, read one or more second funds transfer identifiers associated with the extracted first funds transfer identifier from the payment condition list;
generating a remittance request based at least on the retrieved one or more second funds transfer identifiers ;
receiving commercial flow management unit information indicating a relationship between a first commercial flow management identifier and a flow of funds associated with the trading entity;
Generate first graphic information to be displayed on a device of a trading entity based on data associated with the commercial flow management unit information, generate the first fund transfer identifier and the one or more second fund transfer identifiers for subsequent processing associated with the first fund transfer identifier, and store each of them in the payment condition list.
further configured as follows:
A funds settlement support system in which the association between the first funds transfer identifier and the one or more second funds transfer identifiers is performed by operating an icon indicating the flow of funds settlement, which is included in the first graphic information . The funds settlement support system of claim 1 , further configured to generate the remittance request based on the account information of the trading entity and the funds transfer destination information of the trading partner associated with the second funds transfer identifier, and the remittance amount. Determining whether the first funds transfer identifier is present in a payment terms list includes:
further comprising determining whether an additional condition is met;
If the condition is determined to be satisfied, read one or more second funds transfer identifiers associated with the extracted first funds transfer identifier;
The payment facilitation system of claim 1 , further configured to: generate a remittance request based at least on the retrieved one or more second funds transfer identifiers. receiving a second supply chain management identifier;
reading out a plurality of pieces of deposit and withdrawal information associated with the second commercial flow management identifier, the plurality of pieces of deposit and withdrawal information including fund settlement schedule information and actual result information;
2. The payment support system of claim 1, further configured to: generate second graphic information to be displayed on the transacting entity's device based on the retrieved plurality of deposit and withdrawal information, the second graphic information visually showing the flow of funds settlement between the transacting entity and the trading partner, and the flow of funds settlement being displayed in association with the planned information and actual information of the funds settlement. The fund settlement schedule information is generated based on invoice data,
The fund settlement performance information is generated based on the deposit and withdrawal information.
The payment support system according to claim 4 . The fund settlement support system of claim 1, further configured to send the remittance request to a bank system or crypto asset management device associated with the account information of the trading entity included in the remittance request. The fund settlement support system of claim 1, wherein the deposit information is obtained from a bank system or a cryptocurrency management device. A method executed by a fund settlement support system,
In response to obtaining deposit information for the entity's account, extracting a first funds transfer identifier associated with the deposit information;
determining whether the first funds transfer identifier is present in a payment terms list;
If it is determined that the second funds transfer identifier exists, reading one or more second funds transfer identifiers associated with the extracted first funds transfer identifier from the payment condition list;
generating a remittance request based at least on the retrieved one or more second funds transfer identifiers ;
receiving commercial flow management unit information indicating a relationship between a first commercial flow management identifier and a flow of funds associated with the trading entity;
generating first graphic information to be displayed on a device of a trading entity based on data associated with the commercial flow management unit information, generating the first fund transfer identifier and the one or more second fund transfer identifiers for subsequent processing associated with the first fund transfer identifier, and storing each of the second fund transfer identifiers in the payment condition list;
Furthermore,
A method in which the association of the first fund transfer identifier with the one or more second fund transfer identifiers is performed by operating on an icon indicating the flow of fund settlement, which is included in the first graphic information. A program that causes a computer to execute the method according to claim 8 .