01
Scope
Who needs the workflow, what is visible, and what stays out.
Trust boundary · Financials
Financials
The accounting and payments workbench prepares evidence, classifications, export mappings, and payment packets for human review. It does not move money, file taxes, submit 1099s, create live QuickBooks records, or expose internal vendor cost or coordination markup to owners.
Module proof path
Financials connects API boundaries to public proof.
See the workflow, proof, and operating limits in one scan before reviewing the detailed path.
Inspect proof Open demo02
Proof
Screenshot, proof card, or demo path that makes the claim inspectable.
03
Boundary
What requires human review or source evidence.
Why this page is short
This page only publishes the boundary buyers should rely on.
Some areas are intentionally represented by a narrow public boundary instead of a full feature page. That keeps sensitive operations, access rules, and unfinished marketing claims out of the buyer-facing experience.
How we evidence thisEnforced boundary
What the Financials module refuses to do.
The accounting and payments workbench prepares evidence, classifications, export mappings, and payment packets for human review. It does not move money, file taxes, submit 1099s, create live QuickBooks records, or expose internal vendor cost or coordination markup to owners.
WORKBENCH_BOUNDARY · apps/api/src/ironbound_api/modules/financials/router.py:2871
Copied verbatim from apps/api/src/ironbound_api/modules/financials/router.py and regenerated from apps/api/src/ironbound_api/modules. The API returns these same strings in its boundary fields, and a drift check fails the build if this page and the source stop agreeing.
Pilot access
Show the platform through one real operating story.
The best demo is not a feature checklist. It follows a request from owner intake to manager triage, vendor packet, field evidence, reviewed closeout, and owner-safe reporting.
Recommended demo path
- Owner submits a winter maintenance concern.
- Manager reviews urgency, access, and authority.
- Vendor receives only the package-local scope.
- Field evidence becomes a reviewed owner update.
We respond with the recommended demo route, who should attend, and what production access would require.