Program, information processing metho, and information processing system
The program addresses the challenge of efficiently processing invoice-related documents by identifying eligible data and generating draft data for qualified return invoices, thereby simplifying the creation and bookkeeping of these documents.
Patent Information
- Application Number
- JP2023084775
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-23
- Publication Date
- 2024-12-05
- Estimated Expiration
- 2043-05-23
AI Technical Summary
The existing technologies face challenges in efficiently processing documents related to invoice systems, such as qualified invoices and qualified return claims, particularly with the introduction of the Eligible Invoice Storage System in October 2023.
A program is provided that identifies eligible bill data, generates draft data based on this data, and includes predetermined data for creating qualified return invoices, facilitating efficient processing of these documents.
This solution enables efficient execution of processing related to invoice systems, simplifying the creation of qualified invoices and return claims by reducing the effort required for data input and enhancing bookkeeping reversals.
Smart Images

Figure 2024168263000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a program, an information processing method, and an information processing system. [Background technology]
[0002] In the prior art, there is disclosed a technology capable of providing an information processing device, an information processing method, and a program that enable confirmation by referring to the previous month's invoice or the next month's invoice (Patent Document 1). [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2023-048783 A Summary of the Invention [Problem to be solved by the invention]
[0004] By the way, with the introduction of the qualified invoice storage method (invoice system) on October 1, 2023, it will be necessary to prepare documents related to the invoice system, such as qualified invoices and qualified refund invoices.
[0005] In view of the above circumstances, the present invention provides a technique that enables efficient processing of documents related to the invoice system, such as qualified invoices and qualified refund invoices. [Means for solving the problem]
[0006] According to one aspect of the present invention, a program is provided. The program causes a computer to execute the following steps: In the identification step, qualified invoice data is identified, and the qualified invoice data is data of a qualified invoice created by a qualified invoice issuer. In the generation step, draft data is generated based on the identified qualified invoice data, and the draft data is data that includes specified data for creating a qualified refund invoice, and the specified data is data that includes at least a portion of the data included in the qualified invoice data.
[0007] This makes it possible to provide technology that enables efficient processing of documents related to the invoice system, such as qualified invoices and qualified refund invoices. [Brief description of the drawings]
[0008] [Figure 1] 1 is a diagram illustrating an example of a system configuration of an information processing system 1 according to a first embodiment. [Diagram 2] 2 is a diagram illustrating an example of a hardware configuration of a bill server device 2 according to the first embodiment. FIG. [Diagram 3] 2 is a diagram showing an example of the hardware configuration of an accounting server device 3 according to the first embodiment. FIG. [Figure 4] 2 is a diagram illustrating an example of a hardware configuration of a client device 4 according to the first embodiment. [Diagram 5] 2 is an example of a block diagram showing functions realized by a processor 21 of the invoice server device 2 according to the first embodiment. [Figure 6] 2 is an example of a block diagram showing functions realized by a processor 31 of the accounting server device 3 according to the first embodiment. FIG. [Figure 7] FIG. 2 is a diagram showing an example of a sequence diagram according to the first embodiment. [Figure 8] FIG. 2 is a diagram showing an example of an invoice screen 5 according to the first embodiment. [Figure 9] FIG. 9 is a diagram showing an example of an invoice screen 5 displayed in response to pressing a copy / convert button 510 in FIG. 8. [Figure 10] FIG. 10 is a diagram showing an example of an invoice screen 6 displayed in response to pressing the draft data generation button 512 in FIG. [Figure 11] FIG. 2 is a diagram showing an example of an invoice screen 7 according to the first embodiment. [Figure 12] FIG. 2 is a diagram showing an example of a checkout screen 8 according to the first embodiment. [Figure 13] FIG. 11 is a diagram showing an example of an invoice screen 9 according to the second embodiment. [Figure 14] FIG. 10 shows an example of a billing total amount screen 1000. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described with reference to the drawings. Various characteristic features shown in the following embodiments can be combined with each other.
[0010] 1. Explanation of terms First, each term used in this specification will be explained.
[0011] In this specification, the "program" for realizing the software mentioned may be provided as a non-transitory computer-readable recording medium, or may be provided so as to be downloadable from an external server, or may be provided so that the program is started on an external computer and its functions are realized on a client terminal (so-called cloud computing).
[0012] In this specification, the term "unit" may include, for example, a combination of hardware resources implemented by a circuit in the broad sense and software information processing that can be specifically realized by these hardware resources. In addition, various information is handled in this embodiment, and this information is represented by, for example, physical values of signal values representing voltage and current, high and low signal values as a binary bit collection consisting of 0 or 1, or quantum superposition (so-called quantum bits), and communication and calculation can be performed on the circuit in the broad sense.
[0013] In this specification, a "circuit" in a broad sense refers to a circuit realized by at least appropriately combining a circuit, circuitry, a processor, a memory, etc. In other words, it includes an application specific integrated circuit (ASIC), a programmable logic device (e.g., a simple programmable logic device (SPLD), a complex programmable logic device (CPLD), and a field programmable gate array (FPGA)), etc.
[0014] A "qualified invoice" is a document that a seller issues to a buyer to communicate the exact applicable tax rate and amount of consumption tax. A qualified invoice is issued by a business that is registered as a qualified invoice issuer. A qualified invoice is also called an invoice.
[0015] "Qualified invoice issuing business" refers to a taxable business that is authorized to issue qualified invoices and qualified refund invoices. In addition, qualified invoice issuing business may include at least one of the following: a business registered under the provisions of Article 57-2, paragraph 1 of the Consumption Tax Act that came into force on March 31, 2016, a business that is in a roughly equivalent position due to the legal amendments to the Consumption Tax Act that will be implemented on or after March 31, 2016, and a business that is in a roughly equivalent position to a qualified invoice issuing business under other laws.
[0016] "Qualified invoice data" is data that represents a qualified invoice created by a qualified invoice issuer. Qualified invoice data includes issuer data, delivery date data, transaction content data, amount data, tax rate data, and tax amount data. Qualified invoice data may also include customer data, invoice date data, address data, remarks data, and identification data. The issuer data is data that indicates the name or title of the qualified invoice issuer and the registration number. The registration number consists of the letter T and a 13-digit number. The provision date data is the data showing the date on which the assets or services related to the transaction were provided. On a qualified invoice, the provision date data is the data showing the date on which the taxable assets were transferred, etc. - Transaction content data is data that indicates the content of the assets or services related to the transaction. On a qualified invoice, the transaction content data is data that indicates the content of the assets or services related to the transfer, etc. of taxable assets (in the case where the transfer, etc. of taxable assets is a transfer, etc. of assets eligible for tax reduction, the content of the assets and the fact that it is a transfer, etc. of assets eligible for tax reduction). Amount data is data showing the amount of a transaction. On a qualified invoice, amount data is data showing the total amount of the tax-excluded or tax-inclusive value of the transfer of taxable assets, etc., categorized by tax rate. Tax rate data is data showing the applicable tax rate for a transaction. On a qualified invoice, tax rate data is data showing the applicable tax rate for the transfer of taxable assets, etc. Tax amount data is data showing consumption tax amounts etc. categorized by tax rate. · Business partner data is data that indicates the name or title of the business entity to which the document is to be delivered. The billing date data indicates the date on which the billing for sales is made. · Address data is data that indicates the address of a business partner. The remarks data is text data indicating information as remarks for the invoice. -Identification data is unique data assigned to a qualified invoice and is data that can identify (specify) the qualified invoice.
[0017] A "qualified refund invoice" is a document issued by a qualified invoice issuer when a return of consideration related to sales is made. A qualified refund invoice can be issued by a business that is registered as a qualified invoice issuer. A qualified refund invoice is also called a return invoice. Examples of return of consideration related to sales include returns, discounts, rebates, early departure fees for ships paid by marine transport businesses, sales incentives paid by businesses, business volume dividends paid by cooperatives, sales discounts, and sales rebates that apply to both taxable and non-taxable sales.
[0018] "Qualified refund invoice data" is data created by a qualified invoice issuer and indicates a qualified refund invoice that refunds at least a portion of the sales linked to the qualified invoice. Qualified refund invoice data includes issuer data, provision date data, transaction content data, amount data, tax rate data, tax amount data, address data, and remarks data. Qualified refund invoice data may also include business partner data, refund data, and identification data. -On a qualified refund invoice, the issuer data is data that indicates the name or title and registration number of the business entity that issued the qualified invoice. On a qualified refund invoice, the date of provision data is the date on which the consideration related to the sales is returned, etc., and the date on which the taxable assets that are the basis for the return, etc., of the consideration related to the sales are transferred, etc. (in the case of sales for which a qualified invoice is issued, it may be a certain period within the tax period). On a qualified refund claim form, the transaction details data is data showing the details of the assets or services related to the transfer of taxable assets that is the basis for the return of the consideration related to sales (if the transfer of taxable assets that is the basis for the return of the consideration related to sales is a transfer of assets eligible for tax reduction, the details of the assets and the fact that it is a transfer of assets eligible for tax reduction). - On a qualified refund invoice, the amount data is the data that shows the total amount of the tax-excluded or tax-included amount of the refund of consideration related to sales, etc., categorized by tax rate. On a qualified refund invoice, the tax rate data is data that indicates the applicable tax rate for the amount of the refund of consideration related to sales, etc. On a qualified refund invoice, the tax amount data is data that indicates the amount of consumption tax, etc., related to the amount of the refund of the consideration related to sales. -Even on a qualified refund claim form, the business partner data is data that indicates the name or title of the business entity to which the document is to be issued. - On a qualified refund claim form, the refund data is the data showing the date on which the refund or reduction will be made due to the return, discount or rebate of taxable assets. -Even on a qualified refund invoice, the address data is data that indicates the address of the business partner. -Even on a qualified refund invoice, the remarks data is data that indicates text that shows information as a remark on the invoice. - On a qualified refund claim, on a qualified refund claim, identification data is data that can specify (identify) qualified invoice data that corresponds to one qualified refund claim data.
[0019] The qualified refund invoice data may be data created based on the draft data. This "draft data" is data that includes the specified data for creating a qualified refund invoice. The issuer data, delivery date data, transaction content data, amount data, tax rate data, tax amount data, customer data, address data, remarks data, and identification data of the qualified invoice data are compatible with the issuer data, delivery date data, transaction content data, amount data, tax rate data, tax amount data, customer data, address data, remarks data, and identification data of the qualified refund invoice data. Therefore, the specified data is data that includes at least one of the issuer data, delivery date data, transaction content data, amount data, tax rate data, tax amount data, customer data, address data, remarks data, and identification data included in the qualified invoice data. Note that the specified data does not include data corresponding to the refund data of the qualified refund invoice data.
[0020] [Embodiment 1] 2. System configuration of information processing system 1 Next, the system configuration of the information processing system 1 according to the first embodiment will be described with reference to FIG.
[0021] FIG. 1 is a diagram showing an example of the system configuration of an information processing system 1 according to the first embodiment. As shown in FIG. 1, the information processing system 1 includes a billing server device 2, an accounting server device 3, a client device 4, and a network N. The billing server device 2, the accounting server device 3, and the client device 4 are configured to be able to communicate with each other via the network N. As a result, the billing server device 2, the accounting server device 3, and the client device 4 can transmit or receive various information to each other. The billing server device 2, the accounting server device 3, and the client device 4 are examples of information processing devices and are not limited to the present embodiment. The client device 4 may be any of a PC (Personal Computer), a tablet computer, a smartphone, and the like. The billing server device 2 and the accounting server device 3 may be composed of a single server or may be composed of multiple servers. There may be multiple client devices 4. Here, the system exemplified by the information processing system 1 is composed of one or more devices or components. Therefore, each of the billing server device 2, the accounting server device 3, and the client device 4 is included in the system exemplified by the information processing system 1 even if it is a single device.
[0022] 2. Hardware Configuration Next, the hardware configurations of the invoice server device 2, the accounting server device 3, and the client device 4 of the first embodiment will be described with reference to FIGS.
[0023] 2.1. Hardware configuration of bill server device 2 Fig. 2 is a diagram showing an example of a hardware configuration of the invoice server device 2 according to the embodiment 1. As shown in Fig. 2, the invoice server device 2 has a processor 21, a storage unit 22, and a communication unit 23, and these components are electrically connected via a communication bus inside the invoice server device 2. The invoice server device 2 executes the processing according to the embodiment.
[0024] The processor 21 processes and controls the overall operations related to the invoice server device 2. The processor 21 is, for example, a central processing unit (CPU). The processor 21 reads out a predetermined program stored in the storage unit 22 and executes processing based on the program, thereby realizing various functions related to the invoice server device 2, for example, processing related to Figs. 7 to 14 described below. The processor 21 is not limited to being single, and may be implemented with multiple processors 21 for each function. Also, a combination of these may be used.
[0025] The memory unit 22 stores various information defined by the above description. This can be implemented, for example, as a storage device such as a solid state drive (SSD) that stores various programs and the like related to the invoice server device 2 executed by the processor 21, or as a memory such as a random access memory (RAM) that stores temporarily required information (arguments, arrays, etc.) related to the calculation of the programs. The memory unit 22 stores various programs and variables related to the invoice server device 2 executed by the processor 21, and data and the like used when the processor 21 executes processing based on the programs. The memory unit 22 is an example of a storage medium.
[0026] The communication unit 23 is preferably a wired communication means such as USB, IEEE1394, Thunderbolt (registered trademark), wired LAN network communication, etc., but may also include wireless LAN network communication, mobile communication such as LTE / 3G / 4G / 5G, BLUETOOTH (registered trademark) communication, etc. as necessary. In other words, it is more preferable to implement it as a collection of multiple communication means. In other words, the invoice server device 2 may communicate various information from the outside via the communication unit 23.
[0027] 2.2. Hardware configuration of accounting server device 3 Fig. 3 is a diagram showing an example of the hardware configuration of the accounting server device 3 according to the first embodiment. As shown in Fig. 3, the accounting server device 3 has a processor 31, a memory unit 32, and a communication unit 33, and these components are electrically connected via a communication bus inside the accounting server device 3. The accounting server device 3 executes the processing according to the embodiment. For the processor 31, memory unit 32, and communication unit 33 of the accounting server device 3, please refer to the processor 21, memory unit 22, and communication unit 23 of the invoice server device 2.
[0028] 2.3. Hardware Configuration of Client Device 4 FIG. 4 is a diagram showing an example of a hardware configuration of the client device 4 according to the first embodiment. The client device 4 is used by a user. As shown in FIG. 4, the client device 4 has a processor 41, a storage unit 42, a communication unit 43, an input unit 44, and an output unit 45, and these components are electrically connected inside the client device 4 via a communication bus. The client device 4 executes the process according to the embodiment. For the processor 41, the storage unit 42, and the communication unit 43 of the client device 4, please refer to the processor 21, the storage unit 22, and the communication unit 23 of the invoice server device 2.
[0029] The input unit 44 may be included in the housing of the client device 4 or may be externally attached. For example, the input unit 44 may be implemented as a touch panel integrated with the output unit 45. If it is a touch panel, the user can input a tap operation, a swipe operation, or the like. Of course, a switch button, a mouse, a QWERTY keyboard, or the like may be adopted instead of the touch panel. That is, the input unit 44 accepts an input based on an operation performed by the user. The input is transferred as a command signal to the processor 41 via a communication bus, and the processor 41 can execute a predetermined control or calculation as necessary.
[0030] The output unit 45 can function as a display unit of the client device 4. The output unit 45 may be included in the housing of the client device 4, for example, or may be attached externally. The output unit 45 displays a screen of a Graphical User Interface (GUI) that can be operated by a user. This is preferably implemented by using display devices such as a CRT display, a liquid crystal display, an organic EL display, and a plasma display, depending on the type of the client device 4.
[0031] 3.1. Functional configuration of the processor 21 of the bill server device 2 In this section, the functional configuration of the first embodiment will be described with reference to Fig. 5. Fig. 5 is an example of a block diagram showing functions realized by the processor 21 of the invoice server device 2 according to the first embodiment. The processor 21 of the invoice server device 2, which is an example of the information processing system 1, includes an information transmitting / receiving unit 210, an identifying unit 211, a generating unit 212, a notifying unit 213, and a display control unit 214. As described above, information processing by software stored in the storage unit 22 is specifically realized by the processor 21, which is an example of hardware, and can be executed as each functional unit included in the processor 21.
[0032] The information transmitting / receiving unit 210 is configured to accept, receive, or acquire various information from other devices via the network N and the communication unit 23. In addition, the information transmitting / receiving unit 210 is configured to transmit or output various information to other devices via the communication unit 23 and the network N.
[0033] The identification unit 211 identifies qualified invoice data.
[0034] The generation unit 212 generates draft data based on the identified qualified invoice data.
[0035] If the amount of the transaction related to the qualified refund invoice is less than a specified amount, or if the business partner related to the qualified refund invoice is a tax-exempt business, the notification unit 213 notifies that a qualified refund invoice does not need to be issued.
[0036] The display control unit 214 controls the screen data to be displayed on the output unit 45 of the client device 4. Note that the screen data may be visual information itself, such as a screen, an image, an icon, text, etc., generated in a manner that is visible to the user, or may be rendering information for displaying visual information, such as a screen, an image, an icon, text, etc., on various terminals.
[0037] The information transmitting / receiving unit 210, the identifying unit 211, the generating unit 212, the notifying unit 213, and the display control unit 214 will be described in detail later.
[0038] 3.2. Functional configuration of the processor 31 of the accounting server device 3 In this section, the functional configuration of the first embodiment will be described with reference to Fig. 6. Fig. 6 is an example of a block diagram showing functions realized by the processor 31 of the accounting server device 3 according to the first embodiment. The processor 31 of the accounting server device 3, which is an example of the information processing system 1, includes an information transmitting / receiving unit 310, an acquisition unit 311, a data output unit 312, and a display control unit 313. As described above, information processing by software stored in the storage unit 32 is specifically realized by the processor 31, which is an example of hardware, and can be executed as each functional unit included in the processor 31.
[0039] The information transmitting / receiving unit 310 is configured to accept, receive, or acquire various information from other devices via the network N and the communication unit 33. In addition, the information transmitting / receiving unit 310 is configured to transmit or output various information to other devices via the communication unit 33 and the network N.
[0040] The acquisition unit 311 acquires qualified invoice data and qualified refund invoice data.
[0041] The data output unit 312 outputs reversal data for performing a reversal entry in the bookkeeping of the qualified invoice issuer based on the qualified refund invoice data.
[0042] The display control unit 313 controls the screen data to be displayed on the output unit 45 of the client device 4 .
[0043] The information transmitting / receiving unit 310, the acquiring unit 311, the data output unit 312, and the display control unit 313 will be described in detail later.
[0044] 4. Operation in Information Processing System 1 In this section, an example of a preferable information process executed by the information processing system 1 of this embodiment will be described.
[0045] In this specification, it is assumed that various pieces of information that have been transmitted or received are stored in the memory unit of each device used for transmission or reception. For example, when information is transmitted from the billing server device 2 to the accounting server device 3, the information is stored in the memory unit 22 of the billing server device 2 and the memory unit 32 of the accounting server device 3. The information is also stored in the memory unit 42 of the client device 4.
[0046] In this specification, the invoice server device 2 may be described with some of the information processing using the communication unit 23 and the network N omitted. For example, the processor 21 (information transmission / reception unit 210) transmitting and receiving information to and from other devices via the communication unit 23 and the network N may be described simply as the processor 21 (information transmission / reception unit 210) transmitting information to other devices, or simply as the processor 21 (information transmission / reception unit 210) receiving information from other devices. Such descriptions are also used for the information processing performed by the processor 31 (information transmission / reception unit 310) of the accounting server device 3 and the processor 41 of the client device 4.
[0047] In this specification, some of the descriptions of information processing using the input unit 44 of the client device 4 may be omitted. For example, the processor 41 receiving a predetermined input through a user's operation on the input unit 44 may be simply described as the processor 41 receiving a predetermined input from the user.
[0048] In this specification, the information processing for displaying information on the output unit 45 may be described as the processor 41 simply displaying certain information on the output unit 45, or indirectly as the display control unit 214 (or the display control unit 313) displaying certain information on the output unit 45. In this case, the following information processing is executed. That is, the processor 41 receives an instruction from the user to display information on the screen. The processor 41 transmits the instruction to the invoice server device 2 (or the accounting server device 3). The processor 41 receives the instruction from the invoice server device 2 (or the accounting server device 3). The display control unit 214 (or the display control unit 313) generates display information based on the instruction. The information transmission / reception unit 210 (or the information transmission / reception unit 310) transmits the generated display information to the client device 4. The processor 41 receives the generated display information from the invoice server device 2 (or the accounting server device 3). The processor 41 controls the display on the output unit 45 based on the generated display information.
[0049] First, an example of information processing according to the first embodiment will be described with reference to Figs. 7 to 12. In the first embodiment, an example will be described in which qualified refund invoice data is created from qualified invoice data using an invoice service, and reversal data is output using an accounting service. The invoice service is a service capable of creating qualified invoices or qualified refund invoices in response to user instructions, and is a service provided by the invoice server device 2. The accounting service is a service capable of processing and managing accounting in response to user instructions, and is a service provided by the accounting server device 3.
[0050] 4.1. Overview of information processing First, an overview of information processing according to the first embodiment will be described with reference to the sequence diagram of Fig. 7. Fig. 7 is a diagram showing an example of the sequence diagram according to the first embodiment.
[0051] In S1, the processor 41 of the client device 4 accepts the identification of qualified invoice data from one or more qualified invoice data created in the past based on an operation from a user. The identification of qualified invoice data is accepted via the invoice screen 5 shown in Figures 8 and 9, which will be described later.
[0052] In S2, the processor 41 of the client device 4 transmits information about the identified qualified invoice data to the invoice server device 2. The information transmitting and receiving unit 210 of the invoice server device 2 receives information about the identified qualified invoice data from the client device 4.
[0053] In S3, the identification unit 211 of the invoice server device 2 identifies qualified invoice data based on the received data. In S4, the generation unit 212 of the invoice server device 2 generates draft data based on the specified qualified invoice data.
[0054] In S5, the information transmitting / receiving unit 210 of the invoice server device 2 transmits the draft data to the client device 4. The processor 41 of the client device 4 receives the draft data from the invoice server device 2.
[0055] In S6, the processor 41 of the client device 4 accepts data input or editing of the draft data based on an operation from the user in order to create qualified refund invoice data. The acceptance of data input or editing is performed via an invoice screen 6 shown in Fig. 10, which will be described later. If no data input or editing is performed, S6 may be omitted.
[0056] In S7, the processor 41 of the client device 4 transmits information on the qualified refund claim data including the input data to the invoice server device 2. The information transmitting / receiving unit 210 of the invoice server device 2 receives information on the qualified refund claim data including the input or edited data from the client device 4.
[0057] In S8, the generation unit 212 of the invoice server device 2 generates qualified refund invoice data based on the input or edited data. After that, the display control unit 214 of the invoice server device 2 causes the output unit 45 to display image information of the invoice screen 7 shown in FIG. 11, which will be described later.
[0058] In S9, the information transmitting / receiving unit 210 of the invoice server device 2 transmits information on the qualified invoice data and the qualified refund invoice data to the accounting server device 3. The information transmitting / receiving unit 310 of the accounting server device 3 receives information on the qualified invoice data and the qualified refund invoice data from the invoice server device 2.
[0059] In S10, the acquisition unit 311 of the accounting server device 3 acquires the qualified invoice data and the qualified refund invoice data. In S11, the data output unit 312 of the accounting server device 3 outputs reversal data 811 for performing a reversal entry in bookkeeping that corresponds to the journal entry of the acquired qualified invoice data, based on the acquired qualified refund invoice data. The information processing related to the output of the reversal data 811 will be explained below with reference to the accounting screen 8 in FIG. 12. This makes it easy to perform a reversal entry in bookkeeping for a qualified invoice based on the qualified refund invoice data. It is also possible to provide a technology that makes it possible to efficiently execute processing related to qualified refund invoices.
[0060] 4.2 Details of data processing Next, the details of the screens displayed in the first embodiment will be described with reference to Figs. 8 to 12. Fig. 8 is a diagram showing an example of an invoice screen 5 according to the first embodiment. The invoice screen 5 in Fig. 8 is a screen that allows the user to proceed to information processing related to qualified invoices used in the past. The invoice screen 5 includes an invoice list area 50, an invoice operation area 51, and an invoice details area 52.
[0061] The invoice list area 50 is an area where the user can refer to qualified invoices or qualified refund invoices that they have used in the past. The identification unit 211 identifies qualified invoice data or qualified refund invoice data by accepting a selection from the user of any qualified invoice or qualified refund invoice from the invoice list area 50. The display control unit 214 displays the identified qualified invoice data or identified qualified refund invoice data in the invoice operation area 51 and the invoice details area 52.
[0062] The invoice operation area 51 is an area for generating an instruction to start information processing for a qualified invoice or a qualified refund invoice identified in the invoice list area 50. Information processing for a qualified invoice or a qualified refund invoice includes, for example, editing the invoice, duplicating the invoice, converting the invoice to other data, deleting the invoice, generating data for mailing the invoice, sending the invoice by email, converting the invoice to PDF, printing the invoice, and the like. The invoice operation area 51 may include information such as the name or title of the business entity to which the document is to be delivered, the date of invoice creation, and the invoice number. The invoice operation area 51 includes a copy conversion button 510. The display control unit 214 displays the selection area 511 shown in FIG. 9 in response to the user pressing the copy conversion button 510.
[0063] The invoice details area 52 is an area that displays detailed information about the qualified invoice or qualified refund invoice identified in the invoice list area 50. The invoice details area 52 is configured to enable reference of, for example, a preview of the invoice, a history of information processing linked to the invoice, and related documents linked to the invoice.
[0064] Fig. 9 is a diagram showing an example of the invoice screen 5 displayed in response to pressing the copy / convert button 510 in Fig. 8. Compared to Fig. 8, the invoice screen 5 in Fig. 9 further includes a selection area 511.
[0065] Selection area 511 is an area where the start of any of the following information processing can be selected: duplicating a qualified invoice, converting a qualified invoice to an invoice, converting a qualified invoice to a receipt, converting a qualified invoice to a qualified refund invoice, and setting up automatic creation of qualified invoices. Selection area 511 includes a draft data generation button 512 for converting a qualified invoice to a qualified refund invoice.
[0066] The draft data generation button 512 is a button for generating draft data for creating qualified refund invoice data from qualified invoice data. In response to the user pressing the draft data generation button 512, the generation unit 212 generates draft data for qualified refund invoice data in a form including predetermined data including issuer data, transaction content data, amount data, tax rate data, delivery date data, tax amount data, customer data, identification data, address data, and remarks data. In addition, in response to the user pressing the draft data generation button 512, the display control unit 214 displays the invoice screen 6 shown in FIG. 10.
[0067] Figure 10 is a diagram showing an example of the invoice screen 6 displayed in response to pressing the draft data generation button 512 in Figure 9. The invoice screen 6 in Figure 10 is a screen for creating qualified refund invoice data. The invoice screen 6 includes a data input area 60, a data display area 61, and a Complete button 62. The invoice screen 6 displayed in Figure 10 is the screen displayed immediately after the qualified invoice data has been output, and therefore data showing the same information as each piece of data entered in the qualified invoice data has been entered in advance, and needs to be edited by the user.
[0068] The data input area 60 is configured to allow input of data for creating qualified refund invoice data. Each area for inputting data in the data input area 60 displays draft data including predetermined data in a pre-entered form. The data input area 60 includes a business partner input area 600, an issuer input area 601, an identification input area 602, a refund date input area 603, an address input area 604, a description input area 605, a transfer destination input area 606, and a remarks input area 607.
[0069] The supplier input area 600 is an area configured so that supplier data can be input. In the supplier input area 600, the supplier data included in the qualified invoice data (in the example of FIG. 10, "Supplier 1-2") may be input as the specified data.
[0070] The issuer input area 601 is an area configured to allow issuer data to be input. Issuer data as a registration number contained in the qualified invoice data ("IV20230427000001" in the example of FIG. 10) and issuer data as the name of the issuer of the qualified refund invoice ("ABC Company" in the example of FIG. 10) may be input in the issuer input area 601. This allows the issuer data contained in the qualified invoice data to be used as is for the qualified refund invoice data, thereby reducing the effort required to create a qualified refund invoice.
[0071] The identification input area 602 is an area configured to allow identification data to be input. Identification data including alphanumeric characters contained in the qualified invoice data ("IV20230427" in the example of FIG. 10) may be input into the identification input area 602. This makes it easy to identify which qualified invoice a qualified refund invoice was created based on.
[0072] The return date input area 603 is an area configured to allow return data to be input. In the example of FIG. 10, "2023 / 05 / 31" is input as return data in the return date input area 603. The return date input area 603 may also be configured to allow the date of the end of this month or the end of next month to be automatically input in response to pressing a button such as "End of this month" or "End of next month." This makes it possible to accept input of return data from the user that is likely to differ from the content of the qualified return invoice when creating a qualified return invoice.
[0073] The address input area 604 is an area configured to allow address data to be input. The address input area 604 may contain address data that was included in the qualified invoice data (in the example of FIG. 10, "2-2-2 Oyata, Adachi-ku, Tokyo 1200001, Accounting Department, Accounting Officer, Last Name, First Name"). This allows the address data included in the qualified invoice data to be used as is for the qualified refund invoice data, reducing the effort required to create a qualified refund invoice.
[0074] The details input area 605 is an area configured to allow input of the delivery date data 605a, the transaction content data 605b, and the tax rate data 605d. The details input area 605 may have the delivery date data 605a ("April 27, 2023" in the example of FIG. 10), the transaction content data 605b ("ZZZ-000" and "ZZZ-001" in the example of FIG. 10), and the tax rate data 605d ("10%" and "8%" in the example of FIG. 10) that were included in the qualified invoice data input therein. With this configuration, when creating a qualified refund invoice, it is possible to accept inputs from the user of the transaction content data, amount data, tax rate data, and delivery date data that are likely to be the same as the contents of the qualified invoice.
[0075] The details input area 605 is an area configured to allow the amount calculation data 605c to be input. The amount calculation data 605c included in the qualified invoice data may be input as predetermined data in place of the amount data in the details input area 605. The amount calculation data 605c is data that allows the amount data and tax amount data to be calculated, and includes unit price data for each transaction content and quantity data. In the example of FIG. 10, the amount calculation data 605c includes unit price data of "100,000 yen" and quantity data of "2" for "ZZZ-000" with a tax rate of "10%," and includes unit price data of "20,000 yen" and quantity data of "5" for "ZZZ-001" with a tax rate of "8%". The amount calculation data 605c may be determined by its absolute value, and may be treated as the same result whether a positive value or a negative value is input.
[0076] In the example of FIG. 10, the amount data includes data on the total amount of the tax-excluded amount of the return of the consideration related to the sales amount divided by tax rate, such as "200,000 yen" for a transaction with a tax rate of "10%" and "100,000 yen" for a transaction with a tax rate of "8%". This "200,000 yen" is calculated from the unit price of "100,000" and the quantity of "2", and this "100,000 yen" is calculated from the unit price of "20,000" and the quantity of "5". In other words, the amount data is calculated based on the amount calculation data 605c. With this configuration, when creating a qualified refund invoice, it is possible to accept input from the user for calculation of amount data that is likely to be the same as the contents of the qualified invoice.
[0077] In the example of FIG. 10, the tax amount data includes data on consumption tax amount etc. classified by tax rate, such as data on "20,000 yen" for a transaction with a tax rate of "10%" and data on "8,000 yen" for a transaction with a tax rate of "8%". This "20,000 yen" is calculated by applying the tax rate "10%" to "200,000 yen", and this "20,000 yen" is calculated by applying the tax rate "8%" to "100,000 yen". In other words, the tax amount data is calculated based on the amount calculation data 605c and the tax rate data 605d. With this configuration, when creating a qualified refund invoice, it is possible to accept input from the user for calculation of tax amount data that is likely to be the same as the contents of the qualified invoice.
[0078] The transfer destination input area 606 is an area configured so that data on the transfer destination of a bank account (bank name, branch name, account number, account type, account holder, etc.) can be input as return destination data. The transfer destination input area 606 may be configured so that transfer destination data can be input from a registered transfer destination. In the example of FIG. 10, the transfer destination input area 606 has input therein "ABC Bank" as the bank name, "DEFGH Branch" as the branch name, "Regular" as the account type, "1234567" as the account number, and "Kouza Meigi" as the account holder.
[0079] The remarks input area 607 is an area configured to allow remarks data to be input. Remarks data ("Please pay the handling fee" in the example of FIG. 10) that was included in the qualified invoice data may be input in the remarks input area 607. This allows the remarks data included in the qualified invoice data to be used as is for the qualified refund invoice data, thereby reducing the effort required to create a qualified refund invoice.
[0080] In this way, by generating draft data in a manner that includes predetermined data in the data input area 60, it is possible to generate draft data for creating a qualified refund invoice based on the qualified invoice data, making it easier to create a qualified refund invoice. In addition, it is possible to provide a technology that enables efficient execution of processes related to qualified refund invoices.
[0081] The data display area 61 is an area where a preview of the qualified refund invoice is displayed in a visible manner based on the data entered in the data entry area 60. The data display area 61 includes a customer display area 610, an issuer display area 611, an identification display area 612, a refund date display area 613, an address display area 614, a statement display area 615, a transfer destination display area 616, and a remarks display area 617.
[0082] The supplier display area 610 is an area in which the supplier data entered in the supplier input area 600 is displayed in a visually recognizable manner as the supplier of a qualified refund invoice.
[0083] The issuer display area 611 is an area in which the issuer data entered in the issuer input area 601 is displayed in a visible manner as the registration number of the issuer of the qualified refund claim and as the name or title of the issuer of the qualified refund claim.
[0084] The identification display area 612 is an area where the identification data entered in the identification input area 602 is displayed in a visually recognizable manner as the invoice number of a qualified invoice.
[0085] The return date display area 613 is an area in which the return data entered in the return date input area 603 is displayed in a visually recognizable manner as the date on which the return of the consideration related to the sales will be made.
[0086] The address display area 614 is an area in which the business partner address data entered in the address input area 604 is displayed in a visually recognizable manner as the business partner address of the qualified refund invoice.
[0087] The details display area 615 is an area where the provision date data 605a, transaction content data 605b, and tax rate data 605d entered in the details input area 605 are displayed in a visually recognizable manner as the provision date, transaction content, and tax rate data of the qualified refund invoice. The details display area 615 is also an area where the amount data and tax amount data calculated based on the amount calculation data 605c and tax rate data 605d are displayed in a visually recognizable manner.
[0088] The payee display area 616 is an area in which the payee data for the bank account entered in the payee input area 606 is displayed in a visually recognizable manner as the payee data for the bank account of the qualified refund invoice.
[0089] The remarks display area 617 is an area in which text associated with the remarks data input in the remarks input area 607 is displayed in a visually recognizable manner.
[0090] The Complete button 62 is a button for completing the qualified refund claim data based on the data entered in the data entry area 60. In response to the user pressing the Complete button 62, the display control unit 214 displays the claim screen 7 shown in FIG.
[0091] FIG. 11 is a diagram showing an example of an invoice screen 7 relating to embodiment 1. The invoice screen 7 in FIG. 11 is a screen on which the created qualified refund invoice can be confirmed. The invoice screen 7 includes a qualified refund invoice area 70. The qualified refund invoice area 70 is an area in which the qualified refund invoice created based on the data entered in the data input area 60 is displayed. The qualified refund invoice area 70 is also an area in which the data in the data display area 61 is displayed.
[0092] Next, an example of reversing an accounting service based on qualified refund invoice data created by the invoice service will be described with reference to Fig. 12. In response to receiving a user pressing the Complete button 62 in Fig. 11, or in response to receiving an instruction from the user on the invoice service to link with the accounting service, the data output unit 312 outputs reversal data 811 for performing a reversal in the bookkeeping of the qualified invoice issuer based on the qualified refund invoice data. When the display control unit 313 receives an instruction from the user to log in to the accounting service and an instruction to confirm the journalization following the login instruction, it causes the output unit 45 to display the accounting screen 8 shown in Fig. 12.
[0093] 12 is a diagram showing an example of the accounting screen 8 according to embodiment 1. The accounting screen 8 is a screen that displays information related to accounting. The accounting screen 8 in FIG. 12 displays a screen related to journalizing or reversing journalizing in bookkeeping, and includes a narrowing-down area 80 and a journalizing area 81.
[0094] A "journal entry" is a bookkeeping task in which bookkeeping transactions are classified as debits and credits, and the account items and amounts are recorded in the journal. A "reversal entry" is a journal entry that reverses the account items of the debit and credit sides of the journal entry. A reversal entry is also called a reverse entry, cancellation entry, or correction entry.
[0095] The narrowing area 80 is an area for narrowing down information on candidates for journalization or reversal to be displayed in the journalization area 81. The narrowing area 80 is configured to be able to accept conditions such as a start date, an end date, a business partner, and a summary.
[0096] The journal entry area 81 is an area where information related to bookkeeping journal entries or reverse journal entries is displayed. The journal entry area 81 is configured so that the information displayed can be changed according to the conditions received via the narrowing area 80. The journal entry area 81 in FIG. 12 displays journal entry data 810a and 810b and reverse journal entry data 811.
[0097] The journal data 810a and 810b are data for classification in bookkeeping. The journal data 810a and 810b include, for example, a transaction date, a debit account item (e.g., sales amount), a sub-item, a tax category, an amount, a debit account item (e.g., cash, current account, bills receivable, accounts receivable), a tax category, an amount, and a summary. The data output unit 312 outputs the journal data 810a and 810b for classification in the bookkeeping of the qualified invoice issuer based on the acquired qualified invoice data. For example, data corresponding to the amount data included in the qualified invoice data ("220,000 yen" and "108,000 yen") is output as the amount of the journal data 810a and 810b, and data corresponding to the tax rate data 605d included in the qualified invoice data ("10%" and "8%") is output as the tax category of the journal data 810a and 810b. This makes it easier to perform accounting entries based on qualified invoice data. It is also possible to provide a technology that enables efficient processing of qualified invoices.
[0098] The reversal data 811 is data for performing reversal in bookkeeping. The reversal data 811 includes, for example, a transaction date, a debit account item (e.g., sales amount), a sub-item, a tax category, an amount, a debit account item (e.g., cash, current account, bills receivable, accounts receivable), a tax category, an amount, and a summary. The data output unit 312 outputs the reversal data 811 for performing classification in the bookkeeping of the qualified invoice issuer based on the acquired qualified invoice data. More specifically, for example, the data output unit 312 outputs the reversal data 811 for performing reversal in the bookkeeping of the qualified invoice issuer based on the qualified refund invoice data. For example, as the amount of the reversal data 811, data corresponding to the amount data included in the qualified refund invoice data (e.g., "11,000 yen") is output, and as the tax category of the reversal data 811, data corresponding to the tax rate data included in the qualified refund invoice data (e.g., "10%") is output. This makes it easy to perform bookkeeping reversal of qualified invoices based on qualified refund invoice data. It is also possible to provide a technology that enables efficient execution of processes related to qualified refund invoices.
[0099] Each of the journal data 810a, 810b and the reversal data 811 is configured to be editable. Each of the journal data 810a, 810b and the reversal data 811 is reflected as accounting data by being registered via a registration button or the like. Each of the journal data 810a, 810b and the reversal data 811 is used to create various accounting documents such as ledgers, tax returns, profit and loss statements, balance sheets, and cash flow statements.
[0100] As described above, according to the first embodiment, a technique can be provided that enables efficient processing of documents related to the invoice system, such as qualified invoices and qualified refund invoices.
[0101] [Embodiment 2] Next, an example of combining a qualified invoice and a qualified refund invoice into one invoice will be explained with reference to Figure 13. Hereinafter, an invoice that combines a qualified invoice and a qualified refund invoice into one will be referred to as a composite qualified invoice. The second embodiment has the same system configuration, hardware configuration and functional configuration as the first embodiment. Figure 13 is a diagram showing an example of an invoice screen 9 relating to the second embodiment.
[0102] The invoice screen 9 in Figure 13 is a screen for creating a composite qualified invoice. The invoice screen 9 in Figure 13 includes a data input area 90, a data display area 91, and a Complete button 92.
[0103] The data input area 90 of the second embodiment is configured to be able to input data for creating qualified invoice data in addition to the features of the data input area 60 of the first embodiment. The data input area 90 includes a supplier input area 900, an issuer input area 901, an identification input area 902, a date input area 903, an address input area 904, a description input area 905, a transfer destination input area 906, and a remarks input area 907. For the supplier input area 900, the issuer input area 901, the identification input area 902, the address input area 904, the transfer destination input area 906, and the remarks input area 907, please refer to the supplier input area 600, the issuer input area 601, the identification input area 602, the return date input area 603, the address input area 604, the transfer destination input area 606, and the remarks input area 607.
[0104] The date input field 903 is an area configured so that billing date data for qualified invoices and refund data for qualified refund invoices can be input.
[0105] The details input area 905 is an area configured to allow input of transaction content data, amount data, tax rate data, and delivery date data for each of qualified invoices and qualified refund invoices. The details input area 905 may also be configured to allow selection of the type of return of consideration related to sales, such as returns, discounts, rebates, sales incentives, etc.
[0106] The data display area 91 of the second embodiment is an area in which a preview of a composite qualified invoice is displayed in a visible manner based on the data entered in the data input area 90. The data display area 91 includes a customer display area 910, an issuer display area 911, an identification display area 912, a date display area 913, an address display area 914, a statement display area 915, a transfer destination display area 916, and a remarks display area 917. The customer display area 910, the issuer display area 911, the identification display area 912, the address display area 914, the transfer destination display area 916, and the remarks display area 917 include the customer display area 610, the issuer display area 611, the identification display area 612, the address display area 614, the transfer destination display area 616, and the remarks display area 617.
[0107] The date display area 913 is an area in which the invoice date data entered in the date input area 903 is displayed in a visually recognizable manner as the invoice date of a qualified invoice, and the refund etc. data is displayed in a visually recognizable manner as the return date of a qualified refund invoice.
[0108] The details display area 915 is an area in which the transaction content data, tax rate data, delivery date data, and amount data for the qualified invoice that have been entered in the details input area 905 are visually displayed. The details display area 915 is also an area in which the transaction content data, amount data, tax rate data, and delivery date data for the qualified invoice that have been entered in the details input area 905 are visually displayed. The details display area 915 may also be configured to be capable of displaying the refund of the consideration for the sales, etc., selected in the details input area 905.
[0109] The completion button 92 of the second embodiment has the same features as the completion button 62 of the first embodiment.
[0110] When creating a composite qualified invoice, the composite qualified invoice may be created based on data of any invoice that the user has used in the past. In other words, the specified data included in the composite qualified invoice may vary depending on whether the composite qualified invoice is created based on qualified invoice data, qualified return invoice data, or composite qualified invoice data.
[0111] When the invoice is created based on qualified invoice data, the predetermined data may be data included in the qualified invoice data. In this case, the predetermined data may include at least one of issuer data, delivery date data, transaction content data, amount data, tax rate data, tax amount data, customer data, billing date data, address data, remarks data, and identification data.
[0112] When the specified data is created based on the qualified refund claim data, the specified data may be the data included in the qualified refund claim data. In this case, the specified data may include at least one of the following: issuer data, provision date data, transaction content data, amount data, tax rate data, tax amount data, address data, remarks data, customer data, refund data, and identification data.
[0113] When created based on synthetic qualified invoice data, the specified data may include at least one of issuer data, provision date data, transaction content data, amount data, tax rate data, tax amount data, customer data, invoice date data, refund etc. data, address data, remarks data, and identification data.
[0114] As described above, according to the second embodiment, a technology can be provided that enables efficient processing of documents related to the invoice system, such as qualified invoices and qualified refund invoices.
[0115] [others] The notification unit 213 may notify the user by displaying on the output unit 45 of the client device 4 that the amount of the transaction related to the qualified refund invoice is less than a predetermined amount, or that the business partner related to the qualified refund invoice is a tax-exempt business operator. For example, the notification unit 213 determines that the amount of the transaction related to the qualified refund invoice is less than a predetermined amount when the tax-inclusive price is less than a predetermined amount (an amount determined by law, regulations, etc., for example, less than 10,000 yen) based on the amount calculation data 605c and tax rate data 605d input in the detail input area 605, and notifies the user. In addition, the notification unit 213 determines that the business partner related to the qualified refund invoice is a tax-exempt business operator based on the business partner data input in the business partner input area 600 and reference data such as a table, and notifies the user. This reference data is data that stores information on whether or not the business partner is an exempt business operator for each business partner. This makes it possible to notify the user of cases where it is not necessary to create a qualified refund invoice.
[0116] In a modified example, the generating unit 212 may generate the predetermined data according to the type of return of the consideration related to the sales applied to the qualified refund invoice. For example, when applying a fractional deduction as the type of return of the consideration related to the sales, there is no need to describe the individual transaction details in the qualified refund invoice, so the generating unit 212 generates the predetermined data in a form that does not include transaction details data, and generates draft data including the predetermined data. This makes it possible to generate draft data including the predetermined data according to the type of return of the consideration related to the sales applied to the qualified refund invoice, and therefore to generate draft data according to the transaction.
[0117] Next, referring to Figure 14, we will explain the billing total amount screen 1000, which allows the user to refer to the total amount based on the issued qualified invoice data and the issued qualified refund invoice data. Figure 14 is a diagram showing an example of the billing total amount screen 1000. The total amount is the billing amount linked to the qualified invoice minus the refund amount linked to the qualified refund invoice.
[0118] The billing total screen 1000 is a screen that displays the total amount in various formats, such as by period, by customer, by tag, by month, etc. The billing total screen 1000 includes a billing total area 1001, a billing amount by customer area 1002, a billing amount by tag area 1003, and a monthly billing amount area 1004.
[0119] The total billing amount area 1001 is an area configured to be able to display the total amount for customers of the organization to which the user belongs for a specific period (e.g., this month). In addition to the total amount, the total billing amount area 1001 may also display the result of comparing the total amount for a specific period (e.g., this month) with a specific past period (e.g., last month) (e.g., -3,702,130 yen compared to last month). The total billing amount area 1001 may also include the number of invoices (e.g., 29 invoices), the number of issued invoices that have not been paid (e.g., 2 invoices), and the number of issued invoices that have been paid (e.g., 1 invoice).
[0120] The billing amount by supplier area 1002 is an area where the total amount by supplier is displayed. The billing amount by supplier area 1002 in Figure 14 displays the top few customers (e.g., the top three) with the largest total amounts. The billing amount by supplier area 1002 in Figure 14 includes buttons that allow the user to output a report by supplier.
[0121] The billing amount by tag area 1003 is an area where the billing amount by tag is displayed. These tags are freely set by the user, such as project names or department names, and are used for grouping. The billing amount by tag area 1003 in FIG. 14 displays the top few tags (e.g., three) with the largest total amounts. The billing amount by tag area 1003 in FIG. 14 includes a button that can output a report by tag.
[0122] The monthly billing area 1004 is an area where the total amount by month is displayed. The monthly billing area 1004 in FIG. 14 displays the monthly total amount for April 2022 to March 2023 in a bar graph. The monthly billing area 1004 in FIG. 14 includes a button that can output a CSV file that can refer to the monthly total amount.
[0123] The display control unit 214 of the invoice server device 2 displays the total invoice amount screen 1000 in response to a user operation. In other words, the display control unit 214 displays on the output unit 45 as information for each business partner the amount obtained by subtracting the amount of the transaction included in the qualified refund invoice from the amount of the transaction included in the qualified invoice issued for each business partner. This makes it easy to grasp the total amount of the invoice amount related to the qualified invoice and the amount to be refunded related to the qualified refund invoice for each business partner.
[0124] The creation of qualified refund invoice data in the first embodiment and the creation of composite qualified invoice data in the second embodiment may be performed based on qualified simplified invoice data. Qualified simplified invoices differ from the items to be written on qualified invoices in that the entry of "the name or business name of the business receiving the document" is not required, and only one of "the amount of consumption tax classified by tax rate" or "the applicable tax rate" is required. Therefore, the data on qualified simplified invoices includes issuer data, provision date data, transaction content data, and amount data. Furthermore, the data on qualified simplified invoices may include either tax rate data or tax amount data. The data on qualified simplified invoices may not include customer data. Furthermore, qualified simplified invoice data may include billing date data, address data, remarks data, and identification data. These data may be used as predetermined data when generating draft data.
[0125] In the first and second embodiments, the invoice server device 2 and the accounting server device 3 are described as being configured by separate servers, but in a modified example, they may be configured by the same server.
[0126] In the example of FIG. 10 in the first embodiment, an example of calculating tax amount data and amount data has been described. However, in a modified example, the system may be configured to accept input of tax amount data and amount data from a user.
[0127] The invoice server device 2 and / or the accounting server device 3 may be in an on-premise form or in a cloud form. The invoice server device 2 and / or the accounting server device 3 in a cloud form may provide the above functions and processes in the form of, for example, SaaS (Software as a Service) or cloud computing.
[0128] In the above embodiment, the invoice server device 2 and / or the accounting server device 3 each performed various storage and control, but multiple external devices may be used instead of the invoice server device 2 and / or the accounting server device 3. In other words, various information and programs may be distributed and stored in multiple external devices using block chain technology or the like.
[0129] The information processing method includes steps of a program. The information processing system includes a computer that executes the program.
[0130] Furthermore, the present invention may be provided in the following manner.
[0131] (1) A program which causes a computer to execute the following steps: in an identification step, identifying qualified invoice data, the qualified invoice data being data of a qualified invoice created by a qualified invoice issuer; in a generation step, generating draft data based on the identified qualified invoice data, the draft data being data including specified data for creating a qualified refund invoice, the specified data being data including at least a portion of the data included in the qualified invoice data.
[0132] According to this configuration, it is possible to generate draft data for creating a qualified refund invoice based on the qualified invoice data, which makes it easier to create a qualified refund invoice. This makes it possible to provide a technology that enables efficient processing of qualified refund invoices.
[0133] (2) A program which causes a computer to execute the following steps: in an acquisition step, qualified invoice data and qualified refund invoice data are acquired, the qualified invoice data being data for a qualified invoice created by a qualified invoice issuer, the qualified refund invoice data being data created by the qualified invoice issuer and being data for a qualified refund invoice to be issued when returning at least a portion of the sales linked to the qualified invoice; and in an output step, based on the qualified refund invoice data, output reversal data for performing a reversal entry in the accounting of the qualified invoice issuer.
[0134] According to this configuration, it is easy to perform bookkeeping reversal of qualified invoices based on the qualified refund invoice data. As a result, it is possible to provide a technology that enables efficient processing of qualified refund invoices.
[0135] (3) In the program described in (1) above, the draft data is data capable of accepting input of refund data from a user indicating the date on which a refund or deduction will be made in connection with the return, discount or rebate of taxable assets.
[0136] With this configuration, when creating a qualified refund invoice, it is possible to accept input of refund and other data from the user that may result in content that differs from that of the qualified invoice.
[0137] (4) In the program described above in (1), the specified data includes identification data capable of identifying the qualified invoice data corresponding to the qualified return invoice data.
[0138] With this configuration, it becomes easy to identify which qualified invoice a qualified refund claim was created based on.
[0139] (5) In the program described in (1) above, the specified data includes transaction content data indicating the content of the assets or services related to the transaction, amount data indicating the amount of the transaction, tax rate data indicating the applicable tax rate for the transaction, and provision date data for the assets or services related to the transaction, and in the generating step, the draft data is generated in a manner including the transaction content data, the amount data, the tax rate data, and the provision date data.
[0140] With this configuration, when creating a qualified refund invoice, it is possible to accept input from the user of transaction content data, amount data, tax rate data, and delivery date data that are likely to be the same as the contents of the qualified invoice.
[0141] (6) A program as described in (1) above, further comprising an output step, in which reversal data for performing a reversal entry in the bookkeeping of the qualified invoice issuer is output based on the qualified refund invoice data, the qualified refund invoice data being data for a qualified refund invoice created by the qualified invoice issuer and being data created based on the draft data.
[0142] With this configuration, it becomes easy to perform bookkeeping reversal entries based on the qualified refund invoice data that is created based on the qualified invoice data.
[0143] (7) A program as described in (1) above, further comprising a display control step, in which the display control step displays, for each trading partner, the amount of the transaction included in the qualified invoice issued for each trading partner minus the amount of the transaction included in the qualified refund invoice.
[0144] With this configuration, it becomes easy to grasp the total amount of the invoice amount related to the qualified invoice and the amount to be refunded related to the qualified refund invoice for each business partner.
[0145] (8) In the program described in (1) above, in the generation step, the specified data is generated depending on the type of return of sales consideration that is applied to the qualified refund invoice.
[0146] With this configuration, draft data including specified data can be generated depending on the type of return of sales-related consideration that applies to the qualified refund invoice, thereby making it possible to generate draft data according to the transaction.
[0147] (9) A program as described in (1) above, further comprising a notification step, in which if the amount of the transaction related to the qualified refund invoice is less than a specified amount, or if the business partner related to the qualified refund invoice is a tax-exempt business, a notification is given that the qualified refund invoice does not need to be issued.
[0148] With this configuration, the user can be notified when there is no need to create a qualified refund invoice.
[0149] (10) An information processing method comprising the steps of the program according to any one of (1) to (9) above.
[0150] With this configuration, it is possible to provide a technology that enables processing related to qualified refund invoices to be carried out efficiently.
[0151] (11) An information processing system comprising a computer that executes the program according to any one of (1) to (9) above.
[0152] With this configuration, it is possible to provide a technology that enables processing related to qualified refund invoices to be carried out efficiently. Of course, this is not the case.
[0153] Finally, although various embodiments of the present invention have been described, these are presented as examples and are not intended to limit the scope of the invention. The novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. The embodiments and their modifications are included within the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]
[0154] 1: Information processing system 2: Invoice server device 21: Processor 210: Information transmission and reception unit 211: Specific part 212 :Generation part 213: Notification Department 214: Display control unit 22: Storage section 23: Communications Department 3: Accounting server device 31: Processor 310: Information transmission and reception unit 311: Acquisition Department 312: Data output section 313: Display control unit 32: Storage section 33: Communications Department 4: Client device 41: Processor 42: Storage section 43: Communications Department 44: Input section 45: Output section 5: Bill screen 50: Invoice list area 51: Invoice operation area 510: Duplicate conversion button 511: Selection area 512: Draft data generation button 52: Invoice details area 6: Invoice screen 60: Data entry area 600: Customer input area 601: Issuer input area 602: Identification input area 603: Return date input field 604: Address input area 605: Detail input area 605a: Date of provision 605b: Transaction details data 605c: Amount calculation data 605d: Tax rate data 606: Transfer destination input area 607: Remarks input area 61: Data display area 610: Customer display area 611: Publisher display area 612:Identification display area 613: Return date display area 614:Address display area 615: Details display area 616: Transfer destination display area 617:Remarks display area 62:Complete button 7: Invoice screen 70: Eligible return claim area 8: Checkout screen 80: Narrow down area 810: Journal entry data 811: Reversal data 81: Journal entry area 9: Bill screen 90: Data entry area 900: Customer input area 901: Issuer input area 902: Identification input area 903: Date input area 904: Address input area 905: Detail input area 906: Transfer destination input area 907: Remarks input area 91: Data display area 910: Customer display area 911: Issuer display area 912:Identification display area 913: Year, month, and day display area 914:Address display area 915: Details display area 916: Transfer destination display area 917 :Remarks display area 92:Complete button 1000: Total billing amount screen 1001: Total amount billed area 1002: Invoice amount by business partner area 1003: Billing amount by tag area 1004: Monthly billing amount area N: Network
Claims
1. A program, Have the computer perform the following steps: In the identification step, qualified invoice data is identified, the qualified invoice data being data of a qualified invoice created by a qualified invoice issuer; In the generation step, draft data is generated based on the identified qualified invoice data, the draft data is data including predetermined data for creating a qualified refund invoice, and the predetermined data is data including at least a portion of the data included in the qualified invoice data. program.
2. A program, Have the computer perform the following steps: In the acquisition step, qualified invoice data and qualified refund invoice data are acquired, the qualified invoice data being data of a qualified invoice created by a qualified invoice issuer, and the qualified refund invoice data being data created by the qualified invoice issuer and being data of a qualified refund invoice to be issued when returning at least a portion of the sales linked to the qualified invoice, In the output step, reversal data for performing a reversal entry in the bookkeeping of the qualified invoice issuer is output based on the qualified refund invoice data. program.
3. The program according to claim 1, The draft data is data that can accept input of refund data from a user indicating a date on which a refund or reduction will be made in connection with the return, discount or rebate of taxable assets. program.
4. The program according to claim 1, The predetermined data includes identification data capable of identifying the qualified invoice data corresponding to the qualified return invoice data; program.
5. The program according to claim 1, The predetermined data includes transaction content data indicating the content of the assets or services related to the transaction, amount data indicating the amount of the transaction, tax rate data indicating the applicable tax rate for the transaction, and provision date data of the assets or services related to the transaction; In the generating step, the draft data is generated in a form including the transaction content data, the amount data, the tax rate data, and the provision date data. program.
6. The program according to claim 1, Further execute the output step, In the output step, reversal data for performing a reversal entry in the bookkeeping of the qualified invoice issuer is output based on the qualified refund invoice data, and the qualified refund invoice data is data of a qualified refund invoice created by the qualified invoice issuer and is data created based on the draft data. program.
7. The program according to claim 1, Further performing a display control step; In the display control step, an amount obtained by subtracting the amount of the transaction included in the qualified refund invoice from the amount of the transaction included in the qualified invoice issued to each business partner is displayed for each business partner. program.
8. The program according to claim 1, In the generating step, the predetermined data is generated according to the type of return of the consideration related to the sales applied to the qualified return invoice. program.
9. The program according to claim 1, performing further notification steps; In the notification step, if the amount of the transaction related to the qualified refund invoice is less than a predetermined amount, or if the business partner related to the qualified refund invoice is a tax-exempt business operator, a notification is made that the qualified refund invoice does not need to be issued. program.
10. 1. An information processing method, comprising: The program includes steps according to any one of claims 1 to 9. Information processing methods.
11. An information processing system, The present invention comprises a computer that executes the program according to any one of claims 1 to 9. Information processing system.
Citation Information
Patent Citations
Slip issuing method
JP2002298067A
Accounting data creation device, method, and program
JP2022144683A
Information processing device, information processing method, and program
JP2023048783A
