Settlement condition management device, settlement condition management method, and settlement condition management program

Abstract

To provide a settlement condition management device, a settlement condition management method, and a settlement condition management program which enable easy extraction of a transaction settled by a condition more disadvantageous than a scheduled collection condition.SOLUTION: This settlement condition management device comprises a control unit, and can access a billing destination master, sales data, billing data, collection schedule data, payment data, and payment deletion data. The control unit is provided with a work table generation part that generates a work table for outputting a business form on the basis of the billing destination master, the collection schedule data, the payment data, and the payment deletion data, and a settlement condition extraction part that extracts a transaction of a condition designated on a collection plan and actual table extraction screen among transactions in the work table.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a payment terms management device, a payment terms management method, and a payment terms management program. [Background technology]

[0002] There are several payment methods for receiving payment when trading with customers for goods or services, including cash and bills. Even when settling with cash, not just bills, it is common for the timing of the provision of goods or services and the timing of payment to differ, as in credit transactions. In order to avoid problems with customers regarding the collection of payment, collection terms are agreed upon with the customer at the start of trading.

[0003] However, after starting a transaction, there may be cases where the payment is not received according to the agreed upon collection conditions due to the client's cash flow situation, etc. For example, if the collection condition is agreed upon as a bank transfer and the due date is changed to a bill of exchange 30 days later, the transaction that was scheduled to be cashed in 30 days will be cashed in 60 days, which is undesirable from the perspective of cash flow.

[0004] Patent document 1 describes a sales collection amount prediction device that predicts the collection amount for accounts receivable on a monthly basis, and is characterized by comprising: a collection condition acquisition means for acquiring collection conditions that are determined in advance by a transaction contract and include conditions related to a contractual closing date and a scheduled collection date for identifying a collection date according to the date on which the accounts receivable was generated; a collection condition storage means for storing the collection conditions; an accounts receivable information acquisition means for acquiring accounts receivable information related to the actual and / or scheduled amounts of the accounts receivable and the date on which the accounts receivable was generated; an accounts receivable information storage means for storing the accounts receivable information; a monthly planned collection amount calculation means for calculating, on a monthly basis based on the stored collection conditions and accounts receivable information, the monthly planned collection amount, which is the total of the accounts receivable having the collection date in that month; and a collection amount list output means for outputting a list of the monthly planned collection amounts for a specific period based on the calculated monthly planned collection amounts. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2004-265072 A Summary of the Invention [Problem to be solved by the invention]

[0006] The sales collection amount prediction device of Patent Document 1 can easily predict the sales collection amount, but cannot grasp transactions in which the collection method has been changed.

[0007] The present invention has been made in consideration of the above problems, and aims to provide a payment terms management device, a payment terms management method, and a payment terms management program that can easily extract transactions that are settled under conditions that are less favorable than the planned collection conditions. [Means for solving the problem]

[0008] In order to solve the above-mentioned problems and achieve the object, the payment conditions management device of the present invention is a payment conditions management device equipped with a control unit, and is capable of accessing a billing destination master that stores the collection conditions, which are the collection method code, collection method, collection site, and bill site, linked to a billing destination code, sales data including a slip number, sales date, billing destination, and sales amount, billing data including the billing number, billing destination, billing amount, scheduled collection date, collection method code, and bill due date, collection schedule data including the collection schedule number, billing number, collection method code, and scheduled collection date, deposit data including the deposit number, billing destination, deposit category, deposit amount, and bill due date, and deposit reconciliation data including the deposit number, collection schedule number, and deposit reconciliation amount, and the control unit is characterized by having a work table creation unit that creates a work table for report output based on the billing destination master, the collection schedule data, the deposit data, and the deposit reconciliation data, and a payment conditions extraction unit that extracts transactions that meet the conditions specified on the collection forecast table extraction screen from the transactions in the work table.

[0009] Further, in the payment condition management device according to the present invention, in the above invention, the payment condition extraction unit extracts transactions in which there is a difference between the deposited amount and the invoiced amount.

[0010] In addition, the payment conditions management device of the present invention is capable of accessing a collection method linking master that stores collection method codes and type codes in association with each other in the above invention, and a deposit linking master that stores deposit classifications and type codes in association with each other, and the work table creation unit calculates the difference between the invoice amount and the deposit amount for each transaction for each type code, and the payment conditions extraction unit extracts transactions that have a difference according to the specified type code.

[0011] In addition, in the payment conditions management device of the present invention, in the above invention, the work table creation unit refers to the deposit date and bill due date of the deposit data and calculates the difference with the bill site stored in the billing destination master, and the payment conditions extraction unit extracts transactions in which there is a difference between the expected and actual bill due dates in the work table.

[0012] In addition, the payment conditions management method of the present invention is a payment conditions management method executed by a payment conditions management device equipped with a control unit, the payment conditions management device being capable of accessing a billing destination master that stores collection conditions, such as a collection method code, collection method, collection site, and bill site, linked to a billing destination code, sales data including a slip number, sales date, billing destination, and sales amount, billing data including a billing number, billing destination, billing amount, scheduled collection date, collection method code, and bill due date, collection schedule data including a collection schedule number, billing number, collection method code, and scheduled collection date, deposit data including a deposit number, billing destination, deposit category, deposit amount, and bill due date, and deposit reconciliation data including a deposit number, collection schedule number, and deposit reconciliation amount, and is characterized in that the payment conditions management method includes a work table creation step executed by the control unit that creates a work table for outputting reports based on the billing destination master, the collection schedule data, the deposit data, and the deposit reconciliation data, and a payment conditions extraction step that extracts transactions that meet the conditions specified on a collection forecast table extraction screen from the transactions in the work table.

[0013] In addition, the payment conditions management program of the present invention is a payment conditions management program to be executed by a payment conditions management device having a control unit, and the payment conditions management device is capable of accessing a billing destination master that stores collection conditions, such as a collection method code, collection method, collection site, and bill site, linked to a billing destination code, sales data including a slip number, sales date, billing destination, and sales amount, billing data including a billing number, billing destination, billing amount, scheduled collection date, collection method code, and bill due date, collection schedule data including a collection schedule number, billing number, collection method code, and scheduled collection date, deposit data including a deposit number, billing destination, deposit category, deposit amount, and bill due date, and deposit reconciliation data including a deposit number, collection schedule number, and deposit reconciliation amount, and is configured to cause the control unit to execute a work table creation step of creating a work table for report output based on the billing destination master, the collection schedule data, the deposit data, and the deposit reconciliation data, and a payment conditions extraction step of extracting transactions that meet the conditions specified on a collection forecast table extraction screen from the transactions in the work table. Effect of the Invention

[0014] According to the present invention, it is possible to easily extract transactions that are settled under less favorable conditions than the planned collection conditions. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of a payment condition management device according to the present embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of the billing destination master. [Diagram 3] FIG. 3 is a diagram illustrating an example of the collection method linking master. [Figure 4] FIG. 4 is a diagram illustrating an example of sales data. [Diagram 5] FIG. 5 is a diagram showing an example of the request data. [Figure 6] FIG. 6 is a diagram illustrating an example of collection schedule data. [Figure 7] FIG. 7 is a diagram showing an example of the deposit data. [Figure 8] FIG. 8 is a diagram illustrating an example of the deposit matching master. [Figure 9] FIG. 9 is a diagram showing an example of the deposit reconciliation data. [Figure 10] FIG. 10 is a diagram illustrating an example of the work table. [Figure 11] FIG. 11 is a diagram showing an example of the bill collection forecast table extraction screen. [Figure 12] FIG. 12 is a diagram showing an example of a bill collection forecast / actual table. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] Hereinafter, an embodiment of a payment terms management device, a payment terms management method, and a payment terms management program according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the embodiment.

[0017] [1. Configuration] An example of the configuration of a payment condition management device according to this embodiment will be described with reference to Fig. 1 etc. Fig. 1 is a diagram showing an example of the configuration of a payment condition management device 100 according to this embodiment.

[0018] The payment condition management device 100 is constructed based on a commercially available desktop personal computer. The payment condition management device 100 is not limited to being constructed based on a stationary information processing device such as a desktop personal computer, but may be constructed based on a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.

[0019] The payment condition management device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the payment condition management device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0020] The communication interface unit 104 communicatively connects the payment condition management device 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 the communication line. Here, the network 300 has a function of connecting the payment condition management device 100 and the server device 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). The data stored in the memory unit 106 may be stored in the server device 200, for example.

[0021] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to realize a pointing device function. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0022] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs for cooperating with an OS (Operating System) to give instructions to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. For example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used as the storage unit 106.

[0023] The memory unit 106 stores, for example, a billing destination master 106a, a collection method linking master 106b, sales data 106c, billing data 106d, collection schedule data 106e, deposit data 106f, deposit linking master 106g, deposit reconciliation data 106h, and a work table 106i.

[0024] The billing destination master 106a stores the collection conditions agreed upon with the customer. As shown in FIG. 2, the billing destination master 106a stores collection conditions such as the collection method code, collection method, collection site, and bill site in association with the billing destination code and billing destination name.

[0025] The collection method association master 106b stores collection method codes and type codes in association with each other. As shown in FIG. 3, the collection method association master 106b stores collection method codes and collection method names in association with type codes and type names.

[0026] The sales data 106c is data related to sales for each transaction. The sales data 106c stores a slip number, a category, a sales date, a billing destination, a sales amount, and the like, as shown in an example in FIG.

[0027] The billing data 106d is data related to billing to customers. As shown in Fig. 5, the billing data 106d stores information including the accounting year and month, billing number, billing date, billing destination code, billing destination, billing amount, scheduled collection date, scheduled collection month, collection method code, collection method, bill due date, and payment clearing completion category for each transaction.

[0028] The collection schedule data 106e stores information about the collection schedule for the sales of a transaction. As shown in Fig. 6, the collection schedule data 106e stores information including the accounting year and month, collection schedule number, sales amount, billing number, collection method code, collection method, scheduled collection date, reconciled amount, and reconciliation completion category. The collection schedule data 106e is linked to the billing data 106d by the billing number.

[0029] The deposit data 106f is data related to deposits from customers. The deposit data 106f stores information including the accounting year and month, deposit number, deposit date, deposit category, deposit category name, deposit amount, and bill due date, as shown in FIG. 7.

[0030] The deposit correlating master 106g stores the deposit classification and the type code in association with each other. As shown in Fig. 8, the deposit correlating master 106g stores the deposit classification and the deposit classification name in association with the type code and the type name. The deposit correlating master 106g is linked to the collection method correlating master 106b by the type code.

[0031] The deposit reconciliation data 106h is data related to the reconciliation of a transaction. The deposit reconciliation data 106h stores information including the accounting year and month, deposit number, collection schedule number, deposit reconciliation amount, collection method code, collection method, etc., as shown in an example in Fig. 9. The deposit reconciliation data 106h is linked to the deposit data 106f by the deposit number, and to the collection schedule data 106e by the collection schedule number.

[0032] The work table 106i is a table for creating the billing collection forecast / actual table MB shown in Fig. 12. As shown in Fig. 10 as an example, the work table 106i stores billing destination code, billing destination, scheduled collection month, sales amount, deposit amount, type code, collection method code, collection method, collection site, bill due date in billing data, bill due date in deposit data, difference in collection amount by type, difference between forecast and actual bill due date, deposit clearing completion category, etc.

[0033] The control unit 102 is a CPU or the like that comprehensively controls the payment condition management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs.

[0034] The control unit 102 conceptually comprises, in terms of functions, a billing data creation unit 102a, a collection schedule data creation unit 102b, a payment reconciliation data creation unit 102c, a work table creation unit 102d, a payment condition extraction unit 102e, and the like.

[0035] The billing data creation unit 102a creates billing data 106d based on the billing destination master 106a, the collection method linking master 106b, the sales data 106c, and the payment reconciliation data 106h.

[0036] The collection schedule data creation unit 102b creates collection schedule data 106e based on the billing data 106d and the payment reconciliation data 106h.

[0037] The deposit reconciliation data creation unit 102c creates deposit reconciliation data 106h based on the deposit data 106f.

[0038] The work table creating unit 102d creates a work table 106i for outputting forms, based on the billing destination master 106a, the collection schedule data 106e, the deposit data 106f, and the deposit reconciliation data 106h.

[0039] The payment condition extraction unit 102e extracts, from among the transactions in the work table 106i, transactions that satisfy the conditions specified on the payment collection forecast / actual table extraction screen MA, an example of which is shown in FIG.

[0040] [2. Processing] Here, a specific example of the process executed by the payment condition management device 100 will be described with reference to FIGS.

[0041] When a transaction is concluded with a customer, sales data 106c is created by the operator, including the transaction slip number, the sales date, the billing destination, and the sales amount.

[0042] After creating the sales data 106c, the billing data creation unit 102a creates billing data 106d based on the sales data 106c, billing destination master 106a, and payment reconciliation data 106h. The billing data creation unit 102a obtains the billing destination code, collection method code, collection method, collection site, and bill due date of the billing destination from the billing destination master 106a, calculates the scheduled collection date, collection month, collection method code, collection method, and bill due date, and stores them as data. In addition, after the payment reconciliation data 106h described below is created, the payment reconciliation amount is obtained from the payment reconciliation data 106h and stored. For example, for the billing code "SEI002" of the billing master 106a in FIG. 2, the collection method is "bill", the collection site is "end of next month", and the bill side is "60", so at the stage of "2023 / 4" when the accounting year and month for creating the billing data 106d in FIG. 5 is "2023 / 5", the next month's "2023 / 5" is the scheduled collection month, "2023 / 5 / 31" is the scheduled collection date, and the bill due date is "2023 / 6 / 30". Furthermore, the billing data creation unit 102a obtains and stores the collection method code from the billing master 106a. In the billing data 106d shown in FIG. 5, all items have been entered, but since the payment is incomplete at this stage, all of the payment settlement completion parts are stored as "0".

[0043] After creating the billing data 106d, the collection schedule data creation unit 102b creates collection schedule data 106e based on the billing data 106d and the deposit reconciliation data 106h. The collection schedule data creation unit 102b obtains and stores the billing number, collection method code, collection method, and scheduled collection date from the billing data 106d. In addition, after the deposit reconciliation data 106h, which will be described later, is created, the deposit reconciliation amount is obtained from the deposit reconciliation data 106h and stored. In the collection schedule data 106e shown in Figure 6, all items have been entered, but since the deposit is incomplete at this stage, the deposit reconciliation amount and the deposit reconciliation completion category are all stored as "0".

[0044] When the deposit is confirmed, deposit data 106f is created by the operator, including the accounting year and month, deposit number, deposit date, deposit category, deposit category name, deposit amount, and bill due date.

[0045] After creating the deposit data 106f, the deposit reconciliation data creation unit 102c creates deposit reconciliation data 106h based on the deposit data 106f.

[0046] For a transaction for which deposit reconciliation data 106h has been created, the work table creation unit 102d creates a work table 106i for outputting a report based on the billing destination master 106a, scheduled collection data 106e, deposit data 106f, and deposit reconciliation data 106h. As shown in Fig. 10 as an example, the work table 106i includes billing destination code, billing destination, scheduled collection month, sales amount, deposit amount, type code, collection method code, collection method, collection site, bill due date in billing data, bill due date in deposit data, difference in collection amount by type, difference between expected and actual bill due date, deposit reconciliation completion category, etc.

[0047] The work table creation unit 102d creates a work table 106i by calculating the difference in the amount of collection by item and the difference between the expected and actual bill due dates. In the work table 106i shown in FIG. 10, the difference in the amount of collection by item is calculated by dividing it into the difference in the amount of collection for transactions in which the collection method item code "S001" of cash, check, and transfer is selected, and the difference in the amount of collection for transactions in which the collection method item code "S002" of bill, due date, and electronic is selected. For example, in the billing destination code "SEI001" of □△ Industry, the sales amount is "2,000,000" and the deposit amount is "1,500,000", so the difference is "500,000". However, since the collection method is "transfer" and the type code is "S001", the difference "500,000" is entered in cash, check, and transfer (difference). Also, at ×△ House with billing code "SEI003", the sales amount is "3,000,000" and the deposit amount is "3,000,000", but the collection method is "transfer" and the deposit was made by bill with a bill due date of "2023 / 08 / 31". Because there is a difference in the collection amount for both cash, check, and transfer with item code "S001" and bill, due date, and electronic with item code "S002", the difference "3,000,000" is entered in cash, check, and transfer (difference) and the difference "-3,000,000" is entered in bill, due date, and electronic (difference).

[0048] The work table creation unit 102d refers to the payment date and the bill due date of the payment data 106f, calculates the difference with the bill site stored in the bill master 106a, and stores it in the work table 106i as the expected difference between the bill due date. For example, for the bill code "SEI002" of the XX Construction Company, the bill master 106a states that the collection method is a bill with a bill site of 60 days, but a bill dated "2023 / 09 / 30" was issued on "2023 / 05 / 31". If the bill site is 60 days, the bill due date would be "2023 / 06 / 30", but since the bill is dated "2023 / 09 / 30", the expected difference between the bill due date and the actual difference is "90". In addition, when a bill is deposited without a schedule, such as the bill code "SEI003" of the XX House, a fixed value of "999" is entered.

[0049] When a user wishes to check the planned and actual collection amounts, the payment condition extraction unit 102e extracts transactions that meet the conditions specified on the collection forecast / actual table extraction screen MA-1, an example of which is shown in Figure 11, and creates and outputs the collection forecast / actual table MB, an example of which is shown in Figure 12.

[0050] In the collection schedule table extraction screen MA-2 in Fig. 11, the planned collection month and billing destination are specified, and the payment condition extraction unit 102e extracts the transactions of the specified planned collection month and billing destination from the work table 106i to create the collection schedule table MB. In the collection schedule table MB, in addition to the agreed collection method, planned collection amount (planned, actual, difference), and bill due date (planned, actual, difference) for each billing destination, the planned collection amount (planned, actual, difference) is clearly indicated by type (cash, check, transfer, bill, due date, electronic). By checking the planned collection amount and bill due date, it is possible to check transactions with differences in the planned collection amount and bill due date.

[0051] In addition, in the collection forecast / actual table extraction screen MA-2 in Fig. 11, the expected collection month and billing destination are specified, but if "Uncollected only" is checked in the collection status, a collection forecast / actual table is created for transactions where the payment clearing completion classification flag in the work table 106i is "1", for example, in the work table 106i in Fig. 10, for ×△ House with billing destination code "SEI003". Also, if "Cash / Check / Transfer" is checked in the collection condition difference, a collection forecast / actual table is created for transactions where a difference has occurred in the collection amount cash / check / transfer (difference) in the work table 106i, for example, in the work table 106i in Fig. 10, for □△ Industry with billing destination code "SEI001" and ×△ House with billing destination code "SEI003". Also, if you check "Bills and electronic receivables," a collection forecast and actual table will be created only for transactions where there is a difference in the collected amount, bill, due date, and electronic (difference), for example, in the work table 106i in Fig. 10, for the ×△ House with billing code "SEI003." Also, if you specify a date in the bill due date difference, a collection forecast and actual table will be created for transactions that are later than the date specified in the bill due date (difference between expected and actual) in the work table 106i in Fig. 10.

[0052] The payment terms management device 100 in this embodiment can create a collection forecast / actual table for transactions that match the specified payment terms by specifying payment terms on the collection forecast / actual table extraction screen MA, making it easy to understand transactions whose collection terms and payment terms differ.

[0053] [3. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to goals 8 and 9 of the SDGs.

[0054] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0055] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[0056] [4. Other embodiments] The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0057] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0058] In addition, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

[0059] Moreover, with regard to the payment condition management device 100, each of the components shown in the figures is a functional concept, and it is not necessary for the device to be physically configured as shown in the figures.

[0060] For example, the processing functions of the payment condition management device 100, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded in a non-transient computer-readable recording medium that includes programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the payment condition management device 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into a RAM, and cooperates with the CPU to form a control unit.

[0061] In addition, this computer program may be stored in an application program server connected to the payment condition management device 100 via any network, and it is also possible to download all or part of it as needed.

[0062] In addition, the program for executing the process described in this embodiment may be stored in a non-transient computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) Disc.

[0063] Moreover, a "program" is a data processing method written in any language or description method, and may be in any form, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration as multiple modules or libraries, and a program that works with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, may use well-known configurations and procedures.

[0064] The various databases etc. stored in the memory unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files etc. used for various processes and providing websites.

[0065] The payment terms management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The payment terms management device 100 may be realized by installing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

[0066] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively. [Industrial Applicability]

[0067] The present invention is useful, for example, in businesses that use multiple payment collection methods for commercial transactions with customers. [Explanation of symbols]

[0068] 100 Payment terms management device 102 Control section 102a Billing Data Creation Department 102b Collection Schedule Data Creation Department 102c Payment Reconciliation Data Creation Department 102d Worktable Creation Department 102e Payment condition extraction unit 104 Communication interface section 106 Storage section 106a Billing Master 106b Collection method linking master 106c Deposit Data 106d Billing Data 106e Scheduled recovery data 106f Deposit Data 106g Deposit Linking Data 106h Payment reconciliation data 106i Work Table 108 Input / Output Interface Section 112 Input Devices 114 Output Device 200 Servers 300 Network

Claims

1. A payment condition management device including a control unit, A billing destination master that stores the collection conditions, such as the collection method code, collection method, collection site, and bill site, in association with the billing destination code; Sales data including invoice number, sales date, billing address and sales amount; Invoice data including invoice number, invoice destination, invoice amount, expected collection date, collection method code, and bill due date; collection schedule data including a collection schedule number, a billing number, a collection method code, and a collection schedule date; Deposit data including deposit number, billing address, deposit category, deposit amount, and bill due date, Receipt reconciliation data including the receipt number, collection schedule number, and reconciliation amount; is accessible to The control unit is a work table creating unit that creates a work table for outputting a report based on the billing destination master, the collection schedule data, the deposit data, and the deposit reconciliation data; a payment condition extraction unit for extracting transactions that satisfy conditions designated on a payment collection forecast table extraction screen from among the transactions in the work table; A payment condition management device comprising:

2. 2. The payment conditions management device according to claim 1, wherein the payment conditions extraction unit extracts transactions in which there is a difference between a deposited amount and a billed amount.

3. a collection method association master that associates and stores a collection method code and a type code; A deposit linking master that links and stores a deposit classification and a type code; is accessible to The work table creation unit calculates the difference between the billing amount and the deposit amount for each transaction for each transaction type code, 2. The payment terms management device according to claim 1, wherein the payment terms extraction unit extracts transactions having a difference according to a specified type code.

4. The work table creation unit refers to the payment date and the bill due date of the payment data, and calculates a difference from the bill site stored in the billing destination master, 2. The payment terms management device according to claim 1, wherein the payment terms extraction unit extracts transactions in which there is a difference between the expected and actual bill due dates in the work table.

5. A payment condition management method executed by a payment condition management device having a control unit, The payment condition management device includes: A billing destination master that stores the collection conditions, such as the collection method code, collection method, collection site, and bill site, in association with the billing destination code; Sales data including invoice number, sales date, billing address and sales amount; Invoice data including invoice number, invoice destination, invoice amount, expected collection date, collection method code, and bill due date; collection schedule data including a collection schedule number, a billing number, a collection method code, and a collection schedule date; Deposit data including deposit number, billing address, deposit category, deposit amount, and bill due date, Receipt reconciliation data including the receipt number, collection schedule number, and reconciliation amount; is accessible to Executed by the control unit, a work table creating step of creating a work table for outputting a report based on the billing master, the collection schedule data, the deposit data, and the deposit reconciliation data; A payment condition extraction step of extracting transactions that satisfy conditions specified on a payment collection forecast table extraction screen from among the transactions in the work table; A payment condition management method comprising:

6. A payment condition management program to be executed by a payment condition management device having a control unit, The payment condition management device includes: A billing destination master that stores the collection conditions, such as the collection method code, collection method, collection site, and bill site, in association with the billing destination code; Sales data including invoice number, sales date, billing address and sales amount; Invoice data including invoice number, invoice destination, invoice amount, expected collection date, collection method code, and bill due date; collection schedule data including a collection schedule number, a billing number, a collection method code, and a collection schedule date; Deposit data including deposit number, billing address, deposit category, deposit amount, and bill due date, Receipt reconciliation data including the receipt number, collection schedule number, and reconciliation amount; is accessible to The control unit, a work table creating step of creating a work table for outputting a report based on the billing master, the collection schedule data, the deposit data, and the deposit reconciliation data; A payment condition extraction step of extracting transactions that satisfy conditions specified on a payment collection forecast table extraction screen from among the transactions in the work table; A payment terms management program for executing the above.

Images