JP3333126B2 - Accounting system with automatic journalizing function for transfer payment data - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to an accounting system for automatically retrieving billing data of a billing source that matches transfer data from a financial information network.

[0002]

2. Description of the Related Art When a company A as a billing source (also referred to as a payee) requests a payment from a company B as a billing destination (hereinafter also referred to as a business partner), an accounting worker of the company A uses a computer. Create an invoice (invoice date, transfer date, supplier name, invoice source transfer account number, invoice amount, etc.) for company B and send it to company B, generate an A / R slip, and create a ledger (collectively (Also called billing data).

[0003] When the accounting worker of company B receives the invoice from company A, it checks the contents, and if it is an appropriate invoice, the payment request from the main bank of company B contains the invoice from company B. Write the amount, etc. (payment side transfer date, payment side name, payment side transfer account number, transfer amount, payee name, payee account number), bring it to the main bank of Company B, and transfer it to the payment ledger. .

The main bank of Company B checks whether the amount of the transfer request form of Company B is in the account of Company B, and if so, the amount is transferred to the designated bank of Company A on the transfer date. Transfer to.

The bank of the company A notifies the company A that a transfer has been made from the main bank of the company B. This notification notifies the transfer date, the company name, and the transfer amount.

[0006] On the other hand, the accounting employee of the company A receives the transfer information (the transfer date, the transfer amount,
The transfer company name) and the billing data were manually checked (also referred to as a matching process) to confirm the transfer.

[0007] Generally, this confirmation is generally made by deducting a transfer fee, etc., so the accounting worker of the company A adds the transfer fee, etc. to the transfer amount of the transfer information, and the total is charged. When there was a transfer that was in the billing amount when it matched the amount, the reconciliation process from the ledger was performed.

Further, when the transfer amount and the bill amount match, a journal entry slip is raised as a transfer fee bearer's burden, and the process of clearing from the ledger has been performed.

[0009]

However, since the matching process in the conventional method as described above is performed manually by the accounting worker, there is a problem that the number of working steps of the accounting worker increases. Was.

[0010] Further, when there are a plurality of kinds of bills from the company A to the company B, the company B generally transfers the total amount of the billing slips to the bank by the transfer date.

[0011] For this reason, the accounting worker of the company A calculates each amount of the plurality of invoices from the total amount recorded in the passbook, and deducts the commission etc., so that the total amount recorded in the passbook is the billing data. Must be matched.

[0012] In particular, since the transfer destination name, date, and amount often differ slightly, it has been difficult to convert the matching business into a computer.

Therefore, it is desirable that the billing source be an accounting system that can automatically assign the billing data relating to the transfer amount from the billing party even if there are a plurality of billing data for the billing party.

[0014]

SUMMARY OF THE INVENTION The present invention provides an accounting system with an automatic journalizing function for transfer data, in an accounting system in which a financial information network that enables inquiries of transfers and transaction contents is connected to a billing host. A plurality of invoice files preliminarily storing a plurality of billing information including billing information including billing information including a date and a supplier name and billing data including billing amounts of the billing parties; A transfer schedule file in which the billing information and the transfer schedule data are stored in association with each other, and the monthly billing information is searched from the bill file, and the bill data having the same transaction name as the billing information is retrieved. All of them are searched, and the scheduled transfer amount obtained by summing up the amounts of the monthly bill data and the scheduled transfer data including the billing destination information are stored in the transfer scheduled file in advance. When transfer data including a date, a transfer destination name and an amount is input from the billing destination via the transfer information data generation unit and the financial information network, the transfer schedule having a business partner name that matches the transfer data is input. A matching processing unit that determines whether data exists in the scheduled transfer file; and if the matching processing unit determines that there is scheduled transfer data that matches the scheduled transfer data, the matching processing unit determines that the match exists from the bill file. The gist of the invention is to provide a bill data clearing unit for clearing bill data having a billing destination name of the scheduled transfer data.

[0015]

<First Embodiment> FIG. 1 is a schematic configuration diagram of an online accounting system according to a first embodiment of the present invention. As shown in FIG. 1, the accounting system 1 of the billing company A includes terminals 2a, 2b,.
(Hereinafter simply referred to as a host), and the accounting system 1 is connected to the firm banking 4 (hereinafter referred to as F
B4) through a dedicated line 5.

The host 3 of the company A has the company B,
C, .... Scheduled transfer data based on the billing slip (scheduled transfer date, transfer date, supplier name, billing source transfer account number,
The expected amount of money to be received, etc.) is generated, and the company A
Is received, and the file is searched for the scheduled transfer data that matches the transfer data.

Then, it is automatically checked whether or not a transfer fee is included in the transfer amount of the transfer data. If the transfer amount is appropriate, the transfer amount of the company B, C,... Check for a match. Then, when all of them match, a billing data clearing process is performed.

The above-mentioned determination of the match between the transfer amount and the expected deposit amount is made by obtaining a value qi obtained by subtracting the transfer amount from the expected deposit amount, and then subtracting the qi from the expected deposit amount to obtain a new expected deposit amount. It is determined by comparing with the transfer amount.

<Structure of Host 3> FIG. 2 is a schematic structural view of an embodiment of the host 3 of the present invention. As shown in FIG. 2, the host 3 stores the invoice slip data Fi (invoice date, transfer date, supplier name, transfer account number of billing source, billing amount, etc.) for the billing party as shown in FIG. And a transfer schedule data generation unit 8 that converts the bill slip data Fi of the bill file 6 into transfer schedule data Hi in a predetermined format and stores the same in the transfer schedule file 7.

The transfer data reading unit 11 reads the transfer data Ki from the FB 4 and stores the transfer data Ki in the temporary receiving file 10, and corresponds to the transfer data Ki (also referred to as temporary receiving data) of the temporary receiving file 10. A matching processing unit 12 for searching for the scheduled transfer data Hi to be transferred; a billing data clearing unit 13 for performing a clearing process on billing data related to the scheduled transfer data Hi searched by the matching processing unit 12; And a journal voucher generation unit 14 for generating journal voucher data (including a commission) of the transfer amount corrected in 12. This journal entry slip can be issued from the printer 15.

<Explanation of Each Part> The bill slip data Fi stored in the bill file 6 is created by an accounting worker of the company A, which is the billing source, and includes a supplier code fa,
Billing source account number fb, billing amount fc, and transfer date fd
And a supplier name fe, and are stored in plurals for each supplier code.

The transfer schedule data generation unit 8 calculates the bill slip data Fi having the same supplier code from the bill file 6.
, And the transfer schedule data Hi (scheduled transfer date, transfer date, transaction) in which the sum total of the billing amounts fc (F1 is fc1, F2 is fc2,...) Of the invoice slip data Fi is written. A destination name, a transfer account number of a billing source, a scheduled payment amount, etc.) are generated and stored in the scheduled transfer file 7.

That is, when the bill file 6 stores the bill form data F1 and F2 of the company A as the billing source, as shown in FIG. 3A, for example, FIG. As shown in (1), the billing amounts fc1 and fc2 of these billing slip data are added, and one piece of scheduled data Pi with the payment date as the payment month is generated.

When the schedule data Pi is stored in the scheduled transfer file 7, as shown in FIG. 4, the supplier code ha, the billing account number hb, the scheduled transfer amount hc,
It is stored as transfer scheduled data Hi of a record including the scheduled payment date hd and the supplier name he.

However, the scheduled transfer amount hc is the transfer amount hca
And the commission hcb, and the supplier name he is composed of a plurality of expressions. For example, if the billing source is Company A,
The customer who is the billing party is "BBS (hereinafter simply BB
S)), the business name 1 is "Business
"Brain Ota Showa", and "BB"
S ", and" Business Brain Ota Showa ",. In other words, the billing source stores a plurality of types of business partner names in katakana.

The matching processing unit 12 includes a scheduled transfer data search unit 20, a scheduled transfer amount correcting unit 21, and a checking unit 22.

The transfer schedule data search means 20 receives the transfer data Ki (transfer amount kc on the transaction side, transfer date k on the transaction side).
d, the supplier name ke) is imported into the transfer file 10, and the transfer month kb of the transfer data Ki and the supplier name k
The transfer schedule data Hi matching e is allocated from the transfer schedule data file 7.

For example, when the supplier name ke of the transfer data Ki is [BBS], the supplier name 1 of the supplier name he of the transfer schedule data Hi is set to " Business Brain Ota Showa ", Supplier Name 2 is written as" BBS ", and Supplier Name 3 is written as" Business Brain Ota Showa ", etc., matches when compared with the second Supplier Name 2. I do.

If the estimated transfer amount hc of the expected transfer data Hi assigned by the expected transfer data search means 20 does not match the estimated transfer amount kc of the transfer data Ki, the estimated transfer amount hc is calculated. From transfer amount kc
After obtaining the value qi obtained by subtracting
It judges whether it is within the range, and in the case of the commission hcb range, a value subtracted from the estimated transfer amount hc is used as a new estimated deposit amount hc.
And

The collation unit 22 calculates the scheduled transfer amount h of the scheduled transfer data Hi assigned by the scheduled transfer data search unit 20.
By comparing c with the transfer amount kc of the transfer data Ki, it is determined whether both amounts match.

The billing data clearing unit 13 reads the journal slip data generated by the journal slip generating unit 14 and performs a clearing process on the billing data related to the journal slip data.

When the journal slip generation unit 14 determines that the value qi obtained by the scheduled transfer amount correcting unit 21 of the matching processing unit 12 matches the commission hcb, the journal slip generation unit 14 calculates the transfer amount using the above-mentioned value qi as the commission. The journal slip data is generated and transmitted from the printer 15.

The operation of the accounting system configured as described above will be described below. 5, 6, 7, and 8
5 is a flowchart illustrating the operation of the accounting system according to the first embodiment.

The transfer schedule data generator 8 of the host 3 reads the bill file 6 (S1), searches the bill slip data Fi having the same supplier code (S2), and checks the bill slip of the same supplier code. It is determined whether a plurality of data Fi are stored (S3).

If it is determined in step S3 that there is a plurality of invoice slip data Fi having the same supplier code,
These invoice slip data Fi (Fi: F1, F2,
..) Are summed up (S4).

Next, the schedule data Pi as shown in FIG. 3B is generated by removing the date from the transfer date of each billing slip data Fi (S5), and this transfer schedule file 7 When storing the data Pi, as shown in FIG. 4, the supplier code ha, the biller account number hb, and the scheduled transfer amount h
c, the scheduled payment date hd, and the name of the supplier, he, are stored in advance as the scheduled transfer data Hi (S6).

Next, it is determined whether or not the invoice file 6 has any difference from the invoice slip data Fi of the supplier code searched in step S2 (S7). , And updates the billing slip data Fi of the different supplier code to return to step S2.

On the other hand, in the transfer schedule data searching means 20 of the matching processing unit 12, the transfer data reading unit 11 determines that the transfer data Ki (the billing source account number kb, the transfer amount kc on the business partner side, the business partner name ke) from the FB 4 Is received and stored in the temporary file 10, the transfer data Ki is allocated as shown in FIG. 6 (S10).

Then, the process reads the supplier name ke of the transfer data Ki (S11), and allocates the transfer schedule data Hi having the supplier name he that matches the supplier name ke from the transfer schedule file 7. (S12). This allocation processing will be described with reference to FIG.

In this allocation processing, as shown in FIG. 7, the supplier name he of the scheduled transfer data Hi is set (S12a).
This supplier name he and the supplier name ke of the transfer data Ki
Are compared (S12b), and it is determined whether both names match (S12c).

If it is determined in step S12c that both names do not match, it is determined whether or not there is another supplier name hi in the scheduled transfer data Hi (S12d). If there is another supplier name hi in step S12d, the supplier name is updated to that supplier name hi (S12e) and the process is performed in step S12d.
Returning to 12a, the names are compared.

If there is no other supplier name he in step S12d, the fact that the names do not match is notified (S12f). Further, step S12c
If it is determined that the two names match, it notifies that both names match (S12g).

Next, as shown in FIG. 6, the collating means 22 determines the month of the transfer date kd of the transfer data Ki and the scheduled transfer data H
It is compared with the month hd of i (S13), and it is determined whether both months match (S14). If it is determined in step S14 that the months coincide with each other, the estimated payment amount hc of the corresponding scheduled transfer data Hi and the transfer amount kc of the transfer data Ki are compared (S15), and it is determined whether both amounts match. A determination is made (S16).

If both amounts match in step S16, the journal voucher generator 14 generates journal voucher data (S17). Next, the billing data clearing unit 13
Uses the journal slip data to apply the billing data (S18). In this reconciliation process, for example, the billing amount for the BBS in December is 500,000 in the ledger.
In the case where there is the first billing data and the second billing data with the billing amount of 500,000, if the BBS receives a transfer of 1,000,000 in December, the first billing data will be The second billing data refers to processing for setting the balance to "0" when the transfer amount is 500,000 and the balance "0" for the transfer amount of 500,000.

If it is determined in step S14 that the month of the scheduled transfer data Hi and the month of the transfer data Ki do not match, another process (such as a non-invoice payment process) is performed, and the process ends (step S14). S19).

If it is determined in step S16 that the expected payment amount hc of the scheduled transfer data Hi does not match the estimated transfer amount kc of the transfer data Ki, the transfer schedule correcting means 21 changes the transfer schedule as shown in FIG. , Transfer scheduled data H
Transfer amount k of transfer data Ki from expected transfer amount hc of i
A value qi obtained by subtracting c is calculated (S21). Then, it is determined whether or not the qi is within the range of the commission hcb (whether or not it is appropriate) (S22). Next, when it is determined that the commission hcb is appropriate, a value obtained by subtracting qi from the scheduled transfer amount hc is set as a new scheduled deposit amount hc (S23). In the above-mentioned fee determination, for example, when the transfer amount is less than 30,000 yen and the shortage amount is 500 yen or less, the shortage amount is set as the fee.
When the transfer amount is 30,000 yen or more and the shortage amount is 1,000 yen or less, the shortage amount is determined as a fee.

Then, the collation unit 22 again compares the scheduled transfer amount fc of the transfer schedule data Hi of the transfer schedule file 7 assigned by the transfer schedule data search unit 20 with the transfer amount kc (S24). In this case, the transfer amount kc of the transfer data Ki is determined to be within the transfer amount range (S2).
5). Then, the process returns to step S17 in FIG. 6 to generate journal entry slip data of a fee as shown in FIG.

That is, the accounting system searches for invoice slips of the same business partner (a in FIG. 10), and prepares in advance transfer schedule data Hi in which the invoice amounts of these invoice slips are totaled (FIG. 10). 10b). In (a) and (b) of FIG. 10, transfer scheduled data Hi is stored in advance in which the billing slip data F1 and F2 with the billing amount of 500,000 are summed up (1,000,000). Indicates that

Then, as shown in FIG.
The transfer amount kc of the transfer data Ki from No. 4 is 999, 47
When the number is input at 5, as shown in FIG.
It is calculated as 00,000-999,475 = 525 (fee), and 5 is calculated from the scheduled transfer amount hc (1,000,000).
25 minus the new transfer amount hc (999, 47
Check again as 5).

That is, if there is a transfer from the supplier in the scheduled transfer month, the name of the transferor (supplier side) matches one of the prepared transferor (supplier side) names, and If the amount kc is within the transfer amount range in consideration of the fee, it is determined that the transfer data is the transfer scheduled data Hi.

Then, as shown in FIG. 10 (e), the billing slip data F1 (billing amount 500,000) and billing slip data F2 (billing amount 500,000) of the billing destination are erased. .

<Second Embodiment> FIG. 11 is a flowchart for explaining the outline of a second embodiment. As shown in FIG. 11, in the second embodiment, the account number of the transfer data Ki matches the account number of the scheduled transfer data Hi (S30), and it is determined whether the transfer amount of the transfer data Ki is within the transfer amount range (S31). ) And whether the payment date of the transfer data Ki is within the range of the payment date of the transfer data Hi (S3).
After performing 2) and the determination of the supplier name (S33), the reconciliation process (S34) is performed.

For this reason, as shown in FIG. 12, the transfer schedule data Hi includes a supplier code ha, a supplier account number hb,
Expected transfer amount hc, expected payment date hd, supplier name he
Is stored as the scheduled transfer data Hi of the record provided with the adjustment range date hf.

The adjustment range day hf is composed of hfa two days before and hfb two days after. In other words, the adjustment range day takes into account Saturday and Sunday.

FIGS. 12, 13 and 14 show a second embodiment.
3 is a flowchart for explaining the operation of the accounting system of FIG.

The matching processor assigns the transfer data Ki (the billing source account number kb, the transfer amount kc, the transfer date kd of the business partner, the business partner name ke, etc.) (S40).

The transfer data Ki and the supplier name ke are read (S41), and the transfer schedule data Hi that matches the supplier name ke is transferred to the transfer schedule file 7 in the same manner as in the first embodiment. (S42). next,
The transfer date Ki of the transfer data Ki and the scheduled transfer data Hi
Is compared with the expected payment date hd (S43), and it is determined whether both dates coincide (S44). If it is determined in step S44 that the dates match, the expected payment amount hc of the matching transfer data Hi and the transfer amount kc of the transfer data Ki are compared (S45).
It is determined whether both amounts match (S4
6). If both amounts match in step S46, journal entry slip data is generated, and a reconciliation process is performed on the billing data using the journal slip entry data (S
47).

In step S44, the expected payment date h
If d does not match the transfer date kd from the business partner, as shown in FIG. 14, whether the adjustment date hf of the scheduled transfer data Hi has been added to the transfer date kd of the transfer data Ki. Is determined (S50).

If it is determined in step S50 that the adjustment date hf has not been added, the adjustment date hf (two days before or two days after) is added to the transfer date kd (S51), and the process proceeds to step S51. Returning to S43, the scheduled payment date and the transfer date are compared again.

If it is determined in step S50 that the adjustment date hf has been added, it is determined whether or not there is another scheduled transfer data Hi in the scheduled transfer file 7 (S5).
2).

In step S52, if there is no other scheduled transfer data Hi, another process similar to that of the first embodiment is performed (S53), and this process ends.

When it is determined in step S52 that there is another scheduled transfer data Hi, the process returns to step S42 to compare the other scheduled transfer data Hi with the read-in transfer data Ki.

Further, if it is determined in step S46 that the two amounts do not match, as shown in FIG. 14, the value qi obtained by subtracting the transfer amount kc of the transfer data Ki from the transfer amount hc of the transfer expected data Hi. Is calculated (S61). Then, it is determined whether this qi is within the commission hcb range (whether or not it is appropriate) (S62). next,
A value obtained by subtracting qi from the estimated transfer amount hc for which the commission hcb is appropriate is set as a new expected transfer amount hc (S63).

Then, the estimated transfer amount fc and the transfer amount kc of the scheduled transfer data Hi of the allocated transfer schedule file 7
(S64), and if they match, the transfer amount k of the transfer data Ki is determined to be within the transfer amount range (S6).
5). Then, the process returns to step S47 in FIG. 13 to perform a process for automatically issuing a journal slip as shown in FIG. That is, matching is performed on the two days before and after the scheduled payment date as an error range.

[0065]

As described above, according to the present invention, a month and a month are stored in a bill file in which a plurality of bill data in which a date, a business partner name, and a bill amount are associated (associated) are stored. Retrieve all invoice data that matches the supplier name, sum up the amounts of these invoice data, and set the total amount, month and supplier name (invoice information) to be the transfer schedule data of the invoice destination for the month Is stored in the transfer schedule file. Then, when transfer data including the date, the transfer destination name, and the amount is input from the billing destination via the financial information network, transfer schedule data having a business partner name that matches the transfer data exists in the transfer schedule file. It is determined whether or not there is matching transfer schedule data, and if it is determined that the corresponding transfer schedule data exists, the bill data is erased from the bill file.

[0066]

Accordingly, since the accounting worker does not need to intervene in the matching processing work, the effect of reducing the number of work steps of the accounting worker is obtained.

[Brief description of the drawings]

FIG. 1 is a schematic configuration diagram of an online accounting system according to a first embodiment.

FIG. 2 is a schematic configuration diagram of a terminal of a billing source.

FIG. 3 is an explanatory diagram illustrating processing of a transfer schedule data generation unit.

FIG. 4 is an explanatory diagram of transfer schedule data.

FIG. 5 is a flowchart illustrating an operation of a scheduled transfer data generation unit.

FIG. 6 is a flowchart illustrating an operation of a matching processing unit.

FIG. 7 is a flowchart illustrating allocation by name.

FIG. 8 is a flowchart illustrating an operation of a matching processing unit.

FIG. 9 is an explanatory diagram of a journal entry slip.

FIG. 10 is an explanatory diagram illustrating the concept of the second embodiment.

FIG. 11 is a flowchart illustrating the concept of the second embodiment.

FIG. 12 is an explanatory diagram of transfer schedule data according to the second embodiment.

FIG. 13 is a flowchart illustrating details of the second embodiment.

FIG. 14 is a flowchart illustrating details of a second embodiment.

[Explanation of symbols]

 4 FB 6 Invoice file 7 Transfer scheduled file 8 Transfer scheduled data generation unit 10 Transfer file 11 Transfer data reading unit 12 Matching processing unit 13 Transfer scheduled data deletion unit 14 Adjustment slip generation unit

────────────────────────────────────────────────── ─── Continuation of the front page (56) References JP-A-8-297709 (JP, A) NELSON, Stephen L. , Microsoft Money: Guide to Personal Finance, Microsoft Press, 1996.06 (2nd ed.), (Pp.128-130) LYONS, Daniel, "HKM use EDI tonice Republic of Korea. , Vol. 17, no. 17, 1995. 04.24, p. 80 (58) Field surveyed (Int. Cl. ⁷ , DB name) G06F 17/60 G06F 19/00

Claims (8)

(57) [Claims] 1. An accounting system in which a financial information network capable of making a transfer and inquiring of transaction contents is connected to a host of a billing source, wherein the host makes a request to a billing destination consisting of a date and a business partner name. A bill file in which a plurality of invoice files are stored in advance in which billing information including billing information including billing information of the billing party; and a scheduled transfer file in which the billing party information and the scheduled billing data are relatedly stored. And retrieving the monthly billing information from the bill file, retrieving all bill data with the same transaction name as the billing information, and summing up the amounts of these monthly bill data. A transfer schedule data generating unit that associates the transfer schedule data including the amount and the billing destination information with each other and stores the data in the transfer schedule file in advance; and the billing destination via the financial information network. When the transfer data including the transfer date and the transfer destination name and the amount is input, a matching processing unit that determines whether the transfer schedule data having the business partner name that matches the transfer data exists in the transfer schedule file. And when the matching processing unit determines that there is transfer schedule data that matches the transfer schedule data, a request to erase billing data having a billing destination name of the transfer schedule data determined to match that from the invoice file. An accounting system with an automatic journalizing function for remittance data, comprising: 2. The billing destination information of the scheduled transfer data is a record in which a scheduled transfer date, a scheduled transfer amount, and a plurality of names of billing destinations are written, and the matching processing unit performs a transfer of the transfer data. 2. When the name on the destination side matches the name of any billing party in the searched transfer schedule data, the transfer schedule data is allocated. Accounting system with automatic journalizing function. 3. A temporary receipt slip is generated from the transfer data and stored in a temporary receipt file. Then, the transfer data of the temporary receipt slip is passed to the matching processing unit, and the transfer scheduled data matching the transfer data is received. 3. The accounting system with an automatic transfer function for transfer payment data according to claim 1, further comprising a transfer data reading unit for searching for a transfer data. 4. The matching processing unit calculates an amount obtained by subtracting the transfer amount from the transfer amount when the transfer amount of the transfer data from the temporary file does not match the transfer amount. This amount is subtracted from the scheduled transfer amount as the commission, and after the subtraction,
4. The accounting system according to claim 1, wherein the reconciliation between the deducted transfer amount and the transfer amount is determined again. 5. The method according to claim 1, wherein the matching processing unit determines whether the subtracted amount is within a predetermined amount range, and if the amount falls within a predetermined amount range, determines the amount as the fee of the financial information network. An accounting system with an automatic journalizing function for transfer payment data according to claim 1, 2, 3, or 4. 6. When it is determined that the commission obtained by subtracting the transfer amount from the scheduled transfer amount is correct,
6. An automatic journalizing function for transfer payment data according to claim 1, further comprising a journal slip generation unit for automatically generating journal slip data of the transfer amount for application. Accounting system. 7. A billing data clearing unit for performing a clearing process on billing data related to the scheduled transfer data retrieved by the matching processing unit.
An accounting system with an automatic journalizing function for the transfer data described in 4, 5 or 6. 8. The automatic journalizing of payment transfer data according to claim 7, wherein the billing data clearing unit performs the clearing process using the journal slip data generated by the journal slip generating unit. Accounting system with functions.