Construction surety tracking: setup and daily use
Sureties is the register under Finance for bank guarantees in both directions: instruments received from subcontractors and instruments the company's bank has issued to customers. Reading it needs View finance, recording and releasing need Edit and approve finance. A row carries reference, type, project, guarantor, amount, a validity range and a release date. This page covers the fields, the expiry figure and what the release action does once.

Direction, guarantee type and the finance right behind the register
Two directions exist. Received covers what a subcontractor has put up in your favor, given covers what your own bank has issued to a customer. The type is one of performance bond, warranty bond or the builder security under section 650f BGB, and the choice is a fixed list rather than free text, so the register stays sortable and comparable across years and projects.
The project is deliberately optional, because a framework guarantee belongs to a business relationship rather than a single site. The register itself opens with View finance, which means a site manager holding that right can read the exposure without being able to change it. Recording a surety and releasing one both need Edit and approve finance, enforced by the write gate before the controller is reached.
Recording a received or issued surety with reference and validity
The capture form asks for project, direction, type, guarantor, amount, reference and the validity range. The guarantor is the bank or insurer that stands behind the paper and takes up to 150 characters. The amount has to be above zero. The reference is required and takes up to 100 characters; the placeholder shows the shape of a usual bond number, and it is what everybody searches for when the paper has to be found again.
Valid from defaults to today and valid until may stay empty, which records the instrument as open-ended. An end date must not fall before the start date, and the form refuses the combination rather than storing an impossible range. Saving returns to the register with a message naming the reference, and the new row appears inside its direction group.

Reading exposure and the ninety-day expiry figure
Three figures head the register: the sum of open instruments received, the sum of open instruments given, and how many open instruments run out within ninety days. That third figure turns amber the moment it rises above zero and is the reason to open the page at all, because a performance bond has to be extended before it lapses rather than after.
Rows group by direction, received first and given below, and sort inside each group by end of validity, so the paper that expires next is near the top of its block. The status reads open, expires with the date, or released with the date. The status bar adds both exposure sums into one open exposure figure, and the project name in the row opens the job it belongs to.
The release action and what stays visible afterwards
Releasing is a single action on an open row, shown only to somebody holding the finance right. It stamps today as the release date, and it does so inside a locked transaction that first checks the field is still empty. A double submit therefore cannot overwrite a date already recorded, and an instrument that has been released offers no release button at all.
After the release the amount drops out of both exposure sums and out of the expiry count, while the row itself stays where it was, still naming the guarantor, the amount, the validity and now the release date. Nothing is deleted. The register has no edit route and no delete route, so what is recorded stays readable, which is the point of a register that a bank may ask about.

Sureties, projects and the handover date behind a warranty bond
A surety with a project shows the job name as a link into the project file, and the file is where the dates that decide the validity live: the handover date and the warranty phase that follows it. A warranty bond is expected to outlast that period, which is why the register keeps the end date beside the amount rather than in a note.
Instruments received belong to the subcontract they secure, so the guarantor and the reference should match the paper filed with that contract. The company's own bank guarantees run the other way and tie up credit line until the release, which is what the given figure quantifies. Neither figure counts a released instrument, so the two sums answer what is bound today rather than what was ever issued.
A performance bond recorded and a warranty bond released at Cedar Ridge
For the Riverbend Landing Clubhouse job with its contract sum of $1,860,000.00 the customer asks for security of ten percent, and Carolina Surety Group issues the paper in January. Priya Raman records it with direction given, type performance bond, guarantor Carolina Surety Group, the amount of $186,000.00, the reference BOND-2026-6033 and a validity from the eighteenth of January of 2026 to the same day of 2028. The row joins the group of given instruments, the exposure of that direction rises by exactly the bond amount, and the reference is what the bank quotes in every letter about the instrument.
In May the second warranty walk-through at Bridgewater Commons Phase I closes the last defect, the customer hands back the warranty bond BOND-2024-2210 over $224,000.00 issued by Piedmont Bonding Co., and one click releases it; the row stays put with its release date of May eighteenth. Since that day the register reads $1,364,000.00 given and $81,000.00 received as open, an overall exposure of $1,445,000.00, and the expiry figure stands at zero because the earliest open instrument runs until April of 2027. What the bank still holds against the credit line is answered by those two sums.
Construction surety tracking: checks before saving
Recording and releasing both demand the Edit and approve finance right; the write gate refuses the request even when the route is called directly.
The release writes today's date only while the field is still empty, inside a locked transaction, so a double submit cannot overwrite it.
Valid until must fall on or after valid from; an empty end date is stored as an open-ended instrument.
A surety belonging to another company answers 404 rather than a permission message.
Only instruments without a release date count toward the two exposure sums and the expiry figure.
Construction surety tracking: common mistakes
The register has no editing route. A mistyped guarantor, amount or reference cannot be corrected in place, so read direction, amount and reference once more before saving.
An open-ended surety never appears in the expiry figure, because that count needs an end date to work with. Give a bank guarantee its real end date instead of leaving the field blank.
Releasing is final. An instrument released by accident keeps its release date, stays out of both sums and offers no way back on the screen.
The product page describes the same module from the business side, with the decisions it supports and the modules it connects to.
See the product pageFrequently asked questions
Can a surety exist without a project?
Yes. Framework sureties can be recorded without a project.
Can a released surety be released again?
No. The first release date closes the instrument for exposure calculations.
Configuring this part for your own company?
Describe the sequence you follow today and the result you need at the end of it. We can walk through the settings that produce it.