Public Finance Attestation Playbook 2.3D.2-3

Overview and Context

Public finance is where encoded objective law meets the largest possible audience. Budget decisions affect everyone. Trust requires auditability. The Public Finance Attestation Playbook provides a step-by-step system for publishing financial records in ways that enable verification without requiring institutional trust.

This sidebar operationalizes the four operability conditions defined in (2.3D.2) at the financial governance scale. For the broader enterprise governance framework, see (2.3D.1). For organizational precedent at smaller scale, see (2.3C.3). The alignment between internal integrity and external verification — the core of the honesty innovation — is developed in Arc 1 (2.1.7).

The Practice: Append-Only Ledger for Budget and Spend

Pre-Budget Transparency

Step 1: Publish Budget Assumptions and Framework. Before the budget process begins, publish your revenue forecast, cost drivers, and contingency approach. This is transparency about process. Stakeholders know the rules before decisions are made.

For example: you forecast $10M revenue based on FY2025 actual $9.5M plus 5% growth, supported by identified market assumptions. Your cost structure allocates 60% to personnel, 15% to infrastructure, 10% to services and tools, and 15% to contingency. You specify that the board approves budget allocation above 5% of category, the CFO approves allocation within category, and department heads can reallocate within their department up to 10%. Emergency spending requires CEO plus CFO approval. Contract amendments exceeding 20% variance from original require board approval. You publish this framework on 1 January 2026.

The framework itself is not proprietary. It is the rule set that governs decision-making. Publish it, date it, and hold to it.

Budget Construction with Traceability

Step 2: Publish Detailed Budget with Rationale. The budget is not a number. It is a set of line items with justifications, each traceable to documented reasoning.

For a public health agency, this means showing staff epidemiologists budgeted at $500k against FY2025 actual of $480k — a 4% increase justified by hiring one additional staff member and a 2% salary increase. Testing kits budgeted at $200k against $180k actual — an 11% increase justified by volume increase from population growth and disease prevalence. Equipment lab machinery budgeted at $100k (new in this budget) with itemized cost breakdown. Each line item invites the question: "Why this specific number?" The answer is already published. A stakeholder can ask: "Why 11% increase in testing kits?" The rationale is visible.

Step 3: Publish Exception Approvals. Exceptions to planned budgets are not hidden. They are recorded as they happen, with date, approval authority, rationale, and signature.

An example: on 17 March 2026, unexpected availability of key laboratory equipment at 20% below market rate creates a 30-day purchase window. The CFO and CEO approve a $50k emergency equipment purchase against the $100k annual allocation. They sign and timestamp the decision, record the rationale (opportunity cost of waiting exceeds decision cost), and offset the exception by deferring travel training to Q2. This exception is recorded in an append-only log, not erased from historical budget documents.

Exceptions are not secret. They are recorded with date, approval, rationale, and signature.

Spend Tracking with Real-Time Visibility

Step 4: Publish Spend Against Budget Weekly or Monthly. Spend transparency builds trust. Publish actual expenditures against budget with a clear statement of variance and, where variance exists, explanation.

For example, at March month-end, staff epidemiologists show $125k spent against $500k budgeted (25% on target). Testing kits show $45k spent against $200k budgeted (23%, slightly ahead because disease prevalence was lower than forecast in February but higher in March). Lab machinery shows $150k spent (equipment purchased in month, spend completed). Data analysis shows $45k spent against $175k budgeted (26%, on target). Total $365k spent against $1,025k authorized budget is 36% spend rate.

When actual spend diverges from forecast, publish variance analysis. Testing kits at 23% vs. 25% planned represents favorable variance of 2%, attributable to disease prevalence patterns; YTD average tracks seasonal assumptions; projection remains 25% full-year; no action required. Lab equipment shows timing variance (purchase completed in month, not budget variance); spend line is complete; remainder of budget unaffected. Data analysis shows 26% vs. 25% planned (1% unfavorable), explained by the approved custom outbreak analysis exception; projection 27% of budget YTD, within authorized exception; no corrective action needed.

Variances are not hidden. They are explained. If a variance signals a problem, the explanation says so.

Reconciliation and Verification

Step 5: Monthly Reconciliation Report. At month-end, publish reconciliation: opening budget, exceptions processed in period, current authorized budget, actual spend, expected spend rate for the period, variance from plan, variance explanation, and outlook for full-year spend.

A reconciliation report for March 2026: opening budget 1 January was $1,000k. Exceptions approved in Q1 totaled +$25k (data analysis custom work). Current authorized budget $1,025k. Spent through March $365k (36% of budget). Expected spend rate for Q1 (3 months) is 25% of annual; actual is 36%. Variance +11% favorable. Variance reason: lab equipment purchased in month, explains 100% of variance; without equipment, spend would be 24% on pace. Outlook: if equipment purchase was one-time (expected), remainder of year should track to budget; if spend continues at elevated rate, corrective action may be needed by April.

The CFO attests: "This reconciliation is accurate to my knowledge. Items reconcile to bank statements, purchase orders, and vendor invoices. Exceptions recorded above represent all unbudgeted spends in Q1." The CFO signs with timestamp. Internal audit reviews and records: "Audit review completed 02 April 2026. No discrepancies noted."

The reconciliation is signed. The CFO attests to accuracy. The auditor reviews. The reconciliation is public or available to stakeholders.

Annual Audit and Certification

Step 6: Independent Audit with Published Findings. At year-end, an independent auditor reviews the complete budget, spend, exceptions, and reconciliations.

An audit report for FY2026 covers scope: all budget allocations, spend, exceptions, and financial controls. Opinion: "The financial records accurately represent expenditures. Budget process followed documented procedures. No material errors identified." Exceptions tested: twelve exceptions exceeding $10k were approved in the year. All had documented rationale and proper approval. One exception ($35k equipment purchase) would have benefited from faster review process, but no financial impact. Controls tested: budget authority levels were observed. No expenditures were made without approval. No exceptions were processed without signed authorization. Data consistency between budget tracking and bank records was verified.

Findings are specific: three small variances (<$5k) in month-end reconciliation timing are not material, but process improvement is recommended. The data analysis line item ended the year 18% under budget; re-evaluating the estimate for next year is recommended.

Recommendations are actionable: implement monthly reconciliation sign-off by department heads (currently CFO only); establish quarterly review of budget vs. actuals with leadership team; develop process for fast-track approval of time-sensitive exceptions (equipment purchases, emergency response).

The audit report is signed by lead auditor and audit firm, dated, and public. Stakeholders know whether the budget process was followed and whether concerns exist.

Application: Handling Surprises and Corrections

Honest financial reporting includes honesty about errors.

Scenario: Vendor Overbilling

You discover in May that a vendor has been overbilling for four months. Total overcharge: $15,000. You demand correction.

Transparent handling means publishing a correction notice: Data Systems Inc., contracted for $150k annually for data services, overbilled from January through April 2026. Invoices totaled $155k instead of $150k — an overcharge of $15,000. Root cause: vendor misconfigured billing system and double-charged for the custom analysis line item. You discovered this on 8 May 2026 during vendor invoice reconciliation. The vendor has agreed to a credit of $15,000, applied to the June invoice.

Budget impact: original budget $150k; actual spent before credit $155k; final spend with credit $140k; variance $10k favorable. Budget line is updated to reflect true spend.

Preventive action: implement three-way reconciliation matching purchase order, contract, and invoice; conduct quarterly vendor invoice audit; establish automated alerts for line-item variance exceeding 10%.

You publish this correction notice on 10 May 2026, visible to stakeholders. Impact on stakeholders: none. Credit is applied to following month's payment.

This is honesty. You found an error. You fixed it. Stakeholders know about it.

Scenario: Unbudgeted Necessity

An unexpected opportunity arises: a leading researcher in infectious disease becomes available and wants to join, but requires immediate lab setup. Cost: $75k unbudgeted.

Transparent handling means publishing an exception request: Type — unbudgeted personnel acquisition. Proposal — hire leading researcher; requires immediate lab setup. Cost breakdown: $100k salary for remainder of year, $50k lab equipment and furnishings, $25k one-time setup, total $175k. Justification: researcher brings $500k in grant funding; fills critical expertise gap; available for 30 days only (time-limited opportunity).

Decision required from board to approve unbudgeted spend of $175k.

Present the actual alternatives: approve as exception, offset by deferring lower-priority initiatives (travel training $50k deferred to Q4; contingency reserve reduced $25k); defer hiring to next budget cycle (opportunity lost, grants lost); reduce scope by deferring salary, offering equipment only (less attractive to candidate, expertise gap remains).

Recommendation: approve as exception, offset by deferring travel training ($50k) and reducing contingency reserve ($25k). Net budget impact: +$100k (salary for remainder of year; one-time equipment cost is frontloaded).

Approval is recorded: board votes, decision is documented, timestamp recorded. The exception request is published on 12 April 2026.

This is not hiding the expenditure. It is transparent about the necessity and the tradeoffs.

The Practice: Finance as Infrastructure

An enterprise practicing RO at finance scale operationalizes encoded objective law through these structural elements: published budget frameworks with documented assumptions and decision authority, before decisions are made; detailed budget line items with rationale, so each number is traceable; real-time spend tracking published weekly or monthly, showing actual versus budgeted with variance explanation; an append-only exception log recording all unbudgeted spends with approval, rationale, and signature; monthly reconciliation signed by finance leadership and reviewed by auditors; annual independent audit with external verification that budget process was followed and records are accurate; variance analysis explaining when budget diverges from actual; and correction transparency, so when errors are found, they are disclosed and corrected in the open record.

The practice is not perfect budget management. It is budget management where trust is structural. Stakeholders do not have to trust the CFO's virtue. They can verify the budget themselves. The ledger is open. Exceptions are recorded. Auditors attest to accuracy. Trust flows from transparency, not from faith in people.