JP7753766B2 - Information processing device, method, program, and system - Google Patents

Description

The present invention relates to an information processing device, method, program, and system.

Previously, methods have been disclosed for determining the eligibility of supporting data related to qualified invoices under the invoice system. Specifically, for example, in Patent Document 1, the eligibility of supporting data is determined by converting multiple characters contained in the supporting data into text and comparing those multiple characters with the business name and business identification information.

Patent No. 6712738

However, the supporting data in Patent Document 1 is image data of invoices held by the accounting firm's clients, which have been scanned (see, for example, paragraph [0020] of the specification in Cited Document 1). In other words, the supporting data in Patent Document 1 is supporting data relating to issued invoices, and with this prior art, if the supporting data is determined to be ineligible because it does not meet the specified conditions, the deduction cannot be applied.

The present invention aims to issue reports that meet specified conditions.

An information processing device according to one embodiment of the present invention comprises a reception unit that receives a request to issue a form, a first judgment unit that determines whether there is input in a specific area of the form, a second judgment unit that, if there is input in the specific area, determines whether input in areas of the form other than the specific area satisfies specified conditions, and an issuance unit that issues the form if there is no input in the specific area, and issues the form if there is input in the specific area and the input in areas of the form other than the specific area satisfies the specified conditions, wherein the form is a qualified invoice under the invoice system, the areas other than the specific area are items that should be included on the qualified invoice, and the specific area is the registration number of a qualified invoice issuer .

This invention makes it possible to issue reports that meet specified conditions.

1 is a diagram illustrating an overall configuration according to an embodiment of the present invention. 1 is a hardware configuration diagram of an information processing apparatus according to an embodiment of the present invention; 1 is a functional block diagram of an information processing apparatus according to an embodiment of the present invention; 4 is an example of data stored in a form data storage unit according to an embodiment of the present invention. 10 is an example of data stored in a customer data storage unit according to an embodiment of the present invention. 1 is a flowchart (Example 1) of a form issuing process according to an embodiment of the present invention. 10 is a flowchart (Example 2) of a form issuing process according to an embodiment of the present invention. 10 is an example of a screen according to an embodiment of the present invention.

Embodiments of the present disclosure will be described below with reference to the drawings.

<Terminology>
In this specification, a "document" is a document (e.g., an invoice, a delivery note, a receipt, a receipt, etc.) that indicates the amount of money that a buyer pays to a seller (e.g., a supplier). For example, the document is a qualified invoice under the qualified invoice storage system (also called the invoice system).
In this specification, "issuing" refers to creating a form such as a qualified invoice and making it valid (for example, printing the form data, transmitting the form data).

<System Configuration>
1 is a diagram showing the overall configuration of an embodiment of the present invention. The system 1 includes an information processing device (server) 10 and a user terminal (client) 20. The information processing device 10 and the user terminal 20 are connected to each other so as to be able to communicate with each other via a communication network N. Each of these will be described below.

<<Information processing device>>
The information processing device 10 issues forms such as qualified invoices under the invoice system. Specifically, when the information processing device 10 receives a request to issue a form, it determines whether or not there is input in a specific area of the form (for example, whether or not there is input in the "qualified invoice issuer registration number"). If there is input in the specific area, the information processing device 10 determines whether or not the input in areas other than the specific area of the form meets predetermined conditions (for example, whether or not predetermined items (such as "transaction date,""transactiondetails,""total amount of consideration and applicable tax rate divided by tax rate,""amount of consumption tax divided by tax rate," and "name or title of business receiving the issuance") are described). If there is no input in the specific area, the information processing device 10 issues the form.

The devices described in the examples merely represent one of several computing environments for implementing the embodiments disclosed herein. The information processing device 10 is, for example, a personal computer (PC) or a workstation. The information processing device 10 may also be implemented as a server device, an ASP (Application Service Provider), or cloud computing. In one embodiment, the information processing device 10 includes multiple computing devices, such as a server cluster. The multiple computing devices are configured to communicate with each other via any type of communication link, including a network, shared memory, etc., and perform the processing disclosed herein.

<<User terminal>>
The user terminal 20 is a terminal used by a user who wants to issue a form such as a qualified invoice under the invoice system. Specifically, the user terminal 20 requests the information processing device 10 to issue a form. The user terminal 20 also acquires the form issued by the information processing device 10. For example, the user terminal 20 is a personal computer or the like.

Note that the user terminal 20 is not limited to a personal computer, as long as it is a device with communication capabilities. The user terminal 20 may be, for example, a PJ (Projector), an IWB (Interactive White Board: an electronic whiteboard with intercommunication capabilities), an output device such as digital signage, a HUD (Head Up Display) device, industrial machinery, an imaging device, a sound collection device, medical equipment, a network appliance, an automobile (Connected Car), a notebook PC (Personal Computer), a mobile phone, a smartphone, a tablet device, a game console, a PDA (Personal Digital Assistant), a digital camera, a wearable PC, or a desktop PC.

<Hardware configuration>
2 is a hardware configuration diagram of an information processing apparatus 10 according to an embodiment of the present invention. The same applies to a user terminal (in the case of a personal computer) 20.

As shown in FIG. 2, the information processing device 10 is constructed by a computer and includes a CPU 1001, ROM 1002, RAM 1003, HD 1004, HDD (Hard Disk Drive) controller 1005, display 1006, external device connection I/F (Interface) 1007, network I/F 1008, data bus 1009, keyboard 1010, pointing device 1011, DVD-RW (Digital Versatile Disk Rewritable) drive 1013, and media I/F 1015.

Of these, the CPU 1001 controls the overall operation of the information processing device 10. The ROM 1002 stores programs used to drive the CPU 1001, such as IPL. The RAM 1003 is used as a work area for the CPU 1001. The HD 1004 stores various data, such as programs. The HDD controller 1005 controls the reading and writing of various data from the HD 1004 under the control of the CPU 1001. The display 1006 displays various information, such as a cursor, menus, windows, characters, or images. The external device connection I/F 1007 is an interface for connecting various external devices. In this case, external devices include, for example, USB (Universal Serial Bus) memory and printers. The network I/F 1008 is an interface for data communication using the communication network N. The bus line 1009 is an address bus, data bus, etc. for electrically connecting the various components, such as the CPU 1001, shown in FIG. 2.

The keyboard 1010 is a type of input device equipped with multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 1011 is a type of input device for selecting and executing various instructions, selecting a processing target, moving the cursor, etc. The DVD-RW drive 1013 controls the reading and writing of various data from a DVD-RW 1012, which is an example of a removable recording medium. Note that this is not limited to a DVD-RW, and may be a DVD-R or the like. The media I/F 1015 controls the reading and writing (storing) of data from a recording medium 1014, such as a flash memory.

<Function block>
FIG. 3 is a functional block diagram of the information processing device 10 according to an embodiment of the present invention.

The information processing device 10 can include a reception unit 101, a judgment unit 102, an issuance unit 103, an error processing unit 104, a forced setting unit 105, a screen generation unit 106, a report data storage unit 107, and a customer data storage unit 108. Furthermore, by executing a program, the information processing device 10 can function as the reception unit 101, the judgment unit 102, the issuance unit 103, the error processing unit 104, the forced setting unit 105, and the screen generation unit 106.

The reception unit 101 receives a request to issue a document (e.g., an invoice) from the user terminal 20.

The judgment unit 102 functions as a "first judgment unit" and a "second judgment unit" and may consist of one or more modules.

The judgment unit 102 (first judgment unit) determines whether or not there is input in a specific area of the form. For example, the judgment unit 102 determines whether or not there is input in the "Registration number of qualified invoice issuer" field in the invoice.

The determination unit 102 (second determination unit) determines whether input into areas other than specific areas of the form meets predetermined conditions. For example, the determination unit 102 determines whether predetermined items (e.g., "transaction date," "transaction details," "total amount of consideration divided by tax rate and applicable tax rate," "amount of consumption tax divided by tax rate," and "name or title of business receiving the issuance") are entered.

The issuing unit 103 issues a form to the user terminal 20. For example, the issuing unit 103 can make settings related to the issuance (e.g., settings for printing the form) before issuing the form. Note that the issuing unit 103 may also determine whether other items (i.e., items other than those determined by the determining unit 102) satisfy predetermined conditions before issuing the form.

The error processing unit 104 executes error processing. For example, the error processing unit 104 can display a screen informing the user that an error has occurred and that the report cannot be issued, a screen presenting items that do not meet specified conditions, a screen prompting the user to correct items that do not meet specified conditions, etc.

The forcing setting unit 105 changes input into an area that is determined not to satisfy a predetermined condition to input that does satisfy the predetermined condition.

The screen generation unit 106 generates a screen. Specifically, the screen generation unit 106 generates a screen for accepting a request to issue a form. If there is input in a specific area of the form, the screen generation unit 106 generates a screen depending on whether the input in areas other than the specific area of the form meets specified conditions (for example, if the specified conditions are not met, a screen notifying the user that an error has occurred and the form cannot be issued, a screen presenting items that do not meet the specified conditions, a screen prompting the user to correct items that do not meet the specified conditions, etc.; if the specified conditions are met, a screen for issuing the form). If there is no input in the specific area, the screen generation unit 106 generates a screen for issuing the form (for example, a screen for settings for printing the form).

The report data storage unit 107 stores data related to reports.

The customer data storage unit 108 stores data related to customers (e.g., billing recipients).

<Data structure>
The data stored in the form data storage unit 107 will be described with reference to FIG. 4, and the data stored in the customer data storage unit 108 will be described with reference to FIG.

Figure 4 shows an example of data stored in the form data storage unit 107 according to one embodiment of the present invention. The form data storage unit 107 stores data related to forms.

The form data storage unit 107 stores the following information entered by the user for each form: "Qualified invoice issuer," "Transaction date," "Use of identifier for items subject to reduced tax rate," "Classify items by consumption tax rate," "Hide explanations for items subject to reduced tax rate," and "Customer ID." Each of these is explained below.

The "qualified invoice issuer" field stores the "qualified invoice issuer registration number" of the invoice source. The determination unit 102 determines that the invoice is a qualified invoice if a registration number is stored in the "qualified invoice issuer" field ((2) (3) (4) in Figure 4), and determines that the invoice is not a qualified invoice if a registration number is not stored in the "qualified invoice issuer" field ((1) in Figure 4). The determination unit 102 may also determine whether the registration number is an appropriate number.

The "transaction date" field stores the date of invoice issuance, etc. The determination unit 102 determines that a specified condition is met if a date is stored in the "transaction date," and determines that the specified condition is not met if a date is not stored in the "transaction date."

In "Use of identifier for item subject to reduced tax rate," information is stored regarding whether an identifier indicating that the item is subject to the reduced tax rate (for example, the * mark in Figure 8) is being used (for example, whether the identifier display function is turned on). If the identifier is being used, the determination unit 102 determines that the specified condition is met, and if the identifier is not being used, it determines that the specified condition is not met.

"Classify items by consumption tax rate" stores information on whether items are classified by consumption tax rate (for example, whether the "Classify items by consumption tax rate" function is turned on). If items are classified, the determination unit 102 determines that the specified conditions are met, and if items are not classified, it determines that the specified conditions are not met.

"Hide explanations of reduced tax rate items" stores information on whether the explanations of reduced tax rate items are hidden (for example, whether the "Hide explanations of reduced tax rate items" function is off). The determination unit 102 determines that the specified condition is met if the explanations are not hidden, and determines that the specified condition is not met if the explanations are hidden.

The "Customer ID" stores an ID (identification information) for identifying the billing party of the invoice. The determination unit 102 determines that a predetermined condition is met if a business name (customer name) linked to the "Customer ID" is stored (for example, the "Business Name" in Figure 5 is stored), and determines that the predetermined condition is not met if a business name (customer name) linked to the "Customer ID" is not stored (for example, the "Business Name" in Figure 5 is not stored).

In this way, the presence or absence of input for each field on the form and the content of the input for each field are stored, making it possible to determine whether the form meets specified conditions.

Figure 5 shows an example of data stored in the customer data storage unit 108 according to one embodiment of the present invention. The customer data storage unit 108 stores data related to customers (e.g., billing destinations). Note that the customer data storage unit 108 may not be provided, and customer information may be entered into a form.

The customer data storage unit 108 stores the following information for each customer: "Customer ID," "Business Name," "Telephone Number," and "Email." Each of these is explained below.

"Customer ID" is an ID used to identify a customer.

"Business name" is the name or title of the business partner.

"Phone number" is the client's phone number.

"Email" is the client's email address.

<Processing method>
FIG. 6 is a flowchart (example 1) of a form issuing process according to an embodiment of the present invention.

In step 11 (S11), the reception unit 101 receives a request to issue a document (e.g., an invoice) from the user terminal 20.

In step 12 (S12), the determination unit 102 determines whether or not there is input in a specific area of the form. If there is input in the specific area ("YES" in Figure 6, i.e., there is input), proceed to step 13; if there is no input in the specific area ("NO" in Figure 6, i.e., there is no input), proceed to step 14.

For example, the determination unit 102 determines whether or not there is an entry in the "Registration number of qualified invoice issuer" field in the invoice (i.e., whether or not there is an entry in the qualified invoice issuer column of the invoice).

In step 13 (S13), the determination unit 102 determines whether the input to areas other than the specific area of the form satisfies predetermined conditions. If the predetermined conditions are met ("YES" in Figure 6, i.e., all items are met), proceed to step 14; if the predetermined conditions are not met ("NO" in Figure 6, i.e., there are unmet items), proceed to step 15.

For example, the determination unit 102 determines whether or not certain items (e.g., "transaction date," "transaction details," "total consideration amount divided by tax rate and applicable tax rate," "amount of consumption tax divided by tax rate," "name or name of business receiving the issuance") are included (i.e., whether or not the format corresponds to a qualified invoice format).

In step 14 (S14), the issuing unit 103 issues a form to the user terminal 20. For example, the issuing unit 103 can make settings related to the issuance (e.g., settings for printing the form) before issuing the form. Note that the issuing unit 103 may also determine whether other items (i.e., items other than those determined by the determining unit 102) satisfy predetermined conditions before issuing the form.

In step 15 (S15), the error processing unit 104 executes error processing. For example, the error processing unit 104 can display a screen informing the user that an error has occurred and that the report cannot be issued, a screen presenting items that do not meet specified conditions, a screen prompting the user to correct items that do not meet specified conditions, etc.

In this way, by simply making an entry in a specific area of the form (for example, entering the "Registration number of a qualified invoice issuer" in the invoice), the user can find out if the form does not meet certain conditions (for example, if certain information (for example, information required for a qualified invoice under the invoice system) is not included).

Figure 7 is a flowchart (example 2) of the report issuance process according to one embodiment of the present invention.

In step 21 (S21), the reception unit 101 receives a request to issue a document (e.g., an invoice) from the user terminal 20.

In step 22 (S22), the determination unit 102 determines whether or not there is input in a specific area of the form. If there is input in the specific area ("YES" in Figure 7, i.e., there is input), proceed to step 23; if there is no input in the specific area ("NO" in Figure 7, i.e., there is no input), proceed to step 24.

For example, the determination unit 102 determines whether or not there is an entry in the "Registration number of qualified invoice issuer" field in the invoice (i.e., whether or not there is an entry in the qualified invoice issuer column of the invoice).

In step 23 (S23), the judgment unit 102 determines whether it has been determined whether input into areas other than specific areas of the form satisfies predetermined conditions (whether all items have been checked). If all items have been checked ("YES" in Figure 7, i.e., all items have been checked), proceed to step 24; if at least some items have not been checked ("NO" in Figure 7, i.e., there are items that have not been checked), proceed to step 25.

In step 24 (S24), the issuing unit 103 issues a form to the user terminal 20. For example, the issuing unit 103 can make settings related to the issuance (e.g., settings for printing the form) before issuing the form. Note that the issuing unit 103 may also determine whether other items (i.e., items other than those determined by the determination unit 102) satisfy specified conditions before issuing the form.

In step 25 (S25), the judgment unit 102 determines whether the input to an area other than the specific area of the form satisfies a predetermined condition. If the predetermined condition is met ("YES" in Figure 7, i.e., compatible), the process returns to step 23 and the next item is judged (in this way, each item is judged sequentially). If the predetermined condition is not met ("NO" in Figure 7, i.e., not compatible), the process proceeds to step 26.

For example, the determination unit 102 determines whether each of the specified items (e.g., "transaction date," "transaction details," "total consideration amount divided by tax rate and applicable tax rate," "amount of consumption tax divided by tax rate," "name or name of business receiving the issuance") is included (i.e., whether the format corresponds to a qualified invoice).

In step 26 (S26), the forcing setting unit 105 changes the input into the area determined in S25 to not satisfy the predetermined condition to an input that does satisfy the predetermined condition. Then, the process returns to step 23, and the next item is judged (in this way, each item is judged sequentially).

In this way, by simply entering information into a specific area of the form (for example, entering the "registration number of the qualified invoice issuer" in the invoice), even if the form does not meet the specified conditions (for example, if it does not include specified information (for example, information required for a qualified invoice under the invoice system)), the user can issue a modified form that meets the specified conditions.

<Screen example>
8 is an example of a screen (for example, a screen displayed on the user terminal 20) according to an embodiment of the present invention. Fig. 8 is a screen displaying a qualified invoice under the invoice system issued by the information processing device 10.

As shown in Figure 8, a qualified invoice under the invoice system includes the following items: "1. Name or title of the business issuing the qualified invoice and registration number," "2. Date of transaction," "3. Transaction details," "4. Total amount of consideration (excluding or including tax) broken down by tax rate and applicable tax rate," "5. Amount of consumption tax, etc. broken down by tax rate," and "6. Name or title of the business receiving the invoice."

The functions of the above-described embodiments can be realized by one or more processing circuits. In this specification, the term "processing circuit" includes processors programmed to perform functions by software, such as processors implemented by electronic circuits, as well as devices such as ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), FPGAs (Field Programmable Gate Arrays), and conventional circuit modules designed to perform the above-described functions.

Note that the present invention is not limited to the configurations described in the above embodiments, and may be combined with other elements. These aspects may be modified without departing from the spirit of the present invention, and may be determined appropriately depending on the application form.

1 System 10 Information processing device 20 User terminal 101 Reception unit 102 Determination unit 103 Issuance unit 104 Error processing unit 105 Forced setting unit 106 Screen generation unit 107 Report data storage unit 108 Customer data storage unit

Claims (9)

a reception unit that receives a request for issuing a form;
a first determination unit that determines whether or not there is an input to a specific area of the form;
a second determination unit that, when there is an input to the specific area, determines whether or not an input to an area other than the specific area of the form satisfies a predetermined condition;
If there is no input in the specific area, issue the form ;
an issuing unit that issues the form when there is an input to the specific area and an input to an area other than the specific area of the form satisfies the predetermined condition ;
The document is a qualified invoice under the invoice system,
The areas other than the specified areas are matters to be included in the qualified invoice,
An information processing device , wherein the specific area is a registration number of a qualified bill issuing business . The information processing device according to claim 1 , further comprising a forced setting unit that, when an input to an area other than the specific area does not satisfy the predetermined condition, changes the input that does not satisfy the predetermined condition to an input that satisfies the predetermined condition. The information processing apparatus according to claim 1 , further comprising an error processing unit that executes error processing when an input to an area other than the specific area does not satisfy the predetermined condition. a screen generation unit that generates a screen;
The screen generation unit
A screen for accepting requests to issue reports;
When there is an input to a specific area of the form, a screen is displayed according to whether or not the input to an area other than the specific area of the form satisfies a predetermined condition.
a screen for issuing the form if there is no input in the specific area;
generating a screen for issuing the form when there is an input to the specific area and when an input to an area other than the specific area of the form satisfies the predetermined condition;
The document is a qualified invoice under the invoice system,
The areas other than the specified areas are matters to be included in the qualified invoice,
An information processing device , wherein the specific area is a registration number of a qualified bill issuing business . A method executed by an information processing device,
receiving a request for issuing a report;
A step of determining whether or not there is an input in a specific area of the form;
If there is an input to the specific area, determining whether or not an input to an area other than the specific area of the form satisfies a predetermined condition;
If there is no input in the specific area, issue the form ;
and issuing the form when there is an input to the specific area and the input to areas other than the specific area of the form satisfies the predetermined condition ,
The document is a qualified invoice under the invoice system,
The areas other than the specified areas are matters to be included in the qualified invoice,
A method wherein the specific area is a registration number of a qualified billing business . The method according to claim 5 , further comprising the step of: if an input to an area other than the specific area does not satisfy the predetermined condition, changing the input that does not satisfy the predetermined condition to an input that satisfies the predetermined condition. The method according to claim 5 , further comprising the step of performing error processing if an input to an area other than the specific area does not satisfy the predetermined condition. an information processing device; a reception unit that receives a request for issuing a form;
a first determination unit that determines whether or not there is an input to a specific area of the form;
a second determination unit that, when there is an input to the specific area, determines whether or not an input to an area other than the specific area of the form satisfies a predetermined condition;
If there is no input in the specific area, issue the form ;
When there is an input to the specific area and an input to an area other than the specific area of the form satisfies the predetermined condition, the device functions as an issuing unit that issues the form ;
The document is a qualified invoice under the invoice system,
The areas other than the specified areas are matters to be included in the qualified invoice,
The program , wherein the specific field is a registration number of a qualified billing business . A system including an information processing device and a user terminal,
The information processing device includes:
a reception unit that receives a request for issuing a form from the user terminal;
a first determination unit that determines whether or not there is an input to a specific area of the form;
a second determination unit that, when there is an input to the specific area, determines whether or not an input to an area other than the specific area of the form satisfies a predetermined condition;
If there is no input in the specific area, issue the form to the user terminal ;
an issuing unit that issues the form to the user terminal when there is an input to the specific area and an input to an area other than the specific area of the form satisfies the predetermined condition;
The user terminal
requesting the information processing device to issue the form, and acquiring the form issued by the information processing device ;
The document is a qualified invoice under the invoice system,
The areas other than the specified areas are matters to be included in the qualified invoice,
The specific area is a registration number of a qualified bill issuing business, the system.