METHOD FOR CLOUD COMPUTING COST REIMBURSEMENT PAYMENT

Abstract

The method has the collection of data from a user to apply for licensing cost reimbursement for a software application. The method processes payments from the user per service terms. The service terms appear in an electronic agreement displayed to the user and cover the user and the customer of the user utilizing the method. The provider pays the user the amount per the agreement less the license cost, per payment schedule billing, and any other fees. The method provides a platform for the user to provide a service, receive payment for the service, and cover the license cost to the user only upon receipt of payment from the user's customer. The invention does not create an independent contractor and an employee relationship with its user.

Claims

1. A method to allow a user to register for cloud-based software and to pay for the use of the cloud-based software, said cloud-based software being owned by software provider, said user having a customer, said method comprising: registering a user; receiving data from the user; receiving a request to apply for cloud-based software application cost reimbursement from the user; processing said request for cloud-based software cost reimbursement automatically and programmatically; processing payments of a customer of the user; generating customizable terms and conditions for an electronic payment schedule; computing and processing authorization of a payment from payment funds of the customer; including licensing incentive functions within said terms and conditions; and presenting licensing incentive details to the user upon the user registering a new account and upon updating an existing account; wherein said method reimburses a cloud-based software provider from the user's customer's payment accepted through said method; wherein said method records agreement of the user to said terms and conditions generated by said method; wherein said method records acceptance by the user of a structured incentive for payment reimbursement to the software provider during said registering a user or during said receiving data from a user.

2. The method to allow a user to register for cloud-based software and to pay for the use of the cloud-based software of claim 1 wherein said processing payments of a customer includes electronic payments of the customer.

3. The method to allow a user to register for cloud-based software and to pay for the use of the cloud-based software of claim 2 wherein said electronic payments includes credit card, debit card, wire transfer, automated clearing house, and mobile payments.

4. The method to allow a user to register for cloud-based software and to pay for the use of the cloud-based software of claim 1, further comprising: providing at least one database wherein said method operates upon said at least one database.

5. A method of tracking a project performed by a customer and disbursing payment for the project to a user of said method, said method comprising: registering a user of the method; receiving data from the user; registering a customer of said user; receiving data from said customer; creating a project requested by said customer; generating terms and conditions for said project including an electronic payment schedule; recording consent of said customer to said terms and conditions; tracking progress of said customer upon said project; determining completion of said project; calculating a payment upon completion of said project and processing authorization of said payment; collecting a portion of said payment and sending it to said user; and disbursing a remainder of said payment to said customer.

6. The method of tracking a project performed by a customer and disbursing payment for the project to a user of said method of claim 5, further comprising: providing within said electronic payment schedule means to move funds.

7. The method of tracking a project performed by a customer and disbursing payment for the project to a user of said method of claim 6 wherein said means to move funds includes credit card, debit card, wire transfer, automated clearing house, and mobile payments.

8. The method of tracking a project performed by a customer and disbursing payment for the project to a user of said method of claim 5, further comprising: providing at least one database; said registering a user of the method upon said at least one database; said receiving data from the user entering that data upon said at least one database; said registering a customer of said user upon said at least one database; said receiving data from said customer entering that data upon said at least one database; and said creating a project requested by said customer upon said at least one database.

9. The method of tracking a project performed by a customer and disbursing payment for the project to a user of said method of claim 8, further comprising: said collecting a portion of said payment and sending it to said user is adapted to communicate with external credit card services; and said disbursing a remainder of said payment to said customer is adapted to communicate with external credit card services.

10. A method of tracking a project performed by a customer and disbursing payment for the project to a user of said method, said method comprising: registering a user of the method; providing at least one database; receiving data from the user; registering a customer of said user; receiving data from said customer; creating a project requested by said customer; generating terms and conditions for said project including an electronic payment schedule; recording consent of said customer to said terms and conditions; tracking progress of said customer upon said project; determining completion of said project; calculating a payment upon completion of said project and processing authorization of said payment; collecting a portion of said payment and sending it to said user; disbursing a remainder of said payment to said customer; said registering a user of the method upon said at least one database; said receiving data from the user entering that data upon said at least one database; said registering a customer of said user upon said at least one database; said receiving data from said customer entering that data upon said at least one database; said creating a project requested by said customer upon said at least one database; said collecting a portion of said payment and sending it to said user is adapted to communicate with external credit card services; said disbursing a remainder of said payment to said customer is adapted to communicate with external credit card services; including licensing incentive functions within said terms and conditions; and presenting licensing incentive details to the user upon the user registering a new account and upon updating an existing account; wherein said method reimburses a cloud-based software provider from the user's customer's payment accepted through said method; wherein said method records agreement of the user to said terms and conditions generated by said method; wherein said method records acceptance by the user of a structured incentive for payment reimbursement to the software provider during said registering a user or during said receiving data from a user.

11. The method of tracking a project performed by a customer and disbursing payment for the project to a user of said method of claim 1 further comprising: providing within said electronic payment schedule credit card, debit card, wire transfer, automated clearing house, and mobile payments.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In referring to the drawings,

[0031] FIG. 1 is a flow chart describing the preferred embodiment of the present invention;

[0032] FIG. 2 is a flow chart further describing the preferred embodiment of the present invention the invention after FIG. 1; and

[0033] FIG. 3 is a flow chart further describing the preferred embodiment of the present invention continuing FIG. 2.

[0034] The same reference numerals refer to the same parts throughout the various figures.

DESCRIPTION OF THE PREFERRED EMBODIMENT

[0035] The drawings illustrate the invention, particular implementations of processes and methods of carrying out the invention, the Method For Cloud Computing Cost Reimbursement Payment. In brief, FIG. 1, as a flow chart, describes how a user of the invention's software application initially registers and is then presented with the option to, during this software application registration process, accept the terms and conditions and use the method of reimbursement payments to pay for the software application. FIG. 2, as a flow chart, then describes how the user of the software application signs into their existing account, uses the software application to receive external lead sources. And FIG. 3, also as a flow chart, then illustrates and describes the process of monetary transactions from customer payments and handling of these payments. The handling of the payment then reimburses the software application fees due, on their due date, from the software application user. The payment handling continues on to how the user is paid the remaining amount of the transaction or, when no software application fees are due, all of the payment made from the customer in this situation.

[0036] Turning to FIG. 1, here a user of the invention accesses it through a website or mobile application, on a mobile device, as at 100, and securely registers for a new account 101, or signs in 103 and updates 115 his existing account 114. The method of this invention transmits data to a database 113 for the software application to create a new cloud-based user account or update an existing account, collectively as at 114. During the software application new account registration process, as at 102, the invention presents to the user a reimbursement payment option 104 to choose, as at 105, or select, the invention, or the cloud computing cost reimbursement payment, to pay for the software application costs. When the user agrees to payment reimbursement terms and conditions, as at 106, the invention transmits this data input to the database 113 and processes, as at 112, the registration data for a new account, as at 114. Terms and conditions as used herein is one concept though it has three words. The user also has the option of submitting a change to their existing account 115 later to opt in for cloud computing reimbursement or credit card payment terms. Where credit card appears in this description, that phrase includes related financial activity including debit card, wire transfer, automated clearing house, and mobile payments, such as Venmo®, Zelle®, CashApp®, PayPal®, and others.

[0037] When the user chooses to apply for the invention, or cost reimbursement payment, to pay for the software application 105, the user securely agrees to the cost reimbursement terms and conditions, as at 106, and the software application proceeds to process the data and then transmits that data input to the database 113 once more. Then the user of the invention has access to an administration user account 114 or, if the user denies the user agreement as at 106, then the user is presented with a credit card payment option 107. There, the invention receives from the user his entered credit card information, as at 108, and the software application validates this entered credit card information 109 with external credit card services, as at 110. If the entered credit card input is successfully, the invention then transmits this data to the database 113. The invention then processes the registration data for a new account, or an existing account is updated, as at 112. Where the user account is created or existing account updated, as at 116, the user account 114 will now show application payment information and schedule where applicable, as at 117. If user credit card is not successfully validated, as at 110, then the software application displays an error message, as at 111, to the user and the invention presents to the user again the credit card entry option again 107.

[0038] With an account open and payment entered into the invention, FIG. 2 begins where the user navigates, or is directed to a website or an application on a mobile device for the invention 100 and securely accesses their application account. If successfully signed into the software application 200, the application matches inbound leads from customers to user account details, as at 201, where the invention the displays, or presents, to the user information as a lead 203 from external lead sources 209. As a reminder, the user operates the method of the invention, the user has its own customers who communicate to the user, and the customers have limited use of the invention primarily under user direction as later explained. The invention then allows the user to choose to access the lead information 204 and accept the lead from the auto generated lead input 205 to the software application. The application of the invention then converts the lead to a proposal 206 where the application presents the proposal details, terms, and condition with the customer 208. If the user accesses the lead information 204 and does not accept the auto generated lead data input 205, then the user may input lead data manually into the invention, or the application, as at 207, where the invention converts this manually entered lead information to a proposal as at 206, and then the invention presents the proposal details to the customer 208.

[0039] As a user operates the invention and a user sees information from it, FIG. 3 begins. The invention, or the application, presents proposal details to the customer, as at 208, and the customer accepts or does not accept the proposal terms and conditions 209. If the customer does not accept the proposal terms and conditions 209 then proposal details are modified upon the invention between the customer and the invention's user, as at 211, and if the customer or software application user do not modify the proposal 211 then the application sends communication to the customer and software application user.

[0040] If the customer accepts the proposal terms and condition, as at 209, then the software application converts the proposal to a job 210, or a project. The term project includes work performed by tradesmen, contractors, professional services firms, and the like, along with their results, and also physical items. If service hours, actions, or functions remain on the proposal term specifications, as at 212, then the software application user or the invention itself perform the service 214. The invention then calculates the value of the service completed as at 224 for billing purposes and to compare with the job's, or service's, terms and conditions.

[0041] If the software application user or the invention have met job terms and conditions 212, then the software application notifies the customer requesting acceptance of job terms and conditions 213. If the customer accepts the job terms and conditions 213 then the software application of the invention sends a bill to the customer 215 for the job and the customer makes the payment for the job, service, or transaction, as at 216, through the invention. Then the software application of the invention verifies if the software application subscription cost is due based on reimbursement payment terms and conditions and payment schedule as at 217. If so, the software application of the invention calculates the outstanding payment due 219 and the invention collects these fees due for the software application usage from the software application user, as at 221. The invention deducts this payment from the payment form authorized by the customer.

[0042] If the application subscription cost is not due as at 217, then the software application user has no fees deducted from this payment and receives a full payment authorized by the customer 218. Then, the software application of the invention records the transaction and service information automatically 220 to a database 223. If the customer does not make the payment for the job service, as at 216, then the customer or user modify the proposal terms and conditions on the invention through its software application embodiment, as at 211, where the invention the presents these modified terms and conditions to the customer as at 208, also initially described above. Here, the customer or user via the invention can accept or deny these modifications as at 209 until the customer and the software application user, user of the invention, come to terms to finish the job, service, or transaction.

[0043] In an alternate embodiment, the invention had a user of the software application who initially registers and is presented with the option to, during this software application registration process, accept the terms and conditions and use the method of reimbursement payments to pay for the software application. Then the user of the software application signs into their existing account, uses the software application to receive external lead sources to process monetary transactions from customer payments to the software application user.

[0044] In the alternate embodiment, a user navigates or is directed to a website or application on device and securely signs up or updates their existing account and data is transmitted to databases for the software application online using a device to create a cloud-based software application user account. During the software application account signup data input is transmitted to databases that process it, and the user is presented with the option to securely apply online for a cloud computing cost reimbursement payment model to pay for the software application costs.

[0045] When the user chooses to apply for the cost reimbursement payment model to pay for the software application, the user securely agrees to the cost reimbursement terms and conditions and the software application proceeds to process the user data and then data input is transmitted to databases or other data storage and the software application user now has access to administration account or, if the user denies the user agreement then the user can enter their credit card information and submit the credit card information and the software application validates with external credit card services, the credit card information and data input is transmitted to database processes. If the user credit card information is validated the user registration data is processed and software application presents user with secured administration account showing software application payment information and schedule. If a user's credit card is not successfully validated then the software application displays error message to the user and is presented with the credit card entry option again.

[0046] The alternate embodiment continues where the user navigates or is directed to a website or application on a device and securely signs into or accesses their application account, and, if successfully signed into the software application, the user is presented with information as a lead from external lead sources and the user chooses to access the lead information and accept the proposal from the lead input to the software application then proposal details and terms are communicated with the customer and the customer accepts the proposal and any or no affiliated proposal terms and if the customer does not accept the proposal and any or no affiliated proposal terms then proposal details are modified and any or no affiliated proposal terms with the customer. If service hours or actions are remaining on the proposal term specifications then the user and or application perform the service and are calculated for billing purposes then the software application bills accordingly for the service and the customer makes the payment for the job, service or functional transaction then the software application verifies if the application subscription cost is due and, if so, the user's allocated, current payment is due based on reimbursement payment terms and conditions and payment schedule, and is deducted from the payment authorized by the customer. If the application subscription cost is not due, then the user receives payment authorized by the customer less any or no affiliated service fees and, then, the software application records the transaction and service information automatically. The present invention operates upon a database.

[0047] During usage, the user of the method navigates or is directed to the method of the present invention stored upon the user's electronic device. The software application user registers for a new account or updates their existing account. While registering for a new account or updating an existing account, the software application displays an option to view additional information about reimbursement payments to pay for the software application. The software application presents the user with detail showing an example payment schedule with reimbursement method or the user bypasses this information. The software application user chooses to use the reimbursement option to pay for the software application.

[0048] The software application user agrees to or denies the reimbursement payment terms and conditions. If the software application user denies the reimbursement payment terms and conditions the user is presented with a credit card payment entry option to pay for the application. If the software application user accepts the reimbursement payment terms and conditions, the user account registration data is processed, and registration process is finalized. The software application presents the user with a secured administration account access showing application leads, payment information and schedule.

[0049] Once the software application user account has been created, the user signs into or accesses their application account. If the user has successfully signed into or accessed their account, the user is presented with information as a lead within the software application. If the user has not successfully signed into or accessed their application account they will receive a message and be redirected to sign in or access again.

[0050] Once signed in successfully to the software application, the user is presented with lead information. The user accesses lead detail information and accepts the lead offer per lead or service type or the user enters a new lead and service manually into the software application. Once the user accepts the lead offer, the lead converts to a proposal where details are communicated to the customer along with any or no affiliated terms and conditions.

[0051] The customer accepts the proposal and any or no affiliated terms and conditions. If the customer does not accept the proposal terms and conditions, the proposal and any or no affiliated terms and condition details are modified and are resubmitted back to the customer for approval. If the customer does not respond to the resubmitted proposal terms and conditions, the software application attempts to contact the customer until sending final communication.

[0052] When the customer accepts the proposal terms and conditions, the application begins to track whether or not the terms and conditions have been met with the current service. If the service terms and conditions have been met, the software application bills the customer. If the service terms and conditions have not been met, the software application continues tracking the service terms and conditions until met or until manually reconfigured.

[0053] The customer makes payment for the service per service terms and conditions and the software application verifies if the software application subscription cost is due from the software application user. If the software application cost is due, the allocated payment ratio, credit, incentive offer increase or reduction on cost or service offering is calculated and the amount outstanding is deducted from the payment authorized by the customer. The software application user receives payment authorized by the customer less any or no affiliated service fees and any or no transaction processing fees. If the customer does not make payment for the service when billed, a payment arrangement including details and any or no terms and conditions are communicated with the customer. The customer accepts the revised service payment arrangement and any or no affiliated terms and conditions, the application tracks whether or not the terms and conditions have been met with the current service, then re-bills the customer accordingly. If the customer does not accept the revised payment arrangement, additional service payment arrangements are made and either eventually accepted or not by the customer where the software application is paid for the service or is forced to close the service agreement and seek other methods outside of the scope of this software application. The software application of the invention records the translation information for any transactions accordingly.

[0054] In an alternate embodiment, a user securely signs up for the software online using a device, device screen, and device keyboard to create a cloud-based software user account. During the software account signup process, the user is presented with the option to securely apply online for a loan to finance the software cost.

[0055] When the user chooses to apply for financing of the software cost, the user securely inputs additional data and securely uploads files to the software interface and securely submits data to the software and software processes loan application request with internal software application processing and outside loan application data servers and data sources to automatically, programmatically complete the loan application process with the software and with any other sources which, any other sources for processing loan, send loan application detail data back to the software application. Once the software's loan application process completes the loan application process status is communicated to the user by email, SMS/text message, and back to the software user administration area. If the loan is approved, the loan is funded to a new read only financial account where software will debit this financial account for the software price. The user will have read-only access to the financial account. Software payment history will be displayed on software user account.

[0056] The user navigates to the cloud-based software application on a device. The user chooses to subscribe to the cloud-based software application and apply for a loan to finance the costs of the application. For the finance portion of the registration and lending process, the user inputs data and uploads documents specifically to apply for cloud-based software financing. The user verifies, approves, and certifies data accuracy before electronically submitting a loan application for processing to and as part of the invention. If the user is an existing customer of the cloud-based software, they are presented with the financing option to their existing account.

[0057] The invention receives the loan application request electronically and automatically sends the loan application for additional computational processing. The loan application is processed through various steps and is subject to include programmatically sending the loan application data to proprietary or outside sources of data processing, lookups, underwriting, and vetting for approving or denying the loan.

[0058] The loan application processing steps are tracked and are available to be displayed on the customer administration area of the cloud-based software application upon user secure sign in. These steps include, but are not limited to, loan submission to underwriting, whether or not the loan is conditionally approved, the loan is clear to close, loan closing, and loan funding.

[0059] The loan application process has been completed. When the loan has been approved, the funds are allocated to a newly created account where the cloud-based software company is allowed to debit the account for the monthly software application subscription amount per the terms of the loan.

[0060] The loan borrower loan payment schedule begins, and the loan payment is automatically deducted from their own financial institution account. Payment history and any other necessary payment details are available to be displayed to the loan borrower in the customer administration area of the cloud-based software application upon user secure sign in.

[0061] If denied, loan denial is conveyed to the loan borrower in the customer administration area of the software application upon user secure sign in. The loan borrower is provided with the option of prepaying the loan amount. The alternate embodiment of the invention will perform ongoing monitoring of loan payment history and processes with internal, proprietary software application data analytics to offer additional financial services to the user and cloud-based software company.

[0062] And, the present invention tracks a project performed by a customer and then disburses payment for the project to a user of the invention. On a database, possibly two of them, the invention registers its user and receives data from the user, then registers a customer of the user and receives data from the customer. With that data, the invention creates a project requested by the customer and generates terms and conditions for the project including an electronic payment schedule for it. The invention then presents the terms and conditions to the customer as described above and records the consent of the customer to those terms and conditions. Then the customer, and sometimes the user, works the project while the invention tracks the progress of the customer upon the project, The invention uses its tracking to determine completion of the project. When that has occurred, it calculates a payment upon completion of the project and processes authorization of the payment. The invention then collects a portion of the payment and sends it to the user, typically to cover a portion of the software license fee. The invention then disburses the remaining portion of the payment to the customer.

[0063] While a preferred embodiment of the Method for Cloud Computing Cost Reimbursement Payment has been described in detail, it should be apparent that modifications and variations thereto are possible, all of which fall within the true spirit and scope of the invention. With respect to the above description then, it is to be realized that the optimum dimensional relationships for the parts of the invention, to include variations in size, materials, shape, form, function and manner of operation, assembly and use, are deemed readily apparent and obvious to one skilled in the art, and all equivalent relationships to those illustrated in the drawings and described in the specification are intended to be encompassed by the present invention.

[0064] Therefore, the foregoing is considered as illustrative only of the principles of the invention. Further, since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the invention to the exact construction and operation shown and described, and accordingly, all suitable modifications and equivalents may be resorted to, falling within the scope of the invention.

[0065] Various aspects of the illustrative embodiments have been described using terms commonly employed by those skilled in the art to convey the substance of their work to others skilled in the art. However, it will be apparent to those skilled in the art that the present invention may be practiced with only some of the described aspects. For purposes of explanation, specific numbers, materials and configurations have been set forth in order to provide a thorough understanding of the illustrative embodiments. However, it will be apparent to one skilled in the art that the present invention may be practiced without the specific details. In other instances, well known features are omitted or simplified in order not to obscure the illustrative embodiments.

[0066] Various operations have been described as multiple discrete operations, in a manner that is most helpful in understanding the present invention, however, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations need not be performed in the order of presentation.

[0067] Moreover, in the specification and the following claims, the terms “first,” “second,” “third” and the like—when they appear—are used merely as labels, and are not intended to impose numerical requirements on their objects.

[0068] The above description is intended to be illustrative, and not restrictive. For example, the above-described examples may be used in combination with each other. Other embodiments can be used, such as by one of ordinary skill in the art upon reviewing the above description. The Abstract is provided to allow the reader to ascertain the nature of the technical disclosure. Also, in the above Detailed Description, various features may be grouped together to streamline the disclosure. This should not be interpreted as intending that an unclaimed disclosed feature is essential to any claim. Rather, inventive subject matter may lie in less than all features of a particular disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. The scope of the invention should be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.

[0069] As such, those skilled in the art will appreciate that the conception, upon which this disclosure is based, may readily be utilized as a basis for the designing of other structures, methods and systems for carrying out the several purposes of the present invention. Therefore, the claims include such equivalent constructions insofar as they do not depart from the spirit and the scope of the present invention.