JP7565739B2 - Credit and payable management device, business support program, and business support method - Google Patents

Description

The present invention relates to an account receivable/payable management device, a business support program, and a business support method.

Conventionally, an account receivable/payable management device has been used to manage accounts receivable and payable within a company. When accounts payable and accounts receivable are incurred within the same corporation, the account receivable management device may be used to carry out offsetting procedures.

Patent document 1 also describes how offsetting is performed when managing debit and credit notes.

JP 2018-028843 A

To perform offsetting, it is necessary to determine the billing and payment recipients that are subject to offsetting, the amount that can be offset, and the offsetting date. Furthermore, if your company or another company is engaged in multiple businesses and manages accounts receivable and payable by business division, it is necessary to perform offsetting within each business division. Therefore, the operator performing the offsetting process must make these decisions and then register the offsetting process for each item, which is time-consuming.

The present invention has been made in consideration of the above, and aims to provide an account receivable/payable management device, a business support program, and a business support method that can reduce the burden on operators who manage accounts receivable and payable within a company.

In order to solve the above-mentioned problems and achieve the object, the receivables/payables management device of the present invention is an receivables/payables management device equipped with a control unit, which is capable of accessing a billing destination master for managing billing destinations on an intra-company organizational basis, in which payment identification information for identifying whether payments are made collectively on an intra-company basis or individually on an intra-company organizational basis is set in association with the billing destination, a payee master for managing payees on an intra-company organizational basis, in which payment identification information for identifying whether payments are made collectively on an intra-company basis or individually on an intra-company organizational basis is set in association with the payee, collection schedule data including collection schedule information including a scheduled collection amount and the billing destination, and payment schedule data including payment schedule information including a scheduled payment amount and the payee, and the control unit is capable of accessing from the collection schedule data and the payment schedule data collection schedule information and payment schedule information including a scheduled payment amount and the payee, The offset processing target selection means extracts fixed information, displays the extracted collection schedule information and payment schedule information on a screen for each company as candidates for offset processing of receivables and payables, and allows the user to select the collection schedule information and payment schedule information to be offset on the screen; and a collective offset processing means creates mutually linked deposit management data and payment management data, deposit reconciliation management data linked to the collection schedule data and the deposit management data, and payment reconciliation management data linked to the payment schedule data and the payment management data, based on the information selected by the offset processing target selection means and taking into consideration the deposit identification information in the billing destination master, the payment identification information in the payment destination master, and the offsettable amount for each company defined as the smaller of the total of the collection schedule amount and the total of the payment schedule amount for each company.

In addition, in the receivables/payables management device according to the present invention, the control unit may further include an offset schedule creation means for extracting, from the collection schedule data and payment schedule data, collection schedule information and payment schedule information for which the billing destination and payment destination are the same intra-company organization, and creating an offset schedule that displays the extracted collection schedule information and payment schedule information by company as candidates for offset processing of receivables/payables.

In addition, in the receivables/payables management device according to the present invention, the control unit may update the collection schedule data based on the deposit reconciliation management data and update the payment schedule data based on the payment reconciliation management data.

In addition, in the receivables/payables management device according to the present invention, the control unit may further include an input means for accepting input of the deposit identification information and the payment identification information.

In addition, in the receivables/payables management device according to the present invention, the offset processing target selection means may display on the screen as candidates for offset processing of the receivables/payables those whose total planned recovery amount per company is equal to or greater than the total planned payment amount.

In addition, in the receivables/payables management device according to the present invention, the offset processing target selection means may display on the screen as candidates for offset processing targets for the receivables/payables those for which the total of the amounts planned to be collected per company is smaller than the total of the amounts planned to be paid.

In addition, the business support program according to the present invention is for causing a control unit of an account receivable/payable management device having a control unit to execute the program, and is capable of accessing a billing destination master that manages billing destinations by organizational unit within a company, in which payment identification information for identifying whether payments are made collectively by company unit or individually by organizational unit within a company is set in association with the billing destination, a payment destination master that manages payment destinations by organizational unit within a company, in which payment identification information for identifying whether payments are made collectively by company unit or individually by organizational unit within a company is set in association with the payee, collection schedule data including collection schedule information including the planned collection amount and the billing destination, and payment schedule data including payment schedule information including the planned payment amount and the payee, and extracting collection schedule information and payment schedule information in which the billing destination and the payee are in the same intra-company organization from the collection schedule data and the payment schedule data. and an offsetting process target selection step for displaying the extracted collection schedule information and payment schedule information on a screen for each company as candidates for offsetting the receivables and payables, and allowing the user to select the collection schedule information and payment schedule information to be offset on the screen; and a batch offsetting process step for creating mutually linked deposit management data and payment management data, deposit reconciliation management data linked to the collection schedule data and the deposit management data, and payment reconciliation management data linked to the payment schedule data and the payment management data, based on the information selected in the offsetting process target selection step and taking into consideration the deposit identification information in the billing destination master, the payment identification information in the payment destination master, and the offsettable amount for each company defined as the smaller of the total of the collection schedule amount and the total of the payment schedule amount for each company.

In addition, the business support method according to the present invention is executed by a control unit of an account receivable/payable management device having a control unit, and is capable of accessing a billing destination master for managing billing destinations by intra-company organization units, in which payment identification information for identifying whether payments are made collectively by company unit or individually by intra-company organization unit is set in association with the billing destination, a payment destination master for managing payment destinations by intra-company organization units, in which payment identification information for identifying whether payments are made collectively by company unit or individually by intra-company organization unit is set in association with the payee, collection schedule data including collection schedule information including a scheduled collection amount and a billing destination, and payment schedule data including payment schedule information including a scheduled payment amount and a payee, and extracting collection schedule information and payment schedule information in which the billing destination and the payee are in the same intra-company organization from the collection schedule data and the payment schedule data, The offsetting process includes an offsetting process target selection step of displaying the collected collection schedule information and payment schedule information on a screen for each company as candidates for offsetting the receivables and payables, and allowing the user to select the collection schedule information and payment schedule information to be offset on the screen, and a batch offsetting process step of creating mutually linked deposit management data and payment management data, deposit reconciliation management data linked to the collection schedule data and the deposit management data, and payment reconciliation management data linked to the payment schedule data and the payment management data, based on the information selected in the offsetting process target selection step and taking into consideration the deposit identification information in the billing destination master, the payment identification information in the payment destination master, and the offsettable amount for each company defined as the smaller of the total of the planned collection amount and the total of the planned payment amount for each company.

The present invention has the effect of reducing the burden on operators who manage receivables and payables within a company.

FIG. 1 is a diagram showing an example of the configuration of an account receivable/payable management device. FIG. 2 is a correlation diagram of the master and data stored in the storage unit. FIG. 3 is a correlation diagram of the master and data stored in the storage unit. FIG. 4 is a correlation diagram of the master and data stored in the storage unit. FIG. 5 is a diagram showing the flow of processing executed by the credit and debt management device. FIG. 6 is a diagram showing the flow of processing executed by the credit/debt management device. FIG. 7 is a diagram illustrating an example of the establishment master. FIG. 8 is a diagram illustrating an example of the corporation master. FIG. 9 is a diagram showing an example of the billing destination master. FIG. 10 is a diagram showing an example of the payment destination master. FIG. 11 is a diagram illustrating an example of collection schedule data. FIG. 12 is a diagram showing an example of payment schedule data. FIG. 13 is a diagram showing an example of an offset schedule. FIG. 14 is a diagram showing an example of a batch offset processing screen. FIG. 15 is a diagram illustrating an example of a batch offset process. FIG. 16 is a diagram showing an example of a batch offset processing screen. FIG. 17 is a diagram showing an example of the deposit data. FIG. 18 is a diagram showing an example of the deposit details data. FIG. 19 is a diagram showing an example of payment data. FIG. 20 is a diagram showing an example of payment details data. FIG. 21 is a diagram showing an example of the payment reconciliation data. FIG. 22 is a diagram showing an example of payment reconciliation detail data. FIG. 23 is a diagram illustrating an example of collection schedule data. FIG. 24 is a diagram showing an example of payment reconciliation data. FIG. 25 is a diagram showing an example of payment reconciliation detail data. FIG. 26 is a diagram showing an example of payment schedule data.

Below, an embodiment of the receivables/payables management device, business support program, and business support method 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.

[1. Configuration]
An example of the configuration of an account receivable/payable 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 an account receivable/payable management device.

The accounts receivable/payable management device 100 supports the work of operators who manage accounts receivable and payable within a company. The accounts receivable management device 100 reduces the burden on operators who perform offsetting procedures when accounts payable and accounts receivable arise within the same corporation.

The receivables/payables management device 100 is a commercially available desktop personal computer. Note that the receivables/payables management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be 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.

The receivables/payables management device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit of the receivables/payables management device 100 is connected to each other so as to be able to communicate with each other via any communication path.

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

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 works with a mouse to provide 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.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, or the like.

The memory unit 106 stores, for example, business establishment master 106a, corporation master 106b, billing destination master 106c, payment destination master 106d, collection schedule data 106e, payment schedule data 106f, deposit data 106g, deposit detail data 106h, payment data 106i, payment detail data 106j, deposit reconciliation data 106k, deposit reconciliation detail data 106l, payment reconciliation data 106m, and payment reconciliation detail data 106n.

Figures 2 to 4 are correlation diagrams of the master and data stored in the memory unit. In Figures 2 to 4, the corresponding relationships between each item in each master and each data stored in the memory unit 106 are illustrated by arrows.

The establishment master 106a is a table that holds, for example, establishment codes and establishment names.

Corporate master 106b is a table that holds, for example, corporate codes and corporate names.

The billing destination master 106c is a table that holds, for example, billing destination codes, billing destination names, corporate codes, billing payment destination codes, and main business code. The billing destination master 106c manages billing destinations by intra-company organization. An intra-company organization corresponds to a "branch" or "head office" of a company with multiple business locations, or each "business G (group)" of a company that conducts multiple businesses. In the billing destination master 106c, payment identification information is set in association with the billing destination to identify whether the payment is made collectively by the company or individually by intra-company organization. When the payment is made collectively by the company, a common billing payment destination code is used for each intra-company organization. On the other hand, when the payment is made individually by intra-company organization, an individual billing payment destination code is used for each intra-company organization.

The payee master 106d is a table that holds, for example, payee codes, payee names, corporate codes, withdrawal payee codes, and main business code. The payee master 106d manages payees by intra-company organization. In the payee master 106d, payment identification information is set in association with the payee to identify whether payments are made collectively by company or individually by intra-company organization. When payments are made collectively by company, a common withdrawal payee code is used for each intra-company organization. On the other hand, when payments are made individually by intra-company organization, a separate withdrawal payee code is used for each intra-company organization.

Collection schedule data 106e is a table that holds, for example, the collection schedule number, collection schedule line number, accounting date, billing destination code, billing destination name, scheduled collection date, scheduled collection amount, reconciled amount, and payment reconciliation completion category. Collection schedule data 106e includes collection schedule information, including the scheduled collection amount and billing destination.

Payment schedule data 106f is a table that holds, for example, payment schedule number, payment schedule line number, accounting date, payee code, payee name, scheduled payment date, scheduled payment amount, reconciled payment amount, and payment reconciliation completion category. Payment schedule data 106f includes payment schedule information, including the scheduled payment amount and payee.

Deposit data 106g is a table that holds, for example, the deposit number, deposit invoice code, deposit invoice name, deposit date, deposit amount, reconciled deposit amount, and deposit reconciliation completion category.

Deposit details data 106h is a table that holds, for example, the deposit number, deposit details line number, deposit category, deposit amount, and offset payment number.

Payment data 106i is a table that holds, for example, payment number, withdrawal payee code, withdrawal payee name, payment date, payment amount, reconciled payment amount, payment reconciliation completion category, deposit number, and deposit detail line number.

Payment details data 106j is a table that holds, for example, payment number, payment details line number, payment category, and payment amount.

Deposit reconciliation data 106k is a table that holds, for example, the deposit reconciliation number, deposit invoice recipient code, deposit invoice recipient name, and deposit reconciliation date.

Deposit reconciliation detail data 106l is a table that holds, for example, the deposit reconciliation number, deposit reconciliation detail number, deposit number, scheduled collection number, scheduled collection detail line number, and the reconciled deposit amount.

Payment reconciliation data 106m is a table that holds, for example, the payment reconciliation number, withdrawal payee code, withdrawal payee name, and payment reconciliation date.

Payment reconciliation detail data 106n is a table that holds, for example, the payment reconciliation number, payment reconciliation detail number, payment number, payment schedule number, payment schedule detail line number, and reconciled payment amount.

The control unit 102 is a CPU or the like that provides overall control of the accounts receivable/payable 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. The control unit 102 can access the business establishment master 106a to payment reconciliation detail data 106n stored in the memory unit 106.

The control unit 102, in terms of its functional concept, comprises a business establishment master creation unit 102a, a customer integrated master creation unit 102b, a billing payment schedule input unit 102c, an expense payment schedule input unit 102d, an offset schedule creation unit 102e, an offset processing target selection unit 102f, and a lump-sum offset processing unit 102g.

Figures 5 and 6 show the flow of processing executed by the receivables/payables management device.

The establishment master creation unit 102a is an information processing means that generates the establishment master 106a.

The supplier integrated master creation unit 102b is an information processing means that generates a supplier integrated master including the corporate master 106b, the billing destination master 106c, and the payment destination master 106d. In other words, the supplier integrated master creation unit 102b is an input means that accepts input of deposit identification information and payment identification information.

The billing payment schedule input unit 102c is an information processing means that generates the collection schedule data 106e.

The expense payment schedule input unit 102d is an information processing means that generates payment schedule data 106f.

The offset schedule creation unit 102e is an information processing means that extracts collection schedule information and payment schedule information for which the billing destination and payee are the same intra-company organization from the corporate master 106b to the payee master 106d, collection schedule data 106e, and payment schedule data 106f, and creates an offset schedule that displays the extracted collection schedule information and payment schedule information by company as candidates for offset processing of receivables and payables.

The offset processing target selection unit 102f is an information processing means that extracts scheduled collection information and scheduled payment information from the scheduled collection data 106e and scheduled payment data 106f, where the billing destination and payment destination are the same intra-company organization, displays the extracted scheduled collection information and scheduled payment information on the screen by company as candidates for offset processing of receivables and payables, and allows the user to select the scheduled collection information and scheduled payment information to be the target of offset processing on the screen.

The lump-sum offset processing unit 102g is an information processing means that generates deposit data 106g, deposit detail data 106h, payment data 106i, payment detail data 106j, deposit reconciliation data 106k, deposit reconciliation detail data 106l, payment reconciliation data 106m, and payment reconciliation detail data 106n, and updates collection schedule data 106e and payment schedule data 106f. The lump-sum offset processing unit 102g is an information processing means that generates deposit data 106g, deposit detail data 106h, payment data 106i, payment detail data 106j, deposit settlement data 106k, deposit settlement detail data 106l, payment settlement data 106m, and payment settlement detail data 106n, and updates collection schedule data 106e and payment schedule data 106f, based on the information selected by the offset processing target selection unit 102f, and taking into consideration the deposit identification information in the billing destination master 106c, the payment identification information in the payment destination master 106d, and the offsettable amount for each company defined by the smaller of the total amount to be collected and the total amount to be paid per company, and updates the deposit management data (deposit data 106g and deposit detail data 106h) and payment management data (payment data 106i and payment detail data 106j), deposit settlement data, and payment management data (payment data 106i and payment detail data 106j), which are linked to each other. It is an information processing means that creates deposit management data (deposit reconciliation data 106k and deposit reconciliation detail data 106l) that is linked to collection schedule data 106e and deposit management data, and payment reconciliation management data (payment reconciliation data 106m and payment reconciliation detail data 106n) that is linked to payment schedule data 106f and payment management data, updates collection schedule data 106e based on the deposit reconciliation management data, and updates payment schedule data 106f based on the payment reconciliation management data.

2. Specific examples of processing
Here, a specific example of the processing executed by the credit/debt management device 100 will be described with reference to FIGS.

This explanation describes the process by which the receivables and payables management device 100 records revenue when revenue from principal transactions and revenue from agent transactions are mixed.

[S1: Business establishment master registration]
Based on the operator's input, the establishment master creating unit 102a registers the establishment master 106a in the storage unit 106. The establishment master 106a includes an establishment code and an establishment name (see FIG. 7).

[S2: Corporate master registration]
Based on the operator's input, the supplier integrated master creation unit 102b registers the corporation master 106b in the storage unit 106. The corporation master 106b includes a corporation code and a corporation name (see FIG. 8).

[S3: Billing destination master registration]
The integrated business partner master creation unit 102b registers the billing destination master 106c in the storage unit 106 based on the operator's input. The billing destination master 106c includes a billing destination code, a billing destination name, a corporate code, a billing payment destination code, and a representative business establishment code (see FIG. 9). In the example shown in FIG. 9, the billing payment destination code is unified among the various in-company organizations of Company A. That is, the billing payment destinations of the various in-company organizations of Company A are consolidated in the head office, which is the representative business entity. In contrast, the billing payment destination code of Companies B and C is different among the various in-company organizations. That is, Companies B and C make billing and receive payments individually to the various in-company organizations. Furthermore, the representative business entity code of Company C is different among the various in-company organizations. That is, each in-company organization of Company C manages its credits and payables individually.

[S4: Payee master registration]
The customer integrated master creation unit 102b registers the payee master 106d in the storage unit 106 based on the operator's input. The payee master 106d includes a payee code, a payee name, a corporation code, a withdrawal payee code, and a representative business code (see FIG. 10). In the example shown in FIG. 10, the withdrawal payee code of Company A is unified among the organizations in the company. That is, the withdrawal payees of each organization in the company A are consolidated in the head office, which is the representative business. In contrast, the withdrawal payee code of Companies B and C is different among the organizations in the company. That is, Companies B and C make withdrawals and payments to each organization in the company individually. Furthermore, the representative business code of Company C is different among the organizations in the company. That is, each organization in the company C manages its credits and payables individually.

[S5: Registration of collection schedule data]
The billing payment schedule input unit 102c registers the collection schedule data 106e in the storage unit 106 based on the operator's input. The collection schedule data 106e includes a collection schedule number, a collection schedule detail line number, an accounting date, a billing destination code, a billing destination name, a scheduled collection date, a scheduled collection amount, a payment cleared amount, and a payment clearing completion category (see FIG. 11). 0: incomplete or 1: complete is input to the payment clearing completion category.

[S6: Payment schedule data registration]
The expense payment schedule input unit 102d registers payment schedule data 106f in the storage unit 106 based on the operator's input. The payment schedule data 106f includes a payment schedule number, a payment schedule detail line number, an accounting date, a payee code, a payee name, a scheduled payment date, a scheduled payment amount, a reconciled payment amount, and a payment reconciliation completion category (see FIG. 12). 0: incomplete or 1: complete is input as the payment reconciliation completion category.

[S7: Output offset schedule]
The offset schedule creation unit 102e extracts the collection schedule information and payment schedule information for which the billing destination and the payment destination are the same intra-company organization from the corporation master 106b to the payment destination master 106d, the collection schedule data 106e, and the payment schedule data 106f registered in steps S2 to S6, and creates an offset schedule that displays the extracted collection schedule information and payment schedule information by company as candidates for offset processing of credits and debts (see FIG. 13).The offset schedule allows the operator to check the candidates for offset processing at a glance.

[S8: Bulk offset processing]
The offset processing target selection unit 102f extracts collection schedule information and payment schedule information where the billing destination and payment destination are the same internal company organization from the collection schedule data 106e and payment schedule data 106f registered in steps S5 and S6, and displays the extracted collection schedule information and payment schedule information on a screen (bulk offset processing screen) by company as candidates for offset processing of receivables and payables (see Figures 14 and 16).

As shown in Figure 14, when the Payment >= Recovery button BT1 is selected on the bulk offset processing screen, check boxes CB1 to CB4, CB11, and CB12 corresponding to the intra-company organizations whose total planned payment amounts are equal to or greater than the total planned recovery amounts are checked all at once. In this way, the offset processing target selection unit 102f displays on the screen as candidates for offset processing of receivables and payables those whose total planned recovery amounts per company are equal to or greater than the total planned payment amounts. When there are many planned payments, the difference after deducting the planned recovery amounts is used for processing to pay on the payment date, so the planned payment date can be used as the offset date and the processing can be carried out all at once on this screen.

In the example shown in FIG. 14, the total of "30,000" consisting of "10,000" generated by the Tokyo branch of Company A, which is the invoice recipient, and "20,000" generated by the Osaka branch of Company A is compared with the total of "50,000" consisting of "20,000" generated by the Tokyo branch of Company A, which is the payee, and "30,000" generated by the Osaka branch of Company A. It is determined that the amount that can be offset with Company A is "30,000", and the remaining "20,000" is paid. In addition, in the offsetting process, since it is necessary to perform offsetting process on the balance of accounts receivable and accounts payable generated by the invoice recipient and the payee, it is necessary to perform the process at the invoice recipient and the payee level, not on a corporate basis. Therefore, "20,000" generated by the Tokyo branch of Company A, which is the payee, is offset with "10,000" generated by the Tokyo branch of Company A, which is the invoice recipient, and "10,000" generated by the Osaka branch of Company A. In addition, for Company C's Textile Division, which manages accounts receivable and payable by division, the "20,000" incurred by Company C's Textile Business G, which is the invoice recipient, can only be offset against the "10,000" incurred by Company C's Textile Business G. As a result, the amount that can be offset by Company C's Textile Business G is determined to be "10,000," and the remaining "10,000" is paid.

As shown in Figure 15, by directly selecting check boxes CB1 to CB4, for example by selecting only check boxes CB2 and CB4, it is possible to perform offset processing for Company A's Osaka branch but not for Company A's Tokyo branch.

As shown in Figure 16, when the Payment < Recovery button BT2 is selected on the bulk offset processing screen, the check boxes CB5 to CB10 of the intra-company organizations whose total planned payment amount is less than the total planned recovery amount are checked all at once. In this way, the offset processing target selection unit 102f displays on the screen as candidates for offset processing of receivables and payables those whose total planned recovery amount per company is less than the total planned payment amount.

In the example shown in FIG. 16, the total of "50,000" consisting of "20,000" generated by the invoice recipient's Fukuoka branch and "30,000" generated by the Kyoto branch of Company B is compared with the total of "30,000" consisting of "10,000" generated by the payee's Fukuoka branch and "20,000" generated by the Kyoto branch of Company B. The amount that can be offset with Company B is determined to be "30,000", and the remaining "20,000" is deposited. In addition, in the offsetting process, since it is necessary to perform offsetting process on the balance of accounts receivable and accounts payable generated by the invoice recipient and payee, it is necessary to perform the process at the invoice recipient and payee level, not on a corporate basis. Therefore, "20,000" generated by the invoice recipient's Fukuoka branch of Company B is offset with "10,000" generated by the payee's Fukuoka branch of Company B and "10,000" generated by the Kyoto branch of Company B. Additionally, in the case of the Steel Business Division of Company C, which manages accounts receivable and payable by division, the "20,000" incurred by the invoice recipient, Steel Business G of Company C, can only be offset against the "10,000" incurred by Steel Business G of Company C. As a result, the amount that can be offset by Steel Business G of Company C is determined to be "10,000," and the net amount of "10,000" is deposited.

In addition, on the batch offset processing screen, by selecting the Select All button BT3, all of the check boxes CB1 to CB12 can be selected. Similarly, by selecting the Cancel All button BT4, all of the check boxes CB1 to CB12 can be deselected. By selecting the Display button BT5, the batch offset processing screen can be updated and displayed according to the selection status of the check boxes. By selecting the Register button BT6, the batch offset processing unit 102g performs the batch offset processing, and the deposit data 106g to the payment reconciliation detail data 106n are created according to the selection status of the check boxes CB1 to CB12, and the collection schedule data 106e and payment schedule data 106f are updated. The batch offset processing screen can be closed by selecting the Close button BT7.

[S9: Create deposit data]
The lump-sum offset processing unit 102g creates deposit data 106g. The deposit data 106g includes the deposit number, deposit billing destination code, deposit billing destination name, deposit date, deposit amount, deposited amount cleared, and deposit clearing completion category (see FIG. 17). 0: incomplete or 1: complete is entered in the deposit clearing completion category. For Company A, the billing destinations are consolidated, so they are tallied into one statement. For Companies B and C, the billing destinations are not consolidated, so multiple statements are created.

[S10: Create deposit details data]
The lump-sum offset processing unit 102g creates the payment details data 106h. The payment details data 106h includes the payment number, payment details line number, payment classification, payment amount, and offset payment number (see FIG. 18). The payment classification is input as one of 1: cash, 2: check, 3: transfer, 4: bill receivable, 5: accounts payable offset, 6: cash due, or 9: other.

[S11: Create payment data]
The lump-sum offset processing unit 102g creates payment data 106i. The payment data 106i includes the payment number, withdrawal payee code, withdrawal payee name, payment date, payment amount, payment cleared amount, payment clearing completion category, deposit number, and deposit statement line number (see FIG. 19). The payment clearing completion category is entered as 0: incomplete or 1: complete. For company A, the withdrawal payees are consolidated, so they are tallied into one statement. For companies B and C, the withdrawal payees are not consolidated, so multiple statements are created.

[S12: Create payment details data]
The lump-sum offset processing unit 102g creates payment details data 106j. The payment details data 106j includes the payment number, the payment details line number, the payment category, and the payment amount (see FIG. 20). The payment category is input as one of the following: 1: cash, 2: check, 3: transfer, 4: bill payable, 5: accounts receivable offset, 6: cash due, or 9: other.

[S13: Create payment reconciliation data]
The lump-sum offset processing unit 102g creates the payment reconciliation data 106k. The payment reconciliation data 106k includes a payment reconciliation number, a payment invoice destination code, a payment invoice destination name, and a payment reconciliation date (see FIG. 21).

[S14: Create payment reconciliation detail data]
The lump-sum offset processing unit 102g creates the payment reconciliation detail data 106l. The payment reconciliation detail data 106l includes the payment reconciliation number, the payment reconciliation detail number, the payment number, the collection schedule number, the collection schedule detail line number, and the payment reconciled amount (see FIG. 22).

[S15: Update collection schedule data]
The lump-sum offset processing unit 102g updates the scheduled collection data 106e. If the scheduled collection amount is equal to the settled payment amount, the payment settlement completion classification is updated from 0: incomplete to 1: complete (see FIG. 23). The data are sorted by the oldest scheduled collection date and oldest posting date, and the oldest vouchers are settled in order of line number.

[S16: Create payment settlement data]
The lump-sum offset processing unit 102g creates payment reconciliation data 106m. The payment reconciliation data 106m includes a payment reconciliation number, a withdrawal payee code, a withdrawal payee name, and a payment reconciliation date (see FIG. 24).

[S17: Create payment reconciliation detail data]
The lump-sum offset processing unit 102g creates payment reconciliation detail data 106n. The payment reconciliation detail data 106n includes a payment reconciliation number, a payment reconciliation detail number, a payment number, a payment schedule number, a payment schedule detail line number, and a payment reconciled amount (see FIG. 25).

[S18: Update payment schedule data]
The lump-sum offset processing unit 102g updates the payment schedule data 106f. If the payment schedule amount and the payment cleared amount are equal, the payment clearing completion classification is updated from 0: incomplete to 1: complete (see FIG. 26). The data are sorted in order of the oldest scheduled payment date and oldest posting date, and the oldest vouchers are cleared in order of row number.

As described above, according to this embodiment, the offset processing target selection unit 102f displays the collection schedule information and payment schedule information on the screen by company as candidates for offset processing targets for receivables and payables, so the operator can check the candidates for offset processing targets in a list. Furthermore, the bulk offset processing unit 102g creates deposit management data, payment management data, deposit reconciliation management data, and payment reconciliation management data based on the information selected by the offset processing target selection unit 102f, updates the collection schedule data 106e based on the deposit reconciliation management data, and updates the payment schedule data 106f based on the payment reconciliation management data, thereby performing offset processing in a lump sum. As a result, the burden on the operator who manages receivables and payables within the company can be reduced.

3. 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.

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 a known method.

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.

In addition, with regard to the receivables/payables management device 100, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the receivables/payables 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 on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the receivables/payables management device 100 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

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

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

A "program" is a data processing method written in any language or description method, and may be in any format, 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 consisting of multiple modules or libraries, and a program that works in conjunction 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, can use well-known configurations and procedures.

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

The receivables/payables 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 receivables/payables management device 100 may be realized by implementing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on 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.

The present invention is useful, for example, in managing receivables and payables within a company.

100 Credit and Debt Management Device 102 Control Unit
102a Business establishment master creation unit
102b Customer integrated master creation unit
102c Bill payment schedule input section
102d Expense payment schedule input section
102e Offset Schedule Creation Department
102f offset processing target selection unit
102g: collective offset processing unit 104: communication interface unit 106: storage unit
106a Business establishment master
106b Corporate master
106c Billing destination master
106d Payment destination master
106e Data to be collected
106f Payment schedule data
106g Deposit data
106h Deposit details data
106i Payment Data
106j Payment details data
106k Payment reconciliation data
106l Payment reconciliation details data
106m Payment settlement data
106n Payment settlement detail data 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (6)

A credit and payable management device including a control unit,
a billing destination master for managing billing destinations on an organizational basis within a company, in which payment identification information for identifying whether payments are made collectively on an organizational basis within the company is set in association with the billing destination; a payee master for managing payees on an organizational basis within the company, in which payment identification information for identifying whether payments are made collectively on an organizational basis within the company is set in association with the payee; access to scheduled collection data including scheduled collection information including the scheduled collection amount and the billing destination; and scheduled payment data including scheduled payment information including the scheduled payment amount and the payee;
The control unit is
an offset processing target selection means for extracting, from said collection schedule data and said payment schedule data, collection schedule information and payment schedule information for which the billing destination and payment destination are the same intra-company organization, displaying the extracted collection schedule information and payment schedule information on a screen by company as candidates for offset processing targets for credits and payables, and allowing the user to select, on said screen, the collection schedule information and payment schedule information to be subjected to offset processing;
a means for calculating a total of the amounts to be collected and the total of the amounts to be paid for each company based on the collection schedule information and payment schedule information selected by the offset processing target selection means, comparing the two calculated totals for each company, and displaying the smaller amount on the screen for each company as an offsettable amount;
an input means for receiving input of the deposit identification information and the payment identification information;
To have
A receivables/payables management device comprising: The control unit is
an offset schedule creation means for extracting, from the collection schedule data and the payment schedule data, collection schedule information and payment schedule information in which the billing destination and the payment destination are the same intra-company organization, and creating an offset schedule in which the extracted collection schedule information and payment schedule information are displayed by company as candidates for offset processing of credits and debts;
2. The credit and debt management device according to claim 1, The offset processing target selection means
Displaying on the screen as candidates for offsetting of claims and payables those whose total amount to be collected per company is equal to or greater than the total amount to be paid;
3. The credit and payable management device according to claim 1 or 2 , The offset processing target selection means
Displaying on the screen, as candidates for offsetting of claims and payables, those for which the total of the amount to be collected per company is smaller than the total of the amount to be paid;
4. The credit and debt management device according to claim 1, A business support program to be executed by a control unit of a credit/debt management device having a control unit,
The credit and payable management device is capable of accessing a billing destination master for managing billing destinations on an intra-company organizational basis, in which payment identification information for identifying whether payments are made collectively on an intra-company organizational basis or individually on an intra-company organizational basis is set in association with the billing destination, a payee master for managing payees on an intra-company organizational basis, in which payment identification information for identifying whether payments are made collectively on an intra-company basis or individually on an intra-company organizational basis is set in association with the payee, collection schedule data including collection schedule information including a scheduled collection amount and the billing destination, and payment schedule data including payment schedule information including a scheduled payment amount and the payee,
To cause the control unit to execute
an offset processing target selection step of extracting, from the collection schedule data and the payment schedule data, collection schedule information and payment schedule information for which the billing destination and the payment destination are the same intra-company organization, displaying the extracted collection schedule information and payment schedule information on a screen by company as candidates for offset processing targets for credits and payables, and allowing the user to select, on the screen, the collection schedule information and payment schedule information to be subjected to offset processing;
A step of calculating the total of the amount to be collected and the total of the amount to be paid for each company based on the collection schedule information and payment schedule information selected in the offset processing target selection step, comparing the two calculated totals for each company, and displaying the smaller amount on the screen for each company as the offsettable amount;
an input step of receiving input of the deposit identification information and the payment identification information;
Business support programs including: A business support method executed by a control unit of a credit/debt management device including a control unit,
The credit and payable management device is capable of accessing a billing destination master for managing billing destinations on an intra-company organizational basis, in which payment identification information for identifying whether payments are made collectively on an intra-company organizational basis or individually on an intra-company organizational basis is set in association with the billing destination, a payee master for managing payees on an intra-company organizational basis, in which payment identification information for identifying whether payments are made collectively on an intra-company basis or individually on an intra-company organizational basis is set in association with the payee, collection schedule data including collection schedule information including a scheduled collection amount and the billing destination, and payment schedule data including payment schedule information including a scheduled payment amount and the payee,
The control unit executes:
an offset processing target selection step of extracting, from the collection schedule data and the payment schedule data, collection schedule information and payment schedule information for which the billing destination and the payment destination are the same intra-company organization, displaying the extracted collection schedule information and payment schedule information on a screen by company as candidates for offset processing targets for credits and payables, and allowing the user to select, on the screen, the collection schedule information and payment schedule information to be subjected to offset processing;
A step of calculating the total of the amount to be collected and the total of the amount to be paid for each company based on the collection schedule information and payment schedule information selected in the offset processing target selection step, comparing the two calculated totals for each company, and displaying the smaller amount on the screen for each company as the offsettable amount;
an input step of receiving input of the deposit identification information and the payment identification information;
A method of supporting business operations, including:

Images