JP7588173B2 - Sales management system and sales management program - Google Patents

Description

The present invention relates to a sales management system and a sales management program that support electronic bookkeeping.

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).

For digital transformation, not only are internet-based systems essential, but the role of core business systems that can quickly record transactions between companies, organize them, and output them at any time will also be important.

These core business systems must also contribute to strengthening internal controls while improving efficiency and supporting the growth of the company. 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").

The Electronic Bookkeeping Act allows for the storage of documents as electronic data 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 that have been created electronically using a computer or other device. 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.

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.

In particular, from January 2022, the tax office director's prior approval system will be abolished and the conditions will be significantly revised and relaxed, and many electronic accounting systems have electronic bookkeeping functions, which can now be used by sole proprietorships.

At this point, system changes are also being made, such as requiring only date, amount, and transaction partner to search electronically stored data.

In this context, from January 2022, invoices, etc. for electronic transactions (including receipts for online shopping) will no longer be valid if they are 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 scanned files of invoices, etc. output from an electronic bookkeeping system, and ii) storing files of invoices, etc. in systems where corrections or deletions cannot be made or where records are left (such as cloud services such as electronic bookkeeping systems).

In addition, as mentioned above, in the JIIMA certification system, a function for recording corrections and deletions is an important requirement for a good electronic ledger to be recognized. Here, it is not enough to simply search and extract and output the correction and deletion history; the ability to seamlessly link with other systems will lead to digital transformation, efficiency, and internal control.

Here, an example of a "system that keeps a record of corrections and deletions" that meets the above technical requirements is the technology disclosed in Patent Document 1.

The technology disclosed in Patent Document 1 discloses a data management device that includes a proxy correction processing means for correcting managed data associated with a subordinate account in response to an input operation by a user of a proxy account that is previously associated with a specific subordinate account among multiple accounts, a load information generating means for generating load information related to an expected load of correction work by a user of the proxy account based on correction history information related to a history of corrections of the managed data by the proxy correction processing means over a predetermined period of time and the managed data associated with the subordinate account registered in a storage unit, and an output control means for causing an output unit to perform an output according to the expected load based on the load information.

JP 2018-142183 A

However, the data management device disclosed in Patent Document 1 operates under the recognition of 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."

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.

Of course, in a company's sales management system or accounting software, it is naturally expected that corrections and deletions will occur, so a "system that does not allow corrections or deletions" is not realistic. Therefore, while it is essential that the system "keeps a record of corrections and deletions," the device disclosed in Patent Document 1 does not take into consideration the fact that such records (revision history) cannot be changed by the user.

Furthermore, in accounting software, the so-called "journal entry processing" is carried out when recording in double-entry bookkeeping format. However, when performing this type of journal entry processing and recording, a major issue exists in how to link the two systems, for example, while maintaining the condition that the sales data is consistent with the accounting software and that the revision history cannot be changed.

The present invention has been made to solve the above problems, and aims to provide a sales management system and a sales management program that can keep a revision history while meeting the requirements of the Electronic Bookkeeping Act and other laws.

Yet another object of the present invention is to provide a sales management system and a sales management program that can execute accounting processing that is consistent with accounting software while leaving the revision history in an unchangeable state on the sales management system side.

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 revision history information for the sales book data, and including 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, and deleting each item in the sales database as revision history information, and a history recording means for storing a history of the processes of writing, modifying, and deleting each item in the sales database in response to a request from the external terminal. The system further comprises a read processing means for outputting data for displaying the contents of the sales database and the contents of the correction history information on an external terminal, a means for prohibiting writing to and changing the correction history information from the external terminal , a journal entry generation means for generating journal entry data to be supplied to external accounting software based on the 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 in generating the journal entry data, the journal entry generation means generates journal entry data for turning 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.

Preferably, when generating the journal data, the journal generation means generates journal data for making black voucher journal entries for data before the transcription process by the accounting software linkage means is completed, in accordance with the change history to the sales database.

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 already been posted, and corrections to data that has already been posted, and second flag data indicating post-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 posting 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;

The journal entry generation means generates journal entry data for black voucher journal entry for data before the end of the posting process based on the third flag data.

Preferably, the billing management database individually authenticates the user's operator when logging in to the external terminal, the history recording means stores the revision history information in association with the history and the operator, and the read processing means outputs the revision history information in association with information identifying the operator as data for displaying the contents of the revision history information on the external terminal.

Preferably, the system further includes a billing management means for accepting order data from the user's customers and issuing invoices after delivery processing according to the order data, and the billing management database further stores sales book data and data on payment processing related to the invoice, and when issuing an invoice, the billing management means stores invoice copy data in the billing management database, extracts index data that allows the invoice to be searched from the sales book data , associates it with the original invoice data, sends it to the electronic data storage service providing server, and sends a notification from the electronic data storage service providing server to the customer urging them to download the original invoice data.

According to another aspect of the present invention, there is provided a sales management program for controlling the operation of a sales management system having a storage device for storing a billing management database and a calculation device for executing processing to operate the 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 and 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, and 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 responding to a request from the external terminal by executing the following steps: and outputting data for displaying the contents of the sales database and the contents of the correction history information on an external terminal , the step of executing the write process includes a step of prohibiting writing to and changes to the correction history information from the external terminal, and further comprising a step in which the arithmetic device generates journal entry data to be supplied to external accounting software based on the data of the sales database, and a step in which the arithmetic device transfers the journal entry data generated in the journal entry data generating step into the accounting software, and in the step of generating journal entry data, the arithmetic device causes the computer to execute a process of generating journal entry data for making a red slip entry for data before correction for which the transfer process has been completed in the transfer to the accounting software step, in accordance with the change history to the sales database.

The sales management system and sales management program of the present invention make it possible to keep a revision history while satisfying the requirements of the Electronic Bookkeeping Act and other laws.

In addition, this invention makes it possible to execute accounting processing that is consistent with the accounting software while leaving the revision history unchangeable on the sales management system side.

FIG. 1 is a diagram showing an overview of the configuration of a sales management system 1000 according to an embodiment of the present invention. FIG. 3 is a functional block diagram for explaining the functional configuration of the sales management service providing server 3000. 3 is a block diagram for explaining the hardware configuration of a sales management service providing server 3000. [0033] FIG. FIG. 13 is a conceptual diagram showing an example of editing processing for sales book data 3310. 5 is a conceptual diagram showing an example of an editing process for the sales book data 3310 shown in FIG. 4 and history data stored in the sales history data 3320 corresponding to the editing process. This 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 journal entry data 3330 when journal entry processing is performed. 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. 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. 9 is a flowchart showing a flow of adding, editing, journalizing, and posting the sales data as shown in FIGS. 6 to 8. 8, and the corresponding history data stored in sales history data 3320, and an example of journal data 3330. FIG. 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. This is a conceptual diagram showing an example of the journal entry posting process for sales book data 3310 after the amount deletion process in Figure 11, and the corresponding history data stored in sales history data 3320, as well as journal entry data 3330. 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. A diagram showing customer account relationships managed in the sales management service providing server 3000. 13 is a conceptual diagram showing the flow of data when an invoice is issued using the sales management service providing server 3000. 13 is a conceptual diagram showing the flow of data in an electronic ledger in the sales management service providing server 3000.

The configuration of the sales management system 1000 according to an embodiment of the present invention will be described below. Note that in the following embodiments, components and processing steps with the same reference numerals are the same or equivalent, and their description will not be repeated unless necessary.

In the following, the program running on the sales management service providing server 3000 of the sales management system 1000 of the present invention will be described as a computer program that is installed on a single server device and executes processing as a sales management system.

However, the processing of the sales management service providing server 3000 may be distributed among multiple computer devices, and the computing device that executes the computer processing may be single or multiple.

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 part or all of important sales management data may be stored on an on-premise server, and, as necessary, processing such as linking with accounting processing may be performed in cooperation 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)

Figure 1 shows an overview of the configuration of the sales management system 1000 in this embodiment.

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).

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.

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 company's main business. It is managed daily, weekly, monthly, annually, etc.

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 all correction history data from when the data is newly registered as sales data in the sales management department terminal 2000, and history data related to linking processing with accounting software. 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.

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 entries, 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 it is possible to work remotely or while traveling. As with the sales management service providing server 3000, the accounting service providing server 4000 may also be configured to be operated in part or in whole on an on-premise server.

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 network 2. The evidence management service providing server 8000 provides a service that allows "evidence" received from customers or issued by the company to be stored and managed on the cloud. Here, "evidence" refers to documentary evidence showing the contents of a transaction, such as a receipt, invoice, delivery note, or quotation.

In this case, the management of evidence in the evidence management service providing server 8000 must comply with search requirements and preventive measures against correction and deletion in accordance with the provisions of the Electronic Bookkeeping Act.

Here, "measures to prevent corrections and deletions" are required to meet the storage requirements (ensuring authenticity) of Article 7 (electronic transactions) of the Electronic Bookkeeping Act.

In order to "ensure authenticity," it is necessary to take one of the following measures:

1. After the disclosure/non-disclosure flag has been attached to the recorded items of the electromagnetic record, the transaction information is exchanged.

2. Use one of the following methods to mark the items recorded in the electromagnetic records as public/private, and make it possible to confirm information about the person who stores the electromagnetic records or the person who directly supervises that person.

2-1. Immediately after receiving or sending the transaction information, a public/private flag must be attached to the recorded items in the electromagnetic record.

2-2. Mark the electromagnetic records as public or private promptly after the normal period for processing the business has elapsed (only if regulations have been established for the processing of each business from the receipt and delivery of the transaction information to marking the recorded matters as public or private).
3. The transaction information is exchanged and the electromagnetic records are stored using a computer processing system that satisfies any of the following requirements:

3-1. If any corrections or deletions are made to the information recorded in the electromagnetic record, these facts and contents can be confirmed.

3-2. The information recorded in the electromagnetic record cannot be corrected or deleted.

4. Establish rules for administrative procedures to prevent unauthorized corrections and deletions of the electromagnetic records, operate in accordance with said rules, and keep said rules in place when storing the electromagnetic records.

Therefore, when uploading evidence to the evidence management service providing server 8000 manually, in order to "ensure authenticity," it is necessary to establish, for example, the above-mentioned 4. administrative procedure regulations. However, as described below, when uploading evidence 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.

In addition, the "search requirements" must meet the following requirements:

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 or in writing in a clear and organized format.

1. You can set the transaction date and other dates, transaction amount, and trading partner as search conditions.

2. Ability to search by specifying date or amount range.

3. Ability to search using conditions that combine two or more arbitrary record items.

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 the electromagnetic records based on their right to question and inspect, there is no need to ensure that there is a function that allows the specification of the scope and the combination of items to be set.

The configuration for satisfying the "search requirements for evidence" when going via the sales management service provider server 3000 will be described later.

Figure 2 is a functional block diagram to explain the functional configuration of the sales management service providing server 3000.

Referring to FIG. 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 storage unit 3300 for storing data in a non-volatile manner.

The memory unit 3300 stores a billing management database.

The billing management database includes a sales book database 3310, sales history data 3320, journal entry data 3330, billing management data 3340, billing management history data 3350, and operator registration data 3360.

The billing management database can be realized as a relational database, an object relational database, an object database, etc., but the data structure is not important.

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 column-oriented database management system, in which data in the same column is stored in a physically close area.

In the following, as an example, the billing management database will be described as a relational database.

In this case, 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" or "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.

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 or 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.

The table data writing process MD3110 is prohibited from accessing the sales history data 3320 and the billing management history data 3350, and writing, modifying, deleting, or other editing of this data cannot be performed from the sales management department terminal 2000.

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.

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 that executes the process of transferring the journal data created by the table data journal creation MD 3140 to the accounting service providing server 4000.

Although not limited to this, the accounting software linkage MD3150 can be configured to have a transcription format for commercially available accounting software preregistered, 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.

The calculation processing unit 3100 further includes a billing management module (hereinafter, billing management MD) 3160 that manages order data, issues quotations, manages delivery notes, issues invoices, saves invoices, and so on, in response to operations and instructions from the sales management department terminal 2000, registers the data as billing management data 3340, and performs the specified processing. The table data writing processing MD 3110 has a function of performing editing processes such as adding new data and modifying/deleting 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 billing management history data 3350.

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, which is similar to the sales history data 3320.

The billing management database also has users of the sales management service server 3000 registered in advance as operator registration data 3360. When accessing the database, authentication is performed using a password or other means, and editing processes such as new data additions, corrections, and deletions performed through operations or instructions from the sales management department terminal 2000 are recorded in association with the operator.

Figure 3 is a block diagram illustrating the hardware configuration of the sales management service providing server 3000 shown in Figure 2.

As described above, the sales management service providing server 3000 may be configured so that a computing device (CPU: Central Processing Unit) within its own housing executes the arithmetic processing, or part of the program processing may be executed on another server. In the following description, it is assumed that a computing device within its own housing executes the arithmetic processing.

Note that although the sales management department terminal 2000, accounting department terminal 2300, accounting service providing server 4000, and evidence management service providing server 8000 differ in CPU processing power, the hardware configuration is basically the same, so the description will not be repeated.

Referring to FIG. 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. In addition, each unit of the sales management service providing server 3000 is connected via a bus 3007.

The CPU 3100 reads 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.

RAM3200 is, for example, a volatile memory, and has a work area for temporarily storing various programs and data read by CPU3100.

The storage unit 3300 is configured, for example, with a non-volatile storage device such as a hard disk drive (HDD), a solid state drive (SSD), or a flash memory. 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 claim management database.

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.

The display unit 3005 is configured, for example, by an LCD (Liquid Crystal Display) or an organic EL (Electroluminescence) display. The display unit 3005 displays the results of application program processing, the contents of input via the operation unit 3004, etc., on a display screen in accordance with a control signal output from the CPU 3100.

The communication interface 3002 is, for example, configured with 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, to transmit and receive data.

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 information display input programs such as a browser.

When distributed, the program that enables the sales management service providing server 3000 to function as a computer device does not necessarily need to include an operating system (OS) that causes the computer itself to execute functions such as an information processing device. The program only needs to include instructions that call up appropriate functions (modules) in a controlled manner and produce the desired results. How computer systems operate is well known, so a detailed explanation will be omitted.

Furthermore, the CPU 3100 may also be a one-core processor or a multiple-core processor. That is, it may be a single-core processor or a multi-core processor.

Figure 4 is a conceptual diagram showing an example of an editing process for book sales data 3310.

Although not limited to this, if the sales book data 3310 is a relational database, the sales history data 3320 may be associated with each item of a tuple of the sales book data that can be added, modified, or deleted. Alternatively, the configuration is not limited to this, as long as it can be associated with the history of additions, modifications, and deletions to the sales book data.

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, and whether the transaction is accounts receivable or cash. 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 pieces of data are written is called a "field."

Note that the sales book data 3310 and sales history data 3320 shown in FIG. 2 are designed to be linked with other commercially available accounting software, as described below.

In addition, instead of posting a journal entry to the accounting software each time a correction or deletion is made, the system is set up so that only the minimum necessary journal entries are posted. In other words, no matter how many corrections are made in sales management, only the posted entries will be recorded as red slips.

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.

Refer to Figure 4 to explain how correction and deletion history works.

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 value 200, and the sales data is then deleted.

Figure 5 is a conceptual diagram showing an example of the editing process for the sales book data 3310 shown in Figure 4 and the corresponding history data stored in the sales history data 3320.

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 writing 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 records the update category of "1: Addition".

3) For example, in processing step 3, when a user operates the sales management department terminal 2000 to correct the amount from 100 to 200 in the sales input, 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 process MD3110 corrects and overwrites the content of the sales book data 3310.

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: Deleted." The table data writing processing MD3110 deletes the sales book data from the sales book data 3310.

Figure 6 is a conceptual diagram showing an example of the editing process for sales book data 3310 and the corresponding history data stored in sales history data 3320, as well as journal entry data 3330 when journal entry processing is performed.

Figure 9 is a flowchart showing the process of adding, editing, accounting for, and posting sales data as shown in Figures 6 to 8.

Referring to Figures 6 and 9, first, as shown in Figure 6(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 (S100), the table data writing process MD3110 makes the new addition to the sales book data 3310 (S102), and at the same time, as shown in Figure 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 records "1: Addition" as the update category.

Note that at this point, the transcription process of the journal data to the accounting service provider server 4000 has not been executed, so the transcription flags for the sales book data and sales history data are recorded as "0: Not Transcribed."

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 black voucher journal entry (accounts receivable 100/sales 100) data based on the sales book data and records it in the journal entry data 3330 (S108). For this journal entry data, the accounting software linkage module 3150 executes a posting process to the accounting service provider 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".

Figure 7 is a conceptual diagram showing an example of an editing process for sales book data 3310 following the process in Figure 6, and the corresponding history data stored in sales history data 3320, as well as journal entry data 3330.

Referring to Figures 7 and 9, first, as shown in Figure 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 Figure 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".

Following the processing of FIG. 7, FIG. 8 is a conceptual diagram showing the process of posting journal entries to the sales book data 3310 and the corresponding history data stored in the sales history data 3320, as well as an example of journal entry data 3330.

8 and 9, as shown in FIG. 8(a), when a user instructs journalization processing based on the revised amount 200 of the sales book data by operating the sales management department terminal 2000, the table data journalization creation MD 3140 creates red slip journalization (accounts receivable △100/sales △100) data from the transfer flag of the sales history data immediately before "2: revised amount posted" is "1: data posted" (S120), and creates black slip journalization (accounts receivable 200/sales 200) data from the revised but unposted sales book data (S122), and records it in the journalization data 3330. The accounting software linkage module 3150 executes the transfer processing to the accounting service provider server 4000 for this journalization 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.

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."

The following further describes the editing process for the sales book data 3310 in FIG. 8 and the corresponding history data stored in the sales history data 3320, as well as the journal data 3330.

Figure 10 is a conceptual diagram showing an example of the editing process of the sales book data 3310 performed following Figure 8, and the corresponding history data stored in the sales history data 3320, as well as the journal entry data 3330.

Figure 10 shows the case where, after the red and black journal entries in Figure 8 and their posting process, further corrections are made to the sales book data, but no journal entries are created.

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 the sales book data 3310 to 150, the table data write process MD3110 amends the amount in the sales book data 3310, and as shown in FIG. 10(b), the table data history recording MD3130 records the amended amount in the sales history data 3320. 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".

Figure 11 is a conceptual diagram showing an example of the editing process performed on the sales book data 3310 following Figure 10, and the corresponding history data stored in the sales history data 3320, as well as the journal entry data 3330.

Figure 11 shows the case where the sales book data is further deleted after the post-transcription amount correction process in Figure 10.

That is, first, as shown in FIG. 11(a), when the amount of 150 is deleted from the sales slip amount in the sales book data 3310 by user operation on the sales management department terminal 2000, the table data writing process MD3110 deletes the amount from the sales book data 3310, and as shown in FIG. 11(b), the table data history recording MD3130 records the amount before the deletion in the sales history data 3320. At this time, the table data history recording MD3130 leaves the posting flag in the sales history data as "2: Correction of posted amount" and records the update category flag of the sales history data as "4: Delete".

Figure 12 is a conceptual diagram showing the process of posting journal entries to the sales book data 3310 after the amount deletion process in Figure 11, and the corresponding history data stored in the sales history data 3320, as well as an example of journal entry data 3330.

Referring to FIG. 12, as shown in FIG. 12(a), when a user instructs journal processing after deleting the sales book data through operation at the sales management department terminal 2000, the table data journal creation MD 3140 creates red slip journal entry (accounts receivable △200/sales △200) data from the transfer flag of the sales history data that is immediately before "2: Correction of posted data" and the transfer flag is "1: Posted data", and records this 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.

In addition, in FIG. 10, the posting flag indicates that the revised amount of sales book data 150 has not been posted, so the table data journal creation MD3140 does not create red-transfer journal data.

The accounting software linkage module 3150 transfers the journal data created in the above manner to the accounting service provider server 4000. In response to this processing, the table data history recording MD3130 maintains "4: Delete" as the sales history data update category flag for the sales history data.

As a result, when the accounting service provider server 4000 totals the accounting history, the accounts receivable becomes 0/sales becomes 0, which is consistent with the sales data in the sales management service provider server 3000.

Through the above processing, in the sales book data 3310, new additions, whether or not posting to the accounting software, and corrections after posting are managed by the posting flag, and in the sales history data 3320, new additions, whether or not posting to the accounting software, and corrections after posting are managed by the posting flag in association with the value of the sales book data itself, and the status of new additions, corrections, and deletions is managed by the update category flag, and based on these flags, red transfer journal entries and black transfer journal entries are created and posted to the accounting software when journalizing and posting. With this configuration, the sales management system records all history of corrections and deletions, and in the journalizing and posting processes, it becomes possible to integrate sales data in cooperation with external accounting software running on the accounting service provider server 4000.

Figure 13 shows an example of a sales update history inquiry screen displayed on the display unit of the sales management department terminal 2000.

In the operator registration data 3360, the administrator can also use "functional restrictions by person in charge" to restrict editing operations such as new additions, modifications, and deletions by that person in charge.

For example, you can set the function restrictions for a specific operator so that they can only view sales data.

Figure 13 shows an example of a sales history inquiry screen.

The lower box 200 displays the person in charge of the new addition/correction/deletion operation, the date and time, and the number of history entries. By clicking the "<" or ">" button, you can also move to the previous or next history screen.

In FIG. 13, it is shown that the administrator last modified the file at 11:45:59 on 1/11/2023.
(Regarding collaboration with electronic document storage services)

Figure 14 shows the account relationships managed by the sales management service provider server 3000.

Referring to FIG. 14, the relationship between users who use the electronic evidence storage service providing server 8000 via the sales management service providing server 3000 is as follows:

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.

The management account for the sales management system (sales management service provider server 3000) has the authority to add, edit, and delete contractors, change passwords, and set up company-wide operations, check accounts, and view and download electronic vouchers.

Contractor B's administrator account has the authority to check contract information, edit his/her own account, change password, and add, edit, delete, and change password for customer accounts. In addition, he/she can set up operations for each company, check all customer accounts, upload electronic vouchers to customers, and upload electronic vouchers received from other companies, as well as view and download electronic vouchers.

Customer C's account has the ID of Contractor B with whom they do business, and can edit their own account and change their password, as well as view and download their company's electronic vouchers received from Contractor B.

Figure 15 is a conceptual diagram showing the flow of data when issuing an invoice using the sales management service provider server 3000.

Figure 16 is a conceptual diagram showing the flow of electronic ledger data in the sales management service provider server 3000.

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 but not limited to, in the local storage 2400 of the sales management department terminal 2000.

Now, on the other hand, referring to Figures 15 and 16, for customers of users of the sales management service providing server 3000, 1) a customer account is registered from the sales management department terminal 2000.

After that, 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), receipt of purchase orders (3 in Figure 15), etc. are carried out via the sales management service providing server 3000.

After that, in response to an operation from the sales management department terminal 2000, 2) the invoice is uploaded to the evidence electronic storage service providing server 8000 via the sales management service providing server 3000.

The original data of the invoice is uploaded, for example, as PDF (Portable Document Format) data. Note that the format of the original data is not limited to PDF, and may be other image formats such as bmp, jpeg, and png.

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 it can add searchable data such as the transaction date and other dates, transaction amount, and business partner as electronic data to the original invoice data, and then upload it to the electronic evidence storage service providing server 8000.

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 Bookkeeping Act. 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 electronic voucher storage service providing server 8000.

When the original invoice data is uploaded to the electronic voucher 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.

In response to this, the client terminal 2800 becomes able to download 5) the original data of the invoice from the electronic evidence storage service providing server 8000.

In this case, by going through the sales management service providing server 3000, there is no need to store a copy of the invoice data on the electronic evidence storage service providing server 8000.

If the sales management service provider server 3000 is not used, the electronic voucher storage service provider server 8000 must store both the original data and the copy data, and costs increase by the amount of storage space required for the copy data. Also, to satisfy the "search requirements," it is generally necessary to use a character reading function (OCR (Optical Character Recognition) function) to read the data required for the search from the PDF data of the invoice. However, in this case, it is unavoidable that a certain percentage of character errors will occur due to reading errors.

By passing through the sales management service provider server 3000, such character reading errors can be avoided.

As described above, the sales management system and sales management program described in the embodiment can 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 other laws.

In addition, according to the sales management system and sales management program described in the embodiment, it is possible to execute accounting processing that is consistent with the accounting software while leaving the revision history in an unchangeable state on the sales management system side.

In addition, the sales management system and sales management program described in the embodiment can satisfy the conditions required by the Electronic Bookkeeping Act and other laws, while reducing the amount of data stored on an external server and reducing search errors.

The embodiments disclosed herein are illustrative 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.

2 network, 1000 sales management system, 2000 sales management department terminal, 2300 accounting department terminal, 3000 sales management service providing server, 3002 communication 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 (7)

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. 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. 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. 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. 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. 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. 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 .

Images