JP2018063690A - Information processing system, information processing device, and information processing method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To support certificate registration for expense settlement.SOLUTION: An information processing system connected with an expense settlement system includes: reception means for receiving first image data including one or more certificate images for expense settlement from an apparatus connected with the information processing system; extraction means for extracting the one or more certificate images included in the first image data received by the reception means and generating one or more pieces of second image data corresponding to the respective one or more certificate images; and registration means for registering each of the one or more pieces of second image data generated by the extraction means with the expense settlement system.SELECTED DRAWING: Figure 4

Description

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

  In recent years, services that provide a function combining a plurality of functions (for example, scanning, printing, mail delivery, file upload to an external service, etc.) have been known. For example, a service for uploading an electronic file generated by scanning to an external service is known. Such a service is realized by executing one or more processes for realizing each function as a series of processes.

  There is also known an image forming apparatus that executes a series of processes based on an instruction sheet including processing information representing one or more processes as a series of processes (see, for example, Patent Document 1).

  However, it has not been possible to provide a service for registering certificates for certifying expenses such as receipts and receipts in cooperation with external services such as expense settlement services. For this reason, for example, it has not been possible to provide a service for registering an image file generated by scanning a receipt or the like with an image forming apparatus in an external expense settlement service.

  One embodiment of the present invention has been made in view of the above points, and an object thereof is to support certificate registration for expense settlement.

  In order to achieve the above object, an embodiment of the present invention provides an information processing system connected to an expense settlement system, wherein one or more certificates for expense settlement are received from a device connected to the information processing system. Receiving means for receiving first image data including an image; and extracting the one or more certificate images included in the first image data received by the receiving means to extract the one or more certificates. Extraction means for creating one or more second image data corresponding to each document image; registration means for registering each of the one or more second image data created by the extraction means in the expense settlement system; Have

  According to an embodiment of the present invention, it is possible to support certificate registration for expense settlement.

1 is a diagram illustrating a system configuration of an example of an information processing system according to a first embodiment. It is a figure which shows the hardware constitutions of an example of the service provision system which concerns on 1st embodiment, and a PC terminal. It is a figure which shows the hardware constitutions of an example of the apparatus which concerns on 1st embodiment. It is a figure explaining the outline of the receipt registration service concerning a first embodiment. It is a figure which shows the function structure of an example of the information processing system which concerns on 1st embodiment. It is a figure which shows the function structure of an example of the logic process part which concerns on 1st embodiment. It is a figure which shows an example of the process flow information in which a series of processes which implement | achieve the receipt registration service which concerns on 1st embodiment were defined. It is a figure which shows an example of the process flow information in which a series of processes performed repeatedly are defined in a series of processes which implement | achieve the receipt registration service which concerns on 1st embodiment. It is a sequence diagram which shows an example of the whole process in the case of using the receipt registration service which concerns on 1st embodiment. It is a figure which shows an example of the utilization screen of a receipt registration service. It is a sequence diagram which shows an example of the execution process of the processing flow which implement | achieves the receipt registration service which concerns on 1st embodiment. It is a sequence diagram which shows an example of the registration process of a receipt which concerns on 1st embodiment. It is a sequence diagram which shows an example of the whole process in the case of utilizing the expense adjustment service which concerns on 1st embodiment. It is a figure which shows an example of the screen transition in an expense adjustment service. It is a figure which shows the hardware constitutions of an example of the apparatus which concerns on 2nd embodiment. It is a figure which shows an example of the process flow information in which a series of processes which implement | achieve the receipt registration service which concerns on 2nd embodiment were defined. It is a figure which shows an example of the process flow information in which a series of processes performed repeatedly are defined in a series of processes which implement | achieve the receipt registration service which concerns on 2nd embodiment. It is a sequence diagram which shows an example of the whole process in the case of using the receipt registration service which concerns on 2nd embodiment. It is a figure which shows an example of the screen transition in a receipt registration service. It is a figure which shows an example of imaging | photography of a receipt. It is a figure which shows the other example of imaging | photography of a receipt. It is a sequence diagram which shows an example of the execution process of the processing flow which implement | achieves the receipt registration service which concerns on 2nd embodiment. It is a sequence diagram which shows an example of the extraction process of the receipt image which concerns on 2nd embodiment. It is a figure which shows the function structure of an example of the information processing system which concerns on 3rd embodiment. It is a figure which shows an example of token information. It is a sequence diagram which shows an example of the setting process of the authentication cooperation which concerns on 3rd embodiment. It is a figure which shows an example of the screen transition in the setting of authentication cooperation. It is a sequence diagram which shows an example of the whole process in the case of using the receipt registration service which concerns on 3rd embodiment. It is a figure which shows an example of the utilization screen of a receipt registration service. It is a figure which shows the function structure of an example of the information processing system which concerns on 4th embodiment. It is a sequence diagram which shows an example of the setting process of the agent which concerns on 4th embodiment. It is a figure which shows an example of an agent setting screen. It is a sequence diagram which shows an example of the whole process in the case of using the receipt registration service which concerns on 4th embodiment on behalf. It is a figure which shows an example of the screen transition in the case of using a receipt registration service on behalf. It is a figure which shows the other example of the screen transition in the case of using a receipt registration service on behalf. It is a figure which shows the function structure of an example of the logic processing part which concerns on 5th embodiment. It is a figure which shows an example of a template registration screen. It is a figure which shows an example of the process flow information in which a series of processes which implement | achieve the receipt registration service which concerns on 5th embodiment were defined. It is a sequence diagram which shows an example of the whole process in the case of using the receipt registration service which concerns on 5th embodiment. It is a figure which shows an example of a template selection screen. It is a sequence diagram (1/2) which shows an example of the execution process of the processing flow which implement | achieves the receipt registration service which concerns on 5th embodiment. It is a sequence diagram (2/2) which shows an example of the execution process of the processing flow which implement | achieves the receipt registration service which concerns on 5th embodiment. It is a sequence diagram which shows an example of the registration process of the receipt which concerns on 5th embodiment.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[First embodiment]
<System configuration>
First, the system configuration of the information processing system 1 according to the present embodiment will be described with reference to FIG. FIG. 1 is a diagram illustrating a system configuration of an example of an information processing system 1 according to the present embodiment.

  An information processing system 1 shown in FIG. 1 includes a service providing system 10, a device 20, a PC terminal 30, and an expense settlement system 40, which are communicably connected via a wide area network N1 such as the Internet. Yes.

  The service providing system 10 is realized by one or more information processing apparatuses, and is realized by a series of processes that combine one or more processes among a plurality of processes that realize various functions via the network N1. Provide various services.

  The functions include, for example, printing, scanning, facsimile transmission, data format conversion, mail delivery, OCR (Optical Character Recognition) processing, processing, compression / decompression, storage in a repository, and the like. The function includes, for example, cooperation with an external service (for example, an expense settlement service provided by the expense settlement system 40).

  The service providing system 10 according to the present embodiment provides a service realized by a series of processes including a process for realizing cooperation with the expense settlement service. Specific examples of services provided by the service providing system 10 according to the present embodiment will be described later. Hereinafter, a series of processing is also referred to as “processing flow”.

  The device 20 is various electronic devices used by the user. That is, the device 20 is an image forming apparatus such as an MFP (Multifunction Peripheral). The user can use various services provided by the service providing system 10 using the device 20.

  However, the device 20 is not limited to the image forming apparatus, and may be, for example, a smartphone, a tablet terminal, a digital camera, a projector, an electronic blackboard, or the like.

Hereinafter, when distinguishing each of the plurality of devices 20, they are described using a subscript such as “device 20 ₁ ”, “device 20 ₂ ”, and the like.

  The PC terminal 30 is, for example, a desktop PC (personal computer), a notebook PC, a smartphone, a tablet terminal, or the like used by the user. The user can use the expense settlement service provided by the expense settlement system 40.

Hereinafter, when distinguishing each of the plurality of PC terminals 30, they are described using subscripts such as “PC terminal 30 ₁ ” and “PC terminal 30 ₂ ”.

  The expense settlement system 40 is a computer system that provides an expense settlement service via the network N1. The expense adjustment service is a service for adjusting travel expenses, travel expenses, entertainment expenses, etc. as expenses. The user can use the expense settlement service by accessing the expense settlement system 40 using, for example, a browser installed in the PC terminal 30.

  The configuration of the information processing system 1 illustrated in FIG. 1 is an example, and other configurations may be used. For example, the information processing system 1 according to the present embodiment includes various devices that perform at least one of input and output of electronic data, and these devices may use services provided by the service providing system 10. .

<Hardware configuration>
Next, the hardware configuration of the service providing system 10 and the PC terminal 30 included in the information processing system 1 according to the present embodiment will be described with reference to FIG. FIG. 2 is a diagram illustrating a hardware configuration of an example of the service providing system 10 and the PC terminal 30 according to the present embodiment. Since the service providing system 10 and the PC terminal 30 have the same hardware configuration, the hardware configuration of the service providing system 10 will be mainly described below.

  A service providing system 10 illustrated in FIG. 2 includes an input device 11, a display device 12, an external I / F 13, and a RAM (Random Access Memory) 14. The service providing system 10 includes a ROM (Read Only Memory) 15, a CPU (Central Processing Unit) 16, a communication I / F 17, and an HDD (Hard Disk Drive) 18. Each of these hardware is connected by a bus B.

  The input device 11 includes a keyboard, a mouse, a touch panel, and the like, and is used by a user to input each operation signal. The display device 12 includes a display and the like, and displays a processing result by the service providing system 10. Note that at least one of the input device 11 and the display device 12 may be connected to the service providing system 10 when necessary.

  The communication I / F 17 is an interface that connects the service providing system 10 to the network N1. Thereby, the service providing system 10 can perform communication via the communication I / F 17.

  The HDD 18 is a nonvolatile storage device that stores programs and data. The programs and data stored in the HDD 18 include an OS (Operating System) that is basic software for controlling the entire service providing system 10 and application software that provides various functions on the OS.

  The service providing system 10 may use a drive device (for example, a solid state drive: SSD) that uses a flash memory as a storage medium instead of the HDD 18. The HDD 18 manages stored programs and data by a predetermined file system and / or DB.

  The external I / F 13 is an interface with an external device. The external device includes a recording medium 13a. Thereby, the service providing system 10 can read and write to the recording medium 13a via the external I / F 13. Examples of the recording medium 13a include a flexible disk, a CD, a DVD, an SD memory card, and a USB memory.

  The ROM 15 is a non-volatile semiconductor memory that can retain programs and data even when the power is turned off. The ROM 15 stores programs and data such as BIOS (Basic Input / Output System), OS settings, and network settings that are executed when the service providing system 10 is activated. The RAM 14 is a volatile semiconductor memory that temporarily stores programs and data.

  The CPU 16 is an arithmetic device that realizes control and functions of the entire service providing system 10 by reading a program and data from a storage device such as the ROM 15 and the HDD 18 onto the RAM 14 and executing processing.

  The service providing system 10 and the PC terminal 30 according to the present embodiment can implement various processes as described later by having the hardware configuration shown in FIG.

  Next, a hardware configuration when the device 20 included in the information processing system 1 according to the present embodiment is an image forming apparatus will be described with reference to FIG. FIG. 3 is a diagram illustrating a hardware configuration of an example of the device 20 according to the present embodiment.

  The device 20 illustrated in FIG. 3 includes a controller 21, an operation panel 22, an external I / F 23, a communication I / F 24, a printer 25, and a scanner 26. The controller 21 includes a CPU 31, a RAM 32, a ROM 33, an NVRAM 34, and an HDD 35.

  The ROM 33 is a nonvolatile semiconductor memory that stores various programs and data. The RAM 32 is a volatile semiconductor memory that temporarily stores programs and data. The NVRAM 34 stores setting information, for example. The HDD 35 is a non-volatile storage device that stores various programs and data.

  The CPU 31 is an arithmetic unit that realizes control and functions of the entire device 20 by reading programs, data, setting information, and the like from the ROM 33, the NVRAM 34, the HDD 35, and the like onto the RAM 32 and executing processing.

  The operation panel 22 includes an input unit that receives input from a user and a display unit that performs display. The external I / F 23 is an interface with an external device. The external device includes a recording medium 23a. Thereby, the device 20 can read and / or write the recording medium 23a via the external I / F 23. Examples of the recording medium 23a include an IC card, a flexible disk, a CD, a DVD, an SD memory card, and a USB memory.

  The communication I / F 24 is an interface that connects the device 20 to the network N1. Thereby, the device 20 can perform communication via the communication I / F 24. The printer 25 is a printing device that prints print data. The scanner 26 is a reading device that reads an original and generates an electronic file (image file).

  The device 20 according to the present embodiment has the hardware configuration shown in FIG.

<Services provided by the service providing system>
Here, services provided by the service providing system 10 according to the present embodiment will be described. In the present embodiment, description will be made assuming that the device 20 is an image forming apparatus.

  The service providing system 10 according to the present embodiment extracts an area indicating a receipt from a scanned image file generated by scanning a receipt placed on the document table (scanner 26) of the device 20, and obtains the receipt image file. Providing services to create and register for expense settlement services.

  That is, as shown in FIG. 4, the service providing system 10 according to the present embodiment includes, for example, regions R110 to R130 indicating receipts from a scanned image file G100 generated by scanning three receipts. The receipt image files G110 to G130 are created by extraction. Then, the service providing system 10 according to the present embodiment registers the created receipt image files G110 to G130 in the expense settlement service.

  Description will be made assuming that the above-described service (hereinafter referred to as “receipt registration service”) according to the present embodiment is provided.

  However, the service provided by the service providing system 10 is not limited to this. For example, the service providing system 10 performs an OCR process, an encryption process, etc. on a receipt image file created by extracting an area indicating a receipt from a scanned image file. A service to register may be provided.

<Functional configuration>
Next, the functional configuration of the information processing system 1 according to the present embodiment will be described with reference to FIG. FIG. 5 is a diagram illustrating a functional configuration of an example of the information processing system 1 according to the present embodiment.

  The device 20 illustrated in FIG. 5 includes a client application 210 that is executed by, for example, the CPU 31 or the like. The client application 210 is an application program for using a service provided by the service providing system 10. The user can use the receipt registration service provided by the service providing system 10 using the client application 210 installed in the device 20.

  The PC terminal 30 illustrated in FIG. 5 includes a browser 310 that is executed by the CPU 16 or the like, for example. The user of the PC terminal 30 can use the expense settlement service provided by the expense settlement system 40 via the browser 310.

  The service providing system 10 illustrated in FIG. 5 includes an input / output service processing unit 110 and a document service unit 120. Each of these functional units is realized by a process that the CPU 16 causes one or more programs installed in the service providing system 10 to execute.

  The service providing system 10 illustrated in FIG. 5 includes an application information storage unit 130. The storage unit can be realized by the HDD 18. The application information storage unit 130 may be realized by a storage device or the like connected to the service providing system 10 via the network N1.

  The input / output service processing unit 110 performs processing related to services provided by the service providing system 10. Here, the input / output service processing unit 110 includes an application management unit 111 and a logic processing unit 112.

  The application management unit 111 manages application information 1000 stored in the application information storage unit 130. The application information 1000 is an application for providing a service realized by a series of processes. That is, various services (for example, receipt registration service) provided by the service providing system 10 are provided by the application information 1000.

  In addition, the application management unit 111 returns processing flow information 1100 included in the application information 1000 in response to a request from the logic processing unit 112. The process flow information 1100 is information that defines a series of processes for realizing a service provided by the application information 1000.

  In response to a request from the client application 210, the logic processing unit 112 acquires processing flow information 1100 included in the application information 1000 from the application management unit 111. Then, based on the processing flow information 1100 acquired from the application management unit 111, the logic processing unit 112 executes a series of processing (processing flow) for realizing the service provided by the application information 1000. Thereby, the service providing system 10 according to the present embodiment can provide various services (for example, a receipt registration service).

  The document service unit 120 executes predetermined processing included in a series of processing (processing flow) based on the processing flow information 1100. Here, the document service unit 120 includes a region extraction unit 121.

  The area extraction unit 121 extracts a predetermined area (for example, an area indicating a receipt) from the scanned image file, and creates one or more image files (for example, a receipt image file). The region extraction unit 121 performs such extraction of a predetermined region by using an image processing technique such as template matching, for example.

  The document service unit 120 includes, for example, an encryption / decryption unit that encrypts or decrypts an electronic file, a compression / decompression unit that compresses or decompresses an electronic file, an OCR processing unit that performs OCR processing on the electronic file, and the like. You may have.

  As described above, the document service unit 120 includes various functional units that execute predetermined processing included in a series of processing (processing flow). Therefore, the document service unit 120 is realized by a group of programs (modules) that provide these various functions.

  The application information storage unit 130 stores application information 1000. The application information 1000 is stored in the application information storage unit 130 in association with an application ID that identifies the application information 1000. The application information 1000 may be associated with an application name.

  Here, the application information 1000 includes processing flow information 1100. For example, the application information 1000 that provides the receipt registration service includes processing flow information 1100 that defines a series of processes for realizing the service.

  Note that the application information 1000 may include two or more processing flow information 1100.

  As described above, the processing flow information 1100 is information in which a series of processing (processing flow) for realizing the service provided by the application information 1000 is defined. Details of the processing flow information 1100 will be described later.

  Here, a detailed functional configuration of the logic processing unit 112 will be described with reference to FIG. FIG. 6 is a diagram illustrating a functional configuration of an example of the logic processing unit 112 according to the present embodiment.

  The logic processing unit 112 illustrated in FIG. 6 includes a flow execution unit 301, a component management unit 302, and a component group 303.

  In response to a request from the client application 210, the flow execution unit 301 acquires processing flow information 1100 included in the application information 1000 from the application management unit 111. The flow execution unit 301 executes a series of processing (processing flow) based on the processing flow information 1100 acquired from the application management unit 111.

  Here, a series of processing (processing flow) based on the processing flow information 1100 is executed by combining components for executing each processing included in the series of processing. The component is realized by a program, a module, or the like for executing processing for realizing a predetermined function, and is defined by, for example, a class or a function.

  The component management unit 302 manages components. The component management unit 302 generates a component in response to a request from the flow execution unit 301 and returns the generated component to the flow execution unit 301. The generation of a component means that a component defined by, for example, a class or a function is expanded on a memory (for example, the RAM 14).

  The component group 303 is a set of components. The component group 303 includes a region extraction component 410, an expense settlement component 420, and an iterative component 430.

  The region extraction component 410 is a component for creating a receipt image file. In other words, the region extraction component 410 requests the region extraction unit 121 of the document service unit 120 to perform processing, thereby extracting a region indicating a receipt from the scan image file and creating a receipt image file.

  The expense settlement component 420 is a component for making various requests to the expense settlement system 40. That is, the expense settlement component 420 requests the expense settlement system 40 to create a ledger in which the receipt image file is registered. The expense settlement component 420 requests registration of a receipt image file in the ledger.

  The iteration component 430 is a component for realizing iteration of one or more processes. That is, the repetition component 430 realizes repetition of one or more processes by repeatedly executing another series of processes (processing flow) including one or more processes a predetermined number of times.

  In addition to these components, the component group 303 includes various components such as a compression component for compressing an electronic file and a conversion component for converting the data format of the electronic file.

  Each component included in the component group 303 has a component common I / F 400. The component common I / F 400 is an API (Application Program Interface) defined in common for each component, and includes an API for generating a component and an API for executing processing of the component.

  Note that the component management unit 302 may generate each component included in the component group 303 by the component common I / F 400, for example, when the service providing system 10 is activated.

  Here, processing flow information 1100 in which a series of processing (processing flow) for realizing the receipt registration service according to the present embodiment is defined will be described with reference to FIG. FIG. 7 is a diagram showing an example of processing flow information 1100 in which a series of processes for realizing the receipt registration service is defined.

  The process flow information 1100 illustrated in FIG. 7 includes a flow ID 1101 for identifying the process flow information 1100 and a flow detail 1102 in which process details of each process included in the process flow are defined.

  The flow details 1102 include process definitions 1111 to 1113 that define the processing content of each process included in the processing flow. The process definitions 1111 to 1113 include ““ component ”” indicating the component name of the component for executing the process, and ““ parameters ”” in which parameter information for the component is defined.

  Specifically, the component name “extract” of the region extraction component 410 is defined in ““ component ”” of the process definition 1111. In addition, parameter information for the region extraction component 410 is defined in ““ parameters ”” of the process definition 1111.

  The parameter information for the region extraction component 410 includes, for example, parameter information for specifying a region to be extracted (for example, an image file of a receipt to be extracted).

  Similarly, the component name “expense” of the expense adjustment component 420 is defined in ““ component ”” of the process definition 1112. Also, parameter information for the expense settlement component 420 is defined in ““ parameters ”” of the process definition 1112.

  In ““ parameters ”” of the process definition 1112, parameter information ““ auth ”: null” for setting authentication information (for example, a user name, password, access token) for using the expense settlement system 40 is stored. Is defined.

  The parameter information for the expense settlement component 420 includes, for example, parameter information for setting a request (for example, a ledger creation request) to the expense settlement system 40.

  Similarly, the component name ““ iterate ”” of the repetitive component 430 is defined in ““ component ”” of the process definition 1113. Also, parameter information for the repetitive component 430 is defined in ““ parameters ”” of the process definition 1113.

  In "" parameters "" of the process definition 1113, parameter information "" flowid ":" flow101 "" indicating the flow ID of the process flow information 1100 in which a series of processes to be repeatedly executed by the repetitive component 430 is defined is defined. Yes.

  In addition to this, the parameter information for the repetitive component 430 includes, for example, parameter information for setting the number of times that the repetitive component 430 repeatedly executes a series of processes (the number of repetitions).

  As described above, the processing flow information 1100 defines a component that executes each process included in a series of processes and parameter information for the component. Note that the execution order of the processes defined in each process definition is defined in order from the top in the flow details 1102. That is, in a series of processes (process flow) based on the process flow information 1100 illustrated in FIG. 7, the order of the process defined in the process definition 1111, the process defined in the process definition 1112, and the process defined in the process definition 1113. Is executed. However, the present invention is not limited to this, and the process flow information 1100 may define, for example, information indicating the execution order of processes defined in each process definition.

  Thereby, the region extraction component 410 can extract one or more receipt image files by extracting a receipt region included in the scanned image file. Further, the expense settlement component 420 can create a ledger for registering the receipt image file on the expense settlement service.

  Here, the process definition 1113 of the process flow information 1100 illustrated in FIG. 7 defines that the iterative component 430 repeatedly executes a series of processes based on the process flow information 1100 of the flow ID “flow101”. Accordingly, the processing flow information 1100 of the flow ID “flow101” will be described with reference to FIG. FIG. 8 is a diagram showing an example of process flow information 1100 in which a series of processes that are repeatedly executed in a series of processes that realize the receipt registration service are defined.

  The processing flow information 1100 illustrated in FIG. 8 includes a flow ID 1201 and flow details 1202.

  The flow details 1202 includes a process definition 1211. The process definition 1211 includes ““ component ”” indicating the component name of the component for executing the process, and ““ parameters ”” in which parameter information for the component is defined.

  Specifically, a component name “expense” of the expense adjustment component 420 is defined in ““ component ”” of the process definition 1211. In addition, parameter information for the expense adjustment component 420 is defined in ““ parameters ”” of the process definition 1211.

  In "" parameters "" of the process definition 1211, parameter information "" auth ": null" for setting authentication information (for example, a user name, password, access token) for using the expense settlement system 40 is included. Is defined.

  The parameter information for the expense settlement component 420 includes, for example, parameter information for setting a request to the expense settlement system 40 (for example, a receipt image file registration request).

  Accordingly, the iterative component 430 can register one or more receipt image files in the expense settlement service by the expense settlement component 420 by repeatedly executing a series of processes based on the processing flow information 1100 shown in FIG. it can.

<Details of processing>
Next, details of processing of the information processing system 1 according to the present embodiment will be described. First, a process in which the user of the device 20 registers the receipt image file (receipt image file) in the expense settlement service using the receipt registration service will be described with reference to FIG. FIG. 9 is a sequence diagram showing an example of overall processing when using the receipt registration service according to the present embodiment.

  First, the user uses the device 20 to display a receipt registration service usage screen (step S901). Then, the client application 210 of the device 20 accepts a display operation of a receipt registration service usage screen. Note that the display operation of the receipt registration service usage screen is, for example, a startup operation of the client application 210 or the like.

  Upon receiving the display operation by the user, the client application 210 displays a receipt registration service usage screen G200 shown in FIG. 10, for example (step S902).

  Here, the receipt registration service use screen G200 shown in FIG. 10 includes a user name input field G210, a password input field G220, and a scan execution button G230. The user name input field G210 and the password input field G220 are input fields for inputting a user name and a password in the expense settlement service as an example of authentication information for using the expense settlement service. The scan execution button G230 is a display component for scanning a receipt and creating a scanned image file.

  Next, the user performs an operation to start using the receipt registration service using the device 20 (step S903). That is, the user sets one or more receipts in the scanner 26 of the device 20, and sets the user name and password in the user name input field G210 and the password input field G220 of the receipt registration service usage screen G200 shown in FIG. Enter each. Then, the user presses the scan execution button G230, and performs the use start operation of the receipt registration service. Then, the client application 210 accepts a use start operation for the receipt registration service. In addition to the receipt, the user may set various certificates for certifying expenses such as a receipt in the scanner 26.

  Upon receiving the use start operation by the user, the client application 210 reads each receipt by the scanner 26 and generates a scan image file including an area where each receipt is displayed (step S904).

  In addition, although the apparatus 20 which concerns on this embodiment produced | generated the image file (scanned image file) by reading a receipt with the scanner 26, it is not restricted to this. For example, when the device 20 is a digital camera, a smartphone, a tablet terminal, or the like, an image file may be generated by shooting a receipt with a camera.

  Next, the client application 210 transmits a processing flow execution request to the logic processing unit 112 (step S905). The processing flow execution request includes a flow ID “flow001” of the processing flow information 1100 for realizing the receipt registration service according to the present embodiment, a scanned image file, authentication information (that is, a user name and a password), and the like. Is included.

  Here, the flow ID “flow001” is associated with, for example, the scan execution button G230 on the receipt registration service use screen G200. However, the flow ID “flow001” may be associated with the receipt registration service use screen G200, for example.

  Next, when receiving a processing flow execution request, the logic processing unit 112 performs processing flow execution processing (step S906). That is, the logic processing unit 112 executes a series of processes based on the process flow information 1100 of the flow ID “flow001” included in the execution request.

  Then, the logic processing unit 112 returns the processing result of the processing flow execution process to the client application 210. Thereby, the service providing system 10 according to the present embodiment can provide a receipt registration service to the device 20.

  Here, the details of the process flow execution process shown in FIG. 9 (the process of step S906) will be described with reference to FIG. FIG. 11 is a sequence diagram showing an example of processing flow execution processing for realizing the receipt registration service according to the present embodiment.

  First, when receiving a processing flow execution request from the client application 210, the flow execution unit 301 transmits a processing flow information acquisition request to the application management unit 111 (step S1101). The process flow information acquisition request includes the flow ID “flow001” acquired from the process flow execution request.

  Upon receiving the processing flow information acquisition request, the application management unit 111 acquires the processing flow information 1100 of the flow ID “flow001” included in the acquisition request from the application information 1000 stored in the application information storage unit 130. (Step S1102). That is, the application management unit 111 acquires the processing flow information 1100 illustrated in FIG. 7 from the application information storage unit 130.

  Then, the application management unit 111 returns the processing flow information 1100 acquired from the application information storage unit 130 to the logic processing unit 112.

  The flow execution unit 301 transmits a component acquisition request based on the processing flow information 1100 illustrated in FIG. 7 to the component management unit 302 (step S1103). That is, the flow execution unit 301 sends a component acquisition request for the component having the component name “etract” defined in ““ component ”” included in the process definition 1111 of the process flow information 1100 illustrated in FIG. Send to.

  Upon receiving the component acquisition request, the component management unit 302 generates a component with the component name “etract” (ie, the region extraction component 410) (step S1104). The region extraction component 410 can be generated using an API for generating a component defined in the component common I / F 400.

  Then, the component management unit 302 returns the generated region extraction component 410 to the flow execution unit 301. That is, the component management unit 302 returns, for example, an address on a memory (for example, the RAM 14) in which the area extraction component 410 is expanded to the flow execution unit 301.

  Next, the flow execution unit 301 transmits a component execution request to the region extraction component 410 (step S1105).

  The component execution request includes data. Here, the data is a scanned image file included in the processing flow execution request received from the client application 210. As described above, the flow execution unit 301 simply transmits electronic data such as an image file to each component as “data” (that is, without being aware of the data format).

  Further, the component execution request includes each parameter information defined in ““ parameters ”” included in the process definition 1111 of the process flow information 1100 illustrated in FIG. 7.

  Upon receiving the component execution request, the region extraction component 410 executes processing on the data included in the execution request using the parameter information (step S1106). In other words, the area extraction component 410 uses the area extraction unit 121 of the document service unit 120 to extract a receipt area included in the scanned image file, thereby creating a receipt image file. When a plurality of receipt areas are included in the scanned image file, the area extraction component 410 extracts each of the plurality of receipt areas and creates a plurality of receipt image files.

  In addition, for example, when a scan image file includes a region indicating a receipt, the region extraction component 410 may extract a region indicating the receipt and create a receipt image file. In this case, the receipt image file is registered in the expense settlement service by the receipt registration service.

  Further, for example, when the receipt area included in the scan image file is inclined, the receipt image file is created by rotating and extracting the area.

  Then, the region extraction component 410 returns data indicating the created receipt image file to the flow execution unit 301.

  Next, the flow execution unit 301 transmits a component acquisition request based on the processing flow information 1100 illustrated in FIG. 7 to the component management unit 302 (step S1107). In other words, the flow execution unit 301 sends a component acquisition request for the component with the component name “expense” defined in ““ component ”” included in the process definition 1112 of the process flow information 1100 shown in FIG. Send to.

  When the component management unit 302 receives the component acquisition request, the component management unit 302 generates a component with the component name “expense” (that is, the expense adjustment component 420) (step S1108). The expense settlement component 420 can be generated using an API for generating a component defined in the component common I / F 400.

  Then, the component management unit 302 returns the generated expense settlement component 420 to the flow execution unit 301. That is, for example, the component management unit 302 returns the address on the memory (for example, the RAM 14) in which the expense adjustment component 420 is expanded to the flow execution unit 301.

  Next, the flow execution unit 301 transmits a component execution request to the expense adjustment component 420 (step S1109).

  The component execution request includes each parameter information defined in ““ parameters ”” included in the process definition 1112 of the process flow information 1100 illustrated in FIG.

  That is, the component execution request includes parameter information in which authentication information is set for the parameter information ““ auth ”: null”. For example, when the user name “user001” and the password “abcde” are input to the user name input field G210 and the password input field G220 of the receipt registration service use screen G200, the parameter information is ““ auth ”:“ user001 / ”. abcde "".

  In addition, the component execution request includes parameter information for requesting the expense settlement system 40 to create a ledger.

  Upon receiving the component execution request, the expense settlement component 420 executes processing using the parameter information (step S1110). That is, the expense settlement component 420 sends a ledger creation request to the expense settlement system 40. The expense settlement component 420 can make a ledger creation request using, for example, a Web API published by the expense settlement system 40. The ledger creation request includes authentication information.

  Then, the expense settlement system 40 creates a ledger for registering the receipt image file, and returns a ledger ID for identifying the created ledger to the expense settlement component 420 as a processing result. Then, the expense settlement component 420 returns data indicating the ledger ID to the flow execution unit 301.

  In this way, the expense settlement component 420 requests the expense settlement system 40 to create a ledger, thereby creating a ledger for registering the receipt image file on the expense settlement service.

  Next, the flow execution unit 301 transmits a component acquisition request based on the processing flow information 1100 illustrated in FIG. 7 to the component management unit 302 (step S1111). That is, the flow execution unit 301 sends a component acquisition request for a component having the component name ““ iterate ”” defined in ““ component ”” included in the process definition 1113 of the process flow information 1100 illustrated in FIG. Send to.

  When the component management unit 302 receives the component acquisition request, the component management unit 302 generates a component having the component name “iterate” (that is, the repetitive component 430) (step S1112). The iterative component 430 can be generated using an API for generating a component defined in the component common I / F 400.

  Then, the component management unit 302 returns the generated repetitive component 430 to the flow execution unit 301. That is, for example, the component management unit 302 returns the address on the memory (for example, the RAM 14) in which the repetitive component 430 is expanded to the flow execution unit 301.

  Next, the flow execution unit 301 transmits a component execution request to the repetitive component 430 (step S1113).

  The component execution request includes data indicating the receipt image file created by the region extraction component 410. Therefore, when a plurality of receipt image files are created by the region extraction component 410, the component execution request includes a plurality of data indicating the plurality of receipt image files.

  Further, the component execution request includes each parameter information defined in “" parameters "" included in the process definition 1113 of the process flow information 1100 illustrated in FIG. That is, the component execution request includes parameter information ““ flowid ”:“ flow101 ”” and parameter information indicating the ledger ID returned in step S1110.

  Upon receiving the component execution request, the repetitive component 430 transmits a processing flow execution request to the flow execution unit 301 for each piece of data (that is, a receipt image file) included in the execution request (step S1114). That is, the repetitive component 430 repeatedly executes the receipt registration process in step S1115 for the number of receipt image files. The processing flow execution request includes data (that is, a receipt image file), a flow ID “flow101”, and a ledger ID.

  Upon receiving the processing flow execution request, the flow execution unit 301 performs a process (receipt registration process) for registering a receipt image file in the ledger indicated by the ledger ID in the expense settlement service (step S1115). . Then, the flow execution unit 301 returns the processing result of the receipt registration process to the repetition component 430.

  After that, the repetitive component 430 returns data indicating the processing result obtained by repeatedly executing the receipt registration processing in step S1115 to the flow execution unit 301.

  Details of the receipt registration process (the process of step S1115) will be described with reference to FIG. FIG. 12 is a sequence diagram illustrating an example of a receipt registration process according to the present embodiment.

  First, when receiving a processing flow execution request from the repetitive component 430, the flow execution unit 301 transmits a processing flow information acquisition request to the application management unit 111 (step S1201). The processing flow information acquisition request includes the flow ID “flow101” acquired from the processing flow execution request.

  Upon receiving the processing flow information acquisition request, the application management unit 111 acquires the processing flow information 1100 of the flow ID “flow101” included in the acquisition request from the application information 1000 stored in the application information storage unit 130. (Step S1202). That is, the application management unit 111 acquires the processing flow information 1100 illustrated in FIG. 8 from the application information storage unit 130.

  Then, the application management unit 111 returns the processing flow information 1100 acquired from the application information storage unit 130 to the logic processing unit 112.

  Next, the flow execution unit 301 transmits a component execution request to the component having the component name “expense” defined in ““ component ”” included in the process definition 1211 of the process flow information 1100 illustrated in FIG. 8. (Step S1203). That is, the flow execution unit 301 transmits a component execution request to the expense adjustment component 420.

  The component execution request includes data (that is, a receipt image file). In addition, for parameter information ““ auth ”: null”, parameter information in which authentication information is set, parameter information for making a receipt registration request to the expense settlement system 40, and a parameter indicating a ledger ID Information.

  Upon receiving the component execution request, the expense adjustment component 420 executes processing using the data and parameter information (step S1204). That is, the expense settlement component 420 sends a receipt registration request to the expense settlement system 40. The expense settlement component 420 can make a receipt registration request using, for example, a Web API published by the expense settlement system 40. The receipt registration request includes a receipt image file, a ledger ID, and authentication information.

  Then, the expense settlement system 40 registers the receipt image file in the ledger indicated by the ledger ID, and returns the registration result to the expense settlement component 420. Then, the expense settlement component 420 returns data indicating the registration result to the flow execution unit 301.

  In this way, the expense settlement component 420 can register the receipt image file in the ledger on the expense settlement service by requesting the expense settlement system 40 to register the receipt.

  Here, when the receipt image file is registered in the ledger on the expense settlement service, the receipt data corresponding to the receipt image file is registered in the ledger. The receipt data includes items such as account items and dates. For each item included in the receipt data, for example, a processing result (for example, item value of account item, item value of date, etc.) obtained by performing OCR processing on the receipt image file may be set.

  Next, processing when the user of the PC terminal 30 uses the expense settlement service will be described with reference to FIG. FIG. 13 is a sequence diagram illustrating an example of overall processing when using the expense settlement service according to the present embodiment.

  First, the user uses the PC terminal 30 to perform an operation for displaying a login screen of the expense settlement service (step S1301). Then, the browser 310 of the PC terminal 30 receives a display operation for a login screen of the expense settlement service. For example, the user can perform a display operation of the login screen by pressing a link to the login screen of the expense settlement service on a predetermined screen displayed by the browser 310. Note that the user may perform a login screen display operation by, for example, inputting a URL (Uniform Resource Locator) of a login screen of the expense settlement service into an address bar or the like of the browser 310.

  When the browser 310 receives the display operation by the user, the browser 310 transmits a login screen acquisition request to the expense settlement system 40 (step S1302). Then, the expense settlement system 40 returns screen information for displaying the login screen (for example, information in which the login screen is defined in the HTML (HyperText Markup Language) format).

  Upon receiving the screen information for displaying the login screen, the browser 310 displays a login screen G300 shown in FIG. 14A, for example, based on the screen information (step S1303).

  Here, the login screen G300 shown in FIG. 14A includes a user name input field G310, a password input field G320, and a login button G330. The user name input field G310 and the password input field G320 are input fields for inputting a user name and a password in the expense settlement service as an example of authentication information for using the expense settlement service. The login button G330 is a display component for transmitting a login request to the expense settlement service.

  Next, the user performs a login operation to the expense settlement service using the PC terminal 30 (step S1304). That is, the user inputs a user name and password in the user name input field G310 and password input field G320 of the login screen G300 shown in FIG. 14A, and then performs a login operation by pressing the login button G330. . Then, the browser 310 accepts the login operation.

  When accepting the login operation by the user, the browser 310 transmits a login request to the expense settlement system 40 (step S1305). The login request includes authentication information (that is, the user name and password input in the user name input field G310 and the password input field G320).

  Then, the expense settlement system 40 returns the login result to the browser 310 after verifying the validity of the authentication information included in the received login request. Hereinafter, the description will be continued assuming that a login result indicating successful login is returned.

  Upon receiving the login result, the browser 310 transmits an acquisition request for the ledger list screen to the expense settlement system 40 (step S1306). Then, the expense settlement system 40 returns screen information for displaying the ledger list screen (for example, information in which the ledger list screen is defined in the HTML format).

  When the browser 310 receives screen information for displaying the ledger list screen, the browser 310 displays, for example, a ledger list screen G400 shown in FIG. 14B based on the screen information (step S1307).

  Here, a ledger list screen G400 shown in FIG. 14B includes a ledger list G410. The user can edit the receipt data registered in the selected ledger by selecting a desired ledger from the ledger list G410. The user can also create a new ledger by selecting a “create new ledger” icon included in the ledger list G410.

  Next, the user performs a ledger selection operation using the PC terminal 30 (step S1308). That is, the user performs a selection operation for selecting a desired ledger from the ledger list G410 on the ledger list screen G400 shown in FIG. Then, the browser 310 accepts the selection operation. Hereinafter, the description will be continued assuming that the user has selected the “ledger A” icon.

  Upon receiving the selection operation by the user, the browser 310 transmits an acquisition request for the ledger screen of the selected “ledger A” to the expense settlement system 40 (step S1309). Then, the expense settlement system 40 returns screen information for displaying the ledger screen of “ledger A” (for example, information in which the ledger screen is defined in the HTML format).

  Upon receiving screen information for displaying the ledger screen of “ledger A”, the browser 310 displays a ledger screen G500 shown in FIG. 14C, for example, based on the screen information (step S1310).

  Here, the ledger screen G500 shown in FIG. 14C includes a receipt list G510, a receipt edit field G520, a switching tab G530, and an application button G540. The user can input or edit receipt data (for example, account item, date, etc.) in the receipt edit field G520 after selecting a desired receipt from the receipt list G510.

  When the user performs a pressing operation on the switching tab G530 on the ledger screen G500 shown in FIG. 14C, the browser 310 accepts the operation and switches the display to the ledger screen G600 shown in FIG. .

  Here, the ledger screen G600 shown in FIG. 14D includes a receipt image G610 and a switching tab G620. In the receipt image G610, a receipt image file of the receipt selected in the receipt list G510 is displayed. Thereby, the user can input or edit the receipt data in the receipt edit field G520 of the ledger screen G500 shown in FIG. 14C after referring to the receipt image G610.

  When the user performs a pressing operation on the switching tab G620 on the ledger screen G600 shown in FIG. 14D, the browser 310 accepts the operation and switches the display to the ledger screen G500 shown in FIG. .

  Thus, the user can confirm the receipt image G610 by selecting a desired receipt from the receipt list G510. Therefore, the user can input or edit each item (for example, account item or date) included in the receipt edit field G520 after referring to the receipt image G610. The receipt edit field G520 and the receipt image G610 may be displayed on the same screen.

  Next, the user performs a receipt application operation using the PC terminal 30 (step S13111). That is, the user presses the application button G540 on the ledger screen G500 shown in FIG. 14C or the ledger screen G600 shown in FIG. Then, the browser 310 accepts the application operation.

  When the browser 310 accepts the application operation by the user, the browser 310 transmits an expense settlement request for the applied receipt to the expense settlement system 40 (step S1302). Then, the expense settlement system 40 executes, for example, an expense settlement process using a workflow and returns a result for the expense settlement request. Thereby, the receipt in which the receipt data is input or edited by the user is settled as an expense.

[Second Embodiment]
Next, a second embodiment will be described. In the second embodiment, when the device 20 is, for example, a smartphone, a tablet terminal, a digital camera, or the like, a receipt image file is created from a captured image file generated by shooting the receipt. The case of registering for the expense settlement service will be described.

  In the description of the second embodiment, differences from the first embodiment will be mainly described. Locations having substantially the same functional configuration as those in the first embodiment and processes that are substantially the same. The description of the place where the process is executed will be omitted as appropriate.

<Hardware configuration>
First, a hardware configuration when the device 20 included in the information processing system 1 according to the present embodiment is a smartphone or a tablet terminal will be described with reference to FIG. FIG. 15 is a diagram illustrating a hardware configuration of an example of the device 20 according to the present embodiment.

  The device 20 illustrated in FIG. 15 includes an input device 41, a display device 42, an external I / F 43, and a communication I / F 44. The device 20 includes a RAM 45, a CPU 46, a flash memory 47, and a camera device 48. Each of these hardware is connected by a bus 49.

  The input device 41 is a touch panel or the like, and is used by a user to input various operation signals. The display device 42 is a display or the like, and displays a processing result by the device 20.

  The communication I / F 44 is an interface that connects the device 20 to the network N1. Thereby, the device 20 can perform communication via the communication I / F 44.

  The flash memory 47 is, for example, an EEPROM (Electrically Erasable and Programmable Read Only Memory) or the like, and is a nonvolatile storage device for storing programs and data. The programs and data stored in the flash memory 47 include OS that is basic software for controlling the entire device 20, application software that provides various functions on the OS, and the like.

  The external I / F 43 is an interface with an external device. The external device includes a recording medium 43a. Thereby, the device 20 can read and write the recording medium 43a via the external I / F 43. Examples of the recording medium 43a include an SD memory card and a USB memory.

  The RAM 45 is a volatile semiconductor memory that temporarily stores programs and data. The CPU 46 is an arithmetic device that realizes control and functions of the entire device 20 by reading a program and data from a storage device such as the flash memory 47 onto the RAM 45 and executing processing. The camera device 48 is an imaging device that generates an image file (captured image file) by capturing an image within the capturing range.

  The device 20 according to the present embodiment has the hardware configuration illustrated in FIG.

<Services provided by the service providing system>
Here, services provided by the service providing system 10 according to the present embodiment will be described. In the present embodiment, the device 20 is described as being a smartphone or a tablet terminal. However, the device 20 may be, for example, a digital camera, a game device, a wearable information terminal, or the like as long as the camera device 48 is mounted.

  The service providing system 10 according to the present embodiment provides a service (receipt registration service) for creating a receipt image file from a photographed image file generated by the device 20 and registering it in the expense settlement service.

  Here, processing flow information 1100 in which a series of processing (processing flow) for realizing the receipt registration service according to the present embodiment is defined will be described with reference to FIG. FIG. 16 is a diagram showing an example of process flow information 1100 in which a series of processes for realizing the receipt registration service according to the present embodiment is defined.

  The process flow information 1100 illustrated in FIG. 16 includes a flow ID 1301 for identifying the process flow information 1100 and a flow detail 1302 in which process details of each process included in the process flow are defined.

  The flow details 1302 includes process definitions 1311 to 1313 that define the processing content of each process included in the processing flow. The process definitions 1311 to 1313 include ““ component ”” indicating the component name of the component for executing the process, and ““ parameters ”” in which parameter information for the component is defined.

  Specifically, the component name ““ iterate ”” of the repetitive component 430 is defined in ““ component ”” of the process definition 1311. Also, parameter information for the repetitive component 430 is defined in ““ parameters ”” of the process definition 1311.

  In ““ parameters ”” of the process definition 1311, parameter information ““ flowid ”:“ flow102 ”” indicating the flow ID of the process flow information 1100 in which a series of processes to be repeatedly executed by the repetitive component 430 is defined is defined. Yes.

  Similarly, the component name “expense” of the expense adjustment component 420 is defined in ““ component ”” of the process definition 1312. In addition, parameter information for the expense adjustment component 420 is defined in ““ parameters ”” of the process definition 1312.

  In "" parameters "" of the process definition 1312, parameter information "" auth ": null" for setting authentication information (for example, a user name, password, access token) and the like for using the expense settlement system 40 is included. Is defined.

  Similarly, the component name ““ iterate ”” of the repetitive component 430 is defined in ““ component ”” of the process definition 1313. In addition, parameter information for the repetitive component 430 is defined in ““ parameters ”” of the process definition 1313.

  In "" parameters "" of the process definition 1313, parameter information "" flowid ":" flow101 "" indicating the flow ID of the process flow information 1100 in which a series of processes to be repeatedly executed by the repetitive component 430 is defined is defined. Yes.

  As described above, the process definition 1311 of the process flow information 1100 illustrated in FIG. 16 defines that the repetitive component 430 repeatedly executes a series of processes based on the process flow information 1100 of the flow ID “flow102” described later. Yes. Further, the process definition 1312 of the process flow information 1100 shown in FIG. 16 defines that the expense settlement component 420 requests the expense settlement system 40 to create a ledger. Further, the processing flow information 1100 illustrated in FIG. 16 repeatedly causes a series of processing based on the processing flow information 1100 of the flow ID “flow101” to be repeatedly executed, similarly to the processing definition 1113 of the processing flow information 1100 illustrated in FIG. Is defined.

  Here, the process definition 1311 of the process flow information 1100 illustrated in FIG. 16 defines that the repetition component 430 repeatedly executes a series of processes based on the process flow information 1100 of the flow ID “flow102”. Therefore, the processing flow information 1100 of the flow ID “flow102” will be described with reference to FIG. FIG. 17 is a diagram showing an example of process flow information 1100 in which a series of processes to be repeatedly executed is defined in a series of processes for realizing the receipt registration service.

  The processing flow information 1100 illustrated in FIG. 17 includes a flow ID 1401 and flow details 1402.

  The flow details 1402 includes a process definition 1411. The process definition 1411 includes ““ component ”” indicating the component name of the component for executing the process, and ““ parameters ”” in which parameter information for the component is defined.

  Specifically, the component name “extract” of the region extraction component 410 is defined in ““ component ”” of the process definition 1411. In the process definition 1411, parameter information for the region extraction component 410 is defined.

  The parameter information for the region extraction component 410 includes, for example, parameter information for specifying a region to be extracted (for example, an image file of a receipt to be extracted).

  Accordingly, the repetitive component 430 extracts a receipt image file from each of one or more photographed image files by the region extraction component 410 by repeatedly executing a series of processing based on the processing flow information 1100 shown in FIG. Can do.

<Details of processing>
Next, details of processing of the information processing system 1 according to the present embodiment will be described. Hereinafter, FIG. 18 shows a process in which the user of the device 20 extracts a receipt image file from a photographed image file generated by photographing a receipt using the receipt registration service and registers it in the expense reimbursement service. The description will be given with reference. FIG. 18 is a sequence diagram showing an example of overall processing when using the receipt registration service according to the present embodiment.

  First, the user uses the device 20 to display the receipt registration service usage screen (step S1801). Then, the client application 210 of the device 20 accepts a display operation of a receipt registration service usage screen. Note that the display operation of the receipt registration service usage screen is, for example, a startup operation of the client application 210 or the like.

  When the client application 210 receives the operation by the user, the client application 210 displays a receipt registration service use screen G700 shown in FIG. 19A, for example (step S1802).

  Here, the receipt registration service use screen G700 shown in FIG. 19A includes an authentication information input button G710 and a receipt photographing start button G720. The authentication information input button G710 is a display component for transitioning to an authentication information input screen for using the expense settlement service. The receipt shooting start button G720 is a display component for activating the camera device 48 and transitioning to a shooting start screen for shooting a receipt.

  In the receipt registration service use screen G700 shown in FIG. 19A, the user presses the authentication information input button G710 to perform the display operation of the authentication information input screen (step S1803). Then, the client application 210 receives an operation for displaying an authentication information input screen.

  When receiving the operation by the user, the client application 210 displays an authentication information input screen G800 shown in FIG. 19B, for example (step S1804).

  Here, the authentication information input screen G800 shown in FIG. 19B includes a user name input field G810, a password input field G820, an OK button G830, and a cancel button G840. The user name input field G810 and the password input field G820 are input fields for inputting a user name and a password, which are examples of authentication information for using the expense settlement service.

  The OK button G830 stores the user name and password input in the user name input field G810 and the password input field G820, respectively, and returns to the receipt registration service use screen G700 shown in FIG. It is a display component. On the other hand, the cancel button G840 returns to the use screen G700 of the receipt registration service shown in FIG. 19A without saving the user name and password input in the user name input field G810 and the password input field G820, respectively. Display parts.

  In the authentication information input screen G800 shown in FIG. 19B, the user inputs the user name and password in the user name input field G810 and the password input field G820, respectively, and then presses an OK button G830, and the authentication information is displayed. Is input (step S1805). Then, the client application 210 accepts an authentication information input operation.

  Upon receiving the input operation, the client application 210 stores the user name and password input in the user name input field G810 and the password input field G820, respectively, and displays the receipt registration service usage screen G700 (step S1806). ). The client application 210 may store the user name and password input in the user name input field G810 and password input field G820, respectively, in a predetermined storage area of the flash memory 47, for example.

  For example, when authentication information (for example, a user name and a password) is already stored, the above steps S1803 to S1806 may not be performed. That is, in this case, the user presses the receipt shooting start button G720 on the receipt registration service use screen G700 shown in FIG. 19A without pressing the authentication information input button G710, which will be described later. In step S1807, the receipt start operation may be performed.

  In the receipt registration service use screen G700 shown in FIG. 19A, it is assumed that the user has pressed the receipt shooting start button G720 to perform the receipt shooting start operation (step S1807). Then, the client application 210 accepts a receipt shooting start operation.

  Upon receiving the operation by the user, the client application 210 activates the camera device 48 and displays, for example, a shooting start screen G900 shown in FIG. 19C (step S1808).

  Here, the shooting start screen G900 shown in FIG. 19C includes a reference frame G910, a receipt shooting button G920, and a shooting completion button G930. The reference frame G910, the receipt photographing button G920, and the photographing completion button G930 are displayed superimposed on an image showing the photographing range of the camera device 48.

  The reference frame G910 is a marker serving as a reference when photographing a receipt. The user adjusts the distance between the receipt and the device 20 and the enlargement / reduction ratio so that the receipt to be photographed is included in the reference frame G910, so that the receipt appears in an appropriate range in the photographed image. You can shoot like that. The receipt photographing button G920 is a display component for photographing the photographing range by the camera device 48 and generating a photographed image file. The shooting completion button G930 is a display component for ending the receipt shooting.

  Here, taking a receipt will be described with reference to FIG. FIG. 20 is a diagram showing an example of taking a receipt.

  As shown in FIG. 20 (a), the user adjusts the receipt R140 to be photographed to be included in the reference frame G910, and then presses the receipt photographing button G920 to display the receipt R140. You can shoot.

  Further, as shown in FIG. 20B, for example, after the user shoots the receipt R140 by pressing the receipt shooting button G920, the user can continuously shoot the receipt R150. As described above, the user can sequentially photograph a plurality of receipts until the user presses the photographing completion button G930.

  Note that the user may shoot a plurality of receipts in one shooting. That is, for example, as shown in FIG. 21, the user may press the receipt shooting button G920 after adjusting the receipt R140 and the receipt R150 to be included in the reference frame G910.

  On the shooting start screen G900 shown in FIG. 19C, the user adjusts the receipt to be shot within the reference frame G910, and then presses the receipt shooting button G920 to shoot the receipt. It is assumed that an operation has been performed (step S1809). Then, the client application 210 accepts a receipt shooting operation.

  When the client application 210 accepts the operation by the user, the camera device 48 captures an image within the imaging range and generates a captured image file (step S1810).

  As described above, the user can repeatedly perform the receipt photographing operation in step S1810 until the user presses the photographing completion button G930.

  In the shooting start screen G900 shown in FIG. 19C, it is assumed that the user has performed a shooting completion operation by pressing the shooting completion button G930 (step S1811). Then, the client application 210 accepts a shooting completion operation.

  Upon receiving the operation by the user, the client application 210 transmits a processing flow execution request to the logic processing unit 112 (step S1812). The processing flow execution request includes the flow ID “flow002” of the processing flow information 1100 that realizes the receipt registration service according to the present embodiment, and authentication information (that is, a user name and a password). The processing flow execution request includes one or more captured image files generated in step S1810.

  Here, the flow ID “flow002” is associated with the shooting completion button G930 on the shooting start screen G900, for example. However, the flow ID “flow002” may be associated with the shooting start screen G900, for example.

  Next, when receiving the processing flow execution request, the logic processing unit 112 performs the processing flow execution processing (step S1813). That is, the logic processing unit 112 executes a series of processes based on the process flow information 1100 of the flow ID “flow002” included in the execution request.

  Then, the logic processing unit 112 returns the processing result of the processing flow execution process to the client application 210. Thereby, the service providing system 10 according to the present embodiment can provide a receipt registration service to the device 20.

  Here, the details of the process flow execution process shown in FIG. 18 (step S1813) will be described with reference to FIG. FIG. 22 is a sequence diagram showing an example of execution processing of a processing flow for realizing the receipt registration service according to the present embodiment.

  First, when receiving a processing flow execution request from the client application 210, the flow execution unit 301 transmits a processing flow information acquisition request to the application management unit 111 (step S2201). The processing flow information acquisition request includes the flow ID “flow002” acquired from the processing flow execution request.

  Upon receiving the processing flow information acquisition request, the application management unit 111 acquires the processing flow information 1100 of the flow ID “flow002” included in the acquisition request from the application information 1000 stored in the application information storage unit 130. (Step S2202). That is, the application management unit 111 acquires the processing flow information 1100 illustrated in FIG. 16 from the application information storage unit 130.

  Then, the application management unit 111 returns the processing flow information 1100 acquired from the application information storage unit 130 to the logic processing unit 112.

  The flow execution unit 301 transmits a component acquisition request based on the processing flow information 1100 illustrated in FIG. 16 to the component management unit 302 (step S2203). That is, the flow execution unit 301 sends a component acquisition request for the component having the component name ““ iterate ”” defined in ““ component ”” included in the process definition 1311 of the process flow information 1100 illustrated in FIG. Send to.

  When the component management unit 302 receives the component acquisition request, the component management unit 302 generates a component having the component name “iterate” (that is, the repetitive component 430) (step S2204). The iterative component 430 can be generated using an API for generating a component defined in the component common I / F 400.

  Then, the component management unit 302 returns the generated repetitive component 430 to the flow execution unit 301. That is, for example, the component management unit 302 returns the address on the memory (for example, the RAM 14) in which the repetitive component 430 is expanded to the flow execution unit 301.

  Next, the flow execution unit 301 transmits a component execution request to the repetitive component 430 (step S2205).

  The component execution request includes one or more data. Here, the data is a captured image file included in the processing flow execution request received from the client application 210.

  Further, the component execution request includes each parameter information defined in ““ parameters ”” included in the process definition 1311 of the process flow information 1100 illustrated in FIG. 16. That is, the component execution request includes the parameter information ““ flowid ”:“ flow102 ””.

  When the repetitive component 430 receives a component execution request, the repetitive component 430 transmits a processing flow execution request to the flow execution unit 301 for each of one or more pieces of data (that is, one or more captured image files) included in the execution request ( Step S2206). That is, the repetitive component 430 repeatedly executes the receipt image extraction process in step S2207 for the number of times of the number of photographed image files. The processing flow execution request includes data (that is, a captured image file) and a flow ID “flow102”.

  Upon receiving the processing flow execution request, the flow execution unit 301 extracts a receipt image from the photographed image file and performs a process (receipt image extraction process) for creating a receipt image file (step S2207). ). Then, the flow execution unit 301 returns the processing result of the receipt image extraction process (that is, data indicating the receipt image file extracted from the captured image file) to the repetitive component 430.

  After that, the repetitive component 430 returns data indicating the processing result obtained by repeatedly executing the receipt image extraction processing in step S <b> 2207 to the flow execution unit 301.

  Details of the receipt image extraction process (the process of step S2207) will be described with reference to FIG. FIG. 23 is a sequence diagram showing an example of a receipt image extraction process according to the present embodiment.

  First, when receiving a processing flow execution request from the repetitive component 430, the flow execution unit 301 transmits a processing flow information acquisition request to the application management unit 111 (step S2301). The processing flow information acquisition request includes the flow ID “flow102” acquired from the processing flow execution request.

  Upon receiving the processing flow information acquisition request, the application management unit 111 acquires the processing flow information 1100 of the flow ID “flow102” included in the acquisition request from the application information 1000 stored in the application information storage unit 130. (Step S2302). That is, the application management unit 111 acquires the processing flow information 1100 illustrated in FIG. 17 from the application information storage unit 130.

  Then, the application management unit 111 returns the processing flow information 1100 acquired from the application information storage unit 130 to the logic processing unit 112.

  Here, when the region extraction component 410 has not been generated, the flow execution unit 301 performs the process of step S2303. That is, the flow execution unit 301 sends a component acquisition request for the component with the component name “extract” defined in ““ component ”” included in the process definition 1411 of the process flow information 1100 illustrated in FIG. (Step S2303).

  On the other hand, when the region extraction component 410 is generated, the flow execution unit 301 does not perform the process of step S2303.

  Upon receiving the component acquisition request, the component management unit 302 generates a component having the component name “extract” (that is, the region extraction component 410) (step S2304). Note that. The region extraction component 410 can be generated using an API for generating a component defined in the component common I / F 400.

  Then, the component management unit 302 returns the generated region extraction component 410 to the flow execution unit 301. That is, the component management unit 302 returns, for example, an address on a memory (for example, the RAM 14) in which the area extraction component 410 is expanded to the flow execution unit 301.

  Next, the flow execution unit 301 transmits a component execution request to the region extraction component 410 (step S2305).

  The component execution request includes data indicating the captured image file. Further, the component request includes each parameter information defined in ““ parameters ”” included in the process definition 1411 of the process flow information 1100 illustrated in FIG. 17.

  Upon receiving the component execution request, the region extraction component 410 executes processing on the data included in the execution request using the parameter information (step S2306). In other words, the area extraction component 410 uses the area extraction unit 121 of the document service unit 120 to extract a receipt area included in the photographed image file, thereby creating a receipt image file. When a plurality of receipt areas are included in the photographed image file, the area extraction component 410 extracts the plurality of receipt areas, and creates a plurality of receipt image files.

  In addition, for example, when a scan image file includes a region indicating a receipt, the region extraction component 410 may extract a region indicating the receipt and create a receipt image file. In this case, the receipt image file is registered in the expense settlement service by the receipt registration service.

  Further, for example, when the area of the receipt included in the photographed image file is inclined, the area is rotated and extracted, and a receipt image file is created.

  Then, the region extraction component 410 returns data indicating the created receipt image file to the flow execution unit 301.

  Returning to FIG. When the flow execution unit 301 receives the data indicating the processing result (processing result obtained by repeatedly executing the receipt image extraction process) by the repetitive component 430, the flow execution unit 301 issues a component acquisition request based on the processing flow information 1100 illustrated in FIG. The data is transmitted to the management unit 302 (step S2208). That is, the flow execution unit 301 sends a component acquisition request for the component with the component name “expense” defined in ““ component ”” included in the process definition 1312 of the process flow information 1100 illustrated in FIG. Send to.

  When the component management unit 302 receives the component acquisition request, the component management unit 302 generates a component having the component name “expense” (that is, the expense adjustment component 420) (step S2209). The expense settlement component 420 can be generated using an API for generating a component defined in the component common I / F 400.

  Then, the component management unit 302 returns the generated expense settlement component 420 to the flow execution unit 301. That is, for example, the component management unit 302 returns the address on the memory (for example, the RAM 14) in which the expense adjustment component 420 is expanded to the flow execution unit 301.

  Next, the flow execution unit 301 transmits a component execution request to the expense adjustment component 420 (step S2210).

  The component execution request includes each parameter information defined in "" parameters "" included in the process definition 1312 of the process flow information 1100 illustrated in FIG.

  That is, the component execution request includes parameter information in which authentication information is set for the parameter information ““ auth ”: null”. For example, when the user name “fugafuga@hoge.com” and the password “xxxxxxxx” are input to the user name input field G810 and the password input field G820 of the authentication information input screen G800, and the OK button G830 is pressed. To do. In this case, the parameter information is, for example, ““ auth ”:“ fugafuga @ hoge. com / xxxxxxxx "".

  In addition, the component execution request includes parameter information for requesting the expense settlement system 40 to create a ledger.

  Upon receiving the component execution request, the expense settlement component 420 executes processing using the parameter information (step S2211). That is, the expense settlement component 420 sends a ledger creation request to the expense settlement system 40. The expense settlement component 420 can make a ledger creation request using, for example, a Web API published by the expense settlement system 40. The ledger creation request includes authentication information.

  Then, the expense settlement system 40 creates a ledger for registering the receipt image file, and returns a ledger ID for identifying the created ledger to the expense settlement component 420 as a processing result. Then, the expense settlement component 420 returns data indicating the ledger ID to the flow execution unit 301.

  Next, the flow execution unit 301 transmits a component execution request to the repetitive component 430 (step S2212).

  The component execution request includes data indicating the receipt image file created by the region extraction component 410. Therefore, when a plurality of receipt image files are created by the region extraction component 410, the component execution request includes a plurality of data indicating the plurality of receipt image files.

  Further, the component execution request includes each parameter information defined in “" parameters "" included in the process definition 1313 of the process flow information 1100 illustrated in FIG. That is, the component execution request includes parameter information ““ flowid ”:“ flow101 ”” and parameter information indicating the ledger ID returned in step S2211.

  Upon receiving the component execution request, the repetitive component 430 transmits a processing flow execution request to the flow execution unit 301 for each data (that is, a receipt image file) included in the execution request (step S2213). That is, the repetitive component 430 repeatedly executes the receipt registration process in step S2214 for the number of times of the number of receipt image files. The process flow execution process includes data (that is, a receipt image file), a flow ID “flow101”, and a ledger ID.

  Upon receiving the processing flow execution request, the flow execution unit 301 performs a process (receipt registration process) for registering a receipt image file in the ledger indicated by the ledger ID in the expense settlement service (step S2214). . Then, the flow execution unit 301 returns the processing result of the receipt registration process to the repetition component 430.

  After that, the repetitive component 430 returns data indicating the processing result obtained by repeatedly executing the receipt registration processing in step S2214 to the flow execution unit 301. The receipt registration process in step S2214 is the same as the receipt registration process in step S1115 in FIG.

[Third embodiment]
Next, a third embodiment will be described. In the third embodiment, a case where the service providing system 10 performs authentication cooperation using, for example, OAuth or the like with the expense settlement system 40 will be described. When the service providing system 10 performs authentication cooperation with the expense settlement system 40, each time the user of the device 20 uses the receipt registration service, authentication information (such as a user name and password for using the expense settlement service) is provided. No need to enter.

  In the description of the third embodiment, differences from the first embodiment will be mainly described. Locations having substantially the same functional configuration as those of the first embodiment and processes that are substantially the same. The description of the place where the process is executed will be omitted as appropriate.

<Functional configuration>
First, the functional configuration of the information processing system 1 according to the present embodiment will be described with reference to FIG. FIG. 24 is a diagram illustrating a functional configuration of an example of the information processing system 1 according to the present embodiment.

  The device 20 illustrated in FIG. 24 includes a browser 220 that is executed by, for example, the CPU 31 or the like. The user of the device 20 can use the receipt registration service provided by the service providing system 10 via the browser 220.

  The service providing system 10 illustrated in FIG. 24 further includes a web service processing unit 140 and an authentication service processing unit 150. Each of these functional units is realized by a process that the CPU 16 causes one or more programs installed in the service providing system 10 to execute.

  Further, the service providing system 10 illustrated in FIG. 24 further includes a screen information storage unit 160 and a token information storage unit 170. Each of these storage units can be realized by the HDD 18. Note that at least one of these storage units may be realized by a storage device connected to the service providing system 10 via the network N1.

  The Web service processing unit 140 performs a process for the user of the device 20 to use a service (for example, a receipt registration service) provided by the service providing system 10 using the browser 220. That is, the Web service processing unit 140 functions as an application server that provides a Web application (that is, application information 1000) to the browser 220. Here, the Web service processing unit 140 includes a screen configuration unit 141 and an application execution unit 142.

  The screen configuration unit 141 returns screen information stored in the screen information storage unit 160 in response to a request from the browser 220 of the device 20. The screen information is information that defines a screen for using a service (for example, a receipt registration service) provided by the application information 1000. In the screen information, for example, a screen is defined in a format that can be interpreted by the browser 220, such as HTML, XHTML (Extensible HyperText Markup Language), CSS (Cascading Style Sheets), and JavaScript (registered trademark). As a result, various screens for using the service provided by the service providing system 10 are displayed on the operation panel 22 of the device 20 by the browser 220.

  In response to a request from the browser 220 of the device 20, the application execution unit 142 transmits a processing flow execution request to the logic processing unit 112 of the input / output service processing unit 110.

  The authentication service processing unit 150 performs a process for performing authentication cooperation with the expense settlement system 40. In other words, when the authentication in the expense settlement system 40 is successful, the authentication service processing unit 150 acquires an access token from the expense settlement system 40 using a temporary token returned in response to the success of the authentication. Then, the authentication service processing unit 150 stores token information in which the access token is associated with the user ID in the token information storage unit 170.

  The screen information storage unit 160 stores screen information of various screens for using the service provided by the service providing system 10.

  The token information storage unit 170 stores token information in which a user ID for using the service providing system 10 is associated with an access token for using the expense settlement service. Here, the token information stored in the token information storage unit 170 will be described with reference to FIG. FIG. 25 is a diagram illustrating an example of token information.

  As illustrated in FIG. 25, the token information stored in the token information storage unit 170 is associated with a user ID and an access token. Thereby, the user of the service providing system 10 (that is, the user who uses the service providing system 10 via the browser 220) uses the receipt registration service by using the access token associated with the user ID of the user. can do.

<Details of processing>
Next, details of processing of the information processing system 1 according to the present embodiment will be described. In the following, a process for performing settings for authentication cooperation with the expense settlement system 40 before the user of the device 20 uses the receipt registration service will be described with reference to FIG. FIG. 26 is a sequence diagram illustrating an example of authentication cooperation setting processing according to the present embodiment.

  First, the user uses the browser 220 of the device 20 to perform an operation for displaying an authentication cooperation setting screen (step S2601). For example, the user can perform a display operation of the authentication cooperation setting screen by pressing a link to the authentication cooperation setting screen on a predetermined screen displayed by the browser 220. Note that the user may perform the display operation of the authentication cooperation setting screen by, for example, inputting the URL of the authentication cooperation setting screen into the address bar of the browser 220 or the like.

  When the browser 220 of the device 20 accepts the display operation of the authentication cooperation setting screen, the browser 220 of the apparatus 20 transmits an authentication cooperation setting screen acquisition request to the Web service processing unit 140 of the service providing system 10 (step S2602).

  Upon receiving an authentication cooperation setting screen acquisition request, the screen composition unit 141 of the Web service processing unit 140 acquires screen information for displaying the authentication cooperation setting screen from the screen information storage unit 160. Then, the screen configuration unit 141 transmits a service list acquisition request to the authentication service processing unit 150 based on the screen information (step S2603). The service list acquisition request is a request for acquiring a list of external services that can be authenticated and linked with the service providing system 10 (for example, an expense settlement service provided by the expense settlement system 40).

  Upon receiving the service list acquisition request, the authentication service processing unit 150 returns a service list indicating a list of external services that can be authenticated and linked to the service providing system 10 to the Web service processing unit 140. Then, the screen configuration unit 141 returns the service list and screen information for displaying the setting screen for authentication cooperation to the browser 220.

  When the browser 220 receives the screen information for displaying the authentication cooperation setting screen and the service list, the browser 220 displays, for example, the authentication cooperation setting screen G1100 shown in FIG. 27 based on these information (step S2604). .

  Here, on the authentication cooperation setting screen G1100 shown in FIG. 27, for each service included in the service list, an “authentication cooperation” button for setting authentication cooperation and the setting of authentication cooperation are canceled (deleted). And a “cancel cooperation” button for doing this. The user can perform an operation for setting up authentication cooperation with the expense settlement service (expense cooperation service authentication cooperation setting operation) by pressing an “authentication cooperation button” G1101.

  Using the browser 220, the user performs an authentication cooperation setting operation for the expense settlement service (step S2605).

  Upon receiving the expense settlement service authentication cooperation setting operation, the browser 220 transmits an authentication collaboration screen acquisition request for inputting authentication information of the expense settlement service to the Web service processing unit 140 (step S2606).

  When the screen composition unit 141 of the Web service processing unit 140 receives the authentication cooperation screen acquisition request, the authentication service processing unit 150 sends a URL acquisition request (authentication cooperation screen URL acquisition request) indicating the expense cooperation service authentication cooperation screen. (Step S2607). Upon receiving the authentication cooperation screen URL acquisition request, the authentication service processing unit 150 returns the authentication cooperation screen URL to the Web service processing unit 140.

  The authentication cooperation screen URL is a URL indicating the authentication cooperation screen provided by the expense settlement system 40. However, the URL may be, for example, a URI (Uniform Resource Identifier) or a URN (Uniform Resource Name).

  When receiving the authentication collaboration screen URL, the screen composition unit 141 of the Web service processing unit 140 transmits an acquisition request for the authentication collaboration screen indicated by the URL to the expense settlement system 40 (step S2608). When the expense settlement system 40 receives the acquisition request for the authentication collaboration screen, it returns screen information for displaying the authentication collaboration screen to the Web service processing unit 140.

  When the screen composition unit 141 of the Web service processing unit 140 receives screen information for displaying the authentication cooperation screen from the expense settlement system 40, the screen composition unit 141 gives a redirect destination URL to the screen information and returns it to the browser 220. To do. Note that the redirect destination URL given here is, for example, a URL for transmitting a temporary code to the authentication service processing unit 150.

  When the browser 220 receives the screen information to which the redirect URL is assigned (screen information for displaying the authentication cooperation screen), the browser 220 displays, for example, the authentication cooperation screen G1200 shown in FIG. S2609).

  Here, in the authentication cooperation screen G1200 shown in FIG. 27, a user name input field G1201 for inputting a user name in the authentication information of the expense settlement service, and a password for inputting a password in the authentication information. And an input field G1202.

  The user performs the authentication cooperation permission operation by pressing the “permit authentication cooperation” button G1203 after inputting the user name and password of the expense settlement service in the user name input field G1201 and the password input field G1202, respectively. Can do. The authentication cooperation permission operation is an operation for permitting authentication cooperation with the expense settlement service.

  In the authentication collaboration screen G1200 illustrated in FIG. 27, for example, a scope used for authentication collaboration such as OAuth may be set.

  The user performs an authentication cooperation permission operation using the browser 220 (step S2610). Upon receiving the authentication cooperation permission operation, the browser 220 transmits an authentication cooperation permission request to the expense settlement system 40 (step S2611). Note that the authentication cooperation permission request includes the authentication information (that is, the user name and password of the expense settlement service) input on the authentication cooperation screen G1200 and the redirect destination URL.

  When the expense settlement system 40 receives an authentication cooperation permission request, it performs authentication based on the authentication information included in the permission request. Then, when the authentication is successful, the expense settlement system 40 issues a temporary code used for issuing an access token (step S2612), and transmits a redirect instruction including the issued temporary code to the browser 220.

  Note that, when the authentication fails, the expense settlement system 40 returns information indicating that the authentication has failed to the browser 220. Hereinafter, the description will be continued assuming that the expense settlement system 40 has been successfully authenticated.

  Upon receiving the redirect instruction from the expense settlement system 40, the browser 220 causes the authentication service processing unit 150 to redirect (step S2613). That is, the browser 220 transmits the temporary code received from the expense settlement system 40 to the redirect destination URL.

  Upon receiving the temporary code from the browser 220, the authentication service processing unit 150 transmits an access token acquisition request to the expense settlement system 40 (step S2614). The access token acquisition request includes a temporary code. An access token acquisition request can be made by sending a request to the Web API for acquiring an access token, which is disclosed by the expense settlement system 40.

  Upon receiving the access token acquisition request, the expense settlement system 40 verifies the validity of the temporary code included in the acquisition request, and if the validity is verified, issues an access token (step S2615). To the authentication service processing unit 150.

  Upon receiving the access code, the authentication service processing unit 150 receives the user ID of the user who uses the browser 220 (that is, the user who has logged in the service providing system 10 using the browser 220), and the access token. Token information that associates with is created. Then, the authentication service processing unit 150 stores the created token information in the token information storage unit 170 (step S2616).

  As described above, the service providing system 10 according to the present embodiment stores the access token for authentication cooperation with the expense settlement system 40 in association with the user ID of the user who has logged into the service providing system 10. As a result, the user can use the receipt registration service in cooperation with the expense settlement system 40 using the browser 220.

  Next, a process in which the user of the device 20 registers a receipt image file (receipt image file) in the expense settlement service using the receipt registration service will be described with reference to FIG. FIG. 28 is a sequence diagram showing an example of the entire process when using the receipt registration service according to the present embodiment.

  First, the user uses the browser 220 of the device 20 to display the receipt registration service usage screen (step S2801). For example, the user can perform a display operation of the use screen of the receipt registration service by pressing a link to the use screen of the receipt registration service on a predetermined screen displayed by the browser 220. The user may perform the display operation of the receipt registration service use screen by inputting the URL of the receipt registration service use screen into the address bar of the browser 220, for example.

  Upon receiving the receipt registration service usage screen display operation, the browser 220 of the device 20 transmits a receipt registration service usage screen acquisition request to the Web service processing unit 140 of the service providing system 10 (step S2802). .

  When the screen composition unit 141 of the Web service processing unit 140 receives an acquisition request for a receipt registration service screen, the screen configuration unit 141 acquires screen information for displaying the receipt registration service usage screen from the screen information storage unit 160. Then, the screen configuration unit 141 returns the screen information to the browser 220.

  Upon receiving the screen information for displaying the receipt registration service usage screen, the browser 220 displays the receipt registration service usage screen G1300 shown in FIG. 29, for example, based on the screen information (step S2803).

  Here, the receipt registration service use screen G1300 shown in FIG. 29 includes a scan execution button G1301 for creating a scan image file. The user can perform an operation (scan start operation) for starting scanning by setting one or more receipts in the scanner 26 of the device 20 and pressing the scan execution button G1301.

  The user performs a scan start operation using the browser 220 (step S2804). Upon receiving the scan start operation, the browser 220 reads each receipt by the scanner 26 and generates a scan image file including an area in which each receipt is displayed (step S2805). The browser 220 controls the execution of the scanner 26 by executing JavaScript included in the receipt registration service usage screen in response to, for example, a scan start operation.

  When the scan image file is generated, the browser 220 transmits an acquisition request for an access token used for authentication cooperation with the expense settlement service to the Web service processing unit 140 (step S2806).

  When receiving the access token acquisition request from the browser 220, the screen composition unit 141 of the Web service processing unit 140 transmits the access token acquisition request to the authentication service processing unit 150 (step S2807).

  Upon receiving the access token acquisition request, the authentication service processing unit 150 uses the browser 220 that has transmitted the acquisition request (that is, the browser 220 that has transmitted the access token acquisition request in step S2806). The user ID is acquired. Then, the authentication service processing unit 150 acquires an access token associated with the user ID from the token information storage unit 170, and returns the acquired access token to the Web service processing unit 140. Thereafter, the Web service processing unit 140 returns the access token returned from the authentication service processing unit 150 to the browser 220.

  The user ID of the user who uses the browser 220 may be included in the access token acquisition request, for example, or the user ID may be specified from the session ID or the like included in the acquisition request. .

  Upon receiving the access token, the browser 220 transmits a processing flow execution request to the Web service processing unit 140 (step S2808). The processing flow execution request includes the flow ID of the processing flow information 1100 for realizing the receipt registration service, the scanned image file, and the access token. The flow ID is associated with, for example, a scan execution button G1301 on the receipt registration service use screen G1300.

  Upon receiving the processing flow execution request, the application execution unit 142 of the Web service processing unit 140 transmits the processing flow execution request to the logic processing unit 112 (step S2809).

  The logic processing unit 112 receives a processing flow execution request and performs processing flow execution processing (step S2810). That is, the logic processing unit 112 executes a series of processing based on the processing flow information 1100 of the flow ID included in the execution request. At this time, the logic processing unit 112 requests various processes from the expense settlement system 40 using the access token included in the execution request.

  Specifically, for example, the expense settlement component 420 transmits a ledger creation request to the expense settlement system 40 using the access token. Further, for example, the expense settlement component 420 transmits a receipt registration request to the expense settlement system 40 using the access token.

  As described above, the user of the device 20 can use the receipt registration service using the access token stored in the service providing system 10 in advance. Therefore, the user of the device 20 can use the receipt registration service without inputting authentication information (such as the user name and password of the expense settlement system 40).

[Fourth embodiment]
Next, a fourth embodiment will be described. Some expense settlement services provide services such as receipt registration by agents. This is because, for example, there is a need for a general affairs person in the company to register receipts in a lump. Therefore, in the fourth embodiment, a case where the expense settlement system 40 provides services such as receipt registration by an agent will be described.

  In the description of the fourth embodiment, differences from the first embodiment will be mainly described. Locations having substantially the same functional configuration as those in the first embodiment and processes substantially similar to those in the first embodiment will be described. The description of the place where the process is executed will be omitted as appropriate.

<Functional configuration>
First, the functional configuration of the information processing system 1 according to the present embodiment will be described with reference to FIG. FIG. 30 is a diagram illustrating a functional configuration of an example of the information processing system 1 according to the present embodiment.

  The expense settlement system 40 illustrated in FIG. 30 includes, for example, a proxy processing unit 510 that performs processing related to receipt registration and the like by a proxy, and a proxy management DB 520 that manages the proxy and the agent. In the proxy management DB 520, for example, the user name of the agent (agent setting person) and the user name and authority of the agent are stored in association with each other. The authority is a range of functions that can be executed by the agent.

  For example, the proxy processing unit 510 performs processing for associating the user name of the agent (agent setting person) with the user name and authority of the agent and storing them in the proxy management DB 520. In addition, the proxy processing unit 510 performs, for example, an authority check process for the agent.

  Further, the logic processing unit 112 of the service providing system 10 according to the present embodiment acquires a list of other users who can be represented (list of agents) in response to a request from the client application 210.

<Details of processing>
Next, details of processing of the information processing system 1 according to the present embodiment will be described. Hereinafter, processing when the user of the PC terminal 30 sets a proxy (in other words, when the user sets a proxy to be a proxy) will be described with reference to FIG. FIG. 31 is a sequence diagram illustrating an example of a proxy setting process according to the present embodiment.

  First, the user performs a display operation of the agent setting screen using the browser 310 of the PC terminal 30 (step S3101). For example, the user can perform a display operation of the agent setting screen by pressing a link to the agent setting screen on a predetermined screen displayed by the browser 310. Note that the user may perform the display operation of the agent setting screen by, for example, inputting the URL of the agent setting screen into the address bar or the like of the browser 310.

  Upon receiving the agent setting screen display operation, the browser 310 of the PC terminal 30 transmits an agent setting screen acquisition request to the expense settlement system 40 (step S3102). When the expense settlement system 40 receives the acquisition request for the agent setting screen, it returns screen information for displaying the agent setting screen to the browser 310.

  Upon receiving the screen information for displaying the agent setting screen, the browser 310 displays, for example, the agent setting screen G1400 shown in FIG. 32 based on the screen information (step S3103).

  Here, the agent setting screen G1400 shown in FIG. 32 includes an agent setting field G1401. The user selects a desired agent from the agent setting column G1401, and sets authority to be set for the agent. Hereinafter, in the agent setting screen G1400, the user who sets the agent is also referred to as “recipient user”, and the user who is set as the agent is also referred to as “agent user”.

  The authority in the agent setting field G1401 of the agent setting screen G1400 shown in FIG. 32 includes “ledger creation / application”, “receipt registration”, and “approval”.

  The agent user can use these functions by setting these authorities (check boxes).

  For example, it is assumed that the agent user is “Seiya Suzuki”. At this time, if the agent user “Taro Tanaka” authority “ledger creation / application” and “receipt registration” are set by the agent user, the agent user “Taro Tanaka” As an agent of "Seiya", it will be possible to create / apply ledgers and register receipts.

  Similarly, for example, when the delegated user sets the authority “approval” of the proxy user “Yuta Sato”, the proxy user “Yuta Sato” acts as a proxy for the proxy user “Seiya Suzuki”. You will be able to approve receipt registration.

  The agent user can perform the setting operation of the agent by setting the agent and authority in the agent setting column G1401 and then pressing the “save setting” button G1402. The agent user can add the agent user to the agent setting column G1401 by pressing the add button G1403. On the other hand, the agent user can delete the selected agent user from the agent setting column G1404 by selecting a desired agent user from the check column G1404 and pressing the delete button G1405.

  The user (recipient user) uses the browser 310 to perform a proxy setting operation (step S3104).

  When accepting the proxy setting operation, the browser 310 transmits a proxy setting request to the expense settlement system 40 (step S3105). The proxy setting request includes, for example, the user name of the proxy user, the user name of the proxy user, and the authority set for the proxy user.

  Upon receiving the agent setting request, the agent processing unit 510 of the expense settlement system 40 performs agent setting processing (step S3106). That is, the proxy processing unit 5110 stores the user name of the proxy user included in the setting request, the user name of the proxy user, and the authority set for the proxy user in the proxy management DB 520 in association with each other. To do. Thereby, the agent user for the agent user and the authority set for the agent user are managed.

  Next, a process in which the user of the device 20 registers a receipt image file in the expense settlement service using the receipt registration service as an agent will be described with reference to FIG. FIG. 33 is a sequence diagram showing an example of overall processing when the receipt registration service according to the present embodiment is used as a proxy.

  First, using the device 20, the user performs a display operation of a registration method selection screen for selecting whether or not to register a receipt as an agent (step S3301). Then, the client application 210 of the device 20 receives a display method selection screen display operation. For example, the user can perform a display operation of the registration method selection screen by selecting a predetermined icon or the like on a predetermined screen displayed by the client application 210. Note that the display operation of the registration method selection screen may be a startup operation of the client application 210, for example.

  Upon receiving the display operation by the user, the client application 210 displays a registration method selection screen G1510 shown in FIG. 34, for example (step S3302).

  Here, the registration method selection screen G1510 shown in FIG. 34 includes a “register receipt as principal” button G1511 and a “register receipt as agent” button G1512.

  By selecting the “Register Receipt as Agent” button G1512, the user can register a receipt in the expense settlement service as an agent of another user. On the other hand, the user selects the “Receive Receipt as User” button G1511, so that, as in the first embodiment, the user receives the expense settlement service as the principal (that is, not as an agent of another user). Registration of the certificate. In the following description, it is assumed that the user selects the “Register receipt as agent” button G1512.

  Using the device 20, the user performs a selection operation of selecting the “Register Receipt as Agent” button G1512 (step S3303). Then, the client application 210 receives the selection operation.

  Upon receiving the selection operation, the client application 210 transmits an acquisition request for a list of other users that can be represented by the user (list of agents) to the logic processing unit 112 (step S3304). The acquisition request for the list of agents includes, for example, the user name of the user (that is, the user name of the expense settlement system 40). The client application 210 may transmit an acquisition request for the agent list to the logic processing unit 112 via the application management unit 111.

  When the logic processing unit 112 receives the acquisition request for the agent list, the logic processing unit 112 transmits the acquisition request to the expense settlement system 40 (step S3305).

  Upon receiving the agent list acquisition request, the proxy processing unit 510 of the expense settlement system 40 acquires, from the proxy management DB 520, the user name of the agent user whose user name included in the acquisition request is the agent user. (Step S3306). In other words, the proxy processing unit 510 acquires from the proxy management DB 520 the user names of other users that can be proxyed by the user with the user name included in the acquisition request.

  Then, the proxy processing unit 510 of the expense reimbursement system 40 returns a list (recipient list) of the acquired user names (user names of delegated users) to the logic processing unit 112. Thereafter, the logic processing unit 112 returns the received agent list to the client application 210.

  Upon receiving the agent list, for example, the client application 210 displays an agent selection screen G1520 shown in FIG. 34 (step S3307).

  Here, the agent selection screen G1520 shown in FIG. 34 includes an agent selection column G1521. In the agent selection field G1521, the user names of other users included in the agent list returned from the logic processing unit 112 (that is, the user names of other users to whom the user can act) can be selected. Is displayed. The user (agent user) selects another user that he / she is proxying from the agent selection field G1521, and then performs a proxy registration start operation by pressing the “start proxy registration” button G1522. Can do.

  The user (agent user) uses the device 20 to perform a proxy registration start operation (step S3308). Then, the client application 210 receives the start operation.

  Upon receiving the proxy registration start operation, the client application 210 displays a receipt registration service use start screen G200 shown in FIG. 10, for example, as in the first embodiment (step S3309). Subsequent steps S3310 to S3311 are the same as steps S903 to S904 in FIG.

  When the scan image file is generated in step S3311, the client application 210 transmits a processing flow execution request to the logic processing unit 112 (step S3312). The processing flow execution request includes the flow ID of the processing flow information 1100 for realizing the receipt registration service, the scanned image file, the authentication information, and the user name of the agent user. The user name of the agent user is the user name of another user selected from the agent selection column G1521 of the agent selection screen G1520.

  Here, the execution request for the above processing flow includes the authentication information (that is, the user name and password of the expense settlement system 40). However, the present invention is not limited to this, for example, as in the third embodiment. May include an access token. Note that the authentication information and the access token of the proxy user are used as the authentication information and the access token.

  Next, when receiving the processing flow execution request, the logic processing unit 112 performs the processing flow execution process (step S3313). That is, the logic processing unit 112 executes a series of processing based on the processing flow information 1100 of the flow ID included in the execution request. At this time, the logic processing unit 112 creates a ledger and registers a receipt using the user name of the agent user.

  Specifically, for example, the expense reimbursement component 420 transmits to the expense reimbursement system 40 a request to create a ledger including the user name of the agent user. In addition, for example, the expense settlement component 420 transmits a receipt registration request including the user name of the agent user to the expense settlement system 40. Accordingly, in the expense settlement system 40, a ledger is created with the user name of the agent user, and a receipt is registered in the ledger with the user name of the agent user.

  The expense settlement system 40 checks the authority of the proxy user by the proxy processing unit 510 when, for example, creating a ledger or registering a receipt. That is, the proxy processing unit 510 checks whether the authority of the requested function (such as ledger creation or receipt registration) is set for the proxy user. Then, the proxy processing unit 510 executes the corresponding function when the corresponding authority is set for the proxy user, and performs logic such as an error when the corresponding authority is not set for the proxy user. A reply is sent to the processing unit 112.

  As described above, the user of the device 20 can use the receipt registration service as an agent of another user. Therefore, for example, even when a general affairs officer of a company registers receipts in a lump, for example, the general affairs officer can be set as an agent in advance so that the affairs officer can receive the receipt of the agent. It becomes possible to act as a proxy for certificate registration.

  Here, although the case where the device 20 is an image forming apparatus has been described with reference to FIG. 33, the device 20 may be, for example, a smartphone, a tablet terminal, or a digital camera, as in the second embodiment.

  In this case, in step S3302 of FIG. 33, for example, a registration method selection screen G1610 shown in FIG. Similar to the registration method selection screen G1510 shown in FIG. 34, the registration method selection screen G1610 shown in FIG. 35 includes a “receipt registration as principal” button G1611 and a “receipt registration as agent” button G1612. .

  Also, in step S3307 in FIG. 33, for example, the agent selection screen G1620 shown in FIG. 35. Similarly to the agent selection screen G1510 shown in FIG. 34, the agent selection screen G1620 shown in FIG. 35 includes an agent selection column G1621 and a “start proxy registration” button G1622.

  As described above, this embodiment can be similarly applied even when the device 20 is a smartphone, a tablet terminal, a digital camera, or the like, as in the second embodiment.

[Fifth embodiment]
Next, a fifth embodiment will be described. Some expense settlement services can register information (meta information) such as the amount and date of the receipt in addition to the receipt image file. Therefore, in the fifth embodiment, a case where meta information is extracted from a receipt image file using a predetermined template and then the receipt image file and the extracted meta information are registered in the expense settlement system 40 will be described. To do.

  In the description of the fifth embodiment, differences from the first embodiment will be mainly described. Locations having substantially the same functional configuration as those in the first embodiment and processes substantially similar to those in the first embodiment will be described. The description of the place where the process is executed will be omitted as appropriate.

<Functional configuration>
First, the functional configuration of the logic processing unit 112 of the device 20 included in the information processing system 1 according to the present embodiment will be described with reference to FIG. FIG. 36 is a diagram illustrating a functional configuration of an example of the logic processing unit 112 according to the present embodiment.

  The logic processing unit 112 illustrated in FIG. 36 includes a template management unit 441. Also, a form processing component 440 is included in the component group 303 of the logic processing unit 112 shown in FIG.

  The template management unit 441 manages the templates stored in the template storage unit 180. Here, the template is information for extracting meta information (for example, the amount and date of the receipt) from the receipt image file. The template storage unit 180 is a storage unit included in the service providing system 10 and can be realized by the HDD 18.

  The form processing component 440 is a component for acquiring meta information from a receipt image file using a template. As described above, the meta information is information such as the amount and date included in the receipt image indicated by the receipt image file. The meta information is, for example, numeric information or character (including English and Chinese characters) information. However, the meta information may be information combining numbers and characters.

  Here, each template stored in the template storage unit 180 can be registered in the service providing system 10 using, for example, a template registration screen G1700 shown in FIG. A receipt image G1701 is displayed on the template registration screen G1700 shown in FIG. In addition, the receipt image G1701 designates an extraction position G1702 indicating a position from which meta information is extracted.

  For example, the user can create and register a template by displaying the template registration screen G1700 shown in FIG. 37 on the device 20 or the PC terminal 30 and specifying the extraction position G1702 in the receipt image G1701.

  Here, processing flow information 1100 in which a series of processing (processing flow) for realizing the receipt registration service according to the present embodiment is defined will be described with reference to FIG. FIG. 38 is a diagram showing an example of process flow information 1100 in which a series of processes for realizing the receipt registration service according to the present embodiment is defined.

  The process flow information 1100 illustrated in FIG. 38 includes a flow ID 1401 for identifying the process flow information 1100 and a flow detail 1402 in which process details of each process included in the process flow are defined.

  The flow details 1402 includes process definitions 1411 to 1414 that define the processing content of each process included in the processing flow. Of the process definitions 1411 to 1414, the process definition 1411, the process definition 1413, and the process definition 1414 are the same as the process definition 1111, the process definition 1112, and the process definition 1113 of the process flow information 1100 illustrated in FIG.

  A component name ““ template ”” of the form processing component 440 is defined in ““ component ”” of the process definition 1412. Further, parameter information for the form processing component 440 is defined in ““ parameters ”” of the process definition 1412.

  In the process definition 1412 “parameters”, parameter information “template_id”: null for setting identification information (template ID) for identifying a template used by the form processing component 440 is defined.

  As described above, the processing flow information 1100 defines a component that executes each process included in a series of processes and parameter information for the component.

  Thereby, the expense settlement component 420 can register the meta information extracted by the form processing component 440 and the receipt image file extracted by the area extraction component 410 on the created ledger.

<Details of processing>
Next, details of processing of the information processing system 1 according to the present embodiment will be described. Hereinafter, a process in which the user of the device 20 registers the receipt image file and the meta information extracted from the receipt image file in the expense settlement service using the receipt registration service with reference to FIG. explain. FIG. 39 is a sequence diagram showing an example of overall processing when using the receipt registration service according to the present embodiment.

  First, the user uses the device 20 to perform a display operation of a template selection screen for selecting a template (step S3901). Then, the client application 210 of the device 20 accepts a template selection screen display operation. For example, the user can perform a display operation of the template selection screen by selecting a predetermined icon or the like on a predetermined screen displayed by the client application 210. The display operation of the template selection screen may be, for example, a startup operation of the client application 210.

  Upon receiving the display operation by the user, the client application 210 displays a template selection screen G1800 shown in FIG. 40, for example (step S3902).

  Here, the template selection screen G1800 shown in FIG. 40 includes a template selection field G1801. The user can perform a template selection operation by selecting a desired template from the template selection field G1801.

  Note that the user can use the receipt registration service without using a template by pressing a “Do not use template” button G1802. In the following description, it is assumed that the user performs a template selection operation.

  The user performs a template selection operation using the device 20 (step S3903). Then, the client application 210 receives the selection operation. The subsequent steps S3904 to S3906 are the same as steps S902 to S904 in FIG.

  When the scan application file is generated in step S3904, the client application 210 transmits a processing flow execution request to the logic processing unit 112 (step S3907). The processing flow execution request includes the flow ID “flow003” of the processing flow information 1100 shown in FIG. 38, the scanned image file, and the authentication information. The processing flow execution request includes the template ID of the template selected from the template selection field G1801 of the template selection screen G1800 shown in FIG.

  Here, the execution request for the above processing flow includes the authentication information (that is, the user name and password of the expense settlement system 40). However, the present invention is not limited to this, for example, as in the third embodiment. May include an access token.

  Next, when receiving the processing flow execution request, the logic processing unit 112 performs processing flow execution processing (step S3908). That is, the logic processing unit 112 executes a series of processing based on the processing flow information 1100 of the flow ID included in the execution request.

  Then, the logic processing unit 112 returns the processing result of the processing flow execution process to the client application 210. Thereby, the service providing system 10 according to the present embodiment can provide the device 20 with a receipt registration service realized by a series of processing based on the processing flow information 1100 shown in FIG.

  Details of the process flow execution process (the process of step S3908) shown in FIG. 39 will be described with reference to FIGS. 41 and 42. FIG. 41 and 42 are sequence diagrams illustrating an example of processing flow execution processing for realizing the receipt registration service according to the present embodiment.

  First, when receiving a processing flow execution request from the client application 210, the flow execution unit 301 transmits a processing flow information acquisition request to the application management unit 111 (step S4101). The processing flow information acquisition request includes the flow ID “flow003” acquired from the processing flow execution request.

  Upon receiving the processing flow information acquisition request, the application management unit 111 acquires the processing flow information 1100 of the flow ID “flow003” included in the acquisition request from the application information 1000 stored in the application information storage unit 130. (Step S4102). That is, the application management unit 111 acquires the processing flow information 1100 illustrated in FIG. 38 from the application information storage unit 130.

  Then, the application management unit 111 returns the processing flow information 1100 acquired from the application information storage unit 130 to the logic processing unit 112.

  The flow execution unit 301 transmits a component acquisition request based on the processing flow information 1100 illustrated in FIG. 38 to the component management unit 302 (step S4103). That is, the flow execution unit 301 sends a component acquisition request for the component with the component name “etract” defined in ““ component ”” included in the process definition 1411 of the process flow information 1100 illustrated in FIG. 38. Send to.

  Subsequent steps S4104 to S4106 are the same as steps S1104 to S1106 in FIG.

  Subsequent to step S4106, the flow execution unit 301 transmits a component acquisition request based on the processing flow information 1100 illustrated in FIG. 38 to the component management unit 302 (step S4107). That is, the flow execution unit 301 sends a component acquisition request for the component name “template” defined in ““ component ”” included in the process definition 1412 of the process flow information 1100 illustrated in FIG. Send.

  When the component management unit 302 receives the component acquisition request, the component management unit 302 generates a component with the component name “(template”) (that is, the form processing component 440) (step S4108). The form processing component 440 can be generated using an API for generating a component defined in the component common I / F 400.

  Then, the component management unit 302 returns the generated form processing component 440 to the flow execution unit 301. That is, for example, the component management unit 302 returns the address on the memory (for example, the RAM 14) in which the form processing component 440 is expanded to the flow execution unit 301.

  Next, the flow execution unit 301 transmits a component execution request to the form processing component 440 (step S4109).

  The component execution request includes data indicating the receipt image file created by the region extraction component 410. Therefore, when a plurality of receipt image files are created by the region extraction component 410, the component execution request includes a plurality of data indicating the plurality of receipt image files.

  Further, the component execution request includes each parameter information defined in ““ parameters ”” included in the process definition 1412 of the process flow information 1100 illustrated in FIG. 38. That is, the component execution request includes parameter information in which the template ID of the template selected on the template selection screen G1800 shown in FIG. 40 is set for the parameter information ““ template_id ”: null”. For example, when “Receipt 1 template” of parameter ID “temp1” is selected on the template selection screen G1800, the parameter information is ““ template_id ”:“ temp1 ””.

  Upon receiving the component execution request, the form processing component 440 transmits a template acquisition request for acquiring a template with the template ID included in the execution request to the template management unit 441 (step S4110). When receiving the template acquisition request, the template management unit 441 acquires the template with the template ID included in the acquisition request from the template storage unit 180 and sends it back to the form processing component 440.

  Upon receiving the template from the template management unit 441, the form processing component 440 extracts meta information from the receipt image file indicated by the data based on the template (step S4111). In other words, the form processing component 440 extracts meta information (for example, amount and date) from the image area at the extraction position specified in the template in the image area indicated by the receipt image file.

  Then, the form processing component 440 returns data indicating the extracted meta information to the flow execution unit 301.

  Next, the flow execution unit 301 transmits a component acquisition request based on the processing flow information 1100 illustrated in FIG. 38 to the component management unit 302 (step S4112). In other words, the flow execution unit 301 sends a component acquisition request for the component with the component name “expense” defined in ““ component ”” included in the process definition 1413 of the process flow information 1100 shown in FIG. Send to.

  When the component management unit 302 receives the component acquisition request, the component management unit 302 generates a component with the component name “expense” (that is, the expense adjustment component 420) (step S4113). The expense settlement component 420 can be generated using an API for generating a component defined in the component common I / F 400.

  Then, the component management unit 302 returns the generated expense settlement component 420 to the flow execution unit 301. That is, for example, the component management unit 302 returns the address on the memory (for example, the RAM 14) in which the expense adjustment component 420 is expanded to the flow execution unit 301.

  Subsequent steps S4114 to S4115 are the same as steps S1109 to S1110 in FIG.

  Subsequent to step S1110, the flow execution unit 301 transmits a component acquisition request based on the processing flow information 1100 illustrated in FIG. 38 to the component management unit 302 (step S4116). That is, the flow execution unit 301 sends a component acquisition request for the component having the component name ““ iterate ”” defined in ““ component ”” included in the process definition 1414 of the process flow information 1100 illustrated in FIG. Send to.

  When the component management unit 302 receives the component acquisition request, the component management unit 302 generates a component having the component name “iterate” (that is, the repetitive component 430) (step S4117). The iterative component 430 can be generated using an API for generating a component defined in the component common I / F 400.

  Then, the component management unit 302 returns the generated repetitive component 430 to the flow execution unit 301. That is, for example, the component management unit 302 returns the address on the memory (for example, the RAM 14) in which the repetitive component 430 is expanded to the flow execution unit 301.

  Next, the flow execution unit 301 transmits a component execution request to the repetitive component 430 (step S4118).

  The component execution request includes data indicating the receipt image file created by the area extraction component 410 and the meta information extracted from the receipt file by the form processing component 440. Therefore, when a plurality of receipt image files are created by the region extraction component 410, the component execution request includes a plurality of pieces of data indicating the plurality of receipt image files and a plurality of meta information.

  Further, the component execution request includes each parameter information defined in ““ parameters ”” included in the process definition 1113 of the process flow information 1100 illustrated in FIG. 38. That is, the component execution request includes parameter information ““ flowid ”:“ flow101 ”” and parameter information indicating the ledger ID returned in step S4115.

  When the repetitive component 430 receives the execution request of the component, the repetitive component 430 flows the execution request of the processing flow for each data (that is, the receipt image file and the meta information extracted from the receipt image file) included in the execution request. It transmits to the execution part 301 (step S4119). That is, the repetitive component 430 repeatedly executes the receipt registration process in step S4120 for the number of receipt image files. The processing flow execution request includes data (that is, a receipt image file and meta information), a flow ID “flow101”, and a ledger ID.

  Upon receiving the processing flow execution request, the flow execution unit 301 performs a process (receipt registration process) for registering the receipt image file and meta information in the ledger indicated by the ledger ID in the expense settlement service ( Step S4120). Then, the flow execution unit 301 returns the processing result of the receipt registration process to the repetition component 430.

  After that, the repetitive component 430 returns data indicating the processing result obtained by repeatedly executing the receipt registration process in step S4120 to the flow execution unit 301.

  Details of the receipt registration process (the process of step S4120) will be described with reference to FIG. FIG. 43 is a sequence diagram illustrating an example of a receipt registration process according to the present embodiment. Steps S4301 to S4302 in FIG. 43 are the same as steps S1201 to S1202 in FIG.

  Subsequent to step S4302, the flow execution unit 301 executes the component on the component having the component name “expense” defined in ““ component ”” included in the process definition 1211 of the process flow information 1100 illustrated in FIG. A request is transmitted (step S4303). That is, the flow execution unit 301 transmits a component execution request to the expense adjustment component 420.

  The component execution request includes data (that is, a receipt image file and meta information). In addition, for parameter information ““ auth ”: null”, parameter information in which authentication information is set, parameter information for making a receipt registration request to the expense settlement system 40, and a parameter indicating a ledger ID Information.

  Upon receiving the component execution request, the expense settlement component 420 executes processing using the data and parameter information (step S4304). That is, the expense settlement component 420 sends a receipt registration request to the expense settlement system 40. The expense settlement component 420 can make a receipt registration request using, for example, a Web API published by the expense settlement system 40. The receipt registration request includes a receipt image file, meta information, ledger ID, and authentication information.

  Then, the expense settlement system 40 registers the receipt image file and the meta information in the ledger indicated by the ledger ID, and returns the registration result to the expense settlement component 420. Then, the expense settlement component 420 returns data indicating the registration result to the flow execution unit 301.

  As described above, the expense settlement component 420 can register the receipt image file and the meta information in the ledger on the expense settlement service by requesting the expense settlement system 40 to register the receipt.

  In addition, although the service providing system 10 according to the present embodiment has been described with respect to the case where the template is selected by the user on the template selection screen G1800 illustrated in FIG. 40, for example, the present invention is not limited thereto. For example, the form processing component 440 may specify the template used in step S <b> 4111, and then transmit the specified template acquisition request to the template management unit 411 in step S <b> 4110. Here, the template is identified by, for example, calculating the similarity between the receipt image file and each template stored in the template storage unit 180 and then determining the template having the highest similarity (or the similarity is a predetermined value). It is only necessary to specify a template that is greater than or equal to the value.

<Summary>
As described above, the service providing system 10 according to the first embodiment can provide the device 20 with the receipt registration service in cooperation with the expense settlement system 40. Therefore, the user of the device 20 can register the image file indicating the certificate in the expense settlement system 40 by scanning the certificate that proves the expense such as a receipt or a receipt.

  In addition, the service providing system 10 according to the second embodiment captures an image file indicating these certificates in the expense reimbursement system 40 by photographing a certificate certifying expenses such as a receipt or a receipt with the device 20. You can register.

  As a result, when the user uses the expense settlement service provided by the expense settlement system 40 to perform expense settlement, the user can easily provide the expense settlement system 40 with an image file indicating a certificate certifying expenses such as a receipt or a receipt. Will be able to register.

  In addition, the service providing system 10 according to the third embodiment performs authentication cooperation using, for example, OAuth with the expense settlement system 40. Thereby, in the service providing system 10 according to the third embodiment, each time the user of the device 20 uses the receipt registration service, he / she enters authentication information (such as a user name and password for using the expense settlement service). There is no need to do it.

  In the service providing system 10 according to the fourth embodiment, the user of the device 20 can use the receipt registration service on behalf of other users. Therefore, according to the service providing system 10 according to the fourth embodiment, for example, the general affairs person in charge of the company can meet the needs for registering receipts in a lump.

  Furthermore, the service providing system 10 according to the fifth embodiment extracts meta information (for example, amount and date) from the receipt image file using the template, and the extracted meta information is also used as the expense settlement system 40. Can be registered.

  The present invention is not limited to the specifically disclosed embodiments, and various modifications and changes can be made without departing from the scope of the claims.

DESCRIPTION OF SYMBOLS 1 Information processing system 10 Service provision system 20 Apparatus 30 PC terminal 40 Expense settlement system 110 Input / output service processing part 111 Application management part 112 Logic processing part 120 Document service part 121 Area extraction part 130 Application information storage part 210 Client application 301 Flow execution Section 302 Component management section 303 Component group 310 Browser 410 Area extraction component 420 Expense settlement component 430 Iteration component

Japanese Patent No. 4039191

Claims (12)

An information processing system connected to an expense settlement system,
Receiving means for receiving first image data including one or more certificate images for expense adjustment from a device connected to the information processing system;
Each of the one or more certificate images included in the first image data received by the receiving unit is extracted to generate one or more second image data corresponding to each of the one or more certificate images. Extraction means to
Registration means for registering each of the one or more second image data created by the extraction means in the expense settlement system;
An information processing system. Creating means for creating a ledger in which the one or more second image data is registered on the expense settlement system;
The registration means includes
The information processing system according to claim 1, wherein each of the one or more second image data is registered on the ledger created by the creation unit. The registration means includes
The information processing system according to claim 1, wherein each of the one or more second image data is registered in the expense settlement system using a Web API provided by the expense settlement system.   The first image data is created by scanning one or more certificates with the device, or when the device images one or more certificates. Information processing system according to item.   The information processing system according to claim 4, wherein the certificate is a receipt or a receipt. The receiving means includes
Receiving, from the device, the first image data and authentication information used for authentication of the expense settlement system;
The registration means includes
The information processing system according to any one of claims 1 to 5, wherein each of the one or more second image data is registered in the expense settlement system using the authentication information. First storage means for storing a token issued in response to a successful authentication in the expense settlement system;
The registration means includes
The information processing according to any one of claims 1 to 5, wherein each of the one or more second image data is registered in the expense settlement system using the token stored in the first storage unit. system. Second storage means for storing a template in which an extraction position for extracting predetermined information from the second image data is defined;
Information extraction means for extracting predetermined information from the extraction positions of the one or more second image data created by the extraction means using the template stored in the second storage means; And
The registration means includes
Each of the one or more second image data created by the extraction means and predetermined information extracted from the one or more second image data by the information extraction means are registered in the expense settlement system. The information processing system according to any one of claims 1 to 7. The information extraction means includes
The number information indicating the amount is extracted from the extraction position of the one or more second image data created by the extraction unit using the template stored in the second storage unit. Information processing system described in 1. An information processing apparatus connected to an expense settlement system,
Receiving means for receiving first image data including one or more certificate images for expense adjustment from a device connected to the information processing apparatus;
Each of the one or more certificate images included in the first image data received by the receiving unit is extracted to generate one or more second image data corresponding to each of the one or more certificate images. Extraction means to
Registration means for registering each of the one or more second image data created by the extraction means in the expense settlement system;
An information processing apparatus. An information processing system including an image forming apparatus and a server device connected to the image forming apparatus, wherein the information processing system is connected to an expense settlement system.
The image forming apparatus includes:
Having image creation means for creating first image data by scanning one or more certificates for expense settlement;
The server device
One or more second areas corresponding to each of the one or more certificates are extracted from the first image data created by the image creation means by extracting image areas where the one or more certificates are displayed. Extraction means for creating image data;
Registration means for registering each of the one or more second image data created by the extraction means in the expense settlement system;
An information processing system. An information processing method used in an information processing system connected to an expense settlement system,
A receiving procedure for receiving first image data including one or more certificate images for expense adjustment from a device connected to the information processing system;
Each of the one or more certificate images included in the first image data received by the reception procedure is extracted to generate one or more second image data corresponding to each of the one or more certificate images. Extraction procedure to
A registration procedure for registering each of the one or more second image data created by the extraction procedure in the expense settlement system;
An information processing method comprising:

Images