1. The community decides
The board reviews the request under its governing documents, budget, policies, and applicable requirements. Authorized people decide whether to approve it.
Payment workflow
How money moves with Bylaw Ledger
A clearer payment record starts before money moves and continues after the outcome is reported.
A connected record
Four roles in one payment path.
2. Bylaw Ledger checks and records
Bylaw Ledger can connect the request, supporting information, recorded decision, and configured requirements in a workflow. It does not select a recipient or move funds by itself.
3. Bridge provides the infrastructure
Bylaw Ledger Pro is designed to integrate with Bridge, a Stripe company, for supported money movement, subject to onboarding and program approval. Bridge provides payment infrastructure; the board and its authorized people retain approval authority.
4. The outcome is reconciled
Bylaw Ledger is designed to record available payment events and compare them with the community record, so an exception can be reviewed when an outcome is missing or inconsistent.
Who holds the funds?
The community’s money stays under community authority.
Bylaw Ledger provides the workflow, record, and configured checks. It does not hold or pool HOA funds, take title to them, custody private keys, independently transmit money, or unilaterally choose a recipient.
The relevant banking or payment partner executes approved payment services within its approved structure. The final account and treasury arrangement depend on the participating community and required provider, legal, security, and operational approvals.
Current scope
What the page describes.
Does Bylaw Ledger act as a bank or custodian?
No. It is software for records, workflows, configured checks, status, and reconciliation context.
Does every record lead to a payment?
No. The record can show a request, decision, missing requirement, or exception without an instruction being executed.