Systems and methods for automated purchase requests
First Claim
1. A method for electronically purchasing a product comprising:
- specifying a user;
stipulating an approval level of the user;
defining routing actions based on the approval level and identity of the specified user;
submitting a transaction by the specified user to purchase the product;
identifying payment options to complete the transaction based upon the submitted transaction and the specified user;
selecting an identified payment option;
submitting a purchase request by the specified user, indicating the selected payment option;
determining if the submitted purchase request complies with the stipulated approval level of the specified user;
accepting the submitted purchase request if it is determined that the submitted purchase request complies with the stipulated approval level of the specified user and routing the submitted purchase request based on the defined routing actions if it is determined that the submitted purchase request does not comply with the stipulated approval level of the specified user; and
purchasing the product if the submitted purchase request was accepted and taking the defined routing if the submitted purchase request does not comply with the stipulated approval level of the specified user.
2 Assignments
0 Petitions
Accused Products
Abstract
A purchase request system efficiently procures goods and services by recognizing purchase authority levels of users within an enterprise, division, or project team. Administrators establish authority levels to ensure that purchase requests within a user'"'"'s authority level are automatically processed and submitted to vendors for fulfillment of orders, while purchase requests beyond a user'"'"'s authority level are routed according to a determined protocol. Determined protocols include routing the purchase request to a designated user with a different authority level for disposition, rejection of the purchase request, or modification of the purchase request in accordance with the determined protocol. Users may select from multiple payment methods to complete a purchase transaction and may access the purchasing system in real time to determine the status of an order at any point in the life cycle of the purchase request, from submission of the request to payment for received goods and services.
142 Citations
42 Claims
-
1. A method for electronically purchasing a product comprising:
-
specifying a user; stipulating an approval level of the user; defining routing actions based on the approval level and identity of the specified user; submitting a transaction by the specified user to purchase the product; identifying payment options to complete the transaction based upon the submitted transaction and the specified user; selecting an identified payment option; submitting a purchase request by the specified user, indicating the selected payment option; determining if the submitted purchase request complies with the stipulated approval level of the specified user; accepting the submitted purchase request if it is determined that the submitted purchase request complies with the stipulated approval level of the specified user and routing the submitted purchase request based on the defined routing actions if it is determined that the submitted purchase request does not comply with the stipulated approval level of the specified user; and purchasing the product if the submitted purchase request was accepted and taking the defined routing if the submitted purchase request does not comply with the stipulated approval level of the specified user. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14)
-
-
15. A computer-readable medium having computer-executable instructions for electronically purchasing a product, the computer-readable medium comprising:
-
specifying a user; stipulating an approval level of the user; defining routing actions based on the approval level and identity of the specified user; submitting a transaction by the specified user to purchase the product; identifying payment options to complete the transaction based upon the submitted transaction and the specified user; selecting an identified payment option; submitting a purchase request by the specified user, indicating the selected payment option; determining if the submitted purchase request complies with the stipulated approval level of the specified user; accepting the submitted purchase request if it is determined that the submitted purchase request complies with the stipulated approval level of the specified user and routing the submitted purchase request based on the defined routing actions if it is determined that the submitted purchase request does not comply with the stipulated approval level of the specified user; and purchasing the product if the submitted purchase request was accepted and taking the defined routing if the submitted purchase request does not comply with the stipulated approval level of the specified user. - View Dependent Claims (16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28)
-
-
29. An electronic purchase request system comprising:
-
a user specification system that specifies an approved user of the electronic purchasing system and an approval level of the specified user; an interface system that receives submitted transactions and submitted purchase requests by the specified user to purchase a product; a payment system that identifies and selects available payment options to complete the transaction based upon the submitted transaction and the specified user; and a routing system that defines routing actions based on the approval level and identity of the specified user, determines if a submitted purchase request complies with the approval level of the specified user, and accepts the submitted purchase request if it is determined that the submitted purchase request complies with the approval level of the specified user and routes the submitted purchase request based on the defined routing actions if it is determined that the submitted purchase request does not comply with the approval level of the specified user. - View Dependent Claims (30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42)
-
Specification