JP2010049348A - Asset management system and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To prevent a payment mistake of a debtor, and to facilitate confirmation of money reception by a creditor. <P>SOLUTION: In an asset management system having a server for managing assets and payment of debtors, the server has: an asset management DB for managing the assets of the debtors; and a contract management DB for managing contract information concluded between the debtors and creditors. The server creates payment data related to assets for a prescribed period charged in each debtor in reference to the asset management DB and the contract management DB, and transmits them to a terminal of the debtor. The server receives the already confirmed payment data and asset data transmitted from the terminal of the debtor, creates application data for payment of that month in each debtor based on the already confirmed payment data, and transmits them to the terminal of the debtor so as to confirm billing contents. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to an asset management system and method, and more particularly to an asset management system capable of generating payment data of an amount charged as a consideration for provision of goods and services from a creditor to a debtor and confirming payment details. And its management method.

  When a contract for the sale of goods or services (hereinafter referred to as goods, etc.) is concluded between the seller (creditor) and the buyer (debtor), the seller is charged with the accounts receivable at the stage of providing the goods, etc. Payables are recorded after the received goods are accepted. In addition, in a lease or rental contract for goods or services (hereinafter referred to as assets) concluded between a creditor and a debtor, the debtor is obliged to pay a billing fee at regular intervals (for example, every month). When the debtor transfers the billing amount to the account of the financial institution designated by the creditor every month, the creditor matches the receivable or billing fee with the transferred item and amount, and clears the receivable.

  This work for clearing accounts receivable requires a lot of labor for creditors who have many contracts. On the other hand, for the debtor, mistakes in payment of accounts payable, lease and rental costs induce unnecessary work for correction and post-processing of the payment, further complicating payment management.

  Conventionally, with regard to a payment settlement management system, for example, in Patent Document 1, when a total amount related to a plurality of billing matters is settled in a lump, in order to identify which billing matter the settlement is for, A settlement management system is disclosed in which billing details are easily erased by matching settlement details data and billing details data using agents arranged on both the debtor side and the creditor side.

  Further, in Patent Document 2, a data management center that mediates between a billing side and a payment side uses a data identifier that is unified to billing detail data created by the billing side and payment detail data created by the payment side, so that individual accounts receivable An individual accounts receivable application system for quick and accurate application is disclosed.

JP 2001-350929 A JP 2002-32698 A

  The above-mentioned patent document describes a mechanism for canceling accounts receivable and billing details. However, for example, how to prevent debtors from making payment mistakes for payment projects that require periodic payments based on leases and rental contracts, and how easy it is for creditors to confirm the payment of the invoiced amount. There is no mention of what to do.

  The purpose of the present invention is to manage assets that prevent payment by the obligor and make it easy for the creditor to confirm the payment of the case where payment is made periodically based on the contract between the creditor and the obligor. It is to provide a system and method.

The asset management system according to the present invention is preferably an asset including a server that connects a plurality of creditor terminals and a debtor terminal via a network and manages the assets of the debtor and payments to the creditor. A management system, wherein the server includes a database (DB) and a processing device,
The DB includes an asset management DB that manages asset information of the debtor, and a contract management DB that manages contract information between the creditor and the debtor.
The processing apparatus uses the asset information managed by the asset management DB and the contract information managed by the contract management DB to create payment data related to the matter for a predetermined period, which is charged to the debtor. Data creation means, means for transmitting the payment data and the asset information created by the creation means to the debtor's terminal, and the payment confirmed by the debtor sent from the debtor's terminal A means for receiving data payment and the asset information; a means for creating a billing payment statement for the predetermined period for each creditor based on the confirmed payment data; and And a means for transmitting to the user's terminal.

The asset management method according to the present invention preferably manages a debtor's assets and payments to the creditor using a management server that connects a plurality of creditor terminals and debtor terminals via a network. An asset management method for
Storing and managing asset information of the debtor in the asset management DB; storing and managing contract information between the creditor and the debtor in the contract management DB; A step of creating payment data relating to a matter of a predetermined period, which is charged to the debtor, using the asset information managed by the asset management DB and the contract information managed by the contract management DB by processing of the server Transmitting the created payment data and the asset information to the debtor's terminal; and payment of the payment data confirmed by the debtor and the asset transmitted from the debtor's terminal A step of receiving information, a step of creating payment request data for the predetermined period for each creditor based on the confirmed payment data and the asset information by processing of the management server, and the generated payment And transmitting the calculated data to 該債 owner of the terminal, configured as a method asset management, characterized by having a.

  According to the present invention, payment data can be created and confirmed by the obligor with respect to a case in which payment is made periodically based on a contract between the creditor and the obligor. It is possible to make it easier for creditors to confirm payment.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 shows a configuration example of an asset management system.
This system has an asset management service company (hereinafter simply referred to as a service company) 1, a plurality of creditors 2 who are providers of goods or services (referred to as goods), and is obligated to pay for the provision of goods, etc. The debtor 3 and each information processing station of the financial institution 4 are connected via a network such as the Internet. Each information processing station of the creditor 2, the debtor 3, and the financial institution 4 has a client terminal including an input / output unit, a storage unit, and an information processing unit, for example. Hereinafter, the service company 1, the creditor 2, the debtor 3, and the financial institution 4 mainly refer to an information processing station having these processing means.

Creditor 2 is a plurality of companies that provide various products to debtor 3, among which companies that provide products, etc. based on rental or lease contracts, insurance companies, maintenance service companies, etc. included.
The debtor 3 is a customer of the service company 1, and includes, for example, a manufacturing company, an administrative company, and a public company such as a municipality. appear.

The service company 1 manages the assets of the debtor 3, and performs characteristic processing operations such as creation of payment data for the creditor 2 and confirmation of the payment data, and further, creation of a bill of payment for the debtor.
In the illustrated example, one obligor 3 is shown, but a plurality of obligors 3 are connected to the network, and the service company 1 can provide service operations to these plural obligors. In this case, a debtor ID for identifying each debtor 3 is given.

  In addition, an account of the creditor 2 is opened in the financial institution 4, and the debtor 3 transfers the billing fee to the account according to the payment request from the creditor 2. Although one financial institution 4 is shown in the figure, the creditor may actually use a plurality of financial institutions, and the plurality of financial institutions 4 are connected to the network.

The service company 1 is the core of this system, and includes a management server 10 that performs information processing for managing debtor assets, and a management database (hereinafter simply referred to as DB) that stores various information for asset management. ) 12, and a transmission / reception unit 14 connected to the network, a display 15, and an input device 16.
The management server 10 is a computer having a processor (processing device) that executes asset management and payment work by executing a program, and a storage device such as a memory and a hard disk.

  The management DB 12 has several DBs for asset and payment management. That is, the management DB 12 includes an asset management DB 121 that manages the debtor's assets, a contract management DB 122 that manages information related to a contract concluded between the debtor and the creditor regarding provision of goods, etc. It has a plurality of DBs such as a payment data management DB 123 for managing payment of a price generated to a creditor and a billing / payment statement management DB 124 for managing billing / payment details in order to confirm the contents of billing to the creditor. . The configuration of each management DB will be described later with reference to FIGS.

  The management server 10 of the service company 1 executes a related application program on the processor, thereby allowing the asset management unit 101, the contract management unit 102, the payment data creation unit 103, the payment confirmation processing unit 104, the asset update unit 105, the deposit cancellation Each function of the deposit processing unit 106, the bill issuing unit 107, the bill creation issuing unit 108, and the deposit application processing unit 109 is realized.

  The asset management unit 101 performs processing for registering and managing the asset information of the debtor 3 in the asset management DB 121. Specifically, the information of the asset newly acquired by the debtor 3 input from the input device 16 is registered in the asset management DB 121, and unnecessary information is deleted from the DB.

  The contract management unit 102 performs processing for managing contract information that the debtor 3 exchanges with the creditor 2 in the contract management DB 122. Since the debtor 3 normally has contracts with a plurality of creditors, the creditor 3 is identified and managed for each creditor. Specifically, the process of registering the contract information newly entered by the debtor 3 in the contract management DB 122, the process of deleting unnecessary information from the contract management DB 122, which is input from the input device 16, and the contract contents Is changed (for example, the contract period is extended or shortened, the contract amount is changed, the payment period is changed, the contract is canceled halfway, etc.), update processing such as changing the contract management DB 122 is performed for the changed part.

The payment data creation unit 103 creates payment data that occurs periodically (for example, every month) for the debtor 3. This process acts on behalf of the payments that the obligor originally makes, and inquires the creditor 2 for the monthly payment data that has been created, and responds to the monthly claims between the creditor and the obligor. We hope to prevent payment mistakes. This process refers to the asset management DB 121 and the contract management DB 122 of the debtor 3 and extracts payment items related to the assets that are paid in the current month in the contract, and payment data corresponding to the assets of each department of the debtor. It is a process that collects and collects.
Payment data created by the payment data creation unit 103 is stored in the payment data management DB 123. The storage format of the payment data management DB 123 will be described later.

  The payment confirmation processing unit 104 is a process for transmitting the monthly payment data created by the payment data creating unit 103 to the debtor 3 and confirming the payment contents. For example, when one obligor 3 pays to a plurality of creditors 2, the processing unit 104 divides and arranges payment contents for each creditor and transmits them to the obligor 3 for confirmation. Receive the results.

  The contents received from the debtor 3 include information indicating the result of the debtor confirming the contract and confirming the payment in the current month, and the change status of the debtor's assets. The asset change corresponds to, for example, a case where the installation department of a personal computer, which is one of the assets, is changed, the cost burden destination is changed, the manager in charge is changed, or the lease contract is canceled. The processing on the debtor 3 side will be described later.

  The asset update unit 105 is a process of updating the asset information by reflecting the change in the registration information of the asset management DB 121 when the asset of the debtor 3 is changed as a result of the payment confirmation process. The asset update unit 105 may be integrated into the asset management unit 101 as one process.

  The billing / payment statement creation unit 106 creates payment data confirmed by the debtor 3 in the payment confirmation processing unit 104 as a billing / payment statement for each creditor. This is to send the billing / payment details to each creditor 3 via the network, and let the creditor verify the billing / payment details of this month against the transfer amount to the designated account of the financial institution. It is processing. The created billing / payment details are stored in the billing / payment details management DB (FIG. 5) as a record.

  The billing / payment statement confirmation processing unit 107 transmits the billing / payment statement created by the billing / payment statement creation unit 106 to each creditor 3 via the network so that the billing / payment details of the current month can be confirmed. It is processing of. The result confirmed by the creditor 2 is received via the network in the form of the billing / payment details.

  As a result of the correct confirmation of the debtor 3, a check mark “L” is added to the payment confirmation item column of the details stored in the billing / payment details management DB. If a comment is received from the creditor, it will be entered in the remarks column. Depending on the creditor's confirmation results, the claims may be corrected.

  The invoice creation and issue unit 108 is a process for creating and printing and issuing an invoice for the service company 1 to issue an invoice to the debtor 3 on behalf of the creditor 2. When the claim from the creditor to the debtor is correct, the invoicing issuing and issuing unit 108 refers to the billing / payment statement management DB to obtain the bill for the current month billed from the creditor to the debtor 3. Create and print.

As shown in FIG. 6, the invoice printed and issued displays the contents of the bill for the current month and the fact that the creditor is acting on behalf of the creditor. This invoice is sent to the payment department such as the debtor's cashier.
In the case where there are a large number of creditors for one obligor, the service company 1 may not be entrusted with the issuance of a bill. In that case, the bill created by the creditor is sent to the debtor as before. Of course, the content matches the result confirmed by the billing / payment statement confirmation processing unit 107.

When the debtor transfers the payment amount requested by the creditor to the creditor's designated account, the deposit application processing unit 109 obtains the transfer information including the transfer amount from the creditor 2 and charges / pays This is a process of checking against the payment details for the creditor stored in the statement management DB 123 and deleting it. If all items requested by multiple creditors for the current month are cleared, then that debtor's payment for the current month has been processed correctly.
When the application is correctly performed, for example, a check mark “” is recorded in the payment application confirmation column 532 of the item stored in the billing / payment statement management DB.

Next, the processing station of the debtor 3 will be described.
The debtor 3 is responsible for paying the terminal 31 such as a PC (personal computer) as a window for transmitting and receiving related information to and from the service company 1, a plurality of PCs 32 arranged in a plurality of departments, and a payment. It has a payment terminal 33 such as a PC arranged in a department (such as a depositing / dispensing department) and a transmission / reception unit 34 connected to the network. The PC 32 of each department is a PC arranged in a department such as the planning department, development department, or general affairs department of the company. Each PC and terminal are connected by an in-house LAN or an intra network.

Next, a configuration example of each management DB will be described.
FIG. 2 is a configuration example of the asset management DB 121.
It manages the asset status of the debtor who is the customer of the service company 1, and has an asset management DB 121 for each debtor. As shown in the figure, the asset management DB registers each information such as the debtor's property name, manufacturer name, number of properties, asset number, property unique ID, payee, and the like.
Note that the registered content of the asset management DB 121 is updated by the processing of the asset update unit 105.

FIG. 3 is a configuration example of the contract management DB 122.
The contract management DB 122 registers each information such as asset classification, contractor creditor company, transaction number, contract name, billing code, contract start date, contract end date, payment amount, payment method, contract amount, etc. to manage.

FIG. 4 is a configuration example of the payment data management DB 123.
The payment data management DB 123 stores payment data created by the payment data creation unit 103. This payment data includes items for confirming payment by the debtor and items for investigating the change status of assets based on information obtained from the contract management DB 122 and information obtained from the asset management DB 121. .
That is, it comprises a billing information column 41, a payment confirmation column 42, a property information column 43, and a change column 44. The payment confirmation column 42 and the change column 44 are permitted to be filled in by the person in charge of the relevant department of the debtor 3.

  The billing information column 41 includes information obtained from the contract management DB 122, such as asset classification, item number, contractor company name, transaction number, contractor name, billing destination code, contract start date, contract target date, and contract object. Includes property name, number of properties, contract amount, billing amount for the current month, and information on the recipient.

  The payment confirmation column 42 is a payment slip issuance confirmation column for filling in a check mark when the person in charge in the target department confirms the billing information and the payment confirmation department issues a payment slip to the depositing / dispensing department for this billing matter. 421, a payment confirmation amount 422 of the current month, and a deposit / department department confirmation column 423 for entering a check mark when the person in charge of the deposit / department department confirms the amount of the payment slip.

  The property information column 43 includes property information such as the debtor's property item number, installation department, property number, user, manufacturer name, installation location, property type name, and the like, which is information obtained from the asset management DB 121. The person in charge of each department refers to the property information and confirms whether or not there is any change.

  The change column 44 is a column for entering change information when there is a change as a result of checking the property information by the person in charge of the related department. The change information includes, for example, movement between departments of a property, change of a user or a person in charge of the property, and change of a payee.

FIG. 5 is a configuration example of the billing / payment details management DB 124.
The billing / payment details management DB 124 stores the details created by the billing / payment details creation unit 106. The details are divided by creditor's company. Billing information 51 includes asset classification, item number, company name, transaction number, contractor name, billed amount for the current month, and payment confirmation item 52 as a payment confirmation item 52. There are matters confirmed for (corresponding to 421 to 423 in FIG. 4).

  Furthermore, as a credit company column 53, there are columns of a deposit confirmation 531, a deposit application confirmation 532, and a remark 533. When the creditor 2 confirms the payment, a check mark “Re” is recorded in the payment confirmation column 531, and when the payment is canceled by the service company 1, “Re” is recorded in the payment application confirmation column 532. Is done.

Next, a series of processing operations from payment data creation to payment cancellation will be described with reference to FIG.
First, in the processing of the payment data creation unit 103 of the management server 10 in the service company 1, the asset management DB 121 and the contract management DB 122 are referred to extract a payment item for the current month and create payment data shown in FIG. 4 (7101). ). The payment item of the current month is a transaction that is paid monthly or periodically according to the contract and corresponds to the current month. The created payment data is transmitted to the debtor 3 and stored in the payment data management DB 123.

  At the processing station of the debtor 3, the window terminal 31 receives the payment data transmitted from the management server 10 of the service company 1, and temporarily stores it in the management DB 311 (7301). The received payment data includes payment items and asset information of a plurality of departments. The receiving terminal 31 divides the payment data received by the operation of the manager for each department and transmits it to the PC 32 of each department and the payment terminal 33 of the depositing department via the in-house LAN (7302).

  The person in charge of each unit confirms the billing information and property information of the received payment data (7303), and after confirming the payment details, creates a payment slip for the payment case and sends it to the depositing / dispensing department. At that time, if an invoice arrives from the creditor, it is attached to the payment slip.

  Then, a check mark is entered in the payment slip issue confirmation field 421. Further, if there is a change in the property information, the change content is entered in the change column 44 (7304). Then, the completed data including the confirmation result is transmitted from each unit PC 32 to the window terminal 31.

  The window terminal 31 receives the confirmation result transmitted from each part PC, and reflects the confirmation result and the change status in the payment data previously stored in the management DB 311 (7305). Upon receipt of confirmation responses from all the related departments and reflecting them in the payment data, the window terminal 31 transmits the reflected payment data to the depositing and receiving department (Step 7306).

  When the payment terminal 33 of the cashier department receives the confirmed payment data transmitted from the window terminal 31, the person in charge of payment pays the contents of the payment slip sent from the person in charge of each department and the received payment data. (7307). If the result of the verification is correct, a check mark is entered in the payment data entry / exiting department payment confirmation column 423. Then, the payment data in which all the confirmation results are entered is transmitted to the window terminal 31.

  Upon receiving the payment confirmation result from the payment terminal 33, the window terminal 31 transmits the confirmed payment data and the property information change data to the management server 10 of the service company 1 (7308).

When the management server 10 receives the payment data and the change data as the confirmation result from the debtor 3, it reflects them in the information stored in the payment data management DB 123 (Step 7103). Further, the change data is updated by reflecting it in the registration information of the asset management DB 121 (Step 7104).
Then, based on the confirmed payment data, the bill payment details are created for each creditor and transmitted to each creditor (Step 7105). Further, the billing payment details are stored in the billing / payment details management DB 124 (Step 7106).

The creditor 2 receives the billing / payment details transmitted from the service company 1, and the responsible person confirms the contents (7201). If the result of the confirmation is correct, a check mark is entered in the payment confirmation column 531 of the billing / payment details and transmitted to the service company 1 (7202). If the result of the confirmation is incorrect or if there is a special comment, that fact is entered in the remarks column 533.
If the creditor 2 does not entrust the issuance of the invoice to the service company 1, the creditor 2 creates an invoice himself and sends it to the debtor.

When the service company 1 receives the confirmation result of the billing / payment details transmitted from the creditor 2, the service company 1 reflects it in the storage information of the billing / payment details management DB 124 (Step 7107). That is, the information in the payment confirmation column 531 and the remarks column 533 is updated.
If the bill creation is performed on its behalf, the bill is created and printed (7108). The issued invoice is sent to the payment department of the debtor 3 (Step 7109).

  The payment department of the debtor 3 confirms the contents of the invoice and the previously confirmed payment data, and deposits the billed amount into the designated account of the creditor's designated financial institution (7309). Since the invoice is sent to each creditor, this remittance process is performed for each creditor.

  When there is a deposit in the designated account of the creditor 2, the creditor receives a deposit notification from the financial institution by the EB (electronic banking) system (7203). Then, the received payment notice is transmitted to the service company 1 (7204).

  When the service company 1 receives the payment notification, the service company 1 performs a payment application process by collating the notification with information stored in the billing / payment statement management DB 124 (Step 7110). As a result, if the billing content matches the payment notification, a check mark is entered in the payment application confirmation column 532. Then, the application result is transmitted to the creditor 2 (7110).

  The above processing is performed, for example, every month for each debtor provided by the service company 1. It should be noted that processing that is not partially entrusted, such as payment cancellation processing, invoice proxy issuance processing, and the like may differ depending on the content of the request from the creditor.

Next, another embodiment will be described with reference to FIG.
In this example, the service company 1 refers to the contract management DB 122 on the assumption that the contract management DB 122 has been updated accurately (registration of new contract, change of contract contents, reflection of mid-term cancellation, etc.) This is an example in which a monthly invoice is created, and the obligor 3 is checked in parallel with the confirmation of the created invoice and a payment data creation process 7101.
Therefore, processing steps 8101 and 8102 are added as compared with the embodiment of FIG. 7, and the processing steps 7202 and 7101 to 7109 of FIG. 7 are unnecessary.

  That is, in the processing of the bill issuing unit 108, the management server 10 refers to the contract management DB 122 to create and issue a bill (FIG. 6) for the next month's payment request to the debtor 3 (8101). . In this case, all the billing contents of the bill can be acquired from the information registered in the contract management DB 122. The issued invoice is sent to the depositor's account department of the debtor 3 by mail or the like (8102).

Further, the management server 10 refers to the asset management DB 121 and the contract management DB 122 as the payment data creation process 7101 in order to confirm the payment data of each part of the debtor 3 for the next month bill to the debtor 3. Next, the payment item for next month is extracted, and the payment data shown in FIG. 4 is created (Step 7101). The created payment data is transmitted to the debtor 3 and stored in the payment data management DB 123 (7102).
By the way, since the billing item for which the billing amount has to be paid by the end of next month needs to be sent from the service company 1 to the debtor 3 by the end of this month, the above processing (8101-8102 and 7101-7102) is By the end of this month.

In the debtor 3, when the window terminal 31 receives payment data for next month, the window terminal and each unit perform the same processing (7302 to 7308) as described above.
However, the processing 7307 ′ at the cashier department is slightly different, and the cashier department has three payment slips sent from each part, payment data sent via the window terminal 31, and invoice sent from the service company 1. Collate. If the result of the verification is correct, a procedure for remitting the amount of the invoice to each creditor is performed (7309).

The subsequent processing in the management server 10 of the service company 1 is the same as the processing in FIG. 7 (7103 to 7106).
The creditor 2 receives and stores the next month's billing / payment details confirmed by the contractor of the debtor 3 (7201 '). In this case, since the service company 1 issues a bill on behalf of the creditor 2, the creditor 2 does not need to confirm the contents of the billing / payment details. It is sufficient for the creditor 2 to recognize the fact that the contractor of the debtor 3 is performing according to the contract, such as creating a payment slip.
The application process for the next month's deposit is the same as in FIG. 7 (7203-7111).

As mentioned above, although the Example of this invention was described, this invention is not limited to the said Example, It can implement by various deformation | transformation and application.
For example, in the above-described embodiment, the management server 10 of the service company 1 is responsible for issuing and issuing an invoice for the creditor 2 and canceling the payment. If not, the invoice creation issuance processing unit 107 or the deposit application processing unit 109 is not necessary.

Moreover, when there are a plurality of creditors 2 for one debtor 3, not all creditors are acting for billing issuance and payment cancellation. Needless to say, in the case where the invoicing issuance or payment application is performed only at the request of a specific creditor, the invoicing issuance process or the payment application process is performed only for those creditors. Of course, when the service company 1 does not perform these processes, the creditor will perform these processes.

The figure which shows the structural example of the asset management system by one Example. The figure which shows the structural example of asset management DB121. The figure which shows the structural example of contract management DB122. The figure which shows the structural example of payment data management DB123. The figure which shows the structural example of billing / payment details management DB124. The figure which shows the example of the bill issued on behalf of the agency. The flowchart which shows a series of process operation | movement of payment data preparation-payment application cancellation in one Example. The flowchart which shows a series of process operation | movement of payment data preparation-payment cancellation in another Example.

Explanation of symbols

1: Service company 2: Creditor 3: Obligor 4: Financial institution 10: Management server 12: DB 14: Transceiver
101: Asset management unit 102: Contract management unit 103: Payment data creation unit
104: Payment confirmation processing unit 105: Asset update unit 106: Billing / payment details creation unit 107: Billing / payment details confirmation processing unit 108: Invoice creation / issuance unit
109: Deposit application processing unit 31: Window terminal 32: PC 33: Payment terminal 34: Transmission / reception unit
121: Asset management DB 122: Contract management DB 123: Payment data management DB 124: Billing / payment details management DB

Claims (10)

An asset management system comprising a server for managing a plurality of creditors' terminals and debtors' terminals via a network, and managing the debtors' assets and payments to the creditors,
The server has a database (DB) and a processing device,
The DB includes an asset management DB that manages asset information of the debtor, and a contract management DB that manages contract information between the creditor and the debtor.
The processing apparatus uses the asset information managed by the asset management DB and the contract information managed by the contract management DB to create payment data related to the matter for a predetermined period, which is charged to the debtor. Data creation means;
Means for transmitting the payment data and the asset information created by the creating means to the debtor's terminal;
Means for receiving payment of the payment data confirmed by the debtor and the asset information transmitted from the debtor's terminal;
Means for creating a billing payment statement for the predetermined period for each creditor based on the confirmed payment data;
Means for transmitting the created bill payment details to the creditor's terminal;
An asset management system comprising: The DB further includes a payment data management DB for storing the payment data created by the payment data creation means for each predetermined period in association with related asset information for each billing item,
The processing device includes means for updating the contents of the payment data management DB based on the confirmed payment data and the asset information transmitted from the debtor's terminal and received via the receiving means. The asset management system according to claim 1, comprising: The processing device has means for updating the contents of the asset management DB based on the confirmed asset information transmitted from the debtor's terminal and received via the receiving means. The asset management system according to claim 1 or 2. The asset management system according to any one of claims 1 to 3, wherein the processing device further includes a bill payment details issuing means for generating and issuing a bill payment details for the debtor. The asset management system according to any one of claims 1 to 4, wherein the DB includes a bill payment details management DB that stores the payment bill details created by the bill payment details creation means. The processing device further includes information related to the payment from the debtor for the bill payment details transmitted from the creditor, and billing information of the related billing details stored in the bill payment details management DB. 6. The asset management system according to claim 5, further comprising a deposit cancellation processing means for collating and canceling the deposit. An asset management method for managing a debtor's assets and payments to the creditors using a management server that connects a plurality of creditors 'terminals and debtors' terminals via a network,
Storing and managing asset information of the debtor in an asset management DB;
Storing and managing contract information between the creditor and the debtor in a contract management DB;
By the processing of the management server, using the asset information managed by the asset management DB and the contract information managed by the contract management DB, the payment data related to the matter for a predetermined period is charged to the debtor. And steps to
Transmitting the created payment data and the asset information to the debtor's terminal;
Receiving payment of the payment data confirmed by the debtor and the asset information transmitted from the debtor's terminal;
Creating billing payment details for each predetermined period for each creditor based on the confirmed payment data and the asset information by processing of the management server;
Transmitting the created bill payment details to the creditor's terminal;
An asset management method characterized by comprising: Storing the created payment data for each predetermined period in a payment data management DB in association with asset information related to each billing matter;
Updating the contents of the payment data management DB or the asset management DB based on the confirmed payment data and the asset information transmitted from the debtor's terminal by the processing of the management server;
The asset management method according to claim 7, further comprising: 9. The asset management method according to claim 7, further comprising a step of creating and issuing a bill payment statement for the debtor by processing of the management server. Storing the billing statement created in the billing payment statement creation step in a billing payment statement management DB;
Information related to the payment from the debtor for the bill payment details sent from the creditor by the processing of the management server, and billing information of the related billing details stored in the bill payment details management DB The asset management method according to any one of claims 7 to 9, further comprising a step of collating and canceling the payment.

Images