Construction payment management system and method with hierarchical invoicing and direct payment features

• US 7,734,546 B2
• Filed: 09/12/2007
• Issued: 06/08/2010
• Est. Priority Date: 06/29/2004
• Status: Active Grant

• Current Assignee: Textura LLC (Oracle Corporation)
• Original Assignee: Textura LLC (Oracle Corporation)
• Inventors: Eichhorn, William H., Allin, Patrick J., Niden, Howard L., Pedersen, Richard P. Jr., Bagley, Matthew R., Cherry, Charles C.
• Primary Examiner(s): Trammell; James P
• Assistant Examiner(s): LIU, I JUNG
• Application Number:
  US11/900,546
• Publication Number:
  US 20080005022A1
• Time in Patent Office: 1,000 Days
• Field of Search: 705 1- 55, 726/4, 707/3, 707/E17.014
• US Class Current: 705/40
• CPC Class Codes: G06F 3/0484 for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
• CPC Class Codes: G06Q 10/00 Administration; Management
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/0631 Resource planning, allocation, distributing or scheduling for enterprises or organisations
• CPC Class Codes: G06Q 10/06313 Resource planning in a project environment
• CPC Class Codes: G06Q 10/103 Workflow collaboration or project management
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/14 specially adapted for billing systems
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 30/00 Commerce
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G06Q 40/03 Credit; Loans; Processing thereof
• CPC Class Codes: G06Q 40/04 Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
• CPC Class Codes: G06Q 40/06 Asset management; Financial planning or analysis
• CPC Class Codes: G06Q 40/12 Accounting
• CPC Class Codes: G06Q 50/08 Construction
• CPC Class Codes: G06Q 50/16 Real estate

Abstract

A system and method for managing a construction payment process. One method embodying the invention can include creating an electronically-executed first request for payment on behalf of a first participant in a construction project, transmitting the first request for payment to a second participant in the construction project, creating an electronically-executed second request for payment based on the first request for payment, transmitting the second request for payment to a payment source in the construction project, directing transmitting a payment to the second participant from the payment source, and directly transmitting a payment to the first participant from the payment source.

Claims

1. A construction payment management system comprising:

an application server including a processor and a computer readable memory, wherein the computer readable memory stores

a construction project profile that identifies a plurality of participants associated with a construction project and a role for each of the plurality of participants in the construction project, wherein, according to the construction project profile, the plurality of participants includes a first participant, a second participant, and a third participant, and wherein, according to the construction project profile, the third participant is a payor for the construction project, the second participant is a contractor that is contractually subordinate to the third participant for the construction project, the first participant is a contractor that is contractually subordinate to the second participant for the construction project, and the first participant is not directly in contract with the third participant for the construction project,

an identifier of a first participant device, a second participant device, and a third participant device corresponding to the first participant, the second participant, and the third participant, respectively, and

instructions that, when executed by the processor,

establish electronic communication between the application server and each of the first participant device, the second participant device, and the third participant device,

generate an electronically-executed first request for payment on behalf of the first participant in the construction project in response to information received from the first participant device,

transmit the first request for payment to the second participant device,

generate an electronically-executed second request for payment on behalf of the second participant based on the first request for payment,

transmit the second request for payment to the third participant device,

transmit a first payment directly from the third participant to the first participant, and

transmit a second payment directly from the third participant to the second participant.

2. The construction payment management system of claim 1 wherein the electronically-executed first request for payment includes an electronically-executed invoice.

3. The construction payment management system of claim 2 claim wherein the electronically-executed second request for payment includes a sworn statement electronically-executed by the second participant.

4. The construction payment management system of claim 1 wherein the third participant includes at least one of an owner, a lender, a title company, a general contractor, and a subcontractor.

5. The construction payment management system of claim 1 wherein the application server receives an approval of the first request for payment from the second participant device before generating and transmitting the second request for payment.

6. The construction payment management system of claim 1 wherein the application server receives approval of the second request for payment from the third participant device before directly transmitting the first payment and the second payment.

7. The construction payment management system of claim 1, wherein the computer readable memory includes further instructions that, when executed, automatically reconcile the first request for payment based on a budget of the construction project.

8. The construction payment management system of claim 1, wherein the computer readable memory includes further instructions that, when executed, automatically reconcile the second request for payment based on a budget of the construction project.

9. The construction payment management system of claim 1, wherein the application server receives an electronically executed lien waiver from the first participant device and stores the electronically executed lien waiver to the computer readable memory.

10. The construction payment management system of claim 9 wherein the received lien waiver corresponds to a payment that has been requested, but has not yet been transmitted to the first participant.

11. The construction payment management system of claim 9 wherein the received lien waiver corresponds to a payment that has been requested and transmitted to the first participant.

12. The construction payment management system of claim 9 and further comprising an electronic signature service to electronically execute the lien waiver.

13. The construction payment management system of claim 9 wherein the application server

tracks outstanding lien waivers associated with the construction project,

receives a plurality of lien waivers from a plurality of participants associated with the construction project,

stores each of the plurality of received lien waivers, and

automatically transmits the first payment and the second payment when all of the outstanding lien waivers are received.

14. The construction payment management system of claim 9 wherein the application server automatically transmits the first payment to the first participant after receiving the lien waiver.

15. The construction payment management system of claim 9 wherein the application server

tracks outstanding lien waivers associated with the construction project,

receives lien waivers from a plurality of participants that are contractually subordinate to the second participant and stores each one of the lien waivers to the computer readable memory,

transmits the first payment to the first participant when a lien waiver is received from the first participant , and

transmits the second payment to the second participant when all of the outstanding lien waivers are received.

16. The construction payment management system of claim 9 wherein the application server directly transmits the payment to the first participant by generating and transmitting to a payment system an automated instruction to pay the first participant and by receiving from the payment system an acknowledgement that the first participant has received funds.

17. The construction payment management system of claim 16 wherein the application server prevents any of the participants associated with the construction project from accessing the stored lien waiver until after receiving the acknowledgement.

18. The construction payment management system of claim 16 wherein the payment system includes at least one of an automated clearing house system, a wire transfer system, a debit card system, a credit card system, and a check generating system.

19. The construction payment management system of claim 1, wherein the application server generates a budget for the construction project.

20. The construction payment management system of claim 19 wherein the application server generates at least one of the first request for payment and the second request for payment based on the generated budget.

21. The construction payment management system of claim 20 wherein the application server generates at least one of an automated sworn statement and an automated lien waiver based on at least one of the first request for payment and the second request for payment.