CN114462751A

CN114462751A - Payment method based on engineering progress

Info

Publication number: CN114462751A
Application number: CN202111328706.7A
Authority: CN
Inventors: 吴跃; 何仲明; 谭家齐; 阮嘉怡; 刘健军
Original assignee: Beifeng Holding Co ltd
Current assignee: Beifeng Holding Co ltd
Priority date: 2020-11-10
Filing date: 2021-11-10
Publication date: 2022-05-10

Abstract

A payment method of project progress based on a block chain comprises the following steps: initializing a payment record linked list of the engineering project; responding to the received project progress payment request, creating a corresponding progress node in the payment record chain table, and sending a progress check message; the progress node at least comprises payment amount, and the progress checking message indicates a progress indication file to be recorded; receiving a progress indication file corresponding to the progress check message to record the progress indication file into the progress node, and sending a progress payment message; receiving a payment bill corresponding to the progress payment message to record the payment bill into the progress node. Wherein the progress node in the payment record linked list is an immutable node.

Description

Payment method based on engineering progress

Technical Field

The invention relates to a method for project management and progress payment application, which can realize periodic and monitorable payment based on a remote interaction platform and a terminal, in particular to payment management based on project progress.

Background

Construction projects involve multiple aspects of the ecosystem, including developers, contractors, subcontractors, and quality control personnel. Construction projects often require significant capital and take a long time to complete. Project delays, partial project reworking, delayed payments are common examples of various problems in construction projects. In practice, progress payments are commonly used in construction projects. The progress payment can be paid monthly or proportionally according to a certain project. The progress payment provides key guarantee for smoothly developing construction work. It not only concerns the interests of each party, but also directly affects the important goals of the safety, quality, progress, cost, etc. of the whole project. In particular, it allows developers and/or contractors to review the subcontractor's quality of work and resolve any potential dispute and liability issues as the project progresses.

However, in processing payment applications in a building, multiple payment requests are involved at a time, authorization is obtained in different aspects, and progress of the work is monitored. If the interest-related party at the upstream of the fund chain delays the payment of the project money, in order to ensure the interest of the interest-related party, the interest-related party at the downstream of the fund chain has to continuously propagate the delayed payment risk, thereby influencing the progress of the project and threatening the quality and the safety of the project.

Accordingly, there is a need to provide a method for organizing, managing and monitoring operational flows in a construction project to ensure quality control (monitoring and inspection) of the construction project. It manages and verifies progress during the course of the project, avoiding disputes between invoicing and payment, to ensure that the project passes the acceptance before the expiration date.

Disclosure of Invention

The invention aims to solve the defects of the prior art and provide a credible, complete and accurate project management method for each participant of a building project so as to avoid potential quality and project money disputes as much as possible.

In order to achieve the above object, the present invention adopts the following technical means.

Firstly, the application provides a payment method of project progress based on a block chain, which comprises the following steps: initializing a payment record linked list of the engineering project; responding to the received project progress payment request, creating a corresponding progress node in the payment record chain table, and sending a progress check message; the progress node at least comprises payment amount, and the progress checking message indicates a progress indication file to be recorded; receiving a progress indication file corresponding to the progress check message to record the progress indication file into the progress node, and sending a progress payment message; receiving a payment bill corresponding to the progress payment message to record the payment bill into the progress node. Wherein the progress node in the payment record linked list is an immutable node.

In the above embodiment of the present application, after initializing the payment record linked list of the engineering project, the method further includes the following steps: the actual identity of each user receiving the message, sending the project progress payment request, and sending the progress indication file is identified.

In one or more embodiments of the present application, rights are assigned to identify the receiving message, sending project progress payment requests, and progress indication files based on the actual identity of each user.

In one or more embodiments of the present application, the progress indication file includes a construction stage photograph or a progress certification file.

In one or more embodiments of the present application, the payment record linked list is recorded on the storage medium in a distributed manner.

In one or more embodiments of the present application, the linked list of payment records provides access to third parties (e.g., banks, etc. financial institutions that may provide financing) in a read-only manner.

In one or more embodiments of the present application, the method further comprises reviewing the progress indication document and the bill for payment, and performing the payment by a third party.

In one or more embodiments of the present application, the progress indication file is sent to a corresponding progress node through the internet.

In one or more embodiments of the present application, the progress indication file transmitted to the corresponding progress node via the internet is read-only.

In one or more embodiments of the present application, the progress indication files in the payment record linked list are automatically extracted and collated into project progress reports in chronological order.

Secondly, this application still provides a computer system. The computer system includes a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the following steps are executed: initializing a payment record linked list of the engineering project; responding to the received project progress payment request, creating a corresponding progress node in the payment record chain table, and sending a progress check message; the progress node at least comprises payment amount, and the progress checking message indicates a progress indication file to be recorded; receiving a progress indication file corresponding to the progress check message to record the progress indication file into the progress node, and sending a progress payment message; receiving a payment bill corresponding to the progress payment message to record the payment bill into the progress node. Wherein the progress node in the payment record linked list is an immutable node.

In one or more embodiments of the present application, when the processor executes the program, the following steps are further performed: the progress indication file and the bill for payment are reviewed and payment is performed by a third party.

Finally, the present application discloses a storage medium, wherein the storage medium has stored therein a computer program. The computer program is arranged to perform the following steps when executed: initializing a payment record linked list of the engineering project; responding to the received project progress payment request, creating a corresponding progress node in the payment record chain table, and sending a progress check message; the progress node at least comprises payment amount, and the progress checking message indicates a progress indication file to be recorded; receiving a progress indication file corresponding to the progress check message to record the progress indication file into the progress node, and sending a progress payment message; receiving a payment bill corresponding to the progress payment message to record the payment bill into the progress node. Wherein the progress node in the payment record linked list is an immutable node.

In one or more embodiments of the application, the computer program is arranged to perform the following further when executed: the progress indication file and the bill for payment are reviewed and payment is performed by a third party.

The technical solutions provided by the embodiments in this description can be used to organize, manage and monitor the operational flows in a construction project to ensure quality control (monitoring and inspection) of the construction project. The progress is managed and verified in the project process, and disputes of invoicing and payment are avoided. In particular, the system and method utilize a blockchain to record project progress, check progress and pay bills, so that the payment process is transparent to the participants and cannot be tampered.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of embodiments of the invention.

In addition, any one of the embodiments in the present specification is not required to achieve all of the effects described above.

Drawings

Fig. 1 is a schematic flow chart of a payment method based on project progress according to an embodiment of the present invention;

FIG. 2 is a message flow diagram illustrating a payment method according to an embodiment of the present invention;

FIG. 3 is a diagram illustrating a data structure of a payment record linked list used in a payment method;

FIG. 4 is a detailed block diagram of the progress data of FIG. 5;

fig. 5 is a schematic diagram of an apparatus for configuring a method according to an embodiment of the present invention.

Detailed Description

The conception, the specific structure and the technical effects of the present invention will be clearly and completely described in conjunction with the embodiments and the accompanying drawings to fully understand the objects, the schemes and the effects of the present invention. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The same reference numbers will be used throughout the drawings to refer to the same or like parts.

Fig. 1 is a schematic flowchart of a payment method based on project progress of a blockchain according to an embodiment of the present invention. The method comprises the following steps:

s100: a linked list of payment records for the engineering project is initialized.

S200: and responding to the received project progress payment request, creating a corresponding progress node in the payment record linked list, and sending an advance check message. The progress node at least comprises payment amount, and the progress checking message indicates a progress indication file to be recorded.

S300: and receiving a progress indication file corresponding to the progress check message, recording the progress indication file into the progress node, and sending a progress payment message.

S400: receiving a payment bill corresponding to the progress payment message to record the payment bill into the progress node;

wherein the progress node in the payment record linked list is an immutable node. The execution subject of the method can be specifically a server of the electronic payment platform. The server may be accessed and accessed by hardware devices such as mobile terminals or personal computers by developers, schedule checkers (e.g., architects and surveyors), contractors, subcontractors, and suppliers, as relevant participants to the construction project. Because the payment record linked list is stored on the personal terminals or distributed storage media (including cloud ends) of a plurality of participants in a distributed mode in a decentralized mode of the block chain, the content on the payment record linked list is difficult to be tampered maliciously. Meanwhile, as the related information of the payment record linked list can be accessible to all the participants, the transparency of the payment process is increased. The steps performed by the electronic payment platform (i.e., the steps performed by the server of the electronic payment platform) are described below.

According to the embodiment of the invention, in step S100 after the project is started, a developer, a contractor, a third-party management organization, or the like may initialize the payment record chain table on the server of the electronic payment platform, and publish a way of accessing and acquiring the payment record chain table to the relevant participants of the building project. Meanwhile, in order to ensure that the payment record chain table is obtained or maliciously tampered by an unrelated third party, after the payment record chain table of the engineering project is initialized, the server can identify the actual identity of each user (i.e. a developer, a progress checker, a contractor, a subcontractor, a supplier and other related participants) which receives the message, sends the engineering progress payment request and sends the progress indication file. The verification method may be an existing verification technical means such as an electronic signature, a credit card, and the like, and a person skilled in the art may select an appropriate verification method according to a specific actual need, which is not specifically limited in this application. Only the verified user has access to the linked list of payment records for the item. In particular, the payment record chain table may be distributively stored on a personal terminal (e.g., a mobile terminal, a personal computer, etc.) or a distributed storage medium (e.g., a cloud) of each authenticated user, so that the related information is transparent and can be uniformly shared by each authenticated user. Alternatively, however, according to embodiments of the present invention, the rights to identify the received message, the sent project progress payment request, and the progress indication file may be assigned based on the actual identity of each user. For example, developers, general contractors, subcontractors, surveyors, architects, etc. will have different access rights when preparing and approving different progressive payment applications.

Referring to fig. 2, when a subcontractor or provider of a construction project prime contractor settles a project in stages as required at the completion of a specific schedule or at a specific time of each schedule period (e.g., the end of a month), it may initiate a payment application by the prime contractor and create a new schedule node at the end of the payment record chain. Referring to fig. 3, the progress node may include a data header, progress data, and a digital signature. For example, the progress node includes at least a payment amount.

In some embodiments of the present application, the prime contractor may fill out the payment application page as fed back on the personal terminal. For example, the payment application page requires the type of request to fill out the project payment and the project progress to be settled. Of course, the user fills out the requested payment amount and/or the payment bank account number in the payment application page. After the payment application page is filled out and submitted, the personal terminal may broadcast a progress check message to the various associated participants of the construction project via the server. Alternatively, the personal terminal may also directly send a progress check message to the progress checker, and the related progress checker performs the checking work of the project progress. In particular, the progress checking message indicates a progress indication file to be recorded, so that the progress indication file is automatically checked in the uploading process or checked by a progress checker in the uploading process.

In other embodiments of the present application, the payment application may also be initiated by the subcontractor/provider. For example, the SCE/supplier can declare the project payment to be paid according to the payment application page fed back from the personal terminal. The payment application page requires the type of request (e.g., project progress or material settlement) and amount of money to be filled out by the subcontractor/supplier. Of course, the user fills out the requested payment amount and/or the payment bank account number in the payment application page. After the payment application page is filled out and submitted, the personal terminal may broadcast a progress check message to the various associated participants of the construction project via the server. The related requests may be automatically aggregated to the general contractor on a periodic basis, or submitted to the prime contractor on the fly. The prime contractor submits requests from the subcontractors/suppliers en masse to progress verifiers who, in turn, perform project progress verification work, respectively (e.g., surveyors and architects). For example, after checking the confirmation, the surveyor issues a payment audit with an electronic signature and uploads it as a progress indication file into the linked list. The architect then issues a "certificate of payment" with an electronic signature after checking for confirmation and uploads it to the linked list as a progress indication file. Similarly, the progress checking message indicates a progress indication file to be recorded so as to realize automatic checking of the progress indication file in an uploading process or checking by a progress checker in the uploading process.

Referring to fig. 1 and 2, according to an embodiment of the present invention, before performing step S300, the progress checker may check the specific progress status of the construction project after receiving the progress check message. For example, an assessment of the progress of a project by a surveyor (e.g., construction phase photographs) and an architect review of the progress of the project form a progress indication document, such as an application document and a certification document, respectively, for supporting payment. Referring to fig. 4, a related progress indication file may be recorded into the progress node. Particularly, in the embodiment of the application, the progress indication file such as the construction phase photo or the material stocking is sent to the corresponding progress node through the internet. Meanwhile, in order to avoid potential disputes, the progress indication file sent to the corresponding progress node via the internet is read only after being uploaded. Alternatively, a photograph or other progress indication file of the construction phase may be automatically and securely saved in the payment record linked list. These data, which are used to indicate the progress of the construction, are also not modifiable to ensure integrity, transparency, and trust between the parties.

Referring to fig. 1 and 2, in accordance with an embodiment of the present invention, the progress payment message transmitted to the developer may include an invoice that the prime contractor intends to make based on the current project progress payment request when performing step S300. After the developer examines the progress indication file and the invoice in the progress node corresponding to the project progress payment request, the developer can pay for the prime contractor through a third-party financial institution such as a bank. For example, in some embodiments of the present application, the prime contractor issues invoices with electronic signatures to the developer. The invoice may also be saved to a linked list of payment records. Referring to fig. 1 and 4, in accordance with an embodiment of the present invention, a payment bill and an invoice may be recorded into the progress data of the progress node when step S400 is performed. At this point, the progress node is an immutable node in the payment record linked list, so that the payment process at each stage of the overall project is transparent and immutable to all relevant participants to ensure trust between stakeholders.

According to an embodiment of the invention, the payment record linked list may provide access to a third party (e.g., a financing institution such as a bank) in a read-only manner. This helps stakeholders (e.g., subcontractors, suppliers) to raise funds on the one hand, and also allows loan issuers to assess timely changes in project risk on the other hand. For example, in some embodiments of the present application, a developer authorizes electronic payments connected to a bank through a blockchain network. The bank pays the contractor, thereby allowing the contractor to receive the electronic payment.

Fig. 5 is a schematic diagram of a payment device based on project progress provided by an embodiment of the invention. As shown in fig. 5, the project progress-based payment apparatus of this embodiment includes: a processor, a memory, and a computer program stored in the memory and executable on the processor, such as a payment program based on project schedule. Further, as shown in fig. 5, the engineering progress based payment device may include the engineering progress based payment device may further include an input output device, a network access device, a bus, and the like.

The processor, when executing the computer program, implements the steps in each of the above embodiments of the project progress-based payment method, such as steps S100 to S400 shown in fig. 1.

Illustratively, the computer program may be partitioned into one or more modules/units that are stored in the memory and executed by the processor to implement the invention. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution process of the computer program in the engineering progress based payment device.

The payment device based on the engineering progress can be a desktop computer, a notebook, a palm computer, a cloud server and other computing devices. The engineering progress based payment device may include, but is not limited to, a processor, a memory. Those skilled in the art will appreciate that FIG. 5 is merely an example of a project schedule-based payment device and does not constitute a limitation of a project schedule-based payment device. Those skilled in the art may arrange more or fewer components than those shown, or combine certain components, or different components, according to actual needs.

The Processor may be a Central Processing Unit (CPU), or may be other general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, a discrete hardware component, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described system embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method according to the above embodiments may be implemented by a computer program, which may be stored in a computer readable storage medium and used by a processor to implement the steps of the above embodiments of the method. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc.

Embodiments of the present invention also provide a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method illustrated in fig. 1.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave. It should be noted that the computer readable medium may contain suitable additions or subtractions depending on the requirements of legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media may not include electrical carrier signals or telecommunication signals in accordance with legislation and patent practice.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present invention, and are intended to be included within the scope of the present invention.

Claims

1. A payment method of project progress based on a block chain comprises the following steps:

initializing a payment record linked list of the engineering project;

responding to the received project progress payment request, creating a corresponding progress node in the payment record linked list, and sending an advance checking message; the progress node at least comprises payment amount, and the progress checking message indicates a progress indication file to be recorded;

receiving a progress indication file corresponding to the progress check message to record the progress indication file into the progress node, and sending a progress payment message;

receiving a payment bill corresponding to the progress payment message to record the payment bill into the progress node;

wherein the progress node in the payment record linked list is an immutable node.

2. Payment method according to claim 1, further comprising, after initializing the linked list of payment records for the engineering project, the steps of:

the actual identity of each user receiving the message, sending the project progress payment request, and sending the progress indication file is identified.

3. A payment method as claimed in claim 2, wherein the rights to identify the receipt of the message, to send the project progress payment request and to the progress indication file are assigned based on the actual identity of each user.

4. A payment method as claimed in any one of claims 1 to 3 wherein the progress indication file comprises a construction stage photograph or a progress certificate file.

5. The payment method of claim 4, wherein the payment record linked list is recorded in a distributed manner on a storage medium.

6. A payment method as recited in claim 4, wherein the linked list of payment records provides access to third parties in a read-only manner.

7. A payment method as claimed in claim 6, further comprising the steps of:

the progress indication document and the bill for payment are reviewed and paid by a third party.

8. A payment method as claimed in claim 4, wherein the progress indication file is sent to the corresponding progress node via the Internet.

9. The payment method of claim 8, wherein the progress indication file sent to the corresponding progress node via the internet is read-only.

10. Payment method according to claim 8 or 9 wherein the progress indication files in the linked list of payment records are automatically extracted and collated in chronological order as engineering progress reports.