Source: https://patents.google.com/patent/JP2015156052A/en
Timestamp: 2020-03-31 08:21:59
Document Index: 755129912

Matched Legal Cases: ['art 102', 'art 103', 'art 104', 'art 105', 'art 106', 'art 111', 'art 112']

JP2015156052A - Information processing system, information processing apparatus, control method of information processing apparatus and program - Google Patents
Information processing system, information processing apparatus, control method of information processing apparatus and program Download PDF
JP2015156052A
JP2015156052A JP2014021248A JP2014021248A JP2015156052A JP 2015156052 A JP2015156052 A JP 2015156052A JP 2014021248 A JP2014021248 A JP 2014021248A JP 2014021248 A JP2014021248 A JP 2014021248A JP 2015156052 A JP2015156052 A JP 2015156052A
JP2014021248A
隆二 関根
2013-03-07 Priority to JP2013045784 priority Critical
2013-03-07 Priority to JP2013045784 priority
2014-01-14 Priority to JP2014003948 priority
2014-02-06 Application filed by 株式会社リコー, Ricoh Co Ltd filed Critical 株式会社リコー
2014-02-06 Priority to JP2014021248A priority patent/JP2015156052A/en
2015-08-27 Publication of JP2015156052A publication Critical patent/JP2015156052A/en
An object is to process an invoice according to requirements that may vary from country to country.
An information processing system that performs information processing based on transaction information, a transaction information acquisition unit that acquires the transaction information, and a first rule that is applied to the amount of each transaction included in the transaction information A prescription information storage unit for storing information and second prescription information applied to invoice data generated based on the first prescription information, and the invoice data generated based on the first prescription information And a storage control unit that controls to store the information based on the second specified information.
The present invention relates to an information processing system, an information processing apparatus, an information processing apparatus control method, and a program.
With the spread of the Internet, it is common for providers of goods or services to issue electronic invoices (e-invoice) to their customers. On the other hand, a provider of goods or services may issue an invoice for a paper medium according to a request from a customer.
There is an invoicing service that collectively issues invoices in electronic form and paper media for such goods or service providers. The invoicing service receives transaction information to be described in the invoice and information about the customer from the goods or service provider, and issues the invoice in a format determined for each customer.
In addition, in the bill issuing service as described above, a service is also provided in which the generated electronic form or paper-based bill is stored for a certain period in accordance with legal requirements.
Patent Document 1 discloses a proxy server that converts transaction information received from a customer into a format that can be received by a banking business system. Patent Documents 2 and 3 disclose apparatuses for maintaining compatibility of data handled by an application.
However, the conventional invoicing service cannot process the invoice according to the policy applied according to the transaction with the customer. For example, in Europe, VAT (Value Added Tax) is widely taxed, and the tax rate can vary depending on the system of the country in which the transaction was made. Also, the storage requirements for generated invoices can vary from country to country. However, the prior art has not been able to process invoices according to such requirements.
The present invention has been made in view of such problems.
In order to solve the above-described problems and achieve the object, an information processing system according to an embodiment of the present invention includes:
An information processing system that performs information processing based on transaction information,
A transaction information acquisition unit for acquiring the transaction information;
Regulation information for storing first regulation information applied to the amount of each transaction included in the transaction information and second regulation information applied to bill data generated based on the first regulation information A storage unit;
A storage control unit that controls to store the bill data generated based on the first regulation information based on the second regulation information;
The information processing system according to an embodiment of the present invention allows bills to be processed according to requirements that may vary from country to country.
The figure showing the outline | summary of the bill data processing system in one Embodiment of this invention. The figure showing the hardware structural example as the whole system of the bill data processing apparatus in one Embodiment of this invention. The functional block diagram of the bill data processing apparatus in one Embodiment of this invention. The figure showing the example of the table which stores customer information. The figure showing the example of the table which stores transaction information. The figure showing the example of the table which stores the tax rate information contained in policy information. The figure showing the example of the table which stores the storage requirement information contained in policy information. The figure showing the example of the bill which the bill data processing apparatus in one Embodiment of this invention outputs. The flowchart showing the outline of the process of the bill data processing apparatus in one Embodiment of this invention. The flowchart showing the bill production | generation process of the bill data processing apparatus in one Embodiment of this invention. The flowchart showing the bill data storage process of the bill data processing apparatus in one Embodiment of this invention. The sequence diagram of the bill data processing system in one embodiment of the present invention. The figure showing the hardware structural example of the bill data processing apparatus in one Embodiment of this invention. The figure showing the example of the table which associates a customer name with the format of an invoice, etc. The figure showing the example of the table which associates a customer name, the form of bill, and composition information.
1. Overview 2. 2. Hardware configuration Function 4. Example of operation
≪ １． Overview ≫
FIG. 1 shows an outline of a bill data processing system 1 according to an embodiment of the present invention. The invoice data processing system 1 includes an invoice data processing device 10, an electronic signature system 20 of an electronic signature service provider T that provides a service for adding an electronic signature to electronic data, and an article or service provider A The backbone system 30 of the system is included. Further, FIG. 1 shows an information processing apparatus 40A of a customer B who is a customer of the provider A and an information processing apparatus 40B of a customer D. The bill data processing apparatus 10, the electronic signature system 20, the backbone system 30, and the information processing apparatuses 40A and 40B are connected to each other via a network such as the Internet.
The backbone system 30 of the provider A is configured by a system represented by ERP (Enterprise Resource Planning), and manages transaction information related to goods or services provided to the customer by the provider A. For example, as shown in FIG. 5, the transaction information includes information such as the item name, the unit price, the quantity, and the item type of the item or service with which the transaction was made (details will be described later). The backbone system 30 also manages customer information about customers. For example, as shown in FIG. 4, customer information includes information on the customer name, the medium for outputting invoice data, the currency used for the transaction, the country to which the customer belongs, and the format of the output invoice data. (Details will be described later). The backbone system 30 is generally configured by one or more server computers.
The invoice data processing apparatus 10 reads customer information and transaction information stored in the core system 30 and calculates an invoice amount (total amount of transaction) according to pre-defined policy information. Generate invoice data for. This policy information is stored in advance in the invoice data processing apparatus 10 and defines, for example, a tax rate set for each type of transaction item. The generated bill data is output using a different medium (electronic format such as paper, FAX, or PDF) for each customer.
Further, the bill data processing apparatus 10 stores the generated bill data according to policy information that is defined in advance. This policy information is stored in advance in the bill data processing apparatus 10 together with the information on the tax rate. This policy information is set in accordance with the system for storing transaction information that varies from country to country. For example, it defines the necessity of adding an electronic signature to invoice data, the expiration date for invoice data, the storage location, the storage format, etc. To do.
For example, when the system of the country related to the transaction requires the invoice data to be stored with an electronic signature, the invoice data processing apparatus 10 adds an electronic signature through the electronic signature system 20, and The invoice data added is stored. In addition, for example, when a national system related to transactions requires that invoice data be stored in the country for five years, the invoice data processing device 10 is installed in the country. Stored in a storage device.
Further, the bill data processing apparatus 10 can take in information on a transaction between the provider A and its customer before being stored in the backbone system 30. For example, when transaction information is provided on a paper medium, the paper medium is scanned and the contents are captured as electronic data. Further, when the transaction information is provided in an electronic format, the contents are read. The invoice data processing apparatus 10 stores the read contents as transaction information in the backbone system 30 of the provider A.
The invoice data processing apparatus 10 is composed of one or more computers, and has a plurality of storage devices installed at different physical locations in order to respond to the above-described requirements for the storage location of the invoice data. Also good. That is, the bill data processing device 10 includes not only a device constituted by one computer but also a device group constituted by a plurality of computers.
The electronic signature system 20 provides an ASP (Active Server Pages) type service that adds an electronic signature generated using a certificate to data received from the outside. As described above, the electronic signature system 20 adds an electronic signature to the invoice data in response to a request from the invoice data processing apparatus 10. The electronic signature system 20 may be provided by being incorporated in a part of the bill data processing apparatus 10.
As described above, the bill data processing system 1 according to an embodiment of the present invention digitizes the transaction between the goods or service provider and the customer and stores it in the core system of the provider. In addition, invoice data for a customer of a provider of goods or services can be generated according to policy information applied for each customer and each transaction. Furthermore, the generated invoice data can be stored according to different requirements for each country. The details of the bill data processing system 1 will be described in detail below.
≪ 2. Hardware configuration ≫
FIG. 2 is a hardware configuration diagram of the bill data processing system 1 according to the embodiment of the present invention. The invoice data processing apparatus 10 includes a CPU 11, a RAM 12, a ROM 13, an HDD 14, a display 15, a NIC (Network Interface Card) 16, a keyboard 17, a mouse 18, a scanner 19, a printer 21, and a FAX 22. And have.
The CPU 11 executes a program for controlling the operation of the bill data processing apparatus 10. The RAM 12 constitutes a work area for the CPU 11. The ROM 13 stores a program executed by the CPU 11 and data necessary for executing the program. The HDD 14 is a storage device that stores bill data, policy information, and the like. The HDD 14 may be a storage device such as a magnetic disk or a solid state disk.
The display 15 is a device that presents information such as an operation screen to an administrator or the like of the bill data processing device 10. The NIC 16 is a communication device for connecting to a network. Instead of the NIC 16, a wireless communication device for connecting to a wireless network may be provided. The keyboard 17 and the mouse 18 are input devices for an administrator of the bill data processing apparatus 10 to directly operate the bill data processing apparatus 10.
The scanner 19 is a device that reads characters and images formed on paper and converts them into electronic data. The printer 21 is a device that prints invoice data on paper. The FAX 22 is a device for transmitting and receiving FAX data via a telephone line. The bus 23 connects the above devices to each other.
FIG. 13 is a hardware configuration diagram when the bill data processing apparatus 10 is configured by a single computer. As shown in FIG. 13, the bill data processing apparatus 10 has a CPU 51, a RAM 52, a ROM 53, an HDD 54, a display device 55, a communication I / F 56, an input device 57, and an external I / F 58. Each device is connected by a bus 59. The bill data processing apparatus 10 is connected to a FAX modem 60, a printer 61, and a scanner 62 via an external I / F 58. The printer 61 and the scanner 62 may be configured to be accessed via a network by the communication I / F 56.
The bill data processing apparatus 10 in FIG. 2 is configured by a single computer. However, as already described, the bill data processing apparatus 10 may be configured across a plurality of computers. . In addition, each of such a plurality of computers may include a part of the apparatus illustrated in FIG. 2 and may be configured to implement the apparatus illustrated in FIG. 2 as a whole.
≪ 3. Function ≫
FIG. 3 is a functional block diagram of the bill data processing system 1 according to an embodiment of the present invention. The bill data processing apparatus 10 of FIG. 3 includes a control unit 101, a document fetch unit 102, a policy information storage unit 103, a generation unit 104, and a bill data storage unit 105.
The control unit 101 is realized mainly by the processing of the CPU 11 and controls each unit so that the bill data processing apparatus 10 operates in accordance with the defined workflow.
First, the control unit 101 sends the contents of the transaction between the provider and the customer, such as paper, FAX, or electronic format (for example, EDI (Electronic Data Interchange) or e-mail), to the document capturing unit 102. Get the document to represent. Then, the control unit 101 stores the contents as transaction information in the provider's backbone system 30.
Next, the control unit 101 causes the generation unit 104 to generate paper, FAX, or invoice data based on the customer information 301 and transaction information 302 stored in the backbone system 30. At this time, policy information applied to the amount of each transaction is read from the policy information storage unit 103.
Further, the control unit 101 causes the bill data storage unit 105 to store the bill data generated by the generation unit 104 in accordance with the policy information stored in the policy information storage unit 103. At this time, the control unit 101 requests the electronic signature unit 201 to add an electronic signature to the invoice data as necessary.
Further, the control unit 101 causes the status output unit 106 to output the progress status of the bill data generation and the detailed information of the stored bill data in response to a request from the provider's terminal or the like. The output is displayed on the provider's terminal through an interface through a Web browser, for example. Such a display screen is also called a dashboard.
The document fetch unit 102 is realized mainly by the functions of the CPU 11, NIC 16, scanner 19, and FAX 20, and fetches a document representing the content of the transaction with the customer provided by the provider. The document capturing unit 102 performs OCR (Optical Character Reader) processing on a document provided by paper or FAX, and captures the contents of the transaction. The document format is assumed to be known. Further, the document fetching unit 102 fetches the contents of the transaction from a document provided in an electronic format such as EDI or e-mail according to a predetermined rule.
In addition, the document capture unit 102 transmits the content of the read transaction to the provider's backbone system 30 through the network. The contents of the transaction are stored in the backbone system 30 as transaction information 302. The document capture unit 102 can transmit the contents of the transaction to the backbone system 30 by any format or protocol.
The transaction information 302 is stored using, for example, a table shown in FIG. FIG. 5 is an example of transaction information related to a transaction performed by the provider A with the customer B. The transaction information 302 includes the item name of goods or services related to the transaction, the unit price thereof, the quantity related to the transaction, and the type of the item. The type of item is defined according to the difference in tax rate imposed by VAT, for example. For example, the same tax rate is applied to all items whose type is “type 1”. The tax rate imposed for each type is defined by policy information 151 described later.
In addition, the basic system 30 stores in advance customer information 301 for storing customer information. FIG. 4 is an example of customer A's customer information. The customer information 301 includes a customer name that is the name of the customer, a medium for outputting invoice data, a currency used for transactions with the customer, a country to which the customer belongs, and a format for outputting invoice data.
The policy information storage unit 103 stores policy information 151 applied when generating or storing bill data. The policy information 151 further includes tax rate information 161 and storage requirement information 162.
The tax rate information 161 includes, for example, items shown in FIG. FIG. 6 is an example of a table that stores the tax rate for each item type, which is applied to the transaction of the provider A with the customer B. The tax rate information 161 includes a type that represents the type of item and a tax rate that is uniformly applied to the item of that type. The type item of the tax rate information 161 corresponds to the type item of the transaction information 302. The tax rate information 161 may be prepared for each country or region.
The storage requirement information 162 includes, for example, items shown in FIG. FIG. 7 is an example of a table for storing invoice data storage requirements defined for each country or region. The storage requirement information 162 is roughly divided into items of country name, electronic signature, and storage requirement.
The electronic signature item further includes “necessity” indicating whether or not addition of an electronic signature is required, and “CA” indicating an issuer of an electronic certificate specified when the electronic signature is required. , An item of “time stamp” indicating whether or not a time stamp needs to be added to the electronic signature is included.
The storage requirement item is further converted to “period” that indicates the storage period of the invoice data, “location” that indicates the restrictions on where the invoice data is stored, and when the stored invoice data is output. It contains a “format” item that represents the format to be done.
Note that the above-described requirements relating to electronic signatures and storage are merely examples, and in practice, further requirements may be imposed based on a system relating to transactions in a country or region. In that case, items included in the storage requirement information 162 are expanded as appropriate.
The generation unit 104 is mainly realized by functions of the CPU 11, the NIC 16, the printer 21, the FAX 22, and the like, and includes an acquisition unit 111, a calculation unit 112, a shaping unit 113, and an output unit 114.
The acquisition unit 111 reads customer information 301 and transaction information 302 stored in the backbone system 30. At this time, the acquisition unit 111 can read the customer information 301 and the transaction information 302 from the backbone system 30 according to an arbitrary protocol or format.
The calculation unit 112 applies the tax rate information 161 stored in the policy information storage unit 103 to the amount of each transaction included in the transaction information 302 read by the acquisition unit 111, and calculates the amount charged (total amount of transaction). calculate. For example, the calculation unit 112 receives the transaction information 302 shown in FIG. 5 for the customer B shown in FIG. 4 (the currency is euro), and calculates the amount charged by applying the tax rate information 161 shown in FIG. In this example, a tax rate of 8% is imposed on “item 1” whose “class” is “class 1”, and a tax rate of 0% is imposed on “item 2” of “class 2”. Become. Therefore, the charged amount in FIGS. 4 to 6 is 208 euros.
The shaping unit 113 shapes the invoice data using the customer information 301 and the transaction information 302 read by the acquisition unit 111 and the billing amount information calculated by the calculation unit 112. For example, the shaping unit 113 performs shaping of the bill data using an arbitrary application. For example, the shaping unit 113 shapes the invoice data by inserting necessary items into a template prepared using Microsoft Word (registered trademark), Excel (registered trademark), or the like. The formatted invoice data is output in an appropriate format by the output unit 114 described later.
Therefore, the shaping unit 113 reads the “format” of the customer information 301 and writes information such as the item name, unit price, and billing amount according to the “format”. The above template is prepared corresponding to the format.
For example, when the format of invoice data to be output for each customer is determined, the shaping unit 113 uses, for example, a table shown in FIG. The corresponding invoice format can be specified. The table shown in FIG. 14 stores customer names, bill forms, bill data templates, output methods, and storage requirements in association with each other. Here, the item “Bill data template” indicates the file name of the file that is the template for outputting the bill data, and the item “Output method” indicates the method for sending the output bill data. Represents. The item “storage requirement” represents the storage period of the invoice data.
Further, the shaping unit 113 may specify configuration information in the form of an invoice for each customer using the table shown in FIG. The table shown in FIG. 15 can store customer names, bill forms, and configuration information in association with each other. Among these, the configuration information indicates items of invoice data to be output. The shaping unit 113 can specify the format of bill data to be output for each customer and the configuration thereof using the table shown in FIG.
In the following description, description will be made assuming that invoice data in the format illustrated in FIG. 8 is output. The format illustrated in FIG. 8 represents an example of “format 1” selected for the customer B in FIG. 4.
“Format 1” in FIG. 8 includes, for example, a title 31, a date 32, a provider A name 33, a customer B name 34, an item name 35, a unit price 36, a quantity 37, and a tax rate 38. , The total amount 39 of the invoiced amount, the text 40, the payment due date 41 of the invoiced amount, and information on the transfer destination 42 of the invoiced amount. The item name 35, the unit price 36, and the quantity 37 are information included in the transaction information 302 as shown in FIG. The tax rate 38 is information included in the tax rate information 161 as shown in FIG. 6, for example. The total 39 is the amount charged by the calculation unit 112. The text 40, the payment due date 41, and the transfer destination 42 are information prepared in advance for each provider or format, and are appropriately stored in a storage unit (not shown). The title 31 may instead be the logo of the provider A.
The output unit 114 outputs the invoice data shaped by the shaping unit 113 to a medium determined according to the customer. The output unit 114 refers to the item “medium” of the customer information 301 read by the acquisition unit 111 and determines a medium to be output. For example, for “customer B” in FIG. 4, the invoice data formatted as shown in FIG. 8 is output in PDF format. When the item “medium” in the customer information 301 is “FAX”, the output unit 114 converts the formatted invoice data into a format that can be transmitted by FAX.
The output unit 114 also prints bill data on a paper medium, outputs bill data by EDI (for example, conversion to XML (Extensible Markup Language)), and outputs bill data by e-mail (billing). Generation of a mail attached with a document data file or the like, or conversion into an HTML mail). Note that the conversion of the invoice data into XML and the conversion into HTML mail may be executed by the shaping unit 113.
Further, the output unit 114 may perform processing for transmitting the bill data output to an arbitrary medium to the customer. For example, when the output format of the bill data is PDF, EDI, or e-mail, the bill data may be transmitted to the customer terminal via the network. Further, when the output format of the bill data is FAX, the bill data may be transmitted to the customer by FAX.
The invoice data storage unit 105 is mainly realized by the functions of the CPU 11 and the HDD 14, and stores the invoice data generated by the generation unit 104 according to the storage requirement information 162 stored in the policy information storage unit 103.
First, the invoice data storage unit 105 reads, for example, storage requirements applied to a transaction between the provider A and the customer B from the storage requirement information 162 illustrated in FIG. Here, it is assumed that each item defined as the requirement of “country 1” has been read.
In “Country 1”, an electronic signature is required to be added to invoice data to be stored, and an electronic certificate for electronic signature needs to be issued by “CA1”. The time stamp information needs to be added. Therefore, the invoice data storage unit 105 adds an electronic signature with a time stamp (using a certificate issued by CA1) to the invoice data to the electronic signature unit 201 of the electronic signature system 20 through the control unit 101. Request.
Next, the bill data storage unit 105 stores the received data with the electronic signature in accordance with the policy information defined in the “storage requirements” of the storage requirement information 162. In “Country 1”, invoice data needs to be stored and stored in an arbitrary place for 7 years, and must be stored so that it can be output in csv (Comma Separated Values) format. In this case, the invoice data storage unit 105 stores the invoice data with the electronic signature in an arbitrary place in a format that can be converted into csv.
On the other hand, if the storage requirement of the storage requirement information 162 requires that the invoice data be stored in a specific country, the invoice data storage unit 105 stores the invoice data installed in that country. Invoice data is stored in the HDD 14 of the processing apparatus 10. As described above, the bill data processing apparatus 10 can be arranged across a plurality of places, and thus can respond to such a request.
As described above, the bill data processing system 1 according to the embodiment of the present invention can calculate the bill amount according to the tax rate determined for each item, and can generate bill data for the customer in an arbitrary format. Further, the bill data processing apparatus 10 can store bill data according to a system applied to a transaction between a provider and a customer. As a result, the bill data processing system 1 promotes the efficiency of the provider's business by performing the provider's invoicing business and bill storage business in a lump, and the international transaction law. Can contribute to compliance with the system.
<< 4. Example of operation ≫
Hereinafter, an operation example of the bill data processing system 1 according to the embodiment of the present invention will be described with reference to FIGS.
FIG. 9 shows an outline of a processing flow of the bill data processing apparatus 10 in an embodiment of the present invention. The invoice data processing apparatus 10 stores the contents of the transaction between the provider and the customer as transaction information 302 in the provider's backbone system 30 (step S100). Next, the bill data processing apparatus 10 reads the customer information 301 and the transaction information 302 stored in the provider's backbone system 30, and generates bill data according to the policy information applied to the transaction (step S200). . Then, the bill data processing apparatus 10 stores the bill data in a predetermined place according to the storage requirement policy information applied to the generated bill data (step S300).
FIG. 10 is a flowchart showing the flow of bill data generation processing of the bill data processing apparatus 10 according to an embodiment of the present invention. The flowchart shown in FIG. 10 represents a specific processing flow of step S200 of FIG. The invoice data generation process is started, for example, by receiving an invoice data generation process request from the terminal of the provider A or the like.
In step S <b> 201, the acquisition unit 111 of the bill data processing apparatus 10 reads the customer name from the customer information 301 stored in the backbone system 30 of the provider A.
In step S202, the acquisition unit 111 of the invoice data processing apparatus 10 reads transaction information corresponding to the customer name read in step S201 from the transaction information 302 stored in the backbone system 30 of the provider A.
In step S <b> 203, the calculation unit 112 of the bill data processing apparatus 10 reads the tax rate information 161 stored in the policy information storage unit 103.
In step S204, the calculation unit 112 of the invoice data processing device 10 applies the tax rate information for each type of transaction item, and calculates a charge amount.
In step S205, the shaping unit 113 of the bill data processing apparatus 10 reads the bill data format corresponding to the customer name read in step S201 from the customer information 301. At this time, the shaping unit 113 may read the table illustrated in FIG. 14 and specify the template of the bill data. The shaping unit 113 may read the table illustrated in FIG. 15 and specify configuration information in a format determined for each customer name.
In step S206, the shaping unit 113 of the bill data processing apparatus 10 shapes the bill data to be output for each customer according to the format read in step S205. Specifically, the shaping unit 113 reads the template specified in step S205, and puts the customer name, transaction information (item name, unit price, quantity), tax rate information (tax rate), tax rate information (tax rate), The billing amount calculated in S204 can be inserted.
In step S207, when the medium of the customer information 301 is an electronic format such as “PDF”, “EDI”, or “electronic mail”, the process proceeds to step S208, and the output unit 114 of the bill data processing apparatus 10 is processed. Outputs bill data in electronic form. Even when the medium is “FAX”, the bill data is processed in an electronic format.
On the other hand, if the medium of the customer information 301 is not in electronic format in step S207, that is, if it is paper, the process proceeds to step S209, and the output unit 114 of the bill data processing apparatus 10 sends a bill on the paper medium. Output data.
In addition, said step S201-S203 is an example of the reading order of the customer information 301 and the transaction information 302, and may actually be comprised so that all these information may be read simultaneously. As described above, the acquisition unit 111 reads necessary information at a time, so that the format reading process in step S205 is not necessary.
FIG. 11 is a flowchart showing a flow of bill data storage processing of the bill data processing apparatus 10 according to an embodiment of the present invention. The invoice data storage process is executed, for example, when the generation of all invoice data of the provider A in a specific period is completed.
In step S <b> 301, the bill data storage unit 105 of the bill data processing apparatus 10 reads the storage requirement information 162 stored in the policy information storage unit 103.
In step S302, if the necessity of the electronic signature of the storage requirement information 162 is “necessary”, the process proceeds to step S303, and if not, the process proceeds to step S305.
In step S <b> 303, the bill data storage unit 105 of the bill data processing apparatus 10 requests the electronic signature unit 201 of the electronic signature system 20 to add an electronic signature to the bill data through the control unit 101.
In step S <b> 304, the bill data storage unit 105 of the bill data processing apparatus 10 receives bill data to which an electronic signature is attached through the control unit 101.
If the location of the storage requirement in the storage requirement information 162 is specified in step S305 (for example, “domestic only”), the process proceeds to step S306, and if not, the process proceeds to step S307.
In step S306, the bill data storage unit 105 of the bill data processing apparatus 10 stores the bill data in a storage device arranged at a designated location in a format that can be output in a predetermined format.
In step S307, the bill data storage unit 105 of the bill data processing apparatus 10 stores the bill data in a storage device arranged at an arbitrary location in a format that can be output in a predetermined format. Here, the bill data storage unit 105 may store the bill data in a storage device having a sufficient free space among the storage devices arranged in a plurality of locations.
In this way, the invoice data stored in the invoice data storage unit 105 of the invoice data processing apparatus 10 is stored for a period defined by the storage requirements. After the period has elapsed, the bill data may be deleted according to a request from a provider or the like, or may be continuously stored.
FIG. 12 is a sequence diagram showing the operation of the bill data processing system 1 in one embodiment of the present invention. Here, it is assumed that the contents of the transaction between the provider A and the customer are already stored in the backbone system 30 of the provider A. In the following example, the bill data processing system 1 will explain an example in which the bill data of the provider A for the customer B is processed.
In step S401, the generation unit 104 (acquisition unit 111) of the invoice data processing apparatus 10 reads the customer information 301 (FIG. 4) stored in the backbone system 30 of the provider A, and outputs the invoice data of the customer B. Identify media, currency, country name and format.
In step S402, the generation unit 104 (acquisition unit 111) of the invoice data processing apparatus 10 reads the transaction information 302 (FIG. 5) with the customer B stored in the backbone system 30 of the provider A and relates to the transaction. Specify the item name, unit price, quantity, and type.
In step S403, the generation unit 104 (calculation unit 112) of the invoice data processing apparatus 10 reads the tax rate information 161 (FIG. 6) stored in the policy information storage unit 103, and the tax rate for each item name type of the transaction. Is identified.
In step S <b> 404, the generation unit 104 (calculation unit 112) of the invoice data processing apparatus 10 calculates a billing amount using the transaction information 302 and the tax rate information 161. Specifically, the generation unit 104 multiplies the unit price and quantity for each item name indicated in the transaction information 302, and further applies the tax rate associated with the type to calculate the billing amount for each item name. Then, the sum of the billing amounts of all the item names is added to calculate the sum of the billing amounts.
In step S <b> 405, the generation unit 104 (the shaping unit 113) of the bill data processing apparatus 10 shapes the bill data according to the format indicated by the customer information 301. Here, the generation unit 104 refers to the tables illustrated in FIG. 14 and FIG. 15, and may read the template of the invoice data and the configuration information regarding the items constituting the invoice data, representing the format of the invoice data. good. The generation unit 104 reads the invoice data template, and inserts the customer name, transaction information (item name, unit price, quantity), tax rate information (tax rate), the charge amount calculated in step S404, and the like at predetermined positions. . The invoice data formatted in this step is temporarily stored, for example, in the Word file format (doc) of Microsoft Corporation.
In step S406, the generation unit 104 (output unit 114) of the invoice data processing apparatus 10 outputs the invoice data to a medium indicated by the customer information 301 (FIG. 4). Here, the medium associated with the customer B is in the “PDF” format. Therefore, the generation unit 104 outputs the invoice data formatted in step S405 in the PDF format.
In step S407, the bill data storage unit 105 of the bill data processing apparatus 10 reads the storage requirement information 162 (FIG. 7) stored in the policy information storage unit 103. Here, in the customer information 301 of FIG. 4, the country name associated with the customer B is “country 1”. Therefore, the bill data storage unit 105 recognizes that the electronic signature with a time stamp generated by the CA “CA1” is necessary to store the generated bill data. Further, the bill data storage unit 105 recognizes that the generated bill data needs to be stored in the “csv” format at “7 years” in an arbitrary place.
In step S408, the invoice data storage unit 105 requests the electronic signature unit 201 of the electronic signature system 20 to add an electronic signature with a time stamp by “CA1” to the generated invoice data through the control unit 101. .
In step S409, the bill data storage unit 105 of the bill data processing apparatus 10 receives the bill data to which the electronic signature is added through the control unit 101.
In step S410, the bill data storage unit 105 of the bill data processing apparatus 10 stores the bill data according to the storage requirements. Here, as shown in FIG. 7, the invoice data of the customer B in “Country 1” can be stored in an arbitrary location in the csv format. Accordingly, the invoice data storage unit 105 stores each element (provider name, customer name, item name, unit price, quantity, tax rate, sum of billing amount, etc.) constituting the generated invoice data in the csv format. Then, store it in any storage device.
Regarding the processing of S410, the bill data processing apparatus 10 may calculate a billing amount of bill data stored in the bill data storage unit 105. For example, when using the system according to the present embodiment, the amount of money for a certain period (one month unit, half year unit, etc.) or a certain amount (invoice processing number, etc.) based on the processing amount negotiated between users in advance. May be calculated.
Further, the customer B or the customer D may access the amount calculated by the invoice data processing system 1 by itself.
It goes without saying that the configurations of the embodiments and operation examples described above can be implemented in any combination as long as they do not contradict each other.
DESCRIPTION OF SYMBOLS 1 Invoice data processing system 10 Invoice data processing apparatus 20 Electronic signature system 30 Core system 101 Control part 102 Document acquisition part 103 Policy information storage part 104 Generation part 105 Invoice data storage part 106 Status output part 111 Acquisition part 112 Calculation Section 113 Formatting section 114 Output section 151 Policy information 152 Invoice data 161 Tax rate information 162 Storage requirement information 201 Electronic signature section 301 Customer information 302 Transaction information
Japanese Patent Laid-Open No. 2003-030431 JP 2001-326762 A JP 2007-072965 A
The first regulation information regulates a tax rate applied to each amount of the transaction.
The information processing system according to claim 1, further comprising: a generation unit that generates the bill data from the transaction information based on the first regulation information.
A calculation unit for calculating the total amount of each transaction;
The generation unit generates the bill data by applying the first regulation information to the total amount calculated by the calculation unit.
A customer information storage unit storing customer information associated with each customer to which information to apply, among the information defined in the first regulation information and the second regulation information;
A customer information acquisition unit for acquiring the customer information;
The information processing system according to claim 4, comprising:
The generating unit generates the bill data from the transaction information using predetermined information in the first regulation information associated with the customer information.
The second regulation information defines the storage period and storage location of the bill data.
The information processing system according to any one of claims 1 to 6.
The storage control unit controls to store the bill data in a predetermined storage device based on a storage term and a storage location of the bill data.
The information processing system according to claim 1, further comprising: a transaction information storage unit that stores the transaction information input as paper, facsimile data, or electronic data.
The second definition information further defines whether or not an electronic signature needs to be added to the bill data.
An information processing apparatus that performs information processing based on transaction information,
A method of controlling an information processing apparatus that performs information processing based on transaction information,
A transaction information acquisition step of acquiring the transaction information;
Control to store the bill data generated based on the first regulation information applied to the amount of each transaction included in the transaction information based on the second regulation information applied to the bill data A memory control process;
The control method of the information processing apparatus for executing
A program that causes a computer to function as an information processing device that performs information processing based on transaction information,
JP2014021248A 2013-03-07 2014-02-06 Information processing system, information processing apparatus, control method of information processing apparatus and program Pending JP2015156052A (en)
JP2013045784 2013-03-07
JP2014003948 2014-01-14
JP2014021248A JP2015156052A (en) 2013-03-07 2014-02-06 Information processing system, information processing apparatus, control method of information processing apparatus and program
US14/196,044 US20140258059A1 (en) 2013-03-07 2014-03-04 Information processing system, information processing apparatus, method of controlling an information processing apparatus, and program
EP14157696.7A EP2775444A1 (en) 2013-03-07 2014-03-04 Information processing system, information processing apparatus, method of controlling an information processing apparatus, and program
AU2014201213A AU2014201213B2 (en) 2013-03-07 2014-03-05 Information Processing System, Information Processing Apparatus, Method Of Controlling An Information Processing Appataus, And Program
KR1020140027021A KR20140110777A (en) 2013-03-07 2014-03-07 Information processing system, information processing apparatus, method of controlling an information processing apparatus, and program
JP2015156052A true JP2015156052A (en) 2015-08-27
ID=50276915
JP2014021248A Pending JP2015156052A (en) 2013-03-07 2014-02-06 Information processing system, information processing apparatus, control method of information processing apparatus and program
US (1) US20140258059A1 (en)
EP (1) EP2775444A1 (en)
JP (1) JP2015156052A (en)
KR (1) KR20140110777A (en)
AU (1) AU2014201213B2 (en)
JP2017052436A (en) * 2015-09-10 2017-03-16 トヨタ自動車株式会社 Vehicle front part structure
JP2008262380A (en) * 2007-04-12 2008-10-30 Shinji Mori Invoice (or estimate or delivery card) creation system
JP2011065640A (en) * 2009-08-21 2011-03-31 Youtohands Co Ltd Document management system and method therefor
JP2001326762A (en) 2000-03-09 2001-11-22 Ricoh Co Ltd Data processing apparatus and its controlling method
JP2003030431A (en) 2001-07-06 2003-01-31 Hsbc Holdings Plc Representative server, bank business system and customer terminal
JP2006347638A (en) * 2005-06-13 2006-12-28 Pascal:Kk Shipment support system
JP2007072965A (en) 2005-09-09 2007-03-22 Mitsubishi Electric Corp Data processor and data processing method
DE102011017400A1 (en) * 2011-04-18 2012-10-18 Tobias Gramer Arrangement for automatically creating accounting records of invoices related to e.g. motor vehicle insurances, performs account assignment with uniform scheme of accounts by supplier, where data for billing account are read from invoices
2014-02-06 JP JP2014021248A patent/JP2015156052A/en active Pending
2014-03-04 US US14/196,044 patent/US20140258059A1/en not_active Abandoned
2014-03-04 EP EP14157696.7A patent/EP2775444A1/en not_active Withdrawn
2014-03-05 AU AU2014201213A patent/AU2014201213B2/en active Active
2014-03-07 KR KR1020140027021A patent/KR20140110777A/en active Search and Examination
EP2775444A1 (en) 2014-09-10
AU2014201213A1 (en) 2014-09-25
KR20140110777A (en) 2014-09-17
US20140258059A1 (en) 2014-09-11
AU2014201213B2 (en) 2015-11-19
JP6179853B2 (en) 2017-08-16 Accounting system, accounting program, and book
US10216713B2 (en) 2019-02-26 Generating documents using templates
US7209897B2 (en) 2007-04-24 Systems and methods for charge-back invoice generation