U.S. rollout focus
U.S. Bookkeeping Workflows for Growing Businesses
Run day-to-day bookkeeping with a strong general-ledger core, bank-linked workflows, controlled period close, and modular federal/state support packs.
GAAP-oriented reporting foundation. Designed for phased U.S. coverage by package maturity.
This page describes U.S. rollout focus. It does not claim full compliance in all states and does not replace licensed accountants.
Primary persona: in-house finance teams managing bookkeeping for their own company. Accounting offices can preview the draft page at /solution/accounting-us-office.
Install entry point
Pricing from Silver.
Pilot/internal cohort path is limited to launch-scope states and controlled onboarding windows.
What you get
Proof block · Controlled month-end close
Freeze routine posting while exceptions are reviewed.
Approve adjustments with attribution and checklist status.
Publish close evidence package for advisor follow-up.
Why this is different
Not just bookkeeping screens
Workflow-driven bookkeeping with approvals, handoffs, visible reconciliation, and exception routing across day-to-day finance operations.
Approval-aware bookkeeping workflows
Attach posting controls and review checkpoints before close-critical actions move forward.
Controlled close with visible evidence
Keep close tasks, adjustments, and sign-off history in a traceable evidence trail.
Reconciliation + exception routing
Route unresolved transactions into operator queues instead of hiding them in manual side lists.
Phased federal/state rollout model
Expand by package scope, keeping rollout decisions explicit as coverage grows.
Best fit for
Built for teams that need bookkeeping plus controls
Finance/ops teams with approval checkpoints
Best when your process needs explicit owner sign-off before period-close and payout-sensitive steps.
Businesses needing advisor handoff packets
Useful when internal operators prepare evidence bundles for external accountant review and follow-up.
Teams expanding by phased U.S. rollout
Strong fit for staged federal + state package adoption rather than all-at-once multi-state promises.
Typical operating profile and throughput fit
Most successful launches are finance/ops teams handling roughly 500 to 20,000 transactions per month, with explicit close ownership and advisor handoff expectations.
Teams below 500 monthly transactions can still use this stack when controls matter; teams above 20,000 usually need staged rollout with reconciliation queue tuning and workflow automation.
Qualification and rollout fit
Share your current state and get the recommended next step: demo, pilot checklist, or phased rollout workshop.
Expected onboarding timeline
- Week 1: connect source data, validate chart structure, and define close owners.
- Week 2: configure posting controls, reconciliation queues, and advisor handoff packet defaults.
- Week 3: execute first controlled live run and confirm rollout readiness for next package scope.
Built for U.S. bookkeeping
Tax filings, legal determinations, and final compliance positions should be reviewed by licensed accountants and legal professionals in the relevant jurisdiction.
Proof block · Advisor handoff/export-friendly review
Chart, trial balance, and source-linked journal lines.
Attach reconciliations, adjustments, and notes in one bundle.
Supports licensed accountant review without replacing professional judgment.
Connect bank activity to your books
Import transactions through controlled bank integrations, review matches, route exceptions, and keep reconciliation visible to finance operators.
Proof block · Bank review & reconciliation workflow
Ingest bank feed batches in a controlled queue.
Apply repeatable matching rules to known patterns.
Push unresolved lines to an exception review lane.
Confirm reconciled status with a visible operator trail.
Start with a U.S. base. Expand with federal and state packs.
Choose your state pack
Install U.S. state-specific package
State options and links below are generated from apps/accounting-us-state-*/manifest.json package names.
Supported states from currently available packages: California (CA), Florida (FL), Texas (TX), Wyoming (WY).
Package maturity mapping
Base/Federal + launch-state status map
Runtime state source: rollout status feed v2026-04-06 (updated 2026-04-16).
| Package layer | Package/status key | Current maturity/status | Source |
|---|---|---|---|
| U.S. base | accounting-us-base |
Foundation layer (required for federal/state add-ons) | Package manifest/install metadata |
| Federal add-on | accounting-us-federal |
Phased federal support surface | Package manifest/install metadata |
| State pack | accounting-us-state-ca |
Pilot / in rollout | Runtime rollout status feed |
| State pack | accounting-us-state-wy |
Launch ready (controlled external rollout) | Runtime rollout status feed |
| State pack | accounting-us-state-tx |
Pilot / in rollout | Runtime rollout status feed |
| State pack | accounting-us-state-fl |
Pilot / in rollout | Runtime rollout status feed |
Current rollout visibility
State rollout visibility (runtime status)
Version 2026-04-06 · last updated 2026-04-16
California (CA)
Pilot / in rolloutFoundation available: Yes
Planned next capability areas
- State checklist hardening for close controls
- Expanded reconciliation exception ownership rules
- Additional report/export validation gates
Not yet included
- Broad multi-state equivalence claims
- Automated filing submission workflows
- Complete jurisdiction-wide compliance coverage
Wyoming (WY)
Launch ready (controlled external rollout)Foundation available: Yes
Planned next capability areas
- Quarterly evidence-validator drift replay
- Post-launch operator coverage hardening
- Cross-pack dependency-change monitoring
Not yet included
- Automated state filing submission
- Universal legal/compliance guarantee
- All-entity edge-case coverage
Texas (TX)
Pilot / in rolloutFoundation available: Yes
Planned next capability areas
- State notice workflow UAT closure
- Launch-state evidence packet hardening
- External review gate preparation
Not yet included
- Automated filing submission workflows
- Complete jurisdiction-wide compliance coverage
- Broad multi-state equivalence claims
Florida (FL)
Pilot / in rolloutFoundation available: Yes
Planned next capability areas
- Expanded state checklist hardening
- Launch-state evidence packet hardening
- Controlled external review readiness
Not yet included
- Automated filing submission workflows
- Complete jurisdiction-wide compliance coverage
- Broad multi-state equivalence claims
Rollout status reflects current package maturity for bookkeeping workflow support. It is not a filing/compliance certification.
Proof metrics module (14-day trend target view)
Launch operations proof signals
Metric definitions align with docs/accounting/us-proof-metrics-dashboard-spec-v1-2026-04-06.md.
close_cycle_days_p50
≤ 7.0 days
recon_match_rate
≥ 0.92
recon_exception_aging_p95_hours
≤ 72h
resolver_fallback_rate
≤ 0.20
state_pack_gate_blockers_open
0 for launch review
AccordFlow approvals and e-signature workflows
AccordFlow integrates approvals and signature evidence with accounting workflows.
AccordFlow provides a technical and audit foundation for electronic-signature workflows. Final legal/compliance posture depends on deployment policy, document type, and jurisdiction-specific requirements.
Foundation first. Compliance packs in phases.
Start with reliable U.S. bookkeeping workflows, then expand federal/state support with controlled package rollouts.
Messaging guardrail: no broad multi-state compliance claim is implied by this page.