BBV compliance checklist (provincies)
This guide is the operator's pre-audit walkthrough for the BBV compliance surface in Shillinq, scoped to Dutch provinces. The seven canonical BBV programmes used by provincies are:
| Code | Programme | Coverage |
|---|---|---|
ruimte | Ruimte | Spatial planning, area development. |
mobiliteit | Mobiliteit | Roads, public transport, mobility infra. |
water | Water | Surface water, drinking water, dykes (shared with waterschappen). |
milieu | Milieu | Air quality, soil, waste, nature. |
cultuur | Cultuur | Cultural heritage, libraries, museums. |
economie | Economie | Economic development, tourism, employment. |
bestuur | Bestuur | Province governance, internal services. |
Two operator surfaces drive compliance — the BBV Compliance Dashboard and the Budget-to-Programme Linker. This checklist walks the operator through the pre-audit sweep.
1. Pre-audit checklist
Work top-to-bottom; the order minimises rework if one of the earlier checks fails.
1.1 All GL lines mapped to a programme
- Open Shillinq → BBV Provincie → Budget Links.
- Set Assignment status = unmapped in the filter bar.
- Confirm the mapping-status badge reads green (less than 10% unmapped). Yellow / red is an audit-finding risk.
- Bulk-link any remaining unmapped expense GL lines via the guided dialog (see the Linker user guide). The audit trail captures every assignment automatically.
1.2 Budget statuses are current
- Open Shillinq → BBV Provincie → BBV Compliance Dashboard.
- Apply Budget status = provisional in the filter bar.
- Every
provisionalbudget should either becomeapprovedbefore the audit, or be explicitly listed as a risk in the management letter (with a board-approval date). - Apply Budget status = amended — every
amendedbudget should cite the council resolution that approved the amendment in itsdescriptionfield.
1.3 No unresolved overspends
- On the dashboard, scroll to the Exceptions block.
- Empty state (
No overspends) — pass; move on. - Non-empty — for each programme in the list, either:
- Re-map a misallocated GL line back to its correct programme via the Linker (the overspend was a misclassification, not a real overrun), or
- Open an amended
Budgetrecord raisingtotalAmount, with the council resolution cited in thedescription. After the refresh interval the programme should drop out of the exceptions list.
1.4 Dashboard accessible to the audit team
- Confirm the audit-team Nextcloud group has read access to the Shillinq app.
- Confirm the active administration's
administrationTypeisprovinciefor those users — the dashboard navigation entry is hidden otherwise (manifestvisibilityPredicate). - Hand the auditor the dashboard URL plus the user guide; no screen-share session is required for a read-only walkthrough.
1.5 Audit-trail accessible
- Open any GL line via the Linker detail view.
- Confirm the OpenRegister audit-trail sidebar lists at least the
most recent assignment with operator, timestamp, before / after
programmaStructure, and source. - If the sidebar is empty for a line you know was edited, the audit-trail plugin is misconfigured — contact your Shillinq administrator before the audit.