JP2021157790A - Journaling creation device, journaling creation method, and journaling creation program - Google Patents

Abstract

To enable department management on journaling on the basis of bill information occurring during paying-in and bill information occurring during paying-out.SOLUTION: A journaling creation device recognizes that business office and a department related to the occurrence of a credit, a business office and a department related to the occurrence of deposit and deposit application, and each amount in each record belong to a bill receivable received by the department on the basis of a deposit detail record with a bill set as a denomination and a deposit header record linked to the record, a deposit application header record linked to the deposit detail record or a deposit slip No. in the deposit header record, and a collection schedule record linked to a deposit application detail record linked to the record and a collection schedule Guid in the deposit application detail record; and creates two pieces of journaling data in which debit and credit related to department transfer of the bill receivable are mutually reversed, a date of drawing is stored as an occurrence date in one journaling data, and a due data is stored as an occurrence date in the other journaling data.SELECTED DRAWING: Figure 13

Description

The present invention relates to a journal creation device, a journal creation method, and a journal creation program.

In the prior art, in order to realize the department management of bills, it was necessary to separately manage slips for each department even in the case of bills with the same face.

In addition, Patent Document 1 describes an electronically recorded claim receiving device for supporting the clearing process of claims and debts related to electronically recorded claims in an accounting system.

Japanese Patent No. 4550156

However, there is a problem that the registration work and the bill management work become complicated in proportion to the number of generated departments.

The present invention has been made in view of the above circumstances, and based on the bill information generated at the time of deposit and the bill information generated at the time of payment, it is possible to create a journal that enables department management (division of bills) on the journal. It is an object of the present invention to provide an apparatus, a journal creation method, and a journal creation program.

In order to solve the above-mentioned problems and achieve the object, the journal creation device according to the present invention is a journal creation device including a control unit, and manages a collection schedule number, a business establishment, a department, and a collection schedule amount. A collection schedule data table, a payment data table that manages the payment number, business establishment, department, denomination, and payment amount, and a payment application number, payment number, business establishment, department, collection schedule number, and payment application amount. Payment application data table that manages payment application data table, payment schedule data table that manages payment schedule number, business establishment, department, payment schedule amount, and payment data that manages payment number, business establishment, department, denomination, and payment amount You can access the table and the payment application data table that manages the payment application number, payment number, place of business, department, payment schedule number, and payment application amount. Based on the payment record for which the bill is set as, the payment application record linked to the payment record, and the collection schedule record linked to the payment application record, the establishment and department related to the generation of the claim, the payment and Recognizing that the establishment and department related to the occurrence of the payment application and each amount in each record are for the bills receivable received by the department, the two journals related to the department transfer of the bills receivable. Processing to create data in which the balance is reversed and one journal data has the issue date as the occurrence date and the other journal data has the due date as the occurrence date, and 2) denomination Based on the payment record for which the bill is set as, the payment application record associated with the payment record, and the payment schedule record associated with the payment application record, the establishment and department related to the occurrence of the debt, and the payment Recognizing that the place of business and department related to the occurrence of payment application and each amount in each record is for the bill payable drawn by the department, two journals related to the department transfer of the bill payable Create a process that creates data in which the balance is reversed and one journal data has the issue date as the occurrence date and the other journal data has the due date as the occurrence date. It is characterized by having means.

In addition, the journal creation method according to the present invention manages a collection schedule data table that manages a collection schedule number, a business establishment, a department, and a collection schedule amount, and a payment number, a business establishment, a department, a denomination, and a payment amount. The payment data table, the payment application number, the payment number, the place of business, the department, the collection schedule number, and the payment application data table that manages the payment application amount, and the payment schedule number, the place of business, the department, and the payment schedule amount. A payment schedule data table to manage, a payment data table to manage payment numbers, establishments, departments, denominations, and payment amounts, and payment application numbers, payment numbers, establishments, departments, payment schedule numbers, and payment cancellations. The payment application data table that manages the payment amount and the control unit of the information processing device that has a control unit that can access the payment application are linked to 1) the payment record for which the bill is set as the denomination, and the payment record. Based on the payment application record and the collection schedule record associated with the payment application record, the business establishments and departments related to the occurrence of receivables, the business establishments and departments related to the occurrence of payment and payment application, and each Recognizing that each amount in the record is for the bills receivable received by the department, the two journal data related to the department transfer of the bills receivable are reversing the balance and one of the journal data. Is the process of creating a journal data that has the issue date as the date of occurrence and the due date is stored as the date of occurrence, and 2) the payment record for which the bill is set as the denomination, and is linked to the payment record. Based on the payment application record and the payment schedule record associated with the payment application record, the establishment and department related to the occurrence of debt, the establishment and department related to the occurrence of payment and payment application, and each Recognizing that each amount in the record is for a bill payable drawn by the department, it is two journal data related to the department transfer of the bill payable, and the balance is reversed and one of the journal data Is characterized in that a process of creating a journal data having an issue date as an occurrence date and a due date stored as an occurrence date in the other journal data and a creation step including the occurrence date are executed.

In addition, the journal creation program according to the present invention manages a collection schedule data table that manages a collection schedule number, a business establishment, a department, and a collection schedule amount, and a payment number, a business establishment, a department, a denomination, and a payment amount. The payment data table, the payment application number, the payment number, the place of business, the department, the collection schedule number, and the payment application data table that manages the payment application amount, and the payment schedule number, the place of business, the department, and the payment schedule amount. A payment schedule data table to manage, a payment data table to manage payment numbers, establishments, departments, denominations, and payment amounts, and payment application numbers, payment numbers, establishments, departments, payment schedule numbers, and payment cancellations. The payment application data table that manages the payment amount and the control unit of the information processing device that has a control unit that can access the payment application unit are linked to 1) the payment record for which the bill is set as the denomination, and the payment record. Based on the payment application record and the collection schedule record associated with the payment application record, the business establishments and departments related to the occurrence of receivables, the business establishments and departments related to the occurrence of payment and payment application, and each Recognizing that each amount in the record is for the bills receivable received by the department, the two journal data related to the department transfer of the bills receivable are reversing the balance and one of the journal data. Is the process of creating a journal data that has the issue date as the date of occurrence and the due date is stored as the date of occurrence, and 2) the payment record for which the bill is set as the denomination, and is linked to the payment record. Based on the payment application record and the payment schedule record associated with the payment application record, the establishment and department related to the occurrence of debt, the establishment and department related to the occurrence of payment and payment application, and each Recognizing that each amount in the record is for a bill payable drawn by the department, it is two journal data related to the department transfer of the bill payable, and the balance is reversed and one of the journal data Is a journal creation program for creating a process in which the issue date is stored as the occurrence date and the due date is stored in the other journal data as the occurrence date, and as a creation means for executing.

According to the present invention, it is possible to manage departments (division of bills) on journals based on the bill information generated at the time of deposit and the bill information generated at the time of payment.

FIG. 1 is a block diagram showing an example of the configuration of the journal creation device 100. FIG. 2 is a diagram showing an example of data to be collected 106a. FIG. 3 is a diagram showing an example of deposit header data 106b. FIG. 4 is a diagram showing an example of payment detailed data 106c. FIG. 5 is a diagram showing an example of the deposit application header data 106d. FIG. 6 is a diagram showing an example of payment application detail data 106e. FIG. 7 is a diagram showing an example of payment schedule data 106f. FIG. 8 is a diagram showing an example of payment header data 106 g. FIG. 9 is a diagram showing an example of payment detail data 106h. FIG. 10 is a diagram showing an example of payment application header data 106i. FIG. 11 is a diagram showing an example of payment application detail data 106j. FIG. 12 is a flowchart showing an example of the journal creation process. FIG. 13 is a diagram showing an example of a journal or the like created in the present embodiment for a bill receivable. FIG. 14 is a diagram showing an example of a journal or the like created in the present embodiment for a bill payable.

Hereinafter, the journal creation device, the journal creation method, and the embodiment of the journal creation program according to the present invention will be described in detail with reference to the drawings. The present invention is not limited to the present embodiment.

[1. Configuration and specific examples of processing]
Here, an example of the configuration of the journal creation device 100 and the like according to the present embodiment will be described with reference to FIG. 1 and the like. FIG. 1 is a block diagram showing an example of the configuration of the journal creation device 100.

The journal creation device 100 is constructed based on a commercially available desktop personal computer. The journal creation device 100 is not limited to a stationary information processing device such as a desktop personal computer, but is a portable type such as a commercially available notebook personal computer, a PDA (Personal Digital Assistants), a smartphone, or a tablet personal computer. It may be an information processing device.

The journal creation device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the journal creation device 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 connects the journal creation device 100 to the network 300 so as to be communicable 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 another device via a communication line. Here, the network 300 has a function of connecting the journal creation device 100 and the server 200 so as to be able to communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). The data stored in the storage 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. As the output device 114, a speaker or a printer can be used in addition to a monitor (including a home television). As the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that cooperates with the mouse to realize a pointing device function can be used. In the following, the output device 114 may be referred to as a monitor 114, and the input device 112 may be referred to as a keyboard 112 or a mouse 112.

Various databases, tables, files, and the like are stored in the storage unit 106. In the storage unit 106, a computer program for giving an instruction to a CPU (Central Processing Unit) in cooperation with an OS (Operating System) to perform various processes is recorded. As the storage unit 106, 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 can be used.

In the storage unit 106, for example, collection schedule data 106a (table), deposit header data 106b (table), deposit detail data 106c (table), deposit application header data 106d (table), deposit application detail data 106e (table). ), Payment schedule data 106f (table), payment header data 106g (table), payment detail data 106h (table), payment application header data 106i (table), payment application detail data 106j (table), and journal data 106k. (Table) etc. are stored.

Here, the collection schedule data 106a corresponds to the collection schedule data table of the present invention. Each record stored in the collection schedule data 106a corresponds to the collection schedule record of the present invention. See FIG. 2 for a specific example of the data to be collected 106a. The collection schedule data 106a may be created and managed in association with the sales data by, for example, the sales recording processing function of the sales management system (application software).

The deposit header data 106b and the deposit detail data 106c are conceptually included in the deposit data table of the present invention. Each record stored in each of the deposit header data 106b and the deposit detail data 106c is conceptually included in the deposit record of the present invention. See FIGS. 3 and 4 for specific examples of the deposit header data 106b and the deposit detail data 106c. The deposit header data 106b and the deposit detail data 106c may be created and managed by, for example, a deposit input function of the sales management system (application software). Examples of the denomination managed by the deposit detail data 106c include, in addition to bills, cash, checks, and transfers.

The deposit application header data 106d and the deposit application detail data 106e are conceptually included in the deposit application data table of the present invention. Each record stored in each of the deposit application header data 106d and the deposit application detail data 106e is conceptually included in the deposit application record of the present invention. See FIGS. 5 and 6 for specific examples of the deposit application header data 106d and the deposit application detail data 106e. The deposit application header data 106d and the deposit application detail data 106e may be created and managed by, for example, the deposit input function of the sales management system (application software).

The payment schedule data 106f corresponds to the payment schedule data table of the present invention. Each record stored in the payment schedule data 106f corresponds to the payment schedule record of the present invention. See FIG. 7 for a specific example of the payment schedule data 106f. The payment schedule data 106f may be created and managed in association with the purchase data by, for example, the purchase accounting processing function of the sales management system (application software).

The payment header data 106g and the payment detail data 106h are conceptually included in the payment data table of the present invention. Each record stored in each of the payment header data 106g and the payment detail data 106h is conceptually included in the payment record of the present invention. See FIGS. 8 and 9 for specific examples of the payment header data 106g and the payment detail data 106h. The payment header data 106g and the payment detail data 106h may be created and managed by, for example, the payment input function of the sales management system (application software). Examples of the denomination managed by the payment statement data 106h include bills, cash, checks, and transfers.

The payment application header data 106i and the payment application detail data 106j are conceptually included in the payment application data table of the present invention. Each record stored in each of the payment application header data 106i and the payment application detail data 106j is conceptually included in the payment application record of the present invention. See FIGS. 10 and 11 for specific examples of the payment application header data 106i and the payment application detail data 106j. The payment application header data 106i and the payment application detail data 106j may be created and managed by, for example, the payment input function of the sales management system (application software).

Each record stored in the journal data 106k corresponds to the journal data of the present invention. Information about the journals managed by each record stored in the journal data 106k is described in each of the journals (in association with the title of "the present embodiment") described in the lower part of each of the figures of FIGS. 13 and 14. Please refer to the journal).

Returning to FIG. 1, the control unit 102 is a CPU or the like that collectively controls the journal creation device 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, required data, and the like, and performs various information processing based on these stored programs. Run. The control unit 102 is functionally provided with a creation unit 102a and the like. The creating unit 102a corresponds to the creating means of the present invention. Please refer to FIG. 12 for a flowchart showing an example of the journal creation process performed by the creation unit 102a.

The creation unit 102a describes "a deposit detail record for which a bill is set as a denomination and a deposit header record associated with the record", and "a deposit application associated with the deposit detail record or the deposit slip No. in the deposit header record". Based on the header record and the payment application detail record linked to the record, and the collection schedule record linked to the collection schedule Guide in the payment application detail record, with the business establishment related to the occurrence of the claim. Recognizing that "department", "business establishments and departments involved in the occurrence of deposits and application of deposits", and "each amount in each record is for the bills receivable received by the department", respectively. At least, the two journal data related to the department transfer of the bills receivable are reversed from each other, and the date of issue is stored in one journal data as the date of occurrence and the date of occurrence is stored in the other journal data. A header (corresponding to the drawing journal (2) and the due date journal (3) shown in the lower part of FIG. 13) is created, and the process of storing the created journal data in the journal data 106k is executed. In addition, the creation unit 102a further creates application journal data related to the clearing of accounts receivable (corresponding to the application journal (1) shown in the lower part of FIG. 13) and stores it in the journal data 106k. May be good. Further, the creation unit 102a may further create the due date journal data (corresponding to the due date arrival journal (4) shown in the lower part of FIG. 13) and store it in the journal data 106k, or, for example, a bill. In cooperation with the system (application software), the due date journal data (corresponding to the due date journal (4) shown in the lower part of FIG. 13) created by the bill system is taken in and stored in the journal data 106k. May be good.

In addition, the creation unit 102a includes "a payment detail record for which a bill is set as a denomination and a payment header record associated with the record" and "a payment associated with the payment detail record or the payment slip No. in the payment header record". Based on the application header record and the payment application detail record associated with the record, and the payment schedule record associated with the payment schedule Guid in the payment application detail record, the business related to the occurrence of debt. Recognizing that "places and departments", "businesses and departments involved in the occurrence of payments and payment reconciliations", and "each amount in each record is for bills payable by the department". At least, the two journal data related to the department transfer of bills payable are reversed from each other, and the date of issue is stored in one journal data as the date of occurrence and the date of occurrence is stored in the other journal data. (Corresponding to the drawing journal (2) and the due date journal (3) shown in the lower part of FIG. 14) is created, and the process of storing the created journal data in the journal data 106k is executed. Even if the creation unit 102a further creates the application journal data related to the clearing of accounts payable (corresponding to the application journal (1) shown in the lower part of FIG. 14) and stores it in the journal data 106k. good. Further, the creation unit 102a may further create the due date journal data (corresponding to the due date arrival journal (4) shown in the lower part of FIG. 14) and store it in the journal data 106k, or, for example, a bill. In cooperation with the system (application software), the due date journal data (corresponding to the due date journal (4) shown in the lower part of FIG. 14) created by the bill system is taken in and stored in the journal data 106k. May be good.

[2. Summary of this embodiment]
There is a business operation that establishes an "in-house interest rate system" in order to properly grasp the profit and loss of each department. In particular, in industries where old business practices remain (for example, the steel industry), there are many transactions using bills, so there is a business operation that establishes an in-house interest rate system according to the volume of bill transactions by department. Here, the in-house interest rate is an interest rate that is artificially assigned in order to reflect the amount of company funds used in the performance evaluation of business divisions and the like. For example, even if there are two businesses that record exactly the same operating profit, if one business is a business that uses a large amount of funds for inventory etc., the company as a whole will use the funds. Since it is considered that businesses that do not have such funds should be highly evaluated, the in-house interest rate system is a mechanism for reflecting the amount of such funds used as numerical values in performance evaluation.

In order to support this business operation, it is necessary to hold bills receivable and bills payable as department-managed items on the accounting system (application software) and grasp the amount of money generated by department. , It was common to use a bill management system (application software) as an option of the accounting system.

However, this general system support has the following two problems.
(1) Since the department information that can be given to the bill on the sales management system (application software) is for each slip, it is necessary to separate the face of the ticket for each department, but when data is linked from the sales management system to the bill management system. Since it is not possible to integrate the face of the bill, it was necessary to manage the bills individually in the bill management system.
(2) In the bill management system, the final management is performed for each bill face, but since only one department information can be held for one bill face, when the bill final journal is generated, the journal is used for one department information. Therefore, it was necessary to issue a transfer journal separately.

According to this embodiment, it is possible to manage departments (division of bills) on the journal based on the bill information generated at the time of deposit and the bill information generated at the time of payment. The present embodiment relates to a division function of a bill subject to enable the management of bills (including Densai) by face and the independent profitability management of B / S subjects. Specifically, it is realized by the following two functions. The first is a function that automatically divides the departments based on the departments that generate accounts receivable and accounts payable that are subject to clearing bills. The second is a function that automatically generates transfer journals assuming the due date of bills for the purpose of managing and operating the bills. The following effects are expected from this embodiment. With regard to bill management, it is possible to be released from multiple management by managing the details of each face of the bill. With regard to financial accounting, by assigning departments to B / S subjects, independent profitability management for each department becomes possible. Regarding credit management, it is possible to perform credit management by taking into account the unsettled amount of bills for each department.

[3. Contribution to the United Nations-led Sustainable Development Goals (SDGs)]
Since this embodiment can contribute to improving operational efficiency and promoting appropriate management decisions of the company, it is possible to contribute to the goals 8 and 9 of the SDGs.

In addition, the present embodiment can contribute to the reduction of waste loss and the promotion of paperless and computerization, and thus can contribute to the goals 12, 13 and 15 of the SDGs.

In addition, since this embodiment can contribute to the strengthening of control and governance, it is possible to contribute to the goal 16 of the SDGs.

[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 ideas described in the claims.

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

In addition, the processing procedure, control procedure, specific name, information including parameters such as registration data and search conditions of each processing, screen examples, and database configuration shown in the present specification and drawings are not specified unless otherwise specified. Can be changed arbitrarily.

Further, with respect to the journal creation 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, with respect to the processing functions included in the journal creation device 100, particularly each processing function performed by the control unit, all or any part thereof may be realized by the CPU and a program interpreted and executed by the CPU. It may be realized as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium including a programmed instruction for causing the information processing apparatus to execute the process described in the present embodiment, and the journal creation apparatus is required. Read mechanically to 100. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or an HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with a CPU to form a control unit.

Further, this computer program may be stored in an application program server connected to the journal creation device 100 via an arbitrary network, and all or a part thereof can be downloaded as needed. be.

Further, the program for executing the process described in the present embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (registration). Trademarks) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magnet-Optical Disk), MO (Magnet-Optical Disk), MO (Magnet-Optical Disc), DVD (Digital), DVD (Digital) It shall include any "portable physical medium".

The "program" is a data processing method described in any language or description method, regardless of the format such as source code or binary code. The "program" is not necessarily limited to a single program, but is distributed as a plurality of modules or libraries, or cooperates with a separate program represented by the OS to achieve its function. Including things. A well-known configuration or procedure can be used for a specific configuration and reading procedure for reading the recording medium in each device shown in the embodiment, an installation procedure after reading, and the like.

Various databases and the like stored in the storage unit are memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and storage means such as optical disks, and are used for various processes and website provision. Stores programs, tables, databases, files for web pages, etc.

Further, the journal creation 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 an arbitrary peripheral device is connected. Further, the journal creation device 100 may be realized by mounting software (including a program or data) that realizes the processing described in the present embodiment on the device.

Further, the specific form of distribution / integration of the device is not limited to the one shown in the drawing, and all or a part thereof may be functionally or physically in an arbitrary unit according to various additions or functional loads. It can be distributed and integrated. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

The present invention is particularly useful in companies such as trading companies and steel companies that have a bill business and perform independent profit management for each department.

100 Journal creation device 102 Control unit
102a Creation unit 104 Communication interface unit 106 Storage unit
106a Scheduled data to be collected
106b Deposit header data
106c Payment details data
106d Deposit application header data
106e Payment application details data
106f Payment schedule data
106g payment header data
106h Payment details data
106i Payment application header data
106j Payment application details data 108 Input / output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (3)

It is a journal creation device equipped with a control unit.
A collection schedule data table that manages the collection schedule number, office, department, and collection schedule amount,
A deposit data table that manages deposit numbers, establishments, departments, denominations, and deposit amounts,
A deposit application data table that manages the deposit application number, deposit number, office, department, collection schedule number, and deposit application amount,
A payment schedule data table that manages payment schedule numbers, offices, departments, and payment schedule amounts,
A payment data table that manages payment numbers, offices, departments, denominations, and payment amounts,
A payment application data table that manages payment application numbers, payment numbers, establishments, departments, payment schedule numbers, and payment application amounts.
Is accessible to
The control unit
1) Based on the payment record for which the bill is set as the denomination, the payment application record linked to the payment record, and the collection schedule record linked to the payment application record, with the business establishment related to the generation of the claim. Recognize that the department, the place of business and department involved in the occurrence of deposits and application, and each amount in each record is for the bills receivable received by the department, and transfer the bills receivable to the department. The process of creating the two related journal data whose lending and borrowing are reversed from each other and the issue date is stored as the occurrence date in one journal data and the due date is stored as the occurrence date in the other journal data. 2) Based on the payment record for which the bill is set as the denomination, the payment application record associated with the payment record, and the payment schedule record associated with the payment application record, with the establishment related to the occurrence of debt. Recognizing that the department, the place of business and department involved in the occurrence of payment and payment application, and each amount in each record is for the bill payable drawn by the department, the department transfer of the bill payable The process of creating the two related journal data whose lending and borrowing are reversed from each other and the issue date is stored as the occurrence date in one journal data and the due date is stored as the occurrence date in the other journal data. To have a means of creation to perform
A journalizing device characterized by. A collection schedule data table that manages the collection schedule number, business establishment, department, and planned collection amount, a deposit data table that manages the deposit number, business establishment, department, denomination, and deposit amount, and a deposit application number and deposit The payment application data table that manages the number, business establishment, department, collection schedule number, and payment application amount, and the payment schedule data table that manages the payment schedule number, business office, department, and payment schedule amount, and the payment number, A payment data table that manages establishments, departments, denominations, and payment amounts, and a payment application data table that manages payment application numbers, payment numbers, offices, departments, payment schedule numbers, and payment application amounts. The control unit of the information processing apparatus including the control unit, which can access the
1) Based on the payment record for which a bill is set as the denomination, the payment application record linked to the payment record, and the collection schedule record linked to the payment application record, with the business establishment related to the generation of the claim. Recognize that the department, the place of business and department involved in the occurrence of deposits and application, and each amount in each record is for the bills receivable received by the department, and transfer the bills receivable to the department. The process of creating the two related journal data whose lending and borrowing are reversed from each other and the issue date is stored as the occurrence date in one journal data and the due date is stored as the occurrence date in the other journal data. 2) Based on the payment record for which a bill is set as the denomination, the payment application record associated with the payment record, and the payment schedule record associated with the payment application record, with the establishment related to the occurrence of debt. Recognizing that the department, the place of business and department involved in the occurrence of payment and payment application, and each amount in each record is for the bill payable drawn by the department, the department transfer of the bill payable The process of creating the two related journal data whose lending and borrowing are reversed from each other and the issue date is stored as the occurrence date in one journal data and the due date is stored as the occurrence date in the other journal data. A journal entry method characterized by performing a creation step that includes. A collection schedule data table that manages the collection schedule number, business establishment, department, and planned collection amount, a deposit data table that manages the deposit number, business establishment, department, denomination, and deposit amount, and a deposit application number and deposit The payment application data table that manages the number, business establishment, department, collection schedule number, and payment application amount, and the payment schedule data table that manages the payment schedule number, business office, department, and payment schedule amount, and the payment number, A payment data table that manages establishments, departments, denominations, and payment amounts, and a payment application data table that manages payment application numbers, payment numbers, offices, departments, payment schedule numbers, and payment application amounts. The control unit of the information processing apparatus including the control unit, which can access the
1) Based on the payment record for which a bill is set as the denomination, the payment application record linked to the payment record, and the collection schedule record linked to the payment application record, with the business establishment related to the generation of the claim. Recognize that the department, the place of business and department involved in the occurrence of deposits and application, and each amount in each record is for the bills receivable received by the department, and transfer the bills receivable to the department. The process of creating the two related journal data whose lending and borrowing are reversed from each other and the issue date is stored as the occurrence date in one journal data and the due date is stored as the occurrence date in the other journal data. 2) Based on the payment record for which a bill is set as the denomination, the payment application record associated with the payment record, and the payment schedule record associated with the payment application record, with the establishment related to the occurrence of debt. Recognizing that the department, the place of business and department involved in the occurrence of payment and payment application, and each amount in each record is for the bill payable drawn by the department, the department transfer of the bill payable The process of creating the two related journal data whose lending and borrowing are reversed from each other and the issue date is stored as the occurrence date in one journal data and the due date is stored as the occurrence date in the other journal data. A journal entry program that acts as a creation tool to execute.

Images