JP2005182237A - Device and method for account processing and account processing program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To perform balance management by clients of spot dealings. <P>SOLUTION: A device is equipped with an input part 2, a display part 3, a client master database recording part 4, a dealings detail database recording part 5, a spot number management master database recording part 6, a spot client master database recording part 7, a continuous client data addition processing part 8 which adds records of continuous clients, a spot representative client data addition processing part 12 which adds records representative of spot clients, a continuous dealings detail data addition processing part 9 which adds records of continuous dealings, a spot dealings data addition processing part 10 which adds records of spot dealings, and an account processing part 11 which totals the amount of dealings of the continuous clients or spot clients. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to an accounting processing apparatus, and further relates to an accounting processing method and an accounting processing program.

  Transactions conducted in companies, etc. include transactions that are continuously performed with a predetermined customer (hereinafter also referred to as “continuous transactions”) and transactions that are performed with a certain customer (hereinafter referred to as “continuous transaction”). "Spot transaction"). A conventional accounting processing apparatus for performing accounting processing relating to such continuous transactions and spot transactions will be described with reference to FIG.

  FIG. 17 is a diagram showing an outline of a conventional accounting processing apparatus. As shown in FIG. 17, this accounting processing device 31 includes an input unit 32, a display unit 33, a supplier master database recording unit 34, a transaction details database recording unit 35, a supplier data addition processing unit 36, A transaction detail data addition processing unit 37 and an accounting processing unit 38 are provided.

  The supplier master database recording unit 34 records a supplier master database for storing data related to suppliers. The business partner master database contains a business partner code field for storing a business partner code for uniquely identifying a business partner, a business partner name field for storing the business partner name, and a business transaction for storing the business partner address. A destination address field, a customer account field for storing an account used to exchange money with a business partner, and a business partner in which data stored in a record is continuously traded (hereinafter referred to as “continuous transaction”). A spot classification field for storing spot classification data indicating whether it is a business partner (hereinafter also referred to as a “spot business partner”) that conducts transactions on a one-off basis.

  The transaction statement database recording unit 35 records a transaction statement database for storing data relating to transaction details. The transaction details database includes a slip number field for storing a slip number that is a number that can uniquely identify a transaction, a supplier code field, a supplier name field, a supplier address field, a supplier account field, and a transaction amount. Has a transaction amount field.

The supplier data addition processing unit 36 performs a process for adding a record to the supplier master database 34 based on the data input from the input unit 32.
The transaction detail data addition processing unit 37 performs a process for adding a record to the transaction detail database 35 based on the data input from the input unit 32.

  The accounting processing unit 38 uses the supplier master database recorded in the supplier master database recording unit 34 and the transaction details database recorded in the transaction details database recording unit 35 to perform accounting processing such as balance management and transfer processing. I do.

Here, when a continuous transaction of 100,000 yen is performed with “A Trading”, the supplier data addition processing unit 36, based on the data input from the input unit 32, the supplier code “001”. , Supplier name "A Shoji", supplier address "Shinagawa-ku Osaki XX-XXX-XXX", supplier account "Shinagawa Bank XX branch current ********", and spot classification "Normal "Is added to the supplier master database. FIG. 18 is a diagram showing the contents of the supplier master database at this time.
Further, based on the data input from the input unit 32, the transaction details data addition processing unit 37 has a slip number “1000”, a business partner code “001”, a business partner name “A Shoji”, a business partner address “Shinagawa Ward” Add a record including “Osaki XXX-XXX-XXX”, customer account “Shinagawa Bank XX Branch Current *****”, and amount “¥ 100,000” to the transaction details database. FIG. 19 shows the contents of the transaction details database at this time.

Next, when a spot transaction of 200,000 yen is performed with “B store”, the supplier data addition processing unit 36 uses the supplier code “002” based on the data input from the input unit 32. A record including the supplier name “spot representative” and the spot classification “spot” is added to the supplier master database. FIG. 20 is a diagram showing the contents of the supplier master database at this time.
Further, based on the data input from the input unit 32, the transaction details data addition processing unit 37 has a slip number “1001”, a customer code “002”, a customer name “B store”, a customer address “Meguro-ku” A record including “Ookayama XXX-XXX”, a customer transfer account “Meguro Bank XX Branch Current *****”, and an amount “¥ 200,000” is added to the transaction details database. FIG. 21 is a diagram showing the contents of the transaction details database at this time.

  Further, when a spot transaction of 300,000 yen is performed with “C store”, the transaction detail data addition processing unit 37, based on the data input from the input unit 32, the slip number “1002”, the transaction Customer code "002", customer name "C store", customer address "Ota-ku Kamata xx-xxx-xxx", customer account "Ota Bank xx branch current ******" A record including the amount “¥ 300,000” is added to the transaction details database. FIG. 22 is a diagram showing the contents of the transaction details database at this time. At this time, the supplier data addition processing unit 36 does not add a record to the supplier master database.

  In the accounting processing device 31, balance management is performed based on the supplier code, but the same supplier code (here, “002”) is assigned to all spot transactions (see FIGS. 20 and 22). The balance management for each spot business partner (here, for each “B store” or for each “C store”) could not be performed.

Further, since there is a desire in a company or the like not to add a record relating to a spot supplier to the supplier master database, the accounting processing device 31 stores the name, address, and account of the spot supplier in the transaction details database. (See FIG. 20 and FIG. 22).
On the other hand, the name, address, and transfer account of the continuous business partner are stored in the business partner master database (see FIG. 20), and it is not necessary to store the name, address, and transfer account of the continuous business partner in the transaction details database. However, from the viewpoint of ensuring the identity of the processing, the name, address, and account of the continuing business partner are stored in the business transaction details database in addition to the business partner master database (see FIG. 22).
Therefore, the amount of data in the transaction statement database has become large.

  Therefore, in view of the above points, an object of the present invention is to provide an accounting processing apparatus that can perform balance management for each spot supplier. Moreover, an object of this invention is to provide such an accounting processing method and an accounting processing program.

  In order to solve the above problems, the accounting processing apparatus according to the present invention performs a single transaction between the first transaction and the second group of business partners that are continuously performed with the first group of business partners. An apparatus for performing accounting processing relating to a second transaction, wherein an input means for inputting various data, and any one of a first group of business partners are uniquely specified or a second group of business partners A supplier code field for storing a supplier code to represent, a supplier name field for storing the name of the first group of suppliers, and a supplier address for storing the address of the first group of suppliers. The field and the transaction account field for storing an account used for exchange of money between the first group business partners, and the data stored in the record are data relating to the first group or the second group business partners. A category file for storing category data A first database including a transaction field, a slip number field for storing a slip number for uniquely identifying the first or second transaction, a partition field for storing partition data, and a supplier code. A customer code field for storing, a customer join key field for storing a customer join key that uniquely identifies either the customer code or the second group of customers, and the first or second transaction A second database including a transaction amount field for storing the transaction amount, a transaction join key field for storing the transaction partner join key, and a transaction for storing the names of the second group of business partners The destination name field, the customer address field for storing the address of the second group of business partners, and the account used for transferring money between the second group of business partners are listed. A transaction means for uniquely identifying a third business partner to be recorded and a new business partner that should belong to the first group of business partners. The destination code is in the supplier code field, the name of the supplier is in the supplier name field, the address of the supplier is in the supplier address field, and the account used to exchange money with the supplier is in the trading account field In addition, any one of the first processing means for adding to the first database a record in which the division data indicating that the supplier belongs to the first group of suppliers is stored in the division field, and any of the first group of suppliers When a first transaction is made with a customer, a slip number that uniquely identifies the transaction is entered in the slip number field, and classification data indicating that the transaction is the first transaction In the Category field, the business partner code that uniquely identifies the business partner is stored in the business partner code field, the business partner code that uniquely identifies the business partner is entered in the business partner join key field, and the transaction amount of the business transaction is entered in the transaction amount field. The second processing means for adding the records stored in the second database, the supplier code representing the second group of suppliers to the supplier code field, and the character string representing the second group of suppliers to the transaction A third processing means for adding a record in which the classification data representing the second group of business partners are stored in the first field to the first database; and a business partner to belong to the second group of business partners When a second transaction is performed between the transaction number and the slip number field, a slip number that uniquely identifies the transaction is displayed in the slip number field, and the transaction is a second transaction. Enter the data in the division field, the supplier code representing the second group of suppliers in the supplier code field, the supplier join key that uniquely identifies the customer in the supplier join key field, and the transaction amount of the transaction. The records stored in the transaction amount field are added to the second database, the customer join key that uniquely identifies the customer is assigned to the customer join key field, the customer name is assigned to the customer name field, A fourth processing means for adding, to the third database, a record in which a business address is stored in the business address field, and an account used for transferring money with the business partner is stored in the business account field; When a value that uniquely identifies one of the suppliers in the group or the second group is entered, the value is entered in the supplier join key field. When the first group of records stored in the field is extracted from the second database and aggregated, and the segment data stored in the segment field in the first group of records represents the first transaction The second group of records whose values are stored in the supplier code field are extracted from the first database, and the data stored in the section field in the first group of records represents the second transaction. And a fifth processing means for extracting, from the third database, a third group of records whose values are stored in the supplier join key field.

  Here, when the third processing means has no record in the supplier code field that stores the supplier code representing the second group of suppliers in the first database, the second group of transactions A record in which the customer code representing the customer is stored in the customer code field, the character string representing the second group of customers is stored in the customer name field, and the classification data representing the second group of customers is stored in the classification field. It may be added to one database.

  Furthermore, the recording means indicates that the first field in which the numerical value is stored and the numerical value stored in the first field is not yet used or already used as the supplier join key. A fourth database having a second field storing data is recorded, and the fourth processing means performs a second transaction with a business partner that should belong to the second group business partner. In addition, a numerical value that is not yet used as a supplier join key may be acquired from the fourth database as a supplier join key that uniquely identifies the supplier.

  In addition, the accounting method according to the present invention is the accounting for the first transaction that is continuously performed with the first group of business partners and the second transaction that is performed with the second group of business partners. In the method for performing processing, when a new business partner that should belong to the first group of business partners is generated, a business partner code that uniquely identifies the business partner is stored in the business partner code field. The name of the business partner is in the business partner name field, the address of the business partner is in the business partner address field, the account used to exchange money with the business partner is in the business account field, and the business partner is the first group. Between the step (a) of adding a record storing classification data indicating belonging to a business partner to the first database to the first database, and the computer between any of the business partners of the first group The first transaction is In this case, the voucher number that uniquely identifies the transaction is entered in the voucher number field, the division data indicating that the transaction is the first transaction is entered in the division field, and the supplier code that uniquely identifies the transaction Adding to the second database a record that stores the customer code in the customer code field, the customer code that uniquely identifies the customer in the customer join key field, and the transaction amount field in the transaction amount field. b), the computer represents the customer code representing the second group of business partners in the business partner code field, the character string representing the second group of business partners in the business partner name field, and the second group of business partners. A step (c) of adding records, each storing classification data in a classification field, to the first database; When a second transaction is made with a business partner to be executed, a slip number that uniquely identifies the transaction is entered in the slip number field, and classification data indicating that the transaction is the second transaction is classified In the field, the business partner code representing the second group of business partners is stored in the business partner code field, the business partner join key that uniquely identifies the business partner is stored in the business partner join key field, and the transaction amount of the business transaction is displayed in the transaction amount field. Are added to the second database, the supplier join key that uniquely identifies the supplier is assigned to the supplier join key field, the supplier name is assigned to the supplier name field, and The third data is a record in which the address is stored in the business address field, and the account used for transferring money with the business partner is stored in the business account field. Step (d) of adding to the base, and when the computer inputs a value that uniquely identifies one of the first group or the second group of business partners, the value is entered into the business partner join key. Step (e) of extracting records from the second database and totalizing records stored in the field, and the division data stored in the division field in the record extracted by the computer in step (e) Represents a first transaction, the step (f) for extracting the record storing the value in the supplier code field from the first database, and the computer the record extracted in step (e) If the category data stored in the category field represents the second transaction, the record storing the value in the customer join key field is the third data. Comprising a step (g) to extract from the over scan.

  Here, step (c) is the second group when the computer stores no record in the first database that stores the customer code representing the second group of customers in the customer code field. A record in which the supplier code representing the customer of the customer is stored in the supplier code field, the character string representing the second group of customers is stored in the supplier name field, and the classification data representing the second group of customers is stored in the classification field. May be added to the first database.

  Furthermore, the computer uses the first field in which the numerical value is stored, and the usage status data indicating that the numerical value stored in the first field is not yet used or has already been used as the supplier join key. When a second transaction is carried out between the step (h) of recording a fourth database having a second field storing and a computer to which the computer should belong to the second group of business partners In addition, the method may further include a step (i) of acquiring from the fourth database a numerical value that is not yet used as a supplier join key as a supplier join key for uniquely specifying the supplier.

  In addition, the accounting processing program according to the present invention provides accounting relating to the first transaction that is continuously performed with the first group of business partners and the second transaction that is performed with the second group of business partners. When a new business partner that should belong to the first group of business partners is generated, a business partner code that uniquely identifies the business partner is entered in the business partner code field. In the business partner name field, the business partner address in the business partner address field, the account used to exchange money with the business partner in the business account field, and the business partner is the first group of business partners. A first transaction between the step (a) of adding records, each of which stores classification data representing belonging to the classification field, to the first database and any one of the first group of business partners If done, the transaction In the slip number field, the slip number that uniquely identifies the transaction is the first transaction, the partition data that indicates that the transaction is the first transaction, the partner code that uniquely identifies the partner in the partner code field, A procedure (b) of adding a record in which a business partner code for uniquely identifying a business partner is stored in the business partner join key field and a transaction amount of the business transaction is stored in the business price field in the second database; A record in which a business partner code representing a business partner is stored in the business partner code field, a character string representing the second group business partner is stored in the business partner name field, and classification data representing the second group business partner is stored in the classification field. When the second transaction is performed between the procedure (c) to be added to the first database and the suppliers that should belong to the second group of suppliers, In the slip number field, the classification data indicating that the transaction is the second transaction in the classification field, the supplier code representing the second group of suppliers in the supplier code field, A transaction that uniquely identifies the business partner by adding a record that stores the business partner join key that uniquely identifies the business partner to the business partner join key field and the transaction value of the business transaction to the business value field in the second database. Trade the account used to exchange money with the customer in the partner join key field, the customer name in the customer name field, the customer address in the customer address field. Step (d) of adding records stored in the account fields to the third database, and any of the first group or the second group of business partners (E) a procedure for extracting and totaling records stored in the customer join key field from the second database when a value uniquely specifying any customer is input; When the division data stored in the division field in the record extracted in (e) represents the first transaction, the record storing the value in the supplier code field is retrieved from the first database. When the category data stored in the category field in the record extracted in step (f) and the record extracted in procedure (e) represents the second transaction, the value is stored in the supplier join key field. And causing the CPU to execute the procedure (g) for extracting the record being performed from the third database.

  Here, when the procedure (c) does not exist in the first database, there is no record storing the customer code representing the second group of customers in the customer code field. The first record is a record in which the customer code representing the customer group is stored in the customer code field, the character string representing the second group of business partners is stored in the customer name field, and the classification data representing the second group of business partners is stored in the classification field. It is also possible to add to the database.

  In addition, a first field storing a numerical value and usage status data indicating that the numerical value stored in the first field is not yet used or already used as a customer join key The supplier join key when the second transaction is performed between the procedure (h) for recording the fourth database having the second field and the suppliers that should belong to the second group of suppliers. It is also possible to further include a procedure (i) of acquiring from the fourth database a numerical value that has not yet been used as a supplier join key for uniquely specifying the supplier.

  According to the above-described configuration, it is possible to perform balance management for each business partner who conducts transactions on a one-off basis.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is a diagram showing an accounting processing apparatus according to an embodiment of the present invention. As shown in FIG. 1, the accounting processing apparatus 1 includes an input unit 2, a display unit 3, a supplier master database recording unit 4, a transaction details database recording unit 5, a spot number management master database recording unit 6, Spot supplier master database recording unit 7, continuation supplier data addition processing unit 8, continuation transaction details data addition processing unit 9, spot transaction data addition processing unit 10, accounting processing unit 11, spot representative customer data And an additional processing unit 12.

  The supplier master database recording unit 4 records a supplier master database for storing data related to suppliers. The supplier master database uniquely identifies one of the suppliers (hereinafter also referred to as “continuous suppliers”) who conduct transactions continuously, or the supplier (hereinafter referred to as “spot supplier”) that conducts transactions on a one-off basis. A supplier code field for storing a supplier code (three-digit number in this embodiment), a supplier name field for storing the supplier name, and an address of the supplier. The business address field for storing the transaction address, the business account field for storing the account for transferring money to and from the business partner, and the data stored in the record is data relating to the continuous business partner A “spot” field for storing spot category data that can take “spot” as a value indicating “normal” or “spot” representing data relating to a spot business partner. .

  The transaction details database recording unit 5 records a transaction details database for storing data relating to transaction details. The transaction details database includes a slip number field for storing a slip number for uniquely identifying a transaction, a spot segment field for storing spot segment data, a partner code field for storing a partner code, It includes a customer join key field for storing a customer code or a customer join key, and an amount field for storing the amount of the transaction. Here, the supplier join key is a value (in this embodiment, a 12-digit number) that uniquely identifies one of the spot suppliers.

  The spot number management master database recording unit 6 has a system automatic numbering field for storing a predetermined number of digits (here, a number of 12 digits) and a number stored in the system automatic numbering field. And a usage status field for storing usage status data indicating whether or not it is already used as a spot customer join key. FIG. 2 is a diagram illustrating an example of a spot number management master database. In the spot number management master database shown in FIG. 2, “000000000001”, “000000000002”, “000000000003”,... Are stored in the system automatic numbering field of a plurality of records, respectively. “Unused” indicating that the number stored in the system automatic numbering field is not yet used as a value for identifying a spot customer is stored.

  Referring to FIG. 1 again, the spot customer master database recording unit 7 includes a customer join key field for storing a customer join key, a customer name field for storing the name of a spot customer, and a spot. It includes a business address field for storing a business address and a business account field for storing an account for exchanging money with a spot business partner.

Referring to FIG. 1 again, the continuous business partner data addition processing unit 8 stores data relating to the continuous business partner in the business partner master database in response to an input from the user.
The spot representative customer data addition processing unit 12 stores a record representing a spot customer in the customer master database in response to an input from the user.
The continuous transaction detail data addition processing unit 9 stores data relating to the transaction details of the continuous transaction in the transaction detail database in response to an input from the user.

The spot transaction data addition processing unit 10 stores data regarding transaction details of spot transactions in the transaction details database and the spot supplier master database in accordance with the input from the user.
The accounting processing unit 11 performs predetermined accounting processing with reference to the supplier master database, the transaction details database, and the spot supplier master database.

  The continuous supplier data addition processing unit 8, the continuous transaction details data addition processing unit 9, the spot transaction data addition processing unit 10, the accounting processing unit 11, and the spot representative customer data addition processing unit 12 shown in FIG. It can be configured by software (program). This program, supplier master database, transaction details database, spot number management master database, and spot supplier master database are hard disk, flexible disk, MO, MT, RAM, CD-ROM, DVD-ROM, etc. It can be recorded on a recording medium.

  FIG. 3 is a flowchart showing the continuous business partner data adding process of the accounting processing apparatus 1. Hereinafter, the continuous customer data adding process of the accounting processing apparatus 1 will be described with reference to FIG.

First, a user inputs a supplier code, a supplier name, a supplier address, and a supplier account from the input unit 2. Here, the user has a supplier code “001”, a supplier name “A Shoji”, a customer address “Shinagawa-ku Osaki XXX-XXX-XXX”, and a customer account “Shinagawa Bank XX branch” “****” is entered.
The continuous supplier data addition processing unit 8 stores the supplier code, supplier name, supplier address, and supplier account input by the user, and further stores the record in which the spot classification “normal” is stored. Add to the master database (step S101). FIG. 4 is a diagram showing the contents of the supplier master database at this time.

  FIG. 5 is a flowchart showing spot representative customer data addition processing of the accounting processing apparatus 1. Hereinafter, the spot representative customer data addition processing of the accounting processing apparatus 1 will be described with reference to FIG.

First, the user inputs a supplier code from the input unit 2. Here, it is assumed that the user inputs the supplier code “002”.
The spot representative supplier data addition processing unit 12 adds a record including the supplier code input by the user and further including the supplier name “spot representative” and the spot classification “spot” to the supplier master database (step S1). S201). FIG. 6 is a diagram showing the contents of the supplier master database at this time.
The spot representative supplier data addition processing unit 12 adds a record only when a record including the supplier name “spot representative” is not yet stored in the supplier master database, and the supplier name “spot representative”. If a record containing is already stored in the supplier master database, no record is added.

  FIG. 7 is a flowchart showing the continuous transaction details data adding process of the accounting processing apparatus 1. Hereinafter, the continuous transaction statement data addition process of the accounting processing apparatus 1 will be described with reference to FIG.

First, the user inputs a slip number, a supplier code, and a transaction amount from the input unit 2. Here, it is assumed that the user inputs a slip number “1000”, a supplier code “001”, and a transaction amount “100,000”.
The continuation transaction details data addition processing unit 9 stores the slip number, the supplier code, and the transaction amount input by the user, stores the spot category “normal”, and further stores the same value as the supplier code. The record stored as the join key is added to the transaction details database (step S301). FIG. 8 shows the contents of the transaction details database at this time.

  FIG. 9 is a flowchart showing spot transaction data addition processing of the accounting processing apparatus 1. Hereinafter, the spot transaction data adding process of the accounting processing apparatus 1 will be described with reference to FIG.

First, the user inputs a spot transaction slip number, transaction amount, supplier name, supplier address, and supplier account. Here, the user has a slip number “1001”, a transaction amount “200,000”, a business partner name “B store”, a business partner address “Ookayama XXX-XXX in Meguro-ku”, and a business partner. Assume that the account “Meguro Bank XX Branch Current ****” is entered.
The spot transaction data addition processing unit 10 refers to the spot number management master database (see FIG. 2), and acquires a number that is not yet used as a value that identifies the spot transaction partner (step S401). Here, it is assumed that the spot transaction data addition processing unit 10 acquires “000000000001”. At this time, the spot transaction data addition processing unit 10 stores “used” in the usage status field in the record including the system automatic numbering number “000000000001”. FIG. 10 is a diagram showing the contents of the spot number management master database at this time.

  Next, the spot transaction data addition processing unit 10 indicates that the slip number and transaction amount input by the user, the supplier join key acquired in step S401, and the supplier name in the supplier master database are “spot representative”. A record storing the customer code (here, “002”) and the spot classification “spot” in a certain record is added to the transaction details database (step S402). FIG. 11 is a diagram showing the contents of the transaction details database at this time.

  Further, the spot transaction data addition processing unit 10 stores the customer name, the business partner address, the business partner account, and the business partner join key acquired in step S401, which are input by the user. It adds to the master database (step S403). FIG. 12 is a diagram showing the contents of the spot supplier master database at this time.

  In addition, after this, when adding the data regarding spot transaction further, the spot transaction data addition process part 10 will perform step S401-step S403 again. For example, the user has a slip number “1002”, a transaction amount “300,000”, a business partner name “C store”, a business partner address “Ota-ku Kamata xxx-xxx-xxx”, and a business partner account “ When “Ota Bank ×× Branch Current *****” is input, the spot transaction data addition processing unit 10 acquires a spot transaction join key (here, “00000000002”) (step S401). FIG. 13 shows the contents of the spot number management master database at this time.

Then, the spot transaction data addition processing unit 10 receives the slip number (here, “1002”) and the transaction amount (here, “300,000”) input by the user, the acquired supplier join key (here, “00000000002”), a customer code in the supplier master database with a customer name “spot representative” in this record, a record storing the customer code (here, “002”) and the spot classification “spot”. (Step S402). FIG. 14 is a diagram showing the contents of the transaction details database at this time.
Further, the spot transaction data addition processing unit 10 receives a customer name (here, “C store”) and a customer address (here, “Ota-ku Kamata xxx-xxx-xxx”) input by the user. , And a customer account (here, “Ota Bank xx branch current ******”)) and a record that stores the acquired customer join key (here “00000000002”) is a spot customer. It adds to the master database (step S403). FIG. 15 is a diagram showing the contents of the spot supplier master database at this time.

  FIG. 16 is a flowchart showing transaction tabulation processing performed by the accounting processing apparatus 1. Hereinafter, the transaction totaling process of the accounting processing apparatus 1 will be described with reference to FIG.

First, the user inputs a supplier code or a supplier join key from the input unit 2.
The accounting processing unit 11 extracts and aggregates records including the supplier code or the customer join key input by the user from the transaction details database (see FIG. 14), and displays the results on the display screen of the display unit 3. (Step S501).

  Next, the accounting processing unit 11 checks whether or not the spot classification in the record extracted in step S501 is “spot”, and if the spot classification in the record extracted in step S501 is not “spot”. In step S503, the process proceeds to step S503. If the spot classification in the record extracted in step S501 is “spot”, the process proceeds to step S504 (step S502).

When it is determined in step S502 that the spot classification is not “spot”, the accounting processing unit 11 extracts a record including the supplier code input by the user from the supplier master database (see FIG. 6), and the supplier name. The customer address and customer account are displayed on the display screen of the display unit 3 (step S503).
On the other hand, when it is determined in step S502 that the spot classification is “spot”, the accounting processing unit 11 extracts a record including the supplier join key input by the user from the spot supplier master database (see FIG. 15). Then, the supplier name, supplier address, and supplier account are displayed on the display screen of the display unit 3 (step S504).

As described above, according to the accounting processing device 1, when a supplier code for uniquely specifying a continuous supplier or a supplier join key for uniquely specifying a spot supplier is input, each continuous supplier or spot supplier The total transaction amount can be calculated.
Further, in the conventional accounting processing device 31 (see FIG. 17), it is necessary to store the customer name, the customer address, and the customer account in the transaction details database. It is not necessary to store the customer name, customer address, and customer account in the transaction details database, and the amount of data in the transaction details database can be reduced.

  The present invention can be used in an accounting processing apparatus, accounting processing method, and accounting processing program. Furthermore, the present invention is for performing accounting processing related to a first transaction that is continuously performed with a first group of business partners and a second transaction that is performed with a second group of business partners. It can be used in an accounting processing apparatus, accounting processing method, and accounting processing program.

It is a figure which shows the outline | summary of the accounting processing apparatus which concerns on one Embodiment of this invention. It is a figure which shows an example of the spot number management master database recorded on the spot number management master database recording part 6 of FIG. It is a flowchart which shows the continuous customer data addition process of the accounting processing apparatus 1 of FIG. It is a figure which shows an example of the supplier master database recorded on the supplier master database recording part 4 of FIG. It is a flowchart which shows the spot representative customer data addition process of the accounting processing apparatus 1 of FIG. It is a figure which shows an example of the supplier master database recorded on the supplier master database recording part 4 of FIG. It is a flowchart which shows the continuous transaction detailed data addition process of the accounting processing apparatus 1 of FIG. It is a figure which shows an example of the transaction statement database recorded on the transaction statement database recording part 5 of FIG. It is a flowchart which shows the spot transaction data addition process of the accounting processing apparatus 1 of FIG. It is a figure which shows an example of the spot number management master database recorded on the spot number management master database recording part 6 of FIG. It is a figure which shows an example of the transaction statement database recorded on the transaction statement database recording part 5 of FIG. It is a figure which shows an example of the spot supplier master database recorded on the spot supplier master database recording part 7 of FIG. It is a figure which shows an example of the spot number management master database recorded on the spot number management master database recording part 6 of FIG. It is a figure which shows an example of the transaction statement database recorded on the transaction statement database recording part 5 of FIG. It is a figure which shows an example of the spot supplier master database recorded on the spot supplier master database recording part 7 of FIG. It is a flowchart which shows the transaction total process of the accounting processing apparatus 1 of FIG. It is a figure which shows the outline | summary of the conventional accounting processing apparatus. It is a figure which shows an example of the supplier master database recorded on the supplier master database recording part 34 of FIG. It is a figure which shows an example of the transaction statement database recorded on the transaction statement master database recording part 35 of FIG. It is a figure which shows an example of the supplier master database recorded on the supplier master database recording part 34 of FIG. It is a figure which shows an example of the transaction statement database recorded on the transaction statement master database recording part 35 of FIG. It is a figure which shows an example of the transaction statement database recorded on the transaction statement master database recording part 35 of FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1,31 Accounting processing device 2,32 Input part 3,33 Display part 4,34 Supplier master database recording part 5,35 Transaction details database recording part 6 Spot number management master database recording part 7 Spot supplier master database recording part 8 Continuing business partner data addition processing unit 9 Continuing business transaction data addition processing unit 10 Spot transaction data addition processing unit 11, 38 Accounting processing unit 12 Spot representative business partner data addition processing unit 36 Business partner data addition processing unit 37 Transaction detailed data addition processing Part

Claims (9)

An apparatus for performing accounting for a first transaction that is continuously performed with a first group of business partners and a second transaction that is performed with a second group of business partners,
Input means for inputting various data;
A customer code field for uniquely identifying one of the first group of business partners or storing a business partner code representing the second group of business partners, and a name of the first group of business partners are stored. A customer name field, a customer address field for storing the address of the first group of business partners, and an account used for sending and receiving money between the first group of business partners. A first database comprising: a trading account field; and a sorting field for storing sorting data indicating that the data stored in the record is data relating to the first group or the second group of business partners, A slip number field for storing a slip number for uniquely identifying the first or second transaction, a partition field for storing the partition data, and a supplier for storing the supplier code Field, a customer join key field for storing a customer join key that uniquely specifies either the customer code or the second group of customers, and the transaction amount of the first or second transaction. A second database including a transaction amount field for storing the transaction, a customer join key field for storing the customer join key, and a transaction for storing the names of the second group of business partners A destination name field, a business address field for storing the address of the second group of business partners, and a business account field for storing an account used for exchange of money between the business partners of the second group Recording means for recording a third database including:
When a new business partner that should belong to the first group of business partners is generated, the business partner code that uniquely identifies the business partner is stored in the business partner code field, and the business partner name is used as the business partner name. In the field, the address of the business partner belongs to the business partner address field, the account used for money exchange with the business partner belongs to the business account field, and the business partner belongs to the first group of business partners. First processing means for adding to the first database records that respectively store the partition data representing the partition data in the partition field;
When the first transaction is performed with any one of the first group of business partners, the slip number uniquely specifying the transaction is entered in the slip number field, and the transaction is The division data representing the first transaction is in the division field, the supplier code that uniquely specifies the supplier is in the supplier code field, and the supplier code that uniquely specifies the supplier A second processing means for adding a record storing the transaction amount of the transaction in the transaction amount field to the second party database,
The customer code representing the second group of business partners is represented in the business partner code field, a character string representing the second group of business partners is represented in the business partner name field, and the second group of business partners is represented. A third processing means for adding records each storing partition data in the partition field to the first database;
When the second transaction is performed with a business partner that should belong to the second group business partner, the slip number that uniquely identifies the transaction is entered in the slip number field, and the transaction is The supplier data that uniquely identifies the customer in the customer field that contains the customer data representing the second group of customers in the customer field. A record in which the key is stored in the supplier join key field and the transaction amount of the transaction is stored in the transaction amount field is added to the second database, and the supplier join key for uniquely identifying the supplier is In the supplier join key field, the name of the supplier in the supplier name field, the address of the supplier in the supplier address field, And fourth processing means for adding a record stored respectively in the transaction account field account to the third database to be used for money transfer between the,
When a value uniquely specifying one of the first group or the second group of suppliers is input, the value is stored in the supplier join key field. When a group record is extracted from the second database and aggregated, and the segment data stored in the segment field in the first group record represents the first transaction, the value is A second group of records stored in the supplier code field is extracted from the first database, and the data stored in the segment field in the first group of records is the second transaction. A fifth processing means for extracting a third group of records storing the value in the supplier join key field from the third database,
An accounting processing apparatus comprising: When the third processing means does not have a record storing the supplier code representing the second group of suppliers in the supplier code field in the first database, the second database The customer code representing a group of business partners in the business partner code field, a character string representing the second group of business partners in the customer name field, and the segment data representing the second group of business partners The accounting processing apparatus according to claim 1, wherein the records respectively stored in the division fields are added to the first database. The recording means uses a first field storing a numerical value and a numerical value stored in the first field indicating that the numerical value stored in the first field is not yet used or already used as the supplier join key A fourth database having a second field storing status data;
When the second transaction is performed with the business partner that should belong to the business partner of the second group, the fourth processing means calculates a numerical value that is not yet used as the business partner join key. The accounting processing apparatus according to claim 1, wherein the transaction processing apparatus is obtained from the fourth database as the supplier join key for uniquely specifying a supplier. A method for accounting for a first transaction that is continuously performed with a first group of business partners and a second transaction that is performed with a second group of business partners,
When a new business partner that should belong to the first group of business partners is generated by the computer, a business partner code that uniquely identifies the business partner is entered in the business partner code field, and the name of the business partner is entered as the business partner name. In the field, the address of the business partner is represented in the business partner address field, the account used for money exchange with the business partner is represented in the business account field, and the business partner belongs to the first group business partner. Adding to the first database records each storing partition data in a partition field;
When the computer performs the first transaction with any one of the first group of business partners, a slip number uniquely identifying the transaction is entered in the slip number field, The division data representing the first transaction is set in a division field, the supplier code for uniquely specifying the supplier is set in the supplier code field, and the supplier code for uniquely specifying the supplier is (B) adding to the second database a record storing the transaction amount of the transaction in the transaction amount field in the supplier join key field;
The computer includes the supplier code representing the second group of suppliers in the supplier code field, a character string representing the second group of suppliers in the supplier name field, and the second group of suppliers. (C) adding to the first database a record that stores the partition data representing each in the partition field;
When the computer performs the second transaction with a business partner that should belong to the second group business partner, the slip number for uniquely identifying the transaction is entered in the slip number field. Transaction that uniquely identifies the customer in the customer field indicating the customer data representing the second group of customers in the customer field A record in which a destination join key is stored in the supplier join key field and a transaction amount of the transaction is stored in the transaction amount field is added to the second database, and the supplier join key for uniquely identifying the supplier is In the business partner join key field, the business partner name is in the business partner name field, the business partner address is in the business partner address field, and And step (d) adding a record storing each account trading account field to a third database for use in the money transfer,
When the computer inputs a value that uniquely identifies one of the first group or the second group of business partners, the value is stored in the business partner join key field. A step (e) of extracting and tabulating the existing records from the second database;
When the segment data stored in the segment field in the record extracted in step (e) represents the first transaction, the computer stores the value in the supplier code field. Extracting a record from the first database (f);
The computer stores the value in the customer join key field when the category data stored in the category field in the record extracted in step (e) represents the second transaction. Extracting from the third database (g)
An accounting method comprising: Step (c), wherein when the computer does not have a record in the customer code field representing the customer code representing the second group of customers in the customer code field, the first database The business partner code representing a second group of business partners in the business partner code field, a character string representing the second group of business partners in the business partner name field, and the classification data representing the second group of business partners. The accounting processing method according to claim 4, wherein records respectively stored in the division field are added to the first database. A first field in which the computer stores a numerical value, and usage data representing that the numerical value stored in the first field is not yet used or has already been used as the supplier join key (H) recording a fourth database having a second field storing
When the second transaction is performed with a business partner that should belong to the business partner of the second group, the computer uniquely identifies the business partner as a numerical value that is not yet used as the business partner join key. The accounting method according to claim 4, further comprising a step (i) of acquiring from the fourth database as the supplier join key to be specified. A program for accounting for a first transaction that is continuously performed with a first group of business partners and a second transaction that is performed with a second group of business partners,
When a new business partner that should belong to the first group of business partners is generated, a business partner code for uniquely identifying the business partner in the business partner code field, a name of the business partner in the business partner name field, Classification data representing that the address of the business partner belongs to the business partner address field, the account used for sending and receiving money with the business partner to the business account field, and that the business partner belongs to the first group business partner. A procedure (a) for adding the records respectively stored in the section fields to the first database;
When the first transaction is performed with any one of the first group of business partners, a slip number that uniquely identifies the transaction is entered in the slip number field, and the transaction is the first business partner. The classification data indicating that the transaction is a classification field, the trading partner code that uniquely identifies the trading partner in the trading partner code field, and the trading partner code that uniquely identifies the trading partner A step (b) of adding records each storing the transaction amount of the transaction in the transaction amount field to the second database in the key field;
The customer code representing the second group of business partners is represented in the business partner code field, a character string representing the second group of business partners is represented in the business partner name field, and the second group of business partners is represented. A step (c) of adding records each storing partition data in the partition field to the first database;
When the second transaction is performed with a business partner that should belong to the second group business partner, the slip number that uniquely identifies the transaction is entered in the slip number field, and the transaction is A customer join key for uniquely identifying the customer in the customer field indicating the customer data of the second group in the customer code field. Is added to the second database, and the customer join key for uniquely identifying the customer is added to the customer join key field. In the key field, the name of the business partner in the business partner name field, the address of the business partner in the business partner address field, and money exchange with the business partner. And Step (d) adding a record storing each account trading account field are in the third database,
When a value for uniquely identifying one of the first group or the second group of business partners is input, a record storing the value in the business partner join key field A procedure (e) of extracting and counting from the second database;
A record in which the value is stored in the supplier code field when the classification data stored in the classification field in the record extracted in step (e) represents the first transaction. Extracting from the first database (f);
When the division data stored in the division field in the record extracted in step (e) represents the second transaction, the value is stored in the supplier join key field. A procedure (g) for extracting records from the third database;
Accounting processing program for causing the CPU to execute. When the record storing the customer code representing the second group of business partners in the business partner code field does not exist in the first database in the step (c), the second group of business partners The supplier code representing a supplier is in the supplier code field, a character string representing the second group of suppliers is in the supplier name field, and the partition data representing the second group of suppliers is in the partition The accounting processing program according to claim 7, wherein the records respectively stored in the fields are added to the first database. A first field storing a numerical value and usage data indicating that the numerical value stored in the first field is not yet used or has already been used as the customer join key Recording a fourth database having a second field (h);
When the second transaction is performed with a business partner that should belong to the second group business partner, the business partner uniquely identifies a numerical value that is not yet used as the business partner join key The accounting processing program according to claim 7 or 8, further comprising a procedure (i) for acquiring from the fourth database as a supplier join key.

Images