변경사항을 유상 변경계약으로 전환
신선할 때 범위 변경을 기록하고, 합의된 단가로 계약 변경계약으로 산정한 뒤 다음 기성청구에 포함시켜, 추가 작업을 조용히 흡수하지 않고 회수합니다.
계약과 그 보증을 등록하고, 내역서에 대조해 기간을 실측하고, 선급금을 회수하고 유보금을 공제하고, 엔지니어가 기성 지급 확인서를 발급하게 하고, 조달법이 정한 지급 기간 내에 발주기관에 청구한다.
플랫폼 전반에 걸친 7단계 - 각 단계에서 무엇을 하는지, 그리고 왜 중요한지.
Record the contract, its the government procurement payment rules payment regime and the dates it turns on, so every later step reads the same terms instead of somebody's memory of them.
이유: A payment regime that lives in a PDF nobody opens is a regime that gets applied differently by each person who applies it. Registered once, the deadlines below are computed rather than argued about.
Record what was executed against each BoQ item for the period as a percentage of its contract quantity. The earned quantity follows from that percentage and the design quantity, and the earned amount from the same percentage and the position total, so one honest number per line produces the whole valuation.
이유: An interim payment certificate built from a single project percentage cannot be checked and therefore cannot be approved without a conversation. Measured line by line, the disagreement is about one BoQ item rather than about the whole month, and the rest of the money moves while that one is settled.
Read the valuation back against the bill and check the rates it used are the contract rates. Where a BoQ item has been measured past the quantity the contract carries, deal with it as a change to the position with an order behind it rather than as a larger figure on the same line.
이유: A variation order certified quietly is one the client can refuse at the final account, months after the work was built and paid for down the chain. Raising it as a change while it is small is the only version of that conversation where you are not asking to be paid for work already done.
Take the cumulative valuation, subtract what has already been certified, and apply retention at the contract percentage. The figure that leaves this step is the one the invoice is raised for, and the backup behind it is the measure that produced it. The advance is recovered on the proportion the period earned and the guarantee is reduced as it is recovered, so the two figures are read together rather than tracked in separate places by separate people.
이유: Interim payments are cumulative, so the month's money is a difference between two totals rather than a total of its own. Computing it from the cumulative figure is what stops a line being paid twice or dropped entirely when a period is re-measured.
Route the interim payment certificate to the Engineer, and to whoever the contract adds after them. Keep the approval date, because the invoice follows the approval and the payment clock runs from there, so an approval that slips moves everything behind it.
이유: Approval sitting in an inbox is the most common reason a payment is late, and it is invisible while it is happening because nobody has refused anything. A route with a date on each hop turns that into a question with an owner instead of a monthly complaint.
Raise the invoice against the approved interim payment certificate, carrying retention and any deduction the contract provides for, and reference the interim payment certificate on it.
이유: A demand for a figure nobody approved is one that will be returned, and the clock does not start on a returned document. Matching it to the interim payment certificate also means the accounts and the valuation tell the same story at year end without anybody reconciling them by hand.
Open a clock over the invoice starting from the day the invoice is submitted against the issued certificate, under the government procurement payment rules. Payment falls due 30 days later, and the clock records that date rather than leaving it to be worked out when somebody asks.
이유: The single most expensive mistake in interim payment is starting the count on the wrong event, because every deadline behind it inherits the error and none of them look wrong. Anchoring on the day the invoice is submitted against the issued certificate once makes the whole chain checkable. The window runs from a compliant submission, so an invoice returned for a missing attachment has not started anything even though it left your office. Recording what was submitted with it is what makes that visible on the day rather than at the end of the month.
플랫폼 190개 모듈 중 6개
Everything in this case follows how construction work is measured, priced and paid for in this market. The forms, the cost breakdown and the payment rules are the ones used there, not a generic version of them.
Standards it follows
You do not have to set any of that up by hand. The first time you open the platform it asks which market you work in. Choose this one and it sets the interface language, loads the matching cost database and records the cost classification, and it adds an example project you can open straight away.
The rule checks for this market come with the platform too. Switch them on once and an estimate that misses something the market expects is flagged while you are still working on it, not after the tender has gone out.
신선할 때 범위 변경을 기록하고, 합의된 단가로 계약 변경계약으로 산정한 뒤 다음 기성청구에 포함시켜, 추가 작업을 조용히 흡수하지 않고 회수합니다.
협력업체에 공종 패키지를 발주하고, 기성 내역서와 유보금 조건을 포함한 하도급 계약으로 전환한 뒤, 실제 완료된 작업에 대해 기성 청구별로 지급합니다.
계약서 대비 해당 기간 시공된 물량을 평가하고, 근거 자료와 함께 기성 청구를 제출하며, 승인된 금액을 실제 입금액과 대조 확인한다.