Contract finance: certificates, invoices and payments
On this page
- How contract finance works
- The Contract finance page
- The contract's finance panel
- The payment path of a payment application
- A payment application by main contract and change order
- The payment status of a payment application
- How to approve a payment application on a contract in finance
- How to include a contract in finance
- How to pause and resume finance on a contract
- Certificates of acceptance and payment
- Invoices
- Invoices submitted by subcontractors
- Payments
- The advance
- The contract ledger
- Warranty deductions and their release
- Reports
- Financial terms of a contract
- Finance alerts
- Finance settings and default terms
- Who can do what
- Attaching a document
- Common questions
- Related
| Where | Company sidebar → Contract finance (Финанси по договори), URL /companies/{company}/contract-finance, with the tabs Contracts, Certificates, Invoices, Submitted invoices, Payments, Warranty deductions, Reports and Settings: all projects combined. For one project: project sidebar → Contract finance, URL /projects/{project}/contract-finance, the same tabs for that project only, without Settings. On one contract: the Finance (Финанси) button in the action bar of a contract with a subcontractor (/projects/{project}/costs/evaluatedTaskList/{boq}/contract) or of your Contract with client (Договор с възложител) opens the contract's finance panel on the right. |
|---|---|
| Who can | Company permission Contract finance (Финанси по договори) at View to see the register and at Edit to work in it; Confirm certificates (contract finance) (Утвърждаване на сертификати (финанси по договори)) to confirm certificates and approve the other binding steps. Both are company-wide: they apply to every project of the company. The same plans as the Financial dashboard: paid plans or trial, not the Free plan. |
| Related | How a payment application works, Contracts: signing, details and history, Financial dashboard: committed, certified, margin, Permission reference |
How contract finance works
A payment application (Отчет) is only the net value of the executed and accepted works: quantities times contract prices, with no VAT and nothing deducted. Contract finance adds the money side, in your company's own register:
- Include the contract. Each company includes its own contracts, one by one, with a date of inclusion and the opening balances at that date. See "How to include a contract in finance" below.
- Approved reports are included in a certificate. Approving a payment application no longer creates its certificate. At approval, or later from the report's Payment path (Път на плащането), you choose Include in a certificate (Включи в сертификат): an open draft certificate of the contract, a new certificate for this report only, or later. Reports not yet in a certificate wait in Approved, without a certificate (Одобрени, без сертификат). New certificate (Нов сертификат) builds one certificate from one or more approved reports of the same contract. A certificate can start as a Draft (Чернова), which collects reports and has no number yet; a certificate made directly, or a draft sent for reconciliation, starts in status For reconciliation (За съгласуване) and freezes the figures by the contract's financial terms, one section for the main contract and one for each change order. The payment path shows the next step, including Include the contract in finance when the contract is not included yet.
- Your finance team checks and confirms it. The accountant checks the figures, marks a difference or asks for a replacement. The project lead, the owner or a manager confirms it. A confirmed certificate is the basis for the invoice.
- The invoice is issued in your accounting software and registered here against the certificate, by hand, from a PDF on the payment application, or (for a subcontractor's invoice) by accepting the subcontractor's submission.
- Payments are registered and allocated to the invoice's parts. The warranty deduction stays held until its release condition is met.
Both parties of a contract may track it, each in its own register. Each company sees only its own certificates, invoices and payments. The only things that cross to the other party are the contract's financial terms, which both parties see on the contract, the certificate PDF that the payer explicitly provides to the subcontractor, and an invoice the subcontractor submits.
| Direction (EN / BG) | When | What the register holds |
|---|---|---|
| Budget / Бюджет | Your company is the contract's receiver: you do the work and invoice your client. A self-contract with a client outside BuildColab counts too. | Receivables: outgoing invoices and the payments you receive. The certificate stays internal: the client receives only the invoice. |
| Cost / Разход | Your company initiated the contract: a subcontractor invoices you. A contract with a self-managed subcontractor counts too. | Payables: incoming invoices and the payments you make. You can provide the certificate to the subcontractor. |
The Contract finance page
Open Contract finance in the company sidebar. The page header reads "All projects · which contracts are tracked in finance". The entry is locked when your role has no Contract finance permission or your plan does not include it.
The company page combines all your projects. Every tab except Settings has a Project (Проект) column and, above it, the Project filter with All projects (Всички проекти) and each project that has a contract. The filter applies to every tab: the rows, the counts ("1–50 of {total}") and the report totals then cover that project only, and it stays when you switch tabs. With a project chosen, Open the project (Отвори проекта) opens that project's page on the same tab. A payment belongs to the projects of the contracts it is allocated to (its Project cell can name several); an unallocated payment belongs to none yet, so it is only on the company page with All projects. Bank statement imports stay on the company page: one statement spans projects.
Contract finance of one project
In a project in the Execution phase, open Contract finance (Финанси по договори) in the project sidebar, right after Report Register. The header reads "{project} · this project's contracts in finance". The page has the same tabs as the company page, narrowed to that project, without the Project column and the filter. The finance settings apply to the whole company, so there is no Settings tab: the Settings (Настройки) button in the header opens them on the company page. The entry needs the same company permission Contract finance as the company page and is locked without it; you do not need to be a member of the project team. External participants (guests) do not see it. The Open contract finance link in the project's Financial dashboard and Open in register in a contract's finance panel open this page. The By contracts (По договори) view of the project's Financial dashboard sums up the same contracts on one screen: three cards (Owed to us by the client, We owe subcontractors, Net position) and one table with the groups Client and Subcontractors, with Invoiced, Paid, Upcoming, Due, Overdue and Warranty deductions per contract, the status and the next step. Clicking a row opens the contract's panel, and a contract not in finance yet has the button Include (Включи).
| Tab (EN / BG) | What it shows |
|---|---|
| Contracts / Договори | Every contract your company is a party of, with its finance status for your company. The filters are All, Active, Draft, Not included and Paused, plus the search "Search contract, project or counterparty". Columns: Contract, Project (company page only), Counterparty, Type (Budget or Cost), Finance (the status), Included from and Action. The action is Include in finance (Включи във финансите), Continue inclusion (Продължи включването) or Open (Отвори); it opens the contract's finance panel on the right. A contract that cannot be included shows why: "Budget contract for your own investment" or "Contract in another currency". |
| Certificates / Сертификати | The certificate register, with bulk confirmation. |
| Invoices / Фактури | The invoice register: outgoing and incoming invoices, credit and debit notes. |
| Submitted invoices / Подадени фактури | Invoices subcontractors submitted to you, and the certificates payers provided to you. |
| Payments / Плащания | The payment register and the allocations to invoices. |
| Warranty deductions / Гаранционни удръжки | Every held and released warranty deduction, and its release. |
| Reports / Справки | Four reports with an xlsx download. |
| Settings / Настройки | The company's finance settings and default financial terms. |
The finance statuses of a contract are Not included (Не е включен), Draft (Чернова), Active (Активно) and Paused (На пауза). They are your company's status only; the other party may track the same contract or not.
The contract's finance panel
Click Finance (Финанси) in a contract's action bar, or Open on the Contracts tab. The panel Contract finance (Финанси по договора) shows the direction, the status, "Active since {date}" and the counterparty, then:
- Not included: "Finance is not included for this contract", the three steps "Choose the date of inclusion", "Enter the opening balances at that date" and "The project lead approves with a reconciliation file", and the Include in finance button. If payment applications were already approved, the panel says how many go into the opening balances.
- Draft: "Inclusion in progress", the date of inclusion, whether the checks pass, and Continue inclusion.
- Active or paused: the finance card, the contract's latest certificates, each with its payment path and next step, with Open in register (Отвори в регистъра), the contract's reports in Approved, without a certificate ({count}) with New certificate, its Draft certificates ({count}) (each opens its draft; with two or more, Merge the drafts (Обедини черновите)), the latest invoices, the Contract ledger and, for holders of Confirm certificates, the Pause or Resume button.
Terms: main contract and change orders (Условия: основен договор и анекси), on an active or paused register, lists the financial terms of the main contract and of every signed change order: Terms: main contract (Условия: основен договор), then Terms: change order No. {n} (Условия: анекс №{n}) for each change order in signing order, each with its signing date, its advance deduction, warranty deductions cap, payment term and warranty deductions rate. A change order with terms of its own says "The change order's own terms — they apply to it only."; one signed without terms of its own says "The change order has no terms of its own — the main contract's terms apply to it." A change order with terms of its own and no advance of its own shows No advance (Без аванс) instead of an advance deduction: its sections deduct nothing. The list is read only: terms are set on a draft and locked at signing. The currency and VAT are the same for the whole contract.
The finance card groups the figures:
| Group | Figures (EN / BG) |
|---|---|
| Certificates of acceptance and payment | Confirmed certificates (Утвърдени сертификати), Awaiting confirmation (Чакат утвърждаване), Confirmed, not invoiced (Утвърдено, нефактурирано) and "With an open difference: {count}". Confirmed certificates counts the whole contract to date: after an inclusion with history it includes the historical certificates entered at inclusion, which are never confirmed, not invoiced. |
| Invoices and payments | Invoiced (Фактурирано), Paid (Платено), Upcoming (Предстои за плащане), Due (Дължимо) and Overdue (Просрочено). Paid shows the payments registered after the date of inclusion; the line under it, "and {amount} paid before inclusion", shows what was paid before it, including the past invoices' payments entered with their dates in an inclusion with history. |
| Advance (Аванс) | Advance total, Made available (paid and confirmed), Deducted, Available, Still to deduct and Open on advance invoices. Made available (paid and confirmed) leaves out the advance that was paid and already deducted before the date of inclusion ("excluding {amount} paid and deducted before inclusion"); Deducted includes it ("incl. {amount} before inclusion"). When a change order has an advance of its own, Advance: main contract and change orders (Аванс: основен договор и анекси) lists under them the Main contract and each such change order, with its state (No advance, Unpaid, Awaiting invoice, Partly paid or Paid) and its Advance total, Paid in total (Платен общо, the advance paid before the date of inclusion included), Still to pay, Deducted, Available, Still to deduct and Open on advance invoices. A contract with only the main contract's advance shows no such list. |
| Warranty deductions (Гаранционни удръжки) | Accrued, Held, Released and Released, not yet paid. |
A certificate never counts as invoiced: only a registered invoice does. Upcoming, Due and Overdue split what is still open on invoice parts: Due is what falls due in the next N days (the «Due» window, 7 days by default), Overdue is past its due date, and Upcoming is due later, including parts without a due date ("of which {amount} without a due date"). Warranty deductions that are still held are in none of the three. "Today" is the date in Bulgaria (Europe/Sofia).
Main contract and change orders. The finance card, the contracts list, the dashboard's finance columns and every finance report show each figure for the main contract and for each change order signed with its own financial terms. A change order shows what its certificate sections, their invoices and payments and its own advance carry. The main contract shows everything else, so the main contract and the change orders always add up to the contract. A contract change made through a payment application, a budget re-acceptance or a subcontract annex counts in the main contract. On the card, once a change order has a share, Contract / change order (Договор / анекс) above the figures shows The whole contract (Целият договор), the Main contract (Основен договор) or one Change order No. {n} (Анекс №{n}). A change order whose number cannot be read is named Change order (contract version {n}) (Анекс (версия {n} на договора)). Every Contract Finance screen uses these same names. The counts in the lines ("{count} confirmed certificates" and the like) count a certificate or an invoice under the main contract and under every change order it has a share in, so they do not add up.
The payment path of a payment application
Once a payment application (Отчет) is approved, its header shows the button Payment path · Step {n} of {total} (Път на плащането · Стъпка {n} от {общо}) next to the report's status, with a small bar for each step (done, current, upcoming). When the next step is yours, the button is orange, with a dot, and its second line names the action, for example "Next: Include the contract in finance" (Следващо: Включи договора във финансите). The button opens Payment path in a panel that slides in from the right over the report: the payment's steps as a vertical list, with "Step {n} of {total} · Cost" (or Budget) above it. The report's table keeps the whole page. Close the panel with ✕, Esc or a click outside it. The first time, a hint under the button says "Here is the payment path — the report's next step" (Тук е пътят на плащането — следващата стъпка за отчета); Got it (Разбрах) hides it. Right after you approve the report, the panel opens by itself on the next step. The report is the centre of the payment: you do each step there.
- Step 0 · Advance (Стъпка 0 · Аванс) comes first when the contract represents an advance in your register: the advance of the main contract and of each change order with an advance of its own, with its state and, while it is still to be paid, the button to register it (see "Registering the advance" under "The advance").
- Done steps take one line each, with when and by whom where it is known, for example "Confirmed by Maria Stoyanova, 28.10.2026".
- The current step is expanded. Where its action fits on the page you do it there: Confirm shows the certificate's amounts (certified, advance deducted, tax base, VAT, to invoice, warranty deduction, payable now), the checkbox "After confirming, provide it to {subcontractor}" (ticked by default) and the buttons Mark difference, PDF and Confirm and provide (Утвърди и предостави), or Confirm when the box is cleared. Provide to the subcontractor and Hand over to accounting are one click. A submitted invoice shows its number, total, submission date and due date, and Review the invoice opens it next to its PDF. Steps that need a form (the inclusion, registering an invoice or a payment, submitting your invoice) open their dialog.
- Future steps say who takes them: "You", the subcontractor's name, "Approver (Confirm certificates)", "Finance" or "Accounting".
When the current step has nothing for you, only that step shows; Show all steps (Покажи всички стъпки) opens the list and Show the current step only closes it again. The path needs Contract finance at View; without it, or before the approval, it is not shown.
The steps depend on your side of the contract:
| Your side | Steps (EN / BG) |
|---|---|
| Cost: you pay the subcontractor | Report approved (Отчетът е одобрен) → Certificate (Сертификат) → Confirmation (Утвърждаване) → To subcontractor (Към подизпълнителя) → Invoice (Фактура) → Payment (Плащане). With a self-managed subcontractor there is no To subcontractor step, since nobody can receive the certificate on BuildColab: Confirmation is followed by Invoice. |
| Budget: you are paid and your company tracks the contract | Report approved → Certificate → Confirmation → To accounting (Към счетоводството) → Invoice → Payment. |
| Subcontractor that does not track the contract | Report approved → Certificate → Invoice → Acceptance (Приемане) → Payment. |
What the current step says, and its button:
| Current step (EN / BG) | Button |
|---|---|
| "The contract is not in your finance register" (Договорът не е включен във финансите ви). No certificate is created for the report until you include the contract. | Include the contract in finance (Включи договора във финансите): opens the inclusion dialog. After the inclusion is approved, the report waits in Approved, without a certificate to be included in a certificate. |
| "Including the contract in finance is not finished" | Continue the inclusion (Продължи включването). |
| "The contract's finance register is paused". No certificates are created while it is paused. | Resume the register (Поднови регистъра). Needs Confirm certificates. |
| "Include in a certificate" (Включи в сертификат): the report is approved and in no certificate yet. "One certificate can cover several reports of this contract." | The choice is made on the step: Add to Draft of {date} (Добави към Чернова от …) for each open draft certificate of the contract (the newest is chosen by default), Start a draft certificate (Започни чернова на сертификат) when there is none, New certificate for this report only (Нов сертификат само за този отчет) or Later (По-късно). The button reads Add to the draft, Start the draft, Create the certificate or Leave for later. New certificate from several reports (Нов сертификат от няколко отчета) opens New certificate with this report ticked. Needs Confirm certificates (contract finance); without it the step says "The report waits in «Approved, without a certificate» until an approver includes it in a certificate." |
| "In a draft certificate" (В чернова на сертификат): "The report is certified when the draft is submitted." | Open the draft (Отвори черновата). |
| "The certificate is being created" (Сертификатът се създава). It appears by itself in a few moments. | None. |
| "The certificate could not be created" (Сертификатът не можа да бъде създаден), with the reason, for example "The contract has no financial terms in force for this report's approval date." or "The contract's VAT regime is not supported yet." Creating it is retried automatically; if it keeps failing, contact support. | None. |
| "This report is in the opening balances": it was approved before the date of inclusion, or the inclusion covers it, so it gets no certificate. The path ends here. | None. |
| "Confirm the certificate" (Утвърдете сертификата) | Confirm (Утвърди). Without Confirm certificates (contract finance) the button is disabled and the card says who can confirm; under the four-eyes principle the certificate's creator cannot confirm it either. |
| "Provide the certificate to the subcontractor" (cost) | Provide to the subcontractor (Предостави на подизпълнителя). |
| "Hand the certificate over to accounting" (budget) | Hand over to accounting (Предай на счетоводството). |
| "Waiting for the subcontractor's invoice" (Очаква се фактура от подизпълнителя): the subcontractor is on BuildColab and submits its invoice against the certificate. | None; Register the invoice yourself (Регистрирай фактурата сам) is offered as a secondary button. |
| "Review the subcontractor's invoice" | Review the invoice (Прегледай фактурата): opens the submitted invoice to accept or return it. |
| "The invoice was returned to the subcontractor" | None; Register the invoice yourself as a secondary button. |
| "Register the subcontractor's invoice" (a self-managed subcontractor, an advance certificate) or "Register the invoice to the client" (budget) | Register invoice (Регистрирай фактура). If part of the certificate is already invoiced, the card says so. For a self-managed subcontractor, Download the PDF for the subcontractor (Изтегли PDF за изпълнителя) is offered as a secondary button: it attaches the certificate's PDF to the payment application if it is not attached yet, then downloads it for you to send. In the budget direction, when your client provided its own certificate on the report, Submit invoice (Подай фактура) is offered as a secondary button from the hand-over step on, also after you register your own invoice and the payment, until the invoice is submitted. Once it is submitted, the button becomes Open the invoice (Отвори фактурата), to see its status or withdraw it while it waits. If the client returned it, the button is Correct and submit again (Коригирай и подай отново) and opens the returned invoice with the client's reason. |
| "Register the payment" or "Register the payment received", with "Due {date}" or "Overdue since {date}" and "Still to pay: {amount}" | Register payment (Регистрирай плащане): opens the payment for this invoice. |
| "The invoice differs from the certificate" (Фактурата се различава от сертификата): an invoice still open on the certificate is in discrepancy, so no payment can be allocated to it. | Review the difference (Прегледай разликата): opens the invoice to accept the difference. Accepting needs Confirm certificates. |
| "Paid" (Платено). The card also lists any warranty deductions still held, with the expected release date, and the advance payments still to confirm on the contract. | None. |
For a subcontractor the current step is "Waiting for the certificate", "Submit your invoice" with the button Submit invoice (Подай фактура), "Waiting for your invoice to be accepted", "Your invoice was returned" with Correct and submit again (Коригирай и подай отново), "Your invoice was accepted" with the due date stated on the invoice, and finally "Your invoice was paid" (Фактурата ви е платена) with "Paid on {date}". While the payer has paid only part of it (a held warranty deduction counts), the card says "Partly paid (last on {date})". You see how far it is paid and the date of the latest payment, never the amounts or the payer's register. If the payer does not take invoices on BuildColab, the card says "Send your invoice to them directly".
Every step that changes the register needs Contract finance at Edit (opening a prepared inclusion with Continue the inclusion also works with Confirm certificates, to review and approve it); a step you may not take still shows, with its button disabled and a line saying who can. The link Open contract finance (Отвори финансите по договора) under the card opens the contract's certificates on the Contract finance page.
The next step after every action. On the payment application, the path itself moves on: after each step the next one is expanded in the list, and the message after an action is only a short confirmation (for example "The certificate is confirmed and provided to the subcontractor"). After you approve the report you stay on it: the message "The report is approved." appears and the path opens with "The report is approved. Continue with step {n} below." Links in notifications open the report with the right step: "Certificate of acceptance and payment received" opens the subcontractor's report on its Invoice step.
In the certificate dialog and the contract's finance panel, after you confirm, provide or hand over a certificate, accept a submitted invoice, register the invoice or register the payment, a message "Next step: {step}" (Следваща стъпка: …) appears once the dialog closes, with a button that opens the next step's dialog directly. While the certificate is being created, the message waits for it and then offers Confirm. When the certificate is paid, the message says "This payment's path is complete."
The same path, in a compact form, is shown under each certificate in the contract's finance panel and at the top of the certificate dialog, where its button runs the step in that dialog.
A payment application by main contract and change order
When a contract has at least one signed change order, the payment application (Отчет) header also shows the button Main contract and change orders (Основен договор и анекси), which opens the same panel on the section This report by main contract and change order (Отчетът по основен договор и анекси), under the payment path when there is one, for every party with Contract finance at View. A contract without a signed change order shows no such section: its payment application looks as before. The section's subtitle states the rule: "Executed work counts against the main contract first, then the change orders in signing order."
- Groups. The report's lines are grouped by what they count against, in signing order, each group with its subtotal on the right: Main contract (Основен договор), then Change order No. {n} — {signing date} (Анекс №{n} — дата). A contract change brought by a payment application with new positions is Payment application No. {n} — new positions; a budget re-acceptance and a BoQ subcontract annex have their own names. Report total (Общо за отчета) closes the table.
- A colored tag on every line names its group: Main (Основен), CO 1 (Анекс 1), CO 2 (Анекс 2) and so on, each change order in a colour of its own.
- A line split across the main contract and change orders appears in each group with its share, and under it the whole split, for example "split: Main 40,000.00 € + CO 1 20,000.00 €". This happens when a change order raised a position's quantity: the report fills the main contract's quantity first, then the change order's increment.
- A new unit price. A change order's new unit price applies to all quantity not reported yet. A line priced by a later change order carries the tag new price from CO {n} (нова цена от Анекс N), the note "the new price applies to all quantity not reported yet" and, under the unit price, "was {price}". Earlier reports keep their prices.
- Negative lines. When a change order lowers a position below the quantity already reported in earlier reports, the difference is added to the next report as a negative line in that change order's group, which is then marked "· corrections" (· корекции). The line is shaded red, its title ends with "reduced by CO {n}" and it explains "new contract quantity {quantity} · reported so far {quantity} → {difference}". A note above the table says: "A change order lowered a position below the quantity already reported. The difference is added to this report automatically as a negative line. Earlier reports are locked and do not change." A report whose quantity to date goes down against the earlier reports gets a "correction of the reported quantity" line, with "reported so far {quantity} → total {quantity}". A line above every contracted quantity is marked "beyond the contracted quantity".
- The filter. The buttons above the table, under Show (Покажи), show The whole contract (Целият договор) or only the main contract or one change order; Hide (Скрий) and Show (Покажи) fold the section.
The section may also say that positions are outside the signed contract and its change orders and are not split, or that the contract history is missing data for a change order or another change, so the split may be inaccurate. The split is computed for the selected company and is read only: it changes no quantity or amount of the report. The main contract and each change order keep their own financial terms, so the groups are the sections a certificate will carry.
Under the payment path. On an approved payment application of a contract with at least one signed change order, a read-only panel This report · main contract and change orders (Отчетът · основен договор и анекси) sits under Payment path: "Report No. {n}", each line with its tag (main contract or change order) and amount, and the total. Under it: "The split was frozen at approval — it is not recalculated." (before the approval: "The split is frozen when the report is approved."). A report is locked once approved, so later change orders never move its split; their effect comes in the next report.
The payment status of a payment application
Each company sees its own finance status of a payment application, as a second pill beside the report's status (submitted, approved, countered …), never instead of it. It shows in the Payment (Плащане) column of the report registers, which can also be filtered by it, in the payment application's header beside its title, in the contract's finance panel next to each certificate, and on the Contract finance page next to the certificates and the submitted invoices.
| Your side | Statuses (EN / BG) |
|---|---|
| The paying side (your company tracks the contract) | "Not in finance" (Не е във финансите), "Register paused" (Регистърът е спрян), "In the opening balances" (В началните салда), "No certificate yet" (Без сертификат), "For reconciliation" (За съгласуване), "Confirmed" (Утвърден), "Handed over to accounting" (Предаден на счетоводството), "Provided" (Предоставен), "Invoice awaiting acceptance" (Фактура чака приемане), "Returned for correction" (Върната за корекция), "Invoiced" (Фактуриран), "Due {date}" (Падеж …), "Overdue" (Просрочен), "Partly paid" (Частично платен), "Paid" (Платен). |
| A subcontractor without its own finance register | "Awaiting certificate" (Очаква сертификат), "Certificate received — submit your invoice" (Сертификат получен — подайте фактура), "Invoice submitted — awaiting acceptance" (Фактура подадена — чака приемане), "Returned for correction", "Invoice accepted" (Фактура приета), "Due {date}", "Overdue", "Partly paid", "Paid". A certificate invoiced with a separate invoice for the main contract and each change order shows "Invoice partly accepted" (Фактура приета частично) while only some of its invoices are accepted, and "Invoice partly returned" (Фактура върната частично) while one of them is returned. |
"Overdue" is red and "Returned for correction" orange. In the header and the finance panel a second pill shows the warranty deduction kept on the report: "Retention held" (Удръжка задържана), "Retention partly released" (Удръжка частично освободена) when part of it was released with its stage, or "Retention released" (Удръжка освободена). Hovering over the status shows the due date and the date of the last payment.
How a subcontractor records a payment it received
A subcontractor that keeps no finance register of its own records what its payer paid. On its accepted invoice (the payment path's last step, or the invoice opened from Submitted invoices) click Payment received (Получено плащане), enter the Payment date, the Amount and optionally the Bank reference, and confirm. The report then shows "Partly paid" or "Paid", and when it is paid in full its payment path is complete. The payments you recorded are listed under Payments received (Получени плащания) on the invoice; Cancel (Анулирай) cancels one with a reason, and it stays listed as cancelled. The button appears only where the payment is yours to record; a company with its own register registers payments in it.
How to approve a payment application on a contract in finance
When your company pays on the contract (Cost) and the contract is in your finance register, Approve (Одобри) on a payment application opens Approve {report} (Одобри …) in three steps:
- Quantities (Количества): the report's confirmation, including any new positions it adds to the contract. To change a quantity, close the dialog and edit the report.
- Certificate (preview) (Сертификат (преглед)): the certificate of acceptance and payment this report gets on its own (a new certificate), by the contract's financial terms. Nothing is saved yet. If the report can get no certificate (it is covered by the opening balances), the step says so.
- Confirmation (Потвърждение): when you hold Confirm certificates (contract finance), first Include in a certificate (Включи в сертификат): an open draft certificate of the contract (the newest is chosen by default), Start a draft certificate when there is none, New certificate for this report only (with the amount to invoice) or Later (the report waits in Approved, without a certificate). With a new certificate and four-eyes off in the finance settings, you can also choose Approve and confirm the certificate and, under it, "…and provide it to {subcontractor}". Otherwise only the approval is offered, and the step says who confirms the certificate. Without Confirm certificates there is no choice: the report waits in Approved, without a certificate. With a draft chosen, the step shows which draft the report joins and the certificate that draft would make with it, per section, for example "The report will be added to Draft of 21.10.2026 (Payment applications No. 2, No. 3)." or "A new draft will be started (Payment application No. 3)."; a draft that can no longer take the report says why ("The report cannot go into this draft: …").
A self-managed subcontractor. For a payment application you record on its behalf, Finalize (Финализирай) is the approval. When the contract is in your finance register it opens Finalize {report} (Финализирай …) in the same three steps. In the last one you choose Only finalize the report (Само финализирай отчета) or Finalize and confirm the certificate (Финализирай и утвърди сертификата), and the last button reads Finalize the report or Finalize and confirm. There is no "…and provide" choice for a self-managed subcontractor, in this dialog, in Approve or on the payment path: confirming also attaches the certificate's PDF to the payment application, and nobody is notified. After finalizing, the report opens with its payment path on the next step, and the message starts with "The report is finalized." when the certificate was confirmed too.
Next (Напред) and Back move between the steps; the last button reads Approve, Approve and add to the draft (Одобри и добави към черновата), Approve and confirm or Approve, confirm and provide. The approval always stands: if the report cannot be included in a certificate, or the certificate cannot be confirmed or provided, the message after the approval says why (for example "The report is approved. It was not included in a certificate: … It waits in «Approved, without a certificate»."), and the payment path shows where it stands. When the message is "Your permissions could not be checked just now. Try again.", it has a Try again (Опитай отново) button that confirms (and provides) again; in the dialog the same message re-reads the preview. It does not mean you lack the permission. When the certificate is not confirmed in the same step, the people who confirm certificates get the notification "Certificate {code} for report No. {n} on {contract} is waiting for your confirmation", which opens the report on the confirm step. Approving the report is binding for the subcontractor, and a confirmed certificate is never overwritten: a correction is a new version. On a contract that is not in finance, or when your company is the one paid, Approve asks for a simple confirmation as before.
How to include a contract in finance
You can include a signed base contract in EUR. Unsigned contracts, contracts in another currency, change-order records and budget contracts for your own investment cannot be included; the panel then says "This contract cannot be included in finance".
- On the Contracts tab click Include in finance, or open the contract's finance panel and click Include in finance. This needs Contract finance at Edit. The dialog Include in finance — opening balances (Включване във финансите — начални салда) opens. Its steps depend on how you give the opening state, chosen on the first step.
- Date of inclusion (Дата на включване): from this date the register keeps the contract; it cannot be in the future. Enter the Counterparty name, which is printed on the certificates, and optionally its UIC (ЕИК) and VAT number. Then answer How do you enter the state as of the inclusion date? (Как въвеждате състоянието към датата на включване?): With history: pay applications, invoices, payments and advances (С история — отчети, фактури, плащания и аванси) works the balances out from what happened before the date, and the totals from accounting become the reconciliation check; Totals only (Само салда) takes only the four balances, the unpaid invoices and the unallocated payments, for a contract without detailed history. Switching between the two loses nothing you saved.
- Contract, change orders & terms (Договор, анекси и условия): the terms come from the signed contract. If the contract was signed without financial terms, enter them from the signed document, with Signed on and the Signed contract (file), uploaded or chosen from the File Manager (see "Attaching a document"). Below that, Change orders (Анекси) lists every change order signed up to the inclusion, as Change order No. N — signed on its date. Only a change order has terms of its own: a contract change made through a payment application, a budget re-acceptance or a subcontract annex runs on the main contract's terms and is not listed. A change order with its own signed terms shows Own terms (signed), one that took the main contract's shows Main contract's terms; nothing is entered for them. A change order signed without financial terms needs a choice: Own terms (Собствени условия) — enter its terms from the signed change order (the same fields as the contract's terms; VAT is contract-wide, so the main contract's applies), its Advance (net), its Warranty deduction, %, the Signed on date and the Signed change order file, which is required (the advance, rate and date are prefilled from the change order) — or Same as the main contract (Като основния договор), when nothing is entered and its lines are certified in the main contract's section on its terms. Own terms are kept in your register only, from the approval; the counterparty does not see them. Each such change order's lines then get their own section in every certificate, with these terms. With history, when a change order has terms of its own, the advance you enter for the contract is the main contract's only: "The advance here is the main contract's only. Change orders with their own terms have their own advance."
- With Totals only, Opening balances (Начални салда): the advance (Invoiced (excl. VAT), Deducted in payment applications, Available (paid, not yet deducted)), the Warranty deductions accrued, the Unpaid invoice parts (+ Add invoice: kind, number, dates, amounts, the warranty deduction in it and its release condition, the due date and what was Paid before inclusion) and the Unallocated payments (+ Add payment). Historic balances never enter the cash flow as new payments. A saved invoice with several warranty-deduction stages keeps its amounts as saved: the form shows one deduction only, so its amount fields are locked; remove the invoice and add it again to change them.
- With history, Historical PAs (Исторически отчети): + Add pay application for every pay application certified before the date of inclusion, with its Pay application number, Approved on (on or before the date of inclusion), a note and the Certificate or pay application (file). Each has one or more sections: Section (Main contract, or a change order with a section of its own), Certified (net, €), Advance deducted (€) and Warranty deduction (€); + Add section adds the next one. The approval records each as a historical certificate, with no new balance movements.
- With history, Invoices & payments (Фактури и плащания): every invoice from before the date of inclusion, paid or not, as with + Add invoice above. Instead of Paid before inclusion, enter each payment under Payments before the inclusion (+ Add payment: date, amount, bank reference, note); an invoice never has both. An advance invoice also says whose advance it is (Advance of: the main contract or a change order with an advance of its own). An invoice's held warranty deduction says whose deduction it is (Belongs to (Към): the Main contract, or a change order with terms of its own, which then releases it by its own stages), and Pay applications invoiced ticks the historical pay applications it invoiced. The Unallocated payments follow.
- With history, Advances (Аванси): Advances paid without an invoice (+ Add advance without invoice: whose advance, date, amount, bank reference, note). Such an advance becomes available only once its invoice is registered and the payment is allocated to it. Below, Advance by contract and change order shows, as of the last save, what was Invoiced, Paid, Deducted, Available and Paid without invoice for the main contract and each change order with its own advance.
- With history, Reconciliation (Сверка): enter the Balances from accounting (the four balances above). After a save, the table shows each balance From the history, From accounting and the Difference, with every difference highlighted. The approval records the totals from the history. While any difference is not zero, the Explanation of the difference is required.
- Covered applications (Покрити отчети): tick every payment application approved on or after the date of inclusion that the opening balances already cover. The covered ones must be exactly those approved since that date. Covered payment applications get no certificate.
- Click Save draft (Запази чернова) at any step. Nothing is recorded in the register until the draft is approved. If a colleague saved the draft while you had it open, a message says so and Save draft and approval stay disabled until you click Reload the draft (Презареди черновата): saving the older form would overwrite their entries.
- Approval (Одобрение): the Checks list what still blocks the approval, for example "Change orders without a decision: No. 2" or "Difference from the balances from accounting: Available (paid, not yet deducted). Correct it or explain it."; click Refresh checks after a change. A user with Confirm certificates attaches the Reconciliation file (Файл за сверка) from accounting, uploaded or chosen from the File Manager, and clicks Approve and activate (Одобри и активирай).
If a payment application is approved, a covered one is no longer approved, or a change order or another change of the contract is signed after the draft was prepared, the draft is out of date: refresh it with Save draft and check it again. If someone else refreshed the draft while you had it open, the dialog says so; click Reload the draft before approving.
Import the history from Excel
In history mode you can fill the Historical PAs, Invoices & payments and Advances steps from an Excel file instead of typing them. The import is at the top of the Historical PAs step, under Import from Excel (Импорт от Excel).
- Save the draft first: the date of inclusion decides what the history is. Until the draft is saved, and while the form has unsaved changes, the import says "Save the draft first".
- Click Download template (Изтегли шаблон). The template is made for the contract, in the language of the app. It has one sheet each for the payment applications certified before the date of inclusion (one row per section: the main contract, or a change order with a section of its own), the invoices issued before it, the payments made on them, and advances paid without an invoice. The Versions sheet names the contract's change orders as you write them in the Section and Advance of columns.
- Fill in the file and click Upload or choose the file (Качи или избери файл): upload it, or choose it from the File Manager (see "Attaching a document"). BuildColab checks every row at once; nothing is saved yet.
- Read the report: how many pay applications (and sections), invoices, invoice payments and advances without invoice the file has, and which parts of the draft it will replace, for example "Will replace: Pay applications, Invoices. What these steps of the wizard hold now will be overwritten." Each sheet with rows replaces that part of the draft; a sheet you leave empty keeps what you entered. Every problem is listed with its Sheet, Row, Column and Problem. Correct the file, upload it again or click Check again.
- When the file has no problems, click Apply (Приложи). The draft is saved with the imported history and the wizard reloads from it. The draft is not booked until it is approved.
A file that is not the filled template is refused: "The file is not the filled template (.xlsx). Use the template, or ask BORO to read a PDF / Word document." If the file or the draft changed after the check, Apply is refused with "The file or the draft changed; check again." and the file is checked again. The import does not link a historical pay application to its file or to a pay application on the platform; add those in the step afterwards.
Complete the history
An approved inclusion is fixed. If its history missed something, such as a pay application certified before the date of inclusion, a past invoice, a payment made before that date or an advance paid without an invoice, complete it with a history amendment. Nothing entered at the inclusion is changed.
- On the contract's finance panel, under History amendments (История на корекциите), click Complete the history (Допълни историята), or Continue amendment No. N for the open draft. You need Contract finance at Edit. A register has one draft amendment at a time.
- Reason and document (Причина и документ): enter the Reason (shown in the register's journal, at most 900 characters) and attach the Supporting document, uploaded or chosen from the File Manager (see "Attaching a document"). The step shows the chosen file's name. Both are required.
- Historical PAs, Invoices & payments and Advances work as at the inclusion with history (see "How to include a contract in finance"). Under Payments on invoices already in the register, + Add payment to an invoice from the history adds a payment made before the date of inclusion on an invoice recorded at the inclusion or by an earlier amendment. Each invoice is offered with its unpaid current part ("Invoice {number} · current part unpaid {outstanding}"): a payment in a history amendment settles the current part only. A held warranty deduction is released and paid in the register; a payment that would need it is refused ("The payment exceeds the invoice's unpaid current part…"). You can also fill these steps from the contract's Excel template with Import from Excel at the top of Historical PAs, as at the inclusion (see "Import the history from Excel"). On the Invoice payments sheet, a payment of an invoice already in the register's history goes to Payments on invoices already in the register. For a new amendment, enter the Reason first: "Enter the reason in step 1 first: the import opens a new amendment with it." The Supporting document of step 1 becomes its evidence, or the imported file when none is attached. An open draft keeps its own reason and document.
- Click Save draft. On Review and approval (Преглед и одобрение) you see, as of the last save, what the approval would record: certified, warranty deductions, invoiced, paid and advances without invoice, and Change to the advance by contract and change order, which shows what each advance figure changes by. Available can go down when the history deducts more. The Checks list what blocks the approval, for example "The available advance would fall below zero; correct it with an adjustment."
- Someone with Confirm certificates (contract finance) clicks Approve the amendment (Одобри корекцията) and confirms with Yes, approve (Да, одобри): "The approval is final: amendment No. {n} is booked into the register and cannot be undone. Approve it?" Back (Назад) leaves the draft unapproved. With the four-eyes principle on, the approver is a different person from the one who prepared it ("Someone else must approve it."). Discard the draft (Откажи черновата) drops a draft you do not need; it stays in the list as Discarded.
Every amendment is listed under History amendments with its number, its status (Draft, Approved or Discarded), who prepared and approved or discarded it and when (for example "Prepared by Maria Ivanova on 04.11.2026 · approved by Ivan Petrov on 05.11.2026"; only the date when BuildColab has no name for the person), its reason, its Supporting document and, once approved, links to the certificates, invoices and payments it recorded. If someone saved the draft while you had it open, the dialog says so; click Reload the draft before you save or approve.
How to pause and resume finance on a contract
A holder of Confirm certificates clicks Pause (Пауза) in the contract's finance panel, enters a Reason and confirms. While paused, no new certificates are created for this contract; approving payment applications is not affected. Resume (Поднови) continues the register; the payment applications approved during the pause then wait in Approved, without a certificate. The panel of a paused contract shows "Finance is paused", the reason and the date.
Certificates of acceptance and payment
A certificate covers one or more approved payment applications of one included contract (see "Grouping reports into certificates"), and an advance certificate is created for the contract's advance (at inclusion, or when a signed change order or another change of the contract raises the advance). It is not an invoice: it is the basis for issuing one. It has its own number (a BC code) and version.
A certificate marked Historical (Исторически) was recorded at the inclusion from a pay application certified before the date of inclusion: "Recorded at the inclusion from a pay application certified before the date of inclusion. It never changes." It has no payment path, no actions, no PDF or Excel, and is never invoiced again; trying anyway is refused with "A historical certificate never changes."
Statuses
A certificate starts as a Draft. While it is a draft you can add or remove approved payment applications freely; it has no number and changes nothing in the register yet. Send for reconciliation turns it into a certificate For reconciliation with its number and figures. The certificate registers show open drafts next to the certificates.
| Status (EN / BG) | Meaning | What you can do next |
|---|---|---|
| Draft / Чернова | A certificate in preparation. "Payment applications can be added to and removed from a draft freely. The certificate gets its number and figures only when it is sent for reconciliation." | Add or remove reports, send it for reconciliation, discard it. |
| For reconciliation / За съгласуване | Just created; the figures are frozen and wait for the finance check. | Mark a difference, replace, confirm. |
| Confirmed / Утвърден | Confirmed by the project lead, the owner or a manager. | Hand over to accounting, provide to the subcontractor, register an invoice, replace while no invoice is allocated. |
| Handed over to accounting / Предаден на счетоводството | Handed to the accountants to issue the invoice. | Register an invoice; replace only after confirming that no invoice was issued (also for a certificate provided to the subcontractor). |
| Invoiced / Фактуриран | Registered invoices cover the whole amount to invoice. Reversing an allocation reopens it. | Corrections only through a credit or debit note. |
| Replaced / Заменен | A corrected version replaced it, or a merge did (the merged certificate is its next version). Invoices go against the new version. | Nothing; open the new version. |
| Cancelled / Анулиран | Its external payment application was voided, or it was merged into another certificate. | Nothing. |
The kinds are Advance (Авансов), Interim (Междинен) and Final (Окончателен). An advance certificate of a change order's own advance is named Advance — Change order No. n (Аванс — Анекс №n). A certificate can also carry the Difference (Разлика) flag: a difference to reconcile.
The certificate register
The Certificates tab filters by status (All, Drafts, For reconciliation, Confirmed, Handed over to accounting, Invoiced, Replaced / cancelled), by direction (Budget / Cost), With a difference to reconcile and Not fully invoiced. Open in register on a contract's panel opens the tab on the contract's project page, filtered to that contract ("Contract: {name}"; All contracts clears it). Above the register, Approved, without a certificate ({count}) lists the reports waiting for a certificate (see "Grouping reports into certificates"). Columns: Certificate, Contract, Project (company page only), Type, Payment application (every report a certificate covers, for example "3, 4"), Finance (status), Created, To invoice, Payable now and Not invoiced yet.
Drafts (Чернови) reads Drafts ({count}) when there are open drafts in the page's scope (the project, the contract filter and the direction). It lists the open draft certificates instead of certificates, under the line "Payment applications can be added to and removed from a draft freely. The certificate gets its number and figures only when it is sent for reconciliation." Columns: Draft ("Draft of {date}"), Contract (with the counterparty), Type, Reports ("Reports: {count}"), Finance (Draft), Created and Reports' value. Click a row to open the draft. With no open draft it says "No open draft certificates. A draft is started when a report is approved, from its «Include in a certificate» step, or with «Save draft» in «New certificate»."
What a certificate shows
Click a row to open it. The dialog Certificate of acceptance and payment names every payment application the certificate cites (for example "Payment applications No. 3, No. 4") and shows Issued by and Issued to with UIC and VAT number, and the Amounts:
| Figure (EN / BG) | Meaning |
|---|---|
| Value of the accepted works (excl. VAT) / Стойност на приетите работи (без ДДС) | The approved payment application's value; on a GC contract split into Works and Markup. |
| Advance deducted / Приспаднат аванс | The part of the paid advance deducted on this certificate. |
| Tax base / Данъчна основа | The value minus the advance deducted. |
| VAT 20% / ДДС 20% | Proposed VAT on the tax base. |
| Amount to invoice / Сума за фактуриране | Tax base plus VAT: what the invoice should state. |
| Warranty deduction / Гаранционна удръжка | Held back at payment, until released. When a release stage was already released, the row under it reads "of which released — stage "{condition}" (released on {date})" with the amount added back: that part is released at once. |
| Other deductions / Други удръжки | Shown only when set by a replacement. |
| Payable now / Дължимо сега | What is paid on the invoice before the warranty deduction is released: the amount to invoice, minus the warranty deduction, plus what of it is released at once, minus other deductions. |
When the payment applications include change-order work, the certificate has one section for the main contract and one for each change order, listed under Sections: main contract and change orders (Раздели: основен договор и анекси): the Main contract, then each change order (Change order No. n — dd.mm.yyyy), each with its own value, advance deducted, tax base and warranty deduction. The certificate's figures are the sum of its sections, and VAT is charged once, on the summed tax base. A certificate of one section shows no sections. The PDF and Excel follow the same layout, with a subtotal per section and the certificate's total.
A certificate issued after a release stage was released shows that stage's warranty deduction as withheld and immediately released ("of which released — stage …"); it is included in the amount payable now. With sections, each section shows its own row under its warranty deduction, and the total shows the sum. Certificates issued before the stage was released keep their figures.
A contract correction (negative line) appears on the certificate as a line of its own in the section of the change order that lowered the quantity. A negative section deducts no advance and no warranty deduction; the certificate's totals are the sum of its sections and VAT is computed once. In the certificate's lines a correction's quantity and amount are shown in red with a minus sign, and a negative section says "A negative section (contract corrections): no advance is deducted and no warranty is withheld." A payment application's value, its card and the registers may then be below zero; see Payment applications.
Below are "Invoiced: {invoiced} · not invoiced yet: {remaining}", the Accepted works of the payment application (code, description, unit, quantity, unit price, amount; units are shown as you write them, for example pcs, in your language), the Invoices allocated to it and the History. The certificate also says how it was created, for example "Created on the approval of payment application No. {number} by {name}", who confirmed it and when it was handed over or provided. PDF and Excel download the certificate, in the language you use BuildColab in (Bulgarian or English).
How to confirm certificates
- Open a certificate in status For reconciliation and check its figures.
- Click Confirm (Утвърди). The dialog asks "Confirm {code} with {amount} to invoice? A confirmed certificate is the basis for the invoice." Click Confirm.
To confirm several at once, tick them on the Certificates tab (the header checkbox ticks every certificate on the page you can confirm), then click Confirm ({count}). The dialog lists each certificate's To invoice and Payable now and the total. Each certificate is confirmed on its own: one that cannot be confirmed does not stop the others, and the result shows "Confirmed: {confirmed} · not confirmed: {refused}. The ones not confirmed stay selected." At most 100 certificates are confirmed at once. Your ticks stay when you page, filter or open a certificate; Clear selection clears them.
Grouping reports into certificates
One certificate can cover several approved payment applications of the same contract. Each report keeps the split by main contract and change order that was frozen at its approval; the certificate adds them up in one section for the main contract and one for each change order, each with its own terms, and computes the VAT once. Every step below needs Confirm certificates (contract finance).
- Approved, without a certificate (Одобрени, без сертификат): on the Certificates tab above the register, and in the contract's finance panel. Columns: Payment application (a link to the report's payment path, with "In a draft" for a report in a draft), Contract, Counterparty, Type, Approved on and Amount. Tick reports of one contract (another contract's report cannot be ticked: "Another contract — one certificate covers reports of one contract only") and click New certificate. Your ticks stay when you cancel; Clear selection clears them.
- New certificate (Нов сертификат): step 1 lists the contract's reports waiting for a certificate, with "{n} approved reports of this contract wait for a certificate · the oldest: Report No. {n}, approved {n} days ago". Step 2 previews the certificate: its sections (the main contract and each change order) with their payment days, then the totals; the terms are those at the latest approval and the balances as they stand now. Create for reconciliation (Създай за съгласуване) creates the certificate; Save draft (Запази чернова) saves a Draft instead. At most 50 reports go into one certificate. A report in a draft is not offered: it is certified with its draft.
- Draft (Чернова): a certificate in preparation, in status Draft. Open it from the Drafts filter of the Certificates tab, from the contract's finance panel (Draft certificates), from "In a draft" in the list, or with Open the draft on a report's payment path. While it is open you add reports (Add ({count})) and remove them (Remove) freely and see its preview; it has no number and changes nothing in the register. Send for reconciliation (Изпрати за съгласуване) creates its certificate For reconciliation, with its number and figures; nothing sends a draft by itself. Discard the draft (Откажи черновата), confirmed with Yes, discard the draft, returns its reports to Approved, without a certificate. An empty draft cannot be sent. Without Confirm certificates (contract finance) you can open a draft but not change, send or discard it. A sent or discarded draft is read-only: a sent one shows the status of its certificate and Open the certificate (Отвори сертификата) when opened from the register.
- Merge into one certificate (Обедини в един сертификат): on the Certificates tab, tick two or more interim certificates still For reconciliation of the same contract and click Merge into one certificate. Before anything is merged, the dialog previews the result: the payment applications the merged certificate cites, its sections and figures (the balances as if the merged certificates were already reversed), which certificate keeps its number ("{code} keeps its number as version {n}.") and which are cancelled ("Cancelled: {codes}."). It also says "{codes} are replaced by one certificate «For reconciliation»: {first} keeps its number as a new version, the others are cancelled. The reports and their split by main contract and change order do not change." A certificate already provided or invoiced, or one of another contract, cannot be merged. In the contract's finance panel, Merge the drafts puts every report of two or more drafts into the oldest draft; the preview then shows the draft every report goes into and what it would certify when submitted.
A certificate you create, submit or merge is yours: with the four-eyes principle on, someone else confirms it, and the people who confirm certificates are notified. Voiding a payment application that shares a certificate with others creates a new version of that certificate without it: the certificate must not be invoiced yet (after invoicing, use a credit or debit note), and one handed over or provided needs the confirmation that no invoice was issued and a reason.
Due dates with change orders
When a certificate covers the main contract and one or more change orders, each with its own payment term, choose under Due dates with change orders (Падеж при основен договор и анекси) how its invoice is due:
- A separate due date for the main contract and each change order (Отделен падеж за основния договор и за всеки анекс): one invoice; the part of the main contract and of each change order is due by its own term. This applies when nothing is chosen.
- One common due date — the earliest, — the latest or — the main contract's: one invoice with one due date.
- A separate invoice for the main contract and each change order (Отделна фактура за основния договор и за всеки анекс): the subcontractor issues one invoice for the main contract and one for each change order; the certificate shows "Expected invoices: {n}".
There is no contract-level default. You choose it in New certificate, in a Draft, when merging (Keep the current choice keeps the first certificate's choice, or a draft's when only drafts are merged) and in the certificate itself, with Confirm certificates (contract finance). It can be set or changed while the certificate is a draft or For reconciliation; once confirmed it is fixed ("The due-date mode cannot be changed once the certificate is confirmed."). The certificate lists the main contract and each change order with its Payment term ("Payment term: {days} calendar days from the invoice date") and its due date where it is known without an invoice; the PDF and Excel print the choice and each term. A certificate of the main contract only shows nothing of this and is unaffected.
How to mark a difference
If the figures do not match the subcontractor's copy or accounting, click Mark a difference (Отбележи разлика), describe What differs and click Save. The certificate shows "Difference to reconcile". A difference is cleared by a replacement or by accepting the invoice difference. An invoice registered with a difference also sets the flag (see "Billing control" below).
How to replace a certificate
A holder of Confirm certificates can replace an interim certificate while no invoice is allocated to it. Click Replace (Замени), enter the Reason for the replacement, and optionally the Advance deducted and Other deductions: an empty amount is recalculated by the contract terms. Replace by the certificate the contractor provided sets the Warranty deduction from the certificate your payer provided, with its PDF attached; a subcontractor uses it to align its own copy with the payer's. If you replace a payment certificate that was handed over to accounting or provided to the subcontractor, you must confirm that no invoice was issued from it: tick "I confirm that no invoice was issued from this certificate". Replacing a certificate recalculates all its sections and all its payment applications. If the certificate has more than one section, the advance and warranty deductions are calculated per section and cannot be set by hand: the dialog does not offer them and says so; record a contract-ledger adjustment instead. The old certificate becomes Replaced and keeps its figures; the new version starts in For reconciliation and must be confirmed again. Amounts that break the contract's balances are refused. An advance certificate is never replaced by hand: it follows the contract's advance.
How to hand over a certificate to accounting
On a Confirmed certificate click Hand over to accounting (Предай на счетоводството) and confirm. Download the PDF and Excel for the accountants. This needs Contract finance at Edit.
How to provide a certificate to the subcontractor
In the Cost direction, the payer provides a confirmed interim certificate to the subcontractor. Click Provide to the subcontractor (Предостави на подизпълнителя) and confirm. The certificate's PDF is attached to every payment application the certificate covers, where the subcontractor sees it among the report's files; nothing else from your register is shared. A subcontractor on BuildColab is notified ("Certificate of acceptance and payment received", in the app on each payment application and in one e-mail that names all of them). For a self-managed subcontractor nobody is notified: download the PDF and send it yourself. On its payment path this is the button Download the PDF for the subcontractor, and confirming the certificate from the payment path, Approve or Finalize already attaches the PDF. Otherwise confirming a certificate never sends it: providing is always a separate step.
Invoices
The legal invoice is always issued in your accounting software. You register it here with its PDF and data, and allocate it to the certificates it invoices.
How to register an invoice
- On the Invoices tab click Register an invoice (Регистрирай фактура). Or open a confirmed certificate: its section Invoice for this certificate — files on payment application No. {number} lists the files attached to the payment application. Click Register invoice on a PDF (for example the invoice the subcontractor attached), or Enter the invoice by hand; the contract and the certificate are pre-filled.
- Choose the contract, the Kind (Advance invoice, Invoice, Final invoice, Credit note, Debit note), the Invoice number as printed, the Issue date, and optionally Received on and the Tax event date.
- Under Amounts as printed on the invoice enter the tax base, VAT and total, or click Fill in VAT (20%) and the total from the tax base. Once you enter any two of the three, the third is calculated (total = tax base + VAT), to the cent, with the note "Calculated from the other two amounts" under it. It stays editable: change one of the two you entered and it is calculated again; type over it and it is yours, and nothing overwrites it. A field you clear stays empty until you change one of the other two. Negative amounts (a credit note) are calculated the same way. The checks show live: the total equals the tax base plus VAT, VAT is 20% of the tax base within 0.01, the amounts are zero or more (a credit note's zero or less), and the total is not zero.
- Under Allocation to certificates enter the amount for each certificate (Remaining fills what is left to invoice on it). Each certificate takes at most what is still not invoiced on it. An amount left unallocated has no due date until it is allocated. An advance invoice goes to the advance certificate, a works invoice to interim certificates. Under each allocated certificate, Due dates from {code} shows the due dates the invoice will get for the dates you entered (for the main contract and each change order, or the one common due date). For a certificate with A separate invoice for the main contract and each change order, choose under Main contract or change order on {code} what the invoice is for; each choice shows what is Remaining to invoice on it, and an amount above that is refused ("The amount is more than is left to invoice on the main contract or change order"). Left on "Main contract or change order: chosen by the amount", it is picked by the amount.
- Attach the Invoice PDF: Upload or choose a file (Качи или избери файл) uploads it or picks it from the File Manager. Or use a PDF from the payment application. Optionally enter the Issuer and recipient (a UIC entered here must match the contract's party) and a Note.
- Click Register (Регистрирай).
For a credit note, choose the Corrected invoice and tick the allocations of that invoice the credit note reverses. A credit note offsets the corrected invoice's open parts; credit beyond what is open is "Credit not yet applied", and Apply credit applies it to an open part of another invoice on the same contract. A credit note that corrects an invoice is shown as matched to that invoice: its Matching reads Corrects invoice {number}. It is not an unallocated item; only its unapplied credit, if any, remains to apply. A credit note that names no corrected invoice shows Not allocated, because its credit is still to apply. A debit note is an ordinary positive invoice.
You need read access to the PDF in the File Manager. A file on the payment application you cannot open is shown as "A file you cannot open — ask for access in the File Manager".
Billing control and differences
BuildColab compares the invoice's tax base and VAT with the allocated certificates. The Matching (Съпоставяне) column then shows Not allocated, Matches the certificates, Difference or Difference accepted. An invoice from the register's history (entered at the inclusion or by a history amendment) shows Historical (Историческа): it belongs to the historical certificates, whose figures are already in the opening balances, so it is not allocated and needs nothing from you. A difference above the company's Difference threshold at matching (€) marks the invoice Difference and flags its certificates. A received invoice (Cost) with a difference is paid only after a holder of Confirm certificates clicks Accept the difference (Приеми разликата) in the invoice, which also clears the certificates' flag.
Working with a registered invoice
The Invoices tab filters by direction, Overdue, With a difference, PDF missing and Show cancelled; the columns are Invoice, Contract, Project (company page only), Type, Issued, Matching, Total, Outstanding and Overdue. Inside an invoice (direction "Outgoing" or "Incoming") you see the dates, the allocations, the Parts and due dates, the credit notes, the payments and the history. The buttons:
- Open PDF opens the invoice's PDF.
- Edit (Редактирай) changes only the PDF, the date of receipt or the note. The number, the dates and the amounts of a registered invoice do not change: cancel it and register it again.
- Allocate allocates what is not allocated yet; Reverse reverses an allocation after you enter the Reason (the certificate is open for invoicing again).
- Register a payment for this invoice opens the payment dialog for this invoice.
- Cancel the invoice (Анулирай фактурата) reverses its allocations and credit offsets. It is refused while a payment is allocated to the invoice. Cancelling an invoice that was registered by accepting a subcontractor's submission returns that submission to the subcontractor, with your reason, so they can submit it again; the dialog says so.
Parts and due dates
An invoice is split into parts. Each certificate it invoices gets one Current part (Текуща част), due by the certificate's payment term. The warranty deduction is split by the release stages into parts "Warranty deduction — stage {n}", which stay Held until released. An unallocated amount is a part with No due date. The due date is the start event of the contract's terms (the invoice date, receipt of the invoice, confirmation of the certificate or approval of the payment application) plus the payment term in calendar or working days. On a certificate with change orders the parts follow its Due dates with change orders: one current part for the main contract and one for each change order (named "Main contract", "Change order No. {n}"), or one part on the common due date. Each section's part is that section's own payable: its share of the invoice minus its own warranty deduction. To change a current part's due date, click Change under it in Due date, choose the date and give a reason; Use the certificate's due date removes the change. Aging, the overdue alerts and the payment plan use each part's own due date. A warranty deduction's due date is set when it is released.
Invoices submitted by subcontractors
When the payer has provided a certificate, the subcontractor can submit its invoice through BuildColab instead of attaching it by hand. Both sides use the Submitted invoices (Подадени фактури) tab; it has two sides, Submitted to us (Подадени към нас) and Our invoices (Нашите фактури). Submitting, accepting and returning need Contract finance at Edit; nobody needs Confirm certificates for it.
How to submit your invoice (subcontractor)
- Issue the invoice in your accounting software and keep its PDF at hand.
- Open the payment application on which the payer provided the certificate and click Submit invoice (Подай фактура) in its Payment path card, or click it on the Our invoices side, which lists every provided certificate with its payer and status.
- Enter the invoice exactly as you issued it: the Kind, the Invoice number, the Issue date, optionally the Tax event date, the tax base, VAT and total (any two of them calculate the third, as when registering an invoice), and the Due date (as on the invoice). The payer sees the due date you state; its register dates the payment from the contract's terms.
- Attach the Invoice PDF with From the project's files or From the company's files (Upload or choose a file when the contract has no project). On Upload a file the PDF is saved in Финанси по договори / the contract's name: in the project's files when you opened the dialog with From the project's files, in your own company's files with the other two buttons. It then shows under Choose from files; on Choose from files you pick a PDF already there. Optionally write a Note to the payer.
- If the invoice covers several certificates of the same contract, tick each of them under Certificates the invoice covers (Сертификати, които фактурата покрива), in the order the invoice covers them; Move up (Нагоре) changes the order. A certificate that cannot be added says why: "Replaced by a later version", "An invoice on it is awaiting acceptance" or "An invoice on it was accepted".
- Click Submit (Подай). The payer is notified.
You can submit one invoice against several certificates of the same contract: select every certificate the invoice covers, in the order it covers them. Certificates of different contracts cannot share a submission, and a certificate that already has an invoice waiting or accepted cannot be added. The general contractor accepts or returns the submission as one invoice: it is allocated to the certificates in your order, each in full until the invoice runs out, and each certificate's due dates follow its own Due dates with change orders setting. The submission is returned if the invoice does not reach every certificate, or if one of the certificates is invoiced with a separate invoice for the main contract and each change order — submit that certificate on its own. A resubmission keeps the same certificates; to change them, submit again after the return. Such a submission shows "Certificates: {codes}" (Сертификати: …) on both sides, and on Our invoices it appears on each of its certificates.
When the payer invoices a certificate with a separate invoice for the main contract and for each change order, the Our invoices side shows one line under the certificate for each of them: Main contract (Основен договор), Change order No. n (Анекс №n). Submit one invoice for each line with its own Submit invoice button. The dialog is titled "Invoice against certificate {code} v{version} — Change order No. n", covers that certificate alone (no other certificate can be added) and asks you to "Enter the amounts as on the certificate for this main contract / change order." From the Payment path card, choose the line under Main contract / change order (Договор / анекс). Each line has its own status ("Awaiting acceptance", "Accepted", "Returned", "Withdrawn") and is withdrawn, returned and submitted again on its own; a corrected invoice stays on its line. The payer accepts each invoice against that main contract or change order only, and it is due by that one's payment term. The limit of 20 submissions counts per line.
The PDF is copied for the payer when you submit; changing the file in your File Manager later changes nothing that was submitted. While the payer has not answered, you can Withdraw (Оттегли) the invoice and submit another one. A returned invoice shows "Returned by {payer}: {reason}"; open it and click Correct and submit again (Коригирай и подай отново). Only one invoice per certificate can be waiting or accepted at a time (one per main contract and per change order when the certificate is invoiced separately for each), and a certificate takes at most 20 submissions. If the payer replaced the certificate, submit against the newer version. A certificate that covers several payment applications appears once on the Our invoices side, with all its payment application numbers; you submit one invoice for it.
After the payer accepts your invoice, the Our invoices list and the invoice show whether it is "Not paid yet" (Още не е платена), "Partly paid (last on {date})" or "Paid on {date}", as the payer registers its payments. Amounts are never shown.
Your own register is not changed by a submission. If you track the contract yourself, register your outgoing invoice in your own register too.
How to accept or return a submitted invoice (payer)
- On Submitted invoices → Submitted to us, the filter Awaiting acceptance shows the invoices waiting for you. Open one.
- Check it against its PDF (Open PDF). The PDF is copied into your company's File Manager, in a hidden folder, where the Company Owner and the people it is shared with can read it. If you cannot open it, ask the Company Owner to use Share PDF (Сподели PDF) for you.
- Click Accept and register (Приеми и регистрирай) to register the invoice in your invoice register against the certificate, with the submitted PDF. The dialog shows the due dates the invoice will get from your certificate, for its issue date and the day it was submitted; under A separate invoice for the main contract and each change order the main contract or change order is picked by the amount, unless the subcontractor submitted the invoice for the main contract or one change order (see below). The checks of a manual registration apply. For an invoice against several certificates the dialog first shows the Expected allocation (Очаквано разпределение): each certificate with what it has Remaining to invoice and what the invoice is expected to allocate to it, in the subcontractor's order, then each certificate's due dates. It says when accepting will be refused (a certificate not reached by the invoice, or with nothing left to invoice); your register makes the final allocation when you accept. An invoice for the main contract or one change order names it next to the certificate, in the list and in the dialog ("BC-PC-0007 — Change order No. 1"); accepting it shows only that one, with what it has Remaining to invoice, how far the invoice is above or below it, and its due date. If your certificate is no longer invoiced separately for it, the dialog says "The certificate is no longer invoiced separately for this main contract / change order — return the submission." Or click Return (Върни) and write the reason, which the subcontractor sees.
Your certificate is the reference. If the invoice differs from it, accepting still registers the invoice, and the certificate is flagged with a difference to reconcile. The subcontractor is notified of the acceptance or the return; it never sees your register.
Payments
Register only money that has moved: approving or sending a payment order is not a payment.
How to register a payment
- On the Payments tab click Register a payment (Регистрирай плащане), or open an invoice and click Register a payment for this invoice.
- Choose the contract: the direction and the counterparty come from it. If the contract is not known yet, tick The contract is not known yet, choose the direction (Budget: received from the client; Cost: paid to a subcontractor) and enter the counterparty's name: the payment stays "To review" until you choose its contract with Edit.
- Enter the Payment date and the amount, and optionally the bank reference, the accounting reference, Our account (IBAN), the Counterparty's account (IBAN) and a document.
- When you started from an invoice, the dialog also offers that invoice's open parts: current parts first, oldest due date first; each amount is at most what is open on the part.
- Click Register.
Later, Allocate (Разпредели) in the payment allocates what is still unallocated: the suggestion fills current parts first, oldest due date first, and Back to the suggestion restores it. Held warranty deductions are not offered, and a received invoice with a difference is paid only after the difference is accepted. The Payments tab filters by direction, Only with an unallocated amount and Show cancelled; an unallocated remainder shows "Unallocated — to review". The Source (Източник) column says where each payment came from: Manual (Ръчно), Bank statement (Банково извлечение) for a payment created by a bank statement import, or At inclusion (При включването) for an opening payment. A payment the inclusion recorded on an advance invoice from before the date of inclusion is in the opening balances: cancelling it or reversing its allocation is refused with "This payment is in the opening balances; correct the advance with an adjustment."
In a payment, Edit changes the references and the contract (only while nothing is allocated); the date and the amount do not change. Reverse on an allocation reverses it, with a reason: the invoice is open again by that amount. Cancel payment (Анулирай плащането) reverses all its allocations with it.
How to import a bank statement
Instead of registering payments one by one, you can import your bank's statement as a CSV file. BuildColab matches each row to the register and proposes what it does; nothing is written until you confirm. Needs Contract finance at Edit.
- On the Payments tab click Import a bank statement (Импорт на банково извлечение), next to Register a payment.
- Click Upload or choose a file (Качи или избери файл). On Upload a file drop the CSV or browse for it: it is saved in the company's File Manager, in the Финанси по договори folder. On Choose from files pick a statement already in the company's File Manager; the preview then runs at once.
- Fill in Our account (IBAN) only if the file does not name the account it is for. If you change it after the preview, a note asks you to preview again, and Import stays disabled until you do.
- Click Preview (Преглед). The preview writes nothing.
- Check the rows. Untick a Proposed row to leave it out. Tick a To review or No match row to register it as an unallocated payment that you allocate afterwards.
- Click Import (Импортирай). The footer counts the rows that will be imported. A message reports how many payments were created and how many were confirmed.
What the file needs. A CSV, TXT or TSV export with a header row, a date column and an amount column (or a debit and a credit column); the separator can be a semicolon, a comma, a vertical bar or a tab. Amounts must be in EUR. A column with the counterparty's account (IBAN), company ID (ЕИК), the payment text and the bank's transaction ID makes the matching better. A file may have at most 2 MB and 5,000 transaction rows, and a payment text at most 4,000 characters; split a larger statement by period.
| Row in the preview (EN / BG) | Meaning | What the import does |
|---|---|---|
| Proposed / Предложен | The row was matched. Either a New payment (Ново плащане) with its allocations to invoices (matched by the certificate code or the invoice number in the payment text, or by counterparty and amount), or Confirms a payment entered by hand (Потвърждава плащане, въведено ръчно). | Creates the payment with the shown allocations, confirmed by the bank, or adds the bank's confirmation to the payment entered by hand. Any amount not allocated stays "To review" on the payment. Untick the row to leave it out. |
| To review / За преглед | The row could not be matched safely. The reason is shown under it, for example: more than one set of open invoices adds up to the amount, the account and the company ID point to different counterparties, or the same bank transaction is in another imported statement. | Nothing, unless you tick it: then it is registered as an unallocated payment, "To review", that you allocate with Allocate. |
| No match / Без съвпадение | No contract, invoice or payment in the register matches the row. | Nothing, unless you tick it (as above). |
| Already imported / Вече импортиран | This bank transaction was imported earlier. | Nothing. Importing the same statement again creates nothing. |
| Unreadable / Нечетим | The row could not be read (for example an unreadable date or amount, a currency other than EUR). The reason is shown as the bank file gave it. | Nothing. |
A payment created by an import shows Bank statement in the Source column, and its detail says "Confirmed by a bank statement." If the register or the file changed between the preview and the import, BuildColab refuses: "The register or the file changed since the preview. Preview the statement again and check the new proposal." Click Preview again (Нов преглед) and import the new proposal. If the file cannot be read at all, the dialog says "The bank statement cannot be read. Check that it is a CSV with a header row, a date and an amount (or debit and credit) column."
Corrections
Holders of Confirm certificates see Correction (Корекция) on payment allocations and a Corrections section in the invoice: reverse a payment allocation, adjust a part (a positive amount settles it, for example a bank fee or a write-off; a negative amount opens it again), reverse an opening entry or reverse a credit offset. Each correction needs a reason and takes an optional document. Corrections add a reversing or adjusting entry; nothing is changed or deleted.
The advance
The advance itself is the contract's Advance field. The financial terms say how it is deducted from the certificates. A payment of an advance invoice makes the advance available for deduction only once it is confirmed:
- Register and allocate the payment to the advance invoice.
- In the payment, click Confirm advance (Потвърди аванса) next to the allocation marked "Advance to confirm", or in the contract's finance panel under Advance payments to confirm click Confirm. That list shows every unconfirmed advance payment of the contract, oldest first, 50 at a time; Show more (Покажи още) reads the next ones.
- The dialog Confirm an advance payment shows the advance invoice, the payment date, the amount allocated and the amount to make available. Opened from Advance payments to confirm, it shows the exact amount the register derives; opened from a payment, an approximate one (≈). The amount is derived from the payment; it is never typed. If it is more than the contract can still make available, the dialog warns that the confirmation will be refused. When a change order has an advance of its own, the dialog also shows Advance of (Аванс по): the advance the payment makes available, which is the one of the advance certificate it was invoiced against. The warning then uses what that advance can still make available, and the confirmation message names it ("Confirmed to the advance of Change order No. 1."). Click Confirm payment.
The advance then becomes available for deduction on the next certificates. Confirmation needs Contract finance at Edit and is never done automatically.
Advance settlement (Уреждане на аванса): if an advance was paid after every interim certificate was invoiced, a holder of Confirm certificates creates an Advance settlement certificate from the contract ledger. It is a negative certificate that deducts the advance, goes through reconciliation and confirmation like any certificate, and is invoiced by a credit note. While an interim certificate can still be replaced, replace it instead.
After an inclusion with history, the historical certificates count as earlier certificates. The first certificate after the inclusion catches up any advance the past certificates deducted below the contract's rate, and an advance settlement certificate can be created as soon as the only interim certificates are the historical ones.
The advance of a change order. A change order signed with financial terms of its own has an advance of its own: what it adds to the contract's advance. It gets its own advance certificate, Advance — Change order No. n, and its advance is deducted only from that change order's section of a certificate. Every other change of the contract (a change order signed without terms of its own, a payment application that changes the contract, a budget re-acceptance, a BoQ subcontract annex) counts in the main contract's advance under the main contract's terms. So does a change order signed before the contract was included in finance: its advance is part of the opening figures. A certificate's preview says for a change order's section where its advance comes from: Advance deducted (from the change order's own advance) or Advance deducted (from the main contract's advance).
Registering the advance. When you sign a contract, a change order with terms of its own or a contract proposal that carries an advance, and the contract is in your finance register, the advance certificate is created at once, and a message offers Register the advance received (Регистрирай получения аванс) on a contract with a client, or Register the advance paid (Регистрирай платения аванс) on a subcontract. The link opens the contract's finance panel. There, and on the payment application's payment path, Step 0 · Advance (Стъпка 0 · Аванс) comes before the certificate steps: one card for the Main contract and one for each change order with an advance of its own (Change order No. n — dd.mm.yyyy), each with its state (Unpaid, Awaiting invoice, Partly paid or Paid), what was paid of the advance and what is outstanding. A holder of Contract finance at Edit clicks the button on a card that is still to be paid and enters the Payment date, the Amount (gross, EUR) (suggested: what is left to invoice on the advance certificate), the Bank reference, a Note and an optional document. Tick With the advance invoice to enter its Invoice number, Issue date, Received date, and the Tax base (EUR) and VAT (EUR) (leave both empty for what is left to invoice on the advance certificate). With the invoice, the payment is allocated to it and the advance is available for deduction at once ("Advance registered: {amount} is available for deduction against {advance}."). Without it, the payment waits for the invoice ("Payment registered. It is awaiting the advance invoice."); the card lists it, and Add the advance invoice (Добави авансовата фактура) registers the invoice later. An advance certificate still For reconciliation takes no invoice: the card says so, Open the certificate (Отвори сертификата) opens it to confirm, and until then the payment is recorded without the invoice. A pool already paid in full, a payment larger than the advance invoice and an advance that has no advance certificate yet are refused with a message that says so.
The contract ledger
The finance panel's Contract ledger (Салда по договора) shows the balances your register keeps: the advance (Advance represented (R), Deducted before inclusion, Made available (paid and confirmed), Deducted, Available for deduction) and the warranty deductions (Accrued, with "Allowed in total {cap}: the main contract's cap plus what change orders with a cap of their own have withheld": each such change order is held to its own cap, so this is the limit the register checks, not a cap written in the contract), with the Latest movements. If the balances break a rule, "Rules that do not hold" lists it. A holder of Confirm certificates corrects a balance with Adjustment (Корекция): choose the balance, a signed amount (negative lowers the balance), a reason and an optional document, and click Record adjustment. An adjustment that would break a rule is refused, and an advance already deducted is never made available again.
Once a change order has an advance of its own, the ledger also shows Advance by main contract and change order (Аванс по основен договор и анекси): one row for the Main contract and one for each such change order, named with its signing date (Change order No. 1 — dd.mm.yyyy), each with its advance represented, made available, deducted, available, Still to deduct and what payments may still make available. The balances above are their sums. Each advance movement says which advance it moves ("advance: Change order No. 1"), and so does each payment under Advance payments to confirm. An adjustment of an advance balance and an advance settlement certificate then ask Advance of (Аванс по): the main contract's advance (the default) or a change order's own, also named with its signing date. The figures they show are that advance's, and a settlement deducts at most that advance's available amount and what it still expects to be deducted. A settlement of a change order's advance is that change order's section. A change order without an advance of its own is refused: "That change order has no advance of its own. Only a change order signed with financial terms of its own has one; choose the main contract's advance instead."
Warranty deductions and their release
Warranty deductions (гаранционни удръжки) are held at payment, on the certified amount excluding VAT, at the rate in the contract's Warranty deductions field. On each invoice they form held parts, one per release stage. The Warranty deductions tab lists them with the filters Held and Released, Due in the next (days) and Show paid ones; the columns are Invoice, Contract, Release stage, State, Due, Amount, Outstanding and Action.
To release one, a holder of Confirm certificates clicks Release (Освободи), enters the date the condition was met (not after today), attaches the document proving the condition when the stage requires one, and clicks Release. The due date is the condition date plus the stage's days; Set another due date overrides it with a reason. The part becomes due on the same invoice: no new invoice, no new certificate.
A warranty deduction withheld after its stage was already released becomes due at once: on the invoice's due date basis plus the stage's days. It cites the stage's release and needs no new approval. In the list it is Released with "Released with its stage" (Освободена с етапа) under it; in the invoice's parts it reads "Released with its stage on {date}" and "Due" while unpaid. It is counted as released, not held, in the stage totals and on the payment path, where the line about held deductions shows only what is still held and says the deduction is partly released.
Main contract and change orders
The main contract and each change order with financial terms of its own hold and release their warranty deductions separately, each by its own release stages, taken from its terms. For example, the main contract releases 50% at handover and 50% after the guarantee period, while change order No. 2 releases 100% at the handover of its own works. Change orders on the main contract's terms, contract changes made through a payment application, budget re-acceptances and subcontract annexes are held and released with the main contract. In the list, a change order's deduction says which one it is under its contract ("Change order No. {n}"). A change order's own terms show their stages as Warranty-deduction release stages — Change order No. {n} (Етапи на освобождаване на гаранционните удръжки — Анекс №{n}).
Narrowed to one contract (Open in register in the contract's finance panel), the tab first shows Warranty-deduction release stages (Етапи на освобождаване на гаранционните удръжки), grouped as Main contract (Основен договор), then each Change order No. {n} (Анекс №{n}), each with "Held: {amount}" and "Released: {amount}". Each stage ("Stage {n}: {condition}") shows its Expected date, what is Held and Released (with the number of parts) and what is still Outstanding. The Contract / change order (Договор / анекс) filter narrows the list below to the main contract or one change order.
To release a whole stage at once, a holder of Confirm certificates clicks Release stage (Освободи етапа). The dialog says "Every held deduction of stage {n} of {name} will be released. Each becomes due on its own invoice. A release is final." Enter the date the condition was met, attach the document when the stage requires one, optionally Set another due date with a reason and a note, and click Release stage. Each held deduction of that stage becomes due on its own invoice, exactly as if released one by one. If nothing is held on the stage any more, the release is refused with "Nothing is held on this stage."
Reports
The Reports (Справки) tab has four reports, each filtered by direction and Contract, with totals per direction and Download xlsx. The project is the page's: the Project filter on the company page, or the project itself on a project page; the contract list then offers only that project's contracts. The workbook is in the language you use BuildColab in (Bulgarian or English). A report is cut at 5,000 rows.
Main contract and change orders. A row with a change order's share has Main contract and change orders ({count}) (Основен договор и анекси) under its contract: it opens a line for the main contract and one for each change order in the report's own columns — in Invoice aging each one's earliest due date and days past due, in Confirmed, not invoiced its To invoice, Invoiced and Still to invoice, in Warranty deductions its Amount and Open. Once a contract has a change order's share, the Contract / change order (Договор / анекс) filter narrows the report from The whole contract (Целият договор) to one part only: Main contract for every contract, or, with a Contract chosen, one of its change orders. The report then shows "Contract / change order: {name}" with Clear (Изчисти), and its rows and totals are that part's share. The filter applies after the 5,000-row cut, so a cut report filtered this way says "Choose a contract to see your choice in full." The Excel export follows the filter and, when a change order has a share, adds sheets with the split by main contract and change order.
| Report (EN / BG) | What it shows |
|---|---|
| Invoice aging / Падежи по фактури | What is still open on invoices, by days past the due date: Not overdue, 1–30 days, 31–60 days, 61–90 days, Over 90 days, No due date. Held warranty deductions are not included. |
| Confirmed, not invoiced / Утвърдено, нефактурирано | Confirmed certificates with an amount still to invoice, and, separately, the certificates awaiting confirmation with the days each has waited. The Payment application column lists every payment application of a certificate, for example "1, 2". |
| Advances / Аванси | Per contract: the advance, what of it was paid, deducted and is still available. A contract with a change order's own advance has Advance: main contract and change orders ({count}) under its name: it opens a table with the Contract / change order (the main contract and each change order signed with terms of its own), its state (No advance / Unpaid / Awaiting invoice / Partly paid / Paid), Advance total, Paid, Still to pay, Deducted, Available, Still to deduct and Open on advance invoices. Changes made through a payment application, a budget re-acceptance or a subcontract annex count in the main contract. The totals stay per contract. The Excel export has a second sheet with the advance by main contract and change order. |
| Warranty deductions / Гаранционни удръжки | Held deductions, and released ones by Upcoming, Due and Overdue until they are paid. |
Financial terms of a contract
A contract's financial terms decide the certificate's figures. They are on the contract panel, in the Financial terms (Финансови условия) section of a draft, a signed contract, a proposal and a change order. The summary shows the advance deduction, the warranty deductions cap, the payment term, the number of release stages and "VAT: standard 20%"; a signed contract also shows its signing date and the advance fixed at signing. While the main contract is a draft, the section shows the expected advance: "Expected advance: {amount} excl. VAT — fixed at signing. Until then it follows the contract value and the advance." (Очакван аванс: {amount} без ДДС — фиксира се при подписване. Дотогава следва стойността на договора и аванса.) It is calculated from the current contract value and advance, and fixed when the contract is signed. A change-order draft has no advance amount before it is signed: "The change order's advance is calculated when it is signed." (Авансът по анекса се изчислява при подписването му.)
A new contract. The contract panel creates the draft only when you click Send to partner (Изпрати към партньор) or Create contract (Създай договор), and the same click sends or signs it. So before that, the Financial terms section shows your company's default financial terms. Click Edit, change them for this contract and click Use these terms (Използвай тези условия); Use the default terms (Използвай условията по подразбиране) drops the change. The terms are saved on the contract when the draft is created, before it is sent or signed. If they cannot be saved, the contract is neither sent nor signed: the panel keeps the draft with its own Financial terms section, where you check them and try again.
The company that drafts the contract sets the terms with Edit while the contract is a draft, has no pending proposal, and the user has Contract finance at Edit. Everyone else sees View. The fields:
| Field (EN / BG) | Rules |
|---|---|
| Deduction of the advance / Приспадане на аванса | No advance, Deducted proportionally (a rate above 0% and at most 100%) or Fixed amount per certificate (€). An advance in percent is a share of the initial or the current contract value. Always deducted only once the advance has been paid. |
| Warranty deductions cap / Таван на гаранционните удръжки | No cap, or a cap on the accrued amount: a share of the initial or current contract value, or a fixed amount (€). |
| Release of warranty deductions / Освобождаване на гаранционните удръжки | Stages with a Share (%), a Condition (required, for example "Act 16 signed"), Days after the event, an Expected date and Document required. The shares must add up to 100%; at most 20 stages. |
| Payment / Плащане | Payment term (days) from 0 to 3650, calendar or working days, Counted from the invoice date, receipt of the invoice, confirmation of the certificate or approval of the payment application; an Accounting object code for the accountants. |
Click Save terms (Запази условията). The other party sees the terms in the proposal. They are locked when the contract is signed and change only with a change order or an update request. The main contract and each change order keep their own terms. A change order starts with the contract's current terms; change them in the change order to give it terms of its own (see "Financial terms in a change order" on the page about change orders). A change order's own terms apply to it only: the main contract's terms do not change, and the main contract's work keeps using them. A change order signed without terms of its own uses the main contract's terms. A draft without terms uses no advance deduction and warranty deductions without a cap. A contract signed without terms gets them entered from the signed document at inclusion.
Finance alerts
Contract finance sends alerts to the notification center (the bell) about money and documents that need attention. A daily check runs every morning; each alert is sent once for the same thing, not every day. All alerts are in the Activity tab, and the notification settings control them under the Contracts (Договори) section.
| Alert | Sent when | Opens |
|---|---|---|
| Payment application no. {n} of {contract} was approved on {date} and is not in a certificate yet | An approved report is still in no certificate 5 working days (by the project's working calendar) after its approval. Sent once per report, only to the people with Confirm certificates (contract finance), also when the report sits in a draft certificate (the alert then ends with "(it is in a draft certificate)"). It is not in the daily e-mail digest: the person responsible for the report gets it in an e-mail of its own (if they cannot confirm certificates, every holder of Confirm certificates does). | The report, on its Include in a certificate step |
| Payment certificate {code} for {contract} has been awaiting confirmation for {n} days | A certificate is "For reconciliation" for more than the days in the setting Certificate awaiting confirmation for more than (days) (default 5). | The certificate, on the Certificates tab |
| Payment certificate {code} for {contract} was confirmed {n} days ago and has no invoice | A confirmed or handed-over certificate has no invoice for more than the days in Confirmed certificate without an invoice for more than (days) (default 10). | The certificate |
| Invoice {number} for {contract} is due on {date} ({amount}) | An open invoice part falls in the Due window (the setting «Due» window (days), default 7). Both directions. | The invoice, on the Invoices tab |
| Invoice {number} for {contract} is overdue since {date} ({amount}) | An open invoice part passes its due date. Both directions. A changed due date alerts again. | The invoice |
| The expected release date of the warranty deduction on invoice {number} for {contract} has been reached ({amount}) | The expected date of a held warranty deduction's release stage has come. | The Warranty deductions tab of that contract |
| The advance of {contract} was lowered after it was invoiced: a credit note of {amount} is owed | A signed change order or another change of the contract lowers an advance that was already invoiced. | The contract's finance panel |
| The new advance of {contract} is below what was already made available or deducted; adjust the register | A signed change order or another change of the contract sets the advance below what was already made available or deducted. The register waits: it applies the change once the payment confirmations are corrected, or when a later change of the contract replaces it. | The contract's finance panel |
| The advance certificate {code} of {contract}, already handed over to accounting, was replaced or cancelled by contract version {n}: check whether an invoice was issued from it | An advance certificate already handed over to accounting was replaced or cancelled by a contract change: check whether an invoice was issued from it. | The certificate |
Who receives finance alerts: the members of your company with the Contract finance permission (View or Edit). When the alert comes from a payment application, its assignee gets the alert marked "you are the responsible person", but only if they also hold Contract finance. External participants (guests) never receive them, and the other party never sees your alerts. A paused contract still alerts.
Daily e-mail digest: each recipient also gets one e-mail a day per company, "Contract finance: N new alerts", listing the new alerts and linking to the Contract finance page. It is in the recipient's profile language (Bulgarian if none) and is sent whatever the notification settings say.
Finance settings and default terms
The Settings tab holds the company-wide settings. Holders of Confirm certificates change them; everyone else sees them read-only. The tab is on the company page only; on a project page the Settings button in the header opens it.
| Setting (EN / BG) | Default | Meaning |
|---|---|---|
| Four-eyes principle / Принцип „четири очи“ | Off | Whoever prepares an inclusion or a replacement cannot approve it themselves; whoever created a certificate cannot confirm it. |
| Certificate awaiting confirmation for more than (days) | 5 | Under Notifications. A certificate "For reconciliation" longer than this sends a finance alert (see Finance alerts). |
| Confirmed certificate without an invoice for more than (days) | 10 | Under Notifications. A confirmed certificate without an invoice for longer than this sends a finance alert. |
| «Due» window (days) / Прозорец „Дължимо“ | 7 | Invoice parts due in the next N days are Due; later ones are Upcoming. A part entering this window sends the "is due" finance alert. |
| Difference threshold at matching (€) | 0 | Above it, a received invoice is marked with a difference and cannot be paid until the difference is accepted. |
Default financial terms (Финансови условия по подразбиране), on the same tab: click Set default terms, fill in the same form as a contract's terms and click Save default terms. Every new draft contract of your company starts from them, including BoQ subcontracts signed on behalf of a self-managed subcontractor; you can change them on each contract. They never change an existing contract. Clear default terms removes them after a confirmation. If the saved defaults are no longer valid, a warning says why, and new drafts start without them until you save a valid set or clear them.
Who can do what
| Action | Contract finance: View | Contract finance: Edit | Confirm certificates |
|---|---|---|---|
| See the page, the panel, the registers and the reports; download certificates and reports | Yes | Yes | — |
| Prepare an inclusion draft | — | Yes | — |
| Mark a difference, hand over, provide a certificate | — | Yes | — |
| Register, allocate, edit and cancel invoices and payments; apply credit; confirm an advance payment | — | Yes | — |
| Import a bank statement | — | Yes | — |
| Receive finance alerts and the daily e-mail digest | Yes | Yes | — |
| Submit, withdraw, accept and return submitted invoices | — | Yes | — |
| Set a draft contract's financial terms | — | Yes | — |
| Confirm certificates (one or in bulk), replace a certificate | — | — | Yes |
| Include a report in a certificate, create a certificate or a draft, add to and remove from a draft, submit or discard a draft, merge certificates | — | — | Yes |
| Approve an inclusion, pause and resume | — | — | Yes |
| Accept an invoice difference, release a warranty deduction | — | — | Yes |
| Corrections, contract-ledger adjustments, advance settlement | — | — | Yes |
| Change the finance settings and the default terms | — | — | Yes |
By default Company owner, Manager and Project supervisor (the project lead) hold both permissions; the Accountant (Счетоводител) role holds Contract finance at Edit without Confirm certificates. The permissions are company-wide: an accountant works on every project of the company without being added to each project. Voiding an external payment application whose certificate was handed over or provided also needs Confirm certificates. External participants (guests) never see contract finance. See Permission reference and Roles.
Attaching a document
Every contract finance dialog that takes a document (the signed contract and the reconciliation file at inclusion, a certificate's reference file, the invoice PDF, a payment's or a correction's document, an adjustment's document, the condition document of a warranty-deduction release, the bank statement and the PDF of a submitted invoice) opens the same window with two tabs. You never leave the dialog.
- Upload a file (Качи файл), the tab it opens on: drag the file onto the window, or click Browse your computer (Изберете от компютъра). A bar shows the progress. The file becomes an ordinary File Manager file and the dialog attaches it at once.
- Choose from files (Избери от файловете): pick a file already in the File Manager, as before.
Where an uploaded file is saved. Saved to (Записва се в) names the folder: in the project's files (the company's files when the contract has no project), the folder Финанси по договори and in it a folder named after the contract. Missing folders are created when you upload; an existing folder of that name is reused, so every document of a contract ends up together. A bank statement goes into Финанси по договори in the company's files. A subcontractor's invoice PDF goes into the files the subcontractor opened: the project's with From the project's files, otherwise their own company's. Click Change folder (Промени папка) to browse the folders and click Save here (Запиши тук) in another one.
Limits. The same as in the File Manager: at most 2 GB per file, and file types the File Manager blocks are refused. Where the dialog needs a type (a PDF for invoices; CSV, TXT or TSV for a bank statement), the tab says so and refuses other files before anything is sent. One file at a time.
Common questions
Why does a credit note show "Corrects invoice …" instead of "Not allocated"?
A credit note never allocates to a certificate. One that names the invoice it corrects is matched against that invoice, so Matching reads Corrects invoice {number} and it is not on your list of items to allocate. If part of its credit is still open, the invoice shows it as "Credit not yet applied": click Apply credit to apply it to another invoice on the same contract. A credit note registered without a Corrected invoice shows Not allocated.
Why does the draft's advance change?
While the main contract is a draft, "Expected advance" is calculated from the current contract value and advance, so it follows every change to the BoQ or the advance. It is fixed when the contract is signed and does not change after that.
Why are a change order's warranty deductions released separately?
A change order with financial terms of its own has its own release stages, so its warranty deductions are held and released apart from the main contract's. Narrow the Warranty deductions tab to the contract: under Warranty-deduction release stages each change order has its own stages and its own Release stage button. A change order on the main contract's terms is released with the main contract.
Why does the inclusion ask about a change order's terms?
The change order was signed before change orders had financial terms of their own, so BuildColab has no terms for it. On the Contract, change orders & terms step, under Change orders, choose Own terms and enter them from the signed change order, or Same as the main contract. Until every such change order has a choice the approval is refused: "Choose terms for every change order without terms." A change order that already has terms takes no choice: "This change order already has terms." A contract change made through a payment application never asks, because it always runs on the main contract's terms.
Why is the inclusion refused because the totals from the history differ?
With history, the approval records the balances worked out from the historical pay applications, the invoices with their payments and the advances. The four balances from accounting are the check. If they differ, the approval is refused with "The totals from the history differ from the entered balances. Correct them or explain the difference." On the Reconciliation step, correct the history or the balances, or write the Explanation of the difference, then save the draft. A problem in the history itself is never accepted: "The history has a problem. Correct it in the draft.", with the problem, for example "Advance deducted above the invoiced advance" or "The pay application was not approved before the cutover date".
Where is a file I upload in a finance dialog saved?
In the File Manager, under Финанси по договори / the contract's name, in the project's files (in the company's files without a project). It is an ordinary file there: the File Manager's sharing and permissions apply, and you can move or rename it. The dialog shows the folder under Saved to before you upload; Change folder picks another one.
The upload failed. What now?
The tab says why, keeps your file and offers Try again (Опитай отново) or Choose another file (Избери друг файл). If you may not add files to that folder, it says "You can't upload files to this folder. Choose another folder, or choose an existing file instead." and offers Choose from files; ask whoever manages the File Manager for access to the folder, or use Change folder.
Where do I see the contract finance of one project?
Open the project and choose Contract finance in its sidebar (Execution phase), or on the company page choose the project in the Project filter and click Open the project. The project page shows the same tabs for that project only. You need the company permission Contract finance, not a place in the project team.
Why is there no Settings tab on the project page?
The finance settings apply to every project of the company. Use the Settings button in the header of the project page: it opens the Settings tab of the company page.
Why is there no certificate for an approved payment application?
Approving no longer creates a certificate by itself: the report is included in one at approval, or waits in Approved, without a certificate until someone with Confirm certificates includes it. A certificate is made only on a contract your company has included in finance, for a payment application approved on or after the date of inclusion that the opening balances do not cover. While finance is paused, no certificate is made. Progress reports never get a certificate. The Payment path card on the approved payment application says which case it is: "Include in a certificate", "In a draft certificate", "The contract is not in your finance register" with Include the contract in finance, "Including the contract in finance is not finished", "The contract's finance register is paused" or "This report is in the opening balances".
Why was I reminded about a payment application that is already in a draft?
A draft is not a certificate yet: until it is sent for reconciliation, its reports are still uncertified. So the reminder "…is not in a certificate yet" also comes for a report in a draft, and says "(it is in a draft certificate)". Open the draft (the Drafts filter of the Certificates tab) and click Send for reconciliation. The reminder is sent once per report.
Can one certificate cover several payment applications?
Yes, if they are approved reports of the same contract. Tick them in Approved, without a certificate and click New certificate, collect them in a Draft, or merge their certificates while they are still For reconciliation with Merge into one certificate. Each report keeps its split by main contract and change order; the certificate shows one section for the main contract and one for each change order and names every payment application in its header ("Payment applications No. 3, No. 4").
Why can't I enter the advance deducted when replacing a certificate?
The certificate has more than one section (the main contract and a change order). Each section's advance and warranty deductions are calculated by its own terms, so they cannot be set by hand. Leave them empty, or record a contract-ledger adjustment instead.
What happens to the certificate when I void one of its payment applications?
If the certificate covers only that payment application, it is cancelled. If it also covers others, a new version of it is created without the voided one, and the old version becomes Replaced. Either way it must not be invoiced yet; after invoicing, correct it with a credit or debit note.
Why can't I merge these certificates?
Only interim certificates still For reconciliation of one contract are merged: "Only interim certificates «For reconciliation» can be merged." or "Only certificates of one contract can be merged." A certificate already confirmed, provided to the subcontractor or invoiced is never merged.
I approved a payment application. What do I do next?
Click the Payment path (Път на плащането) button in the report's header (orange when the next step is yours), and look at the message that appears after the approval. Its step tells you what is next: including the report in a certificate, including the contract in finance, confirming or providing the certificate, the invoice or the payment. See "The payment path of a payment application" above.
Who confirms a certificate? I have the Accountant role.
The accountant checks the figures, marks a difference and hands over. Confirming needs Confirm certificates (contract finance), which by default only the project lead (Project supervisor), the Company owner and the Manager hold. A company can grant it to another role.
Why is the Confirm button disabled for me?
The four-eyes principle is on and you created the certificate (or the replacement): "Four-eyes principle: someone other than the person who created the certificate confirms it."
Does the client or the subcontractor see our certificates?
No. The register is private. A subcontractor sees a certificate's PDF only when you click Provide to the subcontractor. In the Budget direction nothing is provided: your client receives only your invoice.
I get "An invoice is already allocated to this certificate. Correct it with a credit or debit note instead."
A certificate is replaced only before an invoice is allocated to it. After invoicing, correct the amount with a credit or debit note, plus a contract-ledger adjustment where needed.
Why can't I pay an incoming invoice?
The invoice differs from its certificates by more than the difference threshold ("The invoice differs from its certificates. Accept the difference before paying it."). A holder of Confirm certificates accepts the difference in the invoice. A held warranty deduction is also not payable until it is released.
Why is the warranty deduction not in Due or Overdue?
Held warranty deductions are not payable yet and are in none of Upcoming, Due and Overdue. Once released, the part gets a due date and joins them until it is paid. A deduction withheld after its stage was already released is released at once, so it is due straight away with the invoice.
Why does a new certificate release part of its warranty deduction at once?
Its release stage was already released before the certificate was issued. The deduction is still withheld and counted (accrued, the limit, the reports), but the row "of which released — stage …" shows it released at once, and Payable now includes it. Stages not yet released, for example the end of the guarantee period, stay held.
The advance was paid but nothing is deducted on the next certificate. Why?
A payment of an advance invoice makes the advance available only after you click Confirm advance on the payment allocation, or Confirm under Advance payments to confirm in the contract's panel.
I registered the advance payment without the invoice. Why is nothing available for deduction?
An advance becomes available for deduction only through a paid advance invoice. The payment waits under Step 0 · Advance with the state Awaiting invoice: click Add the advance invoice next to it and enter the invoice. The advance is then available at once.
Can I change the number or the amount of a registered invoice?
No. Edit changes only the PDF, the date of receipt and the note. Cancel the invoice (only while no payment is allocated to it) and register it again.
As a subcontractor, where do I submit my invoice?
On the payment application where the payer provided the certificate, click Submit invoice in the Payment path card, or use Contract finance → Submitted invoices → Our invoices. The button appears only after the payer has provided the certificate.
Can one invoice cover several certificates?
Yes, certificates of the same contract. In the Submit invoice dialog tick every certificate the invoice covers, in the order it covers them. The payer allocates the invoice in that order, each certificate in full until the invoice runs out. It returns the submission if the invoice does not reach every certificate, or if a certificate is invoiced with a separate invoice for the main contract and each change order: submit that one on its own. A corrected invoice keeps the same certificates; to change them, submit a new invoice after the return.
Why does a certificate on Our invoices show a line for the main contract and each change order?
The payer invoices that certificate with a separate invoice for the main contract and for each change order. Submit one invoice for each line, against that certificate alone; each line has its own status and is accepted, returned or withdrawn on its own. Such a certificate cannot share an invoice with other certificates. If you get "This certificate is invoiced with a separate invoice for the main contract and each change order — choose one.", submit from the line instead.
What happens if I import the same bank statement twice?
Nothing is created twice. Every bank transaction is imported once: on a second import of the same file (or of a later statement that repeats a row) the row shows Already imported, and if nothing is new, the import reports "Nothing new: this statement was already imported."
Why is a bank statement row "To review" instead of matched?
The import never guesses. It proposes a payment only when the counterparty and the invoices are clear: a certificate code or invoice number in the payment text, or exactly one set of the counterparty's open invoices that adds up to the amount. The reason is shown under the row. Tick the row to register it as an unallocated payment, then open the payment and click Allocate.
Why did I get a finance alert, and how do I stop it?
Finance alerts go to everyone in your company with the Contract finance permission (see Finance alerts on this page). Each alert is sent once for the same certificate, invoice due date or release date. To silence them in the app for a project, set the Contracts (Договори) section of that project's notification settings to Counter only or No notifications; the daily e-mail digest is not affected by those settings. The thresholds are on the Settings tab. See Notifications and their settings.
Why does my payment application have a negative line?
A change order lowered a position below the quantity already reported in earlier payment applications. Earlier reports are locked, so the difference comes into the next report as a negative line in that change order's group of This report by main contract and change order (Отчетът по основен договор и анекси), with the new contract quantity and what was reported so far.
Why does a line say "new price from CO 2" although it is in the CO 1 group?
The quantity counts against change order 1, but change order 2 changed the unit price. A change order's new unit price applies to all quantity not reported yet, whether it belongs to the main contract or to a change order; earlier reports keep their prices. The old price shows under the new one as "was {price}".
How is an invoice due when the certificate covers a change order?
By the certificate's Due dates with change orders: a separate due date for the main contract and each change order, each by its own term (the default), one common due date, or a separate invoice for the main contract and each change order. The due dates are prefilled from the certificate when you register or accept the invoice, and each part's due date can still be changed on the invoice with a reason.
Which terms apply to a change order's work?
The change order's own terms, if it was given some before it was signed: its advance deduction, warranty deductions and payment term apply to it only. Otherwise the main contract's terms apply to it too. The contract finance panel shows which under Terms: main contract and change orders.
Why is a change order's advance not deducted on the main contract's work?
A change order signed with financial terms of its own has an advance of its own, and it is deducted only from that change order's section of a certificate. The main contract's advance is deducted from the main contract's section, and from the sections of change orders without terms of their own. The Contract ledger shows each advance under Advance by main contract and change order.
Why do a change order's figures and the main contract's add up exactly to the contract?
Because the main contract takes the rest. A change order shows only what can be traced to it: its sections of the certificates, their invoices and payments, and its own advance. Everything else, including what was entered at inclusion and an invoice not allocated to a certificate, is the main contract's. An invoice that spans the main contract and change orders is split by the certificate sections' tax bases, the same way its due dates were split.
Can BORO do this for me?
Yes. BORO can read the register and propose every write, including registering an invoice from a PDF you send in the chat and importing a bank statement from the File Manager. Every write waits for your approval. See What BORO can do.
Why does a certificate have a line with a negative quantity?
It is a contract correction: a change order lowered a position below the quantity earlier payment applications had reported, and the difference is billed back in the next payment application. It sits in the section of the change order that lowered it. A negative section deducts no advance and no warranty deduction.