Line service managing device, line service management method, and line service management program

Abstract

To realize complex charge management to an end user without any processing leakage while importing charge data from each carrier regardless of management granularity of a different line and SIM for each line carrier when providing a line service.SOLUTION: A line service managing device has: contract inputting means for inputting order data; ordering input means for inputting ordering data on the basis of the order data; line ID collaboration means for acquiring a line ID corresponding to a line internal key of the ordering data in collaboration with a line carrier and updating the line ID of the ordering data; charge data reception means for updating the line charge number, ordering quantity, and ordering sum of the ordering table on the basis of the line ID of the carrier charge data and a scheduled purchasing date; purchasing input means for inputting purchasing data on the basis of the ordering data; and payment input means for inputting payment data on the basis of the purchasing data.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present invention relates to a line service management device, a line service management method, and a line service management program.

Background Art

[0002] As a system for providing line services, for example, there is Patent Document 1.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in conventional line services, in terms of the management forms and operations in each aspect of contract management, billing management, and payment management, the differences in the management granularities cannot be absorbed, and the business processing timings are scattered. Therefore, management becomes complicated, linkage management cannot be performed, and there are problems such as risks leading to processing omissions in each business.

[0005] The present invention has been made in view of the above, and an object of the present invention is to provide a line service management device, a line service management method, and a line service management program that can realize complex billing management for end-users without processing omissions while taking in billing data from each carrier regardless of the management granularity of lines, SIMs, etc. that are different for each line carrier when providing a line service.

Means for Solving the Problems

[0006] In order to solve the above-described problems and achieve the object, the present invention is a line service management apparatus that includes a control unit and provides a line service using a line of a line carrier. The control unit is configured to be accessible to a billing pattern master in which a customer code, a billing issue pattern code, and a pattern name are registered in association with each other, a product master in which a product code, a product name, whether it is a line ID target, a line ID aggregation destination code, and a volume-based charging code are registered in association with each other, and a volume-based charging calculation master in which a volume-based charging calculation code, SEQ, a volume-based charging calculation name, a calculation classification code, a calculation classification name, a surcharge rate, a quantity, and a unit price are registered in association with each other. The apparatus includes a contract input means for inputting order data including an order number, a contract name, an order line number, a product code, a base, a billing issue pattern code, a planned sales date, an ordered quantity, and an ordered amount, an order input means for inputting order release data including an order release number, an order release name, an order release line number, a product code, a base, a line internal key, a line ID, a line billing number, a planned purchase date, an ordered quantity, an ordered amount, an order number, and an order line number based on the order data, a line ID cooperation means for obtaining a line ID corresponding to the line internal key of the order release data in cooperation with a line carrier and updating the line ID of the order release data, a claim data receiving means for taking in carrier claim data including a planned purchase date, a line ID, a line billing number, an ordered quantity, and an ordered amount in cooperation with a line carrier, and updating the line billing number, the ordered quantity, and the ordered amount of the order release data based on the line ID and the planned purchase date of the carrier claim data; a purchase input means for inputting purchase data including a purchase number, a purchase line number, an order release number, an order release line number, a purchase date, a planned payment date, a purchase amount, and a line billing number based on the order release data; a payment input means for inputting payment data including a payment number, a payment date, a planned payment date, a purchase number, a purchase line number, a payment amount, and a line billing number based on the purchase data; a sales input means for inputting sales data including a sales order number, a sales line number, a sales date, a planned sales date, a planned billing date, an order number, an order line number, a billing issue pattern code, and an ordered amount based on the order data; and a billing input means for inputting billing data including a billing number, a billing date, a planned billing date, a billing issue pattern code, and a billing amount based on the sales data.

[0007] Further, according to one aspect of the present invention, when the product code of the order data is set as the target of the line ID in the product master, the internal line key may be numbered by combining the minimum line number among the same order number, the same base number, and the same product code with the order number.

[0008] Further, according to one aspect of the present invention, when the product code of the order data is set outside the target of the line ID in the product master and the line ID aggregation destination code is set, the internal line key may be set to the same one as the internal line key with the same order number, the same base number, and product code = line ID aggregation destination code.

[0009] Further, according to one aspect of the present invention, when the usage-based billing code is set in the product master for the product code of the order data, the order quantity and the usage-based billing calculation master are used to calculate the usage-based billing and calculate the received order quantity and the received order amount, and the record of the order data is specified from the order number and the order line number of the order data, and the received order quantity and the received order amount may be updated.

[0010] Further, according to one aspect of the present invention, the usage-based billing calculation may include the calculation of quantity update (range unit price), which is a calculation method in which the unit price used for amount calculation is determined to be one according to the quantity, or the calculation of quantity update (accumulated unit price), which is a method in which a plurality of unit prices used for amount calculation are adopted step by step and calculated individually according to the quantity.

[0011] Further, in order to solve the above-described problems and achieve the object, the present invention is a line service management method executed by an information processing apparatus including a control unit, wherein the control unit includes an invoice issuance pattern master in which a contractor code, an invoice issuance pattern code, and a pattern name are associated and registered, and A product master in which a product code, product name, whether it is a target for line ID, line ID aggregation destination code, and metered charge code are registered in association with each other, and a metered charge calculation master in which a metered charge calculation code, SEQ, metered charge calculation name, calculation classification code, calculation classification name, surcharge rate, quantity, and unit price are registered in association with each other, are configured to be accessible. A contract input step of inputting order data including an order number, contract name, order line number, product code, base, invoice issuance pattern code, sales planned date, order quantity, and order amount, which is executed in the control unit; an order input step of inputting order data including a purchase order number, purchase order name, purchase order line number, product code, base, line internal key, line ID, line billing number, purchase planned date, purchase order quantity, purchase order amount, order number, and order line number based on the order data; a line ID cooperation step of obtaining a line ID corresponding to the line internal key of the order data in cooperation with a line carrier and updating the line ID of the order data; a billing data reception step of taking in carrier billing data including a purchase planned date, line ID, line billing number, purchase order quantity, and purchase order amount in cooperation with a line carrier and updating the line billing number, purchase order quantity, and purchase order amount of the order data based on the line ID and purchase planned date of the carrier billing data; a purchase input step of inputting purchase data including a purchase number, purchase line number, purchase order number, purchase order line number, purchase date, payment planned date, purchase amount, and line billing number based on the order data; A payment input step of inputting payment data including a payment number, payment date, payment planned date, purchase number, purchase line number, payment amount, and line billing number based on the purchase data; a sales input step of inputting sales data including a sales order number, sales line number, sales date, sales planned date, billing planned date, order number, order line number, invoice issuance pattern code, and order amount based on the order data; a billing input step of inputting billing data including a billing number, billing date, billing planned date, invoice issuance pattern code, and billing amount based on the sales data, characterized by including these steps.

[0012] Also, in order to solve the above-described problems and achieve the object, the present invention is a line service management program for causing an information processing apparatus including a control unit to execute, wherein the control unit is configured to access a billing pattern master in which a contractor code, a billing issue pattern code, and a pattern name are registered in association with each other, a product master in which a product code, a product name, whether it is a line ID target, a line ID aggregation destination code, and a metered charge code are registered in association with each other, and a metered charge calculation master in which a metered charge calculation code, SEQ, a metered charge calculation name, a calculation classification code, a calculation classification name, a surcharge rate, a quantity, and a unit price are registered in association with each other. The control unit includes a contract input step of inputting order receiving data including an order receiving number, a contract name, an order receiving line number, a product code, a base, a billing issue pattern code, a sales scheduled date, an order receiving quantity, and an order receiving amount, an order placement input step of inputting order placement data including an order placement number, an order placement name, an order placement line number, a product code, a base, a line internal key, a line ID, a line billing number, a purchase scheduled date, an order placement quantity, an order placement amount, an order receiving number, and an order receiving line number based on the order receiving data, a line ID cooperation step of obtaining a line ID corresponding to the line internal key of the order placement data in cooperation with a line carrier and updating the line ID of the order placement data, a billing data receiving step of capturing carrier billing data including a purchase scheduled date, a line ID, a line billing number, an order placement quantity, and an order placement amount in cooperation with a line carrier, and updating the line billing number, the order placement quantity, and the order placement amount of the order placement data based on the line ID and the purchase scheduled date of the carrier billing data, a purchase input step of inputting purchase data including a purchase number, a purchase line number, an order placement number, an order placement line number, a purchase date, a payment scheduled date, a purchase amount, and a line billing number based on the order placement data, a payment input step of inputting payment data including a payment number, a payment date, a payment scheduled date, a purchase number, a purchase line number, a payment amount, and a line billing number based on the purchase data, a sales input step of inputting sales data including a sales number, a sales line number, a sales date, a sales scheduled date, a billing scheduled date, an order receiving number, an order receiving line number, a billing issue pattern code, and an order receiving amount based on the order receiving data, and a billing input step of inputting billing data including a billing number, a billing date, a billing scheduled date, a billing issue pattern code, and a billing amount based on the sales data. The present invention is characterized by being a line service management program for causing the above steps to be executed.

Effect of the Invention

[0013] According to the present invention, when providing a line service, regardless of the management granularity of different lines, SIMs, etc. for each line carrier, while taking in the billing data from each carrier, it is possible to realize complex billing management for end-users without omission.

Brief Description of the Drawings

[0014]

Figure 1

Figure 2

Figure 3

Figure 4A

Figure 4B

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

[0015] Embodiments of a line service management apparatus, a line service management method, and a line service management program according to the present invention will be described in detail below with reference to the drawings. Note that the present invention is not limited to the present embodiment.

[0016] [1. Overview] The overview of the present invention will be described in the order of [1-1. Problem], [1-2. Solution], [1-3. Effect], and [1-4. Explanation of Terms and Management Indicators].

[0017] [1-1. Problem] FIG. 1 shows an example of a relationship diagram of a line-related service provider. A line-related service provider provides line-related services to end users via a contract partner by borrowing lines or SIMs of a line carrier.

[0018] Service providers related to lines have different lines and SIMs for each line carrier. In terms of the management forms and operations of conventional contract management, billing management, and payment management, they cannot absorb the differences in the management granularity of each aspect, and since the business processing timings are scattered, management becomes complex, and it is impossible to manage in a linked manner. There are problems such as risks leading to processing omissions in each business. In this embodiment, service providers related to lines can process complex billing management for end-users without omission while importing billing data from each carrier, regardless of the management granularity of different lines and SIMs for each line carrier.

[0019] [1-2. Solution] In this embodiment, on the selling side, the billing pattern master and management granularity such as sales and billing to be included in the contract information, the detailed order and procurement information managed on the buying side, and the matching information of the billing data from each carrier are linked so as to exceed the differences in the management granularity. FIG. 2 is a diagram for explaining the outline of the mechanism of this embodiment.

[0020] [1-3. Effects] · In contract conclusion and new service provision, it has become possible to manage the order, procurement, and payment operations for each line carrier, and the contract and billing management for each contract partner and end-user while treating them as products in the same category without being aware of the differences in line carriers. · Even with differences in the management granularity for each line carrier, it has become possible to calculate the usage-based charges from the procurement information for the carrier and perform sales recording and billing management for the contract partner and end-user.

[0021] [1-4. Explanation of Terms and Management Indicators The terms and management indicators used in this specification and drawings are as follows.

[0022] · Carrier... A line carrier company. A company that provides network lines, mobile phones, mobile routers, etc. · Line... Network lines, SIMs, etc. ·OP (Option)···Optional services associated with basic services such as network lines and SIMs. VPN options, bandwidth expansion options, accompanying work for line installation work and on-site surveys, etc. ·Line ID···Unique identification ID for each network line and SIM. The numbering system varies by carrier. ·Line Billing Number···Billing detail number sent by the carrier at the time of billing according to the line's charging and fee system. The numbering system varies by carrier. ·Invoice Issuance Pattern Master···Master used for the output unit and distribution of invoices. ·Usage-Based Billing Calculation···Calculate the seller's sales amount, etc. according to the buyer's purchase amount and quantity. ·Quantity Update (Range Unit Price)···Calculation method in which the unit price used for amount calculation is fixed according to the quantity. When it is less than 0 - 00 pieces @ 50 yen, 60 pieces are purchased → @ 50 yen × 60 pieces = 3000 yen ·Quantity Update (Cumulative Unit Price)···Method in which multiple unit prices are adopted step by step and calculated individually according to the quantity for amount calculation. When it is less than 0 - 100 pieces @ 50 yen and 100 pieces - @ 40 yen, 110 pieces are purchased → @ 50 yen × 100 pieces + @ 40 yen × 10 pieces = 5400 yen

[0023] The line service management device of the present invention is widely applicable to companies providing procurement and related services of line carriers, such as infrastructure service industries such as line services, IT communication industries, IT trading companies, etc., and general ledger-based solutions.

[0024] [2. Configuration] An example of the configuration of the line service management device according to the present embodiment will be described with reference to FIG. 3 and the like. The line service management device according to the present embodiment can be preferably used in, for example, real estate management companies (including PM companies). FIG. 3 is a block diagram showing an example of the configuration of the line service management device 100 according to the present embodiment. FIGS. 4A and 4B are diagrams for explaining the master configuration.

[0025] The line service management device 100 is a commercially available desktop personal computer. Note that the line service management device 100 is not limited to a stationary information processing device such as a desktop personal computer, and may be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), smartphone, or tablet personal computer.

[0026] The line service management device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each unit included in the line service management device 100 is communicably connected via an arbitrary communication path.

[0027] The communication interface unit 104 communicably connects the line service management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via a communication line. Here, the network 300 has a function of communicably connecting the line service management device 100 and a server 200 or a system of a line carrier (not shown), and is, for example, the Internet or a LAN (Local Area Network).

[0028] An input device 112 and an output device 114 are connected to the input / output interface unit 108. As the output device 114, in addition to a monitor (including a home television), a speaker or a printer can be used. As the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that cooperates with the mouse to realize a pointing device function can be used. Hereinafter, the output device 114 may be described as the monitor 114, and the input device 112 may be described as the keyboard 112 or the mouse 112. Also, displaying information on the monitor 114 and the user operating the input device 112, etc. may be described as "user operation via the UI".

[0029] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 records a computer program for giving instructions to the CPU (Central Processing Unit) to perform various processes in cooperation with the OS (Operating System). As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc. can be used.

[0030] The storage unit 106 stores a customer master 106a, an invoice issuance pattern master 106b, an end-user master 106c, a base master 106d, a product master 106e, a unit price billing master 106f, a unit price billing calculation master 106g, an order receiving table, an order issuing table, a purchase table, a payment table, a sales table, an invoice table, etc.

[0031] As shown in FIG. 4A, the customer master 106a can be composed of a table etc. that registers by associating a customer code and a customer name. In the example shown in the figure, the first row has a customer code of "CPS01" and a customer name of "Company A".

[0032] As shown in FIG. 4A, the invoice issuance pattern master 106b can be composed of a table etc. that registers by associating a customer code, an invoice issuance pattern code, and a pattern name. In the example shown in the figure, the first row has a customer code of "CPS01", an invoice issuance pattern code of "SP01", and a pattern name of "Fixed Amount Billing A".

[0033] As shown in FIG. 4A, the end-user master 106c can be composed of a table etc. that registers by associating an end-user code and an end-user name. In the example shown in the figure, the first row has an end-user code of "CPE01" and an end-user name of "Company Z".

[0034] As shown in Fig. 4A, the site master 106d can be composed of a table or the like that registers by associating an end-user code, a site code, and a site name. In the example shown in the figure, the first row has an end-user code of "CPE01", a site code of "KY001", and a site name of "Tokyo".

[0035] As shown in Fig. 4B, the product master 106e can be composed of a table or the like that registers by associating a product code, a product name, a line ID target, a line ID aggregation destination code, a usage-based billing code, and a usage-based billing calculation code. In the example shown in the figure, the first row has a product code of "S01", a product name of "Line A", a line ID target of "Target", a line ID aggregation destination code of "-", a usage-based billing code of "-", and a usage-based billing calculation code of "-".

[0036] As shown in Fig. 4B, the usage-based billing master 106f can be composed of a table or the like that registers by associating a usage-based billing code and a usage-based billing name. In the example shown in the figure, the first row has a usage-based billing code of "JR01" and a usage-based billing name of "Line Usage Amount Update".

[0037] As shown in Fig. 4B, the usage-based billing calculation master 106g can be composed of a table or the like that registers by associating a usage-based billing calculation code, SEQ, a usage-based billing calculation name, a calculation classification code, a calculation classification name, a surcharge rate, a quantity, and a unit price. In the example shown in the figure, the first row has a usage-based billing calculation code of "JK01", SEQ of "0", a usage-based billing calculation name of "Amount Update", a calculation classification code of "K1", a calculation classification name of "Amount Update", a surcharge rate of "0", a quantity of "-", and a unit price of "-".

[0038] The order receipt table is a table for registering order receipt (contract) data. The order receipt data may include an order receipt number, a contract name, an order receipt line number, a product code, a product name, a site code, a site name, an invoice issuance pattern code, a sales scheduled date, an order receipt quantity, and an order receipt amount. Since the content of the contract is received, the contract data and the order receipt data are synonymous.

[0039] The order table is a table for registering order data. The order data may include an order number, an order name, an order line number, a product code, a product name, a base code, a base name, an internal line key, a line ID, a line billing number, a scheduled purchase date, an order quantity, an order amount, a received order number, and a received order line number.

[0040] The purchase table is a table for registering purchase data. The purchase data may include a purchase number, a purchase line number, an order number, an order line number, a purchase date, a scheduled payment date, a purchase amount, and a line billing number.

[0041] The payment table is a table for registering payment data. The payment data may include a payment number, a payment date, a scheduled payment date, a purchase number, a purchase line number, a payment amount, and a line billing number.

[0042] The sales table is a table for registering sales data. The sales data may include a sales number, a sales line number, a sales date, a scheduled sales date, a scheduled billing date, a received order number, a received order line number, a billing pattern code, and a received order amount.

[0043] The billing table is a table for registering billing data. The billing data may include a billing number, a billing date, a scheduled billing date, a billing pattern code, and a billing amount.

[0044] The control unit 102 is a CPU or the like that comprehensively controls the line service management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processes based on these stored programs.

[0045] The control unit 102 is configured to be able to access the contract partner master 106a, the invoice issuance pattern master 106b, the end user master 106c, the base master 106d, the product master 106e, the metered billing master 106f, the metered billing calculation master 106g, the order receiving table, the order issuing table, the procurement table, the payment table, the sales table, the invoice table, etc. stored in the storage unit 106. Note that the contract partner master 106a, the invoice issuance pattern master 106b, the end user master 106c, the base master 106d, the product master 106e, the metered billing master 106f, the metered billing calculation master 106g, the order receiving table, the order issuing table, the payment table, the sales table, the invoice table, etc. may be provided in another location (for example, the server 200), as long as the control unit 102 can access them.

[0046] Functionally conceptually, the control unit 102 includes a contract input unit 102a, an order issuing input unit 102b, a line ID cooperation unit 102c, a billing data receiving unit 102d, a procurement input unit 102e, a payment input unit 102f, a sales input unit 102g, a billing input unit 102h, a master maintenance unit 102i, and a screen display control unit 102j.

[0047] The contract input unit 102a inputs order receiving data (contract data) including the order receiving number, contract name, order receiving line number, product code, product name, base code, base name, invoice issuance pattern code, planned sales date, order receiving quantity, and order receiving amount, in response to operations of an operator on a contract input screen (not shown) displayed on the monitor 114, for example, and registers it in the order receiving table.

[0048] The order issuing input unit 102b inputs order issuing data including the order issuing number, order issuing name, order issuing line number, product code, product name, base code, base name, internal line key, line ID, line billing number, planned procurement date, order issuing quantity, order issuing amount, order receiving number, and order receiving line number, based on the order receiving data, in response to operations of an operator on an order issuing input screen (not shown) displayed on the monitor 114, for example, and registers it in the order issuing table.

[0049] Also, when the product code in the order data is set as the target of the line ID in the product master 106e, the internal line key may be numbered by combining the smallest line number among the same order number, the same base number, and the same product code with the order number.

[0050] Also, when the product code in the order data is set outside the target of the line ID in the product master and the line ID aggregation destination code is set, the same internal line key as that of the same order number, the same base number, and product code = line ID aggregation destination code may be set.

[0051] The line ID linkage unit 102c links with the line carrier (system) to obtain the line ID corresponding to the internal line key of the order data and updates the line ID of the order data.

[0052] The claim data reception unit 102d links with the line carrier (system) to take in the carrier claim data including the planned purchase date, line ID, line claim number, order quantity, and order amount, and updates the line claim number, order quantity, and order amount of the order data based on the line ID, planned purchase date, and line claim number of the carrier claim data.

[0053] Also, when the per - volume charging code is set in the product master 106e for the product code of the order data, the claim data reception unit 102d may perform per - volume charging calculation based on the order quantity and the per - volume charging calculation master 106g to calculate the received order quantity and received order amount, specify the record of the received order data from the received order number and received order line number of the order data, and update the received order quantity and received order amount.

[0054] Also, the per - volume charging calculation may include the calculation of quantity update (range unit price), which is a calculation method where the unit price used for amount calculation is determined to be one according to the quantity, or the calculation of quantity update (accumulated unit price), which is a method where multiple unit prices used for amount calculation are adopted step - by - step and calculated individually according to the quantity.

[0055] The purchase input section 102e inputs purchase data including a purchase number, a purchase line number, an order number, an order line number, a purchase date, a scheduled payment date, a purchase amount, and a line billing number based on order data in response to an operator's operation on a purchase input screen (not shown) displayed on the monitor 114, etc., and registers it in the purchase table.

[0056] The payment input section 102f inputs payment data including a payment number, a payment date, a scheduled payment date, a purchase number, a purchase line number, a payment amount, and a line billing number based on the purchase data in response to an operator's operation on a payment input screen (not shown) displayed on the monitor 114, etc., and registers it in the payment table.

[0057] The sales input section 102g inputs sales data including an order sales number, a sales line number, a sales date, a scheduled sales date, a scheduled billing date, an order number, an order line number, a billing pattern code, and an order amount based on the order received data in response to an operator's operation on a sales input screen (not shown) displayed on the monitor 114, etc., and registers it in the sales table.

[0058] The billing input section 102h inputs billing data including a billing number, a billing date, a scheduled billing date, a billing pattern code, and a billing amount based on the sales data in response to an operator's operation on a billing input screen (not shown) displayed on the monitor 114, etc., and registers it in the billing table.

[0059] The master maintenance section 102i edits the contract partner master 106a, the billing pattern master 106b, the end user master 106c, the base master 106d, the product master 106e, the metered billing master 106f, and the metered billing calculation master 106g, such as registering, updating, adding, and deleting data, in response to an operator's operation on a master maintenance screen (not shown) displayed on the monitor 114, etc.

[0060] The screen display control section 102j controls the display and input of various screens (e.g., master maintenance screen, order received input screen, order placed input screen, purchase input screen, payment input screen, sales input screen, billing input screen, etc.) to be displayed on the monitor 114.

[0061] [3. Specific Example] With reference to FIGS. 1 to 15, a specific example of the processing of the control unit 102 of the line service management apparatus 100 in the present embodiment will be described. FIGS. 5 to 15 are diagrams for explaining a specific example of the processing of the control unit 102 of the line service management apparatus 100 in the present embodiment.

[0062] [3-1. Overall Processing] FIG. 5 is a diagram showing a business flow. As shown in FIG. 5, the business is processed in the order of order receipt → order placement → line arrangement (line ID numbering → line activation → line ID linkage) → receiving billing data from the line carrier (receiving line carrier billing data → purchase input → payment processing) → sales input → billing processing.

[0063] FIG. 6 is a diagram showing a flow for explaining an overview of the overall processing of the control unit 102 of the line service management apparatus 100 in the present embodiment. With reference to FIG. 12, an overview of the overall processing of the control unit 102 of the line service management apparatus 100 in the present embodiment will be described.

[0064] In FIG. 6, the contract input unit 102a executes a contract input process (step S1). Specifically, in the contract input process, the contract input unit 102a inputs order data (contract data) including an order number, contract name, order line number, product code, product name, base code, base name, invoice issuance pattern code, planned sales date, order quantity, and order amount in response to, for example, an operator's operation on a contract input screen (not shown) displayed on the monitor 114, and registers it in the order table.

[0065] The order injection input unit 102b executes order injection input processing (step S2). Specifically, in the order injection input processing, the order injection input unit 102b inputs order data including an order number, order name, order line number, product code, product name, base code, base name, line internal key, line ID, line billing number, planned purchase date, order quantity, order amount, order receipt number, and order receipt line number based on the order receipt data in response to, for example, an operator's operation on an order injection input screen (not shown) displayed on the monitor 114, and registers it in the order table. Also, when the product code of the order data is set as the line ID target of the product master 106e, the line internal key may be numbered by combining the smallest line number among the same order number, the same base number, and the same product code with the order number. Further, when the product code of the order data is set outside the line ID target of the product master and the line ID aggregation destination code is set, the same line internal key as that of the same order number, the same base number, and product code = line ID aggregation destination code may be set for the line internal key.

[0066] The line ID cooperation unit 102c executes line ID connection processing (step S3). Specifically, the line ID cooperation unit 102c cooperates with the line carrier (system) to acquire the line ID corresponding to the line internal key of the order data and updates the line ID of the order data. Thereby, the line is opened.

[0067] The claim data receiving unit 102d executes a claim data receiving process (step S4). Specifically, in the claim data receiving process, the claim data receiving unit 102d cooperates with a line carrier (system) to capture carrier claim data including the scheduled purchase date, line ID, line claim number, order quantity, and order amount, and updates the line claim number, order quantity, and order amount of the order data based on the line ID, scheduled purchase date, and line claim number of the carrier claim data. Further, when the per-unit billing code is set in the product master 106e for the product code of the order data, the claim data receiving unit 102d may perform a per-unit billing calculation based on the order quantity and the per-unit billing calculation master 106g to calculate the received order quantity and received order amount, identify the record of the received order data from the received order number and received order line number of the order data, and update the received order quantity and received order amount. The per-unit billing calculation may include a calculation of quantity update (range unit price) which is a calculation method where the unit price used for amount calculation is determined uniquely according to the quantity, or a calculation of quantity update (accumulated unit price) which is a method where a plurality of unit prices used for amount calculation are adopted step by step and calculated individually according to the quantity.

[0068] The purchase input unit 102e executes a purchase input process (step S5). Specifically, in the purchase input process, the purchase input unit 102e inputs purchase data including the purchase number, purchase line number, order number, order line number, purchase date, scheduled payment date, purchase amount, and line claim number based on the order data in response to an operator's operation on a purchase input screen (not shown) displayed on the monitor 114, for example, and registers it in the purchase table.

[0069] The payment input unit 102f executes a payment input process (step S6). Specifically, in the payment input process, the payment input unit 102f inputs payment data including the payment number, payment date, scheduled payment date, purchase number, purchase line number, payment amount, and line claim number based on the purchase data in response to an operator's operation on a payment input screen (not shown) displayed on the monitor 114, for example, and registers it in the payment table.

[0070] The sales input unit 102g executes a sales input process (step S7). Specifically, in the sales input process, the sales input unit 102g inputs sales data including an order receipt sales number, a sales line number, a sales date, a scheduled sales date, a scheduled billing date, an order receipt number, an order receipt line number, a billing pattern code, and an order receipt amount based on the order receipt data in response to an operator's operation on a sales input screen (not shown) displayed on the monitor 114, for example, and registers the data in a sales table.

[0071] The billing input unit 102h executes a billing input process (step S8). Specifically, in the billing input process, the billing input unit 102h inputs billing data including a billing number, a billing date, a scheduled billing date, a billing pattern code, and a billing amount based on the sales data in response to an operator's operation on a billing input screen (not shown) displayed on the monitor 114, for example, and registers the data in a billing table.

[0072] [3-2. Sample Data] Figs. 7 to 15 are diagrams showing sample data for explaining a specific example of the processing of the control unit 102 of the line service management apparatus 100 in the present embodiment. With reference to Figs. 7 to 15, a specific example of the processing of the control unit 102 of the line service management apparatus 100 in the present embodiment will be described. Hereinafter, an example in which the data of the masters in Figs. 4A and 4B are registered in advance and these masters are used will be described.

[0073] In the following description, what the operator inputs on the input screen is denoted as "input", and what the control unit 102 automatically processes is denoted as "automatic".

[0074] (S1: Contract Input Process) Fig. 7 is a diagram for explaining a specific example of the contract input process. In the contract input process, order receipt data (contract data) is input and registered in an order receipt table. Contract = Order receipt.

[0075] The order input section 102a inputs order data (contract data) including the order number, contract name, order line number, product code, product name, base code, base name, invoice issuance pattern code, scheduled sales date, ordered quantity, and ordered amount in response to, for example, an operator's operation on an order input screen (not shown) displayed on the monitor 114, and registers it in the order table.

[0076] Figure 7 shows an example of the order data registered in the order table. The order data has items of order number, contract name, order line number, product code, product name, base code, base name, invoice issuance pattern code, scheduled sales date, ordered quantity, and ordered amount.

[0077] In the example shown in the figure, the first line has the order number "JUC001", contract name "Laying work", order line number "1", product code "S01", product name "Line A", base code "KY001", base name "Tokyo", invoice issuance pattern code "SP01", scheduled sales date "1 / 31", ordered quantity "1", and ordered amount "200 yen".

[0078] (S2: Purchase order input process) With reference to Figure 8, a specific example of the purchase order input process will be described. In the purchase order input process, purchase order data is input and registered in the purchase order table.

[0079] The purchase order input section 102b inputs purchase order data including the purchase order number, purchase order name, purchase order line number, product code, product name, base code, base name, internal line key, line ID, line invoice number, scheduled purchase date, purchase order quantity, purchase order amount, order number, and order line number based on the order data in response to, for example, an operator's operation on a purchase order input screen (not shown) displayed on the monitor 114, and registers it in the purchase order table.

[0080] FIG. 8(A) shows a configuration example of the product master 106e. FIG. 8(B) shows a data example of the order data registered in the order table. The order data includes items such as order number, order name, order line number, product code, product name, base code, base name, line internal key, line ID, line billing number, scheduled purchase date, order quantity, order amount, received order number, and received order line number. In the example shown in the figure, the first line has an order number of "HAC001", an order name of "○○ line arrangement", an order line number of "1", a product code of "S01", a product name of "Line A", a base code of "KY001", a base name of "Tokyo", a line internal key of "HAC001-1", a line ID of "", a line billing number of "", a scheduled purchase date of "1 / 31", an order quantity of "1", an order amount of "100 yen", a received order number of "JUC001", and a received order line number of "1".

[0081] The "line internal key" is set as follows. (1) At the time of ordering, number the line internal key under the following conditions. · The same order number · The same base number · The same product code (limited to the line ID target of the product master 106e) Number it in combination with the order number as the smallest line number among them (because one order does not necessarily mean one commodity).

[0082] (2) At the time of ordering, when the line ID of the product master 106e is "excluded" and the line ID aggregation destination code is set, set the line internal key under the following conditions. · The same order number · The same base number · Product code = line ID aggregation destination code Set the same as the line internal key of (for OP etc. attached to the line).

[0083] (S3: Line ID linkage process) Referring to FIG. 9, a specific example of the line ID linkage process will be described. In the line ID linkage process, in cooperation with the line carrier (system), a line ID linkage data file in which the line ID corresponding to the line internal key of the order data is described is acquired, and the "line ID" of the order data is updated.

[0084] The line ID cooperation unit 102c cooperates with the line carrier (system) to obtain the line ID corresponding to the internal line key of the order data and update the line ID of the order data.

[0085] FIG. 9(A) shows an example of the data in the line ID cooperation data file. The line ID cooperation data file includes the internal line key and the line ID. In the example shown in the figure, the first row is the internal line key "HAC001-1" and the line ID "A001".

[0086] FIG. 9(B) shows an example of the order table after the update of the "line ID". The "line ID" for the "internal line key" is updated in the line ID cooperation. In the example shown in the figure, in the first row, the line ID "A001" has been updated for the internal line key "HAC001-1".

[0087] (S4: Order data receiving process) Referring to FIGS. 10 to 12, a specific example of the order data receiving process will be described. The order data receiving unit 102d cooperates with the line carrier (system) to import the carrier order data including the planned purchase date, line ID, line invoice number, order quantity, and order amount, and based on the line ID, planned purchase date, and line invoice number of the carrier order data, update the line invoice number, order quantity, and order amount of the order data. In addition, when the per-volume billing code is set in the product master 106e for the product code of the order data, the order data receiving unit 102d performs a per-volume billing calculation based on the order quantity and the per-volume billing calculation master 106g to calculate the received order quantity and received order amount, specifies the record of the received order data from the received order number and received order line number of the order data, and updates the received order quantity and received order amount.

[0088] Figure 10(A) is a diagram showing an example of a carrier billing data file. The carrier billing data file includes items such as the scheduled purchase date, line ID, line billing number, ordered quantity, and ordered amount. In the example shown in the figure, the first row shows the scheduled purchase date "1 / 31", line ID "A001", line billing number "SE-A001", ordered quantity "1", and ordered amount "90 yen".

[0089] Figure 10(B) shows an example of the updated order table. In the carrier billing data linkage, based on the "line ID", "scheduled purchase date", and "line billing number" in the carrier billing data file, the "ordered amount", "line billing number", and "ordered quantity" in the order table are updated. Note that due to carrier reasons, OP is billed together for the basic lines.

[0090] Figure 11 shows a configuration example of the product master 106e, metered billing master 106f, and metered billing calculation master 106g. Figure 12 shows an example of the updated order receipt table.

[0091] Using the product code of the order data as the key, when the metered billing code is set in the product master 106e, metered billing calculation is performed based on the ordered quantity and the metered billing calculation master 106g to calculate the order receipt quantity and order receipt amount. The record of the order receipt data is specified from the order receipt number and order receipt line number of the order data, and the order receipt quantity and order receipt amount are updated. In the metered billing calculation, calculations such as quantity update (range unit price) and quantity update (accumulated unit price) are performed. Specifically, it is as follows.

[0092] (1) Based on the product code, perform the metered calculation of "quantity update (range unit price)". Refer to the order receipt table from the order receipt number and order receipt line number, and update it to the ordered quantity and the order receipt quantity and order receipt amount calculated from the metered billing calculation master 106g.

[0093] In this example, the third line of the order data shows a product code of "S04", an order quantity of "15", and an order amount of "150 yen". Since the order quantity is "15" and the per-unit billing calculation code in the product master 106e is "JK03", the record on the fourth line of the per-unit billing calculation master 106g is used. For the quantity update (range unit price), since it is 10 to less than 20 units @ 11 yen, it is @ 11 yen × 15 units = 165 yen. As shown in the third line of the order receipt data shown in Figure 12, the order receipt quantity is updated to "15" and the order receipt amount is updated to "165 yen".

[0094] (2) Based on the product code, perform the per-unit calculation of "line usage quantity update (accumulated unit price)". Refer to the order receipt table from the order receipt number and order receipt line number, and update the order quantity and the order receipt quantity and amount calculated from the per-unit billing calculation master 106g.

[0095] In this example, the ninth line of the order data shows a product code of "S05", an order quantity of "15", and an order amount of "120 yen". Since the order quantity is "15" and the per-unit billing calculation code in the product master 106e is "JK04", the records on the sixth and seventh lines of the per-unit billing calculation master 106g are used. For the quantity update (accumulated unit price), in the case of 0 to less than 10 units @ 20 yen and 10 to less than 20 units @ 15 yen, it is @ 20 yen × 10 units + @ 15 yen × 5 units = 275 yen. As shown in the ninth line of the order receipt data shown in Figure 12, the order receipt quantity is updated to "15" and the order receipt amount is updated to "275 yen".

[0096] (S5: Procurement Input Processing) Referring to Figure 13, a specific example of the procurement input processing will be described. In the procurement input processing, procurement data is input and registered in the procurement table. The payment input section 102f inputs payment data including a payment number, payment date, scheduled payment date, procurement number, procurement line number, payment amount, and line billing number into the payment table based on the procurement data in response to, for example, an operator's operation on a payment input screen (not shown) displayed on the monitor 114.

[0097] The upper part of FIG. 13 shows a data example of purchase data registered in the purchase table. The purchase data includes items such as a purchase number, a purchase line number, an order number, an order line number, a purchase date, a scheduled payment date, a purchase amount, and a line billing number. In the example shown in the figure, the first row shows a purchase number of "SII001", a purchase line number of "1", an order number of "HAC001", an order line number of "1", a purchase date of "1 / 31", a scheduled payment date of "2 / 28", a purchase amount of "90 yen", and a line billing number of "SE-A001".

[0098] Note that even for the same carrier and the same product, there are cases where payments need to be separated. Therefore, the line billing number is specified so that the scheduled payment date and payments can be separated.

[0099] (S6: Payment Input Processing) Referring to FIG. 13, a specific example of the payment input processing will be described. In the payment input processing, payment data is input and registered in the payment table. The payment input unit 102f inputs, for example, payment data including a payment number, a payment date, a scheduled payment date, a purchase number, a purchase line number, a payment amount, and a line billing number based on the purchase data in response to an operator's operation on a payment input screen (not shown) displayed on the monitor 114, and registers it in the payment table.

[0100] The lower part of FIG. 13 shows a data example of payment data registered in the payment table. The payment data includes items such as a payment number, a payment date, a scheduled payment date, a purchase number, a purchase line number, a payment amount, and a line billing number. In the example shown in the figure, the first row shows a payment number of "SHA001", a payment date of "2 / 28", a scheduled payment date of "2 / 28", a purchase number of "SII001", a purchase line number of "1", a payment amount of "90 yen", and a line billing number of "SE-A001".

[0101] (S14: Sales Input Processing) Referring to FIG. 14, a specific example of the sales input process will be described. In the sales input process, sales data is input and registered in the sales table. The sales input unit 102g inputs, for example, sales data including the order sales number, sales line number, sales date, scheduled sales date, scheduled billing date, order number, order line number, invoice issuance pattern code, and order amount based on the order data in response to an operator's operation on a sales input screen (not shown) displayed on the monitor 114, and registers it in the sales table.

[0102] FIG. 14 is a diagram showing a data example of the sales data registered in the sales table. The sales data has items of sales number, sales line number, sales date, scheduled sales date, scheduled billing date, order number, order line number, invoice issuance pattern code, and order amount. In the example shown in the figure, the first row has a sales number of "URI001", a sales line number of "1", a sales date of "1 / 31", a scheduled sales date of "1 / 31", a scheduled billing date of "2 / 5", an order number of "JUC001", an order line number of "1", an invoice issuance pattern code of "SP01", and an order amount of "200 yen". Note that it is also possible to change the invoice issuance pattern during the sales process immediately before billing. This is to enable handling of requests for separate invoicing.

[0103] (S8: Billing Input Process) Referring to FIG. 15, a specific example of the billing input process will be described. In the billing input process, billing data is input and registered in the billing table. The billing input unit 102h inputs, for example, billing data including the billing number, billing date, scheduled billing date, invoice issuance pattern code, and billing amount based on the sales data in response to an operator's operation on a billing input screen (not shown) displayed on the monitor 114, and registers it in the billing table.

[0104] FIG. 15 is a diagram showing a data example of the billing data registered in the billing table. The billing data has items of billing number, billing date, scheduled billing date, invoice issuance pattern code, and billing amount. In the example shown in the figure, the first row has a billing number of "SEI001", a billing date of "2 / 5", a scheduled billing date of "2 / 5", an invoice issuance pattern code of "SP01", and a billing amount of "200 yen".

[0105] As described above, according to this embodiment, an invoice issuance pattern master 106b in which a contractor code, an invoice issuance pattern code, and a pattern name are registered in association with each other, a product master 106e in which a product code, a product name, whether it is a line ID target, a line ID aggregation destination code, and a volume-based charge code are registered in association with each other, a volume-based charge calculation master 106g in which a volume-based charge calculation code, SEQ, a volume-based charge calculation name, a calculation classification code, a calculation classification name, a surcharge rate, a quantity, and a unit price are registered in association with each other, a contract input unit 102a for inputting order data including an order number, a contract name, an order line number, a product code, a base, an invoice issuance pattern code, a planned sales date, an ordered quantity, and an ordered amount, an order input unit 102b for inputting order data including a purchase order number, a purchase order name, a purchase order line number, a product code, a base, an internal line key, a line ID, a line invoice number, a planned purchase date, an ordered quantity, an ordered amount, an order number, and an order line number based on the order data, a line ID cooperation unit 102c for obtaining a line ID corresponding to the internal line key of the order data in cooperation with a line carrier and updating the line ID of the order data, a claim data receiving unit 102d for taking in carrier claim data including a planned purchase date, a line ID, a line invoice number, an ordered quantity, and an ordered amount in cooperation with a line carrier and updating the line invoice number, the ordered quantity, and the ordered amount of the order data based on the line ID and the planned purchase date of the carrier claim data, a purchase input unit 102e for inputting purchase data including a purchase order number, a purchase order line number, a purchase order number, a purchase order line number, a purchase date, a planned payment date, a purchase amount, and a line invoice number based on the order data, a payment input unit 102f for inputting payment data including a payment number, a payment date, a planned payment date, a purchase order number, a purchase order line number, a payment amount, and a line invoice number based on the purchase data, a sales input unit 102g for inputting sales data including a sales invoice number, a sales line number, a sales date, a planned sales date, a planned billing date, an order number, an order line number, an invoice issuance pattern code, and an ordered amount based on the order data, and a billing input unit 102h for inputting billing data including a billing number, a billing date, a planned billing date, an invoice issuance pattern code, and a billing amount based on the sales data. Therefore, when providing a line service, regardless of the management granularity of different lines, SIMs, etc. for each line carrier, it is possible to realize complex billing management for end users without omission while taking in billing data from each carrier.

[0106] [4. Contribution to the United Nations' Sustainable Development Goals (SDGs)] According to this embodiment, since it can contribute to improving business efficiency and making appropriate business judgments of enterprises, it is possible to contribute to Goals 8 and 9 of the SDGs.

[0107] Also, according to this embodiment, since it can contribute to reducing waste loss and promoting paperless and digitalization, it is possible to contribute to Goals 12, 13, and 15 of the SDGs.

[0108] Also, according to this embodiment, since it can contribute to strengthening control and governance, it is possible to contribute to Goal 16 of the SDGs.

[0109] [5. Other Embodiments] In addition to the above-described embodiments, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

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

[0111] Also, regarding the line service management device 100, each component shown in the drawings is a functional concept, and it is not necessarily physically configured as shown in the drawings.

[0112] Also, regarding the line service management device 100, each component shown in the drawings is a functional concept, and it is not necessarily physically configured as shown in the drawings.

[0113] For example, regarding the processing functions provided by the line service management apparatus 100, particularly each processing function performed by the control unit, all or any part thereof may be realized by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware by wired logic. Note that the program is recorded on a non-transitory computer-readable recording medium including programmed instructions for causing an information processing apparatus to execute the processing described in the present embodiment, and is mechanically read by the line service management apparatus 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or an HDD (Hard Disk Drive). This computer program is executed by being loaded into the RAM, and constitutes the control unit in cooperation with the CPU.

[0114] Further, this computer program may be stored in an application program server connected to the line service management apparatus 100 via an arbitrary network, and all or part thereof can be downloaded as necessary.

[0115] Also, a 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, this "recording medium" includes any "portable physical medium" such as a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile Disk), and a Blu-ray (registered trademark) Disc.

[0116] Also, the "program" is a data processing method described in any language or description method, and is not limited to a form such as source code or binary code. Note that the "program" is not necessarily limited to being configured singly, and also includes those that are distributedly configured as a plurality of modules or libraries, or those that achieve their functions in cooperation with another program represented by an OS. Regarding the specific configuration, reading procedure, and installation procedure after reading for reading the recording medium in each device shown in the embodiment, well-known configurations and procedures can be used.

[0117] Various databases and the like stored in the storage unit are storage means such as a memory device such as a RAM or a ROM, a fixed disk device such as a hard disk, a flexible disk, and an optical disk, and store various programs, tables, databases, and web page files used for various processes and website provision.

[0118] Further, the line service management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. Further, the line service management device 100 may be realized by installing software (including programs or data, etc.) for realizing the processing described in this embodiment in the device.

[0119] Furthermore, the specific form of the distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to various additions or according to the function load. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

Explanation of Signs

[0120] 100 Line service management device 102 Control unit 102a Contract input unit 102b Order input unit 102c Line ID cooperation unit 102d Billing data reception unit 102e Procurement input unit 102f Payment input unit 102g Sales input unit 102h Billing input unit 102i Master maintenance unit 102j Screen display control unit 104 Communication interface unit 106 Storage unit 106a Customer master 106b Invoice issuance pattern master 106c End user master 106d Base master 106e Product master 106f Usage-based billing master 106g Usage-based billing calculation master 108 Input / output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims

1. A line service management device that includes a control unit and provides a line service using a line of a line carrier, wherein the control unit is configured to be accessible to a billing pattern master that registers by associating a customer code, a billing issue pattern code, and a pattern name, a product master that registers by associating a product code, a product name, whether it is a line ID target, a line ID aggregation destination code, and a usage-based billing code, a usage-based billing calculation master that registers by associating a usage-based billing calculation code, a SEQ, a usage-based billing calculation name, a calculation classification code, a calculation classification name, a surcharge rate, a quantity, and a unit price, and is configured to be accessible to, contract input means for inputting order data including an order number, a contract name, an order line number, a product code, a base, a billing issue pattern code, a planned sales date, an order quantity, and an order amount, purchase order input means for inputting purchase order data including a purchase order number, a purchase order name, a purchase order line number, a product code, a base, a line internal key, a line ID, a line billing number, a planned purchase date, a purchase order quantity, a purchase order amount, an order number, and an order line number based on the order data, line ID cooperation means for obtaining a line ID corresponding to the line internal key of the purchase order data in cooperation with a line carrier and updating the line ID of the purchase order data, billing data reception means for taking in carrier billing data including a planned purchase date, a line ID, a line billing number, a purchase order quantity, and a purchase order amount in cooperation with a line carrier, and updating the line billing number, the purchase order quantity, and the purchase order amount of the purchase order data based on the line ID and the planned purchase date of the carrier billing data, purchase input means for inputting purchase data including a purchase number, a purchase line number, a purchase order number, a purchase order line number, a purchase date, a planned payment date, a purchase amount, and a line billing number based on the purchase order data, payment input means for inputting payment data including a payment number, a payment date, a planned payment date, a purchase number, a purchase line number, a payment amount, and a line billing number based on the purchase data, sales input means for inputting sales data including a sales order number, a sales line number, a sales date, a planned sales date, a planned billing date, an order number, an order line number, a billing issue pattern code, and an order amount based on the order data, billing input means for inputting billing data including a billing number, a billing date, a planned billing date, a billing issue pattern code, and a billing amount based on the sales data, A line service management device characterized by comprising the above.

2. When the product code of the order data is set as the target of the line ID in the product master, the internal line key numbers the smallest line number among the same order number, the same base number, and the same product code in combination with the order number. The line service management device according to claim 1, characterized in that.

3. When the product code of the order data is set outside the target of the line ID in the product master and the line ID aggregation destination code is set, the internal line key is set to the same as the internal line key with the same order number, the same base number, and product code = line ID aggregation destination code. The line service management device according to claim 1, characterized in that.

4. When the metered billing code is set in the product master for the product code of the order data, the order receiving data receiving means calculates the metered billing based on the order quantity and the metered billing calculation master to calculate the order receiving quantity and the order receiving amount, and specifies the record of the order receiving data from the order receiving number and the order receiving line number of the order data, and updates the order receiving quantity and the order receiving amount. The line service management device according to claim 1, characterized in that.

5. The metered billing calculation includes a calculation of quantity update (range unit price), which is a calculation method in which the unit price used for amount calculation is determined to be one according to the quantity, or a calculation of quantity update (accumulated unit price), which is a method in which a plurality of unit prices used for amount calculation are adopted step by step and calculated individually according to the quantity. The line service management device according to claim 4, characterized in that.

6. A line service management method executed by an information processing device provided with a control unit, The control unit is, A billing pattern master in which a contractor code, a billing pattern code, and a pattern name are registered in association with each other, A product master in which a product code, a product name, whether it is a line ID target, a line ID aggregation destination code, and a metered billing code are registered in association with each other, A metered billing calculation master in which a metered billing calculation code, SEQ, a metered billing calculation name, a calculation classification code, a calculation classification name, a surcharge rate, a quantity, and a unit price are registered in association with each other, Is configured to be accessible to, Executed in the control unit, A contract input step of inputting order receiving data including an order receiving number, a contract name, an order receiving line number, a product code, a base, a billing pattern code, a sales scheduled date, an order receiving quantity, and an order receiving amount, An order input step of inputting order data including an order number, order name, order line number, product code, base, line internal key, line ID, line billing number, scheduled purchase date, ordered quantity, ordered amount, order receipt number, and order receipt line number based on the order receipt data; A line ID linking step of obtaining a line ID corresponding to the line internal key of the order data in cooperation with a line carrier and updating the line ID of the order data; A billing data receiving step of importing carrier billing data including a scheduled purchase date, line ID, line billing number, ordered quantity, and ordered amount in cooperation with a line carrier, and updating the line billing number, ordered quantity, and ordered amount of the order data based on the line ID and scheduled purchase date of the carrier billing data; A purchase input step of inputting purchase data including a purchase number, purchase line number, order number, order line number, purchase date, scheduled payment date, purchase amount, and line billing number based on the order data; A payment input step of inputting payment data including a payment number, payment date, scheduled payment date, purchase number, purchase line number, payment amount, and line billing number based on the purchase data; A sales input step of inputting sales data including a sales invoice number, sales line number, sales date, scheduled sales date, scheduled billing date, order receipt number, order receipt line number, invoice issuance pattern code, and order receipt amount based on the order receipt data; An invoicing input step of inputting invoicing data including an invoice number, invoice date, scheduled billing date, invoice issuance pattern code, and invoice amount based on the sales data; A line service management method characterized by including the above.

7. A line service management program for causing an information processing apparatus provided with a control unit to execute, wherein the control unit is configured to be accessible to an invoice issuance pattern master in which a contract partner code, invoice issuance pattern code, and pattern name are associated and registered; a product master in which a product code, product name, whether it is a line ID target, line ID aggregation destination code, and unit price billing code are associated and registered; a unit price billing calculation master in which a unit price billing calculation code, SEQ, unit price billing calculation name, calculation classification code, calculation classification name, surcharge rate, quantity, and unit price are associated and registered; and is configured to be accessible to the above, and to the control unit, a contract input step of inputting order receipt data including an order receipt number, contract name, order receipt line number, product code, base, invoice issuance pattern code, scheduled sales date, order receipt quantity, and order receipt amount; An order input step of inputting order data including an order number, order name, order line number, product code, base, line internal key, line ID, line billing number, scheduled purchase date, order quantity, order amount, order receipt number, and order receipt line number based on the said order receipt data; A line ID cooperation step of obtaining the line ID corresponding to the line internal key of the said order data in cooperation with the line carrier and updating the line ID of the said order data; A billing data reception step of importing carrier billing data including the scheduled purchase date, line ID, line billing number, order quantity, and order amount in cooperation with the line carrier, and updating the line billing number, order quantity, and order amount of the said order data based on the line ID and scheduled purchase date of the said carrier billing data; A purchase input step of inputting purchase data including a purchase number, purchase line number, order number, order line number, purchase date, scheduled payment date, purchase amount, and line billing number based on the said order data; A payment input step of inputting payment data including a payment number, payment date, scheduled payment date, purchase number, purchase line number, payment amount, and line billing number based on the said purchase data; A sales input step of inputting sales data including a sales receipt number, sales line number, sales date, scheduled sales date, scheduled billing date, order receipt number, order receipt line number, invoice issuance pattern code, and order receipt amount based on the said order receipt data; An invoice input step of inputting invoice data including an invoice number, invoice date, scheduled invoice date, invoice issuance pattern code, and invoice amount based on the said sales data; A line service management program for executing the above.

Images