Sales management device, sales management method, and sales management program
The sales management device simplifies receivables management by identifying and displaying transferable receivables, enabling accurate transfers and credit management, addressing the complexity of managing multiple business partners with differing payment schedules.
Patent Information
- Application Number
- JP2021201738
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-12-13
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2041-12-13
AI Technical Summary
Receivables management becomes complicated when dealing with many business partners, especially when initial and actual payment dates differ, making it difficult to accurately manage cash flow schedules and perform receivables transfers.
A sales management device and method that includes an acquisition unit to gather debt collection schedule data, a detection unit to identify receivables that can be transferred, and a display control unit to present a list of transferable receivables, along with a collection data generation unit to reflect transfer processing, facilitating easy management and accurate transfer of receivables.
Enables easy and accurate management of receivables by displaying transferable candidates, allowing quick and precise receivables transfers, and facilitating credit management using actual amounts, thereby improving business efficiency and reducing complexity.
Smart Images

Figure 0007593914000001 
Figure 0007593914000002 
Figure 0007593914000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a sales management device, a sales management method, and a sales management program. [Background technology]
[0002] Nowadays, it is common for accounts receivable to be transferred to a party other than the party originally intended to receive the payment in order to quickly raise funds for cash flow purposes or to facilitate the flow of funds within a corporate group (liquidation).
[0003] Patent Document 1 (JP Patent Publication 2005-275955A) discloses a liquidation claim management system that aims to complete a series of liquidation procedures quickly and with high accuracy. This liquidation claim management system is equipped with a brand application processing program, a liquidation execution program, and a claim collection processing program. The liquidation execution program acquires claim information sent from each group company, stores it in a claim information storage unit, and calculates a balance concentration rate based on this claim information. It then reads upper limit information from a master information storage unit in which upper limit information has been stored in advance, and judges whether the balance concentration rate exceeds the upper limit information. Furthermore, if the balance concentration rate exceeds the upper limit information, it transmits information indicating that it has exceeded the upper limit information to the terminal of the controlling company and / or the specific purpose company. This allows a series of liquidation procedures to be completed quickly and with high accuracy. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2005-275955 A Summary of the Invention [Problem to be solved by the invention]
[0005] However, when dealing with accounts receivable from many business partners, there was a problem that accounts receivable management became complicated.
[0006] The present invention has been made in consideration of the above-mentioned problems, and has an object to provide a sales management device, a sales management method, and a sales management program that can facilitate credit management. [Means for solving the problem]
[0007] In order to solve the above-mentioned problems and achieve the object, the sales management device of the present invention comprises an acquisition unit that acquires planned collection data for receivables including the planned collection date and planned collection amount for each input billing recipient, a detection unit that detects billing recipients designated as targets for accounts receivable securitization from among the billing recipients for which planned collection data has been acquired by referring to a billing recipient master in which accounts receivable securitization target information indicating whether each billing recipient is a target for accounts receivable securitization is stored, and a display control unit that displays a list of planned collection data for billing recipients designated as targets for accounts receivable securitization detected by the detection unit from among the planned collection data for each billing recipient acquired by the acquisition unit. a collection data generating unit for generating collection schedule data reflecting transfer processing of receivables performed based on a list of billing recipients designated as targets for accounts receivable securitization; has.
[0008] Furthermore, in order to solve the above-mentioned problems, the sales management method according to the present invention includes an acquisition step in which an acquisition unit acquires planned collection data for receivables including a planned collection date and a planned collection amount for each input billing recipient; a detection step in which a detection unit detects billing recipients designated as targets for accounts receivable securitization among the billing recipients for which collection schedule data has been acquired by referring to a billing recipient master in which accounts receivable securitization target information indicating whether each billing recipient is a target for accounts receivable securitization is stored; and a display control step in which a display control unit displays a list of planned collection data for billing recipients designated as targets for accounts receivable securitization detected in the detection step among the planned collection data for each billing recipient acquired in the acquisition step. a collection data generating step in which a collection data generating unit generates collection schedule data reflecting a transfer process of receivables performed based on a list of billing destinations designated as targets for accounts receivable securitization; has.
[0009] In addition, in order to solve the above-mentioned problems, a sales management program according to the present invention includes a computer, comprising: an acquisition unit that acquires planned collection data for receivables, including a planned collection date and a planned collection amount for each input billing recipient; a detection unit that detects billing recipients designated as targets for accounts receivable securitization among the billing recipients for which collection schedule data has been acquired by referring to a billing recipient master in which accounts receivable securitization target information indicating whether each billing recipient is a target for accounts receivable securitization is stored; and a display control unit that displays a list of planned collection data for billing recipients designated as targets for accounts receivable securitization detected by the detection unit among the planned collection data for each billing recipient acquired by the acquisition unit. and functioning as a collection data generating unit that generates collection schedule data that reflects the transfer processing of receivables performed based on a list of billing destinations designated as targets for accounts receivable securitization. It is characterized by: Effect of the Invention
[0010] The present invention has the effect of facilitating credit management. [Brief description of the drawings]
[0011] [Figure 1] FIG. 1 is a block diagram showing a hardware configuration of a sales management device according to an embodiment. [Diagram 2] FIG. 2 is a diagram showing an outline of processing performed by the sales management device according to the embodiment for accounts receivable. [Diagram 3] FIG. 3 is a flowchart showing the flow of processing for accounts receivable in the sales management device according to the embodiment. [Figure 4] FIG. 4 is a diagram for explaining the display process of the liquidation target list and the transfer process of accounts receivable in the sales management device according to the embodiment. [Diagram 5] FIG. 5 is a diagram showing an example of a bond transfer input screen. [Figure 6] FIG. 6 is a diagram showing an example of a credit management summary table that reflects the transfer processing of receivables. [Figure 7] FIG. 7 is a diagram for explaining the operation of recording journal entry data reflecting the transfer processing of accounts receivable in the accounting system. [Figure 8] FIG. 8 is a diagram showing an outline of processing performed by the sales management device according to the embodiment for bills receivable. [Figure 9] FIG. 9 is a flowchart showing a process flow for a note receivable in the sales management device according to the embodiment. [Figure 10] FIG. 10 is a diagram for explaining the display process of the liquidation target list and the transfer process of bills receivable in the sales management device according to the embodiment. [Figure 11] FIG. 11 is a diagram showing an example of a screen for transfer processing of a bill receivable. [Figure 12] FIG. 12 is a diagram for explaining the operation of recording journal entry data that reflects the transfer processing of bills receivable in the accounting system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0012] A sales management device according to an embodiment of the present invention will be described in detail below with reference to the drawings. Note that the present invention is not limited to the embodiment.
[0013] (Hardware configuration) 1 is a block diagram showing a hardware configuration of a sales management device 1 according to an embodiment. As the sales management device 1, in addition to a desktop personal computer, a notebook personal computer or a tablet personal computer can be used. Also, as the sales management device 1, a portable information processing device such as a PDA (Personal Digital Assistant) or a smartphone can be used. Such a sales management device 1 includes a storage unit 2, a control unit 3, a communication interface unit 4 and an input / output interface unit 5.
[0014] An input device 6 and an output device 7 are connected to the input / output interface unit 5. A monitor device (including a home television) can be used as the output device 7. As the input device 6, a keyboard device, a mouse device, a microphone device, and a monitor device that cooperates with a mouse device to realize a pointing device function can be used.
[0015] A storage device such as a ROM (Read Only Memory), a RAM (Random Access Memory), a HDD (Hard Disk Drive), or an SSD (Solid State Drive) can be used as the storage unit 2. The storage unit 2 is provided with a billing destination master 11 and a credit master 12, each of which is a storage area in which predetermined information is stored.
[0016] The billing destination master 11 stores each billing destination company in association with an accounts receivable liquidation target flag, which is information indicating whether each company is a target for accounts receivable liquidation. The credit master 12 stores the credit amount for each company.
[0017] The communication interface unit 4 is connected to a network 8, for example, a wide area network such as the Internet or a private network such as a LAN (Local Area Network). An accounting terminal device 9 is connected to the network 8, and journal entry data corresponding to the receivables transfer processing performed by the sales management device 1 is recorded. Note that in this example, the explanation will be given assuming that the journal entry data is recorded in the accounting system of the accounting terminal device 9 via the network 8, but it may also be recorded in an accounting system provided in the memory unit 2, as shown by the dotted line block in FIG. 1.
[0018] (Functional configuration) Next, a sales management program is stored in the memory unit 2. The control unit 3 executes this sales management program to function as an acquisition unit 21, a data processing unit 22, a display control unit 23, an output control unit 24, and a communication control unit 25.
[0019] The acquisition unit 21 acquires information corresponding to input operations by a business operator, such as sales input processing or transfer processing. The data processing unit 22 generates, for example, collection schedule data from sales input based on the information acquired by the acquisition unit 21, and also generates journal entry data from transfer processing. The display control unit 23 displays a main screen, sub-screen, collection schedule data, liquidation target list, and the like for performing receivable transfer input via the output device 7. The output control unit 24 outputs (prints or displays) a trial balance generated based on the journal entry data reflecting the receivable transfer processing via the output device 7. The communication control unit 25 transmits the journal entry data reflecting the receivable transfer processing to the accounting terminal device 9 for recording.
[0020] (Overview of accounts receivable processing) 2 shows an outline of the processing of the sales management device 1 according to the embodiment for accounts receivable, which is an example of credit. In the case of accounts receivable, the business operator inputs sales data as "accounts receivable / sales" into the sales management device 1. If the accounts receivable is not transferred, the deposit processing is performed as is as "Cash (CASH) / accounts receivable."
[0021] In response to this, a transfer process is also possible in which accounts receivable are transferred to a specified company. When performing this transfer process, the sales management device 1 of the embodiment displays a list of companies that can be specified as transfer destinations (a list of companies to be liquidated). This allows the business operator to recognize at a glance the companies that can be specified as transfer destinations. This makes it possible to quickly complete the transfer process of accounts receivable to companies that can be specified as transfer destinations.
[0022] When the transfer process is complete, the deposit process of "Cash (CASH) / Unpaid", which is the result of the transfer process, is carried out. Also, when the transfer process is complete, journal entry data reflecting the result of the transfer process is generated and recorded in the accounting system on the network or in the memory unit 2. Also, when the transfer process is complete, the sales management device 1 of the embodiment reflects the result of the transfer process in the credit amount management table indicating the credit amount set for each company. This makes it possible to perform credit management based on the actual credit amount excluding the credit amount transferred.
[0023] (Details of accounts receivable processing) Next, the processing operation of the sales management device 1 according to the embodiment for such accounts receivable will be described in detail with reference to the flowchart in Fig. 3. First, the business operator specifies the input of sales for accounts receivable, or the input of bills receivable, which is an example of other receivables. In step S1, the acquisition unit 21 determines whether or not the business operator has specified the input of sales for accounts receivable. If it is determined that the business operator has specified the input of sales for accounts receivable (step S1: Yes), the process proceeds to step S2.
[0024] If it is determined that the bill receivable input has been designated by the business operator (step S1: No), the process proceeds to step S21 in the flowchart of Fig. 9. The process operation of the bill receivable input will be described later.
[0025] When the business operator designates the input of accounts receivable sales and the process proceeds to step S2, the data processing unit 22 generates collection schedule data including the planned collection amount and planned collection date for each billing recipient. Figure 4(b) shows an example of this collection schedule data. As shown in Figure 4(b), the collection schedule data is made up of billing recipients such as Company A to Company D, a posting date such as April 1st, a planned collection date such as September 30th, the planned collection amount and the paid amount for each billing recipient, etc.
[0026] Next, when the collection schedule data is generated, the display control unit 23 determines in step S3 whether or not the business operator has performed a liquidation target list display operation to specify a list display of billing destinations to which the accounts receivable can be transferred. When the display control unit 23 detects the liquidation target list display operation (step S3: Yes), it refers to the billing destination master 11 illustrated in Fig. 4(a) and detects billing destinations to which the accounts receivable can be transferred.
[0027] Specifically, as shown in Fig. 4(a), the invoice destination master 11 stores an accounts receivable securitization target flag (accounts receivable securitization target FLG) indicating whether the invoice destination is a invoice destination to which receivables such as accounts receivable or bills receivable can be transferred, along with each invoice destination name and a unique invoice destination code assigned to the invoice destination name. An accounts receivable securitization target flag of "1" indicates that the invoice destination is a invoice destination to which receivables can be transferred, and an accounts receivable securitization target flag of "0" indicates that the invoice destination is a invoice destination to which receivables cannot be transferred.
[0028] The display control unit 23 functions as an example of a detection unit, and detects from the invoice master 11 invoice destinations to which the accounts receivable securitization target flag of "1" has been added, indicating that the invoice destination is a invoice destination to which receivables can be transferred. In the example of FIG. 4(a), the accounts receivable securitization target flag of "1" has been added to Company A and Company D, indicating that the invoice destination is a invoice destination to which receivables can be transferred. Therefore, the display control unit 23 detects Company A and Company D from the invoice master 11. Then, referring to the scheduled collection data of Company A and Company D shown in FIG. 4(b), the display control unit 23 displays a securitization target list, which is a list of the accounting date, invoice destination name, scheduled collection date, and transferable amount of Company A and Company D, as shown in FIG. 4(c) (step S4).
[0029] By displaying this list of targets for securitization, the business operator can instantly recognize invoice recipients to which receivables can be transferred. When there are many invoice recipients, receivables that can be securitized and receivables that cannot be securitized are mixed together, making management cumbersome. However, by displaying such a list of targets for securitization, the sales management device 1 of the embodiment can quickly and clearly recognize invoice recipients to which receivables can be transferred and perform the transfer process described below. This makes it possible to perform the receivable transfer process accurately and quickly.
[0030] Here, when the display control unit 23 displays the list of liquidation targets, it arranges and displays each billing destination from top to bottom in descending order of the amount that can be transferred, as shown in FIG. 4(c). In the example of FIG. 4(c), the transferable amount for Company A is "1000 yen", and the transferable amount for Company D is "4000 yen". Therefore, the display control unit 23 first displays Company D in the list of liquidation targets, and then displays Company A in the next row. As a result, each billing destination is arranged and displayed in descending order of the amount that can be transferred, so that the business operator can quickly recognize the amount that can be transferred, and the receivable transfer process described below can be performed more accurately and quickly.
[0031] In this example, the securitization targets are displayed in a list in descending order of amount. However, the securitization targets may be rearranged and displayed in a list according to other priorities designated by the business operator, such as the earliest scheduled collection date (the securitization targets may be displayed in a list according to other priorities).
[0032] Next, the business operator performs a transfer operation of the receivables to the billing destinations shown in the liquidation target list. In step S5 of the flowchart in Fig. 3, the data processing unit 22 determines whether or not the business operator has performed a transfer operation. When the data processing unit 22 detects a transfer operation by the business operator (step S5: Yes), it generates collection schedule data that reflects this receivable transfer operation. The display control unit 23 displays the generated collection schedule data (step S6).
[0033] Specifically, when a receivable transfer process is specified by the business operator, the display control unit 23 displays a receivable transfer input screen as exemplified in Fig. 5. Of these, Fig. 5(a) is an example of the main screen of the receivable transfer input screen. As shown in Fig. 5(a), the main screen of the receivable transfer input screen is configured to include an input field (extraction conditions) for the billing destination to which the receivable is to be transferred, an input field for the company to which the receivable is to be transferred, and a display field for transferable details (details display section).
[0034] Through this main screen, the business operator specifies, for example, "Company Z" as the transferee of the receivables, and "Company D" as the billing recipient to which the receivables will be transferred. When "Company D" is specified as the billing recipient to which the receivables will be transferred, the display control unit 23 displays a list of details of the receivables to be transferred by Company D in the details display unit. The business operator selects the details of the receivables to be transferred from the details of the receivables displayed in this list. When the details of the receivables to be transferred are selected from the details of the receivables displayed in the list, the display control unit 23 displays a sub-screen of the receivable transfer input screen, as shown in FIG. 5(b) as an example.
[0035] The display control unit 23 displays on the sub-screen the transfer origin number such as "X0001", the transfer origin amount such as "4000 yen", and the initial scheduled collection date such as "September 30th", which correspond to the details of the receivables to be transferred selected from the main screen. The display control unit 23 also displays on this sub-screen an input field for the date of transfer (input field for transfer date) and an input field for the amount of transfer (input field for transfer amount). The business operator inputs the desired date of transfer of the receivables in the input field for transfer date, and inputs the amount of transfer in the input field for transfer amount. Then, the business operator operates a registration button on this sub-screen with the word "Register" written on it. As a result, the data processing unit 22 functions as an example of a collection data generation unit, and generates scheduled collection data that reflects the receivables transfer operation by the business operator.
[0036] FIG. 4(d) is an example of collection schedule data reflecting the transfer processing of claims. The example of FIG. 4(d) is an example of a transfer processing of a claim of 4000 yen from company D to company Z. Also, the example of FIG. 4(d) is an example of a transfer processing of a claim of 1000 yen from company A to company Z. In this case, the data processing unit 22 cancels the claim of "1000 yen" of company A by setting the amount of payment of company A to "1000 yen", and instead records the claim of "1000 yen" in the amount of expected collection of company Z. Similarly, the data processing unit 22 cancels the claim of "4000 yen" of company D by setting the amount of payment of company D to "4000 yen", and instead records the claim of "4000 yen" in the amount of expected collection of company Z. As a result, the claims of company A and company D are transferred together to company Z.
[0037] Next, in step S7 of the flowchart in FIG. 3, the data processing unit 22 functions as an example of a credit management summary table generating unit, and reflects the result of the receivable transfer process in the credit management summary table. That is, in the credit master 12 stored in the memory unit 2, a credit amount such as "10,000 yen" is set for each billing destination of A Company to D Company, as shown in FIG. 6(a). By referring to the credit master 12, the data processing unit 22 generates a credit management summary table including the base date, billing destination, credit amount, receivable balance, outstanding bill balance, and recordable amount (credit balance), as shown in FIG. 6(b). When the receivable transfer process is performed, the data processing unit 22 reflects the result of the receivable transfer process in the credit management summary table.
[0038] Specifically, in FIG. 6(b), in the case of Company A, the receivable of "1000 yen" has been cleared as described above, so the recordable amount (credit balance) is "10,000 yen." In contrast, in the case of Company B, there is a receivable balance of "2000 yen." Therefore, the recordable amount (credit balance) of Company B is "8000 yen." In addition, in the case of Company C, there is a receivable balance of "3000 yen." Company C also has an outstanding bill balance of "7000 yen," which will be described later. Therefore, the total amount of receivables is "10,000 yen," so the recordable amount (credit balance) is "0 yen." In addition, in the case of Company D, the receivable balance is "0 yen," but the outstanding bill balance, which will be described later, is "80,000 yen." Therefore, the recordable amount (credit balance) is "2000 yen."
[0039] In this example, credit management of the transferee, company Z, is not generally performed. As an example, in this embodiment, company Z is not registered in the credit master 12. For this reason, company Z is not displayed in the credit management summary table.
[0040] Next, in step S8 of the flowchart in Fig. 3, the display control unit 23 monitors whether or not the business operator has performed an operation to display the credit management summary table described above. If the display operation of the credit management summary table is detected (step S8: Yes), the display control unit 23 displays the credit management summary table reflecting the results of the receivables transfer process in step S9, as described above. This allows the fluctuation in credit amount according to receivables to be recognized, and accurate credit management for each billing destination can be performed.
[0041] Next, in step S10 of the flowchart in Fig. 3, the data processing unit 22 monitors whether or not a journal entry operation has been performed by the business operator. When a journal entry operation is detected (step S10: Yes), the data processing unit 22 functions as an example of a journal entry data generation unit, and generates journal entry data that reflects the transfer processing of the receivables corresponding to the operation of the business operator. The communication control unit 25 functions as an example of an accounting unit, and accounts for the generated journal entry data in the accounting system of the accounting terminal device 9 via the communication interface unit 4 and the network 8 (step S11). Note that, as described above, if an accounting system is provided in the storage unit 2, the generated journal entry data may be accounted for in the accounting system of the storage unit 2.
[0042] Specifically, Fig. 7(a) is an example of journal entry data as of April 1, when accounts receivable sales were entered. In the example of Fig. 7(a), April 1 is the posting date, and the debit is accounts receivable and the credit is sales, and journal entry data of 1,000 yen, 2,000 yen, 3,000 yen, and 4,000 yen are posted to the accounting system.
[0043] Next, as mentioned above, assume that on June 1st, the receivables of Company A and Company D are transferred to Company Z. In this case, as shown in Figure 7(b), the accounting date is June 1st, and journal entry data of 1,000 yen and 2,000 yen is generated with the debit side as unpaid transfer and the credit side as accounts receivable, and is recorded in the accounting system.
[0044] As a result, the accounting system generates a trial balance showing a balance of 7,000 yen with June 1 as the base date and accounts receivable as shown in Figure 7(c). The balance of 15,000 yen shown in Figure 7(c) is the balance of notes receivable, which will be described later. Of the 14,000 yen unpaid transfer balance shown in Figure 7(c), 3,000 yen of this 14,000 yen is the balance of accounts receivable. The remaining balance of 11,000 yen is the balance of notes receivable, which will be described later. More details will be provided below.
[0045] The output control unit 24 shown in Fig. 1 obtains a trial balance from the accounting system of the accounting terminal device 9 or the accounting system of the storage unit 2. Then, the output control unit 24 outputs (prints or displays) this trial balance via the output device 7 in accordance with the output instructions of the business operator. This makes it possible to recognize the accurate balance amount reflecting the receivable transfer processing and to perform receivable management.
[0046] (Overview of bills receivable processing) Next, Fig. 8 shows an outline of processing by the sales management device 1 of the embodiment for bills receivable, which are an example of other receivables. In the case of bills receivable, the business operator performs bills receivable input under "bills receivable / accounts receivable" in the sales management device 1. If the bills receivable is not transferred, collection input under "cash (CASH) / bills receivable" is performed as is.
[0047] In response to this, a transfer process is also possible in which a bill receivable is transferred to a specified company. When performing this transfer process, the sales management device 1 of the embodiment displays a list of companies that can be specified as transfer destinations (a list of companies to be liquidated). This allows the business operator to recognize at a glance the companies that can be specified as transfer destinations. This makes it possible to quickly complete the transfer process of the bill receivable to the companies that can be specified as transfer destinations.
[0048] When the transfer process is complete, the deposit process of "Cash (CASH) / Unpaid", which is the result of the transfer process, is carried out. Also, when the transfer process is complete, journal entry data reflecting the result of the transfer process is generated and recorded in the accounting system on the network or in the memory unit 2. Also, when the transfer process is complete, the sales management device 1 of the embodiment reflects the result of the transfer process in the credit amount management table indicating the credit amount set for each company. This makes it possible to perform credit management based on the actual credit amount excluding the credit amount transferred.
[0049] (Details of bills receivable processing) Next, the processing operation of the sales management device 1 of the embodiment for such a bill receivable will be described in detail with reference to the flowchart of Fig. 9. In the above-mentioned flowchart of Fig. 3, if it is determined that the operation by the business operator is not an operation for inputting sales of accounts receivable (step S1: No), the process proceeds to step S21 of the flowchart of Fig. 9.
[0050] In step S21, the data processing unit 22 generates bills receivable data (another example of scheduled collection data) including the scheduled collection amount and scheduled collection date of each bill recipient. Fig. 10(b) shows an example of this bills receivable data. As shown in Fig. 10(b), the bills receivable data is composed of bill recipients such as Company A to Company D, a submission date such as March 1, a settlement date such as September 30, the bill amount and the paid amount of each bill recipient, etc.
[0051] Next, when the bill receivable data is generated, the display control unit 23 determines in step S22 whether or not the business operator has performed a liquidation target list display operation to specify a list display of bill recipients for which transfer processing of bills receivable is possible. When the display control unit 23 detects the liquidation target list display operation (step S22: Yes), it refers to the bill recipient master 11 illustrated in Fig. 10(a) and detects bill recipients for which transfer processing of bills receivable is possible.
[0052] 10(a), the billing destination master 11 stores, together with each billing destination name and a unique billing destination code assigned to the billing destination name, an accounts receivable securitization target flag (accounts receivable securitization target FLG) that indicates whether the billing destination is a billing destination to which receivables such as accounts receivable or bills receivable can be transferred. Note that an accounts receivable securitization target flag of "1" indicates that the billing destination is a billing destination to which receivables can be transferred, and an accounts receivable securitization target flag of "0" indicates that the billing destination is a billing destination to which receivables cannot be transferred.
[0053] The display control unit 23 detects billing destinations to which the accounts receivable securitization target flag of "1" is added, indicating that the billing destination is a billing destination to which receivables can be transferred, from the billing destination master 11. In the example of FIG. 10(a), the accounts receivable securitization target flag of "1" is added to Company A and Company B, indicating that the billing destination is a billing destination to which receivables can be transferred. Therefore, the display control unit 23 detects Company A and Company B from the billing destination master 11. Then, referring to the bill receivable data of Company A and Company B shown in FIG. 10(b), the display control unit 23 displays a securitization target list, which is a list of the submission date, billing destination name, settlement date, and transferable amount of Company A and Company B, as shown in FIG. 10(c) (step S23).
[0054] By displaying this list of targets for securitization, the business operator can instantly recognize invoice recipients to which receivables can be transferred. When there are many invoice recipients, receivables that can be securitized and receivables that cannot be securitized are mixed together, making management cumbersome. However, by displaying such a list of targets for securitization, the sales management device 1 of the embodiment can quickly and clearly recognize invoice recipients to which receivables can be transferred and perform the transfer process described below. This makes it possible to perform the receivable transfer process accurately and quickly.
[0055] Here, when the display control unit 23 displays the list of liquidation targets, as shown in FIG. 10(c), the display control unit 23 arranges the billing destinations from the top row to the bottom row in descending order of the amount that can be transferred. In the example of FIG. 10(c), the amount that can be transferred of company A is "5000 yen", and the amount that can be transferred of company B is "6000 yen". Therefore, the display control unit 23 displays company B first in the liquidation target list, and company A in the next row. As a result, the billing destinations are arranged in descending order of the amount that can be transferred, so that the business operator can quickly recognize the amount that can be transferred, and the transfer process of the receivables described below can be performed more accurately and quickly. As described above, the liquidation targets may be displayed in a list in order of priority other than the amount.
[0056] Next, the business operator performs a transfer operation of the receivables to the bill-to-be indicated in the liquidation target list. In step S24 of the flowchart in Fig. 9, the data processing unit 22 determines whether or not the business operator has performed a transfer operation. When the business operator performs a transfer operation (step S24: Yes), the data processing unit 22 generates bills receivable data that reflects the receivables transfer operation performed by the business operator. The display control unit 23 displays the generated bills receivable data (step S25).
[0057] Specifically, when the business operator specifies a transfer process for a receivable, the display control unit 23 displays a screen for the transfer process of a bill receivable, as exemplified in Fig. 11. Of these, Fig. 11(a) is an example of a bill transfer input screen. As shown in Fig. 11(a), the bill transfer input screen is configured to include an input field for the company to which the bill receivable is to be transferred, an input field for the transfer date, and a display field for the details that can be transferred.
[0058] Through this bill transfer input screen, the business operator specifies, for example, "Company Z" as the transfer destination of the bill receivable, and selects "Company B" as the transfer target of the bill receivable. Then, the business operator operates the registration button marked with the word "Register" on the bill transfer input screen. When this registration button is operated, the display control unit 23 displays the receivable recording input screen, as shown in FIG. 11(b).
[0059] The display control unit 23 displays the transfer date of June 1, which was entered on the bill transfer input screen, as the recording date on the receivables recording input screen, and displays Company Z, which was entered on the bill transfer input screen as the transfer destination, as the billing destination on the receivables recording input screen. The display control unit 23 also displays the amount of "6000 yen" of Company B, whose bill number is "T002" and which was selected on the bill transfer input screen, in the details column as the detailed amount on the receivables recording input screen. The business operator enters a scheduled collection date, for example, July 31, on this receivables recording input screen, and operates a registration button marked with the word "Register" that is provided on this receivables recording input screen. As a result, the data processing unit 22 generates bills receivable data that reflects the bills receivable transfer operation performed by the business operator.
[0060] Figure 10(d) is an example of bills receivable data that reflects the transfer processing of bills receivable. In the example of Figure 10(d), Company A sells a 5,000 yen bill to Company Z, and Company B sells a 6,000 yen bill to Company Z. As a result, the bills of Company A and Company B are transferred together to Company Z. Note that after this transfer processing, Company Z's receivable becomes collection schedule data, and is not reflected in the bills receivable data.
[0061] Next, in step S26 of the flowchart in FIG. 9, the data processing unit 22 reflects the results of the transfer processing of the bills receivable in the credit management summary table. That is, as explained using FIG. 6(a), the credit master 12 has a credit amount, for example, "10,000 yen" set for each bill-to-be of companies A to D. By referring to the credit master 12, the data processing unit 22 generates a credit management summary table including the base date, bill-to-be, credit amount, receivable balance, outstanding bill balance, and recordable amount (credit balance), as shown in FIG. 6(b). When the transfer processing of the bills receivable is performed, the data processing unit 22 reflects the results of the transfer processing of the bills receivable in this credit management summary table.
[0062] Specifically, in Figure 6(b), in the case of Company A, the receivable of "1,000 yen" has been cleared as described above, so the recordable amount (credit balance) is "10,000 yen." In contrast, in the case of Company B, there is a receivable balance of "2,000 yen." Therefore, the recordable amount (credit balance) of Company B is "8,000 yen." In addition, in the case of Company C, there is a receivable balance of "3,000 yen" and an outstanding bill of "7,000 yen." Therefore, the total amount of receivables is "10,000 yen," so the recordable amount (credit balance) is "0 yen." In addition, in the case of Company D, the receivable balance is "0 yen," but the outstanding bill of "80,000 yen." Therefore, the recordable amount (credit balance) is "2,000 yen."
[0063] In this example, credit management of the transferee, company Z, is not generally performed. As an example, in this embodiment, company Z is not registered in the credit master 12. For this reason, company Z is not displayed in the credit management summary table.
[0064] Next, in step S27 of the flowchart in Fig. 9, the display control unit 23 monitors whether or not the business operator has performed an operation to display the credit management summary table described above. If an operation to display the credit management summary table is detected (step S27: Yes), the display control unit 23 displays the credit management summary table reflecting the results of the transfer process of the bill receivable, as described above, in step S28. This allows the fluctuation in credit amount according to receivables to be recognized, and accurate credit management for each billing destination can be performed.
[0065] Next, in step S29 of the flowchart in Fig. 9, the data processing unit 22 monitors whether or not a journal entry operation has been performed by the business operator. When a journal entry operation is detected (step S29: Yes), the data processing unit 22 generates journal entry data corresponding to the operation by the business operator. The communication control unit 25 records the generated journal entry data in the accounting system of the accounting terminal device 9 via the communication interface unit 4 and the network 8 (step S30). Note that, as described above, if an accounting system is provided in the storage unit 2, the generated journal entry data may be recorded in the accounting system of the storage unit 2.
[0066] Specifically, Figure 12(a) is an example of journal entry data as of March 1, when a bill receivable was entered. The example in Figure 12(a) is an example in which journal entry data of 5,000 yen, 6,000 yen, 7,000 yen, and 8,000 yen was entered into the accounting system on March 1, with the debit side being bills receivable and the credit side being accounts receivable, etc.
[0067] Next, as mentioned above, assume that on June 1st, the notes receivable of Company A and Company B are transferred to Company Z. In this case, as shown in Figure 12(b), the journal entry data for 5,000 yen and 6,000 yen is generated with June 1st as the recording date, the debit side as unpaid transfer, and the credit side as notes receivable, and is recorded in the accounting system.
[0068] As a result, in the accounting system, a trial balance is generated showing a balance of 15,000 yen with June 1 as the base date and the account item as "notes receivable" as shown in FIG. 12(c). The breakdown of this 15,000 yen balance is as follows. That is, the total amount of the journal entry data at the time of inputting the notes receivable on March 1 as shown in FIG. 12(a) is "5,000 yen + 6,000 yen + 7,000 yen + 8,000 yen = 25,000 yen." In contrast, by the transfer process on June 1 as shown in FIG. 12(b), "5,000 yen + 6,000 yen = 11,000 yen" was transferred to Company Z. Therefore, the balance amount as of June 1 is "15,000 yen" as shown in FIG. 12(c).
[0069] The 7,000 yen balance shown in Figure 12(c) is the balance due to the transfer process of the accounts receivable mentioned above. Of the 14,000 yen balance of unpaid transfers shown in Figure 12(c), the 3,000 yen balance is the accounts receivable balance. The remaining 11,000 yen balance of unpaid transfers is the balance of notes receivable due to the transfer process shown in Figure 12(c) (5,000 yen + 6,000 yen = 11,000 yen).
[0070] The output control unit 24 shown in Fig. 1 obtains a trial balance from the accounting system of the accounting terminal device 9 or the accounting system of the storage unit 2. Then, the output control unit 24 outputs (prints or displays) this trial balance via the output device 7 in accordance with the output instructions of the business operator. This makes it possible to recognize the accurate balance amount reflecting the receivable transfer processing and to perform receivable management.
[0071] (Effects of the embodiment) As is clear from the above description, the sales management device 1 according to the embodiment can achieve the following effects.
[0072] When there are many business partners, receivables that can be liquidated and receivables that cannot be liquidated are mixed, making management complicated. In addition, since the initial scheduled payment date and the actual payment date for receivables that can be liquidated differ, it is difficult to accurately manage cash flow plans. However, the sales management device 1 of the embodiment can check transferable receivable candidates in a list, which makes it easier to manage receivables. In addition, when displaying the list of receivable candidates, by displaying them in order of priority, such as the scheduled collection date or amount, the business operator can more easily recognize transferable receivable candidates, making receivable management even easier.
[0073] The collection schedule data or bills receivable data resulting from the receivable transfer process can be used to accurately manage the scheduled payment destination and scheduled payment date for each receivable before and after the receivable is assigned.
[0074] Furthermore, by reflecting the transfer processing of claims in the credit management summary table, it becomes possible to perform credit management based on the actual claim amount excluding the transferred claim amount after the claim is transferred.
[0075] By generating accounting data after the receivables transfer process and sending it to the accounting system, the sales management device 1 can check the details of the expected collection after the receivables transfer, and the accounting system can also manage the balance after the transfer.
[0076] [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.
[0077] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of goals 12, 13, and 15 of the SDGs.
[0078] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.
[0079] [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.
[0080] 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.
[0081] In addition, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.
[0082] Moreover, with regard to the sales management device 1, the components shown in the figures are merely conceptual functional components, and the device does not necessarily have to be physically configured as shown in the figures.
[0083] For example, the processing functions of the sales management device 1, particularly the control unit 3 and each processing function performed by the control unit 3, may be realized in whole or in part by a CPU (Central Processing Unit) 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 sales management device 1 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. This computer program is executed by being loaded into a RAM, and constitutes the control unit 3 in cooperation with the CPU.
[0084] In addition, the sales management program of this sales management device 1 may be stored in another server device connected to the sales management device 1 via any network, and it is also possible to download all or part of it as needed.
[0085] The transport temperature management 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 term "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.
[0086] 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 achieves its function by working with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in the sales management device 1 shown in the embodiment, as well as the installation procedure after reading, may use well-known configurations and procedures.
[0087] The memory unit 2 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, and web page files used for various processes and providing websites.
[0088] The sales management device 1 may be configured as an information processing device such as a known personal computer device or a workstation, or may be configured as an information processing device connected to any peripheral device. The information processing device may be realized by implementing software (including programs or data, etc.) that realizes the processing described in this embodiment.
[0089] Furthermore, the specific form of distribution and integration of the devices is not limited to those 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 function additions. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively. [Industrial Applicability]
[0090] The present invention is useful for operations that handle receivables. Specifically, the present invention is useful for the receivables operations of a company that is in a tight cash flow situation and is performing receivables assignment and factoring to quickly raise funds, the receivables operations of a company in which a finance company of a corporate group collectively manages receivables, or the receivables operations of a company that has a mixture of accounts receivable and bills receivable and is performing credit management. [Explanation of symbols]
[0091] 1 Sales management device 2 Storage section 3. Control Unit 4. Communication Interface Section 5 Input / Output Interface Section 6 Input Devices 7 Output Devices 8 Network 9. Accounting terminal equipment 11 Billing Master 12 Credit Master 21 Acquisition Department 22 Data Processing Section 23 Display control section 24 Output control section 25 Communication control section
Claims
1. an acquisition unit for acquiring inputted collection schedule data of receivables including a collection schedule date and a collection schedule amount for each billing party; a detection unit that detects, from among the billing destinations for which the collection schedule data has been acquired, billing destinations designated as targets for accounts receivable securitization by referring to a billing destination master in which accounts receivable securitization target information indicating whether each of the billing destinations is a target for accounts receivable securitization is stored; a display control unit that displays a list of the collection schedule data of the billing recipients that are designated as accounts receivable securitization targets detected by the detection unit, among the collection schedule data of the billing recipients acquired by the acquisition unit; a collection data generation unit that generates the collection schedule data reflecting a transfer process of the receivables performed based on a list of billing destinations designated as the accounts receivable securitization targets; A sales management device having the above configuration.
2. The display control unit displays a list of collection schedule data of the billing destination in accordance with a predetermined priority order.
2. The sales management device according to claim 1,
3. The display control unit displays a list of the collection schedule data of the billing destination in order of the highest collection schedule amount or the earliest collection schedule date.
3. The sales management device according to claim 2,
4. Further comprising a credit management summary table generating unit for generating a credit management summary table showing the credit amount of each of the billing parties reflecting the transfer processing of the receivables.
4. The sales management device according to claim 1, wherein:
5. a journal data generation unit for generating journal data that reflects the transfer processing of the receivables; and an accounting unit that records the generated journal data in an accounting system.
5. The sales management device according to claim 4,
6. an acquisition step of acquiring, by an acquisition unit, collection schedule data of the receivable including the collection schedule date and collection schedule amount of each input billing party; a detection step in which a detection unit detects, among the billing destinations for which the collection schedule data has been acquired, billing destinations designated as targets for accounts receivable securitization by referring to a billing destination master in which accounts receivable securitization target information indicating whether each of the billing destinations is a target for accounts receivable securitization is stored; a display control step of displaying a list of collection schedule data of the billing party designated as a target for accounts receivable securitization detected in the detection step, among the collection schedule data of each billing party acquired in the acquisition step, by a display control unit; a collection data generation step in which a collection data generation unit generates the collection schedule data reflecting a transfer process of the receivables performed based on a list of billing destinations designated as the accounts receivable securitization targets; A sales management method having the above structure.
7. Computer, an acquisition unit for acquiring inputted collection schedule data of receivables including a collection schedule date and a collection schedule amount for each billing party; a detection unit that detects, from among the billing destinations for which the collection schedule data has been acquired, billing destinations designated as targets for accounts receivable securitization by referring to a billing destination master in which accounts receivable securitization target information indicating whether each of the billing destinations is a target for accounts receivable securitization is stored; a display control unit that displays a list of the collection schedule data of the billing recipients that are designated as accounts receivable securitization targets detected by the detection unit, among the collection schedule data of the billing recipients acquired by the acquisition unit; To function as a collection data generating unit that generates the collection schedule data that reflects the transfer processing of the receivables performed based on the list of billing destinations designated as the accounts receivable securitization targets. A sales management program that features:
Citation Information
Patent Citations
Device for fluidizing credit
JP2003242360A
Liquid claim management system and method
JP2005275955A
Credit line output system, credit line transmission system, and credit line setting system
JP2006107427A
