Source: http://www.google.com/patents/US20050216400?dq=5319712
Timestamp: 2016-10-25 07:39:55
Document Index: 764275566

Matched Legal Cases: ['arty 34', 'arty 34', 'arty 34', 'arty 34', 'arty 34', 'arty 34']

Patent US20050216400 - System and method of managing payments - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsThe present subject matter discloses a method of managing payments made in the construction industry. A subcontractor delivers an invoice to the builder, the builder approves the invoice and forwards the invoice to a title company. The title company verifies the builder has the requisite funds in a construction...http://www.google.com/patents/US20050216400?utm_source=gb-gplus-sharePatent US20050216400 - System and method of managing paymentsAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS20050216400 A1Publication typeApplicationApplication numberUS 11/041,810Publication dateSep 29, 2005Filing dateJan 21, 2005Priority dateJan 22, 2004Also published asWO2005071633A2, WO2005071633A3Publication number041810, 11041810, US 2005/0216400 A1, US 2005/216400 A1, US 20050216400 A1, US 20050216400A1, US 2005216400 A1, US 2005216400A1, US-A1-20050216400, US-A1-2005216400, US2005/0216400A1, US2005/216400A1, US20050216400 A1, US20050216400A1, US2005216400 A1, US2005216400A1InventorsDaniel Doyle, David Endrody, Danielle Jirsa, Carlos WhitemanOriginal AssigneeDoyle Daniel F, Endrody David L, Jirsa Danielle M, Whiteman Carlos RExport CitationBiBTeX, EndNote, RefManPatent Citations (3), Referenced by (30), Classifications (9), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetSystem and method of managing payments
DETAILED DESCRIPTION [0012] FIG. 1 illustrates a method 10 of the present invention. As shown in FIG. 1, the method 10 provides a process for managing payment from a contractor to a subcontractor for approved expenditures made by the subcontractor. Although the method 10 shown in FIG. 1 relates specifically to a contractor's reimbursement of expenditures made by a subcontractor, the method 10 is equally applicable to contractors, subcontractors, vendors, suppliers, customers and employees. Further, the invention of the present invention may be applicable in other industries beyond the construction industry. [0013] In the example shown in FIG. 1, the contractor is a builder that has a transaction account for making payments. The transaction account may be a credit account, such as a credit account provided for use with a transaction card, such as a credit card. The transaction account may otherwise be a revolving line of credit or other account from which payment to a subcontractor may be made. [0014] As shown in FIG. 1, a subcontractor performs a service for which payment from the builder is due. The method 10 includes a first step 12 wherein the subcontractor provides an invoice to the builder for the requested funds to be paid from the builder's transaction account. The invoice may be for services, expense or a combination of services and expenses. The method 10 includes a second step 14 wherein the builder reviews the invoice, resolves any questions the builder has with the subcontractor relating to the requested funds, the services performed or the expenses incurred. When the invoice is approved, the builder forwards the approved invoice to a third party, such as a title company, for processing of the requested funds via a third step 16. The third step 16 may include grouping a number of invoices received from the subcontractor together for more efficient payment of a number of related invoices. The title company receives the invoice and orders the requested funds from an existing construction loan via a fourth step 18. The fourth step 18 ensures the builder has the funds required to make the approved payments. Under the method 10 shown in FIG. 1 the title company may be solely liable for the transactions processed via the method 10. In the method 10 shown in FIG. 1, the title company further sends a notice to the subcontractor that the builder has approved the invoice and requests a lien waiver from the subcontractor via the fourth step 18. [0015] In a fifth step 20 of the method 10, upon receipt of the title company's lien waiver request, the subcontractor sends a lien waiver to the title company. When the title company receives the lien waiver from the subcontractor, the title company processes a payment voucher, communicates the approved payment amount to the subcontractor and provides the subcontractor access to the approved payment through the builder's transaction account via a sixth step 22. In the final step 24 of the method 10 shown in FIG. 1, the subcontractor is paid via the builder's transaction account. [0016] Under the method 10 shown in FIG. 1, payment of the requested funds is only authorized by the title company when the title company receives both a lien waiver from the subcontractor and receives confirmation that the requested funds are available from the builder. Accordingly, the method 10 safeguards against disputes arising from a builder's inability to pay and the subcontractor's refusal or failure to release the builder's debt. [0017] The method 10 shown in FIG. 1, may follow the timeline illustrated in FIG. 1, i.e., the final step 24 may occur approximately twenty-eight days after the first step 12 of the method 10. Alternatively, the method 10 may occur according to a different timeline comprising either a shorter or a longer period of time. [0018] As described above, the approved payments made by the builder correspond to pre-approved bank construction loans and lines of credit accessed by the title company. The third party or title company acts as an escrow agent to facilitate the payment process from the builder to the subcontractor. [0019] The steps of the method 10 may be automated via computer systems utilizing the Internet or using other “online technology” to enable electronic transfer of invoices and other communications involved in the method 10. Electronic transfer of communications may enable automated invoice approvals and payments, may reduce the number of invoices that must be subjectively reviewed (enabling managers of the communications to “manage by exception”), may prevent duplicative communications and may enable online dispute resolution. Electronic transfers may also improve the payment cycle time, reduce the billing process costs, improve invoice control and visibility and may allow the posting of invoices from various electronic systems, such as, for example, existing accounting programs. Those of ordinary skill in the art will readily recognize that the functions and capabilities of the method 10 of the present invention can be implemented on one or more machines or computers in a network, which may use one or more computer platforms. [0020] For example, FIG. 2 illustrates a system 26 for implementing the method 10 described with respect to FIG. 1. As shown in FIG. 2, within the system 26 a transaction card company 28 has established relationships with a contractor 30 and a subcontractor 32. For example, the contractor 30 and subcontractor 32 may have transaction card accounts with the transaction card company 28. As shown in FIG. 2, the subcontractor 32 provides an invoice to the contractor 30. If the contractor 30 approves the invoice, the contractor 30 notifies a third party 34, for example, a title company, that the invoice has been approved. The third party 34 then orders the funds required to pay the invoice from the transaction card company 28, as shown in FIG. 2. The third party 34 also notifies the subcontractor 32 the invoice has been approved, the funds have been ordered from the transaction card company 34 and requests a lien waiver from the subcontractor 32. The subcontractor 32 then provides a lien waiver to the third party 34, who in turn processes the lien waiver and authorizes payment of the invoice by the contractor 30 through the transaction card company 28, receives confirmation the finds are available from the contractor 30 through the transaction card company 28 and provides notice to the subcontractor 32 of the approved payment. After the transaction card company 28 receives the authorization for payment of the invoice from the third party 34, the transaction card company 28 completes the transaction by crediting the transaction card account of the subcontractor 32. [0021] The system 26 shown illustrated in FIG. 2 may be employed through a computer network in which various portions of the system are automated. For example, in response to receiving an approved invoice, the third party 34 may automatically provide the subcontractor 32 with the notice of approved invoice and a request for a lien waiver. Similarly, other portions of the system 26 may be automated using a computer, a computer network or other electronic means. [0022] As discussed above, payments made by the contractor in the system 26 and the method 10 may be made from a transaction card account. Accordingly, the contractor may earn reward points or bonuses from the company providing the transaction card account. The contractor may then use those points or rewards for employee incentives, buyer incentives, bonuses, gifts, promotions, etc. When payment is made from a transaction card account, the subcontractor may benefit by receiving a quicker, easier and more efficient payment process, the subcontractor will not have to deal with tracking checks and the payment issues involved with check cashing. The third party that processes the payment voucher may benefit from an expanded customer list and from the simpler lower cost process provided by the system 26 and the method 10. The transaction card account company may benefit from a significant new source of transaction volume, a minimal credit risk and minimal marketing expenses. [0023] The transaction card accounts used in conjunction with the system 26 and the method 10 shown in FIGS. 1 and 2 may be part of a closed loop system wherein each entity requesting payment through the system 26 and the method 10 must be registered as a “merchant.” For example, in order for a subcontractor to receive payment from a contractor's transaction card account, the subcontractor must be enabled to receive payment within the system by being given a merchant code that identifies the subcontractor as a merchant within the context of the system 26 and the method 10. Only payments made to merchants having the proper merchant code may completed within the system 26 and the method 10. Accordingly, if the contractor's transaction card account is fraudulently used in an attempt to purchase goods from a merchant not registered within the system 26 and the method 10 (for example, to buy airline tickets), the transaction will not be approved. The closed loop system provides security against fraud for the transaction card account holder, the transaction card account provider and merchants, both those registered within the system 26 and the method 10 and those outside of the system 26 and the method 10. [0024] A general purpose computer may be used to execute computer or machine readable instructions and carryout or perform desired steps or functions of the system 26 and method 10. As is known to those of ordinary skill in the art, a general-purpose computer typically comprises a central processor, an internal communication bus, various types of memory (RAM, ROM, EEPROM, cache memory, etc.), disk drives or other code and data storage systems, and one or more network interface cards or ports, and sound cards for communication purposes. The computer and computer system may also use a relatively high-speed communication interface to an external network. [0025] Moreover, software functionalities involve programming, including executable code as well as associated stored data. The software code is executable by the general-purpose computers or processors that can functions as part of the securities account monitoring system. In operation, the executable program code or software and associated data can be stored in an appropriate memory or data storage locations and/or transported for loading into appropriate general-purpose computing machines. In one aspect, the present subject matter involves one or more software products and applications in the form of one or more modules of code carried by at least one machine-readable medium. Execution of such code by one or more processors of the computer platform enables implementation and operation of the system 26 and the method 10 of the present invention. [0026] As used herein, terms such as computer or machine “readable medium” refer to any medium that participates in providing instructions to a processor for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media include, for example, optical or magnetic disks, such as any of the storage devices in a computer or machine. Volatile media include dynamic memory, such as main memory of such a computer. Physical transmission media include coaxial cables, copper wire and fiber optics, including the wires that comprise a bus within a computer system. Carrier-wave transmission media can take the form of electric or electromagnetic signals, or acoustic or light waves such as those generated during radio frequency (RF) and infrared (IR) data communications. Common forms of computer-readable media include, for example: a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, DVD, any other optical medium, punch cards, paper tape, any other physical medium with hole patterns, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave transporting data or instructions, cables or links transporting such a carrier wave, or any other medium from which a computer can read programming code and/or data. Many of these forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to a processor for execution. [0027] While the foregoing has described what are considered to be the best mode and/or other examples, it is understood that various modifications may be made therein and that the technology and subject matter disclosed herein may be implemented in various forms and examples, and that they may be applied in numerous applications, only some of which have been described herein. Those skilled in that art will recognize that the disclosed aspects may be altered or amended without departing from the true spirit and scope of the subject matter. Therefore, the subject matter is not limited to the specific details, representative devices, and illustrated examples in this description. It is intended to protect any and all modifications and variations that fall within the true scope of the advantageous concepts disclosed herein. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS20020069188 *Dec 1, 2000Jun 6, 2002Level Z, L.L.C.On-line payment settlement for multi-party based servicesUS20020107790 *Feb 7, 2002Aug 8, 2002Nielson James A.System and method for extending automatically secured credit to building project owners and to building contractors for purchasing building supplies from building supply wholesalersUS20050144100 *Dec 30, 2003Jun 30, 2005Craig ShapiroPayment systems and methods for earning incentives using at least two financial instruments* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7672888Sep 12, 2007Mar 2, 2010Textura CorporationConstruction payment management system and method with automated electronic document generation featuresUS7725384Sep 12, 2007May 25, 2010Textura CorporationConstruction payment management system and method with one-time registration featuresUS7734546Sep 12, 2007Jun 8, 2010Textura CorporationConstruction payment management system and method with hierarchical invoicing and direct payment featuresUS7797210Jul 13, 2006Sep 14, 2010Textura CorporationConstruction payment management system and method with graphical user interface featuresUS7818250Oct 19, 2010Textura CorporationConstruction payment management system and method with automatic workflow management featuresUS7899739Mar 1, 2011Textura CorporationConstruction payment management system and method with real-time draw notification featuresUS7925584Apr 12, 2011Textura CorporationConstruction payment management system and method with document tracking featuresUS7983972Jul 19, 2011Textura CorporationConstruction payment management system and method with graphical user interface featuresUS8180707Oct 10, 2007May 15, 2012Textura CorporationConstruction payment management system and method with actionable notification featuresUS8234211 *Jun 2, 2006Jul 31, 2012Copper Range, Inc.Digital lien serviceUS8306883Apr 30, 2008Nov 6, 2012Textura CorporationConstruction payment management systems and methods with specified billing featuresUS9336542 *Apr 5, 2012May 10, 2016Textura CorporationConstruction payment management system and method with automatic notification workflow featuresUS9355417 *Apr 5, 2012May 31, 2016Textura CorporationConstruction payment management system and method with draw notification featuresUS9460441 *Apr 3, 2008Oct 4, 2016Textura CorporationConstruction payment management system and method with document exchange featuresUS20050289051 *Jan 10, 2005Dec 29, 2005Allin Patrick JConstruction payment management system and methodUS20060271397 *Jul 13, 2006Nov 30, 2006Allin Patrick JConstruction payment management system and method with automatic workflow management featuresUS20060271477 *Jul 11, 2006Nov 30, 2006Allin Patrick JConstruction payment management system and method with real-time draw notification featuresUS20060271478 *Jul 12, 2006Nov 30, 2006Allin Patrick JConstruction payment management system and method with hierarchical invoicing and direct payment featuresUS20060271479 *Jul 12, 2006Nov 30, 2006Allin Patrick JConstruction payment management system and method with budget reconciliation featuresUS20060277516 *Jun 2, 2006Dec 7, 2006Ray Randall LDigital lien serviceUS20070078771 *Aug 24, 2006Apr 5, 2007Allin Patrick JConstruction payment management system and method with document tracking featuresUS20080010199 *Sep 17, 2007Jan 10, 2008Textura, Llc.Construction payment management system and method with budget reconciliation featuresUS20080021823 *Sep 26, 2007Jan 24, 2008Textura, Llc.Construction payment management system and method with graphical user interface featuresUS20080027840 *Sep 27, 2007Jan 31, 2008Textura, Llc.Construction payment management system and method with automatic workflow management featuresUS20080040264 *Oct 10, 2007Feb 14, 2008Textura, Llc.Construction payment management system and method with actionable notification featuresUS20080046350 *Sep 12, 2007Feb 21, 2008Textura, LlcConstruction payment management system and method with automated electronic document generation featuresUS20080281735 *Apr 3, 2008Nov 13, 2008Allin Patrick JConstruction payment management system and method with document exchange featuresUS20120197789 *Apr 5, 2012Aug 2, 2012Allin Patrick JConstruction payment management system and method with automatic notification workflow featuresUS20120197790 *Apr 5, 2012Aug 2, 2012Allin Patrick JConstruction payment management system and method with draw notification featuresUS20140156502 *Mar 15, 2013Jun 5, 2014Cfph, LlcConducting a loan* Cited by examinerClassifications U.S. Classification705/39International ClassificationG07F19/00, G06Q20/00Cooperative ClassificationG06Q20/10, G06Q30/04, G06Q20/14European ClassificationG06Q30/04, G06Q20/10, G06Q20/14Legal EventsDateCodeEventDescriptionJun 7, 2005ASAssignmentOwner name: AMERICAN EXPRESS TRAVEL RELATED SERVICES COMPANY,Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DOYLE, DANIEL FRANCIS;ENDRODY, DAVID LEE;JIRSA, DANIELLEMAUREEN;AND OTHERS;REEL/FRAME:016307/0001;SIGNING DATES FROM 20050119 TO 20050603RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services