JP7591003B2 - Information processing device, information processing method, and information processing program - Google Patents

Description

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

Nowadays, processing a large number of invoices and other documents sent by business partners places a heavy burden on business operators. Patent Document 1 (JP Patent Publication 2022-045315 A) discloses a data processing device that aims to reduce the burden of sorting multiple invoice data.

In this data processing device, the data acquisition unit reads multiple invoices, and the classification unit classifies each read invoice into catalog data for a "catalog" equivalent to a cover page on which the recipient's name, date, etc. are written, and detail data indicating a "detail" on which the invoice amount, etc. is written. The identification unit identifies the issuer of the catalog and the issuer of the detail. The generation unit then aggregates the catalog data and detail data classified by the classification unit for each issuer identified by the identification unit to generate multiple invoice data. The generated invoice data is output by the output unit. This reduces the burden of the task of classifying multiple invoice data.

JP 2022-045315 A

Nowadays, various information, such as invoices or receipts, is often digitized and transmitted. However, even when invoices or receipts are received as data, the work of the business operator is required according to the amount of data received. For this reason, the work burden on the business operator is not much different from when invoices or receipts were sent by mail.

The present invention has been made in consideration of the above-mentioned problems, and aims to provide an information processing device, an information processing method, and an information processing program that can reduce the workload of business operators required for data processing.

In order to solve the above-mentioned problems and achieve the object, the information processing device of the present invention comprises an acquisition unit that acquires data to be imported from an import position set based on the layout of file data, a conversion unit that converts data to be imported that has been acquired as details from the acquired data to be imported into classification data indicating a specified classification, and a data generation unit that generates information processing data for specified information processing including the classification data , wherein the acquisition unit acquires at least the data to be imported of the details and billing amount data indicating the billing amount from each import position set based on the layout of billing data indicating the billing amount, which is file data, and the conversion unit converts the data to be imported that has been acquired as details into item data indicating an accounting classification, and the data generation unit generates expense data for accounting processing including item data and billing amount data as information processing data, and generates journal entry data for accounting based on the expense data .

In addition, in order to solve the above-mentioned problems and achieve the object, the information processing method of the present invention includes an acquisition step in which an acquisition unit acquires data to be imported from an import position set based on the layout of file data, a conversion step in which a conversion unit converts data to be imported that has been acquired as details from the acquired data to be imported, into classification data indicating a predetermined classification, and a data generation step in which a data generation unit generates information processing data for predetermined information processing including the classification data , wherein in the acquisition step, the acquisition unit acquires at least data to be imported of the details and billing amount data indicating the billing amount from each import position set based on the layout of the billing data indicating the billing amount, which is file data, and in the conversion step, the conversion unit converts the data to be imported that has been acquired as details into item data indicating an accounting classification, and in the data generation step, the data generation unit generates expense data for accounting processing including item data and billing amount data as information processing data, and generates journal entry data for accounting based on the expense data .

In addition, in order to solve the above-mentioned problems and achieve the object, the information processing program of the present invention causes a computer to function as an acquisition unit that acquires data to be imported from an import position set based on the layout of file data, a conversion unit that converts data to be imported that is acquired as a breakdown from the acquired data to be imported into classification data indicating a predetermined classification, and a data generation unit that generates information processing data for specified information processing including the classification data, wherein the acquisition unit acquires at least data to be imported of the breakdown and billing amount data indicating the billing amount from each import position set based on the layout of billing data indicating the billing amount, which is file data, and the conversion unit converts the data to be imported that is acquired as the breakdown into item data indicating an accounting classification, and the data generation unit generates expense data for accounting processing including item data and billing amount data as information processing data, and generates journal entry data for accounting based on the expense data .

The present invention can reduce the workload of business operators required for data processing.

FIG. 1 is a block diagram showing a hardware configuration of a billing processing device according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a line master. FIG. 3 is a diagram illustrating an example of the account item master. FIG. 4 is a diagram showing an example of the billing details master. FIG. 5 is a diagram showing an example of the billing ID master. FIG. 6 is a diagram illustrating an example of the date master. FIG. 7 is a diagram showing an example of the billing amount master. FIG. 8 is a diagram illustrating an example of the subject conversion master. FIG. 9 is a diagram showing an outline of data processing in the billing processing apparatus according to the embodiment. FIG. 10 is a flowchart showing the flow of data processing operations of the billing processing device according to the embodiment. FIG. 11 is a diagram showing an example of billing data transmitted from carrier A, which is one of the telephone communication companies, and an example of billing data transmitted from carrier B, which is another telephone communication company. FIG. 12 is a diagram illustrating an example of the expense data generated by the billing processing apparatus according to the embodiment. FIG. 13 is a diagram illustrating an example of journal data generated based on expense data by the billing processing device according to the embodiment.

The following is a detailed explanation of a billing processing device according to an embodiment of the present invention, with reference to the drawings. The billing processing device in this embodiment is a terminal device of a call center contractor, and is a terminal device that processes billing data sent from a telephone communication company (carrier company) for each line (telephone number) used at the call center. However, the present invention is not limited to this embodiment.

(overview)
Call center contractors receive invoices from carrier companies for each line (telephone number) used at the call center. Invoices from carrier companies are broken down into separate details for each type of usage, with different expense items for each type. In addition, the format (layout) differs for each carrier company. This means that business operators are required to analyze the contents of the invoice data for each carrier company and manually enter the data into the payment request input screen, which creates an excessive workload for business operators at the end of the month.

In the billing processing device of the embodiment, data is automatically acquired by specifying the import position on the layout, such as "column" or "row," based on the billing data layout, which differs for each carrier company. This makes it possible to import desired data such as subject, payment category, cost category, etc. for each telephone number. In addition, of the acquired data, breakdown data indicating the contents of the billing is converted into subject data for accounting, and expense data for accounting processing is generated. Furthermore, based on this expense data, journal entry data for accounting purposes is also generated. This significantly reduces the burden on business operators in processing billing data.

Furthermore, if the billing data needs to be modified due to a contract with a carrier company or the like, directly modifying the billing data from the carrier company will result in modifying the original data, which can cause the mistake to be carried over to subsequent processing if an error occurs when modifying the original data. For this reason, the billing processing device of the embodiment does not modify the original billing data, but instead modifies the expense data generated from the billing data. This can prevent the inconvenience of a mistake made when modifying the original billing data being carried over to subsequent processing.

The identification number (ID) of the billing data may differ depending on the carrier company, such as in some cases being a "telephone number" or in other cases being a specific identification number. In either case, the billing processing device of the embodiment is capable of importing the desired data described above.

(Hardware configuration)
Fig. 1 is a block diagram showing the hardware configuration of a billing processing device 1 according to an embodiment. The billing processing device 1 shown in Fig. 1 includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input/output interface unit 5. An input device 6 and an output device 7 are connected to the input/output interface unit 5. The output device 7 may be a display unit such as a monitor device (including a home television). The input device 6 may be a keyboard device, a mouse device, a microphone device, or a monitor device that cooperates with a mouse device to realize a pointing device function.

The communication interface unit 4 is connected to one or more carrier terminal devices 20 of carrier companies and one or more accounting terminal devices 30 via a network 8, which may be a wide area network such as the Internet or a private network such as a Local Area Network (LAN). The communication interface unit 4 receives billing data sent from each carrier terminal device 20. The communication interface unit 4 also sends accounting data generated based on the expense data to the accounting terminal device 30. The accounting terminal device 30 performs accounting processing of this accounting data based on an accounting system 40, which is software. The accounting system 40 may be provided on the billing processing device 1 side, as shown by the dotted line block in FIG. 1.

The storage unit 2 may be, for example, a storage device such as a ROM (Read Only Memory), a RAM (Random Access Memory), a HDD (Hard Disk Drive), or a SSD (Solid State Drive). The storage unit 2 is provided with a line master 11, an account item master 12, a billing breakdown master 13, a billing ID master 14, a date master 15, a billing amount master 16, and an item conversion master 17, each of which is a storage area.

Figure 2 is a diagram showing an example of the line master 11. As shown in this Figure 2, the line master 11 stores the carrier code, carrier name, line ID, billing ID, payment category, and payment category name. The carrier code is a code assigned to each carrier company. The carrier name is the company name of each carrier company. Figure 2 shows an example in which carrier company A is assigned a carrier code of "90", company B is assigned a carrier code of "91", and company C is assigned a carrier code of "92".

The line ID and billing ID are stored as the contracted telephone number or a specific identification number assigned by the carrier company. The example in Figure 2 is an example in which a telephone number such as "090-1111-1111" is stored as the line ID and billing ID of company A. The example in Figure 2 is also an example in which a telephone number such as "090-1111-3333" is stored as the line ID of company B, and a specific identification number such as "B000001" is stored as the billing ID.

The payment category is the category of the fee system, and the payment category name is the name of this fee system. In the example of Figure 2, payment category "1" indicates a "flat rate" fee system, and payment category "2" indicates a "pay as you go" fee system.

Figure 3 is a diagram showing an example of the account item master 12. As shown in this Figure 3, the account item master 12 stores item codes, item names, etc. In the example of Figure 3, the item code "K001" indicates "XX communication expenses", the item code "K002" indicates "XX communication expenses", and the item code "K003" indicates "Consumption tax".

Figure 4 is a diagram showing an example of the billing details master 13. The billing details master 13 stores a first billing details master 13a that stores columns (an example of a first import position) for acquiring billing details data under normal circumstances, and a second billing details master 13b that stores columns (an example of a second import position) different from the above-mentioned normal columns for acquiring billing details data under irregular circumstances. Figure 4(a) shows an example of the first billing details master 13a, and Figure 4(b) shows an example of the second billing details master 13b.

As shown in FIG. 4, the billing details master 13 stores a column number (column No.) that specifies the "column" of data to be obtained from the billing data of the carrier company in association with the carrier code and carrier name. The billing details master 13 also stores the billing details code and billing details name indicated by the data of that column number.

The example of the first billing breakdown master 13a used under normal circumstances shown in FIG. 4(a) shows that for the billing data of Company A, the fifth column (column No. 5) is specified as the column from which data is obtained. The data in this fifth column also shows that it includes the line usage fee (basic fee) with billing breakdown code "101", the dialing fee with billing breakdown code "102", the universal service fee with billing breakdown code "103", the consumption tax equivalent amount with billing breakdown code "104", and the SMS communication fee with billing breakdown code "105".

The example of the first billing breakdown master 13a used under normal circumstances shown in FIG. 4(a) indicates that for the billing data of Company B, the sixth column (column No. 6) is specified as the column from which data is obtained. The data in this sixth column includes "flat-rate communication fee (flat-rate data plan)" with billing breakdown code "106", "indoor wiring usage fee" with billing breakdown code "107", and "lump sum basic fee discount" with billing breakdown code "108".

In contrast, the example of the second billing breakdown master 13b used in irregular cases shown in Figure 4 (b) indicates that for Company A's billing data, the seventh column (column No. 7) is specified as the column from which data is acquired. The data in the seventh column acquired in irregular cases includes "line usage fee (basic fee)" with billing breakdown code "101", "dial call fee" with billing breakdown code "102", "universal service fee" with billing breakdown code "103", "equivalent amount of consumption tax" with billing breakdown code "104", and "SMS communication fee" with billing breakdown code "105".

Figure 5 is a diagram showing an example of the billing ID master 14. In this billing ID master 14, a column number indicating the column in which the billing ID is recorded is stored in association with the carrier code and carrier name. In the example of Figure 5, it shows that the billing ID is recorded in the "first column" for both Company A and Company B.

Figure 6 is a diagram showing an example of the date master 15. In this date master 15, a column number indicating the column in which the billing date is recorded is stored in association with the carrier code and carrier name. In the example of Figure 6, it is shown that the billing date is recorded in the "third column" for both Company A and Company B.

Figure 7 is a diagram showing an example of the billing amount master 16. In this billing amount master 16, a column number indicating the column in which the billing amount is recorded is stored in association with the carrier code and carrier name. In the example of Figure 7, it shows that the billing date is recorded in the "fourth column" for both Company A and Company B.

Figure 8 shows an example of the subject conversion master 17 for converting billing breakdown data into subject codes for account items. This subject conversion master 17 stores subject codes and subject names that correspond to billing breakdown codes and billing breakdown names obtained from a specified column of the billing data of each carrier company as described above.

Specifically, the example in Figure 8 shows that Company A's "Line usage fee (basic fee)" with billing breakdown code "101" is converted to item data with item code "K001" and item name "XX communication fee". The example in Figure 8 also shows that Company A's "Tayal call fee" with billing breakdown code "102", "Universal service fee" with billing breakdown code "103", and "SMS communication fee" with billing breakdown code "105" are each converted to item data with item code "K002" and item name "XX communication fee". The example in Figure 8 also shows that Company A's "Amount equivalent to consumption tax" with billing breakdown code "104" is converted to item data with item code "K003" and item name "consumption tax".

The example in Figure 8 also shows that the billing breakdown code for Company B's "Flat-rate communication charges (flat-rate data plan)" with billing breakdown code "106", "Indoor wiring usage charges" with billing breakdown code "107", and "Lump-sum basic fee discount" with billing breakdown code "108" are each converted into item data with the item code "K001" and the item name "XX communication charges".

(Functional configuration of billing processing device)
Next, the control unit 3 executes the billing processing program stored in the memory unit 2, and thereby functions as an acquisition unit 21, a conversion unit 22, a data generation unit 23, a change processing unit 24, a display control unit 25, and a master selection processing unit 26.

The acquisition unit 21 acquires "column" data that is pre-specified based on the layout of the billing data. Note that, in the following, the description will be given assuming that the billing processing device 1 of the embodiment acquires "column" data that is pre-specified from the billing data, but it may also acquire data from a specified desired import position, such as acquiring "row" data that is pre-specified. In either case, the same effect as described below can be obtained.

The conversion unit 22 converts billing breakdown data indicating billing details, among the data obtained from the billing data, into item data indicating account items. The data generation unit 24 generates expense data (= cost data) indicating the communication costs of the call center, based on the data obtained from the billing data and the item data generated by the conversion process. When a change operation (modification operation) is performed on the expense data by the business operator, the change processing unit 24 changes the value of the expense data in accordance with this change operation.

The display control unit 25 displays the generated expense data, etc., via the output device 7, which is an example of a display unit. The business operator changes the expense data, if necessary, based on the displayed expense data. As described above, the billing breakdown master 13 stores a first billing breakdown master 13a that stores columns for acquiring billing breakdown data under normal circumstances, and a second billing breakdown master 13b that stores columns different from the above-mentioned normal columns as columns for acquiring billing breakdown data under irregular circumstances. The master selection processing unit 26 selects the first billing breakdown master 13a or the second billing breakdown master 13b as the billing breakdown master 13 to be used to acquire billing breakdown data, depending on the selection operation of the business operator. The acquisition unit 21 uses the selected billing breakdown master 13 to acquire billing breakdown data from the carrier company's billing data.

(Overview of billing data processing operation of billing processing device)
Next, Fig. 9 shows an overview of the processing operation of billing data from each company in the billing processing device 1 of this embodiment having such a configuration. As shown in Fig. 9, when the billing processing device 1 of this embodiment acquires billing data from the carrier terminal device 20 of each carrier company such as Company A to Company C, in step S1, it acquires billing detail data (billing detail code and billing detail name) of a specified column from the billing data based on the various masters 11 to 16 such as the billing detail master 13 mentioned above. Then, based on the item conversion master 17, it converts this billing detail data into item data indicating account items.

Next, in step S2, the billing processing device 1 generates expense data including the item data generated by the conversion. Then, in step S3, based on this expense data, it generates journal entry data for accounting purposes and transmits it to the accounting system 40 of the accounting terminal device 30 for accounting processing.

(Details of billing data processing operation of billing processing device)
Next, the billing data processing operation in the billing processing device 1 of this embodiment will be described in detail with reference to the flowchart in Fig. 10. The control unit 3 of the billing processing device 1 executes each process of the flowchart in Fig. 10 based on the billing processing program stored in the storage unit 2. First, in step S11, the acquisition unit 21 acquires billing data received from the carrier terminal device 20 of each carrier company.

Figure 11 shows an example of this billing data. Of these, Figure 11(a) is an example of the billing data for Company A, and Figure 11(b) is an example of the billing data for Company B. Company A's billing data shown in Figure 11(a) is composed of a billing ID, last basic fee, current basic fee, billing amount, billing breakdown code, backup, last meter reading date, and current meter reading date. In the case of Company A, the billing ID is a telephone number such as "090-1111-1111". The billing breakdown code is recorded in the "5th column".

In contrast, the billing data for Company B shown in Figure 11 (b) is composed of a billing ID, last basic fee, current basic fee, billing amount, reserve, billing breakdown code, last meter reading date, and current meter reading date. In the case of Company B, the billing ID is a specific identification number such as "B000001". The billing breakdown code is recorded in the "sixth column".

Next, in step S12, the acquisition unit 21 determines whether or not a change designation operation has been performed on the billing breakdown master 13. That is, as described above, the billing breakdown master 13 stores a first billing breakdown master 13a that stores columns for acquiring billing breakdown data under normal circumstances, and a second billing breakdown master 13b that stores columns different from the above-mentioned normal columns for acquiring billing breakdown data under irregular circumstances.

Normally (or by default), the master selection processing unit 26 selects the first billing detail master 13a. If the first billing detail master 13a is selected by the master selection processing unit 26, the acquisition unit 21 determines that no change designation operation has been performed (step S12: No) and proceeds to step S13.

In step S13, the acquisition unit 21 refers to the first billing breakdown master 13a shown in FIG. 4(a) and detects the "column" in which the billing breakdown code of each company is recorded. In the example of FIG. 4(a), the "column" in which the billing breakdown code of Company A's billing data is recorded is the "fifth column," and the "column" in which the billing breakdown code of Company B's billing data is recorded is the "sixth column." Therefore, the acquisition unit 21 acquires billing breakdown codes such as "101" and "102" by acquiring the data in the fifth column from the billing data of Company A shown in FIG. 11(a). Also, the acquisition unit 21 acquires billing breakdown codes such as "107" and "108" by acquiring the data in the sixth column from the billing data of Company B shown in FIG. 11(a).

In step S13, the acquisition unit 21 also detects the columns in which the billing IDs of each company are recorded by referring to the billing ID master 14 shown in FIG. 5. Based on the detection result, the acquisition unit 21 then acquires a billing ID with a telephone number such as "090-1111-1111" from the first column of the billing data of company A shown in FIG. 11(a). The acquisition unit 21 also acquires a billing ID with a specific billing number such as "B000001" from the first column of the billing data of company B shown in FIG. 11(b).

In addition, in step S13, the acquisition unit 21 detects the columns in which the billing dates of each company are recorded by referring to the date master 15 shown in FIG. 6. Then, based on the detection result, the acquisition unit 21 acquires a billing date such as "February 1, 2021" from the third column of the billing data of Company A shown in FIG. 11(a). The acquisition unit 21 also acquires a billing date such as "February 1, 2021" from the third column of the billing data of Company B shown in FIG. 11(b).

In step S13, the acquisition unit 21 also detects the columns in which the billing amounts of each company are recorded by referring to the billing amount master 16 shown in FIG. 7. Based on the detection result, the acquisition unit 21 then acquires billing amounts such as "1000 yen" and "200 yen" from the fourth column of the billing data of company A shown in FIG. 11(a). The acquisition unit 21 also acquires billing amounts such as "1000 yen" and "200 yen" from the fourth column of the billing data of company B shown in FIG. 11(b).

On the other hand, for example, if the layout of the billing data is changed, the business operator selects the second billing details master 13b shown in FIG. 4(b), for example, which corresponds to the changed layout. The second billing details master 13b shown in FIG. 4(b) is an example in which the layout of Company A's billing data has changed, and the column for acquiring billing details data (billing details code and billing details name) has changed from the fifth column (see FIG. 4(a)) to the seventh column (see FIG. 4(b)). When the billing details master 13b is selected, the acquisition unit 21 determines that a change has been specified (step S12: Yes) and proceeds to step S18.

In step S18, the acquisition unit 21 refers to the second billing breakdown master 13b shown in FIG. 4(b) and detects the "column" in which the billing breakdown code of each company is recorded. In the example of FIG. 4(a), the "column" in which the billing breakdown code of Company A's billing data is recorded has been changed to the "seventh column." Therefore, the acquisition unit 21 acquires the data in the seventh column of Company A's billing data to acquire billing breakdown codes such as "101" and "102." This makes it possible to acquire desired data such as billing breakdown codes in response to changes in the layout of Company A's billing data.

When the layout of the billing data is changed, for example, the column number of the "fifth column" shown in FIG. 4(a) may be modified to the "seventh column." However, as in this embodiment, by preparing a billing details master 13b for handling layout changes in advance and switching the billing details master 13 to be used when a layout change occurs, it is possible to safely and easily handle layout changes without rewriting the column numbers of the billing details master 13.

In step S18, the acquisition unit 21 also detects the columns in which the billing IDs of each company are recorded by referring to the billing ID master 14 shown in FIG. 5. Based on the detection result, the acquisition unit 21 then acquires a billing ID with a telephone number such as "090-1111-1111" from the first column of the billing data of company A shown in FIG. 11(a). The acquisition unit 21 also acquires a billing ID with a specific billing number such as "B000001" from the first column of the billing data of company B shown in FIG. 11(b).

In addition, in step S18, the acquisition unit 21 detects the columns in which the billing dates of each company are recorded by referring to the date master 15 shown in FIG. 6. Then, based on the detection result, the acquisition unit 21 acquires a billing date such as "February 1, 2021" from the third column of the billing data of Company A shown in FIG. 11(a). The acquisition unit 21 also acquires a billing date such as "February 1, 2021" from the third column of the billing data of Company B shown in FIG. 11(b).

In step S18, the acquisition unit 21 also detects the columns in which the billing amounts of each company are recorded by referring to the billing amount master 16 shown in FIG. 7. Based on the detection result, the acquisition unit 21 then acquires billing amounts such as "1000 yen" and "200 yen" from the fourth column of the billing data of company A shown in FIG. 11(a). The acquisition unit 21 also acquires billing amounts such as "1000 yen" and "200 yen" from the fourth column of the billing data of company B shown in FIG. 11(b).

Next, in step S14, the conversion unit 22 converts the billing breakdown data (billing breakdown code and billing breakdown name) acquired in step S13 or step S18 into the subject code of the account subject based on the subject conversion master 17 shown in FIG. 8.

Specifically, by referring to the account conversion master 17, the conversion unit 22 converts Company A's "Line usage fee (basic fee)" with billing breakdown code "101" into account data with account code "K001" and account name "XX communication fee". The conversion unit 22 also converts Company A's "Tayal call charge" with billing breakdown code "102", "Universal service charge" with billing breakdown code "103", and "SMS communication fee" with billing breakdown code "105" into account data with account code "K002" and account name "XX communication fee". The conversion unit 22 also converts Company A's "Amount equivalent to consumption tax" with billing breakdown code "104" into account data with account code "K003" and account name "consumption tax".

The conversion unit 22 also converts B company's "Flat-rate communication fee (flat-rate data plan)" with billing breakdown code "106", "Indoor wiring usage fee" with billing breakdown code "107", and "Lump-sum basic fee discount" with billing breakdown code "108" into item data with item code "K001" and item name "XX communication fee".

Next, in step S15, the data generation unit 23 generates expense data as illustrated in FIG. 12, which includes the converted item data. Specifically, as shown in FIG. 12, the data generation unit 23 generates expense data to include the billing item data (billing item code and billing item name) before the conversion described above, and the item data (item code and item name) generated by the conversion described above. The data generation unit 23 also generates this expense data, including the carrier code, carrier name, billing ID, and billing amount.

Next, the generated expense data can be changed (modified). When changing the expense data, the business operator specifies the display of the expense data via the input device 6. When this display is specified, the display control unit 25 displays the expense data via the output device 7. When the expense data is displayed, the business operator specifies a change to the expense data via the input device 6. This makes it possible to change the expense data, and the business operator changes the desired part of the expense data to the desired value via the input device 6.

In step S16, the change processing unit 24 monitors whether or not such a change operation to the expense data has been performed. If no change operation to the expense data has been performed (step S16: No), the process proceeds to step S17. On the other hand, if a change operation to the expense data has been detected (step S16: Yes), the change processing unit 24 proceeds to step S19 and modifies the expense data in accordance with the change operation by the business operator.

If the billing data needs to be modified due to a contract with a carrier company, etc., directly modifying the billing data from the carrier company will result in modifying the original data, which can cause the mistake to be carried over to subsequent processing if an error occurs when modifying the original data. However, in the billing processing device 1 of the embodiment, rather than modifying the original billing data, the error is carried over to the expense data generated from the billing data. This can prevent the inconvenience of a mistake made when modifying the original billing data being carried over to subsequent processing.

Next, in step S17, the data generation unit 23 generates accounting journal data as shown in FIG. 13 based on the expense data, and ends the processing of the flowchart in FIG. 10. The journal data shown in FIG. 13 is an example in which the debit side is XX communication expenses of 4,400 yen and XX communication expenses of 400 yen, and the credit side is an amount payable of 4,800 yen.

The generated accounting data is sent to the accounting terminal device 30 and processed by the accounting system 40 at a timing specified by the business operator, or is stored in the memory unit 2 and processed by the accounting system 40. In this way, the billing processing device 1 of the embodiment can automatically generate expense data and accounting data, significantly reducing the workload of the business operator.

(Effects of the embodiment)
As is clear from the above description, the billing processing device 1 of the embodiment automatically acquires data by specifying the import position on the layout, such as "column" or "row," based on the layout of billing data that differs for each carrier company. This makes it possible to import desired data such as item, payment category, cost category, etc. for each telephone number. In addition, of the acquired data, the breakdown data indicating the billing content is converted into item data for account items to generate expense data for accounting processing. Furthermore, based on this expense data, journal entry data for accounting purposes is also generated. This makes it possible to significantly reduce the burden on business operators in processing billing data.

Furthermore, if the billing data needs to be modified due to a contract with the carrier company or the like, directly modifying the billing data from the carrier company will result in modifying the original data, which can cause the mistake to be carried over to subsequent processing if an error occurs when modifying the original data. However, in the billing processing device 1 of the embodiment, rather than modifying the original billing data, the error is carried over to the expense data generated from the billing data. This can prevent the inconvenience of a mistake that occurs when modifying the original billing data being carried over to subsequent processing.

In addition, it is possible to obtain data for the desired items in both cases where a "telephone number" is used as the identification number (ID) for the billing data, and where a specific identification number (billing ID) is used. This makes it possible to provide a billing processing device 1 that is easy to use for business operators, etc.

[Contribution to the United Nations-led Sustainable Development Goals (SDGs)]
This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby making it possible to contribute to Goals 8 and 9 of the SDGs.

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs Goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[Other embodiments]
The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method.

In addition, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

Furthermore, with regard to the billing processing device 1, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the billing processing device 1, particularly the control unit 3 and each processing function performed by the control unit 3, may be realized in whole or in part by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the billing processing device 1 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD to work with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit 3.

In addition, the billing processing program of this billing processing device 1 may be stored in another server device connected to the billing processing device 1 via any network, and it is also possible to download all or part of it as necessary.

The billing processing program for executing the processing described in this embodiment may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical Disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a distributed structure consisting of multiple modules or libraries, and a structure that achieves its function by working together with a separate program, such as an OS. Note that the specific structure and reading procedure for reading a recording medium in the billing processing device 1 shown in the embodiment, as well as the installation procedure after reading, can use well-known structures and procedures.

The memory unit 2 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, and web page files used for various processes and providing websites.

The billing processing device 1 may be configured as an information processing device such as a known personal computer device or a workstation, or may be configured as an information processing device to which any peripheral device is connected. The information processing device may also be realized by implementing software (including programs or data, etc.) that realizes the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or function additions. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

The present invention is suitable for use in tasks involving data processing of file data with a fixed layout.

REFERENCE SIGNS LIST 1 billing processing device 2 storage unit 3 control unit 4 communication interface unit 5 input/output interface unit 6 input device 7 output device 8 network 11 line master 12 account item master 13 billing detail master 13a first billing detail master 13b second billing detail master 14 billing ID master 15 date master 16 billing amount master 17 item conversion master 20 carrier terminal device 21 acquisition unit 22 conversion unit 23 data generation unit 24 change processing unit 25 display control unit 26 master selection processing unit 30 accounting terminal device 40 accounting system

Claims (7)

an acquisition unit that acquires data to be imported from an import position that is set based on a layout of the file data;
A conversion unit that converts the data to be imported, which is acquired as a breakdown of the acquired data to be imported, into classification data indicating a predetermined classification;
a data generating unit that generates information processing data for a predetermined information processing, including the classification data ;
The acquisition unit acquires at least the data to be imported of the breakdown and the billing amount data indicating the billing amount from each import position set based on a layout of the billing data indicating the billing amount, which is the file data;
The conversion unit converts the data to be imported acquired as a breakdown into item data indicating an accounting classification,
the data generation unit generates, as the information processing data, expense data for accounting processing including the item data and the billing amount data, and generates journal entry data for accounting based on the expense data;
An information processing device comprising : the acquiring unit acquires, from the file data, the data to be imported of a column to be imported that is set as the import position;
2. The information processing apparatus according to claim 1, The conversion unit converts the data to be imported acquired as a breakdown into item data indicating an accounting classification;
3. The information processing device according to claim 1 or 2, a change processing unit that changes a value of the generated cost data to a value according to a change operation by a business operator ;
4. The information processing device according to claim 1, wherein : the acquiring unit acquires the data to be imported from a first import position set based on a layout of file data or from a second import position different from the first import position;
5. The information processing device according to claim 1, wherein : an acquiring step in which an acquiring unit acquires data to be imported from an import position set based on a layout of the file data;
A conversion step in which a conversion unit converts the captured data acquired as a breakdown of the captured data into classification data indicating a predetermined classification;
a data generating step in which a data generating unit generates information processing data for a predetermined information processing, the information processing data including the classification data;
In the acquisition step, the acquisition unit acquires at least the data to be imported of the breakdown and the billing amount data indicating the billing amount from each import position set based on a layout of the billing data indicating the billing amount, which is the file data;
In the conversion step, the conversion unit converts the data to be imported acquired as a breakdown into item data indicating an accounting classification,
In the data generation step, the data generation unit generates, as the information processing data, expense data for accounting processing including the item data and the billing amount data, and generates journal data for accounting based on the expense data;
An information processing method comprising : Computer,
an acquisition unit that acquires data to be imported from an import position that is set based on the layout of the file data;
A conversion unit that converts the data to be imported, which is acquired as a breakdown of the acquired data to be imported, into classification data indicating a predetermined classification;
a data generating unit that generates information processing data for a predetermined information processing, the information processing data including the classification data ;
The acquisition unit acquires at least the data to be imported of the breakdown and the billing amount data indicating the billing amount from each import position set based on a layout of the billing data indicating the billing amount, which is the file data;
The conversion unit converts the data to be imported acquired as a breakdown into item data indicating an accounting classification,
the data generation unit generates, as the information processing data, expense data for accounting processing including the item data and the billing amount data, and generates journal entry data for accounting based on the expense data;
An information processing program characterized by:

Images