JP2017174389A - Credit and debt management device, credit and debt management method, and credit and debt management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a credit and debt management device for setting credit and debt management information on a system to facilitate operation or management even when the credit and debt management information is changed or added.SOLUTION: When transaction destination data are selected by a user, business office data and department data included in basic information corresponding to the transaction destination data are displayed in a changeable manner, and when the basic information is changed by the user, credit and debt management information including change data including business office data of a credit and debt management business office after change and/or department data of a credit and debt management department after change and unchanged data of the basic information is acquired, and a user is urged to input transaction detailed data including an amount of money and a transaction date and a transaction method corresponding to the credit and debt management information, and transaction data including the credit and debt management information and the transaction detailed data are acquired, and the acquired transaction data are registered.SELECTED DRAWING: Figure 3

Description

  The present invention relates to a claim management apparatus, a claim management method, and a claim management program.

  According to Patent Document 1, this system and process can be used for electronic submission of information using a client system, automatic transmission of information, and a final month-end general ledger for clearing receivables to client users. It facilitates the monitoring / reporting / management of receivables that are operational on the web including the interface. And the remittance processing module needs an application that checks the elapsed days of the receivable and remits the payment, and has several functions, such as accepting funds in a foreign currency or reporting the funds required for reporting purposes. A method, apparatus, and computer program for managing an accounting system interface having a function of translating into currency are disclosed.

Special table 2003-532230 gazette

  However, in Patent Document 1, since the debt management information is managed by the master in association with the contents set for the business partner, it is necessary to add a business partner whenever there is a change or addition to the credit management information, There has been a problem that operation and management become complicated when the number of cases becomes enormous.

  The present invention has been made in view of the above problems, and by setting the claim management information on the system, the claim can be easily operated and managed even if the claim management information is changed or added. An object of the present invention is to provide a debt management device, a debt management method, and a debt management program.

  In order to solve the above-described problems and achieve the object, a claim management apparatus according to the present invention is a claim management apparatus including a storage unit and a control unit, wherein the storage unit is a transaction of a business partner. Basic information storage means for storing basic information in which the business data of the initial display receivables and debts management office and the initial display receivables and debts management department are linked, and the supplier Transaction data storage means for storing transaction data relating to claims or debts with respect to the customer, including the data, and when the customer data is selected by the user via the input device, the control unit The office data and the department data included in the basic information corresponding to the destination data are displayed on the output device in a changeable manner, and the basic information is changed by the user via the input device. In this case, change data including the post-change data of the receivables and debt management office and / or department data of the post-change receivables and liability management department, and receivables and debt management information including the unchanged data of the basic information Basic information display means, controlling the user to input transaction detail data including an amount, a transaction date, and a transaction method corresponding to the claim management information via the input device, and the claim management information Transaction data acquisition means for acquiring transaction data including the transaction detail data, and transaction data registration means for registering the transaction data acquired by the transaction data acquisition means in the transaction data storage means. And

  Further, in the claim management apparatus according to the present invention, the basic information storage means further stores the basic information in which currency data of a basic currency is linked to the customer data, and the basic information display means includes: When the customer data is selected by the user via the input device, the office data, the department data, and the currency data included in the basic information corresponding to the customer data are output to be changeable. When the basic information is changed by the user via the input device, the office data of the changed debt management office, the department data and / or change of the changed debt management department The change data including currency data of a later currency, and the claim management information including unchanged data of the basic information are acquired.

  Further, in the claim management apparatus according to the present invention, the storage unit further includes input authority storage means for storing input authority data related to the claim management office and the claim management department that the user is not authorized to input. The control unit further comprises an input authority check means for checking the input authority of the changed claim management office and the changed claim management department, and the basic information display means further comprises: When the input authority check means determines that the input authority is not present, an error notification is output via the output device.

  In addition, the claim management apparatus according to the present invention, the control unit further comprises a linkage check means for checking the linkage between the changed claim management office and the changed claim management department, The basic information display unit further outputs an error notification via the output device when the pegging check unit determines that the pegging is not performed.

  In the claim management apparatus according to the present invention, the transaction data is collection schedule data related to the collection scheduled for collection or payment schedule data related to the payment scheduled for payment.

  Further, in the claim management apparatus according to the present invention, the transaction data acquisition means further includes the claim for each same claim management office or each claim management department based on a plurality of the collection schedule data. Debt balance data including the total amount of the debt, or based on a plurality of the payment schedule data, the debt balance including the total amount of the debt for each of the same debt management facility or each debt management department Data is acquired, and the transaction data registration means further registers the bond balance data or the debt balance data in the transaction data storage means.

  In addition, the claim management method according to the present invention is a claim management method for causing a claim management apparatus comprising a storage unit and a control unit to execute the claim management method. A basic information storage means for storing basic information in which the business data of the initial display receivables and debt management office and the initial display receivables and debts management department are linked, and the supplier data. Transaction data storage means for storing transaction data relating to claims or debts with respect to the customer, and executed by the control unit, when the customer data is selected via the input device by the user, the transaction The office data and the department data included in the basic information corresponding to the destination data are displayed on an output device in a changeable manner, and the basic information is changed by the user via the input device. If there is a change, the change data including the post-change data of the debt management office and / or the post-change department data of the credit management department, and the credit management information including the unchanged data of the basic information A basic information display step to be acquired; and control to allow the user to input transaction detail data including an amount, a transaction date, and a transaction method corresponding to the claim management information via the input device, and the claim management Transaction data acquisition step for acquiring transaction data including information and the transaction detail data, and transaction data registration step for registering the transaction data acquired in the transaction data acquisition step in the transaction data storage means. It is characterized by.

  The debt management program according to the present invention is a credit management program for causing a credit management device comprising a storage unit and a control unit to execute the storage unit. A basic information storage means for storing basic information in which the business data of the initial display receivables and debt management office and the initial display receivables and debts management department are linked, and the supplier data. Transaction data storage means for storing transaction data relating to claims or debts with respect to the customer, and when the customer data is selected by the user via the input device in the control unit, The office data and the department data included in the corresponding basic information are displayed on an output device in a changeable manner, and the user can change the basic data via the input device. If the information is changed, the receivables and payables including the changed receivables and payables management office data and / or changed receivables and debt management department data, and the basic data unchanged Basic information display step for obtaining management information, and controlling the user to input transaction detail data including an amount corresponding to the claim management information via the input device, a transaction date, and a transaction method, Transaction data acquisition step for acquiring transaction data including claims and debt management information and the transaction detail data; transaction data registration step for registering the transaction data acquired in the transaction data acquisition step in the transaction data storage means; Is executed.

  According to the present invention, by setting the right and debt management information on the system, there is an effect that the operation and management can be easily performed even when the credit and debt management information is changed or added.

FIG. 1 is a diagram illustrating an example of a conventional sales system. FIG. 2 is a diagram showing an outline of the present invention. FIG. 3 is a block diagram showing an example of the configuration of the claim management apparatus. FIG. 4 is a flowchart showing an example of processing in the claim management apparatus. FIG. 5 is a diagram illustrating an example of a system flow in the case of performing bond management of the bond management apparatus. FIG. 6 is a diagram illustrating an example of a system flow in the case of performing bond management of the bond management apparatus. FIG. 7 is a diagram illustrating an example of a system flow in the case of performing bond management of the bond management apparatus. FIG. 8 is a diagram illustrating an example of a system flow in the case of performing bond management of the bond management apparatus. FIG. 9 is a diagram illustrating an example of the master setting of the claim management apparatus. FIG. 10 is a diagram illustrating an example of the initial value setting process in the present embodiment. FIG. 11 is a diagram illustrating an example of an initial value setting process in the present embodiment. FIG. 12 is a diagram illustrating an example of a security check in the present embodiment. FIG. 13 is a diagram illustrating an example of a linkage check in a business office according to the present embodiment. FIG. 14 is a diagram illustrating an example of a system flow in the case of performing debt management of a credit / debt management device. FIG. 15 is a diagram illustrating an example of a system flow in the case of performing debt management of a credit / debt management device. FIG. 16 is a diagram illustrating an example of a system flow in the case of performing debt management of a credit / debt management device. FIG. 17 is a diagram illustrating an example of a system flow in the case of performing debt management of a credit / debt management device.

  Embodiments of the present invention will be described in detail with reference to the drawings. In addition, this invention is not limited by this embodiment.

[1. Overview]
The outline of the present invention will be described with reference to FIGS. FIG. 1 is a diagram illustrating an example of a conventional sales system. FIG. 2 is a diagram showing an outline of the present invention.

  As shown in FIG. 1, in a conventional sales system, receivable and liability management information is linked from the contents set for a business partner and managed by a master. Here, the claim management information included in the sales slip at the time of sales recording (at the time of credit recording) in the credit management has been determined by the billing master. However, according to this method, it is not possible to change the claim management information obtained from the billing master, or change after the claim is recorded, and the management and operation of the supplier may be complicated.

  For example, as shown in example (1) of FIG. 1, a single company (billing address A) is transacted at each location of the company (A sales office, B sales office, and C sales office). And there are two types of transaction currency: JPY (Japanese Yen) and USD (US Dollar), 6 suppliers (multiple company bases “3” multiplied by transaction currency type “2”) The code had to be set in the billing master.

  Further, for example, as shown in the example (2) of FIG. 1, when a transaction by EUR (Euro) is further generated for each base, it is necessary to set three business partner codes for each base in the billing destination master was there.

  Therefore, for example, as shown in example (3) of FIG. 1, after a transaction occurs at the Yokohama sales office for billing destination A, the Yokohama sales office is integrated with the Tokyo sales office, and the receivables are in the jurisdiction of the Tokyo sales office. If the change is made, it will be necessary to correct the receivables from the Yokohama office to the Tokyo office. However, in the conventional sales system, the journal entry is not generated just by changing the value of the billing master (the item of the billing master's credit management office is changed from “Yokohama” to “Tokyo”). It was necessary to provide new data for the billing destination master whose location is “Tokyo”. That is, in the conventional sales system, the correct business partner code needs to be newly set in the billing master.

  In this way, in the conventional sales system, it is necessary to add a new business partner every time receivables and payables management information is changed or added, and if the number of cases becomes enormous, operation and management become complicated. There was a problem. Therefore, although it is conceivable to manage in units of transaction data, setting the information for each transaction data may be complicated.

  Therefore, as shown in FIG. 2, the present embodiment provides a mechanism for giving the system a basic operation in order to reduce the load at the time of input when managing the claim management information and improve the accuracy. ing. Here, in the present embodiment, at the time of recording, the claim management office and transaction currency are declared.

  2, when a billing destination is selected by the user, when the billing destination is selected by the user, the bill management information is initially displayed at the time of sales input of the billing destination. Among them, the credit management office, the credit management department, and the currency (transaction currency) can be changed freely.

  As shown in FIG. 2, when there is a transaction at each base (A sales office, B sales office, C sales office) for one billing destination and the transaction currency is JPY, USD (for example, In the example (1) of FIG. 1 and the like, it is only necessary to correct and input the items of the credit management office and the currency in the initially displayed credit management information. Further, in the present embodiment, even when a transaction by EUR occurs (for example, the example (2) in FIG. 1), the currency item in the initially displayed bond management information may be corrected and input.

  Further, in the present embodiment, as shown in the example (3) in FIG. 1, even when the credit management office is changed during the transaction (for example, the example (3) in FIG. 1), the credit management office It is only necessary to input data for correcting the item from “Yokohama” to “Tokyo” to generate a transfer journal. As described above, in the present embodiment, when there is a plurality of bases and a plurality of transaction currencies in one billing destination, even when there is a change in the establishment, etc., one billing destination code (for initial display) It is possible to operate just by preparing the credit management information).

[2. Constitution]
An example of the configuration of the claim management apparatus according to the present embodiment will be described with reference to FIG. FIG. 3 is a block diagram showing an example of the configuration of the claim management apparatus.

  The claim and debt management apparatus 100 is a commercially available desktop personal computer. The debt management apparatus 100 is not limited to a stationary information processing apparatus such as a desktop personal computer, but is a portable personal computer such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer. It may be a type information processing apparatus.

  The claim and debt management apparatus 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part with which the claim management apparatus 100 is equipped is connected so that communication is possible via arbitrary communication paths.

  The communication interface unit 104 communicatively connects the bond management apparatus 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via a communication line. Here, the network 300 has a function of connecting the bond management apparatus 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

  The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores a computer program for giving various instructions to a CPU (Central Processing Unit) in cooperation with an OS (Operating System). As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) and a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, and an optical disk can be used. The storage unit 106 includes a basic information file 106a, a transaction data file 106j, and an input authority file 106k.

  The basic information file 106a stores the basic information in which the business data of the initial display is linked to the business data of the initial liability and the department data of the initial debt management department. To do. Here, the basic information file 106a may further store basic information in which the currency data of the basic currency is linked to the customer data. Further, the business partner may be a billing destination or a payment destination.

  Here, as shown in FIG. 3, the basic information file 106a includes a billing destination master 106b, a department master 106c, a payment destination master 106d, a basic information management master 106e, a person-in-charge master 106f, an operator configuration master 106g, and a sales common security master. 106h and a security pattern master 106i.

  The billing destination master 106b is a master that stores basic information including the business establishment data of the customer's receivables and debt management business establishment, the person-in-charge data, and the currency data of the basic currency.

  Note that the billing destination master 106b stores, for example, data such as a code (billing destination code and payment destination code), a billing destination name, a payment destination name, a billing destination and a representative office of the payment destination, a person in charge, and a base currency. The master which memorize | stores may be sufficient.

  The department master 106c is a master that stores basic information including business establishment data of a business partner's receivables and debt management business office and department data of a business partner's receivables and debt management department.

  The department master 106c includes, for example, a code (a department (affiliation department code) to which the person in charge belongs), a name of the department to which the person in charge who records the transaction slip belongs, and a business establishment (invoice management) The business unit), the billing department (credit management department), the payee's business office (debt management office), the payee department (debt management department), and the like. .

  The payee master 106d is a master that stores basic information including the business establishment data of the receivables and payable management office of the business partner (payee) and the currency data of the base currency.

  The payee master 106d may be a master that stores data such as a code (payee code), a payee name, a payee's representative office, a person in charge, a base currency, and the like.

  The basic information management master 106e is a master that manages whether basic information is initially displayed on the output device 114 in accordance with any one of the billing master 106b, the department master 106c, and the payment master 106d.

  The basic information management master 106e may include items such as an initial display category of a credit management establishment and an initial display category of a debt management establishment. Here, a variable indicating “Follow billing master” or “Follow department master” or the like can be set in the initial display classification of the receivable management office. It may be possible to set a variable or the like indicating “according to” or “according to department master”.

  The person-in-charge master 106f is a master that stores department data of the department to which the person in charge of the business partner belongs.

  The person-in-charge master 106f may be a master that stores, for example, a code (person-in-charge code), a person-in-charge name, a department of a business partner, and the like.

  The operator configuration master 106g is a master that stores operator data for identifying an operator (user).

  The operator configuration master 106g may be, for example, a master that stores an operator group to which an operator belongs, an operator name, and the like.

  The common sales security master 106h is a master that stores common sales security data related to basic information that can be input by the operator in association with the operator data.

  The common sales security master 106h may be a master that stores, for example, an operator group to which an operator belongs, a security classification, a pattern code, and the like.

The security pattern master 106i is linked to the sales common security data,
This is a master that stores the business pattern data of the customer's credit and debt management office, the department data of the customer's credit and debt management department, and / or the security pattern data related to the currency data of the transaction currency, which can be input by the operator.

  The security pattern master 106i may be a master that stores, for example, a pattern code and security elements (for example, items included in the basic information).

  The transaction data file 106j stores transaction data relating to a receivable or a debt with respect to a business partner, including business partner data. Here, the transaction data may include transaction detail data including the claim management information and the amount, the transaction date, and the transaction method corresponding to the claim management information. Further, the transaction data may be collection schedule data related to a collection schedule and payment schedule data related to a payment schedule. Further, the transaction data file 106j includes a receivable balance data including a total amount of receivables for each same receivable and debt management establishment or each receivables and debt management department based on a plurality of collection schedule data, and / or a plurality of payment schedule data. Based on the above, debt balance data including the total amount of debt for the same credit liability management establishment or credit liability management department may be stored.

  For example, the transaction data indicates the transaction amount with the business partner (billing or paying party), business establishment data of the business partner's receivables and debt management office, department data of the business partner's receivables and debt management department, and transaction currency. It may contain currency data.

  The collection schedule data includes, for example, a collection schedule Guid, a slip number, a slip line number, a business establishment (credit management office), a department (credit management department), a transaction currency, a billing destination, an amount, a scheduled collection date, and A recovery method or the like may be included.

  The payment schedule data includes, for example, payment schedule Guid, slip number, slip line number, establishment (debt management establishment), department (debt management department), transaction currency, payee, amount, estimated payment date, and The payment method may be included.

  The input authority file 106k stores input authority data relating to a claim management office and a debt management department for which the user does not have input authority.

  An input device 112 and an output device 114 are connected to the input / output interface unit 108. As the output device 114, a speaker (including a home television), a speaker, and a printer can be used. As the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that realizes a pointing device function in cooperation with the mouse can be used. In the following description, the output device 114 may be described as the monitor 114, and the input device 112 may be described as the keyboard 112 or the mouse 112.

  The control unit 102 is a CPU or the like that comprehensively controls the claim and liability management apparatus 100. The control unit 102 has an internal memory for storing a control program such as an OS, a program that defines various processing procedures, and necessary data, and performs various information processing based on these stored programs. Run. In terms of functional concept, the control unit 102 includes a basic information display unit 102a, a transaction data acquisition unit 102b, a transaction data registration unit 102c, an input authority check unit 102d, and an association check unit 102e.

  When the customer data is selected via the input device 112 by the user (operator), the basic information display unit 102a can change the office data and department data included in the basic information corresponding to the customer data. When the basic information is displayed on the output device 114 and changed by the user via the input device 112, the post-change data of the credit / debt management office and / or the post-change department / debt management department data Acquire receivables and debt management information including the changed data to be included and the unchanged data of the basic information.

  Here, when the business partner data is selected by the user via the input device 112, the basic information display unit 102a displays the office data, department data, and currency data included in the basic information corresponding to the business partner data. If the basic information is displayed on the output device 114 in a changeable manner and is changed by the user via the input device 112, the business data of the receivables and debt management office after the change, the department data of the receivables and debt management department after the change And / or change data including currency data of the changed currency, and debt management information including unchanged data of the basic information may be acquired.

  Further, the basic information display unit 102a may further output an error notification via the output device 114 when the input authority check unit 102d determines that there is no input authority. Further, the basic information display unit 102a may further output an error notification via the output device 114 when the pegging check unit 102e determines that there is no pegging.

  In addition, when the customer data is selected by the user via the input device 112, the basic information display unit 102a changes the office data, department data, and currency data included in the basic information corresponding to the customer data. If the basic information is not changed by the user via the input device 112, the bond management information including the basic information may be acquired.

  The transaction data acquisition unit 102b controls the user to input transaction detail data including an amount, a transaction date, and a transaction method corresponding to the claim management information via the input device 112. Get transaction data including data. Here, the transaction data acquisition unit 102b further acquires receivable balance data including the total amount of receivables for each same receivables and debt management establishment or each receivables and liability management department based on a plurality of collection schedule data, or Based on a plurality of payment schedule data, debt balance data including the total amount of debt for the same credit liability management establishment or credit liability management department may be acquired.

  The transaction data registration unit 102c registers the transaction data acquired by the transaction data acquisition unit 102b in the transaction data file 106j. Here, the transaction data registration unit 102c may further register the bond balance data or the debt balance data in the transaction data file 106j.

  The input authority check unit 102d checks the input authority of the receivable / liability management establishment after change and the receivable / liability management department after change.

  The linkage check unit 102e checks the linkage between the changed claim management office and the changed claim management department.

[3. Concrete example]
A specific example of this embodiment will be described with reference to FIGS.

[Receivables and debt management processing]
Here, with reference to FIG. 4, an example of the claim management process in this embodiment is demonstrated. FIG. 4 is a flowchart showing an example of processing in the claim management apparatus 100.

  As shown in FIG. 4, first, the basic information display unit 102a, when the customer data is selected via the input device 112 by the operator, the basic information corresponding to the customer data stored in the basic information file 106a. The office data, department data, and currency data included in the information are displayed on the output device 114 in a changeable manner (step SA-1).

  Then, when the basic information is changed by the operator via the input device 112, the basic information display unit 102a has changed the facility data of the receivables and payables management office, the department data of the receivables and debts management department after the change, and The change data including the currency data of the currency after the change and / or the debt management information including the unchanged data of the basic information is acquired (step SA-2).

  Then, the input authority check unit 102d checks the input authority of the changed claim management office and the changed claim management department (step SA-3).

  When the input authority checking unit 102d determines that there is no input authority (step SA-3: No), the process proceeds to step SA-4.

  And the basic information display part 102a outputs an error notification via the output device 114 (step SA-4), and shifts the processing to step SA-1.

  On the other hand, if the input authority check unit 102d determines that there is an input authority (step SA-3: Yes), the process proceeds to step SA-5.

  Then, the linkage check unit 102e checks the linkage between the changed claim management office and the changed claim management department (step SA-5).

  If the association check unit 102e determines that there is no association between the changed claim management office and the changed claim management department (step SA-5: No), the process goes to step SA-4. Transition.

  On the other hand, when the link checking unit 102e determines that there is a link between the changed claim management office and the changed claim management department (step SA-5: Yes), the process goes to step SA-6. Transition.

  Then, the transaction data acquisition unit 102b controls the user to input transaction detail data including an amount, a transaction date, and a transaction method corresponding to the claim management information via the input device 112, Transaction data including transaction detail data (collection schedule data related to a claim to be collected or payment schedule data related to a debt scheduled to be paid) is acquired (step SA-6). Here, the transaction data acquisition unit 102b may further acquire receivable balance data including the total amount of receivables for each same receivables and liability management establishment or each receivables and liability management department based on a plurality of collection schedule data. Good. Further, the transaction data acquisition unit 102b may further acquire debt balance data including the total amount of debt for each of the same debt management offices or credit management departments based on a plurality of payment schedule data. .

  Then, the transaction data registration unit 102c registers the collection schedule data or the payment schedule data acquired by the transaction data acquisition unit 102b in the transaction data file 106j (Step SA-7), and ends the process. Here, the transaction data registration unit 102c may further register the bond balance data or the debt balance data in the transaction data file 106j.

[Debt management processing]
In addition, an example of the claim management process in the present embodiment will be described with reference to FIGS. FIG. 5 to FIG. 8 are diagrams showing an example of a system flow in the case of performing the claim management of the claim management apparatus 100.

  As shown in FIG. 5, the basic information display unit 102 a corresponds to the customer data stored in the basic information file 106 a when the customer data of the billing destination A is selected by the operator via the input device 112. The initial data is displayed on the output device 114 in such a way that the office data of the credit management office (Tokyo), the department data of the credit management department (accounting department) and the currency data of the currency (JPY) included in the basic information to be displayed can be changed. If the basic information is changed through the input device 112, the post office data of the post-change credit management office (Yokohama), the post-change department data of the credit management department (first sales department) and / or change Receivables and debt management information including change data including currency data of the later currency (USD) and unchanged data (customer data) of the basic information is acquired (STEP Flop SB-1).

  Then, as shown in FIG. 6, the transaction data acquisition unit 102 b includes an amount corresponding to the claim management information via the input device 112, a transaction date (scheduled collection date), and a transaction method (collection method). Controls the transaction details data to be input, obtains collection schedule data including receivables management information and transaction details data, and manages each receivable management office (Yokohama) or receivables based on multiple collection schedule data Receivable balance data including the total amount of receivables (sales amount for the current month) for each department (first sales department) is acquired (step SB-2).

  Then, as shown in FIG. 7, the control unit 102 obtains billing data and balance data by totaling the collection schedule data for each credit management office, each credit management department, each currency, or each billing destination. The billing (invoice issuance) process is executed (step SB-3). In the billing process, there is no change in the balance itself.

  Then, as shown in FIG. 8, when the deposit data from the billing destination A is input by the operator via the input device 112, the control unit 102 acquires the deposit application data based on the deposit data. The collection schedule data, billing data, and balance data are updated (step SB-4), and the process ends.

  Here, the initial display setting in the present embodiment will be described with reference to FIGS. 9 to 11. FIG. 9 is a diagram illustrating an example of master settings of the claim and liability management apparatus 100. 10 and 11 are diagrams illustrating an example of the initial value setting process in the present embodiment.

  When the billing destination master 106b, the department master 106c, the payee master 106d, the basic information management master 106e, and the person-in-charge master 106f shown in FIG. 9 are included in the basic information file 106a, and as shown in FIG. If the initial display classification of the credit management establishment in the management master 106e is set to follow the billing destination master 106b, the basic information display unit 102a is based on the billing destination (billing destination A) selected by the operator. 106b is associated with the person-in-charge master 106f, and the credit management office: Tokyo and the credit management department: accounting department are set as initial values for initial display. In other words, in the present embodiment, the claim management office to be initially displayed for each billing destination may be determined in advance. The currency may be set with the customer's base currency as an initial value.

  Further, when the billing destination master 106b, the department master 106c, the payment destination master 106d, the basic information management master 106e, and the person in charge master 106f shown in FIG. 9 are included in the basic information file 106a, and as shown in FIG. When the initial display classification of the credit management establishment in the basic information management master 106e is set to follow the department master 106c, the basic information display unit 102a records sales based on the billing person in charge of the billing destination selected by the operator. The department to which the invoiced person in charge belongs is linked to the first sales department and the department master 106c, and the credit management office: Tokyo and the credit management department: accounting department are set as initial values for initial display. In other words, in the present embodiment, the receivables management office to be initially displayed may be determined in advance corresponding to the department to which the person in charge belongs.

  An example of the security check in this embodiment will be described with reference to FIG. FIG. 12 is a diagram illustrating an example of a security check in the present embodiment.

  As shown in FIG. 12, when the operator in charge of sales is Mr. Tanaka, the input authority check unit 102d associates the operator configuration master 106g, the sales common security master 106h, and the security pattern master 106i. When the change to the Tokyo office is input by Mr. Tanaka, the input authority check unit 102d determines that there is an input authority and proceeds to the transaction data acquisition process. On the other hand, the input authority checking unit 102d determines that there is no input authority when Mr. Tanaka inputs a change to an office other than the Tokyo office, and the basic information display unit 102a outputs an error notification. In other words, in the present embodiment, an error may be caused when a credit management office without input authority is input by the operator.

  Moreover, with reference to FIG. 13, an example of the linkage check in the office in this embodiment is demonstrated. FIG. 13 is a diagram illustrating an example of a linkage check in a business office according to the present embodiment.

  As shown in FIG. 13, when the operator inputs changes to the Tokyo office as the credit management office and the Osaka accounting department as the credit management department, the linking check section 102e refers to the department master 106c, The association between the Tokyo office and the Osaka accounting department is checked, and since the Osaka accounting department does not belong to the Tokyo office, it is determined that there is no association, and the basic information display section 102a outputs an error notification. That is, in the present embodiment, an error may occur when a department that does not belong to the credit management office entered by the operator is entered.

[Debt management processing]
Moreover, an example of the claim management process in this embodiment is demonstrated with reference to FIGS. 14-17. FIG. 14 to FIG. 17 are diagrams showing an example of a system flow in the case where debt management is performed by the claim management apparatus.

  As shown in FIG. 14, the basic information display unit 102a responds to the customer data stored in the basic information file 106a when the customer's customer data is selected via the input device 112 by the operator. The office data of the debt management office (Tokyo), the department data of the debt management department (accounting department), and the currency data of the currency (JPY) included in the basic information to be displayed are displayed on the output device 114 at the initial stage, and the operator If the basic information is changed through the input device 112, the post office data of the debt management office (Yokohama) after the change, the department data of the debt management department (the first sales department) after the change and / or the change Acquire receivables and debt management information including change data including currency data of the later currency (USD) and unchanged data (customer data) of the basic information. -Up SC-1).

  Then, as shown in FIG. 15, the transaction data acquisition unit 102 b includes an amount corresponding to the claim management information via the input device 112, a transaction date (planned payment date), and a transaction method (payment method). Controls to enter transaction details data, obtains payment plan data including receivables and debt management information and transaction details data, and based on multiple payment schedule data, each debt management office (Yokohama) or debt management Debt balance data including the total amount of debt (purchased amount for the current month) for each department (first sales department) is acquired (step SC-2).

  And as shown in FIG. 16, the control part 102 totals payment plan data for every debt management establishment, every debt management department, every currency, or every payee, payment method decision data and balance data (Step SC-3). In the payment closing process, there is no change in the balance itself.

  Then, as shown in FIG. 17, when the payment data to the payee A is input (payment settlement input) by the operator via the input device 112, the control unit 102 applies the payment application based on the payment data. Data is acquired, update processing of payment schedule data, payment method confirmation data, and balance data is executed (step SC-4), and the process is terminated.

  Thus, in the claim and debt management apparatus 100 according to the present embodiment, the claim and debt management information can be set on the system. For example, when setting the establishment / department of receivable information, two patterns of “according to the billing master” and “according to the department master” are prepared in the initial display classification of the basic information management master 106e. . In the case of “according to the billing destination master”, the representative office of the billing destination and the department to which the person in charge of the bill belongs are displayed. In the case of “according to the department master”, the credit management office and department of the department to which the sales representative belongs are displayed. These are only initial displays and can be corrected with each transaction data. Furthermore, the following check items may be implemented at the time of registration in order to prevent unexpected input. For example, when registering an establishment / department of bond information, the operator's non-inputable department and the non-inputable department may be checked, and the association between the establishment and the department may be checked.

  Further, the claim management apparatus 100 according to the present embodiment enables transactions in a plurality of business establishments and a plurality of currencies, and the management of claims and debts using the same customer.

  Further, according to the claim management apparatus 100 according to the present embodiment, it is possible to freely set items such as a new claim management office, department, and / or currency when recording the breakdown, When adding an item, it is possible to input a value different from the master of the billing destination. As a result, it is possible to manage balance data such as receivables and payables management offices, departments, and / or currencies by one billing destination code. Note that, as an example of setting items, the present embodiment has been described by taking the credit and debt management establishment, department, and / or currency as an example, but the present invention is not necessarily limited to this, and any other items other than this are described. It is also possible to set.

  Further, according to the claim management apparatus 100 according to the present embodiment, it is possible to prevent variations in input quality by an operator and improve the accuracy of input information. Furthermore, in order to improve the accuracy of the input information, when there is an information input that cannot be made in the combination of the input information, it is possible to issue an alert to the operator.

[4. Other Embodiments]
In addition to the above-described embodiments, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

  For example, among the processes described in the embodiments, all or part of the processes described as being automatically performed can be performed manually, or all of the processes described as being performed manually are all performed. Alternatively, a part can be automatically performed by a known method.

  In addition, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each processing, screen examples, and database configurations shown in the present specification and drawings, unless otherwise specified. Can be changed arbitrarily.

  Moreover, regarding the claim and debt management apparatus 100, each illustrated component is functionally conceptual and does not necessarily need to be physically configured as illustrated.

  For example, the processing functions provided in the claim and debt management apparatus 100, particularly the processing functions performed by the control unit, are realized by the CPU and a program that is interpreted and executed by the CPU. It may also be realized as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium that includes a programmed instruction for causing the information processing apparatus to execute the processing described in the present embodiment, and the claims and debts are recorded as necessary. It is mechanically read by the management device 100. In other words, in a storage unit such as a ROM or a HDD (Hard Disk Drive), a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded. This computer program is executed by being loaded into the RAM, and constitutes a control unit in cooperation with the CPU.

  Further, this computer program may be stored in an application program server connected to the claim management apparatus 100 via an arbitrary network, and may be downloaded in whole or in part as necessary. It is.

  In addition, the program for executing the processing described in the present embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the “recording medium” refers to a memory card, USB (Universal Serial Bus) memory, SD (Secure Digital) card, flexible disk, magneto-optical disk, ROM, EPROM (Erasable Programmable Read Only Memory), EEPROM (registration). Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), DVD (Digital Digital, Trademark) Any “portable physical media It is intended to include.

  The “program” is a data processing method described in an arbitrary language or description method, and may be in any form such as source code or binary code. Note that the “program” is not necessarily limited to a single configuration, and functions are achieved in cooperation with a separate configuration such as a plurality of modules and libraries or a separate program represented by the OS. Including things. In addition, a well-known structure and procedure can be used about the specific structure and reading procedure for reading a recording medium in each apparatus shown to embodiment, the installation procedure after reading, etc.

  Various databases and the like stored in the storage unit are storage means such as a memory device such as a RAM and a ROM, a fixed disk device such as a hard disk, a flexible disk, and an optical disk. Stores programs, tables, databases, web page files, and the like.

  In addition, the claim management apparatus 100 may be configured as an information processing apparatus such as a known personal computer or workstation, or may be configured as the information processing apparatus connected to an arbitrary peripheral device. Further, the claim and liability management apparatus 100 may be realized by installing software (including a program or data) that realizes the processing described in the present embodiment in the apparatus.

  Furthermore, the specific form of distribution / integration of the devices is not limited to that shown in the figure, and all or a part of them may be functionally or physically in arbitrary units according to various additions or according to functional loads. It can be configured to be distributed and integrated. That is, the above-described embodiments may be arbitrarily combined and may be selectively implemented.

  The present invention is particularly useful in a business format in which transactions with a plurality of business establishments, a plurality of departments, or a plurality of currencies and management of receivables and debts are performed using the same customer.

DESCRIPTION OF SYMBOLS 100 Claims and debt management apparatus 102 Control part 102a Basic information display part 102b Transaction data acquisition part 102c Transaction data registration part 102d Input authority check part 102e Linking check part 104 Communication interface part 106 Storage part 106a Basic information file 106b Billing master 106c Department master 106d Payment destination master 106e Basic information management master 106f Person in charge master 106g Operator configuration master 106h Sales common security master 106i Security pattern master 106j Transaction data file 106k Input authority file 108 Input / output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (8)

A debt management device comprising a storage unit and a control unit,
The storage unit
Basic information storage means for storing basic information in which the business data of the business partner of the initial display is linked to the business data of the business partner of the business partner data of the business partner and the department data of the initial display of the credit and debt management department ,
Transaction data storage means for storing transaction data relating to claims or debts with respect to the customer, including the customer data;
With
The controller is
When the customer data is selected by the user via the input device, the office data and the department data included in the basic information corresponding to the customer data are displayed on the output device in a changeable manner, If the basic information is changed by the user via the input device, the changed data including the changed factory data of the debt management office and / or the department data of the changed credit management department, and Basic information display means for acquiring debt management information including unmodified data of basic information;
Control the user to input transaction detail data including an amount, a transaction date, and a transaction method corresponding to the claim management information via the input device, and include the claim management information and the transaction detail data. Transaction data acquisition means for acquiring transaction data;
Transaction data registration means for registering the transaction data acquired by the transaction data acquisition means in the transaction data storage means;
A debt management apparatus characterized by comprising: The basic information storage means includes
Furthermore, the basic information in which the currency data of the basic currency is linked to the supplier data is stored,
The basic information display means includes
When the customer data is selected by the user via the input device, the office data, the department data, and the currency data included in the basic information corresponding to the customer data are output to be changeable. When the basic information is changed by the user via the input device, the office data of the changed debt management office, the department data and / or change of the changed debt management department 2. The claim and debt management apparatus according to claim 1, wherein the claim and debt management information including change data including currency data of a later currency and unchanged data of the basic information is acquired. The storage unit
An input authority storage means for storing input authority data relating to the claim management office and the claim management department that the user has no input authority;
Further comprising
The controller is
Input authority check means for checking the input authority of the changed claim management office and the changed claim management department;
Further comprising
The basic information display means includes
Furthermore, when the said input authority check means determines that the said input authority does not exist, an error notification is output via the said output apparatus, The claim | claim and debt management apparatus of Claim 1 or 2 characterized by the above-mentioned. The controller is
Pegging check means for checking pegging between the changed claim management office and the changed claim management department,
Further comprising
The basic information display means includes
The debt obligation according to any one of claims 1 to 3, further comprising: outputting an error notification via the output device when the pegging check means determines that the pegging is not performed. Management device. The transaction data is
5. The claim management apparatus according to claim 1, wherein the collection schedule data is related to the debt scheduled to be collected or the payment schedule data related to the debt scheduled to be paid. 6. The transaction data acquisition means
Further, based on a plurality of the collection schedule data, obtains receivable balance data including the total amount of the receivables for the same receivables and debt management establishment or for each receivables and debt management department, or a plurality of the payment schedules Based on the data, obtain the debt balance data including the total amount of the debt for each of the same debt management office or the debt management department,
The transaction data registration means includes
6. The claim and debt management apparatus according to claim 5, wherein the claim balance data or the debt balance data is registered in the transaction data storage means. A claim and debt management method for causing a claim and debt management device including a storage unit and a control unit to execute,
The storage unit
Basic information storage means for storing basic information in which the business data of the business partner of the initial display is linked to the business data of the business partner of the business partner data of the business partner and the department data of the initial display of the credit and debt management department ,
Transaction data storage means for storing transaction data relating to claims or debts with respect to the customer, including the customer data;
With
Executed by the control unit,
When the customer data is selected by the user via the input device, the office data and the department data included in the basic information corresponding to the customer data are displayed on the output device in a changeable manner, If the basic information is changed by the user via the input device, the changed data including the changed factory data of the debt management office and / or the department data of the changed credit management department, and A basic information display step for acquiring debt management information including unmodified data of the basic information;
Control the user to input transaction detail data including an amount, a transaction date, and a transaction method corresponding to the claim management information via the input device, and include the claim management information and the transaction detail data. A transaction data acquisition step for acquiring transaction data;
A transaction data registration step of registering the transaction data acquired in the transaction data acquisition step in the transaction data storage means;
A method for managing debts and debts. A debt management program for causing a credit management device having a storage unit and a control unit to execute,
The storage unit
Basic information storage means for storing basic information in which the business data of the business partner of the initial display is linked to the business data of the business partner of the business partner data of the business partner and the department data of the initial display of the credit and debt management department ,
Transaction data storage means for storing transaction data relating to claims or debts with respect to the customer, including the customer data;
With
In the control unit,
When the customer data is selected by the user via the input device, the office data and the department data included in the basic information corresponding to the customer data are displayed on the output device in a changeable manner, If the basic information is changed by the user via the input device, the changed data including the changed factory data of the debt management office and / or the department data of the changed credit management department, and A basic information display step for acquiring debt management information including unmodified data of the basic information;
Control the user to input transaction detail data including an amount, a transaction date, and a transaction method corresponding to the claim management information via the input device, and include the claim management information and the transaction detail data. A transaction data acquisition step for acquiring transaction data;
A transaction data registration step of registering the transaction data acquired in the transaction data acquisition step in the transaction data storage means;
Receivables and debt management program to make you run.

Images