JP2001331759A - Obligation management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an obligation management system which prevents the temporary increase of the load on obligation liquidation work and facilitate business planning and efficiently performs obligation liquidation work. SOLUTION: The system is provided with an obligee terminal 11 to which an obligee inputs credit information, an obligor terminal 21 to which an obligor inputs debt information, a center host 31 which processes credit and debt information between the obligee and the obligor, and a communication network to which the obligee terminal, the obligor terminal, the center host are connected, and the center host collectively manages credit and debt information and liquidation information accompanied with these information, and the obligee terminal and the obligor terminal share credit and debt information and liquidation information, which the center host has, through the communication network.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a credit and debt management system, and more particularly to a system for easily setting up a business plan without temporarily deteriorating the load of the debt settlement work and improving the efficiency of the debt and debt settlement work. Regarding good debt management system.

[0002]

2. Description of the Related Art In a conventional receivables and payables management system, information on receivables and payables is independently created and managed by a billing source and a billing business unit (business constituent unit). Each billing business unit manages settlement based on the payment result information.

[0003] Referring to FIG. 5, a conventional credit / debt management system SS0 includes a credit / debit management database 102 for holding a creditor terminal 101 and claim data by a creditor system (billing source business unit) 100; It comprises an interest rate / commission database 103 for managing information such as interest rates and commissions. Similarly, the debtor side system (the billing business unit 120) also has the debtor terminal 121.
And a debt management database 122 for holding billing data and an interest / feature database 123 for managing information such as interest rates and fees. The creditor and debtor systems are connected via a network NW. Have been.

[0004] In this case, the claimant has his / her creditor terminal 10
1, the invoice data sent to the debtor is registered in the debt management database 102, and at the same time, the invoice data is transmitted to the debtor via the network NW. The debtor receives debt data at the debtor terminal 121 and registers the contents in the debt management database 122. Thereafter, when the due date approaches, the debtor retrieves debt data from the receivables and payables management database 122 and calculates the actual transfer amount by referring to the interest / fees information independently held in the receivables and payables database 122. The transfer data is transmitted to 130. When the creditor receives the account deposit information from the financial institution 130, the creditor clears (apply) the credit data registered in the credit / debt management database 102 while watching the transfer amount.

[0005]

However, this conventional management method has the following problems. Since the payment result information for billing is concentrated in a specific period such as the end of the month, the load of the settlement work of the receivables temporarily deteriorates remarkably. It is difficult to formulate a management plan such as a quick cash flow due to a bias in the actual deposit and withdrawal data during a specific period. Since each invoicing unit / invoicing business unit independently manages the information on receivables and payables, the invoicing unit's invoicing unit does not match the invoicing unit's payment unit (lump sum payment of multiple invoices) In many cases, the efficiency of debt settlement work is reduced. In each of the billing source and billing destination business units, commission information and interest rate information are managed independently, so it is easy for the billing amount to differ from the actual payment amount, and the efficiency of the settlement of receivables and payables increases. bad.

Accordingly, an object of the present invention is to provide a receivables and payables management system in which the load of the receivables clearing work is not temporarily deteriorated, a business plan is easily prepared, and the receivables and payables settlement work is efficient. That is.

[0007]

In order to solve the above problems, the present invention provides a creditor terminal to which a creditor inputs credit information, a debtor terminal to which a debtor inputs debt information, It comprises a center host for processing debt / debt information between the debtor and a communication network to which the debtor terminal, the debtor terminal and the center host are connected,
The center host collectively manages the receivables / debts information and settlement information associated with the receivables / debts information, and the obligor terminal and the obligor terminal communicate with the receivables / debt information held by the center host via the communication network. And sharing payment information.

By doing so, as shown in FIG. 1, for example, the creditor / debt information held by the data management center 30 and the settlement information accompanying the credit / debt information are stored in the creditor terminal 11 and the debtor terminal 21. It can be shared via the network NW. Therefore, a credit and debt management system that does not temporarily worsen the burden of the credit settlement work for creditors and debtors, makes it easy to formulate a business plan, and has a high efficiency of the credit and debt settlement work. Can be.

[0009]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described below with reference to the illustrated embodiment.

(1) Explanation of the Concept of the Present Invention Prior to the description of the embodiment, the concept of the debt management system of the present invention will be described with reference to FIGS. FIG. 1 is a system configuration diagram of a receivable and debt management system SS1 according to an embodiment described below, and FIG. 3 is a flowchart of the embodiment. In this conceptual description, FIG. 1 and FIG. I do.

According to the present invention, as shown in FIGS. 1 and 3, credit information inputted by a creditor from a creditor user terminal 11 is collectively managed by a data management center 30 via a network NW, and the network NW is similarly managed. A claim and debt management business model that collectively manages debt and debt information, scheduled payment information, and settlement information by sharing billing information with a debtor who queries the same data via the debtor, and a method of the debt and debt management business.

In FIG. 1 and FIG. 3, the present invention provides a method for a creditor who claims a creditor: a) The creditor uses his / her own creditor user terminal (hereinafter referred to as creditor terminal) 11 A function for transmitting claim information such as information on bills for purchase of goods or delinquent interest rate information on past bill payments to the center host 31 in the data management center 30 via the network NW. Step S in FIG.
1) b) Information registered as a scheduled payment before the actual payment by the debtor of the billing party in the database 32 in the data management center 30 (hereinafter referred to as scheduled payment information).
Function (payment schedule information / reference function, step S8) by which a creditor can refer to (payment schedule information / registration function, step S5) using his / her creditor terminal 11 via network NW

C) The debtor actually approves the payment (hereinafter referred to as
This information is referred to as the debtor's transfer confirmation information), and at the time when the transfer confirmation information is transmitted (transfer confirmation information / transmission function, step S10), the creditor immediately uses the creditor terminal 11 of his / her own to execute the network NW. (Transfer confirmation information / reference function, not shown) d) Automatically assigns the debtor's payment contents (transfer confirmation information) to the creditor's debt data (delete) E) function (transfer confirmation information / allocation function, step S11) e) When payment information to the creditor's account received from the financial institution 40 is confirmed (payment information / confirmation function), actual payment to the debtor's receivables Is performed (actual payment / assuming function), and information indicating that the payment has been confirmed (hereinafter referred to as payment confirmation information) is transmitted from the own creditor terminal 11 to the center via the network NW. Function of sending to the host 31 (settlement confirmation information and transmission capabilities, step S16) and providing a.

In FIG. 1 and FIG. 3, f) the credit claim information registered by the creditor (the above-mentioned (a) claim claim information / transmission function) is registered by the creditor in the center host 31. At the time (even before the invoice from the creditor actually arrives, the credit claim information / registration function), the debtor immediately makes his debtor user terminal (hereinafter referred to as debtor terminal) 21
(Debt claim information / reference function, step S4) g) With respect to the credit information registered in the data management center 30 by the requesting creditor, the debtor Using the debtor terminal 21, a function of transmitting scheduled payment information (transfer bank account, scheduled transfer date, etc.) to the center host 31 via the network NW before actual payment (scheduled payment information / transmission function, Step S5) h) “Actual transfer amount including interest amount and commission amount added to the billed amount” (actual transfer amount / calculation function, step S9) automatically calculated and derived by the center host 31 based on the debtor's payment schedule information. ) Is received by the debtor at his / her debtor terminal 21 via the network NW, the payment is actually approved, and the transfer confirmation information is sent to the center host 31. Function (transfer confirmation information and transmission function, step S10)

I) At the stage where the debtor has approved payment at his / her debtor terminal 21 (created the transfer confirmation information), the credit data of the creditor in the data management center 30 (the debt data for the debtor itself) ) Is automatically assigned (applied) (debt data / assignment function,
Step S11) j) A function (payment confirmation information / payment confirmation information) that allows the debtor to refer to the contents of the paid debt information (payment confirmation information of the creditor) via the network NW using his / her debtor terminal 21 immediately.
(Reference function, not shown) k) At the stage where the debtor has approved payment (prepared the transfer confirmation information), the center host 31 sends the transfer information to the financial institution based on a predetermined payment method instead of the debtor. (Transfer information / sending function to financial institution, steps S14, S15).

(2) Embodiment Next, the debt and debt management system of this embodiment is shown in FIGS.
Description will be made with reference to (A), (B) and (C). FIG. 1 is a system configuration diagram of this embodiment, and FIGS.
(C) is a functional block diagram of each of the creditor terminal 11, the debtor terminal 21, and the center host 31 which constitute this embodiment. Referring to FIG. 1, the debt management system SS1 of the present embodiment includes a user terminal (creditor terminal) 11 provided in the billing source business unit 10, a user terminal (debtor terminal) 21 provided in the billing destination business unit 20, The data management center 30 includes a center host 31 and a communication network NW such as the Internet for connecting these constituent devices to each other. The data management center 30 includes a receivables and payables management database 32 that holds detailed information of billing contents, and an interest rate / deposit rate that holds bank transfer fees, discount conditions for each payment condition, and delinquent interest rate information.
A commission database 33 is provided.

The creditor terminal 11 is an information processing device such as a personal computer. The creditor terminal 11 is shown in FIG.
As shown in (A), a function is provided for registering, modifying, and inquiring new credit information by accessing the center host 31 via the network NW (registering, correcting, and querying new credit information). 11a). What is credit information?
Information such as invoice number, billing code (business unit for sending invoice), payee code (business unit for paying for invoice), expiration date of receivable, billing amount, etc. It also includes shipping management information such as product name, product model number, and shipping quantity. Further creditor terminal 11
Is the debt management database (3.
By accessing 2), a function to refer to the application result information based on the payment schedule information sent from the debtor and the actual payment information (transfer confirmation information) to the bank account is also provided. Reference function 11b).

The debtor terminal 21 is an information processing device such as a personal computer. The debtor terminal 21 is shown in FIG.
As shown in (B), a function is provided for accessing the center host 31 via the network NW to display new debt information registered by creditors and to input payment schedule information (display of new debt information). Function 21a,
Input function of payment schedule information 21b). The scheduled payment information indicates a scheduled payment date, payee bank account information, and a payment amount for each bill. The center host 31 also has a function of receiving the bank transfer information calculated based on the scheduled payment information and approving the bank transfer information (creating the transfer confirmation information) (transfer confirmation information creation function 21).
c). The bank transfer information corresponds to the account information entered as the scheduled payment information and the total amount, and the center host 31
In addition, the amount of the transfer fee and the like calculated by (1) is also taken into account, and by approving the information of the amount actually transferred (paid) to the financial institution account, the payment for the debt is determined.

The center host 31 is constituted by an information processing device such as a workstation / server. As shown in FIG. 3 (C), the center host 31 has the following functions. The new credit information input by the creditor terminal 11 is registered in the credit / debt management database 32, and the information of correction and inquiry of the existing data is provided. Acquisition and transmission to creditor terminal 11 via network NW (registration function 31a to credit and debt management DB, correction information acquisition function 31 of existing data)
b, existing data inquiry information acquisition function 31c, existing data transmission function 31d). When the creditor confirms the payment from the actual debtor to his or her financial institution account, the creditor terminal 1
The settlement confirmation information transmitted from No. 1 is reflected on the corresponding credit information in the debt management database 32 (a function 31e for reflecting the settlement confirmation information on the credit information).

In response to the debtor's debt data inquiry request transmitted by the debtor terminal 21, information is acquired and transmitted to the debtor terminal 21 via the network NW (acquisition information / transmission function 31f). Referring to the information in the interest / fees database based on the scheduled payment information input by the debtor terminal 21, the financial institution transfer amount in the most advantageous manner for the debtor is calculated, and the network NW is transmitted to the debtor terminal 21.
(Transfer information / transmission function 31g). When the debtor enters the scheduled payment for the debt at the debtor terminal 21, the center host 31 uses the information as the scheduled payment data in the corresponding debt data in the debt / debt management database 32 (from the viewpoint of the creditor). (Payment schedule information / reflection function 31h). Create the transfer data to the transfer destination financial institution based on the financial institution transfer information determined by the debtor,
Hold until the transfer date. On the transfer date, Center Host 3
1 transmits the held account transfer data to the financial institution (account transfer data / transmission function 31i).

[0021] The first database 32 of the debt management is as follows.
Holds billing information (receivable information when referred from the creditor side and data that becomes debt information when referenced from the debtor side), and schedules payment information and clearing information (transfer to the actual financial institution account) At the same time, the state of the billing data is managed collectively, and the debt and debt management information is provided to both the creditor and the debtor (the debt and debt management information / providing function 31j). The interest / fees database (second database) 33 collectively manages interest rates that vary depending on the financial institution account, the fee information for each transfer amount, and the difference in the number of days between the payment maturity date and the actual payment date, and schedules payment. The necessary information for providing the actual transfer amount as information is provided (necessary information / providing function 31k).

Next, the operation of this embodiment will be described in detail with reference to FIGS. FIG. 3 is a flowchart of the present embodiment. Referring to FIG. 3, first, the creditor uses his / her creditor terminal 11 to access the credit input screen established by the data management center 30 on the Internet NWW, and inputs billing data on the displayed screen. Do
(Step S1). The billing information entered here is the bill number, billing code (the code of the business unit that sends the bill), and the payee code (the code of the debtor's business unit that actually pays the bill) , And information such as the expiration date of the receivable, the amount of the bill, and the shipping management information such as the shipping number, product name, product model number, and shipping quantity. The former is processed by the center host 31 of the data management center 30. Treated as transaction data, the latter is mainly used as reference information for inquiries from creditors / obligors. When the center host 31 receives the instruction to register the billing information from the creditor, the center host 31 registers the billing information input by the creditor in the credit and debt management database 32 (step S2).

The center host 31 determines in step S2
In the same manner as described above, upon receipt of a request for registration of billing information from a creditor, new debt information is transmitted to the debtor terminal 21 of the debtor (step S3). The notification of the registration of the new debt information may be performed by e-mail or by means of transferring a file describing the details of the debt. The debtor confirms the new debt information (claim information registered by the creditor) received by his / her debtor terminal 21 (step S).
4). Thereafter, if the content of the debt data is correct, the debtor uses the debtor terminal 21 to access the payment schedule input screen established by the data management center 30 on the Internet NW, and displays the payment schedule information on the displayed screen. Is input (step S5).

When the center host 31 receives the payment schedule information input by the debtor in step S5, the center host 31 writes the payment schedule information input by the debtor in the corresponding credit data on the debt management database 32 (step S6). At the same time, the payment schedule information is transmitted to the creditor's creditor terminal 11 (step S7). To notify creditors of expected payment information, e-mail may be used,
It may be realized by a method such as transferring a file describing the contents of the payment schedule. At this point, the creditor can check the debtor's payment schedule information received from the center host 31 by browsing the homepage provided by the data management center 30 from his / her creditor terminal 11, and the actual debtor can be confirmed. Before the transfer (payment for billing) from the person is performed, the contents can be recognized (step S8).

The center host 31 calculates the actual transfer amount to the financial institution based on the payment schedule information received from the debtor in step S6. First, information such as transfer account information, a transfer amount, and a scheduled payment date is acquired from the scheduled payment information.
Next, based on the acquired information, the interest / fees database 33 is searched, and a fee for the transfer amount of the financial institution performing the transfer, a tax amount for the transfer amount, an interest rate according to the context of the expected payment date and the expiration date of the receivable ( Or discount). Normally, the transfer fee varies depending on the amount to be transferred, but the fee calculation at this time, if there are multiple scheduled transfers to the same account, combine them up to the combination with the lowest fee for each transfer schedule Take into account. Finally, the actual amount of the account transfer is obtained by adding the calculated various amounts to the original amount of the receivable to be paid. After the calculation, the center host 31 transmits the calculated account transfer amount and various amounts calculated in the calculation process together to the debtor terminal 21 of the debtor (step S9).
The notification of the calculation result of the account transfer amount is performed by means such as electronic mail or file transfer.

The debtor confirms the account transfer amount received from the center host 31 at his or her debtor terminal 21 and the breakdown amount constituting the account transfer amount. If the contents are correct, it is regarded as the final payment approval, and information indicating the approval is transmitted to the center host 31 as the transfer confirmation information (step S10). The information may be sent out by directly accessing a homepage prepared by the data management center for approval, or by transferring an approval / disapproval result file to the data management center 30. A method may be used. When the center host 31 receives the transfer confirmation information from the debtor, it writes the contents in the corresponding loan data on the debt management database 32 (step S11), and simultaneously transfers the transfer confirmation information to the creditor terminal 11 of the creditor. It transmits (step S12).
As means for notifying the creditor of the transfer confirmation information, means such as e-mail or file transfer is used. At this point, the creditor transfers the debtor's transfer confirmation information received from the center host 31 to the data management center 3 using his / her creditor terminal 11.
0 can be confirmed by browsing the homepage provided by the company, and it is possible to grasp the determined deposit amount before the actual transfer (payment for billing) from the debtor to the account (step) S13).

The center host 31 creates transmission data to the financial institution 40 to perform the transfer, based on the transfer confirmation information source received from the debtor in step 11 (step S14).
The transfer data created here is held in the data management center 30 until the actual transfer date, and is transmitted to the financial institution 40 at the transfer date (step S1).
5). In step S15, since the actual amount has been transferred to the financial institution 40, the creditor will receive payment information from the financial institution at a later date. When the creditor receives the deposit information, the creditor confirms the actual deposit amount, and if the amount matches the content of the transfer confirmation information that has been grasped in advance, it is considered that the settlement of the loan has been performed, and the settlement confirmation is performed. The information is transmitted from the creditor terminal 11 to the center host 31 (step S
16). The means for notifying the center host 31 of the payment confirmation information may be realized by directly accessing a homepage prepared by the data management center 30 and inputting a confirmation that the payment has been confirmed. A method of transferring the information to the management center may be used.

When the center host 31 receives the settlement confirmation information from the creditor, the center host 31 regards the corresponding credit data in the credit and debt management database 32 as having been settled by the amount of the transfer, and
The content is updated (step S17). If the credit data has not yet been settled for the entire amount, the data is still in the form of a bond, and the information is transmitted to the debtor as debt data (hereinafter, step S3 and thereafter). Will be repeated). vice versa,
When the total amount of the receivables data has been settled, the receivable is completed.

(2) Second Embodiment Next, this embodiment will be described in detail with reference to FIGS. FIG. 4 is a flowchart of the present embodiment. In the first embodiment, the billing business unit 20 receiving the bill from the billing source business unit 10 pays by "account transfer".
The third embodiment differs from the first embodiment in that the settlement is performed by the “offset process” in which the loan is assigned to the claim source business unit 10 held by the user.

Referring to FIG. 4, first, as in the first embodiment, the claimant uses his / her creditor terminal 11 to access the credit input screen established by the data management center 30 on the Internet NW. The billing data is input on the displayed screen (step T1). The billing information input here is the same as in the first embodiment. Upon receiving the request information registration instruction from the requester, the center host 31 registers the request information input by the requester in the debt management database 32 (step T2). Also, the center host 31 transmits new debt information to the debtor terminal 21 of the billing destination, triggered by the receipt of the billing information registration command from the claimant as in step T2 (step T3). The notification of the registration of the new debt information may be performed by e-mail or by means of transferring a file describing the details of the debt.

Business unit 20 receiving the billing information
Then, the new debt information (claim information registered by the claimant) received by the own debtor terminal 21 is confirmed (step T).
4). Here, if the business unit 20 holds the receivables to the business unit 10 and desires to offset both receivables as the payment method of the debt information confirmed in step T4, the business unit 20 desires the offset processing. This is specified on the screen established by the data management center 30 on the Internet NW using his own debtor terminal 21, and transmitted to the center host 31 (step T5).

When the center host 31 receives the offset instruction input by the business unit 20 in step T5, the center host 31 obtains the charge information from the original business unit 10 and the information on the receivables held by the business unit 20 to the business unit 10. Then, a detailed amount calculation for the offset processing is performed. First, information such as the transfer amount of both receivables and the maturity date of receivables is obtained. Next, based on the acquired information, the interest / fees database is searched to calculate the amount of interest (or discount) associated with the relationship between the scheduled offset date and the maturity date of the receivable. Finally, the actual offset amount is obtained by adding the calculated interest amount to the amount of the receivables. After the calculation, the center host 31 transmits information such as the calculated credit number to be canceled and the amount thereof to the debtor terminal 21 of the business unit 20 (step T6). The notification of the offset information is performed using means such as electronic mail or file transfer.

The offset application information calculated in step T6 is also notified to the business unit 10, which is the sender of the original bill (step T7). Means such as e-mail and file transfer are used for the notification of the offset application information. In the business unit 20, the data management center refers to the content of the received offset application information on a screen established on the Internet NW, and if the content is correct, the data management center approves the execution of the offset process, and accepts the approval data. Is transmitted to the center host 31 (step T8).

On the other hand, the business unit 10 also refers to the contents of the received offset application information on the screen established by the data management center on the Internet NW, and approves the execution of the offset processing if the contents are correct. The approval data is transmitted to the center host 31 (step T9). The center host 31 considers that the settlement has been confirmed when receiving the approval data of the offset application processing from both the business units 10 and 20, and updates the data of the receivable used in the offset application on the database (step T10). ). In addition, both the business units 10 and 20 are notified that the settlement of both the claims has been confirmed by the offset application by means such as e-mail or file transfer (step T11). As described above, by outsourcing the operation of performing the process of canceling the receivables and payables to the data management center 30, it is possible to increase the efficiency of the process of confirming the cancellation between the business units in each business unit.

[0035]

As described above, according to the present invention, the following effects can be obtained. The first effect is that when the debtor approves the bank transfer information calculated automatically by the data management center (creates the transfer confirmation information), the debtor performs the automatic allocation process (automatic clearing process) with the corresponding receivables. This is performed automatically by the center, thereby reducing the burden of the creditor on the settlement of the loan during a specific period such as the end of the month. The second effect is that the automatic allocation processing at the data management center allows creditors to obtain payment information for receivables without waiting for actual deposits, thereby enabling quick funding planning. is there.

The third effect is that, by the automatic allocation processing in the data management center, the creditor can save the trouble of investigating the combination of a plurality of credits for one payment from the debtor as in the past. In other words, the time for settlement work can be significantly reduced. The fourth effect is that the transfer amount and interest / discount information for the debtor can be calculated independently by the creditor by the transfer amount automatic calculation process and the automatic allocation process at the data management center. This means that individual expenses can be ascertained just by referring to the receivable reconciliation information, leading to more efficient operations. The fifth effect is that the data management center immediately notifies the debtor of the credit information registered by the creditor, and the debtor can always refer to the latest debt information before receiving the actual invoice As a result, the risk of late payments is reduced, and the associated interest rates are less likely to occur.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram of an embodiment of the present invention.

FIG. 2 is a functional block diagram of components in the embodiment, (A) is a creditor terminal, (B) is a debtor terminal,
(C) is a functional block diagram of each of the center hosts.

FIG. 3 is a flowchart of the first embodiment of the present invention.

FIG. 4 is a flowchart of a second embodiment of the present invention.

FIG. 5 is a system configuration diagram of a conventional example.

[Explanation of symbols]

 NW Network SS1 Receivable and Debt Management System 10 Billing Source Business Unit 11 Creditor Terminal 20 Billing Destination Business Unit 21 Debt Obligor Terminal 30 Data Management Center 31 Center Host 32 Debt Management Database 33 Interest / Commission database 40 ... Financial institutions

Claims (4)

[Claims] 1. A creditor terminal to which a creditor inputs credit information, a debtor terminal to which a debtor inputs debt information, and a center host for processing credit / debt information between the creditor and the debtor And a communication network in which the creditor terminal, the debtor terminal, and a center host are connected, and the center host collectively manages the debt / debt information and settlement information associated with the debt / debt information. A credit and debt management system, wherein the creditor terminal and the debtor terminal share the credit / debt information and the settlement information possessed by the center host via the communication network. 2. The credit and debt management system according to claim 1, wherein a financial terminal of a financial institution in which the creditor and the debtor have a transaction account is connected to the center host. 3. When the creditor and the debtor have the trading account, the payment accompanying the settlement information is
The credit and debt management system according to claim 2, wherein the credit and debt management is performed by an account transfer to the transaction account. 4. The method according to claim 1, wherein when the debtor has a claim against the creditor, the claim from the creditor is settled by offsetting the claim against the creditor. Accounts payable management system.