TWM552150U - Deposit management service system - Google Patents

Description

Accounting management service system

The present invention relates to a system, and more particularly to an accounting management service system involving virtual account accounting.

For those who have multiple accounts every day, the use of the "virtual account service" provided by the bank can help the efficiency of the account sales and reconciliation. More specifically, the bank's plan to give the industry multiple "virtual accounts" are dedicated accounts that are assigned to multiple different (paying) customers, respectively, and the (payment) payments from any of these virtual accounts are Designate a "physical account" to be entered into the bank by the operator. Therefore, the operator can grasp the payment situation of all customers according to whether the entity account receives the credit from each virtual account. However, when the operator wants to check the account of these virtual accounts, it is still necessary to specifically log in to the entity account to perform the auditing operation, which is quite laborious and time consuming. Therefore, there is still room for improvement in the prior art.

Accordingly, it is an object of the present invention to provide an accounting management service system that overcomes the shortcomings of the prior art.

Therefore, the new accounting management service system comprises a first server and a second server. The first server stores a reference material corresponding to an entity account, the reference material comprising a plurality of reference virtual account numbers different from each other. The second server is connected to the first server, and stores contact information corresponding to a user end, and the user end is related to the entity account. When the first server receives a billing request including a virtual account number and an account amount, and determines that the stored reference virtual account has a target reference virtual account corresponding to the virtual account, the first A server transfers the account amount to the entity account, and generates a credit success notification corresponding to the account request and including the entity account, the virtual account number, and the account amount, and notifies the account success Transfer to the second server. When the second server receives the accounting success notification from the first server, the second server transmits the accounting success notification to the stored information and the contact information related to the entity account. Use the end.

In some implementations, when the second server determines that a certain period of time from the use end and corresponding to the credit success notification is not received within a predetermined period from when the billing success notification is transmitted, At the time of notification, the second server transmits the credit success notification to the user again.

In some implementations, the billing success notification further includes a transaction time data indicating when the first server received the billing request.

In some implementations, the accounting request is from a server, and the accounting success notification further includes a collection path information related to the server.

In some implementations, the reference material further includes a plurality of deadlines respectively corresponding to the reference virtual account numbers, and when the first server receives the accounting request and determines that the reference virtual account has the target Referring to the virtual account, the first server further determines whether the receiving time of receiving the accounting request is later than the deadline corresponding to the target reference virtual account, and before the account amount is transferred to the entity account And determining that the receiving time is not later than the deadline corresponding to the target reference virtual account.

The effect of the novel is that the second server can immediately transmit the accounting success notification to the entity according to the stored contact information upon receiving the credit success notification from the first server. The use end of the account, thereby achieving the active and immediate provision of the relevant information about the account entry request and the successful credit entry, thus completely overcoming the above-mentioned shortcomings of the prior art.

Referring to FIG. 1, an embodiment of the new accounting management service system 1 can be used to manage a plurality of physical accounts, for example, opened by a bank to a plurality of businesses, and includes a first server 11, And a second server 12 connected to the first server 11 via, for example, a local area network or an internet (not shown). In this embodiment, the first server 11 is used, for example, as an accounting check and execution server, and the second server 12 is used, for example, as an automated message instant notification server, but not This is limited to this.

The first server 11 stores a plurality of reference materials 111 respectively corresponding to the physical accounts, each of the reference materials 111 includes a plurality of reference virtual account numbers that are different from each other and unique, and a plurality of corresponding reference virtual account accounts respectively. a deadline, wherein, in this embodiment, each reference virtual account includes, for example, a business identifier representing a company owned by a corresponding supplier, and a transaction identifier associated with the corresponding supplier and a corresponding payer (eg, Running water number), but not limited to this.

The second server 12 stores a plurality of contact data 121 respectively corresponding to a plurality of users, and the users are respectively associated with the entity accounts. Specifically, in this embodiment, each contact information 121 includes, for example, a contact address on a communication network, such as a Uniform Resource Locator (URL) or an IP address, but does not This is limited.

Referring also to Figures 1 and 2, an example of how the accounting management service system 1 executes an accounting management program is illustrated. The accounting management program consists of the following steps.

First, in step S1, the first server 11 receives an account entry request from a server 2 and including a virtual account number and an account amount, for example, via the Internet (not shown). In this embodiment, the server 2 is, for example, an Automated Teller Machine (ATM), but is not limited thereto, and generates a billing request via a payer's person for a payment operation.

Next, in step S2, the first server 11 determines whether there is a target reference virtual account corresponding to the virtual account in all the stored reference virtual accounts. If the result of the determination is affirmative, the flow proceeds to step S3, otherwise, the flow proceeds to step S5.

When the first server 11 determines that there is a target reference virtual account in all stored reference virtual accounts, in step S3, the first server 11 determines whether the receiving time of receiving the accounting request is later than the target. Refer to the deadline for the virtual account. If the result of the determination is affirmative, the flow proceeds to step S5, otherwise, the flow proceeds to step S4. In this embodiment, the deadline is, for example, a specific payment deadline, but is not limited thereto. In other embodiments, the deadline may also be a specific payment deadline. In addition, when the first server 11 determines that the stored reference virtual account exists in the stored reference virtual account, the first server 11 uses the pen reference material 111 including the target reference virtual account as a target reference. Information 111'.

When the first server 11 determines that the receiving time is not later than the deadline corresponding to the target reference virtual account, in step S4, the first server 11 transfers the account amount to the target reference data. The physical account corresponding to 111'. In this case, the first server 11 also uses the entity account corresponding to the target reference material 111' as a target entity account.

When the first server 11 determines that any of the stored reference virtual accounts does not have any target reference virtual account, or determines that the receiving time is later than the deadline corresponding to the target reference virtual account, in step S5, The first server 11 generates a credit failure notification corresponding to the accounting request, and transmits the accounting failure notification back to the server 2.

Following the step S6 following the step S4, the first server 11 generates a credit success notification corresponding to the credit request, and transmits the credit success notification to the second server 12. In this embodiment, the accounting success notification includes the target entity account, the target reference virtual account, the account amount, and a transaction indicating the date and time when the first server 11 receives the account entry request. The time data, but not limited thereto, and in other embodiments, the accounting success notification may further include a collection path information related to the server 2.

Next, in step S7, when the second server 12 receives the credit success notification from the first server 11, the second server 12 is based on the stored and related to the target entity account. The contact information 121 (for example, the contact address) is connected to a user terminal 3 related to the target entity account via a communication network (not shown), and transmits the account completion success notification to the user terminal 3, so that the When the use terminal 3 receives the credit success notification from the second server 12, the credit success notification is displayed to achieve the function of instant notification.

Then, in step S8, the second server 12 determines whether an acknowledgment from the user terminal 3 corresponding to the accounting success notification is received within a predetermined period from the time when the accounting success notification is transmitted. Notice. If the result of the determination is affirmative, the accounting management program is completed; otherwise, the flow returns to step S7 and steps S7 and S8 are repeatedly executed until receiving from the user terminal 3 and corresponding to the accounting success notification. Until the notice is received.

For example, the second server 12 repeats step S7 immediately after determining that it has not received any acknowledgement notification from the user terminal 3 within the predetermined period, or at the next full hour time. Step S7 is repeatedly executed, or step S7 is repeatedly executed at a predetermined time on the next day. It should be noted that, in other embodiments, the accounting management program may also be when the second server 12 determines that the confirmation notification is not received within the predetermined period, the flow returns to step S7 and the steps are repeated. S7 and step S8, and when the number of times of performing step S7 and step S8 is repeated a predetermined number of times (for example, three times), the accounting management program is completed, and is not limited to the embodiment.

In summary, the second server 12 of the new accounting management service system 1 can immediately receive the crediting success notification from the first server 11 based on the stored contact information 121. The credit success notification is transmitted to the user terminal 3 associated with the entity account, thereby achieving the active and immediate provision of the relevant information about the account entry request and the successful credit entry, thus completely overcoming the above-mentioned shortcomings of the prior art. In addition, to ensure that the user terminal 3 can surely receive the credit success notification from the second server 12, the second server 12 may determine that the user terminal 3 is not received within the predetermined period. When the notification is confirmed, the payment success notification is repeatedly transmitted to the user terminal 3 until the second server 12 receives the confirmation notification from the user terminal 3, so that the purpose of the present invention can be achieved.

However, the above is only the embodiment of the present invention, and when it is not possible to limit the scope of the present invention, all the simple equivalent changes and modifications according to the scope of the patent application and the contents of the patent specification are still This new patent covers the scope.

1‧‧‧Accounting Management Service System
11‧‧‧First server
111‧‧‧References
12‧‧‧Second server
121‧‧‧Contact Information
2‧‧‧ server
3‧‧‧Use side
S1~S8‧‧‧Steps

Other features and effects of the present invention will be apparent from the following description of the drawings, wherein: Figure 1 is a block diagram of one embodiment of the present invention; and Figure 2 is a flow chart An example of how this embodiment performs an accounting management program is illustrated.

1‧‧‧Accounting Management Service System

11‧‧‧First server

111‧‧‧References

12‧‧‧Second server

121‧‧‧Contact Information

2‧‧‧ server

3‧‧‧Use side

Claims (5)

A billing management service system, comprising: a first server storing reference data corresponding to an entity account, the reference material comprising a plurality of reference virtual account accounts different from each other; and a second server connecting the first server a server, and storing a contact data corresponding to a user end, the user end is related to the entity account; wherein, when the first server receives a billing request including a virtual account number and an account amount, and determining There is a target reference virtual account corresponding to the virtual account in the stored reference virtual account, and the first server transfers the account amount to the entity account, and generates a corresponding account entry request and includes The entity account, the virtual account number, and the credit success notification of the account amount, and transmitting the account success notification to the second server; when the second server receives the entry from the first server When the account is successfully notified, the second server transmits the account completion success notification to the user terminal according to the contact information stored and related to the entity account. The accounting management service system of claim 1, wherein the second server determines that the usage end is not received within the predetermined period of time when the accounting success notification is transmitted and corresponds to the Upon receipt of the confirmation notification of the successful notification, the second server transmits the credit success notification to the user again. The accounting management service system of claim 1, wherein the accounting success notification further comprises a transaction time data indicating a time when the first server receives the accounting request. The account management service system of claim 1, wherein the account entry request is from a server, and the account completion success notification further includes a collection path information related to the server. The accounting management service system of claim 1, wherein the reference data further includes a plurality of deadlines respectively corresponding to the reference virtual account numbers, and when the first server receives the accounting request and determines the When the reference virtual account has the target reference virtual account, the first server further determines whether the receiving time of receiving the accounting request is later than the deadline corresponding to the target reference virtual account, and the accounting amount is Before being transferred to the entity account, it is further determined that the receiving time is not later than the deadline corresponding to the target reference virtual account.