JP2018028843A - Debt and credit management device, debt and credit management method, and debt and credit management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a debt and credit management device which reduces a work cost or a work error by automation of a debt and credit management work including offset with a client company from issuance of a debit note and a credit note, and can achieve settlement in an early stage by compression of a work time.SOLUTION: A debt and credit management device 100 includes a control section 102, where the control section 102 includes a debt counting section 102a which counts a debt occurring with a client company, a credit counting section 102b which counts a credit occurring with the client company, and a debit credit input section 102c which inputs an amount of charge as the debt occurring with the client company for a period of time and an amount of payment as the credit, and issues a difference between the amounts as a debit note or a credit note from the total balance of the debt and credit for a period of time, and the device performs settlement on the basis of the debit note or credit note issued by the debit credit input section 102c.SELECTED DRAWING: Figure 1

Description

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

  Patent Document 1 provides a bill-like settlement method that assumes that the seller can be cashed while maintaining the merit of bill settlement for the buyer in the transaction between the seller and the buyer, Also disclosed is a settlement apparatus and method that enables a seller to reflect the credit risk of the buyer in the sale price of the product in the transaction with the buyer.

JP 2002-189862 A

  However, in Patent Document 1, management of debit notes and credit notes is performed between document outputs, but at the time of settlement processing, offsetting is applied again in the same way as normal receivables and debts. For this reason, there is a problem that total debit credit cannot be managed on the system until offset settlement.

  The present invention has been made in view of the above-mentioned problems, and reduces work costs and work mistakes by automating from debt issuance and credit note issuance to debt management work including offsetting with business partners. It is an object of the present invention to provide a claims and debt management apparatus, a claims and debt management method, and a claims and debt management program capable of realizing early settlement of accounts by reducing work time.

  In order to solve the above-mentioned problems and achieve the object, the claim management apparatus according to the present invention is a claim management apparatus provided with a control unit. A claim recording means for recording, a debt recording means for recording a debt generated with the business partner, and a claim amount and a payment amount as the debt generated in a predetermined period with the business partner And a debit credit input means for issuing the difference as a debit note or credit note from the total balance of claims and debts in a predetermined period, based on the debit note or credit note issued by the debit credit input means It is characterized by making a settlement.

  Further, in the claim management apparatus according to the present invention, the debit credit input means assigns a management number for associating data to be offset against the claim when the claim and the debt are input, and the control unit Is characterized by further comprising offset input means for designating the management number to extract input data of receivables and payables to be offset, and for performing an automatic application process between the extracted input data.

  Further, in the claim management apparatus according to the present invention, the management number is a debit credit NO when the credit / debt unit to be offset is a debit credit unit, a slip NO when the unit is a slip, When it is set as a unit, it is set as specification NO.

  In addition, the claim management method according to the present invention is a claim management method executed by a claim management apparatus provided with a control unit, which is executed by the control unit and is generated with a business partner. A debt recording step for recording a debt, a debt recording step for recording a debt generated with the business partner, and a claim amount and a payment as the debt generated in a predetermined period with the business partner. A debit credit input step of inputting the amount and issuing the difference amount as a debit note or credit note from the total balance of receivables and payables in a predetermined period, and the debit note or credit note issued by the debit credit input step It is characterized in that payment is made based on this.

  The debt management program according to the present invention is a credit management program for execution in a credit management device provided with a control unit, and is generated with a business partner for execution in the control unit. A claim recording step for recording a claim, a debt recording step for recording a debt generated with the business partner, a billing amount as the credit generated during a predetermined period with the business partner, and the debt A debit credit input step of inputting a payment amount and issuing a difference amount as a debit note or credit note from a total balance of receivables and payables in a predetermined period, and the debit note or credit note issued by the debit credit input step The payment is made based on the above.

  According to the present invention, by automating the work from the issuance of debit notes and credit notes to the receivables and payable management work including offsetting with business partners, work costs and work mistakes are reduced, and work time is shortened to achieve early settlement of accounts. There is an effect that can be realized.

FIG. 1 is a block diagram illustrating an example of a configuration of a claim and liability management apparatus. FIG. 2 is a flowchart showing an example of processing of the claim management apparatus. FIG. 3 is a diagram showing an example of the debit credit input screen in the present embodiment. FIG. 4 is a diagram illustrating an example of a cancellation input screen in units of management NO in the present embodiment. FIG. 5 is a diagram showing an example of a B / L D / O unit cancellation input screen in the present embodiment. FIG. 6 is a diagram illustrating an example of a detail unit offset input screen according to the present embodiment. FIG. 7 is a diagram illustrating an example of a flow up to a settlement process with an overseas agent in a use transportation company. FIG. 8 is a diagram illustrating an example of accounting for an export project charge and an import project payment. FIG. 9 is a diagram illustrating an example of the month-end closing process in the comparative example. FIG. 10 is a diagram illustrating an example of the month-end closing process in the present embodiment. FIG. 11 is a diagram illustrating an example of a settlement process in the present embodiment. FIG. 12 is a diagram illustrating an example of the canceling process in the comparative example. FIG. 13 is a diagram illustrating an example of the cancellation process in the present embodiment.

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

[1. Overview]
In the NVOCC industry at the port (the freight-use transportation industry that does not have international transportation means such as ships in its own company), settlement processing is performed in units of debit credits. In the conventional system, since the debit note and the credit note issuance to the erasure work are manually created using Excel (registered trademark) or the like, the higher the number of cases, the Excel (registered trademark) There were omissions in the extraction of the target data until posting to the site, and there was a mistake in posting, resulting in a high cost of office work that was not cost-effective.

  Therefore, in the present embodiment, in monthly offset settlement (netting) with an overseas agent, the balance between the current month billing and the payment fee is taken into consideration, and the difference is issued as a debit note or a credit note. As a result, even if the transaction volume for the current month is large, it is possible to greatly reduce the work cost of issuing each form by summing up the sales details and purchase details.

  In addition, when settlement is performed based on the debit note or credit note issued as in the present embodiment, the debit note or credit is not applied to the individual sales details or purchase details. As a premise for issuing notes, when entering receivables and payables, management numbers (for example, debit credit NO, slip NO, detail NO, etc.) that link sales details and purchase details are assigned and managed. By specifying a number, it is possible to automatically delete. As a result, by automating the consumption work that tends to be concentrated at the end of the month, work errors can be reduced and the work time can be reduced, so that early monthly settlement can be realized.

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

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

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

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

  The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores a computer program for giving various instructions to a CPU (Central Processing Unit) in cooperation with an OS (Operating System). As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) and a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, and an optical disk can be used. Here, the storage unit 106 includes a deposit schedule data storage unit 106a, a payment request data storage unit 106b, a cancellation data storage unit 106c, a cancellation claim data storage unit 106d, a cancellation subtraction data storage unit 106e, and the like.

  The payment schedule data storage unit 106a records the credits generated with the business partners and stores them as payment schedule data such as sales details.

  The payment request data storage unit 106b records the debt generated with the business partner and stores it as payment request data such as purchase details.

  Since the offset data storage unit 106c only deals with suppliers that are subject to offset when performing deposit processing or payment processing in accordance with the issued debit note or credit note, data on sales details and purchase details of suppliers Is assigned to the deposit schedule data storage unit 106a and the payment request data storage unit 106b on the basis of the management number such as debit credit NO, and the data to be offset is stored.

  The counter claim data storage unit 106d deposits the sales details and purchase details of the business partner based on the management number such as the debit credit NO when performing the payment process or the payment process according to the issued debit note or credit note. The allocation process is performed for the schedule data storage unit 106a and the payment request data storage unit 106b, and the billing data that has not been offset is stored.

  The offset subtraction data storage unit 106e, when performing deposit processing or payment processing according to the issued debit note or credit note, stores the sales details and purchase details of the business partner based on the management number such as debit credit NO. The allocation process is performed on the deposit schedule data storage unit 106a and the payment request data storage unit 106b, and subsidence data to be paid to the subcontractor is stored regardless of whether or not it is an offset target.

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

  The control unit 102 is a CPU or the like that comprehensively controls the claim and liability management apparatus 100. The control unit 102 has an internal memory for storing a control program such as an OS, a program that defines various processing procedures, and necessary data, and performs various information processing based on these stored programs. Run. Here, the control unit 102 includes a debt recording unit 102a, a debt recording unit 102b, a debit credit input unit 102c, an offset input unit 102d, and the like in terms of functional concept.

  The receivable counting unit 102a records receivables generated with the business partner, and stores payment schedule data such as sales details in the payment schedule data storage unit 106a.

  The debt accounting unit 102b records the debt generated with the business partner, and stores payment request data such as payment details in the payment request data storage unit 106b.

  When the debit credit input unit 102c inputs a receivable and a debt generated with a business partner for a predetermined period, the debit credit input unit 102c balances the receivable and payable, and a debit note or a credit note is issued based on the difference, thereby making a settlement I do. In addition, the debit credit input unit 102c may assign a management number for associating data subject to offsetting of claims and debts when inputting claims and debts generated during a predetermined period with a business partner. This control number is a number for extracting the details to be covered when the claims and debts are cleared. For example, the debit credit NO assigned to the claims and debts generated in the predetermined period with the same business partner, For slip slips that are numbered for receivables and payables with the same business partner for each transaction day, or for details that are numbered for receivables and payables that are generated for each business transaction with the same business partner There may be.

  The offset input unit 102d inputs the management number assigned to the receivables and payables to be offset, thereby extracting the input data of the receivables and payables to be offset, and performs automatic offset processing between the extracted input data. . The canceled sales details and payment details are stored in the offset data storage unit 106c. The billing data remaining without being offset is stored in the offset billing data storage unit 106d. Regardless of whether or not it is a cancellation target, the subtraction data to be paid to the subcontractor is stored in the offset subtraction data storage unit 106e.

[3. Concrete example]
A specific example of the present embodiment will be described with reference to FIGS. 2 to 13 as an example of processing performed by the claim management apparatus according to the present embodiment. FIG. 2 is a flowchart showing an example of processing of the claim and liability management apparatus 100. FIG. 3 is a diagram showing an example of the debit credit input screen in the present embodiment. FIG. 4 is a diagram illustrating an example of a cancellation input screen in units of management NO in the present embodiment. FIG. 5 is a diagram showing an example of a B / L D / O unit cancellation input screen in the present embodiment. FIG. 6 is a diagram illustrating an example of a detail unit offset input screen according to the present embodiment.

  First, as shown in FIG. 2, the claim counting unit 102a counts each claim generated with the overseas business partner (step SA-1) and stores it in the deposit schedule data storage unit 106a. Further, the debt counting unit 102b counts each debt generated with the overseas business partner (step SA-2) and stores it in the payment request data storage unit 106b.

  Then, the debit credit input unit 102c reads out the input data of each receivable and payable generated during the predetermined period with the same business partner from the deposit schedule data storage unit 106a and the payment request data storage unit 106b, and inputs the data. For example, when performing monthly settlement, if you specify the recording month for settlement in the “Recording Month” field on the debit credit entry screen shown in FIG. The data is listed in the lower column of FIG. The debit credit input unit 102c balances the receivables and payables in the recording month, and issues a debit note or a credit note according to the difference (step SA-3).

For example, in the journal entry example of credit recording shown in step SA-1 of FIG.
Accounts receivable denominated in foreign currencies / Agency commission income ($ 200)
When the agency fee income is corrected in the example of journal entry for debt recording in step SA-2,
Agency fee / Accounts payable in foreign currency ($ 90)
Thus, a debit note of $ 200- $ 90 = $ 110 is issued by taking the balance of the agency fee and debt.

  In addition, the debit credit input unit 102c assigns a management number for associating data for offsetting receivables and payables to the detailed data of each receivable and payable displayed on the debit credit input screen shown in FIG. May be. For example, when the unit of receivables and payables to be offset is a debit credit unit, the debit credit NO may be assigned as a management number. Further, in the case where the unit of receivables and payables to be offset is a slip unit, the slip number may be assigned as a management number. Further, when the unit of receivables and payables to be offset is a detail unit, the detail number may be assigned as a management number. In addition, the management number may be assigned in units of a bill of lading (B / L) or in a cargo delivery form (D / O).

  Here, a description will be given below using an example in which a debit credit NO (hereinafter, DCNO) is assigned as a management number.

As shown in FIG. 2, the overseas business partner pays in accordance with the debit note issued by the agency. An example of the journal entry at this time is that the deposit rate is (JPY 108.40 / USD).
<Foreign currency>
Deposit ($ 110) / Accounts receivable in foreign currency ($ 200)
Accounts payable in foreign currencies ($ 90) /
<Japanese currency>
Deposit (¥ 11,924) / Accounts receivable in foreign currency (¥ 22,110)
Accounts payable in foreign currency (¥ 10,368) / Foreign exchange gain (¥ 182)
It becomes.

  As described above, according to the claim management apparatus 100 according to the present embodiment, even if a plurality of claims and debts are generated with the same business partner, the debit credit input unit 102c cancels the selling and buying amounts. Therefore, it is only necessary to take a total balance of claims and debts and charge the difference as a debit note or a credit note. Therefore, it is possible to reduce the work cost of totaling each sales details and purchase details and issuing a form.

  Furthermore, the debit / credit input unit 102c of the claim management apparatus 100 according to the present embodiment links each sales / purchase statement with the debit / credit note when the settlement is performed using the issued debit note or credit note. DCNO is assigned as a management number to be assigned. As shown in FIG. 3, DCNO numbering is performed by specifying "auto numbering" on the debit credit input screen, as well as performing numbering while DCNO is sequentially updated, and manually copying DCNO input last time. Numbering may be performed while updating.

  The overseas business partner according to the present embodiment can make a payment by collectively performing deposit / payment processing according to the issued debit note or credit note.

  Further, when registering the deposit / withdrawal information, the offset input unit 102d reads the credit / debt data for only the transaction to be offset using DCNO and performs the allocation process. Whether to cancel or not is controlled by providing a classification in the supplier master. For example, when DCNO is designated as the management NO unit on the offset input screen shown in FIG. 4, the offset input unit 102d receives the detailed data of the receivables and debts to which the DCNO is assigned as the deposit schedule data storage unit 106a and the payment request data storage unit. The data is read from 106b, and the erase process is performed. The cancellation target data subjected to the cancellation process is registered in the cancellation data storage unit 106c. Further, the billing data that has not been subject to cancellation is registered in the cancellation request data storage unit 106d. Further, data to be paid to the subcontractor regardless of whether or not it is a cancellation target is registered in the offset subtraction data storage unit 106e (step SA-4).

  Further, when registering the deposit / withdrawal information, the cancellation input unit 102d uses the B / L (Bill of Lading) D / O (Cargo Delivery Form) NO as the cancellation target as shown in the cancellation input screen of FIG. It is also possible to read the receivables and payables data for only the transaction and perform the allocation process.

  Further, when registering the deposit / withdrawal information, the offset input unit 102d reads the credit / debt data for only the transaction to be offset using the detailed NO as shown in the offset input screen of FIG. An allocation process may be performed.

(Specific example showing difference in processing between this embodiment and comparative example)
FIG. 7 is a diagram illustrating an example of a flow up to a settlement process with an overseas agent in a use transportation company. FIG. 8 is a diagram illustrating an example of accounting for an export project charge and an import project payment. FIG. 9 is a diagram illustrating an example of the month-end closing process in the comparative example. FIG. 10 is a diagram illustrating an example of the month-end closing process in the present embodiment. FIG. 11 is a diagram illustrating an example of a settlement process in the present embodiment. FIG. 12 is a diagram illustrating an example of the canceling process in the comparative example. FIG. 13 is a diagram illustrating an example of the cancellation process in the present embodiment.

  For example, when import / export processing is continuously performed between domestic NVOCC (use transportation company) and overseas agent (Company A) using maritime transportation means, as shown in FIG. In this case, the domestic (NVOCC) company charges the overseas agency (Company A), and the overseas agency (Company A) pays the domestic (NVOCC) company. Moreover, as shown in FIG. 7, in the import project, the overseas agent (Company A) charges the domestic (NVOCC) supplier, and the domestic (NVOCC) supplier pays the overseas agent (Company A). . In these import / export projects, the sea fare is postpaid.

  Here, a domestic (NVOCC) contractor, when three import / export transactions with an overseas agent (Company A) occur in February and March, respectively, the debt recording section 102a and the debt recording section 102b As a result, an export project charge and an import project payment as shown in FIG. 8 are recorded.

  First, in the comparative example, when closing in February, as shown in FIG. 9, from the various recording data shown in FIG. 8, an invoice with a recording date of February (recording NO is S001 to S003) and a payment notice ( The accounting NO is C001 to C003), and each slip is issued manually. For this reason, it takes time for paperwork for issuing a slip, and two charges for billing and payment are required.

  On the other hand, in the present embodiment, when the February tightening is performed, the DCNO (here, DC001) assigned at the time of debit credit input is designated by the debit credit input unit 102c, and the relationship as shown in FIG. Data can be extracted automatically. In the detailed data of the same DCNO extracted in FIG. 10, only the recording month of February is extracted, the total billing amount of the billing item is 600 ($), and the total cost amount of the payment item is 450 ($). Therefore, 150 ($) of the difference is calculated from the total balance of receivables and payables and is issued as a debit note or a credit note. Here, since {billing amount> cost amount}, it is issued as a debit note.

  As a result, as shown in FIG. 11, according to the settlement site of the business partner, the settlement is completed simply by depositing the debit note of 150 ($) on the settlement day of March 31, so that the paperwork related to the settlement is completed. And a one-time fee.

  Subsequently, in the case of performing the processing for receivables and payables, in the comparative example, from the receivable slip and the debt slip shown in FIG. That is, because the credit slip recording NO is S001 to S003, the debt slip recording NO is C001 to C003 is “target”, and the other is “non-target”, and the manual clearing process is performed. There was an accounting workload.

  On the other hand, in the present embodiment, when the receivable / accounting process is performed, a debiting process is already applied when the debit credit is input in advance (see step SA-3). It is possible to automate the current consumption process simply by specifying the DCNO number assigned in step (b).

  For example, in the offset processing in the slip unit shown in FIG. 13, if DCNO is designated and the recording date is February 29, a revocation result of debit note issue of 150 ($) is obtained.

  In addition, in the offset process in detail units shown in FIG. 13, when DCNO is designated, the claim details and the debt details that are to be offset this time are automatically selected, and the details can be automatically cleared.

  According to the above embodiment, not only debit note and credit note form output but also linkage of receivables and debts specified for form output (debit) in the offshore settlement process of receivables and debts with overseas agents specific to the port industry. In addition to agent (AGENT) units, master (MASTER) units, and house (HOUSE) units, debit credit offset settlement can be performed by drilling down to detailed units. . As a result, the debit credit NO is designated, the form is printed, and the offset settlement in units of the debit credit NO can be totally managed by the system.

  In the above-described embodiment, the port business and the use transportation business have been described as examples. However, the present invention is not necessarily limited thereto, and the same logic is used even in the settlement business in the agency transaction business, for example. Can be implemented.

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

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

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

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

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

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

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

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

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

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

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

  The present invention is particularly useful for a settlement operation in a port business, a use transportation business, or an agency transaction business.

DESCRIPTION OF SYMBOLS 100 Claim and debt management apparatus 102 Control part 102a Claim recording part 102b Debt recording part 102c Debit credit input part 102d Offset input part 104 Communication interface part 106 Storage part 106a Deposit scheduled data storage part 106b Payment request data storage part 106c Offset data storage part 106d Cancellation claim data storage unit 106e Cancellation subtraction data storage unit 108 Input / output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (5)

In receivables and payable management equipment equipped with a control unit
The controller is
Receivables recording means for recording receivables with business partners;
Debt recording means for recording debt generated with the business partner,
Enter the amount billed as the receivable and the amount paid as the debt generated in a predetermined period with the business partner, and issue the difference as a debit note or credit note from the total balance of the debt and debt in the predetermined period Debit credit input means;
With
Claims and debt management apparatus for performing settlement based on a debit note or a credit note issued by the debit credit input means. The debit credit input means is:
At the time of entering the claim and the debt, a management number is assigned to link the offsetting data of the claim and debt,
The controller is
An offset input means for extracting the input data of the receivables and payables to be offset by designating the management number, and performing an automatic application process between the extracted input data;
The claim management apparatus according to claim 1, further comprising: The management number is
3. The credit / debt unit to be offset is debit credit NO when debit credit unit, slip NO when slip unit, and detail NO when detail unit is used. Debt management device described in 1. A claim management method executed by a claim management apparatus equipped with a control unit,
Executed by the control unit,
Receivables recording step to record receivables with business partners;
Debt recording step of recording debt generated with the business partner,
Enter the amount billed as the receivable and the amount paid as the debt generated in a predetermined period with the business partner, and issue the difference as a debit note or credit note from the total balance of the debt and debt in the predetermined period Debit credit input step;
Including
Claims and debt management method, wherein settlement is performed based on the debit note or credit note issued in the debit credit input step. A claim management program for execution on a claim management apparatus equipped with a control unit,
In order to be executed in the control unit,
Receivables recording step to record receivables with business partners;
Debt recording step of recording debt generated with the business partner,
Enter the amount billed as the receivable and the amount paid as the debt generated in a predetermined period with the business partner, and issue the difference as a debit note or credit note from the total balance of the debt and debt in the predetermined period Debit credit input step;
Including
Claims and debt management program, wherein settlement is performed based on the debit note or credit note issued in the debit credit input step.

Images