JP5544871B2 - Terminal device and program - Google Patents

Description

The present invention relates to a terminal device and a program .

  2. Description of the Related Art Conventionally, sales data processing devices such as ECR (Electronic Cash Register) for registering sales of products are known. In the sales data processing apparatus, it is possible to input a product that has been sold with a simple operation using a barcode or a touch panel (see, for example, Patent Document 1). In addition, in retail stores, restaurants, and other stores, in addition to sales, a number of transactions such as purchases / withdrawals are frequently performed.

JP 09-245253 A

  However, in the sales data processing device, transactions such as purchase / payment / withdrawal cannot be made in units of transaction occurrence. Therefore, in order for the company (owner) that manages the store where the sales data processing device is installed to know the purchases and withdrawals of the store, employees with knowledge such as double-entry bookkeeping must use the accounting system. It was cumbersome because it was necessary to do journaling work while looking at receipts on the screen.

SUMMARY OF THE INVENTION An object of the present invention is to enable a transaction that requires journal entry to be registered by a data processing apparatus and to enable the registered transaction to be journalized.

The invention according to claim 1 is a terminal device connected to a server device that receives data transmitted from a data processing device, and corresponds to journal entry rule information of a transaction registered in the data processing device. Setting means for setting identification information, storage means for storing the transaction rule information set by the setting means and the identification information in association with each other, journal information rule information for the transaction, and the identification information An output means for outputting a correspondence table indicating a correspondence relationship, and receiving for receiving transaction identification information and a transaction amount transmitted from the data processing device to the server device and transferred from the server device when a transaction occurs And journal entry rule information of the transaction corresponding to the identification information received by the receiving means, read out from the storage means, And a creation means for creating a journal data journal amounts of the transaction in accordance with distribution.

According to the present invention, a transaction that requires journal entry can be registered by the data processing device, and the registered transaction can be journalized.

It is a figure which shows the example of whole structure of the sales data processing system in embodiment of this invention. It is a block diagram which shows the functional structure of the center server of FIG. It is a block diagram which shows the functional structure of ECR of FIG. It is a block diagram which shows the functional structure of the client PC of FIG. It is a figure which shows the data storage example of the 1st journal entry rule file memorize | stored in the memory | storage part of FIG. It is a figure which shows the example of data storage of the 2nd journal rule file memorize | stored in the memory | storage part of FIG. It is a figure which shows the data storage example of the barcode book output item file memorize | stored in the memory | storage part of FIG. It is a figure which shows the example of data storage of the classification table file memorize | stored in the memory | storage part of FIG. It is a flowchart which shows the journal rule setting (sales) process performed by CPU of FIG. It is a figure which shows an example of the sales journal rule setting screen displayed on the display part of FIG. It is a figure which shows an example of the sales journal rule setting screen displayed on the display part of FIG. It is a flowchart which shows the journal rule setting (purchasing / withdrawal) process performed by CPU of FIG. It is a figure which shows an example of the deposit / withdrawal journal entry rule setting screen displayed on the display part of FIG. It is a figure which shows an example of the deposit / withdrawal journal entry rule setting screen displayed on the display part of FIG. It is a flowchart which shows the journalizing rule barcode book output process performed by CPU of FIG. It is a figure which shows an example of a journal entry rule barcode book. It is a flowchart which shows the registration process performed by CPU of FIG. It is a figure which shows the data structural example of the purchase / payment / withdrawal data created in the registration process of FIG. It is a figure which shows the data structural example of the sales data produced in the registration process of FIG. It is a flowchart which shows the journal data creation process performed by CPU of FIG. It is a flowchart which shows the purchase / payment / withdrawal data conversion process performed by CPU in FIG.18 S93. It is a figure which shows the example of data storage of the journal data file memorize | stored in the memory | storage part of FIG. It is a flowchart which shows the sales data conversion process performed in step S94 of FIG. It is a flowchart which shows the cash selling process performed in step S204 of FIG. It is a flowchart which shows the credit process performed in step S206 of FIG. It is a flowchart which shows the data conversion process performed in step S405 of FIG. It is a flowchart which shows the ticket sales process performed in step S208 of FIG. It is a flowchart which shows the lending process performed in step S210 of FIG. It is a flowchart which shows the journal data edit process performed by CPU of FIG. FIG. 5 is a diagram illustrating an example of a journal data editing screen displayed on the display unit of FIG. 4. FIG. 5 is a diagram illustrating an example of a journal data editing screen displayed on the display unit of FIG. 4. It is a flowchart which shows the format conversion process performed by CPU of FIG.

  Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. The present invention is not limited to the illustrated example.

(Configuration of sales data processing system 1)
First, with reference to FIG. 1, the structure of the sales data processing system 1 of this embodiment is demonstrated.
As shown in FIG. 1, the sales data processing system 1 includes a center server 10 as a server device, ECRs 20A and 20B as sales data processing devices, and client PCs 30A and 30B as terminal devices. .

  The center server 10 is communicatively connected to the ECRs 20A and 20B via a communication network N such as the Internet. ECR 20A, 20B is installed in each store that sells products, and when a transaction occurs, registration of sales (input of sold products, quantity, amount, payment method, etc.) and registration of purchases / payments are made. It is a device for receiving sales data D1 and purchasing / withdrawal data D2. The number of ECRs is not limited to the example of FIG.

  The center server 10 is communicatively connected to the client PCs 30A and 30B via a communication network N such as the Internet. The client PCs 30A and 30B are terminal devices of users (a company of the sales data processing system 1 and a company that manages a store where the ECRs 20A and 20B are installed).

(Configuration of the center server 10)
Next, the internal configuration of the center server 10 will be described.
FIG. 2 is a block diagram illustrating a functional configuration example of the center server 10. As shown in FIG. 2, the center server 10 includes a CPU (Central Processing Unit) 11, an input unit 12, a RAM 13 (Random Access Memory), a display unit 14, a storage unit 15, a communication unit 16, and a timekeeping. A unit 17 and a printing unit 18 are provided, and each unit is connected via a bus 19.

  The CPU 11 centrally controls each unit of the center server 10. The CPU 11 expands a program designated from the system program and various application programs stored in the storage unit 15 in the RAM 13 and executes various processes in cooperation with the program expanded in the RAM 13. For example, the CPU 11 executes cash register authentication processing, data storage processing, data transfer processing, and the like, which will be described later, in cooperation with the program.

  The input unit 12 includes a keyboard having cursor keys, characters, numeric input keys, various function keys, and the like, and outputs an operation signal indicating that each key is pressed by the operator to the CPU 11. The input unit 12 may include a pointing device such as a mouse, and may receive a position input signal and transmit it to the CPU 11.

  The RAM 13 is a volatile memory that temporarily stores information, and has a plurality of work areas that store various programs to be executed and data related to these various programs.

  The display unit 14 is configured by an LCD (Liquid Crystal Display), an ELD (Electro Luminescent Display), or the like, and performs various displays according to a display signal from the CPU 11.

  The storage unit 15 is configured by an HDD (Hard Disk Drive) having a magnetic recording medium, and stores various programs and various data so that they can be read and written from the recording medium. The various programs include programs for causing the CPU 11 to execute a registration authentication process, a data storage process, and a data transfer process, which will be described later.

The storage unit 15 stores a cash register authentication master 151, a destination master 152, a PC authentication master 153, and the like.
The cash register authentication master 151 is a master file that stores information for the center server 10 to authenticate cash register (ECR). The cash register authentication master 151 stores, for each ECR, a “register code” for identifying the ECR, a “company code” for identifying the user who manages the ECR, and the like.

The destination master 152 is a master file for storing folder path information of folders for each company. The destination master 152 stores, for each company, a “registration code” for identifying an ECR, a “company code” for identifying a user (company), a “company name”, and sales data D1 transmitted from an ECR managed by the user. In addition, “destination folder path” indicating the folder path of the folder storing the purchase / payment / withdrawal data D2 is stored.
The PC authentication master 153 is a master file that stores information for the center server 10 to authenticate the client PC. The PC authentication master 153 stores, for each client PC, the “company code”, “login ID”, “password”, and the like of the user of the client PC.

  The communication unit 16 includes a modem, a TA (Terminal Adapter), a router, a network card, and the like. The communication unit 16 transmits and receives information to and from the ECRs 20A and 20B on the connected communication network N. The communication unit 16 transmits and receives information to and from the client PCs 30A and 30B.

The timer unit 17 has a built-in timer circuit, and measures and outputs the current time (system time) and the current date (system date and time).
The printing unit 18 is configured by an electrophotographic printer, an ink jet printer, and the like, and prints various print information on a sheet in accordance with a print instruction input from the CPU 11.

(Configuration of ECR 20A, 20B)
Next, the internal configuration of the ECRs 20A and 20B will be described.
FIG. 3 is a block diagram showing a functional configuration of the ECRs 20A and 20B. In the following description, the configuration of the ECR 20A will be described as a representative, but the configuration of the ECR 20B is the same.

  As shown in FIG. 3, the ECR 20A includes a CPU 21, an input unit 22, a RAM 23, a display unit 24, a storage unit 25, a communication unit 26, a drawer 27, a print unit 28, a timing unit 29, Each part is connected via a bus 29a.

  The CPU 21, the RAM 23, the communication unit 26, and the time measuring unit 29 are the same as the configurations of the CPU 11, the RAM 13, the communication unit 16, and the time measuring unit 17 of the center server 10, respectively, and different parts will be mainly described.

  The CPU 21 centrally controls each part of the ECR 20A. The CPU 21 develops a program designated from the system program and various application programs stored in the storage unit 25 in the RAM 23, and executes various processes in cooperation with the program expanded in the RAM 23. For example, the CPU 21 functions as a registration unit and a data creation unit by executing a registration process described later in cooperation with a program.

  The input unit 22 includes a cash register keyboard including cursor keys, characters, numeric input keys, various function buttons, and the like, and outputs an operation signal to the CPU 21 when each key or button is pressed by the operator. The input unit 22 may be configured as a touch panel integrally with the display unit 24. Further, the input unit 22 includes a barcode scanner that reads a barcode provided on the product or a barcode printed on the journalizing rule bar coat book 381 shown in FIG.

  In the present embodiment, the input unit 22 includes, as function buttons, a journal button, a date button, a payment button (cash button, ticket button, loan button, credit button) and the like (not shown). The journal button is a button for inputting an instruction for recognizing a numerical value input immediately before as a journal rule number. The date button is a button for inputting an instruction for recognizing the numerical value input immediately before as the slip date. The payment button is a button for inputting a payment method for sales.

  A function code and a character (key character) are associated with the journal button and the payment button in advance. For example, the journal button is associated with function code = 0901 and character = journal. The function code = 0001 and the character = cash are associated with the cash button. The ticket button is associated with function code = 0002 and character = ticket. The credit button is associated with function code = 0003 and character = lend. The credit button is associated with function code = 0004 and character = credit. The correspondence between each function button, the function code, and the character is stored in the storage unit 25.

  The input unit 22 includes a mode switch. The mode switch is a switch for switching the operation mode of the ECR 20A to any one of a registration mode, an inspection mode, a checkout mode, a setting mode, an OFF mode, and a return mode. The registration mode is a mode for registering transactions such as sales, journal entries, and withdrawals.

  The display unit 24 includes an LCD, an ELD, and the like, and performs screen display according to a display control signal from the CPU 21.

The storage unit 25 is configured by a ROM (Read Only Memory) or the like. The storage unit 25 stores various programs and various data so that they can be read from the ROM. The storage unit 25 may be configured with an HDD or the like. The storage unit 25 stores a registration code for identifying the ECR.
The communication unit 26 transmits / receives information to / from the center server 10 on the communication network N. The communication unit 26 functions as a transmission unit.

  The drawer 27 is a drawer that stores cash such as coins and banknotes. For example, the drawer 27 opens the drawer according to an instruction from the CPU 21.

  The printing unit 28 is, for example, a thermal printer, and has receipt and journal roll papers, and prints out data such as the amount of money on each roll paper in accordance with an instruction input from the CPU 21.

(Configuration of client PCs 30A and 30B)
Next, the internal configuration of the client PCs 30A and 30B will be described.
FIG. 4 is a block diagram showing a functional configuration of the client PCs 30A and 30B. In the following description, the configuration of the client PC 30A will be described as a representative, but the configuration of the PC 30B is the same.

  As shown in FIG. 4, the client PC 30 </ b> A includes a CPU 31, an input unit 32, a RAM 33, a display unit 34, a storage unit 35, a communication unit 36, a timer unit 37, and a printing unit 38 as an output unit. , And each part is connected via a bus 39.

  The CPU 31, the input unit 32, the RAM 33, the display unit 34, the storage unit 35, the communication unit 36, the timing unit 37, and the printing unit 38 are respectively the CPU 11, the input unit 12, the RAM 13, the display unit 14, and the storage unit 15 of the center server 10. The configuration is the same as that of the communication unit 16, the time measuring unit 17, and the printing unit 18, and different parts will be mainly described.

  The CPU 31 centrally controls each part of the client PC 30A. The CPU 31 expands a program designated from the system program and various application programs stored in the storage unit 35 in the RAM 33 and executes various processes in cooperation with the program expanded in the RAM 33. For example, the CPU 31 cooperates with the program to make a journal rule setting (sales) process, a journal rule setting (purchase / withdrawal) process, a journal rule barcode book output process, a journal data creation process, and a journal data edit process, which will be described later. By executing the format conversion process, etc., it functions as a setting means, journal data creation means, journal data editing means, and format conversion means.

  The storage unit 35 is configured by an HDD or the like having a magnetic recording medium. The storage unit 35 stores system programs executed by the CPU 31, various application programs, data necessary for executing these programs, and the like.

  In the present embodiment, the storage unit 35 stores a first journal rule file 351, a second journal rule file 352, a barcode book output item file 353, a classification table file 354, and a journal data file 355. .

The first journal rule file 351 is a file for storing journal rule information about sales set in a journal rule setting (sales) process described later.
FIG. 5 is a diagram illustrating a data storage example of the first journal entry rule file 351. As shown in FIG. 5, the first journal entry rule file 351 includes “record No.”, “accounting software classification”, “classification”, “item name”, “account item code”, “auxiliary item code”, “ Items such as “Account name”, “Subsidiary name”, “Tax classification”, “Card company code or sub function code” are provided.

  In the present embodiment, the first journal entry rule file 351 is provided with records “Record No.” = 01 to 25 in advance. “Record No.” = 1 is a record for storing the classification of accounting software indicating the type of accounting software used in the client PC 30A. Accounting software category = 1 indicates accounting software 1, accounting software category = 2 indicates accounting software 2, accounting software category = 3 indicates accounting software 3. “Record No.” = 02 to 05 is a record for storing the journal entry rule information about the sales target (product sales, service fee, etc.). “Record No.” = 06 to 10 is a record for storing journal entry rule information for cash sale. “Record No.” = 11 to 15 is a record for storing journal entry rule information about credits. “Record No.” = 16 to 20 is a record for storing journal entry rule information for ticket sales. “Record No.” = 21 to 25 is a record for storing the journal entry rule information for the lending. The “Category” and “Item Name” items of each record store the transaction classification and the transaction item name in advance, and the “Account Item Code” and “Auxiliary Item” of each record by journal entry rule setting (sales) processing. "Code", "Account name", "Sub-subject name", "Tax classification", "Card company code or subfunction code" are set.

The second journal rule file 352 is a file for storing journal rule information for each transaction item of purchase and deposit / withdrawal set in a journal rule setting (purchase / deposit / withdrawal) process described later.
FIG. 6 is a diagram illustrating a data storage example of the second journal entry rule file 352. As illustrated in FIG. As shown in FIG. 6, the second journal rule file 352 includes “journal rule number”, “8-digit bar code”, “summary (transaction item)”, “spot transaction category”, “debit account code”, "Debit sub-item code", "Debit account name", "Debit sub-account name", "Debit tax category", "Credit account code", "Credit sub-item code", "Credit account name", "Credit Items such as “Auxiliary subject name” and “Credit tax classification” are provided. The journal entry rule number is an identification number for identifying the entry rule information. The spot transaction is a transaction in which the transaction destination is not predetermined (not fixed), and in the case of a spot transaction, the spot transaction classification = 1.

  In the present embodiment, the second journal entry rule file 352 is provided with records to which “journal entry rule numbers” = 001 to 200 are assigned in advance. Records with “journal rule number” = 001 to 050 are records for storing journal rule information regarding purchase. The records of “journal rule number” = 051 to 100 are records for storing journal rule information about payment. The record of “journal rule number” = 101 to 200 is a record for storing journal rule information regarding withdrawal. In addition, the “8-digit barcode” of each record stores in advance a numerical value composed of a fixed value of 4 digits (here 2900) + journal rule number (3 digits) + check digit.

  The barcode book output item file 353 stores information on which item of which file in each item of the barcode book when the journal rule barcode book 381 (see FIG. 14) is output in the journal rule barcode book output process described later. Is a file in which information indicating whether to output is stored. The barcode book output item file 353 is provided with items such as “barcode book item” and “information to be output” as shown in FIG.

The classification table file 354 is a file that stores information indicating the correspondence relationship between the journal rule number and the print character when outputting the “classification” item of the barcode book in the journal rule barcode book output process described later. As shown in FIG. 8, the classification table file 354 includes items “journal rule number” and “print character”.
The journal data file 355 is a file for storing the created journal data.

  The communication unit 36 in FIG. 4 communicates with external devices such as the center server 10 on the communication network N. The communication unit 36 functions as a receiving unit.

Next, the operation of the sales data processing system 1 will be described.
(Journal rule setting process on client PC)
First, the journal entry rule setting process executed in the client PCs 30A and 30B will be described. Here, the processing of the client PC 30A will be described as a representative, but the same applies to the client PC 30B.

  FIG. 9 is a flowchart showing journal entry rule setting (sales) processing. The journal rule setting (sales) process is a process for setting journal rule information about sales in the first journal rule file 351 described above in accordance with the operation of the operator. The journal rule setting (sales) process is executed in cooperation with the CPU 31 and the program of the storage unit 35 when the input unit 32 instructs to set the journal rule for sales.

  First, the first journal entry rule file 351 is read from the storage unit 35 and expanded in the RAM 33 (step S1), and the sales journal rule setting screen information is read from the screen information file (not shown) stored in the storage unit 35. The sales journal rule setting screen 341 is displayed on the display unit 34 (step S2).

  FIG. 10A to FIG. 10B show an example of the sales journal rule setting screen 341. As shown in FIG. 10A, the sales journal rule setting screen 341 includes an accounting software tab T1, a sales target tab T2, a cash selling tab T3, a credit tab T4, a ticket selling tab T5, a selling tab T6, a confirmation button B1, and a cancel. Button B2 is provided. When the accounting software tab T1 is selected by the input unit 32, an accounting software selection field 341a is displayed on the sales journal rule setting screen 341 as shown in FIG. 10A. When the sales target tab T2 is selected by the input unit 32, as shown in FIG. 10B, an input field 341b for inputting a journal rule for each sales target (product sales, service charge) is displayed on the sales journal rule setting screen 341. Is displayed. Similarly, when the cash sales tab T3 is selected by the input unit 32, an input column for inputting a journal rule for cash sales is displayed on the sales journal rule setting screen 341. When the credit tab T4 is selected by the input unit 32, an input column for inputting a journal rule regarding sales by credit is displayed on the sales journal rule setting screen 341. When the ticket sales tab T4 is selected by the input unit 32, an input column for inputting a journal rule for ticket sales is displayed on the sales journal rule setting screen 341. When the sale tab T5 is selected by the input unit 32, an input column for entering a journal entry rule for sale is displayed on the sales entry rule setting screen 341. In the initial state, the screen display is the same as when the accounting software tab T1 is selected. If there is journal rule information already set in the first journal rule file 351, the current setting content is displayed in the input column by default, and the setting content can be changed and input.

  It is determined whether or not the input from the accounting software tab T1 of the sales journal rule setting screen 341 is performed by the input unit 32 (step S3). Specifically, it is determined whether or not an input has been made from the accounting software selection field 341a displayed when the accounting software tab T1 is selected by the input unit 32. If it is determined by the input unit 32 that an input has been made from the accounting software tab T1 (step S3; YES), the input unit 32 is displayed with the accounting software tab T1 selected (the accounting software selection field is displayed). Thus, it is determined whether or not the confirm button B1 has been pressed (step S4). If it is determined that the confirm button B1 is pressed by the input unit 32 with the accounting software tab T1 selected (step S4; YES), the record of the first journal entry rule file 351 with the content input from the accounting software tab T1. No. 1 record is updated (step S5), and the process returns to step S3.

  On the other hand, if it is determined that the input from the accounting software tab T1 has not been made (step S3; NO), or the confirmation button B1 has not been pressed by the input unit 32 with the accounting software tab T1 selected. If it is determined (step S4; NO), the process proceeds to step S6.

  In step S6, it is determined whether or not input from the sales target tab T2 of the sales journal rule setting screen 341 has been performed by the input unit 32 (step S6). Specifically, it is determined whether or not an input has been made from the input field 341b displayed when the sales target tab T2 is selected by the input unit 32. When it is determined that the input from the sales target tab T2 is performed by the input unit 32 (step S6; YES), the sales target tab T2 is selected (the input field of the sales target journal entry rule is displayed). Then, it is determined whether or not the confirmation button B1 is pressed by the input unit 32 (step S7). If it is determined that the confirmation button B1 is pressed by the input unit 32 with the sales target tab T2 selected (step S7; YES), the first journal entry rule file 351 is based on the contents input from the sales target tab T2. Record No. Records 2 to 5 are updated (step S8), and the process returns to step S3.

  On the other hand, when it is determined that the input from the sales target tab T2 is not performed (step S6; NO), or the confirmation button B1 is not pressed by the input unit 32 in a state where the sales target tab T2 is selected. If it is determined (step S7; NO), the process proceeds to step S9.

  In step S9, it is determined whether or not input from the cash sale tab T3 of the sales journal rule setting screen 341 has been performed by the input unit 32 (step S9). Specifically, it is determined whether or not an input has been made from the input field displayed when the cash sale tab T3 is selected by the input unit 32. When it is determined by the input unit 32 that an input from the cash selling tab T3 has been made (step S9; YES), the cash selling tab T3 is selected (a state in which an entry field for a cash selling journal entry rule is displayed). Then, it is determined whether or not the confirmation button B1 is pressed by the input unit 32 (step S10). If it is determined that the confirm button B1 is pressed by the input unit 32 in a state where the cash sale tab T3 is selected (step S10; YES), the first journal entry rule file 351 is based on the contents input from the cash sale tab T3. Record No. Records 6 to 10 are updated (step S11), and the process returns to step S3.

  On the other hand, when it is determined that the input from the cash selling tab T3 has not been performed (step S9; NO), or the confirmation button B1 has not been pressed by the input unit 32 with the cash selling tab T3 selected. If it is determined (step S10; NO), the process proceeds to step S12.

  In step S12, it is determined whether or not input from the credit tab T4 of the sales journal rule setting screen 341 has been performed by the input unit 32 (step S12). Specifically, it is determined whether or not an input has been performed from the input field displayed when the credit tab T4 is selected by the input unit 32. If it is determined that the input from the credit tab T4 has been performed by the input unit 32 (step S12; YES), the input unit is displayed in a state where the credit tab T4 is selected (a state in which an input field for a credit journal rule is displayed). Whether or not the confirmation button B1 has been pressed is determined at 32 (step S13). When it is determined that the confirm button B1 is pressed by the input unit 32 in a state where the credit tab T4 is selected (step S13; YES), the record of the first journal entry rule file 351 is based on the content input from the credit tab T4. No. Records 11 to 15 are updated (step S14), and the process returns to step S3.

  On the other hand, when it is determined that the input from the credit tab T4 has not been performed (step S12; NO), it is determined that the confirmation button B1 has not been pressed by the input unit 32 while the credit tab T4 is selected. If (step S13; NO), the process proceeds to step S15.

  In step S15, it is determined whether or not the input unit 32 has input from the ticket sales tab T5 of the sales journal rule setting screen 341 (step S15). Specifically, it is determined whether or not an input has been made from the input field displayed when the ticket selling tab T5 is selected by the input unit 32. When it is determined by the input unit 32 that an input from the ticket selling tab T5 has been made (step S15; YES), the ticket selling tab T5 is selected (the entry field for the ticket sales journal entry rule is displayed). Then, it is determined whether or not the confirmation button B1 has been pressed by the input unit 32 (step S16). If it is determined that the confirmation button B1 is pressed by the input unit 32 with the ticket sales tab T5 selected (step S16; YES), the first journal entry rule file 351 is based on the contents input from the ticket sales tab T5. Record No. Records 16 to 20 are updated (step S17), and the process returns to step S3.

  On the other hand, when it is determined that the input from the ticket selling tab T5 is not performed (step S15; NO), or the confirmation button B1 is not pressed by the input unit 32 in the state where the ticket selling tab T5 is selected. If it is determined (step S16; NO), the process proceeds to step S18.

  In step S18, it is determined whether or not the input unit 32 has made an input from the rental tab T6 of the sales journal rule setting screen 341 (step S18). Specifically, it is determined whether or not an input has been made from the input field displayed when the sale tab T6 is selected by the input unit 32. If it is determined by the input unit 32 that an input from the lending tab T6 has been made (step S18; YES), the lending tab T6 is selected (the entry field for the lending journal entry rule is displayed). In step S19, it is determined whether or not the confirmation button B1 is pressed by the input unit 32. If it is determined that the confirmation button B1 is pressed by the input unit 32 in a state where the rental tab T6 is selected (step S19; YES), the first journal entry rule file 351 is based on the contents input from the rental tab T6. Record No. Records 21 to 25 are updated (step S20), and the process returns to step S3.

  On the other hand, when it is determined that the input from the rental tab T6 is not performed (step S18; NO), or the confirmation button B1 is not pressed by the input unit 32 in the state where the rental tab T6 is selected. If it is determined (step S19; NO), the process proceeds to step S21.

  In step S21, it is determined whether or not the cancel button B2 is pressed by the input unit 32. If it is determined that the cancel button B2 is not pressed (step S21; NO), the process returns to step S3. If it is determined by the input unit 32 that the cancel button B2 has been pressed (step S21; YES), the journal entry rule setting (sales) process ends.

  FIG. 11 is a flowchart showing journal entry rule setting (purchasing / withdrawal) processing. The journal rule setting (journal / receipt / withdrawal) process is a process for setting the journal rule information for the stock / receipt / withdrawal of the transaction in the second journal rule file 352 according to the operation of the operator. The journal rule setting (journal / payment / withdrawal) process is executed by the cooperation of the CPU 31 and the program of the storage unit 35 when the input unit 32 inputs the journal rule setting instruction for the journal / payment / withdrawal.

  First, the second journal entry rule file 352 is read from the storage unit 35 and expanded in the RAM 33 (step S31), and the deposit / withdrawal entry rule setting screen information is obtained from the screen information file (not shown) stored in the storage unit 35. The deposit / withdrawal journal entry rule setting screen 342 is displayed on the display unit 34 (step S32).

  FIG. 12A shows an example of a deposit / withdrawal journal entry rule setting screen 342. As shown in FIG. 12A, the deposit / withdrawal rule setting screen 342 is provided with a purchase tab T11, a deposit tab T12, a withdrawal tab T13, a change button B11, and a return button B12. In the initial display of the deposit / withdrawal rule setting screen 342, the purchase tab T11 is selected.

  Next, in the deposit / withdrawal rule setting screen 342, it is determined whether or not the purchase tab T11 is selected by the input unit 32 (or initial display) (step S33). If it is determined that the purchase tab T11 is selected (step S33; YES), as shown in FIG. 12A, the contents of the records of the journal rule numbers 001 to 050 in the second journal rule file 352 are displayed in a list (step). S34).

  Next, it is determined whether or not the return button B12 is pressed by the input unit 32 on the deposit / withdrawal journal rule setting screen 342 (step S35). If it is determined by the input unit 32 that the return button B12 has been pressed (step S35; YES), the journal entry rule setting (journal entry / withdrawal) process ends.

  On the other hand, when it is determined that the return button B12 is not pressed by the input unit 32 on the deposit / withdrawal rule setting screen 342 (step S35; NO), the records are listed in the deposit / withdrawal journal rule setting screen 342. Is selected or clicked by the input unit 32, or it is determined whether or not the line selection + change button B11 is pressed (step S36). If it is determined that none of the records displayed in the list has been selected / clicked on by the input unit 32 and the selection / change button B11 has not been pressed (step S36; NO), the process proceeds to step S33. Return.

  On the other hand, when it is determined that one of the records displayed in the list is selected and clicked on by the input unit 32 or the selection and change button B11 is pressed (step S36; YES), FIG. 12B, an entry field for inputting journal rule information to the record in the selected row is displayed on the deposit / withdrawal journal rule setting screen 342 displayed on the display unit 34, and the journal from the input unit 32 is displayed. Input of rule information is accepted (step S37). In step S37, when the journal rule information has already been set for the selected record, the current setting content is displayed in the input field by default. Further, a confirmation button B13 and a cancel button B14 are displayed on the deposit / withdrawal journal rule setting screen 342.

  Next, it is determined whether or not the cancel button B14 is pressed by the input unit 32 (step S38). If it is determined by the input unit 32 that the cancel button B14 has been pressed (step S38; YES), the process returns to step S33. If it is determined by the input unit 32 that the cancel button B14 has not been pressed (step S38; NO), it is determined whether or not the confirm button B13 has been pressed by the input unit 32 (step S39). If it is determined by the input unit 32 that the confirm button B13 has been pressed (step S39; YES), the corresponding record in the second journal entry rule file 352 is updated with the content input from the displayed input field (step S40). The process returns to step S33.

  On the other hand, if it is determined in step S33 that the purchase tab T11 is not selected by the input unit 32 (step S33; NO), it is determined whether or not the deposit tab T12 is selected by the input unit 32 (step S33). S41). If it is determined that the deposit tab T12 has been selected (step S41; YES), the contents of records with journal rule numbers 051 to 100 in the second journal rule file 352 are displayed in a list (step S42).

  Subsequently, the process of step S43-step S48 is performed. Since the process of step S43-step S48 is the same as the process of step S35-step S40, respectively, description is used.

  On the other hand, if it is determined in step S41 that neither the purchase tab T11 nor the deposit tab T12 is selected by the input unit 32 and the withdrawal tab T13 is selected (step S41; NO), the journal entry in the second journal rule file 352 is selected. The contents of the records having the rule numbers 101 to 200 are displayed as a list (step S49).

  Subsequently, the process of step S50-step S55 is performed. Since the process of step S50-step S55 is the same as the process of step S35-step S40, respectively, description is used.

  By the above journal entry rule setting (sales) process and journal entry rule setup (purchase / withdrawal) process, the type of accounting software used by the user in the first journal entry rule file 351 and the second journal entry rule file 352, the daily transaction Journal rules are set.

(Journaling rule barcode book output processing on client PC)
Next, the journal entry rule barcode book output process executed in the client PCs 30A and 30B will be described. Here, the processing of the client PC 30A will be described as a representative, but the same applies to the client PC 30B.

  FIG. 13 is a flowchart showing the journal entry rule barcode book output process. The journal rule bar code book output process is executed by the cooperation of the CPU 31 and the program of the storage unit 35 when the input unit 32 instructs the output of the journal rule bar code book.

Here, the journal rule bar code book 381 that is printed out in the journal rule bar code book output process is such that the store operator registers the purchase / withdrawal transaction in the ECR 20A, 20B (specifically, the user's client PC The journal rule information (may be a part) for each transaction item related to purchase and deposit / withdrawal in the second journal rule file 352 and the identification number of the journal rule information. It is a correspondence table showing the correspondence with journal entry rule numbers.
FIG. 14 is a diagram showing an example of the journal entry rule bar coat book 381. As shown in FIG. 14, the journal rule bar code book 381 is printed with a journal rule number of the transaction, a barcode indicating the journal rule number, and the like in association with the “summary” indicating the transaction item. The operator of each store refers to this journal rule bar code book 381 and inputs a journal rule number corresponding to the generated transaction (purchase or deposit / withdrawal) from the keyboard of the input unit 22 or By scanning the barcode with the barcode scanner and entering the journal rule number corresponding to the barcode, the journal rule number is added to the purchase / withdrawal transaction data, and the purchase / withdrawal transaction is performed by the user. It is possible to register in the ECR 20A or 20B so that it can be entered in the client PC.

  First, the header 381a of the journal entry rule barcode book 381 is printed out on the paper by the printing unit 38 (step S61). Next, one record is read from the second journal entry rule file 352 (step S62), and it is determined whether or not it is the end of the file (step S63). If it is determined that it is not the end of the file (step S63; NO), it is determined whether or not a page break has been performed in the printing unit 38 (step S64). If it is determined that the page break is not performed in the printing unit 38 (step S64; NO), the process proceeds to step S66. If it is determined that a page break has been made in the printing unit 38 (step S64; YES), the header 381a of the journal rule bar code book 381 is printed out on the paper by the printing unit 38 (step S65), and the process proceeds to step S66. Migrate to

  In step S66, a barcode image indicating the “8-digit barcode” of the record read in step S62 is created (step S66). Then, according to the barcode book output item file 353 (see FIG. 7), a value is set in each item of the journal entry rule barcode book 381 and one line is printed by the printing unit 38 (step S67), and the process returns to step S62. If it is determined in step S63 that the file ends (step S63; YES), the journal entry rule barcode book output process ends.

(Registration process in ECR)
Next, registration processing executed in the ECRs 20A and 20B will be described. Here, the processing of the ECR 20A will be described as a representative, but the same applies to the ECR 20B.

FIG. 15 is a flowchart showing the registration process. The registration process is a process of registering sales, purchases, and deposits / withdrawals, and is executed by the cooperation of the CPU 21 and the program of the storage unit 25 in response to an input from the input unit 22 by the operator in the registration mode.
Here, as the operation of the operator, the purchase and deposit / withdrawal transactions are: (1) Reading by bar code scanner of the bar code corresponding to the transaction item to be registered displayed in the journal rule bar code book 381 + amount Registration + depression of cash button or (2) entry of journal entry rule number from keyboard + depression of journal entry button + input of money amount + depression of cash button. Sales registration is as follows: (3) Reading the barcode of a product with a barcode scanner + entering the amount + pressing the payment button according to the payment method (additional sub-function code for ticket button and lending button, credit button) (4) Enter the product code from the keyboard + enter the amount + press the payment button according to the payment method (additional sub-function code and credit for the ticket button and the lending button) The button can be used for further registration by inputting a credit company code.

  First, a system date is acquired from the time measuring unit 37 and stored in the RAM 23 as a slip date = system date (step S71).

  Next, it is determined whether or not the barcode is scanned by the barcode scanner of the input unit 22 (step S72). If it is determined that the barcode is scanned by the barcode scanner of the input unit 22 (step S72; YES), it is determined whether or not the first two digits of the scanned barcode are 29 (step S73). ). Here, the first two digits of the bar code = 29 means that it is not sales registration. If it is determined that the first two digits of the barcode are 29 (step S73; YES), the last three digits of the barcode are stored in the RAM 23 as the journal entry rule number (step S74), and the process proceeds to step S77. On the other hand, if it is determined that the first two digits of the barcode are not 29 (step S73; NO), the process proceeds to step S85.

  On the other hand, if it is determined in step S72 that the barcode scanner of the input unit 22 has not scanned the barcode (that is, input has been performed from the keyboard) (step S72; NO), It is determined whether or not the journal button has been pressed (step S75). If it is determined that the journal button is pressed (step S75; YES), the numerical value input from the keyboard immediately before is stored in the RAM 23 as the journal rule number (step S76), and the process proceeds to step S77.

  In step S77, it is determined whether or not the date button has been pressed from the input unit 22. If it is determined from the input unit 22 that the date button has not been pressed (step S77; NO), the process proceeds to step S81. If it is determined that the date button has been pressed from the input unit 22 (step S77; YES), it is determined whether or not the numerical value input immediately before the date button is pressed is valid as a date (step S78). Whether or not the input numerical value is valid as a date is determined by, for example, whether or not the input numerical value is 8 digits and the system date> the input numerical value. If it is determined that the numerical value input immediately before the date button is pressed is not valid (step S78; NO), an error message is displayed on the display unit 24 (step S79), and the process returns to step S77. If it is determined that the numerical value input immediately before the date button is pressed is valid (step S78; YES), the slip date in the RAM 23 is changed to the numerical value input immediately before (step S80), and the process is step S81. Migrate to

  In step S81, it is determined whether or not the cash button of the input unit 22 is pressed. If it is determined that the cash button is pressed (step S81; YES), the numerical value input immediately before the cash button is pressed is the amount. Is stored in the RAM 23 (step S82). Then, by setting the cash register code, slip date, function code, character, amount, journal entry rule number in a predetermined purchase / withdrawal data format, purchase / withdrawal data D2 is created (step S83). The created purchase / payment / withdrawal data D2 is transmitted to the center server 10 by the communication unit 26 (step S84), and the registration process is terminated.

  FIG. 16 is a diagram illustrating a data configuration example of the purchase / payment / withdrawal data D2. As shown in FIG. 16, the purchase / withdrawal data D2 includes “registration code”, “slip date”, “function code”, “subfunction”, “key character”, “money amount”, “journal rule number”. It consists of data of items. The “registration code” is an identification code for identifying the ECR 20A, and is stored in the storage unit 25 of the ECR 20A. “Function code” is a function code (fixed at 0901 here) corresponding to the journal button. “Subfunction” is not entered here. The “key character” is a character corresponding to the journal button (here “journal”). The “slip date”, “amount”, and “journal rule number” are stored in the RAM 23.

  On the other hand, when it is determined in step S75 that the journal entry button of the input unit 22 has not been pressed (step S75; NO), the payment button (cash button, ticket button, loan button, credit button) of the input unit 22 is pressed. It is determined whether or not it has been done (step S85). If it is determined that the payment button of the input unit 22 has been pressed (step S85; YES), the numerical value input immediately before the payment button is stored as an amount in the RAM 23 (step S86). When a ticket button or a lending button is pressed as a payment button, input of a subfunction code is accepted. When the credit button is pressed, the input of the credit company code is accepted. In addition, when the service fee is included in the sales, the input of the service fee is accepted by pressing the amount + service fee button. Then, the sales data D1 is created by setting the cash register date, slip date, function code, sub-function code, character, amount, card company code, service fee in a predetermined sales data format (step S87), The generated sales data D1 is transmitted to the center server 10 by the communication unit 26 (step S88), and the registration process ends.

  FIG. 17 is a diagram illustrating a data configuration example of the sales data D1. As shown in FIG. 17, the sales data D1 includes “registration code”, “slip date”, “function code”, “subfunction”, “key character”, “money”, “card company code”, “service fee”. ”Item data. The “registration code” is an identification code for identifying the ECR 20A, and is stored in the storage unit 25 of the ECR 20A. “Function code” is a function code corresponding to the type of the pressed payment button. “Sub-function code”, “card company code”, and “service fee” are values input from the input unit 22. The “key character” is a character corresponding to the pressed payment button. The “slip date” and “amount” are those stored in the RAM 23.

  On the other hand, if it is determined in step S85 that the payment button has not been pressed (step S85; NO), the registration process ends.

(Data transfer in the center server 10)
In the center server 10, when the sales data D1 or purchase / payment / withdrawal data D2 transmitted from the ECRs 20A and 20B is received by the communication unit 16, the CPU 11 and the program stored in the storage unit cooperate with each other. Cash register authentication processing, data storage processing, and data transfer processing are executed.
In the cash register authentication process, cash register authentication is performed based on the cash register code included in the received sales data D1 or purchase / payment / withdrawal data D2. Specifically, it is determined whether or not a registration code that matches the registration code included in the received sales data D1 or purchase / payment / withdrawal data D2 exists in the registration authentication master 151 stored in the storage unit 15. Is done. When it is determined that the registration code matching the registration code included in the received sales data D1 or purchase / payment / withdrawal data D2 exists in the registration authentication master 151, it is determined that the registration authentication is OK. If it is determined that there is no register code in the register authentication master 151 that matches the register code included in the received sales data D1 or purchase / payment / withdrawal data D2, the register authentication is determined to be NG.
In the cash register authentication process, if it is determined that the cash register authentication is OK, a data storage process is executed. That is, a company code corresponding to the registration code included in the received sales data D1 or purchase / payment / withdrawal data D2 is acquired from the registration authentication master 151, and a record having a company code that matches the acquired company code is obtained. Retrieved from the destination master 152. Then, the received sales data D1 and purchase / payment / withdrawal data D2 are stored in the output folder path of the retrieved record (the distribution folder path for each company).
Sales data D1 and purchase / withdrawal data D2 data stored in the distribution folder are obtained by a data transfer process performed based on a request from the client PC of the company that is performed every predetermined time (or every predetermined time). The data is transferred to the requesting client PC by the communication unit 16. The transferred sales data D1 and purchase / payment / withdrawal data D2 are deleted from the distribution folder.
In the client PCs 30 </ b> A and 30 </ b> B, sales data D <b> 1 and purchase / payment / withdrawal data D <b> 2 received from the center server 10 by the communication unit 36 are stored in the storage unit 35.

(Journal data creation process on client PC)
Next, journal data creation processing executed in the client PCs 30A and 30B will be described. Here, the processing of the client PC 30A will be described as a representative, but the same applies to the client PC 30B.

  FIG. 18 is a flowchart showing journal data creation processing. The journal data creation process is executed in cooperation with the CPU 31 and the program in the storage unit 35 when a journal data creation instruction is input from the input unit 32.

  First, the slip No., which is a variable. Is set to 0 (step S91). Next, the first journal rule file 351 and the second journal rule file 352 are read from the storage unit 35 and expanded in the RAM 33 (step S92).

  Next, purchase / payment / withdrawal data conversion processing is executed (step S93). FIG. 19 shows a flowchart of purchase / payment / withdrawal data conversion processing. The purchase / payment / withdrawal data conversion processing is executed in cooperation with the CPU 31 and the program of the storage unit 35.

  In the purchase / payment / withdrawal data conversion process, first, purchase / payment / withdrawal data D2 for one case is read from the storage unit 35 (step S101). As a result of the reading, when it is determined that the purchase / payment / withdrawal data D2 has been read, that is, the reading of all the purchase / payment / withdrawal data D2 stored in the storage unit 35 has not been completed ( Step S102; NO), it is determined whether or not the function code = 0901 of the read purchase / payment / withdrawal data D2 (Step S103). If it is determined that the function code of the read purchase / deposit data D2 is not 0901 (step S103; YES), the process returns to step S101.

  On the other hand, if it is determined that the function code of the read purchase / withdrawal data D2 = 0901 (step S103; YES), the position of the pointer is set at the head of the second journal entry rule file 352 (step S104). ), One record where the pointer is located is read from the second journal entry rule file 352 (step S105). As a result of the reading, if it is determined that the pointer is not the end of the second journal rule file 352 but the record has been read (step S106; NO), the “journal rule number” of the purchase / withdrawal data D2 and the second It is determined whether or not the “journal rule number” of the record read from the journal rule file 352 matches (step S107). If it is determined that the “journal rule number” in the purchase / withdrawal data D2 does not match the “journal rule number” of the record read from the second journal rule file 352 (step S107; NO), Returning to step S105, the next record is read.

  On the other hand, if it is determined that the “journal rule number” of the purchase / withdrawal data D2 matches the “journal rule number” of the record read from the second journal rule file 352 (step S107; YES), the variable Slip No. Is incremented by 1 (step S108). Then, journal data is created based on the purchase / withdrawal data D2 and the second journal rule file 352, and is output to the journal data file 355 of the storage unit 35 (step S109). Then, the process returns to step S101.

  FIG. 20 is a diagram illustrating a data storage example of the journal data file 355. As shown in FIG. 20, the journal data file 355 includes “registration code”, “slip date”, “slip number”, “description”, “spot transaction category”, “debit account code”, “debit sub-account code”. ”,“ Debit Account Name ”,“ Debit Sub-Account Name ”,“ Debit Amount ”,“ Debit Tax Classification ”,“ Credit Account Code ”,“ Credit Sub-Account Code ”,“ Credit Account Name ”,“ Credit ” Journal data including items of “subject name”, “credit amount”, “credit tax classification”, “journal rule number”, and “error flag” is stored.

  In step S109 of FIG. 19, specifically, the “amount” of the purchase / withdrawal data D2 is set to “debit amount” and “credit amount” of the journal data. In addition, the “registration code”, “slip date”, and “journal rule number” of the purchase / withdrawal data D2 are set in the same item of the journal data. The value of (variable) is set in the “slip number” of the journal data. In addition, in the record read from the second journal entry rule file 352 in step S105, “Summary”, “Spot transaction classification”, “Debit account code”, “Debit sub-account code”, “Debit account name”, “ "Debit sub item name", "Debit tax classification", "Credit account code", "Credit sub item code", "Credit account name", "Credit sub item name", "Credit tax classification" are the same in the journal data Set to item. The created journal data is output to the journal data file 355.

  On the other hand, when it is determined in step S106 that the end of the second journal entry rule file 352 is reached (step S106; YES), an error message is displayed on the display unit 34 (step S110). In addition, slip No. (Variable) is incremented by 1 (step S111), and journal data including an error flag is created based on the purchase / payment / withdrawal data D2, and is output to the journal data file 355 of the storage unit 35 (step S112). Then, the process returns to step S101. In step S112, specifically, the “amount” of the purchase / payment / withdrawal data D2 is set to “debit amount” and “credit amount” of the journal data. In addition, the “registration code”, “slip date”, and “journal rule number” of the purchase / withdrawal data D2 are set in the same item of the journal data. The value of (variable) is set in the “slip number” of the journal data. Furthermore, 1 is set in the “error flag” of the journal data. The created journal data is output to the journal data file 355.

  The processing of step S103 to step S111 for all purchase / payment / withdrawal data D2 stored in the storage unit 35 is completed, and in step S102, all purchase / payment / withdrawal data stored in the storage unit 35. If it is determined that the reading of D2 has ended (step S102; YES), the purchase / payment / withdrawal data D2 stored in the storage unit 35 is deleted (step S113), and the purchase / payment / withdrawal data conversion process is performed. The process ends, and the process proceeds to step S94 in FIG.

  In step S94 in FIG. 18, sales data conversion processing is executed. FIG. 21 is a flowchart showing sales data conversion processing. The sales data conversion process is executed in cooperation with the CPU 31 and the program in the storage unit 35.

  In the sales data conversion process, first, sales data D1 for one case is read from the storage unit 35 (step S201). As a result of the reading, if it is determined that the sales data D1 has been read, that is, the reading of all the sales data D1 stored in the storage unit 35 has not yet been completed (step S202; NO), the reading is performed. It is determined whether or not the function code = 0001 (cash) of the sales data D1 is received (step S203). If it is determined that the function code of the read sales data is 0001 (step S203; YES), the cash selling process shown in FIG. 22 is executed (step S204).

If it is determined that the function code = 0004 (credit) instead of the function code = 0001 of the read sales data D1 (step S203; NO) (step S205; YES), the credit processing shown in FIG. 23 is executed. (Step S206).
If it is determined that the function code of the sales data D1 read out is not 0004 (step S205; NO) and the function code is 0002 (ticket) (step S207; YES), the ticket selling process shown in FIG. It is executed (step S208).
If it is determined that the function code of the read sales data D1 is not 0002 (step S207; NO) but the function code is 0003 (lending) (step S209; YES), the lending process shown in FIG. It is executed (step S210).
If it is determined that the function code of the read sales data D1 is not 0003 (step S209; NO), the process returns to step S201.

  The processing of step S203 to step S210 for all sales data D1 stored in the storage unit 35 is completed, and in step S202, it is determined that reading of all sales data D1 stored in the storage unit 35 has been completed. When done (step S202; YES), the sales data D1 stored in the storage unit 35 is deleted (step S211), and the sales data conversion process ends.

  Hereinafter, a cash selling process, a credit process, a ticket selling process, and a rental selling process executed as a subroutine of the sales data conversion process will be described.

First, the cash selling process will be described.
FIG. 22 is a flowchart showing the cash selling process executed in step S204 of FIG. The cash selling process is executed in cooperation with the CPU 31 and the program in the storage unit 35.
In the cash selling process, first, it is determined whether or not “service fee” of the sales data D1 read in step S201 = 0 (step S301). If it is determined that “service fee” = 0 (step S301; YES), the process proceeds to step S303. If it is determined that “service fee” = 0 is not satisfied (step S301; NO), the value of the amount-service fee is set in the “money amount” of the read sales data D1 (step S302), and the processing is step. The process proceeds to S303.

  In step S303, each item of the record “Record No.” = 02 (sales) in the first journal entry rule file 351 (“account item code”, “auxiliary item code”, “account item name”, “subject item name”). ”And“ Tax Classification ”items) are set in the item of the same name in the credit of the journal data (step S303).

  Next, each item of the record “Record No.” = 06 (cash) in the first journal entry rule file 351 (“account item code”, “auxiliary item code”, “account item name”, “auxiliary item name”, “ The value of the “tax category” item is set to the item of the same name as the debit of the journal data (step S304).

  Next, slip No., which is a variable. Is incremented by 1 (step S305), the “amount” of the sales data D1 read out in step S201 of FIG. 21 is set in the “debit amount” and “credit amount” of the journal data, and the “registration code” of the sales data D1. ”And“ slip date ”are set in the same item of the journal data. The value of (variable) is set in the “slip number” of the journal data. In addition, “sales” is set in the “summary” of the journal data. Then, the journal data in which the value of each item is set is output to the journal data file 355 (step S306).

  Next, it is determined whether or not “service fee” of the sales data D1 read out in step S201 = 0 (step S307). If it is determined that the “service fee” of the sales data read in step S201 = 0 (step S307; YES), the cash selling process ends, and the process returns to step S201 in FIG.

  On the other hand, if it is determined that “service fee” of the sales data D1 read in step S201 is not 0 (step S307; NO), “record No.” = 03 (service sales) in the first journal entry rule file 351. ) Record items (“Account Code”, “Sub-subject Code”, “Account Name”, “Sub-subject Name”, “Tax Classification”) are set to the item with the same name in the journal data credit (Step S308).

  Next, each item of the record “Record No.” = 06 (cash) in the first journal entry rule file 351 (“account item code”, “auxiliary item code”, “account item name”, “auxiliary item name”, “ The value of “tax classification”) is set in the item of the same name as the debit of the journal data (step S309).

  Next, slip No., which is a variable. Is incremented by 1 (step S310). Then, the “service fee” of the sales data D1 read out in step S201 in FIG. 21 is set to “debit amount” and “credit amount” of the journal data, and “registration code” and “slip date” of the sales data D1. Is set in the same item of the journal data, and the slip No. The value of (variable) is set to “slip number” of the journal data, and “sales” is set to “summary” of the journal data. Then, journal data in which the value of each item is set is output to the journal data file 355 (step S311), the cash selling process is terminated, and the process returns to step S201 in FIG.

Next, credit processing will be described.
FIG. 23 is a flowchart showing the credit process executed in step S206 of FIG. The credit process is executed in cooperation with the CPU 31 and the program in the storage unit 35.
In the credit processing, first, the record No. of the first journal entry rule file 351 is recorded. The position of the pointer is set to = 10 (step S401).

  Next, the next one of the first journal entry rule file 351 is read (step S402), and the record No. of the read record is recorded. It is determined whether or not> 15 (step S403). Record No. of the read record If it is determined that it is not> 15 (step S403; NO), the “card company code” of the record read to the RAM 33 in step 201 of FIG. 21 is replaced with the “card company code” of the record read in step S402. ”Is determined (step S404). If it is determined that the “card company codes” of both records do not match (step S404; NO), the process returns to step S402. If it is determined that the “card company codes” of both records match (step S404; YES), a data conversion process is executed (step S405), and the credit process ends.

FIG. 24 is a flowchart showing the data conversion process executed in step S405 of FIG. The data conversion process is executed in cooperation with the CPU 31 and the program in the storage unit 35.
In the data conversion process, first, it is determined whether or not “service fee” of the sales data D1 read in step S201 of FIG. 21 is 0 (step S501). If it is determined that “service fee” = 0 (step S501; YES), the process proceeds to step S503. If it is determined that “service fee” = 0 is not satisfied (step S501; NO), the value of the amount-service fee is set in the “amount” of the read sales data D1 (step S502), and the processing is step. The process proceeds to S503.

  In step S503, each item of the record “record No.” = 02 (sales) in the first journal entry rule file 351 (“account item code”, “auxiliary item code”, “account item name”, “subject item name”). ”And“ Tax Classification ”items) are set in the item of the same name of the credit of the journal data (step S503).

  Next, each item of the record currently read from the first journal entry rule file 351 (current record) (“account item code”, “auxiliary item code”, “account item name”, “auxiliary item name”, “tax” The value of the “item” item is set to the item of the same name as the debit of the journal data (step S504).

  Next, slip no. (Variable) is incremented by 1 (step S505), and the “amount” of the sales data D1 read out in step S201 of FIG. 21 is set to “debit amount” and “credit amount” of the journal data, and the sales data D1 “Registration code” and “slip date” are set in the same item of the journal data, and slip number. The value of (variable) is set to “slip number” of the journal data, and “sales” is set to “summary” of the journal data. Then, journal data in which the value of each item is set is output to the journal data file 355 (step S506).

  Next, it is determined whether or not “service fee” of the sales data D1 read out in step S201 = 0 (step S507). If it is determined that “service fee” of the sales data D1 read in step S201 is 0 (step S507; YES), the data conversion process ends, and the process returns to step S201 in FIG.

  On the other hand, if it is determined that “service fee” of the sales data D1 read in step S201 is not 0 (step S507; NO), “record No.” = 03 (service sales) in the first journal entry rule file 351. ) Record items (“Account code”, “Sub-subject code”, “Account name”, “Sub-subject name”, “Tax classification” items) are the same name items in the credit of the journal data. It is set (step S508).

  Next, the value of each item ("Account item code", "Sub-subject code", "Account name", "Sub-subject name", "Tax category" items) of the current record in the first journal entry rule file 351) is the journal entry. It is set to the item of the same name in the data debit (step S509).

  Next, slip No., which is a variable. Is incremented by 1 (step S510), the “service fee” of the sales data D1 read out in step S201 of FIG. 21 is set in the “debit amount” and “credit amount” of the journal data, and the “registration” of the sales data D1. “Code” and “slip date” are set in the same item of the journal data. The value of (variable) is set to “slip number” of the journal data, and “sales” is set to “summary” of the journal data. Then, the journal data in which the value of each item is set is output to the journal data file 355 (step S512), the data conversion process ends, and the process returns to step S201 in FIG.

  On the other hand, in step S403 of FIG. 23, the record No. of the record read from the first journal entry rule file 351 is recorded. If it is determined that> 15 (step S403; YES), an error message is displayed on the display unit 34 (step S406). In addition, slip No. The (variable) is incremented by 1 (step S407), and the “amount” of the sales data D1 read out in step S201 of FIG. 21 is set in the “debit amount” and “credit amount” of the journal data. Further, the “registration code” and “slip date” of the sales data D1 are set in the same item of the journal data, and the slip number. The value of (variable) is set in the “slip number” of the journal data. Furthermore, 1 is set in the “error flag” of the journal data. Then, the created journal data is output to the journal data file 355 (step S408), the credit process is terminated, and the process proceeds to step S201 in FIG.

Next, the ticket selling process will be described.
FIG. 25 is a flowchart showing the ticket selling process executed in step S208 of FIG. The ticket selling process is executed in cooperation with the CPU 31 and the program in the storage unit 35.
In the ticket selling process, first, the record number of the first journal entry rule file 351 expanded in the memory is recorded. The position of the pointer is set to = 15 (step S601).

  Next, the next one of the first journal entry rule file 351 is read (step S602), and the record No. of the read record is recorded. It is determined whether or not> 20 (step S603). Record No. of the read record If it is determined that it is not> 20 (step S603; NO), the “subfunction code” of the record read to the RAM 33 in step 201 of FIG. 21 is replaced with the “subfunction code” of the record read in step S602. ”Is determined (step S604). If it is determined that the “sub-function codes” of both records do not match (step S604; NO), the process returns to step S602. If it is determined that the “sub-function codes” of both records match (step S604; YES), a data conversion process is executed (step S605), and the ticket selling process ends. The data conversion process is the same as that described with reference to FIG.

  On the other hand, in step S603 of FIG. 25, the record No. of the record read from the first journal entry rule file 351 is recorded. If it is determined that> 20 (step S603; YES), an error message is displayed on the display unit 34 (step S606). In addition, slip No. The (variable) is incremented by 1 (step S607), and the “amount” of the sales data D1 read out in step S201 of FIG. 21 is set in the “debit amount” and “credit amount” of the journal data. Further, the “registration code” and “slip date” of the sales data D1 are set in the same item of the journal data, and the slip number. The value of (variable) is set in the “slip number” of the journal data. Furthermore, 1 is set in the “error flag” of the journal data. The created journal data is output to the journal data file 355 (step S608), the ticket selling process ends, and the process proceeds to step S201 in FIG.

Next, the lending process will be described.
FIG. 26 is a flowchart showing the lending process executed in step S210 of FIG. The lending process is executed in cooperation with the CPU 31 and the program of the storage unit 35.
In the lending process, first, the record No. of the first journal entry rule file 351 developed in the memory is recorded. The position of the pointer is set to = 20 (step S701).

  Next, the next one reading of the first journal entry rule file 351 is performed (step S702), and it is determined whether it is the end of the file (step S703). If it is determined that it is not the end of the file (step S703; NO), the “subfunction code” of the record read to the RAM 33 in step 201 of FIG. 21 is replaced with the “subfunction code” of the record read in step S702. It is determined whether or not it matches the “code” (step S704). If it is determined that the “subfunction codes” of both records do not match (step S704; NO), the process returns to step S702. If it is determined that the “subfunction codes” of both records match (step S704; YES), the data conversion process is executed (step S705), and the lending process ends. The data conversion process is the same as that described with reference to FIG.

  On the other hand, if it is determined in step S703 of FIG. 26 that the first journal rule file 351 is at the end of the file (step S703; YES), an error message is displayed on the display unit 34 (step S706). In addition, slip No. The (variable) is incremented by 1 (step S707), and the “amount” of the sales data D1 read out in step S201 of FIG. 21 is set in the “debit amount” and “credit amount” of the journal data. Further, the “registration code” and “slip date” of the sales data D1 are set in the same item of the journal data, and the slip number. The value of (variable) is set in the “slip number” of the journal data. Furthermore, 1 is set in the “error flag” of the journal data. The created journal data is output to the journal data file 355 (step S708), and the process proceeds to step S201 in FIG.

  When the sales data conversion process ends, the journal data creation process shown in FIG. 18 ends.

(Journal data editing process on client PC)
Next, the journal data editing process executed in the client PCs 30A and 30B will be described. The journal data editing process is a process for editing the journal data output by the journal data creation process based on the operation of the operator. Here, the processing of the client PC 30A will be described as a representative, but the same applies to the client PC 30B.

  FIG. 27 is a flowchart showing the journal data editing process. The journal data editing process is executed in cooperation with the CPU 31 and the program of the storage unit 35 when journal data editing is instructed by the input unit 32.

  First, the journal data file 355 is read from the storage unit 35 and expanded in the RAM 33 (step S801), and journal data editing screen information is read from a screen information file (not shown) stored in the storage unit 35. The journal data editing screen 343 is displayed on the display unit 34 (step S802).

  FIG. 28A is a diagram showing an example of the journal data editing screen 343. As shown in FIG. 28A, on the journal data editing screen 343, the type of journal data to be edited is selected from among spot transactions, automatic journal errors (journal data in which the journal data creation process has failed), and all journal data. There are provided a selection field 343a, a list display field 343b for displaying a list of journal data of the type selected as the editing target, a change button B21, a return button B22, and the like.

  Next, it is determined whether or not a spot transaction has been selected by the input unit 32 from the selection field 343a of the journal data editing screen 343 (step S803). When it is determined that the spot transaction is selected by the input unit 32 (step S803; YES), as shown in FIG. 28A, a record of spot transaction classification = 1 is extracted from the journal data file 355, and the list is displayed in the list display field 343b. It is displayed (step S804).

  Next, in the journal data editing screen 343, it is determined whether or not the return button B22 is pressed by the input unit 32 (step S805). If it is determined by the input unit 32 that the return button B22 has been pressed (step S805; YES), the journal data editing process ends.

  On the other hand, when it is determined on the journal data editing screen 343 that the return button B22 is not pressed by the input unit 32 (step S805; NO), any one of the journal data displayed as a list on the journal data editing screen 343 is selected. Is selected or clicked by the input unit 32, or it is determined whether or not the line selection + change button B21 is pressed (step S806). It is determined that none of the journal data displayed in the list has been selected / clicked on by the input unit 32 and the selection / change button B21 has not been pressed (step S806; NO), and the process proceeds to step S803. Return.

  On the other hand, if it is determined that one of the journal data displayed in the list is selected and clicked on by the input unit 32 or the selection and change button B21 is pressed (step S806; YES). As shown in FIG. 28B, the journal data editing screen 343 displayed on the display unit 34 displays an edit field 343c for editing the journal data of the selected line, and an edit input from the input unit 32 is accepted. (Step S807). In step S807, a confirmation button B23 and a cancel button B24 are displayed on the journal data editing screen 343.

  Next, it is determined whether or not the cancel button B24 is pressed by the input unit 32 (step S808). If it is determined by the input unit 32 that the cancel button B24 has been pressed (step 808; YES), the process returns to step S803. If it is determined by the input unit 32 that the cancel button B24 has not been pressed (step 808; NO), it is determined whether or not the confirm button B23 has been pressed by the input unit 32 (step S809). If it is determined by the input unit 32 that the confirm button B23 has been pressed (step S809; YES), the journal data file 355 is updated with the contents input from the displayed edit field 343c (step S810), and the process proceeds to step S803. Return to.

  If it is determined on the journal data editing screen 343 that the return button B22 has been pressed by the input unit 32 (step S805; YES), the journal data editing process ends.

  On the other hand, if it is determined in step S803 that the spot transaction is not selected by the input unit 32 (step S803; NO), it is determined whether or not an automatic journal error is selected by the input unit 32 (step S811). . If it is determined by the input unit 32 that an automatic journal error has been selected (step S811; YES), journal data with an error flag = 1 is extracted from the journal data file 355 and displayed as a list in the list display field 343b (step S812). ).

  Next, the processes in steps S813 to S818 are executed. Since the process of step S813-step S818 is the same as the process of step S804-step S810, respectively, description is used.

  On the other hand, if it is determined in step S811 that neither spot transaction nor automatic journal error has been selected by the input unit 32, that is, all journal data has been selected (step S811; NO), the data is stored in the journal data file 355. The contents of all the journal data are displayed as a list (step S819).

  Subsequently, the process of step S820-step S825 is performed. Since the process of step S820 to step S825 is the same as the process of step S804 to step S810, respectively, description will be incorporated.

  By editing the journal data described above, the operator can efficiently add the trading partner to the spot transaction journal data for which the trading partner is not specified, or edit the journal data that caused an error in the journal data creation process. It becomes possible to correct the data.

(Format conversion processing on client PC)
Next, a format conversion process executed in the client PCs 30A and 30B will be described. The format conversion process is a process of converting journal data into a format that can be used by accounting software. Here, the processing of the client PC 30A will be described as a representative, but the same applies to the client PC 30B.

  FIG. 29 is a flowchart showing the format conversion process. The format conversion process is executed in cooperation with the CPU 31 and the program in the storage unit 35 when an instruction to execute format conversion from the input unit 32 to the accounting software is input.

  First, the record No. = 1 record in the first journal entry rule file 351 is read (step S901). Next, an input screen (not shown) for inputting the output file name is displayed on the display unit 34, and input of the output file name is accepted (step S902). The input screen displayed in step S902 displays a cancel button for instructing cancellation of format conversion and an OK button for instructing execution of format conversion using the input output file name. .

  When the cancel button is pressed by the input unit 32 (step S903; YES), the format conversion process ends. When the OK button is pressed by the input unit 32 (step S904; YES), it is determined whether the accounting software category of the record read in step S901 is 1, and it is determined that the accounting software category = 1. If so (step S905; YES), the data conversion process for the accounting software 1 is executed (step S906), and the format conversion process ends. Here, the data conversion process for the accounting software 1 is a process for converting the journal data into a data format used by the accounting software 1. For example, processing that extracts only the items required by accounting software 1 from journal data, or if the number of digits in each item differs between journal data and accounting software 1, the number of digits is converted according to accounting software 1. Processing is performed.

  On the other hand, if it is determined that the accounting software category = 2 of the record read in step S901 is not accounting software category = 1 (step S905; NO, step S907; YES), data conversion for accounting software 2 is performed. The process is executed (step S908), and the format conversion process ends. Here, the data conversion process for the accounting software 2 is a process for converting the journal data into a data format used by the accounting software 2. For example, processing that extracts only necessary items from the journal data in the accounting software 2, or if the number of digits of each item differs between the journal data and the data format of the accounting software 2, the number of digits is converted according to the accounting software 2. Processing is performed.

  On the other hand, if it is determined that the accounting software category of the record read in step S901 is not 2 but accounting software category = 3 (step S907; NO, step S909; YES), data conversion for accounting software 3 is performed. The process is executed (step S910), and the format conversion process ends. Here, the data conversion process for the accounting software 3 is a process for converting the journal data into a data format used by the accounting software 3. For example, processing that extracts only necessary items from the journal data in the accounting software 3, or if the number of digits of each item differs between the journal data and the data format of the accounting software 3, the number of digits is converted according to the accounting software 3. Processing is performed.

  Since the journal data can be converted into a data format that can be used by the accounting software by the above format conversion process, the journal data that is journalized from the journal / receipt / withdrawal data and sales data transmitted from the ECR 20A can be taken into the accounting software. It becomes possible.

  As described above, according to the client PCs 30A and 30B of the present embodiment, the CPU 31 uses the journal entry rule information of the transaction items relating to the purchase and deposit / withdrawal entered from the deposit / withdrawal journal entry rule setting screen 342 as the journal entry rule number. Correspondingly stored in the second journal rule file 352, and when the input unit 32 instructs the output of the journal rule bar code book 381, the correspondence between the journal rule number in the second journal rule file 352 and the transaction item Is output by the printing unit 38. When the communication unit 36 receives purchase / payment / withdrawal data D2 including a journal rule number and an amount transmitted from the ECR of the store managed by the user, the CPU 31 makes the journal entry included in the purchase / payment / withdrawal data D2. Journal rule information corresponding to the rule number is read from the second journal rule file 352, and journal data in which the amount of the purchase / withdrawal data D2 is journalized according to the read journal rule information is created.

  Accordingly, in the store, the operator can register purchase and deposit / withdrawal transactions by ECR while referring to the journal rule bar code book indicating the correspondence between the journal rule number and the transaction item. In addition, transactions registered by ECR can be automatically journalized by the user's client PC.

Since the created journal data can be edited, convenience is improved.
In particular, the journal data editing screen 343 is used to selectively input journal data including spot transaction classifications, journal data in which an error has occurred when the journal data is created, or journal data to be extracted from all journal data. The CPU 31 extracts the journal data selected from the selection field from the journal data file 355, displays the list on the display unit 34, and displays the list to be edited by the input unit 32 from the displayed list. When the journal data is selected, input of edit contents of each item of the selected journal data is accepted from the journal data editing screen 343. Therefore, the user inputs the journal data of the spot transaction that needs to be edited or the journal data having an error. Can be easily grasped and edited efficiently.

  Further, the deposit / withdrawal journal rule setting screen 342 is configured so that the type of accounting software used in the client PC can be set, and the CPU 31 sets the created journal data in the data format of the accounting software in which it is set. Therefore, the journal data can be easily taken into the accounting software.

  In addition, the description content in the said embodiment is a suitable example of the sales data processing system 1 which concerns on this invention, and is not limited to this.

  For example, in the above embodiment, the journal rule bar code book 381 has been described as being printed out by the printing unit 38 of the client PCs 30A and 30B. However, for example, the communication unit 36 of the client PCs 30A and 30B passes through the center server 10. The electronic data of the journal entry rule barcode book 381 is transmitted (output) to the ECR 20A, 20B of the store managed by the user, and the electronic data of the journal entry rule barcode book 381 is stored in the storage unit 25 of the ECR 20A, 20B. The barcode book 381 may be displayed on the display unit 24 of the ECR 20A, 20B, or the journal entry rule barcode book 381 may be printed on the printing unit 28 of the ECR 20A, 20B. Alternatively, the electronic data of the journal entry rule barcode book 381 may be transmitted (output) to a portable terminal used for store operations via the Internet or a mobile communication network, and displayed on the display unit.

  Further, the data and file configurations described in the above embodiments are merely examples, and the present invention is not limited to these.

  In addition, the detailed configuration and detailed operation of each device constituting the sales data processing system 1 can be appropriately changed without departing from the spirit of the invention.

1 Sales data processing system
10 Center server 11 CPU
12 Input unit 13 RAM
14 Display unit 15 Storage unit 151 Cash register authentication master 152 Destination master 153 PC authentication master 16 Communication unit 17 Timing unit 18 Printing unit 19 Bus 20A ECR
20B ECR
21 CPU
22 Input unit 23 RAM
24 Display unit 25 Storage unit 26 Communication unit 27 Drawer 28 Print unit 29 Timekeeping unit 29a Bus 30A Client PC
30B client PC
31 CPU
32 Input unit 33 RAM
34 Display unit 35 Storage unit 351 First journal rule file 352 Second journal rule file 353 Barcode book output item file 354 Classification table file 355 Journal data file 36 Communication unit 37 Timing unit 38 Printing unit 39 Bus

Claims (6)

A terminal device connected to a server device that receives data transmitted from a data processing device,
Setting means for setting journal entry rule information of transactions registered in the data processing device and identification information corresponding thereto,
Storage means for storing the transaction rule rule information set by the setting means and the identification information in association with each other;
An output means for outputting a correspondence table indicating a correspondence relationship between the journal entry rule information of the transaction and the identification information;
Receiving means for receiving the transaction identification information and the transaction amount transmitted from the data processing device to the server device and transferred from the server device when a transaction occurs;
Creating means for reading the transaction journal rule information corresponding to the identification information received by the receiving means from the storage means, and creating journal data in which the transaction amount is journalized according to the read journal rule information; ,
A terminal device comprising: The output means prints out the correspondence table indicating a correspondence relationship between the journal entry rule information of the transaction and the identification information,
The data processing device inputs the identification information corresponding to the generated transaction based on the printed correspondence table to the server device by inputting the identification information of the transaction and the amount of the transaction. The terminal device according to claim 1 which transmits. A journal data storing means for storing the journal data created prior to reporting,
It is displayed on the display unit an operation screen for inputting the editing content of journal data created before reporting, updating the journal data stored in the journal data storage means based on the editing content input from the operation screen Editing means to
The terminal device according to claim 1, comprising: The operation screen has a selection field for selecting and inputting the type of journal data,
The editing unit extracts the journal data selected from the selection field by the operation unit from the journal data stored in the journal data storage unit, displays the list on the operation screen, and performs the operation from the displayed list. 4. The terminal device according to claim 3, wherein when the journal data to be edited is selected by the means, an input field for inputting edit contents of each item of the selected journal data is displayed on the operation screen. The setting means is configured to set the accounting software of the type,
Terminal device according to any one of claims 1 to 4 comprising a format converting means for converting the journal data to which the created journal data of the set accounting software data format. A computer of a terminal device connected to a server device that receives data transmitted from a data processing device ,
Setting means for setting journal entry rule information of transactions registered in the data processing device and identification information corresponding thereto,
Storage means for storing the transaction rule rule information set by the setting means and the identification information in association with each other;
An output means for outputting a correspondence table indicating a correspondence relationship between the journal entry rule information of the transaction and the identification information;
Receiving means for receiving transaction identification information and transaction amount transmitted from the data processing device to the server device and transferred from the server device when a transaction occurs;
Creating means for reading the transaction journal rule information corresponding to the identification information received by the receiving means from the storage means, and creating journal data in which the amount of the transaction is journalized according to the read journal rule information;
Program to function as.

Images