JP2001283116A - Device and method for processing money reception and recording medium for storing money reception processing program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To automatically realize a series of sales money collecting task including transfer confirmation processing, money reception slip issue processing, and reminder issue processing. SOLUTION: This device is provided with a transfer details obtaining means 11 for obtaining transfer details information stored in the prescribed area of a financial institute side computer 3, and for storing the newly obtained transfer details information in a transfer details storing means 12, an input slip issuing means 13 for preparing money reception slip information based on the transfer details information stored in the transfer details storing means 12, a balance storing means 14 for storing balance information including claimed sum information and money reception scheduled date information, and a reminder outputting means 15 for correcting the balance information stored in the balance storing means 14 based on the transfer details information stored in the transfer details storing means 12, and for outputting a reminder based on the corrected balance information.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a payment processing apparatus using a home banking system, a payment processing method, and a recording medium storing a payment processing program, and more particularly to a transfer confirmation processing, a payment slip issuing processing, and a reminder letter. The present invention relates to a payment processing apparatus, a payment processing method, and a recording medium that stores a payment processing program that can automatically perform a series of sales collection operations including processing.

[0002]

2. Description of the Related Art Conventionally, many companies or general consumers (hereinafter referred to as "customers") receive a product or a service when a provider of the product or service (hereinafter referred to as a "provider") is provided. Payment may be made by transferring money to an established financial institution account.

[0003] In other words, in a system in which a computer on the customer side and a computer on the financial institution installed in the financial institution are connected online, the customer can open another account (provided by the provider) from his / her own deposit account or the like. Financial institution account)
When a bank transfer request is made to the financial institution, the computer at the financial institution that received the request transfers the bank transfer (using the computer if the transfer destination account exists in its own financial institution, or the transfer destination to another financial institution). In the case of (2), the request is made to a computer installed in another financial institution using a dedicated line to perform the account transfer processing).

On the other hand, a home banking system that connects a computer of a financial institution and a computer of a company or a general consumer has been commercialized. Typical forms of home banking are voice or facsimile over a telephone line, for checking the balance of a bank account, transferring funds,
A system that can perform telephone shopping and the like has been considered.

In a personal computer banking system, when a customer's personal computer is connected to a bank via a public line, a screen similar to the ATM of the bank is displayed on the personal computer, and the customer is displayed on the personal computer in the same manner as the ATM. According to the instruction, a balance inquiry, transfer, and transfer can be performed.

[0006] In another bank, a balance inquiry service has been started using electronic mail of personal computer communication. In general, as mentioned above, many companies make payments to accounts receivable by transfer to financial institutions, and there are cases where home banking balance confirmation service is used as a method of confirming that the transfer has been completed. .

[0007]

However, the conventional system is of such a level as to confirm whether or not the transfer has been made by confirming the balance, and has introduced a business system such as a sales management system. In the provider side company, it is necessary to manually input the transferred amount as a payment slip.

[0008] In addition, a reminder to be sent in the case where the transfer has not been made even after the scheduled payment date has to be created and sent to the customer as another work by a word processor or the like.

Therefore, there is a problem that a series of receivables collection operations as described above cannot be systematized and performed. An object of the present invention is to enable a series of sales collection operations including a transfer confirmation process, a deposit slip issuing process, and a reminder notice issuing process to be automatically performed.

[0010]

In order to solve the above-mentioned problems, the present invention employs the following configuration. FIG. 1 is a functional configuration diagram of a deposit processing apparatus to which the present invention is applied.

Referring to FIG. 1, a deposit processing apparatus 1 according to the present invention.
Is connected to the network 2 and further connected to the financial institution side computer 3 via the network 2.
Then, the payment processing device 1 can acquire the balance information held by the financial institution side computer 3 using the home banking service.

The payment processing apparatus 1 includes a transfer statement acquisition unit 11, a transfer statement storage unit 12, a payment slip issuing unit 13, a balance storage unit 14, a reminder letter output unit 15,
Display means 16.

According to one aspect of the present invention, the deposit processing apparatus 1 of the present invention is connected to the financial institution side computer 3 via the network 2 and acquires the transfer statement information from the financial institution side computer 3. A transfer statement acquiring unit 11 for storing newly acquired transfer statement information in the transfer statement storage unit 12; and a payment slip issuing unit for creating payment slip information based on the transfer statement information stored in the transfer statement storage unit 12. 13 is provided.

Thus, in a sales collection business in which a customer is billed for the sales of the provided goods and services, the billing amount (amount to be collected) for each customer and the scheduled payment date for each customer Is obtained, it is possible to grasp the sales collection status of each customer (transfer confirmation processing). Also, if sales are collected,
Subsequent payment processing (processing performed in a business system such as a sales management system after collection of payment, which has been performed after manually inputting the transferred amount as a payment slip) is automatically performed. Since this is performed (payment slip issuing process), there is no need to manually create a payment slip after payment collection or to newly input data based on the payment slip.

Further, according to one aspect of the present invention, the deposit processing apparatus 1 of the present invention is connected to the financial institution side computer 3 via the network 2 and stores balance information including billing amount information and scheduled payment date information. Balance storing means 14 for storing;
The transfer statement information is acquired from the financial institution side computer 3, the balance information stored in the balance storage unit 14 is corrected based on the newly obtained transfer statement information, and a reminder is issued based on the corrected balance information. Dunning letter output means 15 to output
And

[0016] Thereby, it is possible to automatically issue a dunning letter (a dunning letter issuance process) to a customer who does not deposit the requested sales even after a predetermined number of days of the expected payment date.
As another work, there is no need to create a reminder by a word processor or the like and send it to the customer.

Further, according to one aspect of the present invention, the deposit processing apparatus 1 of the present invention is connected to the financial institution side computer 3 via the network 2 and acquires the transfer statement information from the financial institution side computer 3. A transfer statement acquiring unit 11 for storing newly acquired transfer statement information in the transfer statement storage unit 12; and a payment slip issuing unit for creating payment slip information based on the transfer statement information stored in the transfer statement storage unit 12. 13, balance storage means 14 for storing balance information including billing amount information and expected payment date information, and balance stored in the balance storage means 14 based on the transfer statement information stored in the transfer statement storage section 12. A reminder output means 15 for correcting the information and outputting a reminder based on the corrected balance information.

In this way, in a sales collection business in which a customer is billed for a price of a provided product or service, information including a billed amount for each customer and a scheduled payment date for each customer is obtained. Therefore, it is possible to grasp the sales collection status of each customer (transfer confirmation processing). Also,
When the sales proceeds are collected, the subsequent payment processing is automatically performed (payment slip issuing processing). Therefore, a payment slip after the collection is manually created or a new payment slip is generated based on the payment slip. Work such as inputting data to the computer becomes unnecessary. In addition, a dunning letter can be automatically issued (a dunning letter issuance process) to a customer who does not receive the invoiced sales even after a predetermined number of days from the expected payment date. Eliminates the need to create and send dunning notices to customers. Further, a series of sales collection operations including a transfer confirmation process, a deposit slip issuing process, and a reminder issuing process can be automatically performed, and the sales collection operation can be smoothly performed.

Also, preferably, the deposit processing apparatus 1 of the present invention.
Further includes a display unit 16 for displaying the transfer details information stored in the transfer details storage unit 12. Preferably, the deposit processing apparatus 1 of the present invention is arranged so that the balance storage means 1
And a display unit 16 for displaying the balance information stored in the storage unit 4.

Preferably, the deposit processing apparatus 1 according to the present invention.
The output of the reminder performed by the reminder output means 15 is
At least sending the reminder by e-mail,
Either facsimile transmission or output to paper media including postcards.

[0021]

Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 2 is a schematic diagram for explaining the present invention.

In FIG. 2, a company A of a customer who has provided a product or service from a provider (our company) transfers the price of the provided product or service from a company A account of a bank 2 in which the company A has opened. The transfer has been made to the Company's account of Bank 1 established by the provider.

The provider obtains the transfer statement information stored in a predetermined area of the computer of the bank 1 via a network, and newly transfers the transfer statement information among the obtained transfer statement information to a transfer statement file. It is stored, and the slip data is created based on the transfer details information stored in the transfer details file.

Further, the provider acquires the transfer statement information stored in a predetermined area of the computer of the bank 1 via a network, and based on the newly acquired transfer statement information among the acquired transfer statement information. The balance information including the billing amount information and the expected payment date information stored in the balance file is corrected, and a reminder is issued based on the corrected balance information.
Output to the company.

FIG. 3 is a hardware configuration diagram of a deposit processing apparatus to which the present invention is applied. In FIG. 3, a deposit processing device is a central processing unit (CPU) 2 that executes various processes.
1, an input unit 22 for inputting data and instructions, a display unit 23 for displaying transfer statement information and the like, and a first transmitting / receiving unit 24 for transmitting / receiving data to / from a financial institution using, for example, a home banking function. And a second transmitting / receiving unit 25 for transmitting and receiving data (for example, facsimile communication and e-mail communication) with the customer, and a RAM 2 for storing programs and the like.
6, a printing unit 27 for printing a dunning notice, etc., and files of “slip data”, “customer data”, “balance”, “transfer statement”, “transfer statement acquisition management data”, and “account management data”. And a storage unit 28 having the same. The central processing unit 21, the input unit 22, the display unit 23, the first transmitting / receiving unit 24, the second transmitting / receiving unit 25, the RAM 26, the printing unit 27,
The storage units 28 are mutually connected by a bus.

FIG. 4 is a diagram showing the data structure of the "slip data" file. The "slip data" file is a file for storing data of a sales slip, a deposit slip, or a transfer slip, and a customer code (NO1) for identifying a customer who has issued each slip, and a slip indicating the date on which each slip was issued. Date (NO2), slip number indicating each slip number (NO
3), a line number (NO4) indicating the number of each item, a slip type (NO5) indicating the type of the slip (whether the sales slip (1) or the payment slip (2)), and the type of the item (sales details) (1) or remittance details (2)), description category (NO6), description (NO7) indicating product name, etc., quantity (NO8) indicating number (amount) of products, etc., Each item has a unit price (NO9) indicating a unit price, and an amount (NO10) indicating a sales amount and a payment amount.

FIG. 5 is a diagram showing the data structure of the "customer information" file. The "customer information" file is a file for storing customer information. A customer code (NO1) uniquely assigned to each customer and a customer name (N
O2), person in charge (NO3) indicating the name of the person in charge of the customer, address (NO4) indicating the address of the customer, telephone number (NO5) indicating the telephone number of the customer, FAX number indicating the facsimile (FAX) number of the customer ( NO6), a mail address (NO7) indicating the e-mail address of the customer, an output form such as a reminder letter to the customer (FAX (1) or e-mail (2), output to paper medium (printer) (3) )
), A scheduled payment date (NO9) indicating a scheduled payment date (eg, 10th, 20th, etc.), and a trading financial institution indicating a trading financial institution with which the customer is trading ( No. 10).

FIG. 6 is a diagram showing the data structure of the "balance" file. The "balance" file is a file for storing the balance of the billing amount and the expected payment date for each customer, and includes a customer code (NO1) uniquely assigned to each customer, and a price of goods and services provided to the customer. The billing amount (NO2), which indicates the total amount charged, the scheduled payment date (NO3), which indicates the date when the customer is to receive a payment (including a transfer), and the date when a reminder was issued in the past. It has the items of the last reminder issue date (NO4) shown.

Here, the scheduled payment date is set in the billing process (the process of billing for the provided goods and services) and the current date (date of performing the billing process) and the scheduled payment date of the “customer information” file. (For example, 10 days, 20 days, etc.) (for example, if the current date is February 24, 2000)
If the expected payment date of the “customer information” file is 20 days, the date is calculated as of March 20, 2000.)

FIG. 7 is a diagram showing the data structure of the "transfer details" file. The “transfer details” file is a file in which the transfer details obtained from the financial institution using the home banking function are stored, and a unique financial institution code (NO1) assigned to the financial institution, a branch of the financial institution, , A transfer date (NO3) indicating the transfer date, a customer code (NO4) indicating the code of the customer who made the transfer, and a customer name (NO5) indicating the name of the customer who made the transfer ) And a transfer amount (NO6) indicating the transfer amount.

Here, the transfer date, customer name, and transfer amount are set with data obtained by the home banking function, and the customer code is searched from the “customer information” file using the obtained customer name as a key. However, if the balances already processed for payment are deleted (if there are balances with the same transfer date as the acquisition date of the “Transfer Detail Acquisition Management Data” file, the number of Delete from the "Details acquisition management data" file).

FIG. 8 is a diagram showing the data structure of the "transfer details acquisition management data" file. The “transfer statement acquisition management data” file is a file for storing information related to acquisition performed by the financial institution using the home banking function, and includes a unique financial institution code (NO1) assigned to the financial institution, The unique branch code (NO2) assigned to the branch, the acquisition date (NO3) indicating the last (previous) date when the transfer details were acquired from the financial institution using the home banking function, and ( Each item has the number of acquired details (NO4) indicating the number of (acquired) transfer details.

The “transfer details acquisition management data” file indicates when the transfer details are acquired from the financial institution using the home banking function, and when the transfer details are acquired, It is used to ensure consistency with the transfer details. That is, when the transfer details are acquired, the current date is set to the acquisition date (NO3), so that in the next acquisition, the details after the acquisition date (NO3) of the “transfer details acquisition management data” file are set. You just need to get it. However, in consideration of the case where a statement is acquired twice or more (several times) on the same date, if there is a transfer statement of the date set on the acquisition date (NO3), the number of the transfer statement is calculated as the number of acquired statements. By setting (NO4), consistency can be maintained.

FIG. 9 shows the data structure of the "account management data" file. The "account management data" file is a file in which the financial institution that has opened the account and its branch are stored, and the unique financial institution code (NO1, NO
3,..., NO (n−1)), a unique branch code (NO) assigned to the branch of the financial institution that has opened the account.
2, NO4,..., NOn).

FIG. 10 is a flowchart for explaining the overall processing of the present invention. First, when a program for executing a deposit processing to which the present invention is applied is started, an initial screen is generated in step S1.

In step S2, the data of the charged amount ("balance": NO2) in the "balance" file is read out.
The customer code (“Balance”: NO1), the billing amount (“Balance”: NO2), and the expected payment date (“Bill”) of the customer whose value is not 0 (yen), that is, the customer who is charging for the provided goods and services. “Balance”: NO3) is acquired. Then, using this customer code as a key, the customer name (“customer information”: NO2) is obtained from the “customer information” file. Acquired customer name (“customer information”: NO2), billing amount (“balance”: NO2), and expected payment date (“balance”:
NO3) is displayed in a list.

In step S3, a check is made as to whether or not payment has been made from the listed customers (transfer confirmation), and a subsequent payment processing (in a business system such as a sales management system, a processing performed after payment collection). Yes, in the conventional system, is the process performed after manually inputting the transferred amount as a deposit slip) (transfer confirmation and deposit process), or after the scheduled deposit date (the predetermined number of days from the scheduled deposit date) Whether to issue a reminder letter to customers who have not received payment (during the lapse) (dunning letter output)
Alternatively, it waits for an instruction input to terminate this program.

If there is an instruction input for the transfer confirmation & payment process in step S3, a transfer statement acquisition process is performed in step S4, and a payment slip issuing process is performed in step S5. The transfer statement obtaining process and the deposit slip issuing process will be described later with reference to FIGS. 11 and 12.

In step S6, the current (step S6)
4), the data of the billing amount (“Balance”: NO2) in the “Balance” file of the listed customers is read, and the customer name (“Customer Information”: NO2) and the billing amount (“ The balance ": NO2) and the scheduled payment date (" balance ": NO3) are displayed again in a list. Then, the process returns to step S3.

If there is an instruction to output a reminder in step S3, a reminder output process is performed in step S7. Then, the process returns to step S3. The reminder letter output process will be described later with reference to FIG.

FIG. 11 is a flowchart for explaining the "transfer statement acquisition process". In step S11, the financial institution code of the financial institution that has opened an account (“account management data”:
.., NO (n−1)) and the branch code of the branch of each financial institution (“account management data”: NO
2, NO4,..., NOn).

In step S12, an address pointer is set at the beginning of the read financial institution code. In step S13, the date of the last (previous) transfer statement acquisition from the financial institution using the home banking function is indicated from the "transfer statement acquisition management data" file having the branch code of the financial institution in which the address pointer is set. Acquisition Date ("Transfer Details Acquisition Management Data": NO
3) and the number of acquired statements (“transfer statement acquisition management data”: NO4) indicating the number of (acquired) deposit statements on the date of last acquisition.

In step S14, it is determined whether date data is stored on the date of acquisition. If it is determined in step S14 that the date data is not stored (step S14: NO), the process proceeds to step S15.
, Use the home banking function to acquire all the transfer details data up to the current date (date of transfer, name or name of transferor, amount of transfer, etc.), and enter the financial institution code Excluding each data (financial institution code, branch code, transfer date, customer name, transfer amount), the corresponding items (financial institution code (NO1), branch code (NO2), transfer date (NO)
3), and output and store the customer name (NO5) and the transfer amount (NO6).

If it is determined in step S14 that date data is stored (step S14: YE
In step S16, using the home banking function in step S16, data of all transfer details from the acquisition date to the current date (date of transfer, name or name of transferor, amount of transfer) Etc.) and obtain the data (financial institution code, branch code,
The corresponding items (financial institution code (NO1), branch code (NO2), transfer date (NO3), customer name (NO)
5), and output and store the transfer amount (NO6).

Then, in step S17, it is determined whether or not the number of acquired statements acquired in step S13 is 0 (zero). If it is determined in step S17 that the number of acquired items is not 0 (step S17: NO), the process proceeds to step S1.
In step 8, the transfer date of the “transfer statement” file having the branch code of the financial institution in which the address pointer is set (“transfer statement”: NO3) is compared with the acquisition date acquired in step S13. Is the same (same day), that is, even if the acquisition of the transfer details using the home banking function in step S14 is the second time (several times) in the same day, the step is taken to avoid data duplication. The acquired statements corresponding to the number of acquired statements acquired in S13 are deleted.

After step S15, after step S18, or when it is determined in step S17 that the number of acquired statements is 0 (step S17: YES), in step S19, the customer name ("transfer statement" file) The customer code (“customer information”: NO1) is searched from the “customer information” file using “transfer details”: NO5) as a key, and set as the customer code (“transfer details”: NO4) in the “transfer details” file ( Store.

In step S20, the number of items having the same date (same day) as the date stored in the transfer date ("transfer details": NO3) of the "transfer details" file is counted.

In step S21, step S13
It is determined whether or not the acquisition date and the current date are the same (same day). If it is determined in step S21 that the acquisition date is the same as the current date (step S21: YES), in step S22, the number of acquired statements in the "transfer statement acquisition management data" file ("transfer statement acquisition management data") : N
The number of items counted in step S20 is added to O4), and the result is stored in the acquired number of items.

If it is determined in step S21 that the acquisition date is not the same as the current date (step S21: NO)
In step S23, the number of statements counted in step S20 is the number of acquired statements in the "transfer statement acquisition management data" file ("transfer statement acquisition management data": NO4).
Is stored as the number of acquired details on the date of the last acquisition.

After step S22 or step S22
23, in step S24, the current date is set as the date on which the transfer details were last acquired using the home banking function to the acquisition date of the "transfer details acquisition management data" file ("transfer details acquisition management data": NO3). Set (store).

In step S25, step S11
It is determined whether or not there is a next financial institution code (account data) among the financial institution codes read out at step S. If it is determined that there is such a code (step S25: YES), step S2 is performed.
In step 6, an address pointer is set next, and the processing from step S13 is repeated. On the other hand, if it is determined that there is no transfer (step S25: NO), the transfer details processing ends.

FIG. 12 is a flowchart for explaining the “payment slip issuing process”. First, step S31
, The first statement is acquired from the “transfer statement” file, and in step S32, it is determined whether the statement is present as data.

If it is determined in step S31 that there is a statement (step S31: YES), in step S33, the customer code of the acquired statement ("transfer statement": N
O4) and all the accounts with the same transfer date (“Transfer Details”: NO3) are acquired from the “Transfer Details” file. On the other hand, if it is determined in step S31 that there is no specification (step S31: NO), the payment slip issuing process ends.

In step S34, step S33
Issue a payment slip based on the statement obtained in (1) (in a business system such as a sales management system, set data necessary for processing to be performed after payment collection). Also, the customer code of the "slip data" file ("slip data": NO1)
The customer code of the customer who issued the slip is output (stored),
The date when the details were acquired (issued) is output on the slip date ("slip data": NO2), and a unique number is automatically issued and output for the slip number ("slip data": NO3) Then, "2" indicating that the slip is a payment slip is output to the slip classification ("slip data": NO5), and "2" indicating that the payment slip is a detail statement in the detail classification ("slip data": NO6).
Is output. Further, in the billing amount (“Balance”: NO2) of the “Balance” file, an amount obtained by subtracting the transferred amount (the transfer amount (NO6) of the “Transfer Details” file) is stored again.

Next, in step S35, the "balance"
It is determined whether or not the charged amount (“balance”: NO2) of the file is 0 (yen). If it is determined in step S35 that the charge amount in the “balance” file (“balance”: NO2) is 0 (yen) (step S35: YES), in step S36, the charge amount in the “balance” file (“ Last reminder issuance date ”: NO4) is NULL (zero)
To On the other hand, when it is determined in step S35 that the charge amount in the “balance” file (“balance”: NO2) is not 0 (yen) (step S35: NO), the charge amount in the “balance” file (“last Issue date ": proceed to the next step with NO4) as it is.

Then, in step S37, the details which are the objects of the processing in steps S31 to S36 described above and are deleted from the "transfer details" file and return to step S31, the number of the received payments is determined. Repeat the slip issuing process.

Steps S35 and S3
The process performed in 6 is a process for controlling the timing of issuing a reminder in the reminder issuing process described below. In other words, data (previous dunning notice issuance date) necessary to prevent the continuous dunning notice from being issued once the condition for issuing the dunning notice is met is set.

FIG. 13 is a flowchart for explaining the "reminder output process". In step S41, step S4 described with reference to FIGS.
(Steps S11 to S26), Step S5
(Steps S31 to S37) and the same processing (pre-processing) as step S6 is performed. However, in step S6, after reading the transfer statement acquisition process in step S4, the data of the billing amount in the “balance” file of the customers displayed in the list is read out, and the customer name, the billing amount, and the expected payment date are listed again. However, in this pre-processing, the data of the billing amount is read not by the customers listed in the list after the transfer statement acquiring process in step S4, but by the customer whose billing amount value in the “balance” file is not 0 yen. Read out the amount.

The pre-processing is not always required to be executed, but can be omitted (skipped). For example, immediately before, the instruction input of the transfer confirmation & payment process in step S3 described with reference to FIG. 10, the execution of the transfer details acquisition process in step S4, the execution of the payment slip issuing process in step S5, and the re-list in step S6 This is the case where the display is performed and the process returns to step S3.

In step S42, the top of the acquired (re-listed) customer is set as the target of the address pointer (the address pointer is set). In steps S43 and S44, the expected payment date ("balance": NO3) and the previous dunning notice issue date ("balance": NO4) are acquired from the "balance" file of the customer for whom the address pointer is set.

In step S45, it is determined whether or not date data is stored on the acquired last dunning notice issuance date. If it is determined in step S45 that the date data is stored (step S45: YES), in step S46, it is determined whether or not the acquired last reminder issuance date has passed 10 days or more from the current date. .

When it is determined in step S45 that the date data is not stored (step S45: N
O) In step S47, it is determined whether or not the acquired scheduled payment date is 10 days or more from the current date.

If it is determined in step S46 that the last dunning notice issuance date has not passed 10 days or more from the current date (step S46: NO), and if the scheduled payment date has passed 10 days or more from the current date in step S47. If it is determined that they have not been performed (step S47: NO), the process returns to step S43.

Steps S46 and S4
At 7, it was determined whether or not 10 days or more had passed. However, the present invention is not limited to 10 days, and may be 5 days or 15 days. That is, it goes without saying that any number of days can be set.

If it is determined in step S46 that the last dunning notice issuance date has passed 10 days or more from the current date (step S46: YES), or if the scheduled payment date has passed 10 days or more from the current date in step S47. If it is determined that there is (Step S47: YES), Step S48
, The customer name (“customer information”: NO) from the “customer information” file of the customer for which the address pointer is set
3) and the name of the person in charge (“customer information”: NO4) are obtained, and the name of the customer and the name of the person in charge are set in the data for creating a dunning notice.

In step S49, the transmission category (“customer information”: NO8) is obtained from the “customer information” file of the customer whose address pointer is set, and in step S50, the transmission category is 1 (FAX). It is determined whether it is 2 (e-mail) or 3 (printer).

If it is determined in step S50 that the transmission category is 1, the process proceeds to step S51.
A facsimile transmission reminder addressed to the customer name and the person in charge set in 49 is created, a fax number (“customer information”: NO6) is obtained from the “customer information” file, and the reminder is faxed to the facsimile number. I do. Then, the current date is stored (rewritten) in the last reminder issuance date (“balance”: NO4) in the “balance” file.

If it is determined in step S50 that the transmission category is 2, in step S52, an e-mail reminder addressed to the customer name and the person in charge set in step S49 is created, and "customer information" An e-mail address (“customer information”: NO7) is obtained from the file, and the reminder is transmitted to the (e-mail) e-mail address. Then, the date of the last dunning notice in the “Balance” file (“Balance”:
The current date is stored (rewritten) in NO4).

If it is determined in step S50 that the transmission category is 3, in step S53, a paper medium output reminder addressed to the customer name and the person in charge set in step S49 is created, and the printer sends it to the printer. Output (print). Then, the current date is stored (rewritten) in the last reminder issuance date (“balance”: NO4) in the “balance” file. Note that a plurality of types of formats are prepared for the paper medium reminder in accordance with the paper (paper medium) size. Specifically, the sizes and postcard sizes of the A series and the B series of the Japanese Industrial Standard are prepared. In the case of a postcard size, it is also possible to print the name of the customer and the person in charge as an address on one side and the text of a reminder on the other side.

When the reminder is output in step S51, step S52, or step S53, the process proceeds to step S54.
In step S55, the next customer is set as the target of the address pointer, and in step S55, it is determined whether there is a next customer to be the target of the address pointer.

When there is a next customer to be addressed by the address pointer in step S55 (step S55: YES)
Repeats the processing from step S43. If not (step S55: NO), the dunning notice output process ends.

FIG. 14 is a display example of the balance list before the transfer statement obtaining process and the deposit slip issuing process. The payment processing device reads out the data of the charged amount in the “balance” file,
The customer code of the customer whose value is not 0 (yen), billing amount,
And the expected payment date is acquired, and the customer name is acquired from the “customer information” file using the customer code as a key. Then, XX store and XX store as acquired customer names, XX store is 10,000 yen, and XX store is 20
000 yen, XX store on February 10, 2000, and OO store on February 20, 2000 as a scheduled payment date.

FIG. 15 shows a display example of the balance list after the transfer statement obtaining process and the deposit slip issuing process. When the transfer confirmation & payment processing instruction input is performed, the payment processing apparatus receives payments from customers (in the case of FIG. 14, XX store and XX store) in the list display as shown in FIG. After confirming whether or not the payment has been made, the payment processing is performed, and the data of the charged amount in the “balance” file of the XX store and the XX store listed as shown in FIG. XX store and XX store, XX store is 0 yen, XX store is 20,000 yen,
As a scheduled payment date, XX store will be on February 10, 2000.
XX stores redisplay February 20, 2000.

FIG. 16 is a display example of the balance list before the dunning notice output process. The deposit processing device displays the current date of 200
When an instruction to output a reminder is input on March 10, 2008, the data of the charged amount in the "balance" file is read out,
The customer code of the customer whose value is not 0 (yen), billing amount,
And the expected payment date is acquired, and the customer name is acquired from the “customer information” file using the customer code as a key. Then, a list of XX stores as the acquired customer names, 20,000 yen as the billing amount, and February 20, 2000 (elapsed 10 days or more from the current date (the current date)) as the scheduled payment date is displayed.

FIG. 17 is an output example of a reminder. As for the input / output device, as shown in FIG.
○○○ listed as customers over 0 days old
A dunning letter addressed to the store and the name of the person in charge, XXXXX, is created and output by, for example, a printer.

As described above, the embodiment of the present invention has been described with reference to the drawings. However, if the function of the deposit processing apparatus to which the present invention is applied is executed, The present invention is not limited to the embodiment, and may be a single device, a system including a plurality of devices, an integrated device, or a system in which processing is performed via a network such as a LAN or a WAN. Needless to say.

Further, a CPU connected to the bus, a memory such as a ROM or a RAM, an input device, an output device, an external recording device,
The present invention can also be realized by a system including a medium driving device, a portable recording medium, and a network connection device. That is, a ROM or RAM memory that records software program codes for realizing the system of the above-described embodiment,
Needless to say, the present invention is also achieved by supplying the external recording device and the portable recording medium to the deposit processing device, and reading and executing the program code by the computer of the deposit processing device.

In this case, the program code itself read from the recording medium realizes the novel function of the present invention, and a portable recording medium or the like on which the program code is recorded constitutes the present invention. .

As a portable recording medium for supplying the program code, for example, a floppy (registered trademark) disk, hard disk, optical disk, magneto-optical disk,
CD-ROM, CD-R, DVD-ROM, DVD-R
AM, magnetic tape, nonvolatile memory card, ROM
Various recording media recorded via a network connection device (in other words, a communication line) such as a card, electronic mail, and personal computer communication can be used.

The functions of the above-described embodiment are realized by the computer executing the program code read out on the memory, and the OS running on the computer is executed based on the instructions of the program code.
Perform part or all of the actual processing, and the functions of the above-described embodiments are also realized by the processing.

Further, after the program code read from the portable recording medium is written to a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, the program code is transmitted to the instruction of the program code. Based on this, the CPU or the like provided in the function expansion board or function expansion unit performs part or all of the actual processing, and the functions of the above-described embodiments can also be realized by the processing.

That is, the present invention is not limited to the above-described embodiment, and can take various configurations or shapes without departing from the gist of the present invention.

[0083]

As described above, according to the present invention, in a sales collection business in which sales are billed to customers in consideration of provided goods and services, the billing amount (collection) for each customer is collected. Since the information including the amount to be paid) and the expected payment date for each customer is displayed in a list on the same screen, the sales collection status for each customer can be grasped at a glance (transfer confirmation processing).

Further, according to the present invention, when the sales proceeds are collected, the subsequent payment processing (in the business system such as the sales management system, the processing is performed after the collection of the payments, The processing performed after the entered amount is manually input as a payment slip) is automatically performed (the payment slip issuance processing), so that a payment slip after the collection of the payment is manually created or based on this payment slip. This eliminates the need for inputting new data.

According to the present invention, it is possible to automatically issue a reminder (a reminder issuing process) to a customer who does not pay the requested sales even after a predetermined number of days has passed the expected payment date. This eliminates the need to create a dunning letter with a word processor or the like and send it to the customer as another task.

Further, according to the present invention, the transfer confirmation processing,
A series of sales collection operations including the payment slip issuing process and the dunning notice issuance process can be automatically performed, and the sales collection process can be performed smoothly.

[Brief description of the drawings]

FIG. 1 is a functional configuration diagram of a deposit processing apparatus to which the present invention is applied.

FIG. 2 is a schematic diagram for explaining the present invention.

FIG. 3 is a hardware configuration diagram of a deposit processing apparatus to which the present invention is applied.

FIG. 4 is a diagram showing a data structure of a “slip data” file.

FIG. 5 is a diagram showing a data structure of a “customer information” file.

FIG. 6 is a diagram showing a data structure of a “balance” file.

FIG. 7 is a diagram showing a data structure of a “transfer details” file.

FIG. 8 is a diagram showing a data structure of a “transfer details acquisition management data” file.

FIG. 9 is a diagram showing a data structure of an “account management data” file.

FIG. 10 is a flowchart for explaining the overall processing of the present invention.

FIG. 11 is a flowchart illustrating a “transfer statement acquisition process”.

FIG. 12 is a flowchart for explaining “payment slip issuing process”;

FIG. 13 is a flowchart for explaining a “reminder letter output process”.

FIG. 14 is a display example of a balance list before a transfer statement obtaining process and a deposit slip issuing process.

FIG. 15 is a display example of a balance list after a transfer statement obtaining process and a deposit slip issuing process.

FIG. 16 is a display example of a balance list before a dunning notice output process.

FIG. 17 is an output example of a reminder.

[Explanation of symbols]

 REFERENCE SIGNS LIST 1 payment processing device 2 network 3 financial institution side computer 11 transfer statement acquisition means 12 transfer statement storage means 13 payment slip issuing means 14 balance storage means 15 reminder letter output means 16 display means 21 central processing unit (CPU) 22 input unit 23 display Unit 24 first transmitting / receiving unit 25 second transmitting / receiving unit 26 random access memory (RAM) 27 printing unit 28 storage unit

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) G07D 9/00 451 G07D 9/00 451B 451C F term (Reference) 3E040 BA12 BA18 CA11 CA14 CA17 CB01 CB04 EA01 EA02 5B049 AA01 BB11 BB46 CC05 CC36 DD00 DD01 EE00 FF02 GG04 GG07 5B055 BB16 CB03 CB08 CB09 EE02 EE27 FA01 9A001 JJ65 JJ75 JZ14 KK58 KK62

Claims (10)

[Claims] 1. A payment processing apparatus connected to a financial institution computer via a network, wherein the transfer details information is obtained from the financial institution side computer, and the newly obtained transfer details information is stored in the transfer details storage means. A payment processing device, comprising: a transfer statement acquisition unit; and a payment slip issuing unit that generates payment slip information based on the transfer statement information stored in the transfer statement storage unit. 2. A payment processing apparatus connected to a computer at a financial institution via a network, comprising: balance storage means for storing balance information including billing amount information and scheduled payment date information; A reminder letter output means for acquiring information, correcting balance information stored in the balance storage means based on newly acquired transfer statement information, and outputting a reminder letter based on the corrected balance information. A deposit processing device. 3. A deposit processing device connected to a financial institution computer via a network, wherein the transfer statement information is acquired from the financial institution computer, and the newly acquired deposit statement information is stored in the deposit statement storage means. Transfer statement obtaining means, payment slip issuing means for creating payment slip information based on the transfer statement information stored in the transfer statement storage means, and balance storage for storing balance information including billing amount information and scheduled payment date information Means, correcting the balance information stored in the balance storage means based on the transfer statement information stored in the transfer statement storage means,
A payment processing device, comprising: a reminder letter output means for outputting a reminder letter based on the corrected balance information. 4. The payment processing apparatus according to claim 1, further comprising a display unit for displaying the transfer statement information stored in the transfer statement storage unit. 5. The apparatus according to claim 2, further comprising display means for displaying balance information stored in said balance storage means.
Or the deposit processing apparatus according to 3. 6. The reminder output performed by the reminder output means is at least one of sending the reminder by e-mail, transmitting by facsimile, or outputting to a paper medium including a postcard. 6. The deposit processing apparatus according to claim 2, wherein the deposit processing apparatus is provided. 7. A transfer statement information is acquired from a financial institution side computer via a network, and newly acquired transfer statement information of the acquired transfer statement information is stored in a transfer statement storage unit, and the transfer statement storage is performed. A payment processing method, wherein payment slip information is created based on the transfer details information stored in the means. 8. A transfer amount information obtained from a financial institution side computer via a network, and a charge amount stored in a balance storage means based on newly obtained transfer details information among the obtained transfer details information. A payment processing method comprising: correcting balance information including information and expected payment date information; and outputting a reminder letter based on the corrected balance information after the correction. 9. A procedure for acquiring transfer statement information from a financial institution side computer via a network, a procedure for storing newly acquired transfer statement information among the acquired transfer statement information in a transfer statement storage means, A step of creating payment slip information based on the transfer details information stored in the transfer details storage means. 10. A procedure for obtaining transfer statement information from a computer at a financial institution via a network, wherein the transfer statement information is stored in a balance storage unit based on newly acquired transfer statement information among the acquired transfer statement information. A recording medium recording a payment processing program, comprising: a procedure for correcting balance information including billing amount information and expected payment date information; and a procedure for outputting a reminder based on the corrected balance information after correction.