Controls
Six checks on every update. Then the certificate against the ledger.
Each control is a plain rule that runs every time the ledger updates. When one fires, the screen shows the source line behind it.
Duplicate lines
The same vendor, amount and reference posted more than once across check runs.
Building mismatch
The description on a line names one building while the account it was coded to belongs to another.
Purchase orders paid over amount
Payments against a purchase order exceed its revised value.
Unmapped payments
A payment with no project, building or category, so it cannot appear in any board figure.
Thin contingency
A project whose remaining contingency has fallen under 10%.
Double-billed buildings
One building billed twice within a multi-building pay application.
Certified position
Each contractor’s latest certificate, beside what you actually paid.
Every project page shows the latest AIA G702 on each of its contracts next to the ledger. The comparison is one of four states, and the screen never guesses: an older snapshot without the data says “not available”, never “not certified”.
| State | What it means |
|---|---|
| Current | What the district paid matches the contractor’s latest certificate (earned less retainage), within a dollar. |
| Stale | The district has paid beyond the latest certificate. The screen shows the gap and how many payments were made since. |
| Uncomparable | A certificate exists but cannot be lined up with the ledger, usually because it covers more than one project. |
| None | No certificate has been received, or the one received cannot be attributed to a single project. The screen says which. |
Change-order tie-out
The certificate’s change orders against the ones you approved.
Each certificate states the contractor’s net change by change orders. BondControls ties that figure to the change orders posted for that contractor and flags a mismatch on the pay-applications screen. Retainage is read from the latest certificate per contract, never summed down a column.
Honest limits
What the controls cannot do
They run after payment, not before: BondControls is not in your approval chain. They compare records the district already holds; they do not inspect the work. And “certified on N of M projects” is coverage, not a tie-out, because both sides of that count come from the same workbook.
See it on your program.
Every engagement starts with a conversation with Stoner Advisory Group. Ask for the demonstration, or ask how it would work on your bond.