TWM593037U - Lease management system - Google Patents

Abstract

A rental management system includes a storage module, an accounting management module, a payment reminder module, a request review module, and a review module. The storage module stores the lease data of a plurality of leases. The account management module selects the rent payable data from the plural lease data based on the payment cycle data and estimated payment date data of each lease data. The payment reminder module generates pending rent information corresponding to the rent payable data. The request review module receives a request instruction requesting review of rent payable data, and generates a pending message corresponding to the rent payable data according to the request command. The audit module receives the signing instruction to complete the review of the pending message, and transmits the rent payable data to the accounting system according to the signing instruction.

Description

Rental Management System

The present invention relates to a lease management system, in particular to a lease management system which can automatically screen the lease contracts with the payment date of the lease payment expiring on a regular basis to facilitate subsequent rent payment operations.

For companies that need a lot of leased assets to use for business, efficient lease management is very important. Taking banks as an example, in order to serve local customers nearby, it is often necessary to rent houses in various regions as a business base. In the past, the rent payment operation of the leased house was carried out by the contractors responsible for the rent payment date contained in the lease, and the contractors reviewed the lease and the past payment status, and then judged the items and amounts payable. Collect the data manually and then provide it to the accountant for processing.

However, the previous manual method of checking and controlling the rent payment operation is not only time-consuming and inefficient, but also increases the inconvenience of the back-end accounting when performing the payment operation. Therefore, how to provide a lease management system to improve the efficiency in managing a large number of leases is a problem that urgently needs to be solved by related companies.

The main purpose of this new model is to provide a lease management system that can automatically screen the lease contracts that are about to expire on the payment date of the lease payment to facilitate subsequent rent payment operations.

To achieve the above purpose, the new lease management system includes a storage module, an accounting management module, a payment reminder module, and a request review module. The storage module is used to store a plurality of lease data, each of which includes payment cycle data, estimated payment date data and payment method data. The account management module is used to select at least one rental payable data from the plural lease data, wherein the selection is calculated and paid based on the payment cycle data, the estimated payment date data and the selected date. The payment reminder module is used to generate the pending rent information corresponding to the rent payable data. The request review module is used to receive a request instruction requesting to review the rent payable data and generate a pending message corresponding to the rent payable data according to the request instruction.

In the lease management system of the present invention, the lease management system includes a storage module for storing a plurality of lease data, and each lease data includes payment cycle data, estimated payment date data and payment method data. The use steps of the new type of lease management system are as follows: Based on the payment cycle data and estimated payment date data of each lease data, the rent payable lease data is selected from the plural lease data; the rent payable information corresponding to the lease payable lease data is generated; Receive the request instruction requesting to review the rent and lease information payable, and generate a pending message corresponding to the rent and lease information according to the request instruction; receive the signing instruction to complete the review and review of the pending lease information, and according to the signing instruction, the rent and lease information Send to the accounting system.

1: Rental management system

10: Communication module

20: Lease management module

21: File setting unit

22: Sign execution unit

30: Storage module

40: Account Management Module

50: Payment reminder module

60: Request review module

70: Audit module

80: Certificate Management Module

90: Accounting system

200, 300: electronic device

P1: Lease construction page

P11: Lease construction file setting key

P12: Deposit payment setting button

P2: File completion page

P3: Sign-off page

P31: Reminder window

P4: Payment list page

P41: Unpaid amount field

P411: Payment button

P42: pending approval field

P421: Rent difference table key

P422: Rental payment schedule key

P423: Department allocation table key

P43: approved field

P5: Credential management page

P51: Certificate login key

D1: Rent difference table

D2: Rental payment schedule

D3: Departmental allocation table

FIG. 1 is a schematic diagram of a usage environment of a rental management system according to an embodiment of the new model.

FIG. 2 is a flow chart of the use steps of the lease management system according to an embodiment of the new model.

FIG. 3A is a schematic diagram of a part of a lease creation page according to an embodiment of the new model.

FIG. 3B is a schematic diagram of another part of the lease creation page of an embodiment of the new type.

FIG. 4 is a schematic diagram of a file completion page according to an embodiment of the present invention.

FIG. 5 is a schematic diagram of a sign-off page according to an embodiment of the new model.

FIG. 6 is a schematic diagram showing that the deposit to be paid message is displayed in the approved field of the payment list page.

FIG. 7 is a schematic diagram showing that the pending rent information is displayed in the unpaid amount field of the payment list page.

FIG. 8 is a schematic diagram showing that the message to be reviewed is displayed in the field for verification in the payment list page.

9 is a schematic diagram of a rental difference table according to an embodiment of the new model.

10 is a schematic diagram of a rental payment schedule according to an embodiment of the new model.

FIG. 11 is a schematic diagram of a departmental allocation table according to an embodiment of the new model.

12 is a schematic diagram of a credential management page according to an embodiment of the new model.

In order to better understand the technical content of the present invention, the preferred specific embodiments are described below.

FIG. 1 is a schematic diagram of a usage environment of a rental management system according to an embodiment of the new model. FIG. 2 is a flowchart of steps used in a rental management system according to an embodiment of the new model. Please refer to FIGS. 1 and 2 at the same time. This new type of lease management system 1 can provide companies, legal persons or groups that manage their complicated asset leasing operations, such as companies, legal persons or groups that need to rent a large number of houses as business bases, such as banks, insurance companies, chain stores, etc. The new type of lease management system 1 can also be used to manage the lease of movable assets, of which lease refers to finance lease or operating lease. In this embodiment, the lease management system 1 operates in a server (not shown). The lease management system 1 includes a communication module 10, a lease management module 20, a storage module 30, and an accounting management module 40. The payment prompt module 50, the request review module 60, the review module 70, and the certificate management module 80. The lease management system 1 can communicate with the accounting system 90 through a communication module 10 in a wired or wireless manner. In addition, the rental management system 1 can connect and communicate with electronic devices 200 and 300 having communication functions through the network through the communication module 10. A user (for example, a company employee or supervisor) can log in and use the rental management system 1 by operating the electronic device 200 or 300. The flow chart of the steps of using the lease management system shown in FIG. 2 can be executed by the joint operation of each module. The following describes the flow of steps when using the rental management system of this embodiment, and further describes the actions between the modules. For the step description process, please refer to FIGS. 3B to 12 together.

Step S1: According to the payment cycle data and estimated payment date data of each lease data and a selected date, the rent payable lease data is selected from the plural lease data.

In the embodiment of the present invention, the storage module 30 is coupled to the communication module 10, which may be a non-transitory computer-readable storage medium, such as but not limited to flash memory, optical disk, or magnetic disk. media. The storage module 30 is used to store a plurality of lease data. The lease data includes payment cycle data, estimated payment date data, and payment method data, but is not limited thereto. In this embodiment, each lease data is only stored in the storage module 30 after being filed and approved. The lease management module 20 includes a file creation setting unit 21 and a signing execution unit 22.

Regarding the filing and signing procedures of the lease data, first, the user needs to operate the electronic device 200 or 300 to log in to the lease management system 1. After logging in, the user can operate the electronic device 200 or 300 to input a file creation instruction. For example, the rental management system 1 can generate a system main page on the electronic device 200 or 300 after the user logs in and display it on the screen of the electronic device 200 or 300 (not shown). The system main page includes a new lease button , The user can click the new lease button to enter the file creation instruction. After receiving the file building instruction, the file building setting unit 21 may generate a lease file building page P1 as shown in FIGS. 3A and 3B, for example. The user can use the lease building page P1 to execute the lease building operation. The lease creation page P1 can provide users with basic information about the lease information to be added, such as but not limited to the lease object, lease period, rental amount, payment method, payment cycle, estimated payment date of each period, and the name of the lessor , The address of the subject matter of the lease, the amount of the deposit, etc. After completing the basic data input, the user can further control the rental management system 1 to generate a deposit payment setting interface (not shown) by clicking the deposit payment setting button P12 in the lease creation page P1 to display on the electronic device 200 or 300. Screen. The deposit payment setting interface is available Provide users with payment settings for the deposit payable for the lease information to be added.

After completing the leasing data file-building operation, the file-building setting unit 21 will generate a file-building completion page P2 as shown in FIG. 4, for example, and then the user may submit the newly-added leasing data for approval. The signing execution unit 22 can generate a signing page P3 as shown in FIG. 5, for example, a user (such as a supervisor with signing authority) can log in to the rental management system 1 by operating the electronic device 200 or 300 to use the signing Page P3. The sign-off page P3 can provide users with online sign-off for the newly added lease information. As shown in FIG. 5, in this embodiment, if the lease period recorded in the lease period data of the lease data to be signed does not meet the system preset period (for example, 3 years), the signing execution unit 22 will sign in A reminder window P31 will pop up on the page P3 to remind the user to pay attention when signing. After the user completes the online approval, the newly added lease data will be sent to the storage module 30 for storage.

In addition, in this embodiment, when the newly added lease data is online signed, the payment prompt module 50 will generate a pending deposit message according to the deposit payment settings completed by the previous user. This pending deposit information can be displayed, for example, in the approved field P43 in the lower part of the payment list page P4 shown in FIG. 6. The user can log in to the rental management system 1 by operating the electronic device 200 or 300, and click to view the pending deposit information. In addition, the audit module 70 will send the lease information to the accounting system 90 after completing the online approval of the newly added lease data, so that the company's accounting personnel will perform subsequent deposit payment actions according to the deposit amount of the lease information, for example Send money or write a check to the lessor.

In the embodiment of the present invention, the account management module 40 is coupled to the storage module 30. Since each lease data includes payment cycle data and estimated payment date data, the account management module 40 can use the payment cycle data of each lease data, estimated payment date data, and a selected date to select from the plural lease data Select the rent payable information. More specifically, the account management module 40 can periodically compare the payable date set in the payment cycle data and estimated payment date data of each lease data with the date of the selected day to determine whether the number of days between the two dates is less than the Set the number of days (for example, one month); if it is, the account management module 40 will determine the lease data with a date difference between the payable date and the date of the selected day that is less than the preset number of days as a payable but unpaid item. These lease information are selected as rent payable lease information. For example, assuming that the storage module 30 stores 200 lease data, when the account management module 40 judges that there are 50 leases based on the payment cycle data of each lease data, estimated payment date data, and the date of execution selection If the payable date of the information is less than one month away from this date, the 50 lease data will be selected as the rent payable data. Payment cycle data refers to the cycle of rental payments, such as monthly payment, quarterly payment or annual payment. The estimated payment date information is the date of the rent payable in each period, such as the first working day of each month or the fifth day of each month, or the quarterly payment, the first working day of each quarter or the first quarterly Five days of the month.

Step S2: Generate the pending rent information corresponding to the rent payable data.

In the embodiment of the present invention, the payment prompt module 50 is coupled to the account management module 40. After obtaining the rent payable data, as shown in FIG. 7, the payment prompt module 50 will then generate a pending rent message corresponding to the rent payable data. This pending rent The gold message will be displayed in the unpaid amount field P41 on the payment list page P4. Taking the example of pre-disclosure as an example, the payment reminder module 50 will generate corresponding rent-to-pay information on the selected 50 rent-payable lease data, which will be displayed on the unpaid amount field P41 in the payment list page P4 ( That is, there will be 50 pieces of pending rent information on the payment list page P4). After logging in to the rental management system 1 by operating the electronic device 200 or 300, the user can browse the pending rent information by using the payment list page P4 .

Step S3: Receive a request instruction requesting to review the pending rent message, and generate a pending message corresponding to the pending rent message according to the request instruction.

In the embodiment of the present invention, the request review module 60 is coupled to the payment prompt module 50. The request review module 60 is used to receive a request instruction requesting to review the rent pending message, and generate a pending message corresponding to the rent pending message according to the request command. More specifically, after step S2 is executed, if a user (for example, a business contractor) logs in to the rental management system 1, it can know the existence of the pending rent message through the payment list page P4. Further, the user can check at least one of the pending rent information by clicking on it, and then click the payment button P411 to enter the request instruction for requesting review of the rent payable data corresponding to the selected pending rent information. After the request review module 60 receives the request instruction, it will generate a corresponding pending review message according to the rent payment message selected by the user. This pending message will be displayed in the P42 column of the payment list page P4 (as shown in Figure 8).

Step S4: Generate a rent difference table about the rent payable data, and generate a rent payment schedule based on the payment method data of the rent payable data, same as The department allocation table is generated based on the lease usage data of the rent payable data.

In the embodiment of the present invention, when the account management module 40 selects the rent payable lease data from the plural lease data, the account management module 40 may also generate a rent difference table regarding the rent payable lease data. As shown in FIG. 8, after the user (for example, supervisor) logs in to the rental management system 1 through the electronic device 200 or 300 connection, he can click the rental difference table key P421 displayed on the payment list page P4 to enable, for example, The rental difference table D1 shown in 9 is displayed on the screen of the electronic device 200 or 300. As shown in FIG. 9, the generated rental difference table D1 contains the difference of at least one prepayment data of the rent payable lease data. Therefore, the user can use this rental difference table D1 when reviewing the audit information (described later in detail). In order to quickly review the contents of this payment for errors. For example, when the amount of rent payable recorded in the expected payment data in this period is different from the amount of rent recorded in the previous payment data, this difference exists through the rental difference table D1. In other embodiments, when the difference in the rent difference table D1 includes that the amount of the rent is different from the lease object of the expected payment data, the rent difference table D1 can assist the user to quickly check whether the rent payable data is correct.

In the embodiment of the present invention, when the account management module 40 selects the rent payable lease data from the plural lease data, the account management module 40 may also generate a rent payment schedule based on the payment method data of the rent payable lease data. More specifically, in the plural rent payable lease data, some rents are paid by remittance and some are paid by cheque. The account management module 40 of this embodiment is used to pay the rent payable data by remittance Perform a unified process to generate a rent The gold payment schedule (not shown) collects the rent payable lease information paid by cheque and generates another rent payment schedule D2 (for example, as shown in Figure 10). Similarly, after logging in to the rental management system 1 through the electronic device 200 or 300, the user can click the rental payment schedule key P422 (as shown in FIG. 8) displayed on the payment list page P4 to enable, for example, The rental payment schedule D2 shown in FIG. 10 is displayed on the screen of the electronic device 200 or 300. The generated rental payment schedule D2 will be sent to the accounting system 90 after the pending audit message is reviewed (details will be described later) to provide the company’s accounting staff with the ability to use each rental payment schedule quickly when performing subsequent payment operations Complete payment operations conveniently.

In the embodiment of the present invention, when the account management module 40 selects the rent payable lease data from the plural lease data, the account management module 40 also generates a divisional allocation based on the lease usage data of the rent payable data table. Because the house leased by the company is sometimes used by multiple departments, although it is leased in the name of the company, when the department budget is compiled, the rental cost will be taken into account. At this time, it is necessary to use the house according to the status of the department (usually Use area) to apportion rent in proportion. Therefore, the account management module 40 of this embodiment will generate a departmental allocation table based on the lease usage data of the rent payable data. Similarly, after logging in to the rental management system 1 through the electronic device 200 or 300, the user can click the department allocation table key P423 (as shown in FIG. 8) displayed on the payment list page P4 to display, for example, The department allocation table D3 shown in 11 is displayed on the screen of the electronic device 200 or 300. The departmental allocation table D3 can provide the company's accounting personnel with a quick understanding of the rent expenditure of each department during subsequent accounting.

Step S5: Receive a signing instruction to complete the review of the pending message, and send the rent payable data to the accounting system according to the signing instruction.

An audit module 70 is connected to the request audit module 60. The audit module 70 may be a module coupled to the relevant functional module in the new lease management system 1 or a new lease management system 1. A module connected with related functional modules in a wired or wireless manner. When the audit module 70 is installed in a system outside the new lease management system 1, the audit module 70 may include The audit function of the process, that is, the new lease management system 1 can share the audit module 70 with other systems. In this embodiment, when a message to be reviewed is generated, an auditor (such as a supervisor) logs in to the lease management system 1 and can see the message to be reviewed. The message to be reviewed includes at least one item to be reviewed, and the content of the item to be reviewed includes But not limited to the payment object, account information, amount payable, withholding tax amount, estimated payment date, actual payment amount, etc., the review module 70 will generate a sign-off operation interface for the reviewer to click the message to be reviewed, in order to review the message to be reviewed Corresponding rent payable lease information is reviewed, and the audit opinion is entered. Once the reviewer completes the review, he can enter the verification or approval instruction by clicking the complete review button (not shown). In other embodiments, if the audit module 70 is set in an external system, and the external system and the lease management system 1 share the audit module 70, the request audit module 60 will provide the audit message to the audit module 70, When the reviewer wants to review the aforementioned messages to be reviewed, the reviewer must first log in to the external system, and the review module 70 will generate a sign-off operation interface for the reviewer to review and review the pending messages. In other embodiments, the auditor can also log in to the lease management The management system 1 directly jumps or logs into an external system in a single sign-on (SSO) mode to operate the audit module 70 for audit.

In this embodiment, one of the signing instructions input by the user corresponds to at least one message to be reviewed. After receiving the signing instruction, the auditing module 70 transmits the rent payable data corresponding to the message to be audited to the accounting system 90 according to the signing instruction. After the rent-lease payable data is transmitted to the accounting and accounting system 90, the user (such as a company accountant) can perform payment operations, such as remittance or write a check, in accordance with the content of the rent-payable and lease information received by the accounting and accounting system 90 Wait for action.

Step S6: Generate a voucher list based on the payment completion settings.

The voucher management module 80 is coupled to the accounting system 90. After the company accountant completes the payment operation on the rent payable lease data, he can log in and operate the accounting system 90 to send the payment completion setting to the lease management system 1. Generally speaking, if the lessor is a company or a legal person, after paying the rent of the lessor, the lessor needs to issue an invoice to the lessee. Therefore, the certificate management module 80 of this embodiment will generate A list of certificates for verification. This certificate list will be displayed on the certificate management page P5 shown in FIG. 12, for example. It should be understood that the contents and presentation of the certificate list are not limited to this.

It should be noted that, in addition to being able to be configured as a hardware device, firmware, or a combination thereof, each of the foregoing modules can also be configured by circuit loops or other appropriate types; and, each module can be configured in addition to a separate type. Combined type configuration. . In addition, this embodiment only exemplifies the preferred embodiment of the present invention. Document all possible combinations of changes. However, those of ordinary skill in the art should understand that the above modules or components are not necessarily necessary. In order to implement the present invention, other more detailed conventional modules or components may also be included. Each module or component may be omitted or modified as needed, and there may not be other modules or components between any two modules.

It can be seen from the previous disclosure that the new lease management system can judge and filter out the lease payable based on the lease period, rent amount, payment method, payment cycle, estimated payment date and other data in the lease conditions and the date when the selection is executed Data, and generate corresponding reports (including rent difference table, rental payment details table and departmental allocation table) according to the rent payable lease information, in addition to providing users who are responsible for auditing to quickly check the rent payable lease information, and can also simplify subsequent accounting The payment operation of personnel helps companies that need to rent a lot of premises as a business base to manage the lease operation.

Although the present invention has disclosed the above embodiments with embodiments, it is not intended to limit the present invention. Anyone with ordinary knowledge in the technical field can make some changes and modifications without departing from the spirit and scope of the present invention. , Should be the scope of rights claimed by the patent, so the scope of protection of this patent shall be deemed as defined by the scope of the attached patent application.

1: Rental management system

10: Communication module

20: Lease management module

21: File setting unit

22: Sign execution unit

30: Storage module

40: Account Management Module

50: Payment reminder module

60: Request review module

70: Audit module

80: Certificate Management Module

90: Accounting system

200, 300: electronic device

Claims (8)

A lease management system, operating in a server, the lease management system includes: a storage module to store a plurality of lease data, each of the lease data includes payment cycle data, estimated payment date data and payment method data; an account A business management module is coupled to the storage module. The accounting management module selects at least one rental payable lease data from the plural lease data, wherein the selection of the at least one rental payable lease data is based on the payment cycle The data, the estimated payment date data and the date selected for execution are calculated; a payment reminder module is coupled to the account management module, and the payment reminder module generates at least one wait for at least one rent payable lease data Rent payment information; a request review module, coupled to the payment prompt module, the request review module receives a request instruction requesting to review the at least one rent payable lease data, and generates a response corresponding to the at least one according to the request instruction 1. At least one message to be reviewed for rent payable information The lease management system as described in item 1 of the patent application scope, in which the account management module contains a prepayment data. The lease management system as described in item 2 of the patent application scope, wherein the accounting management module is further used to generate a rent difference table regarding the at least one rent payable lease information, the rent difference table including the at least one rent payable lease The difference between the information and the previous payment information. The lease management system as described in item 1 of the patent application scope, wherein the account management module includes a prepayment data, and the account management module is further used to generate a rent difference table regarding the at least one rent payable lease information , The rent difference table contains the difference between the at least one rent payable lease information and the prior payment information. As in the lease management system described in item 1 of the patent application scope, the account management module further generates a rental payment schedule based on the payment method data of the at least one rental payable lease data. As in the lease management system described in item 1 of the patent application scope, the accounting management module further generates a departmental allocation table based on the lease usage data of the at least one lease payable lease data. The lease management system as described in item 1 of the patent application scope further includes a certificate management module that generates a certificate list based on a payment completion setting. The lease management system as described in item 1 of the scope of patent application further includes an audit module that receives a signing instruction to complete the review of the at least one pending message, and according to the signing instruction, the at least one rent payable lease information Send to an accounting system.

Images