JP2023112939A - Information processing device control method, program, and information processing device - Google Patents

Abstract

To provide an information processing device control method, etc., excellent in usability which can efficiently perform invoice-related processing.SOLUTION: An information processing device control method comprises: displaying a first operator for uploading an invoice; displaying a second operator to enable selection from a plurality of upload methods according to an operation of the first operator; and performing invoice upload processing according to a selected upload method.SELECTED DRAWING: Figure 8

Description

The present invention relates to a control method, a program, and an information processing device for an information processing device that executes processing related to invoices.

For example, Patent Literature 1 discloses a payment support system that supports payment processing based on a bill by installing a camera function for reading bills on a user terminal and an OCR function for extracting and recognizing characters from images captured by the camera. disclosed.

Patent No. 6404979

According to the above payment support system, it is possible to extract characters related to payment from the captured image of the invoice and use them to input payment details. Until then, there was a problem that it was not possible to check the process at an appropriate time, such as what kind of processing was being done on the system side, and it was not possible to proceed with the processing related to invoices efficiently. there were.

The present invention has been made in view of the circumstances described above, and provides a control method, a program, and an information processing apparatus for an information processing apparatus that is excellent in usability and can efficiently proceed with processing related to invoices. One of the purposes is to

A control method for an information processing apparatus, which is one aspect of the present invention, comprises the steps of: displaying a first operator for uploading a bill; and a step of executing invoice upload processing based on the selected upload method.

According to the present invention, it is possible to efficiently proceed with processing related to invoices.

It is a figure showing a schematic structure of an information processing system concerning this embodiment. 3 is a block diagram showing a schematic configuration of a management server; FIG. It is a block diagram which shows schematic structure of a store terminal. It is the figure which illustrated the home screen. It is the figure which illustrated the billing list screen. It is the figure which illustrated the transfer history list screen. 4 is a flowchart showing main processing related to operation of the home screen; 4 is a flowchart showing bill upload processing; It is the figure which illustrated the selection screen. It is the figure which illustrated the imaging screen. It is the figure which illustrated the imaging screen. It is the figure which illustrated the imaging screen. It is the figure which illustrated the confirmation screen. It is the figure which illustrated the list screen during data conversion. It is a flowchart which shows a transfer reservation processing flow. It is a flowchart which shows a transfer reservation processing flow. It is the figure which illustrated the list screen. It is the figure which illustrated the billing details screen. It is the figure which illustrated the edit screen. It is the figure which illustrated the billing details screen. It is the figure which illustrated the setting screen. It is the figure which illustrated the selection screen. It is a flowchart which shows a payment waiting process flow. It is a flowchart which shows a payment waiting process flow. It is the figure which illustrated the transfer details screen. It is the figure which illustrated the list screen. It is the figure which illustrated the detailed screen. It is the figure which illustrated the confirmation screen. It is the figure which illustrated the detailed screen. It is the figure which illustrated the confirmation screen. It is a flow chart which shows accounting cooperation processing. It is the figure which illustrated the setting screen. It is the figure which illustrated the notification screen. It is the figure which illustrated the 1st shared screen. It is the figure which illustrated the 2nd shared screen.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. The same reference numerals are given to the same elements, and overlapping explanations are omitted.

(1) Configuration of Embodiment FIG. 1 is a diagram showing a schematic configuration of an information processing system 1 according to this embodiment.
The information processing system 1 is a system for processing various information related to invoices, such as creation of invoices, deposit, transfer, and cooperation with external accounting firms and tax accountant offices. As shown in FIG. 1, an information processing system 1 includes a management server 10 and information processing used by a person in charge of each store (for example, store manager; hereinafter collectively referred to as "user") using this system. and a store terminal 20, which is a device. The management server 10 and each store terminal 20 are connected via a communication network N. Note that the number of store terminals 20 can be arbitrarily set according to system design or the like.

The communication network N includes a communication network that allows mutual information transmission and reception between the management server 10 and the store terminal 20 . The communication network N is, for example, the Internet, LAN, leased line, telephone line, in-house network, mobile communication network, Bluetooth (registered trademark), WiFi (Wireless Fidelity), other communication lines, combinations thereof, or the like. It does not matter whether it is wired or wireless.

FIG. 2 is a block diagram showing a schematic configuration of the management server 10. As shown in FIG.
The management server 10 is configured by, for example, a computer with high processing power, and by executing an information processing program 121, transmits and receives information to and from the store terminal 20, and executes various processes related to invoices. , the function of centrally managing each store terminal 20 is realized. As shown in FIG. 2, the management server 10 includes a communication interface 11, a storage unit 12, and a processor 13.

The communication interface 11 is a hardware module for connecting the management server 10 to the communication network N and communicating with other terminals on the communication network N. FIG. The communication interface 11 is configured using a modulator/demodulator such as an ISDN modem, ADSL modem, cable modem, optical modem, soft modem, or the like.

The storage unit 12 is, for example, a logical device provided by a storage area of a physical device made up of a computer-readable recording medium such as a disk drive or semiconductor memory (ROM, RAM, etc.). The storage unit 12 may be constructed by mapping multiple physical devices to one logical device, or may be constructed by mapping one physical device to multiple logical devices. The storage unit 12 stores various programs including an operating system program and a driver program, and various data used during execution of these programs. Specifically, the storage unit 12 stores an information processing program 121 to be executed by the processor 13, a user-related database (DB) 122, an invoice-related database (DB) 123, and the like.

Various information related to each user who uses the system 1 is registered in the user-related DB 122 . As an example, the user-related DB 122 stores authentication information (for example, user ID, password, etc.) for users to log in to the system 1, basic user information including contact information, address, etc., the system 1 Usage record information that indicates the usage status of , and a transfer password for making a transfer based on an invoice are registered.

Various information related to each user's bill is registered in the bill-related DB 123 . To give an example, the invoice-related DB 123 stores images of invoices uploaded from each store terminal 20, invoice information converted into data by performing OCR processing on the invoice images, and details of transfer details. Transfer data (details will be described later) representing is registered in association with each user.

The processor 13 includes an arithmetic logic operation unit (such as a CPU) that processes arithmetic operations, logical operations, bit operations, etc., and various registers. Realize the function. By executing the information processing program 121, the control unit 131 also cooperates with each store terminal 20 to perform various processes related to invoices, such as invoice registration, transfer reservation based on the invoice, and transfer execution. do.

Here, the computer that constitutes the management server 10 does not necessarily have to be one, and may be composed of a plurality of computers distributed over the communication network N. FIG.

FIG. 3 is a block diagram showing a schematic configuration of the store terminal 20. As shown in FIG.
A store terminal (information processing device) 20 is a terminal used by a user of each store, and is configured by, for example, a personal computer (PC), a notebook PC, a tablet terminal, a handheld computer device, a wearable terminal, a mobile phone, a smartphone, or the like. there is The store terminal 20 stores software (hereinafter referred to as “main application”) 241 necessary for using the system 1 . The user enjoys various services provided by the system 1 by operating the main application 241 installed in the store terminal 20, an Internet browser, and the like. Here, the main application 241 may be configured to be installed in the store terminal 20, or may be configured to provide some or all of the functions of the main application 241 from the management server 10 via the network N. good.

The camera 21 includes an imaging device that captures still images and moving images (hereinafter referred to as “images”). When the user takes an image of the invoice using the camera 21 , the captured image of the invoice is transmitted from the camera 21 to the display unit 22 and the management server 10 .

The display unit 22 is configured using, for example, a liquid crystal display or an organic EL display.
The operation input unit 23 is an input device such as a keyboard, various operation buttons, a touch panel provided on the display unit 22, and a pointing device such as a mouse.

The storage unit 24 is, for example, a logical device provided by a storage area of a physical device made up of a computer-readable recording medium such as a disk drive or semiconductor memory (ROM, RAM, etc.). The storage unit 24 stores various programs including an operating system program and a driver program, various data, and a main application 241 .

The processor 25 is composed of an arithmetic logic operation unit (such as a CPU) that processes arithmetic operations, logical operations, bit operations, etc., and various registers. Realize the function. By executing the main application 241, the control unit 251 not only centrally controls each unit of the store terminal 20, but also cooperates with the management server 10 to execute various processes related to invoices.

The communication interface 26 is a hardware module for connecting the information processing device to the communication network N and communicating with other terminals on the communication network N. For example, an ISDN modem, an ADSL modem, a cable modem, an optical modem. , a modulation/demodulation device such as a soft modem.

Note that the store terminal 20 is not limited to the devices exemplified above, and is capable of exchanging data with other communication devices via the communication network N, and capable of displaying a screen based on the received information. Any terminal device including a unit, an input unit such as a keyboard or touch panel, and a camera can be used.

<Home screen>
FIG. 4 is a diagram exemplifying a home screen P1 displayed on the store terminal 20. As shown in FIG. As a premise, it is assumed that settings necessary for using the system 1 (for example, user registration, etc.) have already been performed.

As shown in FIG. 4, a camera button B1, a home button B2, a billing list button B3, a transfer history button B4, and a setting button B5 are displayed below the home screen P1. The camera button B1 is an operation button for capturing an image of a bill, and the home button B2 is an operation button for returning to the home screen P1. The invoice list button B3 is an operation button for displaying a list of bills of the user, the transfer history button B4 is an operation button for displaying the transfer history (results) based on the bill, and the setting button B5 These are operation buttons for performing various settings related to invoice processing. Although the details will be described later, by tapping the setting button B5, the user can exchange information related to invoices with partner accounting firms, tax accountant offices, etc. (hereinafter collectively referred to as "accounting firms"). It is possible to share (cooperate).

At the center of the home screen P1, cards C11 to C14 representing each status of the bill are displayed. In this embodiment, as cards representing each status, a card being converted to data C11, a card being converted to data C12, a card waiting for payment C13, and a card waiting for transfer C14 are displayed.

The status of the data-progress card C11 is a status when the invoice is converted into data by performing OCR processing or the like on the image of the invoice after the upload of the invoice is completed. In the digitizing status, an image of the invoice that has been uploaded is displayed.

The status of the digitized card C12 is a status that is transferred when the digitization of the invoice is completed. It should be noted that when the conversion of the bill into data is completed, the bill information representing the content of the bill is registered in the management server 10 and the bill information of the converted bill is displayed on the store terminal 20 .

The status of the payment waiting card C13 is a status that is shifted when a payment instruction is received for an invoice that has been digitized. In the payment waiting status, the total amount of all invoice information waiting for payment, etc. is displayed.

The status of the card C14 waiting for transfer is a status that is shifted when payment is confirmed for bill information that has been digitized. Although not shown, if it is confirmed that the transfer has been made while waiting for the transfer, the transfer history status is changed to indicate that the transfer has been completed.

FIG. 5 is a diagram illustrating the billing list screen P2 when the billing list button B3 is tapped, and FIG. 6 is a diagram illustrating the transfer history list screen P3 when the transfer history button B4 is tapped.
In the upper part of the billing list screen P2, the number of bills N11 in the billing month, the total amount billed A11, etc. are displayed, and a plurality of bill confirmation cards C21 for confirming the contents of each bill are displayed below. . Each card C21 includes payment deadline, payment destination, payment amount, and the like.

Above the transfer history list screen P3, the number of transfers N21 in the transfer execution month, the total transfer amount A21, etc. are displayed, and a plurality of transfer confirmation cards C31 for confirming the details of each transfer are displayed below. Each card C31 includes the transfer execution date, transfer destination, transfer amount, and the like.

(2) Operation of Embodiment <<Main Processing Flow>>
FIG. 7 is a flowchart showing main processing related to the operation of the home screen P1. Each flow chart shown below is realized by cooperation of the store terminal 20 with the management server 10 and the like.

When the user taps the camera button B1 (step S1; YES), bill upload processing is started (described later).

When the user taps the data converted card C12 (step S2; YES), transfer reservation processing is started (described later).

When the user taps the payment waiting card C13 (step S3; YES), payment waiting processing is started (described later).

When the user taps the billing list button B3 (step S4), a billing list screen P2 showing the contents of each bill (specifically, the data of the billing information) is displayed (step S5).

When the user taps the transfer history button B4 (step S6), a transfer history list screen P3 showing details of each transfer (specifically, transfer data for which the transfer has been executed) is displayed (step S7).

After the user taps the setting button B5 (step S8; YES), when the user performs a predetermined operation, the accounting cooperation process for sharing the billing information with the affiliated accounting firm is started. (described later).

<<Upload processing flow>>
FIG. 8 is a flow chart showing bill upload processing.
The user taps the camera button (first operator) B1 and selects a bill upload method (step Sa1).

FIG. 9 is a diagram exemplifying a selection screen P4 for selecting an invoice upload method.
In the present embodiment, as a bill uploading method, a first uploading method UM1 of uploading an image of the bill photographed using the camera 21 and a second uploading method UM1 of uploading a file of the bill (for example, a PDF file) are performed. A method UM2 is provided. Furthermore, for the first upload method UM1, different upload methods are prepared according to the number of pages (sheets) of the invoice. Specifically, a method UM11 for capturing and uploading a single-page bill and a method UM12 for capturing and uploading a multi-page bill are provided.

FIG. 10 is a diagram exemplifying the imaged screen P5 when the first upload method UM1 is selected.
An imaging button B6 is displayed on the imaging screen P5. After placing the bill to be uploaded on a desk or the like, the user taps the image capturing button B6. When such an operation is performed, the camera 21 captures an image of the bill and uploads the captured image of the bill to the management server 10 .

FIG. 11 is a diagram illustrating an imaged screen P6 when a one-page bill is imaged, and FIG. 12 is a diagram illustrating an imaged screen P7 when a multiple-page bill is imaged.
An image BP1 of the invoice is displayed in the center of each screen. On the other hand, below the imaging screen P6 of the one-page invoice, a data conversion button B7 for proceeding with data conversion and an imaging button B8 for capturing an image of the next invoice are displayed. Below the image pickup screen P7 of the book, a data conversion button B7 for proceeding with data conversion and an image pickup button B9 for taking an image of the next page are displayed. In any upload method, it is possible to perform correction (for example, exposure correction, etc.) as well as imaging the invoice. The user proceeds with imaging and correction of the invoice by appropriately operating the respective buttons B7 to B9.

(When capturing and uploading a one-page invoice)
When the user selects the method (second operator) UM11 of capturing and uploading a one-page bill as a method of uploading the bill (step Sa2; YES), the bill is captured using the camera 21 and uploaded. Correction is started (step Sa5). If there is a next bill (step Sa8; YES), the user taps the imaging button B8 to perform imaging and correction (step Sa5). After that, when there are no bills to be uploaded (step Sa8; NO), the process proceeds to step Sa10.

(When capturing and uploading an invoice with multiple pages)
When the user selects the method (second operator) UM12 of photographing and uploading a multi-page bill (step Sa3; YES), the camera 21 starts photographing and correcting the bill. If there is a next page (step Sa9; YES), the user taps the image capturing button B9 to perform image capturing and correction. In addition, in the method UM12 of capturing and uploading an invoice having a plurality of pages, not only can each page of the invoice be captured and corrected, but also a page to be enlarged and displayed may be selected. After that, when the imaging and correction of the final page are completed (step Sa9; NO), the process proceeds to step Sa10.

(when uploading an invoice file)
When the user selects the method (second operator) UM2 for uploading the invoice file (step Sa4), the user selects the invoice file to be uploaded (step Sa7), and proceeds to step Sa10.

After proceeding to step Sa10, the user confirms a confirmation screen P8 of the invoice to be uploaded, as shown in FIG. 13, for example. In this embodiment, it is assumed that the confirmation screen P8 is a thumbnail image of the bill, but the present invention is not limited to this. Alternatively, a different confirmation screen P8 may be prepared for each invoice upload method, and different confirmation screens P8 may be displayed according to the upload method selected by the user.

When the user determines that there is no problem with the invoice displayed on the confirmation screen P8, the user presses the digitization execution button (third operator) B10 displayed at the bottom of the confirmation screen P8 to proceed with the digitization of the invoice. Tap (step Sa11). When such an operation is performed, the bill image is uploaded (transmitted) from the store terminal 20 to the management server 10 . The management server 10 registers the image of the uploaded invoice in the invoice-related DB 123 and starts converting the invoice into data (step Sa12). More specifically, the management server 10 performs processing (OCR processing, etc.) for recognizing characters from the uploaded bill image and converting it into data, thereby converting the bill into data.

When the user taps the data conversion card C11 after the bill data is started (step Sa13), a data conversion list screen P9 indicating that data conversion is being performed is displayed, as shown in FIG. 14, for example. (step Sa14). On the digitizing list screen P9, images of all invoices (one invoice in FIG. 14) whose upload has been completed are displayed together with upload date and time.

After that, when the conversion to data of the invoice is completed, the management server 10 registers this as invoice information in the invoice-related DB 123 (step Sa15), and sends a completion message to the effect that the conversion to data has been completed. (step Sa16).
After confirming the completion message sent to the shop terminal 20, the user taps the data-converted card C12 (step Sa17). As a result, the transfer reservation process is started.

<<Transfer reservation processing flow>>
15A and 15B are flowcharts showing the flow of transfer reservation processing.
The user confirms a list of invoice information (that is, invoices converted into data) (step Sb1). When the transfer reservation process is started, a list of invoice information is displayed on the user's store terminal 20 by the management server 10 (step Sb2).

FIG. 16 is a diagram exemplifying an invoice information list screen P10.
The invoice information list screen P10 displays the invoice information of all the invoices whose data conversion has been completed. In the example shown in FIG. 16, three confirmation waiting cards C15 and three transfer reservation waiting cards C16 are displayed on the invoice information list screen P10. The status of the confirmation waiting card C15 is a status of requesting the user to correct/confirm billing information, and the status of the transfer reservation waiting card C16 is a status of waiting for transfer reservation.

The user refers to the list screen P10 and taps either the confirmation waiting card C15 or the transfer reservation waiting card C16.

(If you tap the confirmation waiting card)
When the user taps the confirmation waiting card C15 (step Sb3; YES), the user checks whether the payment means is unknown (step Sb4) or whether the required items are missing (step Sb5). Confirm whether it could not be done (step Sb6).

If the payment method is unknown (step Sb4; YES), a detailed billing screen P11 prompting the user to set the payment method is displayed, as shown in FIG. 17, for example. The user refers to the detailed billing screen P11 and sets the means of payment (step Sb7). Examples of payment methods include specific application payment, bank transfer, account transfer, convenience store payment, post office payment, credit card payment, and smartphone payment, but other payment methods may be set. When the user sets the payment method, a bill information list screen P10 is displayed.

On the other hand, if the required items are insufficient (step Sb5; YES), the user edits the invoice (step Sb8). The management server 10, for example, as shown in FIG. 18, invoice information that prompts the input of essential items (for example, supplier name, billing amount, payment deadline date, billing store, transfer account, fee bearer, etc.) The editing screen P12 is displayed (step Sb9). The user refers to the edit screen P12, inputs the required items, and then saves the changes by tapping the save button B11 (step Sb10). As a result, the changed bill information is selected as a transfer reservation object (step Sb12). On the other hand, the management server 10 updates the user's invoice information registered in the invoice-related DB 123 in response to the user's tap operation on the save button B11 (step Sb11).

On the other hand, if the reading failed (step Sb6), a message prompting re-uploading of the invoice is displayed. The user follows the message and re-uploads the invoice.

(If you tap the transfer reservation waiting card)
When the user taps the transfer reservation waiting card C16 (step Sb13), the user determines whether or not the corresponding bill information has already been confirmed (that is, read) (step Sb14). If it has already been confirmed (step Sb14; YES), the invoice information is selected as a transfer reservation object (step Sb12). On the other hand, if unconfirmed (step Sb14; NO), the user confirms the details of the invoice information (step Sb15). The management server 10 displays a detailed billing screen P13 prompting confirmation of the billing information, as shown in FIG. 19, for example (step Sb9). The user refers to the billing details screen P13, confirms that there is no problem, and then taps the selection button B12 displayed at the bottom of the billing details screen P13. As a result, the confirmed bill information is selected as a transfer reservation target (step Sb12).

After that, the user taps a button for setting the designated transfer date (step Sb16). When such an operation is performed, the management server 10 displays, for example, a setting screen (first setting screen) P14 for the specified transfer date as shown in FIG. 20 (step Sb17). As shown in FIG. 20, the designated transfer date setting screen P14 displays a default value D11 for the designated transfer date as a candidate for the designated transfer date. As an example, the management server 10 determines the default value D11 of the designated transfer date by the following method, but the method is not limited to this and any method can be adopted.

(Method of Determining Default Value D11 for Designated Transfer Date)
・Payment due date ≤ current day → next day ・ current day < payment due date ≤ current day + 30 days → latest payment due date ・ current day + 30 days < payment due date → current day + 30 days

The user refers to the default value D11 of the designated transfer date presented on the setting screen P14, and selects the designated transfer date (step Sb18). Tap (step Sb19).

Here, if there are multiple invoices with the same payee among the multiple invoices for which transfer reservations have been received (step Sb20; YES), the management server 10 performs the following operations as shown in FIG. A selection screen (second setting screen) P15 prompting selection of a transfer method (unit) for each client is displayed. In the example shown in FIG. 21, an operation item (selection operator) Mh1 for selecting a collective transfer method for each of two business partners ("A Corporation" and "B Corporation") and a separate A selection item (selection operator) Mh2 for selecting a method of transferring money to is displayed.

When the user refers to the selection screen P15 and selects a transfer method for each business partner (step Sb21), the user taps a transfer reservation confirmation button B14 displayed at the bottom of the selection screen P15 (step Sb23). In response to this operation, a confirmation screen for confirming the contents of the transfer reservation is displayed. On the other hand, when the transfer method is selected by the user for each business partner, the management server 10 updates the registration in the invoice-related DB 123 and the like based on the selection of the transfer method (step Sb22).

The user refers to the transfer reservation confirmation screen, and when confirming that there is no problem with the transfer reservation (step Sb24), taps the transfer reservation execution button (step Sb25). In response to such an operation, an input screen prompting the input of the transfer passcode is displayed. The user refers to the input screen and inputs the transfer passcode (step Sb26). The input transfer passcode is transmitted to the management server 10 .

When the transfer passcode is received, the management server 10 refers to the user-related DB 122 and the like, and verifies (authenticates) the transfer passcode (step Sb27). If the transfer passcode authentication fails (step Sb28; NO), the user inputs the passcode again. On the other hand, if the transfer passcode is successfully authenticated (step Sb28; YES), the management server 10 creates transfer data representing the details of the transfer reservation (step Sb29), and executes the transfer reservation (step Sb30). Then, the management server 10 notifies the store terminal 20 of the user of a completion message indicating that the transfer reservation has been completed (step Sb31).

After confirming the completion message sent to the store terminal 20, the user taps the payment waiting card C13 (step Sb32). When the payment waiting card C13 is tapped, the payment waiting process is started.

<<Payment waiting process flow>>
22A and 22B are flowcharts showing a payment waiting process flow.
The user confirms a list of transfer data (that is, data representing details of transfer reservations) (step Sc1). When the payment waiting process is started, the transfer data list screen is displayed on the user's store terminal 20 by the management server 10 (step Sc2).

Here, the transfer data list screen is similar to the invoice information list screen P10 shown in FIG. 16, and is configured to include confirmation waiting cards and payment waiting cards.
The status of the card waiting for confirmation is a status requesting the user to correct and confirm the transfer data, and the status of the card waiting for payment is a status waiting for payment (instruction). In addition to the confirmation waiting cards and payment waiting cards, the total amount of all invoices waiting for payment (that is, the total transfer amount) is also displayed on the transfer data list screen.

The user refers to the transfer data list screen and taps either the confirmation waiting card or the payment waiting card.

(If you tap the confirmation waiting card)
When the user taps the confirmation waiting card (step Sc3; YES), the user checks whether the transfer amount (that is, the reserve) is insufficient (step Sc5) or whether the transfer destination account is incomplete (step Sc5). Check Sc6).

If the reserve is insufficient (step Sc5; YES), a transfer details screen P17 prompting confirmation of the insufficient amount is displayed, as shown in FIG. 23, for example. The user refers to the transfer details screen P17, confirms the amount of the shortfall (Step Sc7), and then confirms the reserve account information such as the account number for depositing the funds into the reserve account (Step Sc8). After that, the user uses an ATM (Automatic Teller Machine), an Internet bank, or the like to make a deposit into the reserve account to eliminate the shortfall (step Sc9).

Thereafter, the user returns to the home screen P1 and taps the transfer standby card C14 (step Sc10). As a result, a list screen P18 of transfer data waiting for transfer, as shown in FIG. 24, for example, is displayed. The user refers to the list screen P18 and confirms that the transfer data is in the transfer standby status (step Sc11). After that, the system waits until the specified transfer date set by the user.

On the other hand, if there is a problem with the transfer destination account (step Sc6), the user confirms the details of the transfer data (step Sc12). The management server 10 displays a detailed screen P19 showing the details of the transfer data together with a message prompting correction of the defect in the transfer destination account, as shown in FIG. 25, for example (step Sc14). The user refers to the detailed screen P19 and decides whether to correct the transfer destination account (step Sc15) or cancel the transfer reservation (step Sc16).

The user determines that the transfer account should be corrected (step Sc15; YES), and corrects the transfer account (step Sc19). The confirmation screen P20 is displayed, and the corrected transfer data is transmitted to the management server 10 . When the management server 10 receives the corrected transfer data, it updates the transfer data registered in the invoice-related DB 123 (step Sc20).

The user refers to the confirmation screen P20, confirms the execution of the transfer reservation (step Sc21), and then taps the button B15 for executing the transfer displayed at the bottom of the confirmation screen P20 (step Sc22). When such an operation is performed, an input screen prompting the input of the transfer passcode is displayed. The user refers to the input screen and inputs the transfer passcode (step Sc23). The input transfer passcode is transmitted to the management server 10 .

Upon receiving the transfer passcode, the management server 10 refers to the user-related DB 122 or the like, and verifies (authenticates) the transfer passcode (step Sc24). If authentication of the transfer passcode fails (Step Sc25; NO), the user inputs the passcode again. On the other hand, if the transfer passcode is successfully authenticated (step Sc25; YES), the management server 10 executes the transfer reservation (step Sc26). Then, the management server 10 notifies the store terminal 20 of the user of a completion message indicating that the transfer reservation has been completed (step Sc27).

After confirming the completion message sent to the store terminal 20, the user taps the transfer standby card C14 (step Sc10). In addition, since it has already demonstrated about the operation|movement after this, it omits.

On the other hand, the user determines that the transfer reservation should be canceled (step Sc16; YES), and cancels the transfer reservation (step Sc17). The management server 10 deletes the transfer data registered in the invoice-related DB 123 in accordance with the transfer reservation cancellation instruction (step Sc18). If the user determines that the transfer reservation should not be canceled (step Sc16; NO), the user refers to the transfer detail screen P17 and confirms the amount of the insufficient amount (step Sc7).

(If you tap the payment waiting card)
When the user taps the payment waiting card (step Sc4), the user confirms the details of the transfer data (step Sc13). The management server 10 displays, for example, a detailed screen P21 showing details of the transfer data as shown in FIG. 27 (step Sc14). The user refers to the detailed screen P21 and decides whether to cancel the transfer reservation (step Sc16). In addition, since it has already demonstrated about the operation|movement after this, it omits.

After that, when the specified transfer date set by the user arrives, the management server 10 makes the transfer according to the transfer data, and pays the client or the like (step Sc28→step Sc29). When the payment is normally made, the management server 10 notifies the store terminal 20 of the user of a completion message indicating that the transfer has been completed (step Sc30), and also displays the transfer history, for example, as shown in FIG. A confirmation screen P22 for confirmation is displayed. The user refers to the confirmation screen P22, confirms that the transfer has been performed normally (step Sc31), and terminates the process.

<<Accounting linkage processing flow>>
FIG. 29 is a flow chart showing an accounting linkage processing flow.
When the setting button B5 is tapped by the user, a setting screen P23 as shown in FIG. 30, for example, which enables various settings regarding the system 1, is displayed. The user taps the item IT1 for issuance of shared URL for accounting/tax accountant office displayed on the setting screen P23 (step Sd1). For convenience of explanation, a URL for sharing invoice information and payment history (transfer data) with partner accounting firms is hereinafter referred to as a "shared URL" (reference address information).

(If the shared URL has not yet been issued)
If a shared URL has not yet been issued (step Sd2; NO), a setting screen for issuing a shared URL is displayed. After tapping the setting button displayed on the setting screen, the user performs a predetermined operation to request issuance (creation) of the shared URL (step Sd3). Upon receiving such a request, the management server 10 issues a new shared URL and password (step Sd4), and stores the issued new shared URL and password in the user-related DB 122 or the like. Then, the management server 10 displays a notification screen P25 for notifying issuance of the shared URL and password as shown in FIG. 31, for example.

The user copies the shared URL and password displayed on the notification screen P25 (step Sd5), notifies (shares) the affiliated accounting firm by e-mail or telephone (step Sd6), and executes the process. finish.

The person in charge of the affiliated accounting firm logs in using the notified shared URL and password (step Sd11). As an example, the person in charge logs in by entering the notified shared URL and password into the office terminal of the accounting firm. If the login succeeds, the person in charge can access the user's invoice information and transfer data representing the withdrawal history (steps Sd12 and Sd14).

The management server 10 receives an access request from the office terminal, for example, the first shared screen P26 showing bill information of the user as shown in FIG. The second shared screen P27 showing the data is displayed on the office terminal (step Sd13, step Sd15).

Here, the invoice information shared with the accounting office can be limited to invoice information for a predetermined period (for example, one month) of the user's invoice information. As an example, the user appropriately operates the screen P26 displayed on the store terminal 20 to set the predetermined period. Examples of the predetermined period include, but are not limited to, a period during which payment-related processing (for example, payment to the biller; hereinafter referred to as payment-related processing) is performed based on the invoice information. . In addition, the user can set and change the period during which the bill information is shared with the sharing destination at any timing.

Furthermore, when the user operates a plurality of stores, it is possible to select a store that shares invoice information with the accounting office (hereinafter referred to as a shared store). For example, by appropriately operating the screen P26 displayed on the shop terminal 20, the user can select all shops as shared shops, or select a specific area (for example, Minato-ku, Tokyo). A store can be selected as a shared store.

(If the shared URL has already been issued)
If the shared URL has already been issued (step Sd2; YES), the user determines that the existing shared URL is unnecessary (step Sd7) and requests the management server 10 to invalidate the shared URL. (step Sd8). When the management server 10 receives the request to invalidate the shared URL, it performs a process of invalidating the already issued shared URL (step Sd9). After that, when the user determines that the new shared URL should be used with the affiliated accounting firm (step Sd10), the process proceeds to step Sd3 to perform setting input for issuing the shared URL. In addition, since it has already demonstrated about the operation|movement after this, it omits.

As described above, according to the present embodiment, it is possible to efficiently proceed with processing related to invoices.

The embodiments described above are examples for explaining the present invention, and are not intended to limit the present invention to those embodiments. Also, the present invention can be modified in various ways without departing from the gist thereof. For example, those skilled in the art can replace the resources (hardware resources or software resources) described in the embodiments with equivalents, and such replacements are also included in the scope of the present invention.

DESCRIPTION OF SYMBOLS 1... Information processing system 10... Management server 11... Communication interface 12... Storage part 13... Processor 20... Store terminal 21... Camera 22... Display part 23... Operation input part 24... Storage part 25 Processor 26 Communication interface 121 Information processing program 122 User-related database 123 Invoice-related database 131 Control unit 241 Main application 251 Control unit B1 Camera button B2 Home button B3...Billing list button B4...Transfer history button B5...Setting button B6, B8, B9...Imaging button B7...Data conversion button B10...Data conversion execution button B11...Save button B12...Select button, B13... button to proceed to the next step, B14... button to proceed to transfer reservation confirmation, B15... button to execute transfer, B16... button to set, C11... card being converted to data, C12... card converted to data, C13... waiting for payment Card, C14... Transfer waiting card, C15... Confirmation waiting card, C16... Transfer reservation waiting card, C21... Invoice confirmation card, C31... Transfer confirmation card, N11... Number of claims, N21... Number of transfers, A11... Total amount billed , A21...Total transfer amount, P1...Home screen, P2...Billing list screen, P3...Transfer history list screen, P4...Selection screen, P5, P6, P7...Imaging screen, P8...Confirmation screen, P9...Data conversion list P10... List screen P11... Billing details screen P12... Editing screen P13... Billing details screen P14... Setting screen P15... Selection screen P17... Transfer details screen P18... List screen P19... Details screen P20...Confirmation screen, P21...Details screen, P22...Confirmation screen, P23...Setting screen, P25...Notification screen, P26...First shared screen, P27...Second shared screen.

Claims (10)

A control method for an information processing device that executes processing related to an invoice,
displaying a first operator for uploading invoices;
a step of displaying a second operator for enabling selection of a plurality of upload methods according to the operation of the first operator;
and executing upload processing of the bill based on the selected upload method. 2. The method of controlling an information processing apparatus according to claim 1, wherein said plurality of uploading methods are different uploading methods according to the number of said bills. 2. The method of controlling an information processing apparatus according to claim 1, wherein said plurality of uploading methods are a method of uploading an image of said invoice captured using a camera and a method of uploading a file of said invoice. a step of displaying a third operator for recognizing characters from the captured image of the bill and converting them into data when a method of uploading an image of the bill captured by the camera is selected; 4. The control method for the information processing apparatus according to claim 3, wherein 2. The method of controlling an information processing apparatus according to claim 1, wherein said plurality of uploading methods include at least a method of uploading said invoice file. When a method of uploading an image of the invoice captured by the camera is selected and the invoice consists of a plurality of pages, each page of the invoice is captured and corrected. 4. The control method for the information processing apparatus according to claim 3, wherein 2. The control method for an information processing apparatus according to claim 1, wherein a confirmation screen of said invoice to be uploaded differs for each of said plurality of upload methods. 8. The control method for an information processing apparatus according to claim 7, wherein when said bill consists of a plurality of pages, it is possible to select a page to be enlarged and displayed on said bill confirmation screen. In the information processing device that executes processing related to invoices,
displaying a first operator for uploading invoices;
a step of displaying a second operator for enabling selection of a plurality of upload methods according to the operation of the first operator;
a step of executing the invoice upload process based on the selected upload method; and An information processing device that executes processing related to an invoice and includes a control unit and a storage unit, wherein the control unit executes a program stored in the storage unit to
displaying a first operator for uploading invoices;
a step of displaying a second operator for enabling selection of a plurality of upload methods according to the operation of the first operator;
an information processing apparatus configured to execute: a step of executing upload processing of the bill based on the selected upload method.

Images