Credit collation system, credit collation method, and credit collation program

Abstract

To provide a credit collation system, a credit collation method, and a credit collation program capable of reducing a workload of credit collation and preventing artificial errors.SOLUTION: A credit collation system according to one embodiment comprises: a first mater for registering, for each billing destination, a collation unnecessary flag for omitting or designating a symbol when performing collation about a reservation number of a reservation person name, the number of collation digits and a collation start position in association with each other; and collation means for acquiring, from the first master, a collation symbol unnecessary flag, the number of collation digits, and a collation start position about a reservation number or a reservation person name by using a billing destination of credit data as a key, deleting a symbol of a reservation number or a reservation person name when the acquired collation symbol unnecessary flag is unnecessary to a reservation number or a reservation person name of the credit data, extracting the number of collation digits acquired from the acquired collation start position to create a collation key, and collating the credit data with planned money reception data by using the created collation key.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a credit matching system, a credit matching method, and a credit matching program. [Background technology]

[0002] For example, a company's facilities may be reserved and used through a real agent (agency, etc.) or an online agent (reservation site, etc.). Patent Document 1, for example, discloses a system for making reservations through an agent. [Prior art documents] [Patent documents]

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

[0004] Generally, the reservation numbers assigned to the bond data and expected deposit data received from agents are assigned according to various rules for each agent. Previously, the bond data from agents was collated with the expected deposit data by a staff member outside the system using Excel or similar software, which resulted in a high workload for bond collation and the risk of human error.

[0005] The present invention has been made in view of the above, and aims to provide a credit matching system, a credit matching method, and a credit matching program that can reduce the workload of credit matching and prevent human error. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a debt matching system equipped with a control unit, wherein the control unit is configured to be able to access a memory area storing, for each billing recipient, a first master in which a no-match flag specifying whether symbols are to be omitted when matching a reservation number or a reservation holder name, the number of matching digits, and a matching start position are associated and registered; debt data obtained from the billing recipient, including the billing recipient, reservation number, reservation holder name, and amount; and scheduled deposit data obtained from the billing recipient, including the reservation number, reservation holder name, and amount; and the control unit is configured to access a memory area storing, for each billing recipient, a no-match flag, the number of matching digits, and a matching start position for the reservation number or reservation holder name using the billing recipient of the debt data as a key; and the control unit is further configured to:

[0007] According to another aspect of the present invention, the symbol to be deleted may be registered in a second master.

[0008] According to another aspect of the present invention, the billing destination may include an agent who makes accommodation or facility reservations.

[0009] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides a debt matching method executed by an information processing device equipped with a control unit, wherein the control unit is configured to be able to access a memory area that stores, for each billing recipient, a first master in which a no-match flag that specifies whether symbols are to be omitted when matching a reservation number or a reservation holder name, the number of matching digits, and a matching start position are associated and registered; debt data obtained from the billing recipient, including the billing recipient, reservation number, reservation holder name, and amount; and scheduled deposit data obtained from the billing recipient, including the billing recipient, reservation number, reservation holder name, and amount; and the control unit executes a matching step of obtaining, from the first master, a no-match symbol flag, the number of matching digits, and the matching start position for the reservation number or the reservation holder name using the billing recipient of the debt data as a key; and, for each billing recipient, if the obtained no-match symbol flag for the reservation number or the reservation holder name of the debt data is "not required," deleting symbols from the reservation number or the reservation holder name, extracting the obtained number of matching digits from the obtained matching start position to create a matching key, and using the created matching key to match the debt data with the scheduled deposit data.

[0010] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides a claim matching 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 memory area that stores, for each billing recipient, a first master in which a no-match flag that specifies whether symbols are to be omitted when matching a reservation number or a reservation holder name, the number of matching digits, and a matching start position are associated and registered; claim data obtained from the billing recipient, including the billing recipient, reservation number, reservation holder name, and amount; and scheduled deposit data obtained from the billing recipient, including the billing recipient, reservation number, reservation holder name, and amount; and the claim matching program is configured to cause the control unit to obtain from the first master, using the billing recipient of the claim data as a key, the no-match symbol flag, the number of matching digits, and the matching start position for the reservation number or the reservation holder name; and, for each billing recipient, if the obtained no-match symbol flag for the reservation number or the reservation holder name of the claim data is "not required," delete the symbols from the reservation number or the reservation holder name, extract the obtained number of matching digits from the obtained matching start position to create a matching key, and execute a matching step of matching the claim data with the scheduled deposit data using the created matching key. [Effects of the Invention]

[0011] The present invention has the effect of reducing the workload of receivables matching and preventing human error. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a claim matching system according to this embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of the configuration of the billing destination master. [Figure 3] FIG. 3 is a diagram illustrating an example of the configuration of the general-purpose name master. [Figure 4] FIG. 4 is a flowchart for explaining an outline of the processing of the verification unit of the bond verification system in this embodiment. [Figure 5] FIG. 5 is a diagram for explaining a specific example of the processing of the verification unit of the claim verification system in this embodiment. [Figure 6] FIG. 6 is a diagram for explaining a specific example of the processing of the collation unit of the claim collation system in this 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 the embodiment.

[0014] [1. Overview] For example, when a reservation is made for a stay at one of the company's accommodation facilities via a real agent or online agent, a high operational load is placed on receivables matching (matching receivables data with expected payment data). One factor contributing to this load is that the specifications for receivables matching differ for each agent. The reservation number and name of the person making the reservation used for matching are set according to each agent's rules, and the values ​​set at the time of reservation (receivables data) and at the time of payment (expected payment data) are often different, even for the same agent.

[0015] Previously, the data was checked visually by the person in charge and processed using Excel, etc., which resulted in a high workload and human errors in matching.

[0016] Therefore, in this embodiment, the rules (specifications) for receivables matching can be registered in the master for each billing destination (e.g., agent) and controlled, thereby reducing the workload and human error during receivables matching.

[0017] The present invention is widely applicable to industries where companies use their own facilities, such as the accommodation and leisure industry.

[0018] [2. Configuration] 1 is a block diagram showing an example of the configuration of a credit matching system 100 according to this embodiment. The credit matching system 100 according to this embodiment can be suitably used by a company whose own facilities are reserved and used, and the following example will be described taking as an example a case where a company's facilities are reserved and settled by an agent.

[0019] The claim matching system 100 is, for example, a commercially available desktop personal computer. Note that the claim matching system 100 is not limited to a stationary information processing device such as a desktop personal computer, and 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. In Figure 1, the claim matching system 100 comprises a control unit 102, a communications interface unit 104, a memory unit 106, and an input / output interface unit 108. The units comprised in the claim matching system 100 are connected to each other so that they can communicate with each other via any communications path.

[0020] The communications interface unit 104 communicatively connects the claim matching system 100 to the network 300 via a communications device such as a router and a wired or wireless communications line such as a dedicated line. The communications interface unit 104 has the function of exchanging data with other devices via communications lines. Here, the network 300 has the function of connecting the claim matching system 100, the agents 400, etc., and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). The agents 400, etc., are, for example, agents of various companies (e.g., Companies A to C), who reserve their own facilities and make payments, are equipped with reservation systems, and are connected to the websites of the various companies that make payments (such as card companies, electronic money companies, and app payment companies). Users reserve their own facilities using the reservation system and make payments on the selected website.

[0021] 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 home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that functions as a pointing device in cooperation with a mouse. Note that hereinafter, the output device 114 may be referred to as the monitor 114.

[0022] 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.

[0023] The storage unit 106 stores various data such as a billing destination master (first master) 106a, a general name master (second master) 106b, bond data, and expected payment data. Fig. 2 is a diagram showing an example of the configuration of the billing destination master 106a. Fig. 3 is a diagram showing an example of the configuration of the general name master 106b.

[0024] The billing destination master 106a is a master that sets rules for matching reservation numbers and reservation holder names for each agent (billing destination) and generates a matching key based on the reservation number or reservation holder name in the bond data or sales forecast data. It is possible to generate four matching keys: reservation number or reservation holder name based on the bond data, and reservation number or reservation holder name based on the sales forecast data, and the person in charge can select which one to use. Below, we will explain how to generate a matching key based on the reservation number in the bond data.

[0025] 2, the billing destination master 106a can be configured as a table that associates and registers the billing destination, a reservation number verification symbol unnecessary flag that specifies whether or not to omit symbols in the reservation number when verifying, a reservation number verification start position (for bond data), a reservation number verification start position (for scheduled deposit data), the number of digits in the reservation number verification, a reservation name verification symbol unnecessary flag that specifies whether or not to omit symbols in the reservation name when verifying, a reservation name verification start position (for bond data), a reservation name verification start position (for scheduled deposit data), and the number of digits in the reservation name verification. The contents of each item are as follows:

[0026] Reservation number verification symbol unnecessary flag: Used when verifying by reservation number. Controls whether to verify by omitting the reservation number symbol stored in the bond data and payment schedule data. Reservation number matching start position (for bond data): Used when matching by reservation number. Matching start position of reservation number stored in bond data. Reservation number matching start position (for scheduled payment data): Used when matching by reservation number. Matching start position of reservation number stored in scheduled payment data. · Number of digits for reservation number matching: Used when matching by reservation number. The number of digits used to match the reservation number stored in the bond data and the payment schedule data. · No matching symbol required for reservation name: Used when matching by reservation name. Controls whether to match by omitting the symbols in the reservation name stored in the bond data and expected deposit data. · Reservation name matching start position (for bond data): Used when matching by reservation name. Matching start position of reservation name stored in bond data. · Reservation name matching start position (for scheduled deposit data): Used when matching by reservation name. Matching start position of reservation name stored in scheduled deposit data. Number of digits to match reservation name: Used when matching by reservation name. The number of digits to use when matching reservation names stored in bond data and expected deposit data.

[0027] In the example shown in the same figure, the first line has the billing destination "Agent A Company", reservation number matching symbol not required flag "not required", reservation number matching start position (for debt data) "2", reservation number matching start position (for scheduled deposit data) "7", reservation number matching digits count "5", reservation name matching symbol not required flag "not required", reservation name matching start position (for debt data) "2", reservation name matching start position (for scheduled deposit data) "7", reservation name matching digits count "5".

[0028] The general name master 106b is a master that defines the symbols to be deleted during credit matching when the reservation number matching symbol unnecessary flag is "unnecessary" in the billing destination master 106a, and can be configured as a table that associates and registers types, code values, and code names, as shown in Figure 3. Each item is as follows:

[0029] Type: Any control number Code value: Any sequential number Chord name: Symbol to be defined

[0030] In the example shown in the figure, the symbols "#", "-" and "@" are deleted when creating a matching key.

[0031] The bond data may include the billing address (billing address code and / or billing address name), reservation number, name of the person making the reservation, amount, etc.

[0032] The expected sales data may include the billing address (billing address code and / or billing address name), reservation number, name of person making reservation, amount, etc.

[0033] The control unit 102 is a CPU or the like that performs overall control of the credit matching system 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 operations based on these stored programs.

[0034] The control unit 102 is configured to be able to access the billing destination master (first master) 106a, the general name master (second master) 106b, the bond data, the expected deposit data, etc. stored in the memory unit 106. Note that the billing destination master (first master) 106a, the general name master (second master) 106b, the bond data, the expected deposit data, etc. may be stored in another location (for example, the server 200) as long as the control unit 102 is able to access them.

[0035] The control unit 102 conceptually includes a collating unit 102a, a master maintenance unit 102b, and a screen display control unit 102c.

[0036] The matching unit 102a acquires from the agents 400..., bond data including the billing destination (agent), reservation number, name of the person who made the reservation, and amount, and deposit data including the billing destination, reservation number, name of the person who made the reservation, and amount, and stores these in the memory unit 106. For example, in response to an operation by a person in charge on the deposit confirmation matching screen (see FIG. 6) displayed on the monitor 114, the matching unit 102a acquires from the billing destination master 106a, using the billing destination of the target bond data stored in the memory unit 106 as a key, a matching symbol unnecessary flag, the number of matching digits, and the matching start position for the reservation number or the name of the person who made the reservation, and for each billing destination, if the acquired matching symbol unnecessary flag for the reservation number or the name of the person who made the reservation is "unnecessary," the unit deletes the symbol from the reservation number or the name of the person who made the reservation, extracts the acquired number of matching digits from the acquired matching start position, and uses the created matching key to match the bond data with the scheduled deposit data (including extracting and displaying the bond data and the scheduled deposit data to be matched, and clearing the deposit).

[0037] The symbols to be deleted may be those registered in the general name master 106b.

[0038] The master maintenance unit 102b performs settings such as inputting, adding, changing, and updating data in the billing destination master 106a and the general name master 106b, for example, in response to operator operations on a master maintenance screen (not shown) displayed on the monitor 114.

[0039] The screen display control unit 102c controls the display of various screens (for example, a master maintenance screen, a payment confirmation inquiry screen, etc.) displayed on the monitor 114 and the reception of inputs.

[0040] [3. Specific Examples] A specific example of the processing performed by the control unit 102 of the claim matching system 100 in this embodiment will be described with reference to FIGS.

[0041] [3-1. Processing of the matching section] Figure 4 is a diagram showing a flow for explaining an outline of the processing flow of the collating unit 102a of the claim matching system 100 in this embodiment. With reference to Figure 4, an outline of the processing flow of the collating unit 102a of the claim matching system 100 in this embodiment will be described.

[0042] In FIG. 4, the collation unit 102a acquires bond data and expected deposit data from agents 400, . . . of companies A, B, and C, for example, and stores them in the storage unit 106.

[0043] Figure 4(A) shows an example of acquired receivables data, and Figure 4(B) shows an example of acquired forecast sales data. In the example of receivables data shown in Figure 4(A), the first line contains the billing address "Company A," reservation number "Y-SA001K9," name of the person who made the reservation "Suzuki Taro," and amount "¥10,000." In the example of forecast sales data shown in Figure 4(B), the first line contains the billing address "Company A," reservation number "SS7109-SA001-A," name of the person who made the reservation "Suzuki Taro," and amount "¥10,000."

[0044] When matching receivables, you can select whether to match by reservation number or by reservation holder name. Here, we will explain the case where reservation number is selected. For each record of receivables data, a matching key for the reservation number is generated by referencing the billing destination master 106a and the general name master 106b using the billing destination as a key, and matching is performed with the record of the scheduled payment data for the reservation number that includes the generated matching key. The specific method for creating a matching key is explained in Figure 5. Check for any differences and confirm the cause of the difference to ensure that the receivables have been recorded appropriately.

[0045] Figure 4(C) shows an example of matching the amount for Company A by reservation number. Figure 4(C) shows the billing address, reservation number (matching key), reservation number (debt data), reservation number (scheduled payment data), debt amount, payment amount, and difference. For example, the first line has a matching key of "SA001" and a difference of "¥0", while the second line has a matching key of "ZX001" and a difference of "¥20".

[0046] [3-2: Matching key generation] A method for generating a matching key for a reservation number by the matching unit 102a will be described with reference to Figure 5. A matching key for a reservation person's name can also be generated in a similar manner, so a description thereof will be omitted. Also, while a method for generating a matching key based on the reservation number of the bond data will be described here, a matching key may also be generated based on the reservation number of the sales forecast data.

[0047] FIG. 5(A) shows an example of claim data for Agent A (partial excerpt). Company A's reservation number is "Y-SA001K9" on the first line and "B-ZX001F4" on the second line.

[0048] The matching unit 102a uses the billing destination from the billing destination master 106a as a key to obtain the reservation number matching symbol unnecessary flag, reservation number matching start position (required for bond data), and reservation number matching digit count for the reservation number. In this example, the billing destination "Agent A Company" is used as a key to refer to the billing destination master 106a to obtain the reservation number matching symbol unnecessary flag "not required," the reservation number matching start position (for bond data) "2," and the matching digit count "7."

[0049] (S1: Determine whether to use symbols when matching) FIG. 5(B) is a partial excerpt of an example of data in the billing destination master 106a, and FIG. 5(C) is a diagram showing an example in which symbols have been deleted from the reservation numbers of the bond data in FIG. 5(A).

[0050] If the reservation number verification symbol unnecessary flag is "unnecessary", the verification unit 102a deletes the symbols registered in the general name master 106b ("#", "-", and "@" in the example of FIG. 3) from the reservation number. On the other hand, if the reservation number verification symbol unnecessary flag is "required", the verification unit 102a does not delete the symbols registered in the general name master 106b from the reservation number.

[0051] In this example, as shown in Figure 5(B), the reservation number matching symbol not required flag is set to "not required", so as shown in Figure 5(C), the symbol "-" is deleted from "Y-SA001K9" to make it "YSA001K9", and the symbol "-" is deleted from "B-ZX001F4" to make it "BZX001F4".

[0052] The symbols to be deleted can be set and changed in the general name master 106b in response to an operator's operation.

[0053] (S2: Determine the starting position and number of digits when matching) FIG. 5(D) is a partial excerpt of an example of data in the billing destination master 106a, and FIG. 5(E) is a diagram showing an example of a matching key created from the reservation number of the bond data in FIG. 5(A).

[0054] The matching unit 102a extracts the acquired reservation number matching digits from the acquired reservation number matching start position to create a matching key. In this example, as shown in Figure 5(D), the reservation number matching start position (for bond data) is "2" and the reservation number matching digits is "5", so five digits from the second digit are extracted; specifically, "SA001" is extracted from "YSA001K9" and "ZX001" is extracted from "BZX001F4", and these are used as the matching key.

[0055] (S3: The matching key for the reservation number to be used for matching is determined) 5(F) is a diagram showing an example of a confirmed matching key. The matching unit 102a uses the matching key created (confirmed) for each billing destination to match the bond data with the expected payment data.

[0056] [3-3. Payment confirmation inquiry] An example of payment confirmation inquiry processing executed by the collation unit 102a will be described with reference to Figure 6. For example, if a company owns multiple accommodation facilities or accommodation facilities with a large number of rooms, many receivables slips will be recorded. Since matching the receivables data as soon as a payment is received would not be compatible with the customer's closing schedule, operationally, the receivables data is matched with the expected payment data from mid-month. Causes of discrepancies include incorrect recording of receivables due to sale discounts, coupon use, or point use. After identifying the cause of the discrepancy, the accounting department notifies each department and corrects the receivables slips.

[0057] Figure 6 is a diagram showing a display example of the deposit confirmation inquiry screen 500. The content displayed on the deposit confirmation inquiry screen 500 can be output as a file by pressing the output button. In addition, the output file can be cleared in bulk using the "deposit clearing import process."

[0058] For example, on the payment confirmation inquiry screen 500, by specifying "reservation number" as the matching key and extracting and displaying data with the extraction conditions of "existing difference" and the payment cleared excluding check "checked: excluded", it is possible to extract data where payment has not yet been made and there is a difference, and check the cause of the difference. Some agents 400 cannot be matched by reservation number, so in such cases matching is performed by the name of the person who made the reservation. For example, when a payment is made from agent 400 at the end of the month, data with "no difference" can be extracted and output to a file, and the output file can then be cleared all at once using the payment clearing import process.

[0059] The payment confirmation inquiry screen 500 has an extraction condition specification area where extraction conditions such as billing destination, difference (specify whether there is, there is not, or all), collation key (specify reservation number or reservation holder name), difference amount, credit accounting date, reservation number, expected payment date, reservation holder name, payment cleared exclusion check (a box for specifying whether or not cleared payments should be excluded; checked: not applicable, unchecked: applicable) can be specified, and an extraction result display area (credit accounting date, billing destination code, billing destination name, reservation number, etc.) where credit data and expected sales data that meet the extraction conditions are extracted and displayed. The extraction result display area includes a display area where the total of the data displayed in the extraction result display area is displayed (displays the total amount of claims, total amount of deposit, total difference, number of claim vouchers, number of deposit vouchers, etc.), a display button for displaying the extracted data in the extraction result display area, and an output button for the extraction result display area.

[0060] The extraction conditions include the billing destination, the difference (specify whether it is yes, no, or all), the matching key (specify the reservation number or the name of the person who made the reservation), and the receivables accounting date, and all other items are optional. When the extraction conditions are specified and the display button is pressed, the receivables data and sales forecast data stored in the storage unit 106 that meet the extraction conditions are extracted and displayed in the extraction result display area. (As mentioned above, a matching key is created for each billing recipient, and the receivables data and projected sales data that match the matching key are extracted as a pair.)

[0061] In the example shown in the figure, the billing destination "S001: Agent A Company", difference "All", matching key "Reservation number", receivable accounting date "2023 / 07 / 01~2023 / 7 / 15", and payment cleared excluding check "Checked: Excluded" are specified, and the display button is pressed, and the data shown in the figure is displayed in the extraction result display area.

[0062] As explained above, according to this embodiment, there is provided a billing destination master 106a which registers, for each billing destination (agent 400), a no-match flag which specifies whether symbols are to be omitted when matching a reservation number or a reservation party name, the number of matching digits, and the matching start position in association with each other, and a matching unit 102a which, using the billing destination of the bond data as a key, obtains the no-match symbol flag, the number of matching digits, and the matching start position for the reservation number or the reservation party name from the billing destination master 106a, and, if the obtained no-match symbol flag for the reservation number or the reservation party name of the bond data for each billing destination is "not required," deletes the symbols from the reservation number or the reservation party name, extracts the obtained number of matching digits from the obtained matching start position, and creates a matching key, and uses the created matching key to match the bond data with the expected deposit data. This makes it possible to reduce the workload of bond matching and prevent human error.

[0063] [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.

[0064] 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.

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

[0066] 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.

[0067] 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.

[0068] 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.

[0069] Furthermore, with regard to the credit matching system 100, the components shown in the figure are functional concepts, and do not necessarily have to be physically configured as shown in the figure.

[0070] For example, all or any part of the processing functions of the credit matching system 100, particularly the processing functions performed by the control unit, 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 an information processing device to execute the processing described in this embodiment, and is mechanically read by the credit matching system 100 as needed. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to issue instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

[0071] This computer program may also be stored in an application program server connected to the claim matching system 100 via any network, and all or part of it may be downloaded as needed.

[0072] 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.

[0073] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as 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 the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0074] The various databases stored in the memory unit 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.

[0075] The claim matching system 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as such an information processing device connected to any peripheral device. The claim matching system 100 may also be realized by installing software (including programs or data, etc.) on such a device that causes the device to perform the processing described in this embodiment.

[0076] 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. [Explanation of symbols]

[0077] 100 Credit matching system 102 Control section 102a Matching section 102b Master Maintenance Department 102c Screen display control unit 104 Communication interface unit 106 Storage section 106a Billing Master 106b General Name Master 108 Input / Output Interface Section 112 Input Device 114 Output Device 300 Network 400 Agents

Claims

1. A credit matching system equipped with a control unit, The control unit A first master in which a matching unnecessary flag for specifying whether symbols should be omitted when matching a reservation number or a reservation name for each billing destination, the number of matching digits, and a matching start position are associated and registered; Debt data obtained from the billing destination, including billing destination, reservation number, reservation name, and amount; Scheduled payment data obtained from the billing address, including reservation number, reservation name, and amount, The storage area storing the A debt matching system characterized by comprising a matching means for using the billing destination of the debt data from the first master as a key to obtain a matching symbol not required flag, the number of matching digits, and the matching start position for the reservation number or reservation holder name, and for each billing destination, if the obtained matching symbol not required flag for the reservation number or reservation holder name of the debt data is ``not required,'' deleting the symbol from the reservation number or reservation holder name, extracting the obtained number of matching digits from the obtained matching start position to create a matching key, and using the created matching key to match the debt data with the expected deposit data.

2. 2. A credit matching system according to claim 1, wherein the symbols to be deleted are registered in a second master.

3. 3. The credit matching system according to claim 1, wherein the billing destination includes an agent who makes accommodation reservations or facility reservations at the company's facilities.

4. A claim matching method executed by an information processing device having a control unit, The control unit A first master in which a matching unnecessary flag for specifying whether symbols should be omitted when matching a reservation number or a reservation name for each billing destination, the number of matching digits, and a matching start position are associated and registered; Debt data obtained from the billing destination, including billing destination, reservation number, reservation name, and amount; The payment schedule data obtained from the billing address, including the billing address, reservation number, name of the person making the reservation, and the amount, The storage area storing the Executed in the control unit: A receivable matching method characterized by including a matching step of obtaining a matching symbol not required flag, the number of matching digits, and the matching start position for the reservation number or reservation holder name from the first master using the billing destination of the receivable data as a key, and for each billing destination, if the obtained matching symbol not required flag for the reservation number or reservation holder name of the receivable data is "not required," deleting the symbol from the reservation number or reservation holder name, extracting the obtained number of matching digits from the obtained matching start position to create a matching key, and using the created matching key to match the receivable data with the expected deposit data.

5. A claim matching program to be executed by an information processing device having a control unit, The control unit A first master in which a matching unnecessary flag specifying whether symbols should be omitted when matching a reservation number or a reservation name for each billing destination, the number of matching digits, and a matching start position are associated and registered; Debt data obtained from the billing destination, including billing destination, reservation number, reservation name, and amount; The payment schedule data obtained from the billing address, including the billing address, reservation number, name of the person making the reservation, and the amount, The storage area storing the The control unit A debt matching program for executing a matching process that uses the billing destination of the debt data from the first master as a key to obtain a matching symbol not required flag, the number of matching digits, and the matching start position for the reservation number or reservation holder name, and for each billing destination, if the obtained matching symbol not required flag for the reservation number or reservation holder name of the debt data is ``not required,'' deletes the symbol of the reservation number or reservation holder name, extracts the obtained number of matching digits from the obtained matching start position, and creates a matching key, and uses the created matching key to match the debt data with the expected deposit data.

Images