The workflow should close the loop after the obligation reaches zero rather than leaving the bill open for more support.
The key point
A paid status should be backed by reconciliation evidence, an updated remaining balance, and disabled future payment activity.
What to do
- Confirm the provider-side result.
- Update the reconciled balance and status.
- Stop further support against the resolved obligation.
What to avoid
What happens next
The useful distinction is between evidence that a bill existed, evidence that the balance is current, and evidence that a payment actually posted. Those are different events. A reliable workflow records the verification method and time, then reconciles the provider-side result before calling an obligation resolved.
How funding can work
Verification is useful only when it supports a real decision. Settlemont is moving toward funding-aware review: program-backed submissions can be prioritized when money is already committed, while public and personal-share bills remain separate paths.
Before you submit or help
The workflow should close the loop after the obligation reaches zero rather than leaving the bill open for more support. A paid status should be backed by reconciliation evidence, an updated remaining balance, and disabled future payment activity. The original bill should stay private; the public page, when approved, is built from a smaller reviewed set of facts. Posting or verification does not guarantee payment, and live payment availability depends on a supported biller or payment rail.
Related resources
Choose the right path
Post a bill privately, browse approved bills, or fund a rule-based program for a group of verified obligations.