Royalty management apparatus, royalty management method, and royalty management program

Abstract

To quickly notify with a low work load when payment reservation of royalty payment occurs in a royalty distribution work.SOLUTION: A royalty management device is provided with a main distribution calculation processing means which calculates a distribution amount of a sales amount according to the distribution ratio of each distribution destination on the basis of sales data and a distribution setting table, creates calculation result confirmation data including a calculation statement NO, a sales number, a distribution destination, a distribution amount, and an original contract number, and creates payment schedule data including a payment number, a distribution destination, a calculation statement NO, a scheduled payment date, a payment amount, and a payment completion FLG indicating a payment completion or a payment incompletion on the basis of the calculation result confirmation data; a receipt application input means which applies a receipt application to the scheduled collection data when a scheduled collection amount is received; and a payment retention alert processing means which extracts a detailed statement of which the payment completion FLG is "incompletion" for the scheduled payment data before a reference date designated by an operator, and notifies an alert of payment retention.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a royalty management device, a royalty management method, and a royalty management program. [Background technology]

[0002] For example, in the content production and media industries, there is a royalty distribution business that distributes royalties associated with the use of content. Patent Document 1, for example, is an example of a system for performing royalty distribution business. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-42405 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in royalty distribution operations, there are cases where royalty payments are withheld, and prompt notification is required, but the notification process is cumbersome.

[0005] The present invention has been made in consideration of the above, and aims to provide a royalty management device, a royalty management method, and a royalty management program that can quickly notify with low workload when royalty payments are withheld in royalty distribution operations. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a royalty management device equipped with a control unit, wherein the control unit is configured to be able to access a distribution setting table that associates and registers original contract number, licensed rights, line number, distribution destination classification, distribution destination, distribution rate, and contract confirmation information indicating whether the contract is confirmed or not, a billing destination master that associates and registers billing destinations and credit management personnel, sales data including sales number, line number, original contract number, licensed rights, sales amount, sales management personnel, and billing destination, and collection schedule data including sales number, planned collection amount, planned collection date, and payment settlement completion classification that specifies whether payment settlement is complete or not, and calculates the sales amount and distribution amount according to the distribution rate of each distribution destination using the original contract number as a key based on the sales data and the distribution setting table, and The system is characterized by comprising: a distribution calculation processing means that creates calculation result confirmation data including the distribution amount and original contract number, and creates payment schedule data based on the calculation result confirmation data, including the payment number, distribution destination, statement No., scheduled payment date, payment amount, and a payment completion FLG indicating whether the payment has been completed or not; a payment reconciliation input means that, when the scheduled collection amount is deposited, updates the payment reconciliation completion classification for the scheduled collection data to "completed" and updates the payment completion FLG of the payment schedule data to "completed" using the statement No. of the calculation result confirmation data linked to the sales number as a key; and a payment withholding alert processing means that extracts details of the payment withholding FLG of "incomplete" for the scheduled payment data whose scheduled payment date is up to the reference date specified by the operator, and notifies an alert of payment withholding due to delayed collection.

[0007] In addition, according to one aspect of the present invention, the payment withholding alert processing means may further extract details of the original contract number and the statement number of the result confirmation data linked to the distribution destination for which the contract confirmation information is "unconfirmed" in the distribution setting table, and notify an alert of payment withholding due to an unconfirmed contract.

[0008] In addition, according to one aspect of the present invention, the payment withholding alert processing means may send an email to the sales representative's terminal to alert of payment withholding due to delayed collection, and may send an email to the credit management officer's terminal to alert of payment withholding due to unconfirmed contract.

[0009] Furthermore, in order to solve the above-mentioned problems and achieve the object, the present invention provides a royalty management method executed by an information processing device having a control unit, wherein the control unit is configured to be able to access a distribution setting table that associates and registers original contract number, licensed rights, line number, distribution destination classification, distribution destination, distribution rate, and contract confirmation information indicating whether the contract is confirmed or not, a billing destination master that associates and registers billing destinations and credit management personnel, sales data including sales number, line number, original contract number, licensed rights, sales amount, sales management personnel, and billing destination, and collection schedule data including sales number, planned collection amount, planned collection date, and payment reconciliation completion classification that specifies whether payment reconciliation is complete or not, and the control unit executes a royalty management method based on the sales data and the distribution setting table, using the original contract number as a key, to calculate the sales amount and the distribution amount according to the distribution rate of each distribution destination, and calculate The method includes a distribution calculation processing step that creates calculation result confirmation data including the invoice number, sales number, distribution destination, distribution amount, and original contract number, and creates payment schedule data based on the calculation result confirmation data, including the payment number, distribution destination, invoice number, scheduled payment date, payment amount, and a payment completion FLG indicating whether the payment has been completed or not; a payment reconciliation input step that, when the scheduled collection amount has been deposited, updates the payment reconciliation completion classification for the scheduled collection data to "completed" and updates the payment completion FLG of the payment schedule data to "completed" using the invoice number of the calculation result confirmation data linked to that sales number as a key; and a payment withholding alert processing step that extracts details of the payment withholding FLG of "incomplete" for the scheduled payment data with a scheduled payment date up to the reference date specified by the operator, and notifies an alert of payment withholding due to delayed collection.

[0010] In order to solve the above-mentioned problems and achieve the object, the present invention provides a royalty management program to be executed by an information processing device having a control unit, wherein the control unit is configured to be able to access a distribution setting table that associates and registers original contract number, licensed rights, line number, distribution destination classification, distribution destination, distribution rate, and contract confirmation information indicating whether the contract is confirmed or not, a billing destination master that associates and registers billing destinations and credit management personnel, sales data including sales number, line number, original contract number, licensed rights, sales amount, sales management personnel, and billing destination, and collection schedule data including sales number, planned collection amount, planned collection date, and payment settlement completion classification that specifies whether payment settlement is complete or not, and the control unit calculates the sales amount and distribution amount according to the distribution rate of each distribution destination using the original contract number as a key based on the sales data and the distribution setting table, and calculates the distribution amount according to the distribution rate of each distribution destination, and calculates the sales amount according to the distribution setting table using the original contract number as a key, and calculates the distribution amount according to the distribution setting table using the invoice number, sales number, The royalty management program is characterized by the following: a distribution calculation processing step that creates calculation result confirmation data including the distribution destination, distribution amount, and original contract number, and creates payment schedule data based on the calculation result confirmation data, including the payment number, distribution destination, invoice number, scheduled payment date, payment amount, and a payment completion FLG indicating whether the payment has been made or not; a payment reconciliation input step that, when the scheduled collection amount has been made, updates the payment reconciliation completion classification for the scheduled collection data to "completed" and updates the payment completion FLG of the payment schedule data to "completed" using the invoice number of the calculation result confirmation data linked to the sales number as a key; and a payment withholding alert processing step that extracts details of the payment schedule data where the scheduled payment date is up to the reference date specified by the operator and the payment completion FLG is "incomplete," and notifies an alert of payment withholding due to delayed collection. [Effects of the Invention]

[0011] According to the present invention, in a royalty distribution business, when a royalty payment is withheld, it is possible to notify the same promptly with a low workload. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram for explaining the characters. [Figure 2] FIG. 2 is a block diagram showing an example of the configuration of the royalty management device according to the present embodiment. [Figure 3] FIG. 3 is a flowchart illustrating the overall processing flow of the control unit of the royalty management device according to this embodiment. [Figure 4] FIG. 4 is a diagram for explaining a specific example of the processing of the control unit of the royalty management device according to the present embodiment. [Figure 5] FIG. 5 is a diagram for explaining a specific example of the process of the control unit of the royalty management device according to the present embodiment. [Figure 6] FIG. 6 is a diagram for explaining a specific example of the process of the control unit of the royalty management device according to the present embodiment. [Figure 7] FIG. 7 is a diagram for explaining a specific example of the process of the control unit of the royalty management device according to the present embodiment. [Figure 8] FIG. 8 is a diagram for explaining a specific example of the process of the control unit of the royalty management device according to the present embodiment. [Figure 9] FIG. 9 is a diagram for explaining a specific example of the process of the control unit of the royalty management device according to the present embodiment. [Figure 10] FIG. 10 is a diagram for explaining a specific example of the processing of the control unit of the royalty management device according to the present embodiment. [Figure 11] FIG. 11 is a diagram for explaining a specific example of the process of the control unit of the royalty management device according to the present embodiment. [Figure 12] FIG. 12 is a diagram for explaining a specific example of the processing of the control unit of the royalty management device according to the present embodiment. [Figure 13] FIG. 13 is a diagram for explaining a specific example of the process of the control unit of the royalty management device according to the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0013] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to this embodiment.

[0014] [1. Overview] For example, in the content production and media industries, there is a royalty distribution business that distributes royalties associated with the use of content. Below, an overview of this invention will be explained in the following order: [1-1. Payment withholding alert], [1-2. Payment confirmation for royalty calculation], and [1-3. Functional overview of this invention].

[0015] [1-1. Payment Withholding Alert] "assignment" In royalty distribution operations, the following may occur as reasons for withholding royalty payments: -Patterns where sales have not been paid · The contract with the investor has not been finalized Regarding payments (contracts) that result in payment withholding, prompt notification is required, but this process is cumbersome.

[0016] "Solution" In this invention, a function is implemented to alert sales representatives and receivables (royalties) management personnel about the likely causes of payment withholding for contracts that are likely to result in payment withholding.

[0017] "effect" The above function allows each person in charge to request prompt collection from the customer and to be aware of delays so that the payer can be notified early, thereby preventing problems and minimizing them.

[0018] [1-2. Confirming payment for royalty calculation] "assignment" In royalty distribution work, although the base is the sales amount from the customer, payment is often withheld until payment is completed, and in many cases payments are made in installments. For this reason, it is necessary to find contracts that meet the distribution conditions from among the contracts that are subject to distribution and withhold payments, but this management is cumbersome and prone to errors.

[0019] "Solution" The present invention not only calculates the royalty amount but also creates a payment schedule, promoting the efficiency of payment operations, and by implementing a control function that reserves the royalties until the sales corresponding to the royalties have been deposited, it is possible to further reduce the amount of administrative work and manual labor, eliminate unnecessary external management books, and achieve speedy payments.

[0020] "effect" This function will increase the accuracy and speed of payments, thereby increasing investors' trust in the committee and contributing to business effectiveness.

[0021] [1-3. Functional Overview of the Invention] The royalty management device of the present invention has the following functional outline. (1) When calculating royalties from sales, create payment schedule data to be distributed. (2) Regarding royalty payments, payment processing is carried out after the receivables created when calculating royalties have been settled, so whether to proceed to payment processing is controlled by the completion of payment settlement. (3) For contracts at risk of withholding payment, an alert including the cause (delay in collection, unconfirmed contract) will be sent to the sales manager and royalty manager (accounts manager).

[0022] 1 is a diagram for explaining the characters in this embodiment. The characters are the production committee that uses the royalty management device of the present invention, the distribution destinations (investors, original authors, screenwriters, etc.), and secondary users (manufacturers, etc.).

[0023] The recipients of the distributions will produce and invest in the production committee. The production committee will grant rights to the secondary users. The production committee will collect royalties from the secondary users and distribute the profits to the recipients.

[0024] [2. Configuration] An example of the configuration of the royalty management device 100 according to this embodiment will be described with reference to Fig. 2. Fig. 2 is a block diagram showing an example of the configuration of the royalty management device 100 according to this embodiment.

[0025] 2, the royalty management device 100 is a commercially available desktop personal computer. Note that the royalty management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0026] The royalty management device 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. The units included in the royalty management device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0027] The communication interface unit 104 communicatively connects the royalty 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 the communication line. Here, the network 300 has a function of communicatively connecting the royalty management device 100 with the server 200 and the terminals 400, etc., and is, for example, the Internet or a LAN (Local Area Network). The terminals 400, etc. are terminals used by sales managers, credit managers, etc.

[0028] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a touch panel), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function. In the following, the output device 114 may be referred to as the monitor 114 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0029] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with an OS (Operating System) to issue commands to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. The storage unit 106 can be, 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.

[0030] The storage unit 106 stores billing destination master data 106a, payment destination master data 106b, distribution setting table 106c, sales data, scheduled collection data, calculation result confirmation data, statement header data, scheduled payment data, and the like.

[0031] The billing destination master 106a can be configured as a table or the like in which billing destinations (billing destination CD and / or billing destination name), customers (customer CD and / or customer name), and credit management personnel (credit management personnel CD and / or credit management personnel name) are registered in association with each other (see Figure 4).

[0032] The payee master 106b can be configured as a table or the like in which payees (distribution destinations) (payee CD and / or payee name) and site information (payment month, payment date) are registered in association with each other (see FIG. 6).

[0033] The distribution setting table 106c associates and registers the original contract number, licensed right (licensed right CD and / or licensed right name), row number, distribution destination category (distribution destination category CD and / or distribution destination category name), distribution destination (distribution destination CD and / or distribution destination name), distribution rate, and contract confirmation information (confirmed or unconfirmed) (see Figure 5).

[0034] The sales data may include a sales number, a line number, an original contract number, a licensed right, a sales amount, a person in charge, and a billing destination CD (see FIG. 7(A)).

[0035] The collection schedule data may include a slip number, a collection schedule amount, a collection schedule date, and a payment settlement completion status (0: incomplete, 1: completed) (see FIG. 7(B)).

[0036] The calculation result confirmation data may include distribution processing number, calculation sheet number, reported sales number (sales number), distribution recipient (distribution recipient CD and / or distribution recipient name), distribution amount, and original contract number (see Figure 8(A)).

[0037] The statement header data may include statement number, distribution recipient (distribution recipient CD and / or distribution recipient name), amount including tax, distribution amount, consumption tax amount, and scheduled payment date (see FIG. 8(B)).

[0038] The payment schedule data may include payment number, payee (distribution destination) (payee CD and / or payee name), statement number, scheduled payment date, payment amount, payment amount, consumption tax to be paid, and payment completion FLG (0: incomplete, 1: completed) (see Figure 8(B)).

[0039] The control unit 102 is a CPU or the like that comprehensively controls the royalty 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, required data, etc., and executes various information processing based on these stored programs.

[0040] The control unit 102 is configured to be able to access the billing destination master 106a, the payment destination master 106b, the distribution setting table 106c, the sales data, the scheduled collection data, the calculation result confirmation data, the statement header data, the scheduled payment data, etc. stored in the memory unit 106. Note that the billing destination master 106a, the payment destination master 106b, the distribution setting table 106c, the sales data, the scheduled collection data, the calculation result confirmation data, the statement header data, the scheduled payment data, etc. may be provided in another location (for example, the server 200) as long as the control unit 102 is able to access them.

[0041] In terms of functional concept, the control unit 102 comprises a sales and billing registration unit 102a, a distribution calculation processing unit 102b, a deposit reconciliation input unit 102c, a payment reservation alert processing unit 102d, a payment settlement input processing unit 102e, a master maintenance unit 102f, and a screen display control unit 102g.

[0042] The sales and billing registration unit 102a inputs sales data and collection schedule data in response to an operator's operation on an input screen (not shown) displayed on the monitor 114, for example, and stores the data in the storage unit 106.

[0043] The distribution calculation processing unit 102b calculates the sales amount and the distribution amount according to the distribution rate of each distribution recipient using the original contract number as a key based on the sales data and the distribution setting table 106c, creates calculation result confirmation data including the invoice number, sales number, distribution recipient, distribution amount, and original contract number, and creates payment schedule data based on the calculation result confirmation data including the payment number, distribution recipient, invoice number, scheduled payment date, payment amount, and a payment completion FLG indicating whether payment has been completed or not, and stores this in the memory unit 106. The scheduled payment date may be calculated based on the scheduled collection date in the collection schedule data and the site information in the payment recipient master 106b.

[0044] When the amount scheduled for collection is deposited, the deposit reconciliation input unit 102c updates the deposit reconciliation completion classification for the scheduled collection data to "completed," and updates the deposit completion FLG of the scheduled payment data to "completed" using the statement number of the calculation result confirmation data linked to the sales number as a key.

[0045] For example, in response to an operator's operation on an alert screen (not shown) displayed on the monitor 114, the payment reservation alert processing unit 102d extracts details of payment schedule data for which the payment completion FLG is incomplete for those whose scheduled payment date is up to the reference date specified by the operator, and notifies the person in charge of an alert about payment reservation due to delayed collection. The alert about payment reservation due to delayed collection may be sent by email to the terminal 400 of the credit management person in charge.

[0046] The payment withholding alert processing unit 102d may further extract details of the original contract number and the statement number of the result confirmation data linked to the distribution destination for which the contract confirmation information is "unconfirmed" in the distribution setting table 106c, and notify the person in charge of an alert of payment withholding due to an unconfirmed contract. An alert of withholding of payment due to an unconfirmed contract may be sent by email to the terminal 400 of the sales manager.

[0047] The payment settlement input processing unit 102e determines that the details of the payment schedule data for which the payment completion FLG is "completed" are payable, and performs the payment process.

[0048] In addition, the payment settlement input processing unit 102e may determine that the details of the statement number in the result confirmation data linked to the original contract number and distribution destination for which the deposit completion FLG is ``completed'' and the contract confirmation information in the distribution setting table 106c is ``confirmed'' are payable for the payment schedule data, and perform payment processing.

[0049] The master maintenance unit 102f performs editing such as inputting, adding, changing, and updating data in the billing destination master 106a, the payment destination master 106b, and the distribution setting table 106c, for example, in response to operator operations on a master maintenance screen (not shown) displayed on the monitor 114.

[0050] The screen display control unit 102g controls the display of various screens (for example, a master maintenance screen, an input screen, an alert screen, etc.) displayed on the monitor 114 and the inputs thereto.

[0051] [3. Specific Examples] A specific example of the processing by the control unit 102 of the royalty management device 100 according to the present embodiment will be described with reference to Fig. 2 to Fig. 13. Fig. 3 to Fig. 13 are diagrams for explaining a specific example of the processing by the control unit 102 of the royalty management device 100 according to the present embodiment.

[0052] [3-1. Overall processing] The overall processing flow of the control unit 102 of the royalty management device 100 according to the present embodiment will be described with reference to Fig. 3. Fig. 3 is a diagram showing a flow for explaining the overall processing flow of the control unit 102 of the royalty management device 100 according to the present embodiment.

[0053] 3, the sales and invoice registration unit 102a executes a sales and invoice registration process (step S1). Specifically, in the sales and invoice registration process, the sales and invoice registration unit 102a inputs sales data and collection schedule data in response to an operator's operation on an input screen (not shown) displayed on the monitor 114, for example, and stores the data in the storage unit 106.

[0054] The distribution calculation processing unit 102b executes the distribution calculation process (step S2). Specifically, in the distribution calculation process, the distribution calculation processing unit 102b calculates the sales amount and the distribution amount according to the distribution rate of each distribution destination using the original contract number as a key based on the sales data and the distribution setting table 106c, creates calculation result confirmation data including the statement number, sales number, distribution destination, distribution amount, and original contract number, and creates payment schedule data based on the calculation result confirmation data including the payment number, distribution destination, statement number, scheduled payment date, payment amount, and a payment completion FLG indicating whether payment has been completed or not, and stores the data in the storage unit 106.

[0055] The deposit reconciliation input unit 102c executes the deposit reconciliation input process (step S3). Specifically, in the deposit reconciliation input process, when the scheduled collection amount is deposited, the deposit reconciliation input unit 102c updates the deposit reconciliation completion classification for the collection schedule data to "1: Completed", and updates the deposit completion FLG of the payment schedule data to "1: Completed" using the statement No. of the calculation result confirmation data linked to the sales number as a key.

[0056] The payment reservation alert processing unit 102d executes the payment reservation alert processing (step S4), determines whether the details of the payment schedule data are subject to an alert (step S4-1), and if they are subject to an alert, notifies the alert (step S4-2).

[0057] Specifically, in the payment withholding alert processing, the payment withholding alert processing unit 102d, for example, in response to an operator's operation on an alert screen (not shown) displayed on the monitor 114, extracts details from the payment schedule data where the scheduled payment date is up to the reference date specified by the operator and the payment completion FLG is "0: Incomplete", and notifies the person in charge's terminal 400 by email of an alert of payment withholding due to delayed collection.

[0058] In addition, the payment reservation alert processing unit 102d may further extract details of the original contract number and the statement number of the result confirmation data linked to the distribution destination for which the contract confirmation information is "unconfirmed" in the distribution setting table 106c from the payment schedule data, and notify the person in charge's terminal 400 by email of an alert of payment reservation due to an unconfirmed contract.

[0059] The payment settlement input processing unit 102e executes the payment settlement input process (step S5). Specifically, in the payment settlement input process, the payment settlement input processing unit 102e determines that the details of the payment schedule data for which the deposit completion flag is "completed" are payable, and performs the payment process.

[0060] In addition, the payment settlement input processing unit 102e may determine that the details of the statement number in the result confirmation data linked to the original contract number and distribution destination for which the deposit completion FLG is ``completed'' and the contract confirmation information in the distribution setting table 106c is ``confirmed'' are payable for the payment schedule data, and perform payment processing.

[0061] [3-2. Sample data] 4 to 13 are diagrams showing sample data for explaining a specific example of the processing of the control unit 102 of the royalty management device 100 in this embodiment. A specific example of the processing of the control unit 102 of the royalty management device 100 in this embodiment will be explained with reference to FIGS.

[0062] (Prerequisite master and data) In the following description, it is assumed that the master and data shown in FIGS. 4 to 7 are registered in advance in the storage unit 106.

[0063] 4 is a diagram showing an example of the configuration of the billing destination master 106a. The billing destination master 106a has items such as billing destination CD, customer CD, and credit management officer CD. In the example shown in the figure, the first line contains billing destination CD "SEI0001", customer CD "TOK00001", and credit management officer CD "T00001".

[0064] 5 is a diagram showing an example of the configuration of the distribution setting table 106c. The distribution setting table 106c includes items such as original contract number, licensed rights CD, row number, distribution destination category, distribution destination category name, distribution destination CD, distribution destination name, distribution rate, and contract confirmation information (confirmed or unconfirmed). The licensed rights include, for example, merchandising rights, theatrical film rights, app game rights, and overseas distribution rights. In the example shown in the figure, the first row contains the original contract number "L0001," licensed rights CD "1000," row number "1," distribution destination category "10," distribution destination category name "original author," distribution destination CD "S00001," distribution destination name "Original Author Taro," distribution rate "30%," and contract confirmation category "confirmed."

[0065] Figure 6 is a diagram showing an example of the configuration of the payee master 106b. The payee master 106b includes fields such as payee CD, payee name, payment month, and payment date. In the example shown in the figure, the first line contains payee CD "S00001", payee name "Seisan Taro", payment month "1", and payment date "15".

[0066] 7(A) is a diagram showing an example of sales data. The sales data includes items such as sales number, line number, original contract number, licensed rights, sales amount, sales manager, and billing CD. In the example shown in the figure, the first line contains sales number "U00001," line number "001," original contract number "L0001," licensed rights "merchandising rights," sales amount "1100000," sales manager CD "T00001," and billing CD "SEI0001."

[0067] Figure 7(B) is a diagram showing an example of scheduled collection data. The scheduled collection data includes items such as the slip number, scheduled collection amount, scheduled collection date, and payment reconciliation completion category. In the example shown in the figure, the first line contains the slip number "U00001," the scheduled collection amount "1100000," the scheduled collection date "2024 / 05 / 20," and the payment reconciliation completion category "0."

[0068] (S2: Main distribution calculation process) A specific example of this distribution calculation process will be described with reference to Figure 8. Based on the sales data and distribution setting table 106c, the distribution calculation processing unit 102b calculates the sales amount and the distribution amount according to the distribution rate of each distribution destination using the original contract number as a key, creates calculation result confirmation data including the invoice number, sales number, distribution destination, distribution amount, and original contract number, and based on the calculation result confirmation data, creates payment schedule data including the payment number, distribution destination, invoice number, scheduled payment date, payment amount, and a payment completion FLG indicating whether payment has been completed or not, and stores this in the storage unit 106.

[0069] Conventionally, payment data was created separately after the distribution calculation process. In this invention, payment schedule data is created at the granularity of the statement number at the time of the distribution calculation process. The payment destination is the distribution destination in the statement header, and the scheduled payment date and amount information are also calculated during the calculation process. Using the original contract number of the sales data and the original contract number in the distribution setting table 106c as keys, the distribution amount for sales is calculated and created as calculation result confirmation data. In addition, the distribution setting table 106c is referenced for the statement number and distribution amount in the calculation result confirmation data to create calculation statement header data.

[0070] Figure 8(A) shows an example of calculation result confirmation data. The calculation result confirmation data is generated based on the sales data and distribution setting table 106c. The calculation result confirmation data includes items such as distribution process number, statement number, reported sales number (sales number), distribution destination CD, distribution amount, and original contract number. The "distribution amount" is calculated by using the original contract number as a key and distributing the sales amount of the sales data to each distribution destination in the distribution setting table 106c according to the distribution rate. In the example shown in the figure, the first row contains distribution process number "100001", statement number "1000", reported sales number "U00001", distribution destination CD "S00001", distribution amount "330000 (= 1100000 x 30%)", and original contract number "L0001".

[0071] Figure 8(B) is a diagram showing an example of statement header data. Statement header data is generated based on the calculation result confirmation data. Statement header data includes items such as statement number, distribution destination CD, amount including tax, distribution amount, consumption tax amount, and scheduled payment date. The "scheduled payment date" is calculated based on the "scheduled collection date" in the scheduled collection data and the site information (payment month, payment date) in the payment destination master 106b.

[0072] In the example shown in the figure, the first line has the statement number "1000," distribution destination CD "S00001," tax-inclusive amount "330000," distribution amount "300000," consumption tax amount "30000," and scheduled payment date "2024 / 06 / 15." The scheduled payment date "2024 / 06 / 15" is calculated by adding 2024 / 05 (scheduled collection date "2024 / 05 / 20") + payment month "1" in payment destination master data 106b + payment date "15" in payment destination master data 106b.

[0073] Figure 8(C) is a diagram showing an example of scheduled payment data. Scheduled payment data is created based on the statement header data. Scheduled payment data includes fields such as payment number, distribution destination CD, statement number, scheduled payment date, payment amount, payment amount, payment consumption tax, and payment completion FLG. In the example shown in the figure, the first line contains payment number "SIR000001," supplier CD "S00001," statement number "1000," scheduled payment date "2024 / 06 / 15," payment amount "330000," payment amount "300000," payment consumption tax "30000," and payment completion FLG "0."

[0074] (S3: Payment reconciliation input processing) A specific example of the deposit reconciliation input process will be described with reference to Figure 9. When the amount scheduled for collection has been deposited, the deposit reconciliation input unit 102c updates the deposit reconciliation completion classification for the collection schedule data to "completed," and updates the deposit completion FLG of the payment schedule data to "completed" using the statement number of the calculation result confirmation data linked to the sales number as a key.

[0075] In the payment reconciliation input process, the sales number in the calculation result confirmation data is used as a key to reference the collection schedule data and determine the payment status for the created payment schedule data. When the payment reconciliation completion category for the collection schedule data is updated to "1" (when debt collection is complete), the payment completion FLG for the linked payment schedule data is updated to "1". As will be described later, when entering payment settlement, by adding the payment completion FLG = 1 for the payment schedule data to the extraction conditions for extracting the details of the payment schedule data to be paid, the details of the payment schedule data linked to uncollected debt cannot be processed for payment, preventing erroneous payments.

[0076] 9(A) shows an example of updated collection schedule data, and FIG. 9(B) shows an example of updated payment schedule data.

[0077] As shown in Figure 9(A), when the payment settlement completion classification for sales number "U00002" is updated to "1", the payment completion FLG in the payment schedule data for statement numbers "1004, 1005, 1006, 1007" in the calculation result confirmation data (see Figure 8(A)) linked to sales number "U00002" is updated to "1", as shown in Figure 9(B).

[0078] (S4: Payment withholding alert processing) A specific example of payment withholding alert processing will be described with reference to Figure 10. For example, in response to an operator's operation on an alert screen (not shown) displayed on the monitor 114, the payment withholding alert processing unit 102d extracts details of payment schedule data for which the scheduled payment date is up to the reference date specified by the operator and for which the payment completion FLG is incomplete, and notifies the terminal 400 of the credit management staff by email of an alert of payment withholding due to delayed collection, and further extracts details of the original contract number and the statement number of the result confirmation data linked to the distribution destination for which the contract confirmation information is "unconfirmed" in the distribution setting table 106c, and notifies the terminal 400 of the sales management staff by email of an alert of payment withholding due to the contract not being confirmed.

[0079] In the payment reservation alert process, information that will result in payment reservation is extracted from the "contract confirmation information" in the distribution setting table 106c and the "payment settlement completion classification" in the collection schedule data, and an alert is issued to the sales manager and the credit manager.

[0080] On the alert screen, the operator inputs the base date (payment date) of the alert, extracts details of the payment schedule data that meet the conditions for withholding payments up to that point, and notifies the sales representative and the credit management representative. Notification can be made by email, for example.

[0081] This example explains the case where payment reservations for payment schedule data up to the base date of 2024 / 07 / 31 are checked. Figure 10 shows an example of payment schedule data. As shown in Figure 10, the details of statement numbers "1000" to "1004" on lines 1 to 4 have a payment completion FLG of "0", and are subject to an alert *1 due to delayed collection. In addition, statement number "1007" on line 7 is a detail that corresponds to the contract confirmation information "unconfirmed" in the distribution setting table 106c, and is subject to an alert *2 due to the contract not being confirmed.

[0082] *1: Alerts are available for delayed collection. The logic for extracting "*1: Alert target due to delayed collection" will be explained with reference to Figure 11. Figure 11(A) shows an example of calculation result confirmation data. Figure 11(B) shows an example of collection schedule data. Figure 11(C) shows an example of sales data. Figure 11(D) shows an example of data from the billing destination master 106a.

[0083] As shown in Figure 11(B), sales number "U00001" is subject to an alert with payment settlement completion category "0", so as shown in Figure 11(C), using the billing destination CD "SEI0001" of the sales data linked to sales number "U00001" as a key, the accounts receivable manager CD "T00001" is obtained from the billing destination master 106a as shown in Figure 11(D), and an alert of payment withholding due to delayed collection is sent by email to the terminal 400 of the obtained accounts receivable manager CD "T00001" for the details of statement Nos. "1000" to "1004" of the payment schedule data.

[0084] *2: Alert subject to unconfirmed contract The logic for extracting "*2: Alert target due to unconfirmed contract" will be explained with reference to Figure 12. Figure 12(A) shows an example of calculation result confirmation data. Figure 12(B) shows an example of data in the distribution setting table 106c. Figure 12(C) shows an example of sales data.

[0085] As shown in Figure 12(B), for the original contract number "L0002" and distribution destination CDs "S00003" and "S00004" in the distribution setting table 106c, the contract confirmation information is "unconfirmed" and an alert is targeted. Therefore, as shown in Figure 12(A), for the calculation result confirmation data's statement numbers "1006" and "1007" linked to the original contract number "L0002" and distribution destination CDs "S00003" and "S00004" in the calculation result confirmation data, the details of statement number "1006" on the 7th line in the payment schedule data in Figure 10 are targeted for an alert due to the contract not being confirmed. As for statement number "1007" on the 8th line, it is after the base date (base date "7 / 31 / 2024", scheduled payment date "8 / 31 / 2024"), so it is not targeted for an alert.

[0086] In addition, using the sales number "U00002" of the calculation result confirmation data linked to the original contract number "L0002" in the distribution setting table 106c as a key, the sales manager CD "T00002" is obtained from the sales data as shown in Figure 12 (C), and an alert is sent by email to the terminal 400 of the obtained sales manager CD "T00002" regarding the details of the statement number "1006" of the payment data in Figure 10 mentioned above, indicating that the contract has not been finalized.

[0087] (S5: Payment settlement input processing) The payment settlement input process will be explained with reference to Figure 13. The payment settlement input processing unit 102e determines that the details of the statement number in the result confirmation data linked to the original contract number and distribution destination for which the deposit completion FLG is "completed" and the contract confirmation information in the distribution setting table 106c is "confirmed" are payable for the payment schedule data, and performs the payment process.

[0088] In the payment settlement input process, at the time of payment settlement, only data in which the contract confirmation information in the distribution setting table 106c is "confirmed" and the payment completion FLG of the payment schedule data is set to 1 is determined to be paymentable. Figure 13 shows an example of payment schedule data.

[0089] In Figure 13, for the payment schedule data, the details of the statement numbers "1004" and "1005" in the result confirmation data linked to the original contract number "l0002" and distribution destinations "S00003" and "S00004", where the payment completion FLG is 1 and the contract confirmation information in the distribution setting table 106c is "confirmed", are determined to be processable (payable) details, and payment processing is performed.

[0090] As described above, according to this embodiment, based on the distribution setting table 106c which associates and registers original contract number, licensed right, line number, distribution destination classification, distribution destination, distribution rate, and contract confirmation information indicating whether the contract is confirmed or not, the invoice destination master 106a which associates and registers invoice destinations and credit management personnel, and the sales data and distribution setting table 106c, the original contract number is used as a key to calculate the sales amount and the distribution amount according to the distribution rate of each distribution destination, and calculation result confirmation data including the invoice number, sales number, distribution destination, distribution amount, and original contract number is created, and based on the calculation result confirmation data, payment schedule including the payment number, distribution destination, invoice number, scheduled payment date, payment amount, and payment completion FLG indicating whether payment has been completed or not is generated. The system is equipped with a distribution calculation processing unit 102b that creates the set data, a payment reconciliation input unit 102c that, when the amount to be collected is deposited, updates the payment reconciliation completion classification for the scheduled collection data to "completed" and updates the payment completion FLG of the scheduled payment data to "completed" using the statement number of the calculation result confirmation data linked to the sales number as a key, and a payment withholding alert processing unit 102d that extracts details of the scheduled payment data where the payment completion FLG is "incomplete" for those whose scheduled payment date is up to the reference date specified by the operator and notifies an alert of payment withholding due to delayed collection, so that in the royalty distribution business, when a payment withholding of royalty payment occurs, it is possible to notify quickly with low workload.

[0091] In addition, the payment settlement input processing unit 102e is equipped with a function that determines that payment is possible for details for which the payment completion FLG is "completed" for payment schedule data. This facilitates management in the royalty distribution business when it is necessary to withhold royalty payments to distribution recipients, thereby reducing operational errors.

[0092] [4. 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 contributing to the achievement of SDGs Goals 8 and 9.

[0093] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0094] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

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

[0096] 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 known methods.

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

[0098] Furthermore, with regard to the royalty management device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0099] For example, all or any part of the processing functions of the royalty management device 100, particularly the processing functions performed by the control unit 102, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the royalty management device 100 as needed. That is, a computer program for providing instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). The computer program is executed by being loaded into RAM, and cooperates with the CPU to form the control unit.

[0100] In addition, this computer program may be stored in an application program server connected to the royalty management device 100 via any network, and all or part of it may be downloaded as needed.

[0101] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or 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.

[0102] Furthermore, a "program" is a data processing method written in any language or description method, and does not matter whether it is in the form of source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0103] The various databases stored in the memory unit 106 are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

[0104] The royalty 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. The royalty management device 100 may be realized by installing software (including programs or data) that causes the device to perform the processes described in this embodiment.

[0105] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]

[0106] The present invention is useful in industries involved in content production and copyright work, such as the publishing industry, media industry, game industry, animation industry, music industry, and film industry. [Explanation of symbols]

[0107] 100 Royalty Management Device 102 Control section 102a Sales and Billing Registration Department 102b Distribution calculation processing unit 102c Receipt Reconciliation Entry Section 102d Payment withholding alert processing unit 102e Payment settlement input processing unit 102f Master Maintenance Department 102g Screen display control unit 104 Communication interface unit 106 Storage section 106a Billing Master 106b Payment destination master 106c Distribution Setting Table 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network 400 terminals

Claims

1. A royalty management device having a control unit, The control unit a distribution setting table for registering, in association with each other, original contract number, licensed rights, distribution classification, distribution recipient, distribution rate, and contract confirmation information indicating whether the contract is confirmed or not; Invoice master data that associates invoice recipients and account receivable managers, Sales data including sales number, line number, original contract number, license rights, sales amount, sales manager, and billing address; Collection schedule data including a sales number, a collection schedule amount, a collection schedule date, and a payment settlement completion classification that specifies whether payment settlement has been completed or not; It is configured to be accessible to This distribution calculation processing means calculates the sales amount and the distribution amount according to the distribution rate of each distribution destination using the original contract number as a key based on the sales data and the distribution setting table, creates calculation result confirmation data including the statement number, sales number, distribution destination, distribution amount, and original contract number, and creates payment schedule data based on the calculation result confirmation data including the payment number, distribution destination, statement number, scheduled payment date, payment amount, and a payment completion flag indicating whether or not payment has been completed; a payment settlement input means for updating the payment settlement completion classification of the payment schedule data to "completed" when the scheduled collection amount has been deposited, and updating the payment completion flag of the payment schedule data to "completed" using the statement number of the calculation result confirmation data linked to the sales number as a key; A payment reservation alert processing means for extracting details of the payment schedule data whose payment schedule date is up to a reference date designated by an operator and whose payment completion flag is "incomplete" and notifying an alert of payment reservation due to a collection delay; A royalty management device comprising:

2. The royalty management device described in claim 1, characterized in that the payment withholding alert processing means further extracts details of the original contract number and the calculation result confirmation data linked to the distribution destination whose contract confirmation information is ``unconfirmed'' in the distribution setting table from the payment schedule data, and notifies an alert of payment withholding due to the contract being unconfirmed.

3. The royalty management device described in claim 2, characterized in that the payment withholding alert processing means notifies the sales representative's terminal of an alert of payment withholding due to delayed collection by email, and notifies the credit management representative's terminal of an alert of payment withholding due to an unconfirmed contract by email.

4. A royalty management method executed by an information processing device having a control unit, The control unit a distribution setting table for registering, in association with each other, original contract number, licensed rights, line number, distribution classification, distribution destination, distribution rate, and contract confirmation information indicating whether the contract is confirmed or not; Invoice master data that associates invoice recipients and account receivable managers, Sales data including sales number, line number, original contract number, license rights, sales amount, sales manager, and billing address; Collection schedule data including a sales number, a collection schedule amount, a collection schedule date, and a payment settlement completion classification that specifies whether payment settlement has been completed or not; It is configured to be accessible to Executed in the control unit: a distribution calculation process for calculating the sales amount and distribution amount according to the distribution rate of each distribution destination using the original contract number as a key based on the sales data and the distribution setting table, creating calculation result confirmation data including the statement number, sales number, distribution destination, distribution amount, and original contract number, and creating payment schedule data based on the calculation result confirmation data including the payment number, distribution destination, statement number, scheduled payment date, payment amount, and a payment completion flag indicating whether or not payment has been completed; a payment reconciliation input step for updating the payment reconciliation completion classification for the payment schedule data to "completed" when the scheduled collection amount has been deposited, and updating the payment completion flag of the payment schedule data to "completed" using the statement number of the calculation result confirmation data linked to the sales number as a key; a payment reservation alert processing step for extracting details of the payment schedule data whose payment schedule date is up to a reference date designated by an operator and whose payment completion flag is "incomplete" and notifying an alert of payment reservation due to a collection delay; A royalty management method comprising:

5. A royalty management program to be executed by an information processing device having a control unit, The control unit a distribution setting table for registering, in association with each other, original contract number, licensed rights, line number, distribution classification, distribution destination, distribution rate, and contract confirmation information indicating whether the contract is confirmed or not; Invoice master data that associates invoice recipients and account receivable managers, Sales data including sales number, line number, original contract number, license rights, sales amount, sales manager, and billing address; Collection schedule data including a sales number, a collection schedule amount, a collection schedule date, and a payment settlement completion classification that specifies whether payment settlement has been completed or not; It is configured to be accessible to The control unit a distribution calculation process for calculating the sales amount and distribution amount according to the distribution rate of each distribution destination using the original contract number as a key based on the sales data and the distribution setting table, creating calculation result confirmation data including the statement number, sales number, distribution destination, distribution amount, and original contract number, and creating payment schedule data based on the calculation result confirmation data including the payment number, distribution destination, statement number, scheduled payment date, payment amount, and a payment completion flag indicating whether or not payment has been completed; a payment reconciliation input step for updating the payment reconciliation completion classification for the payment schedule data to "completed" when the scheduled collection amount has been deposited, and updating the payment completion flag of the payment schedule data to "completed" using the statement number of the calculation result confirmation data linked to the sales number as a key; a payment reservation alert processing step for extracting details of the payment schedule data whose payment schedule date is up to a reference date designated by an operator and whose payment completion flag is "incomplete" and notifying an alert of payment reservation due to a collection delay; Royalty management program to carry out.

Images