Sales management system and sales management program
The sales management system addresses inefficiencies in data correction and deletion by maintaining a revision history and ensuring compliant journal entry processing with accounting software, enhancing data management efficiency and compliance with the Electronic Bookkeeping Act.
Patent Information
- Application Number
- JP2023048056
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-03-24
- Publication Date
- 2024-11-21
- Estimated Expiration
- 2043-03-24
AI Technical Summary
Existing sales management systems fail to efficiently manage data corrections and deletions while maintaining a revision history, leading to inefficiencies and non-compliance with the Electronic Bookkeeping Act, particularly in journal entry processing between sales and accounting systems.
A sales management system and program that includes a storage device for billing management databases, with modification history information, and processing means for writing, modifying, and deleting data while recording revision history, ensuring compliance with the Electronic Bookkeeping Act by prohibiting unauthorized changes and enabling consistent journal entry with accounting software.
The system maintains a revision history and ensures consistent journal entry processing with accounting software, adhering to the requirements of the Electronic Bookkeeping Act, thereby enhancing data management efficiency and compliance.
Smart Images

Figure 0007588173000001 
Figure 0007588173000002 
Figure 0007588173000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a sales management system and a sales management program that are compatible with electronic bookkeeping. [Background technology]
[0002] With the introduction of the Electronic Bookkeeping Act and the invoice system, an increasing number of companies are taking advantage of this opportunity to promote digital transformation (DX).
[0003] For digital transformation, not only are internet-based systems essential, but core business systems that can quickly record transactions between companies, organize them, and print them at any time will also play a key role.
[0004] Furthermore, these core business systems need to be efficient and support the growth of the company while also contributing to the strengthening of internal controls. One of the standards for evaluating such core business systems is the certification system of the Japan Image and Information Management Association (JIIMA), a public interest incorporated association (hereinafter referred to as the "JIIMA Certification System").
[0005] The Electronic Bookkeeping Law allows for the storage of documents in electronic form in order to reduce the burden of storing and processing ledgers, receipts, invoices, etc. Here, "electronic bookkeeping" refers to the electronic storage of national tax-related documents created electronically using a computer, etc. National tax-related documents include financial statements (balance sheets and profit and loss statements), purchase orders, contracts, invoices, receipts, journals, cash ledgers, accounts receivable ledgers, etc.
[0006] For example, these documents can be created using a sales management system, accounting software (hereinafter referred to as "accounting software"), and document storage services (hereinafter referred to as "electronic bookkeeping systems"), and can be stored as electronic data when certain requirements are met.
[0007] In particular, from January 2022, the system of prior approval by the tax office director will be abolished, and the conditions will be significantly revised and relaxed. Many electronic accounting systems have electronic bookkeeping functions, and they can now be used by sole proprietorships.
[0008] Here, system changes are also being made, such as requiring only date, amount, and transaction partner to search electronically stored data.
[0009] In this context, from January 2022, invoices, etc. for electronic transactions (including receipts for online shopping) will no longer be valid if printed out and stored on paper, regardless of whether electronic bookkeeping is used or not, and must be stored electronically. Therefore, for example, it will be necessary to take measures such as i) adding a timestamp to the scanned file of the invoice, etc. output from the electronic bookkeeping system, and ii) storing the file of the invoice, etc. in a system where corrections or deletions cannot be made or where records are left (such as a cloud service such as an electronic bookkeeping system).
[0010] In addition, in the JIIMA certification system mentioned above, an important requirement for a good electronic ledger is that it must have a function for recording corrections and deletions. Here, it is not enough to simply search and extract and output the correction and deletion history; it must also be able to seamlessly link with other systems, which will lead to digital transformation, efficiency, and internal control.
[0011] Here, an example of a "system that keeps a record of corrections and deletions" related to the above technical requirements is the technology disclosed in Patent Document 1.
[0012] The technology disclosed in Patent Document 1 discloses a data management device including: a proxy correction processing means for correcting managed data associated with a subordinate account in response to input operations by a user of a proxy account that is pre-assigned to a specific subordinate account among a plurality of accounts; a load information generating means for generating load information relating to an expected load of correction work by a user of the proxy account based on correction history information relating to the history of corrections of the managed data by the proxy correction processing means over a specified period of time and the managed data associated with the subordinate account registered in a memory unit; and an output control means for causing an output unit to perform output according to the expected load based on the load information. [Prior art documents] [Patent documents]
[0013] [Patent Document 1] JP 2018-142183 A Summary of the Invention [Problem to be solved by the invention]
[0014] However, the data management device disclosed in Patent Document 1 operates while recognizing the following problems. In other words, "the frequency with which newly registered managed data needs to be modified by the proxy account user typically varies greatly depending on the level of proficiency of the user who registered the managed data and the type of managed data that the user registers. As a result, with the above-mentioned conventional technology, there is a tendency for the proxy account user to overdo and underdo the work involved in checking and modifying the managed data, resulting in an issue of being unable to efficiently manage the managed data."
[0015] Therefore, although this data management device is a "system that keeps records of corrections and deletions," it is not intended to be a "system that does not allow corrections or deletions or that keeps records," as required by the Electronic Bookkeeping Act.
[0016] Of course, in a company's sales management system or accounting software, it is naturally assumed that corrections and deletions will occur, so a "system that does not allow corrections or deletions" is not realistic. Therefore, although it is necessary to have a "system that keeps a record of corrections and deletions," the device disclosed in Patent Document 1 does not take into consideration the point that such records (correction history) cannot be changed by the user.
[0017] Furthermore, in accounting software, the so-called "journal entry processing" is carried out when recording in double-entry bookkeeping format. However, when performing such journal entry processing and recording, a major issue exists as to how to link the two systems, for example, while maintaining the condition that the sales data is consistent between the sales management side and the accounting software side, and journal entry processing is performed while maintaining the condition that the revision history cannot be changed.
[0018] The present invention has been made to solve the above-mentioned problems, and its object is to provide a sales management system and a sales management program that are capable of recording a revision history while satisfying the conditions required by the Electronic Bookkeeping Act and the like.
[0019] It is still another object of the present invention to provide a sales management system and a sales management program that are capable of executing accounting processing that is consistent with accounting software while leaving the revision history on the sales management system side in an unchangeable state. [Means for solving the problem]
[0020] According to one aspect of the present invention, there is provided a sales management system comprising a storage device for storing a billing management database, the billing management database including a sales database for storing data including sales book data, and revision history information associated with items in the sales database that can be changed or deleted and for storing a revision history for the sales book data, and comprising: a write processing means for receiving an instruction in response to an operation from a user's external terminal and executing a process of writing, modifying or deleting the sales book data in the sales database; a history recording means for storing a history of the processes of writing, modifying or deleting for each item in the sales database as revision history information; and a read processing means for outputting data for displaying the contents of the sales database and the contents of the revision history information on the external terminal in response to a request from the external terminal, and a means for prohibiting writing to and changing the revision history information from the external terminal. The system further includes a journal entry generation means for generating journal entry data to be supplied to external accounting software based on data in the sales database, and an accounting software linkage means for transcribing the journal entry data generated by the journal entry generation means into the accounting software, and when generating the journal entry data, the journal entry generation means generates journal entry data for converting the pre-correction journal entry into a red slip entry for data for which transcribing processing by the accounting software linkage means has been completed in accordance with the change history to the sales database.
[0022] Preferably, when generating the journal data, the journal generation means generates journal data for making black voucher journal entries for data before the completion of the posting process by the accounting software linkage means, in accordance with the change history to the sales database.
[0023] Preferably, the correction history information is a correction history table associated with fields corresponding to items that can be changed and deleted, and the correction history table includes, associated with each sales book data, first flag data for distinguishing between new additions of sales book data, data that has been transcribed, and corrections to transcribed data, and second flag data indicating correction and deletion history, and the journal entry generation means generates journal entry data for turning the pre-correction journal entry into a red slip journal entry for data for which transcribing has been completed, based on the first and second flag data. Preferably, the sales database includes third flag data associated with each sales book data for distinguishing the data as newly added, transcribed, or modified;
[0024] The journal entry generating means generates journal entry data for making a black voucher journal entry for data before the end of the posting process, based on the third flag data.
[0025] Preferably, the claim management database individually authenticates the user operator when logging in to the external terminal, the history recording means stores the correction history information in association with the history and the operator, and the reading processing means outputs the contents of the correction history information in association with information identifying the operator as data for displaying the contents of the correction history information on the external terminal.
[0026] Preferably, the order data is received from the user's customer, and after delivery processing according to the order data, To, please The claim management database further includes a claim management means for issuing a claim form. Book sales data and data on payment processing related to the invoice. The invoice management means stores invoice copy data in the invoice management database when issuing an invoice, and creates index data that enables invoice searches. Book sales data The electronic data storage service providing server then transmits the extracted data to the customer in association with the original invoice data, and a notification is then sent from the electronic data storage service providing server to the customer urging the customer to download the original invoice data.
[0027] According to another aspect of the present invention, a storage device for storing a claims management database is provided. I ask A sales management program for controlling the operation of a sales management system including a calculation device for executing a process for operating a claim management database, the claim management database including a sales database for storing data including sales book data, and revision history information associated with items in the sales database that can be changed or deleted and for storing a revision history of the sales book data, the calculation device receiving an instruction in response to an operation from an external terminal of a user and executing a write process for writing, modifying, or deleting the sales book data in the sales database, the calculation device storing a history of the write, modify, and delete processes for each item in the sales database as revision history information, and the calculation device , outsideUpon request from the terminal , Sell The contents of the database and Bi-rehabilitation Contents of correct history information Outside and outputting data to be displayed on the external terminal. , calligraphy The steps to perform the embedding process are , outside From a terminal Repair Prohibiting writing and modification to positive history information; The method further includes a step in which the calculation device generates journal entry data to be supplied to external accounting software based on data in the sales database, and a step in which the calculation device transfers the journal entry data generated in the step of generating journal entry data to the accounting software, wherein in the step of generating journal entry data, the calculation device generates journal entry data for transferring the pre-correction journal entry to a red slip journal entry for data for which transfer processing has been completed in the step of transferring to the accounting software in accordance with a history of changes to the sales database. The processing is executed by a computer. Effect of the Invention
[0028] According to the sales management system and the sales management program of the present invention, it is possible to keep a revision history while satisfying the conditions required by the Electronic Bookkeeping Law and the like.
[0029] Furthermore, according to the present invention, it is possible to execute accounting processing that is consistent with the accounting software while leaving the correction history in an unchangeable state on the sales management system side. [Brief description of the drawings]
[0030] [Figure 1] FIG. 1 is a diagram showing an overview of the configuration of a sales management system 1000 according to the present embodiment. [Diagram 2] FIG. 2 is a functional block diagram for explaining the functional configuration of a sales management service providing server 3000. [Diagram 3] FIG. 2 is a block diagram for explaining the hardware configuration of a sales management service providing server 3000. [Figure 4] FIG. 13 is a conceptual diagram showing an example of editing processing for sales book data 3310. [Diagram 5] FIG. 5 is a conceptual diagram showing an example of editing processing of the sales book data 3310 shown in FIG. 4 and history data stored in the sales history data 3320 corresponding to the editing processing. [Figure 6] FIG. 13 is a conceptual diagram showing an example of editing processing of sales book data 3310 and the corresponding history data stored in sales history data 3320, as well as journalization data 3330 when journalization processing is performed. [Figure 7] 6, is a conceptual diagram showing an example of an editing process for sales book data 3310 and the corresponding history data stored in sales history data 3320, as well as an example of journal data 3330. [Figure 8] 7, this is a conceptual diagram showing an example of the journal entry posting process for the sales book data 3310 and the corresponding history data stored in the sales history data 3320, as well as an example of the journal entry data 3330. [Figure 9] 9 is a flowchart showing the flow of adding, editing, journalizing, and posting the sales data as shown in FIGS. 6 to 8. [Figure 10] 8. This is a conceptual diagram showing an example of an editing process for sales book data 3310 performed subsequent to FIG. 8, and the corresponding history data stored in sales history data 3320, and journal data 3330. FIG. [Figure 11] FIG. 11 is a conceptual diagram showing a case where, after the correction process of the amount after posting in FIG. 10, further deletion of the sales book data is performed. [Figure 12] 11. This is a conceptual diagram showing an example of journal entry posting processing for sales book data 3310 after the amount deletion processing in FIG. 11, and the corresponding history data stored in sales history data 3320, as well as journal entry data 3330. [Figure 13] 13 is a diagram showing an example of a sales update history inquiry screen displayed on the display unit of the sales management department terminal 2000. FIG. [Figure 14] FIG. 13 is a diagram showing customer account relationships managed in the sales management service providing server 3000. [Figure 15] FIG. 13 is a conceptual diagram showing the flow of data when an invoice is issued using the sales management service providing server 3000. [Figure 16] 13 is a conceptual diagram showing the flow of data in an electronic ledger in the sales management service providing server 3000. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0031] The configuration of the sales management system 1000 according to the embodiment of the present invention will be described below. In the following embodiments, components and processing steps denoted by the same reference numerals are the same or equivalent, and the description thereof will not be repeated unless necessary.
[0032] In the following description, the program running on the sales management service providing server 3000 of the sales management system 1000 of the present invention is assumed to be a computer program installed on a single server device and executing processing as the sales management system.
[0033] However, the processing of the sales management service providing server 3000 may be distributed among a plurality of computer devices, and the number of arithmetic devices that executes the computer processing may be one or more.
[0034] The sales management service providing server 3000 may be configured to run on a server on the cloud, or may be configured to run in a distributed manner on a server on the cloud and an on-premise server within a company. For example, a configuration may be adopted in which some or all of important sales management data is stored on an on-premise server, and, as necessary, linkage with accounting processing, etc. is processed in linkage with a server on the cloud. Alternatively, although not limited thereto, the program running on the sales management service providing server 3000 may run only on an on-premise or cloud server. [Embodiment Mode] (Overview of the overall system configuration)
[0035] FIG. 1 is a diagram showing an overview of the configuration of a sales management system 1000 according to this embodiment.
[0036] In the sales management system 1000, a sales management department terminal 2000 of a user company that uses the system and an accounting department terminal 2300 of a user company that uses the system are connected to a sales management service providing server 3000 via a network 2 (e.g., the Internet).
[0037] The sales management department terminal 2000 is used by the administrator or a user under the administrator's supervision to manage sales management data by inputting and editing sales data, and to manage order data by registering purchase orders, issuing quotations, issuing and registering delivery notes, and issuing invoices.
[0038] Here, the "sales data" managed by the sales management department terminal 2000 is one of the revenue classifications used in corporate accounting, and is data that quantifies revenue from products and services that are the main business of the company. It is managed by day, week, month, year, etc.
[0039] Furthermore, "sales book data" refers to data that, after new additions and corrections, ultimately becomes the original sales data used for corporate accounting. "Sales history data" refers to data on all correction history and history related to linking processing with accounting software after new sales data is registered in the sales management department terminal 2000. As will be described later, although the "sales book data" itself can be edited by an authenticated user on the sales management department terminal 2000 by adding, correcting, or deleting data, the sales management system 1000 is configured to prohibit editing operations such as adding, correcting, or deleting the "sales history data" from the sales management department terminal 2000.
[0040] The accounting service providing server 4000 is a cloud-based accounting software service that provides a service using accounting software that automates accounting tasks such as bookkeeping, accounting journal entry, payment management, and preparation of financial statements over the Internet. In the case of a cloud-based system, the accounting software can be accessed from anywhere with an Internet connection, and remote work and work while traveling are also possible. Note that the accounting service providing server 4000 may also be configured to be operated partially or entirely by an on-premise server, similar to the sales management service providing server 3000.
[0041] The evidence management service providing server 8000 is connected to the sales management department terminal 2000 and the sales management service providing server 3000 via the network 2. The evidence management service providing server 8000 provides a service that allows the storage and management of "evidence" received from customers or issued by the company on the cloud. Here, "evidence" refers to documentary evidence showing the contents of a transaction, such as a receipt, invoice, delivery note, or quotation.
[0042] In this case, in the management of evidence in the evidence management service providing server 8000, it is necessary to comply with search requirements and measures to prevent correction and deletion in accordance with the provisions of the Electronic Books Preservation Law.
[0043] Here, the "measures to prevent corrections and deletions" are those required to satisfy the storage requirements (ensuring authenticity) of Article 7 (electronic transactions) of the Electronic Bookkeeping Act.
[0044] In order to "ensure authenticity," it is necessary to take one of the following measures:
[0045] 1. The transaction information is exchanged after the electromagnetic records have been flagged as public or private.
[0046] 2. Using one of the following methods, the recorded items of the electromagnetic records shall be flagged as public / private, and information regarding the person storing the electromagnetic records or the person who directly supervises that person shall be made available for confirmation.
[0047] 2-1. Promptly affix a public / private flag to the recorded items in the electromagnetic records after receiving the transaction information.
[0048] 2-2. Mark the items in the electromagnetic records as public / private promptly after the usual period for processing the business has elapsed (only if regulations have been established for the processing of each administrative task from the receipt and delivery of the transaction information to the marking of the items in the electromagnetic records as public / private). 3. The transaction information is exchanged and the electronic records are stored using a computer processing system that meets any of the following requirements.
[0049] 3-1. If any corrections or deletions are made to the recorded information in the electronic or magnetic record, these facts and contents can be confirmed.
[0050] 3-2. The information recorded in the electronic or magnetic record cannot be corrected or deleted.
[0051] 4. Establish rules for administrative procedures to prevent the unjustified correction or deletion of the items recorded in the electronic records, operate in accordance with said rules, and keep said rules in addition to storing the electronic records.
[0052] Therefore, when uploading vouchers manually to the voucher management service providing server 8000, in order to satisfy the requirement of "ensuring authenticity," it is necessary to establish, for example, the above-mentioned administrative procedure regulation 4. However, as will be described later, when uploading vouchers via the sales management service providing server 3000, a "history of corrections and deletions" is automatically created in the first place, and the history data cannot be edited, making it possible to take measures to prevent corrections and deletions.
[0053] In addition, the "search requirements" must meet the following requirements:
[0054] The storage location must be equipped with a computer (such as a personal computer), programs, a display, a printer, and their operating manuals so that they can be quickly output on the screen and in writing in a neat and clear format.
[0055] 1. You can set the transaction date, other dates, transaction amount, and transaction partner as search conditions.
[0056] 2. Ability to search by specifying date or amount range.
[0057] 3. The ability to search using conditions that combine two or more arbitrary record items.
[0058] Here, if the person obligated to preserve the records is able to respond to requests from the relevant officials of the National Tax Agency, etc. to download electronic records based on their authority to question and inspect, there is no need to ensure the ability to specify the scope and set a combination of items.
[0059] The configuration for satisfying the "search requirement for evidence" when via the sales management service providing server 3000 will be described later.
[0060] FIG. 2 is a functional block diagram for explaining the functional configuration of the sales management service providing server 3000. As shown in FIG.
[0061] Referring to Figure 2, the sales management service providing server 3000 includes a communication interface 3002 for transmitting data to and from the sales management department terminal 2000, the accounting department terminal 2300, the accounting service providing server 4000, or the voucher management service providing server 8000 via the network 2, an arithmetic processing unit 3100, a memory 3200 for temporarily storing data, and a memory unit 3300 for storing data in a non-volatile manner.
[0062] The storage unit 3300 stores a billing management database.
[0063] The billing management database includes a sales book database 3310 , sales history data 3320 , journal data 3330 , billing management data 3340 , billing management history data 3350 , and operator registration data 3360 .
[0064] The billing management database can be realized by a relational database, an object-relational database, an object database, or the like, but the data structure is not important.
[0065] More generally, a "database" may be a database with a well-defined schema and capable of using transactions, such as a relational database or an object-relational database, or an object database or a column-oriented database management system in which data in the same column is aggregated and stored in a physically close area.
[0066] In the following, as an example, the claim management database will be described as a relational database.
[0067] In this case, the memory 3200 can be configured to hold a database instance. That is, in this case, a "database" refers to physical files such as data files, and includes files that manage change information for the database. In other words, a database refers to a "table" and "other object group," whereas an "instance" can exist as a process in memory and be responsible for data management. Of course, the configuration of a database is not necessarily limited to this configuration.
[0068] The calculation processing unit 3100 includes a table data write processing module (hereinafter, table data write processing MD) 3110 for performing editing such as adding new information to, and modifying and deleting information from, the sales book data 3310, the billing management data 3340, and the operator registration data 3360 in the billing management database (hereinafter, billing management DB) stored in the memory unit 3300.
[0069] Access to the sales history data 3320 and the billing management history data 3350 is prohibited from the table data write process MD 3110, and editing such as writing, modifying, and deleting these data cannot be performed from the sales management department terminal 2000.
[0070] The calculation processing unit 3100 further includes a table data read processing module (hereinafter, table data read processing MD) 3120 for reading data from the billing management database and generating display data for the sales management department terminal 2000 in response to operations and instructions from the sales management department terminal 2000, and a table data history recording module (hereinafter, table data history recording MD) 3130 for generating history information of editing such as new additions, corrections, and deletions to the sales book data by the table data write processing MD 3110, and recording it in the sales history data 3320.
[0071] The calculation processing unit 3100 further includes a table data journal creation module (hereinafter, table data journal creation MD) 3140 that generates journal data to be transferred to the accounting service providing server 4000 based on the data in the sales book data 3310 and the sales history data 3320 in response to operations and instructions from the sales management department terminal 2000, and stores the journal data in the memory unit 3300 as journal data 3330, and an accounting software linkage module (hereinafter, accounting software linkage MD) 3150 for executing the process of transferring the journal data created by the table data journal creation MD 3140 to the accounting service providing server 4000.
[0072] Although not limited to this, the accounting software linkage MD3150 can be configured to have a transcription format for commercially available accounting software pre-registered, and to have the function of converting accounting data into the required format and transcribing it to the accounting service provider server 4000 in response to operations and instructions from the sales management department terminal 2000.
[0073] The calculation processing unit 3100 further includes a billing management module (hereinafter, billing management MD) 3160 for managing order data, issuing quotations, managing delivery notes, issuing invoices, saving invoices, and other management in response to operations and instructions from the sales management department terminal 2000, registering the data as billing management data 3340, and performing prescribed processing. The table data writing processing MD 3110 has a function for performing editing processes such as new addition registration and correction / deletion of the billing management data 3340 in response to operations and instructions from the sales management department terminal 2000, and the data table history recording MD 3130 records this history information in the billing management history data 3350.
[0074] Access to the billing management history data 3350 is prohibited from the table data writing process MD3110, and writing, modifying, deleting, or other editing of this data cannot be performed from the sales management department terminal 2000, just like the sales history data 3320.
[0075] In addition, the billing management database is configured so that users of the sales management service providing server 3000 are registered in advance as operator registration data 3360, and authentication processing is performed using a password or other means when accessing the database. Editing processing such as new additions, corrections, and deletions of data performed through operations or instructions from the sales management department terminal 2000 is also recorded in association with the operator.
[0076] FIG. 3 is a block diagram for explaining the hardware configuration of the sales management service providing server 3000 shown in FIG.
[0077] As described above, the sales management service providing server 3000 may be configured so that a computing device (CPU: Central Processing Unit) in its own housing executes the arithmetic processing, or a part of the program processing may be further executed on another server. In the following, the explanation will be given assuming that a computing device in its own housing executes the arithmetic processing.
[0078] Although the sales management department terminal 2000, accounting department terminal 2300, accounting service providing server 4000, and voucher management service providing server 8000 differ in CPU processing power, their hardware configurations are basically the same, so the explanation will not be repeated.
[0079] 3, the sales management service providing server 3000 includes a CPU 3100 functioning as an arithmetic processing unit 3100, a RAM (Random Access Memory) 3200, a storage unit 3300, an operation unit 3004, a display unit 3005 (output unit), and a communication interface 3002. The various units of the sales management service providing server 3000 are connected to each other via a bus 3007.
[0080] The CPU 3100 reads out various programs such as system programs and application programs stored in the memory unit 3300, expands them in the work area of the RAM 3200, and controls the operation of each part of the sales management service providing server 3000 as the calculation processing unit 3100 in accordance with the programs.
[0081] The RAM 3200 is, for example, a volatile memory, and has a work area for temporarily storing various programs and data read by the CPU 3100.
[0082] The storage unit 3300 is configured with a non-volatile storage device such as a hard disk drive (HDD), a solid state drive (SSD), a flash memory, etc. The storage unit 3300 stores various programs executed by the CPU 3100 and various data such as setting data. The storage unit 3300 also stores a billing management database.
[0083] The operation unit 3004 has, for example, a key input unit such as a keyboard, a pointing device such as a mouse, and a touch panel superimposed on the display screen of the display unit 3005. The operation unit 3004 accepts input operations (key input) to the key input unit and input operations (position input) to the pointing device or touch panel, and outputs the operation information to the CPU 3100.
[0084] The display unit 3005 is configured by, for example, an LCD (Liquid Crystal Display), an organic EL (Electroluminescence) display, etc. The display unit 3005 displays the processing results of the application program, the contents of input by the operation unit 3004, etc. on the display screen in accordance with a control signal output from the CPU 3100.
[0085] The communication interface 3002 is configured, for example, by a network card, a modem, a router, etc. The communication interface 3002 may also be configured to include an antenna, a modulation / demodulation circuit, a signal processing circuit, etc., and to be capable of wireless communication. The communication interface 3002 is connected to an external device, such as a server on the communication network 2, for communication therewith to transmit and receive data.
[0086] For example, in the case of the sales management department terminal 2000, the CPU 3100 executes an information display / input program such as a browser, transmits information based on the contents of the user's input operation on the operation unit 3004 to the server 2 via the communication interface 3002, and displays information received from the server 2 on the display unit 3005. The above programs include an information display / input program such as a browser.
[0087] The program for the sales management service providing server 3000 to function as a computer device does not necessarily have to include an operating system (OS) that causes the computer main body to execute the functions of an information processing device, etc., when distributed. The program only needs to include an instruction portion that calls appropriate functions (modules) in a controlled manner and obtains the desired results. How a computer system operates is well known, and a detailed explanation will be omitted.
[0088] Furthermore, the CPU 3100 may also be a one-core processor or a multiple-core processor, i.e., a single-core processor or a multi-core processor.
[0089] FIG. 4 is a conceptual diagram showing an example of editing processing for the sales book data 3310. As shown in FIG.
[0090] In addition, although not limited thereto, when the sales book data 3310 is a relational database, the sales history data 3320 may be associated with each item of the tuple of the sales book data that can be added, modified, and deleted. Alternatively, as long as it is possible to associate with the history of additions, modifications, and deletions of the sales book data, it is not limited to such a configuration.
[0091] The attributes (item data) of a tuple in the sales book data include items generally required for managing sales data, such as the date and time of the sale, the business partner, the amount, the product name, the number of units traded, whether it is an accounts receivable or cash transaction, etc. It is also possible to configure the system so that business partners and product names are managed separately in a business partner master table and a product master table. In a database, the area where individual data is written is called a "field."
[0092] As will be described later, the sales book data 3310 and sales history data 3320 shown in FIG. 2 are designed with consideration given to linking with other commercially available accounting software.
[0093] In addition, instead of posting a journal entry to the accounting software each time a correction or deletion is made, the system is structured so that only the minimum necessary journal entries are posted. In other words, no matter how many corrections are made in the sales management, only the posted entries are recorded as red slips.
[0094] In addition, by having a history of corrections and deletions, it is also possible to transfer red and black vouchers (red and black entries) to accounting software.
[0095] The mechanism of the correction / deletion history will be described with reference to FIG.
[0096] First, as shown in Figure 4, consider the case where new sales data with an amount of 100 (the unit can be any, for example, 1 million yen) is initially added to the sales book data, and then the amount is revised to the number 200 and the sales data is deleted.
[0097] FIG. 5 is a conceptual diagram showing an example of the editing process for the sales book data 3310 shown in FIG. 4 and the history data stored in the sales history data 3320 corresponding to the editing process.
[0098] 1) As shown in Fig. 5(a), when a user operates the sales management department terminal 2000 to input sales and add (newly add) a sales slip for an amount of 100 to the sales book data, the table data write process MD3110 makes the new addition to the sales book data 3310, and as shown in Fig. 5(b), the table data history recording MD3130 records the addition in the sales history data 3320. At this time, the update category flag in the sales history data is recorded as "1: Addition".
[0099] 3) For example, in processing step 3, when a user operates the sales management department terminal 2000 to correct the amount in the sales input from 100 to 200, the table data history recording MD3130 adds the corrected content of the sales book data to the sales history data 3320 and records the update category of the sales history data as "3: After correction." The table data writing processing MD3110 corrects and overwrites the content of the sales book data 3310.
[0100] 6) Next, for example, in processing step 6, when a sales input is deleted by user operation on the sales management department terminal 2000, the table data history recording MD3130 adds the contents of the sales book data to be deleted to the sales history data 3320, and records the update category of the sales history data as "4: Delete." The table data writing processing MD3110 deletes the sales book data from the sales book data 3310.
[0101] FIG. 6 is a conceptual diagram showing an example of editing processing of sales book data 3310 and the corresponding history data stored in sales history data 3320, as well as an example of journalization data 3330 when journalization processing is performed.
[0102] FIG. 9 is a flowchart showing the flow of the process of adding, editing, accounting, and posting the sales data as shown in FIGS.
[0103] 6 and 9, first, as shown in Fig. 6(a), when a user operates the sales management department terminal 2000 to input sales and add (newly add) a sales slip of 100 to the sales book data (S100), the table data write process MD3110 makes the new addition to the sales book data 3310 (S102), and at the same time, as shown in Fig. 6(b), the table data history recording MD3130 records the addition in the sales history data 3320 (S104). At this time, the update category flag in the sales history data is set to "1: Addition".
[0104] At this point, the journal data has not yet been posted to the accounting service server 4000, so the posting flags for the sales book data and sales history data are recorded as "0: not posted."
[0105] Next, as shown in Fig. 6(a), when a journal entry posting instruction is given by user operation on the sales management department terminal 2000 (S106), the table data journal entry creation MD3140 creates data for black voucher journal entry (accounts receivable 100 / sales 100) based on the sales book data and records it in the journal entry data 3330 (S108). The accounting software linkage module 3150 executes a posting process for this journal entry data to the accounting service providing server 4000. In response to this process, the table data history recording MD3130 sets the posting flags of the sales book data and sales history data to "1: posted" (S100), and the update category flag for the sales history data remains "1: added".
[0106] 7 is a conceptual diagram showing an example of an editing process for the sales book data 3310 following the process of FIG. 6, and the corresponding history data stored in the sales history data 3320, and an example of the journal data 3330. In FIG.
[0107] 7 and 9, first, as shown in Fig. 7(a), when a user operates the sales management department terminal 2000 to amend the sales slip amount of 100 in the sales book data to 200 (S112), the table data write process MD3110 amends the amount in the sales book data 3310 (S114), and, as shown in Fig. 7(b), the table data history recording MD3130 records the amended amount in the sales history data 3320 (S116). At this time, the table data history recording MD3130 sets the posting flag for the sales book data and sales history data to "2: Amendment of posted amount" and records the update category flag for the sales history data to "3: Amendment".
[0108] 8 is a conceptual diagram showing an example of journal entry posting processing for the sales book data 3310, corresponding history data stored in the sales history data 3320, and journal entry data 3330, following the processing in FIG.
[0109] 8 and 9, as shown in Fig. 8(a), when a journal entry process is instructed based on the amount 200 after the correction of the sales book data by a user operation on the sales management department terminal 2000, the table data journal entry creation MD 3140 creates red slip journal entry (accounts receivable △100 / sales △100) data from the transfer flag of the sales history data that is immediately before "2: correction of posted amount" with a transfer flag of "1: data already posted" (S120), creates black slip journal entry (accounts receivable 200 / sales 200) data from the corrected but unposted sales book data (S122), and records it in the journal entry data 3330. The accounting software linkage module 3150 executes a transfer process to the accounting service providing server 4000 for this journal entry data. In response to this processing, the table data history recording MD3130 sets the transcription flags for the sales book data and sales history data to "1: Transcribed" (S124), and records "3: Correction" as the update category flag for the sales history data and as the update category for the sales history data.
[0110] In the following, red slip journal entries will be referred to as "red slip journal entries" and black slip journal entries will be referred to as "black slip journal entries."
[0111] The following further describes the editing process of the sales book data 3310 in FIG. 8, the history data stored in the sales history data 3320 corresponding to the editing process, and the journal data 3330.
[0112] FIG. 10 is a conceptual diagram showing an example of an editing process of the sales book data 3310 performed subsequent to FIG. 8, and the history data stored in the sales history data 3320 corresponding to the editing process, and the journal data 3330. In FIG.
[0113] FIG. 10 shows a case where, after the red and black journal entries in FIG. 8 and their posting process, further corrections are made to the sales book data but no journal entries are created.
[0114] That is, first, as shown in Fig. 10(a), when a user operates the sales management department terminal 2000 to amend the sales slip amount of 200 in sales book data 3310 to 150, table data write process MD3110 amends the amount in sales book data 3310, and, as shown in Fig. 10(b), table data history recording MD3130 records the amended amount in sales history data 3320. At this time, table data history recording MD3130 sets the posting flag for the sales book data and sales history data to "2: Amendment of posted amount" and records the update category flag for the sales history data to "3: Amendment".
[0115] FIG. 11 is a conceptual diagram showing an example of an editing process for the sales book data 3310 performed subsequent to FIG. 10, and the corresponding history data stored in the sales history data 3320, and the journal data 3330. In FIG.
[0116] FIG. 11 shows a case where the sales book data is further deleted after the post-transfer amount correction process in FIG.
[0117] That is, first, as shown in Fig. 11(a), when the amount of 150 is deleted from the sales slip amount in sales book data 3310 by user operation on sales management department terminal 2000, table data write process MD3110 deletes the amount from sales book data 3310, and, as shown in Fig. 11(b), table data history recording MD3130 records the amount before deletion in sales history data 3320. At this time, table data history recording MD3130 leaves the posting flag in the sales history data as "2: Correction of posted amount" and records the update type flag of the sales history data as "4: Delete".
[0118] FIG. 12 is a conceptual diagram showing an example of the journal entry posting process for the sales book data 3310 after the amount deletion process in FIG. 11, and the corresponding history data stored in the sales history data 3320, as well as the journal entry data 3330.
[0119] 12(a), when a user operates the sales management department terminal 2000 to instruct journal processing after deleting the sales book data, the table data journal creation MD 3140 creates red slip journal entry (accounts receivable △200 / sales △200) data from the posting flag "1: posted data" immediately before the transfer flag "2: correct posted amount" of the sales history data, and records it in the journal entry data 3330. At this time, since the update category flag of the latest sales update history data is "4: delete", the table data journal creation MD 3140 does not create black slip journal entry data from the sales book data.
[0120] Also, in FIG. 10, the posting flag indicates that the sales book data with the corrected amount 150 has not been journalized, so the table data journal creation MD 3140 does not create journal data.
[0121] The accounting software linkage module 3150 executes a transcription process for the journal entry data created as described above to the accounting service providing server 4000. In response to this process, the table data history recording MD 3130 maintains "4: Delete" as the update category flag for the sales history data.
[0122] As a result, when the accounting service server 4000 adds up the journal entry history, the accounts receivable becomes 0 / sales becomes 0, which is consistent with the sales data in the sales management service server 3000.
[0123] With the above-mentioned processing, in the sales book data 3310, the new addition, the presence or absence of posting to the accounting software side, and the correction after posting are managed by the posting flag, and in the sales history data 3320, the new addition, the presence or absence of posting to the accounting software side, and the correction after posting are managed by the posting flag in association with the value of the sales book data itself, and the status of new addition, post-correction, and deletion are managed by the update classification flag, and based on these flags, red transfer journal entries and black transfer journal entries are created and posted to the accounting software side during the journalization processing and posting processing. With this configuration, the sales management system records all the history of corrections and deletions, and during the journalization and posting processing, it becomes possible to integrate sales data in cooperation with external accounting software running on the accounting service providing server 4000.
[0124] FIG. 13 is a diagram showing an example of a sales update history inquiry screen displayed on the display unit of the sales management department terminal 2000.
[0125] In the operator registration data 3360, the administrator can also limit editing processes such as new additions, modifications, and deletions by the relevant person in the "person-specific function restrictions" field.
[0126] For example, for a specific operator, the function restrictions can be set so that the operator can only view sales data.
[0127] FIG. 13 shows an example of a sales history inquiry screen.
[0128] The person in charge of the new addition / correction / deletion operation, the date and time, and the number of history entries are displayed in the lower frame 200. By clicking the “<” button or >” button, it is also possible to move to the previous history or next history screen.
[0129] Figure 13 shows that the administrator last modified it at 11:45:59 on 2023 / 1 / 11. (Regarding collaboration with electronic document storage services)
[0130] FIG. 14 is a diagram showing the account relationships managed in the sales management service providing server 3000. As shown in FIG.
[0131] Referring to FIG. 14, the relationship between the users who use the voucher electronic storage service providing server 8000 via the sales management service providing server 3000 is as follows.
[0132] When A is a sales management system (sales management service providing server 3000), B is a user (contractor) of the sales management service providing server 3000, and C indicates a customer of the contractor. Therefore, the ratio of the number of accounts to be managed is generally: A:B=1:N, B:C=1:M (N and M are natural numbers) This is in a relationship.
[0133] The management account for the sales management system (sales management service providing server 3000) has the authority to add, edit, and delete subscribers and change passwords, and can also set up company-wide operations, check accounts, and view and download electronic evidence.
[0134] The administrator account of Contractor B has the authority to check contract information, edit its own account, change password, and add, edit, delete, and change password of client accounts. In addition, it is possible to set up the operation for each company, check all client accounts, upload electronic vouchers to clients, upload electronic vouchers received from other companies, and view and download electronic vouchers.
[0135] Customer C's account has the ID of Contractor B with whom they do business, and is authorized to edit their own account and change their password, as well as view and download their company's electronic vouchers received from Contractor B.
[0136] FIG. 15 is a conceptual diagram showing the flow of data when an invoice is issued using the sales management service providing server 3000.
[0137] FIG. 16 is a conceptual diagram showing the flow of data in the electronic ledger in the sales management service providing server 3000. As shown in FIG.
[0138] First, referring to FIG. 16, for example, a business partner such as a supplier sends delivery notes and invoices as electronic ledgers from the business partner terminal 2500, and these are stored, for example, in the local storage 2400 of the sales management department terminal 2000, although this is not limited thereto.
[0139] 15 and 16, for a customer of a user of the sales management service providing server 3000, 1) a customer account is registered from the sales management department terminal 2000.
[0140] Thereafter, between the registered customer and the sales management department terminal 2000, the issuance of quotations, invoices and delivery notes (corresponding to 2 and 5 in Figure 15, downloading an electronic ledger), and receipt of purchase orders (3 in Figure 15) are carried out via the sales management service providing server 3000.
[0141] Thereafter, in response to an operation from the sales management department terminal 2000, 2) the invoice is uploaded to the voucher electronic storage service providing server 8000 via the sales management service providing server 3000.
[0142] The original data of the invoice is uploaded as, for example, PDF (Portable Document Format) data. Note that the format of the original data is not limited to PDF, and may be another image format such as bmp, jpeg, or png.
[0143] At this time, the sales management service providing server 3000 manages the entire series of transactions such as issuing quotations, receiving purchase orders, and issuing invoices and delivery notes, so that searchable data such as the transaction date and other dates, transaction amount, and business partner can be added as electronic data to the original invoice data, and then uploaded to the evidence electronic storage service providing server 8000.
[0144] As a result, both the copy of the invoice data and the original of the invoice data can satisfy the "search requirements" required by the Electronic Book Preservation Law. In other words, the copy of the invoice data can be searched only within the data of the sales management service providing server 3000 as an electronic book. On the other hand, the original of the invoice data can be searched both within the sales management service providing server 3000 and within the voucher electronic preservation service providing server 8000.
[0145] When the original invoice data is uploaded to the electronic evidence storage service providing server 8000 via the sales management service providing server 3000, 4) an invoice issuance notification email is sent from the sales management department terminal 2000 or the sales management service providing server 3000 to the trading partner terminal 2800 of the user's client company.
[0146] In response to this, the customer terminal 2800 becomes able to download the original data of the invoice (5) from the evidence electronic storage service providing server 8000.
[0147] At this time, by passing through the sales management service providing server 3000, it is not necessary for the voucher electronic storage service providing server 8000 to store a copy of the invoice data.
[0148] If the sales management service providing server 3000 is not used, the voucher electronic storage service providing server 8000 must store both the original data and the copy data, and the cost increases by the storage capacity of the copy data. Also, to satisfy the "search requirements," it is generally necessary to read the data required for the search from the PDF data of the invoice using a character reading function (OCR (Optical Character Recognition) function). However, in this case, it is unavoidable that a certain percentage of character errors will occur due to reading errors.
[0149] By passing through the sales management service providing server 3000, such character reading errors can be avoided.
[0150] As described above, according to the sales management system and sales management program described in the embodiment, it is possible to realize a sales management system and sales management program that can keep a revision history while satisfying the conditions required by the Electronic Bookkeeping Act and the like.
[0151] In addition, according to the sales management system and sales management program described in the embodiment, it is possible to perform accounting processing that is consistent with the accounting software while leaving the correction history unchangeable on the sales management system side.
[0152] In addition, according to the sales management system and sales management program described in the embodiment, it is possible to reduce the amount of data stored on an external server while satisfying the conditions required by the Electronic Bookkeeping Act and the like, and also to reduce search errors.
[0153] The embodiments disclosed herein are merely examples of configurations for specifically implementing the present invention, and do not limit the technical scope of the present invention. The technical scope of the present invention is indicated by the claims, not by the description of the embodiments, and is intended to include modifications within the literal scope of the claims and within the scope of equivalent meanings. [Explanation of symbols]
[0154] 2 network, 1000 sales management system, 2000 sales management department terminal, 2300 accounting department terminal, 3000 sales management service providing server, 3002 communications interface 3002, 3100 calculation processing unit, 3110 table data write processing module, 3120 table data read processing module, 3130 table data history recording module, 3140 table data journal entry creation module, 3150 accounting software linkage module, 3160 order management module, 3200 memory, 3300 storage unit, 3310 sales book database, 3320 sales history data, 3330 journal entry data, 3340 billing management data, 3350 billing management history data, 3360 operator registration data.
Claims
1. A sales management system, a storage device for storing a claim management database; The claim management database includes: a sales database storing data including book sales data; revision history information associated with items in the sales database that can be changed or deleted, the revision history information storing revision history of the sales data; a write processing means for receiving an instruction in response to an operation from a user's external terminal and executing a process of writing, modifying, or deleting the sales book data in the sales database; a history recording means for storing a history of writing, modifying, and deleting processes for each of the items in the sales database as the modification history information; a read processing means for outputting data for displaying the contents of the sales database and the contents of the correction history information on the external terminal in response to a request from the external terminal; means for prohibiting writing and modification of the revision history information from the external terminal; a journal entry generating means for generating journal entry data to be supplied to an external accounting software based on the data in the sales database; accounting software linking means for transferring the journal data generated by the journal data generating means to the accounting software; The journal entry generation means, in generating the journal entry data, generates journal entry data for converting pre-correction journal entries into red slip entries for data for which posting processing by the accounting software linkage means has been completed in accordance with the change history to the sales database, in a sales management system.
2. The sales management system of claim 1, wherein the journal entry generation means, when generating the journal entry data, generates journal entry data for making black voucher entries for data before the posting process by the accounting software linkage means is completed in accordance with the change history to the sales database.
3. the revision history information being a revision history table associated with fields corresponding to the changeable and deletable items; The revision history table includes: first flag data associated with each of the sales book data for distinguishing between a new addition, a transfer process, and a correction of a transfer process of the sales book data; and second flag data indicating a history of modification and deletion; The sales management system according to claim 1, wherein the journal entry generation means generates journal entry data for converting the pre-correction journal entry into a red slip journal entry for data for which the posting process has been completed based on the first and second flag data.
4. the sales database includes third flag data associated with each of the sales book data for distinguishing whether the data is newly added, has been transcribed, or has been modified; 4. The sales management system according to claim 3, wherein said journal entry generating means generates journal entry data for journalizing black vouchers for data before the end of said posting process, based on said third flag data.
5. The request management database individually authenticates the operator of the user when logging in to the external terminal, The history recording means stores the correction history information in such a manner that the history and the operator are associated with each other, 2. The sales management system according to claim 1, wherein said read processing means outputs said correction history information in association with information for identifying said operator as data for displaying the contents of said correction history information on said external terminal.
6. The system further includes a billing management means for receiving order data from the user's customers and issuing an invoice after a delivery process according to the order data, The billing management database further stores the sales data and the payment processing data related to the invoice, The claim management means includes: When issuing the invoice, storing invoice copy data in the invoice management database; extracting index data that enables searching of the invoice from the sales copy data, associating the index data with the original copy data of the invoice, and transmitting the index data to an electronic data storage service providing server; 2. The sales management system according to claim 1, further comprising a step of transmitting a notification from said electronic data storage service providing server to said customer, urging said customer to download original data of said invoice.
7. A sales management program for controlling the operation of a sales management system including a storage device for storing a request management database and a computing device for executing a process for operating the request management database, comprising: The billing management database includes a sales database that stores data including sales book data, and revision history information that is associated with items in the sales database that can be changed or deleted and that stores revision history information for the sales book data; the computing device receiving an instruction in response to an operation from a user's external terminal and executing a write process for writing, modifying, or deleting the sales book data in the sales database; the calculation device storing a history of writing, modifying, and deleting processes for each of the items in the sales database as the modification history information; a step of outputting data for displaying the contents of the sales database and the contents of the correction history information on the external terminal in response to a request from the external terminal by the arithmetic device; the step of executing the writing process includes a step of prohibiting writing and changing of the revision history information from the external terminal; generating journal entry data to be supplied to an external accounting software based on the data in the sales database by the computing device; The calculation device further includes a step of transcribing the journal data generated by the step of generating the journal data into the accounting software, The sales management program causes a computer to execute a process in which, in the step of generating the journal data, the calculation device generates journal data for making red slip entries for the journal entries before correction for data for which the posting process has been completed by the step of posting to the accounting software, in accordance with the change history to the sales database.
Citation Information
Patent Citations
Sales data processing system and program recording medium therefor
JP2001109961A
Receipt data collation support apparatus and receipt data collation support program
JP2012133507A
Traceability system
JP2012177982A
Data management device and program
JP2018142183A
Work supporting device, method for supporting work, and work support program
JP2023027470A
