Payables Documentation
Track upcoming obligations, due dates, status, reminders, and reconciliation without moving money.
Audience: Household members coordinating bills and due dates. · 5-page PDF · v6.26.1
How to read this document
Sections move from purpose → concepts → calculation process → worked examples → edge cases. Formula boxes use plain mathematical notation for clarity; they are conceptual summaries, not API contracts.
- Point lists call out operator-visible behaviour.
- Callouts mark warnings, limitations, or important qualifications.
- Worked examples use round numbers so you can reproduce the arithmetic by hand.
Purpose
Payables organize expected obligations before and after payment. They are reminders and records, not bank instructions.
- Capture amount, payee, due date, and status
- Surface upcoming and overdue items
- Link operational follow-up to the household ledger
Payable lifecycle
- Upcoming
- Due
- Overdue when still open after its due context
- Completed or otherwise resolved
- Archived where supported
Dates, amounts, and ownership
Use the contractual due date, expected currency, clear payee, and responsible member. Update estimates when the bill becomes final.
Completion and expense records
No automatic equivalence
Marking a payable complete does not necessarily prove payment or create an expense. Confirm the actual ledger and external account.
Close a utility bill
- Verify the final amount.
- Record the actual payment as an expense if required.
- Mark the payable resolved.
- Retain reference details.
Reminder state and expense reporting both reflect reality.
Repeated obligations
AccountHouse handles repetition in two distinct ways. Recurring expense patterns do auto-generate ledger rows — on a daily, weekly, monthly, yearly, or custom days-of-week cadence, with a backfill preview shown before the pattern is created. Payable execution stays a confirm-style flow: a payable's schedule surfaces the obligation, and you confirm each execution.
- Recurring expense patterns carry a per-pattern approval mode: Approve posts the generated row, Decline snoozes it for 24 hours, Skip stops it until next month, and Pay now posts immediately.
- A backfill preview shows exactly which rows a new pattern would create before anything is written.
- Payables remain reminders and records — executing one is an explicit confirmation, and recording the actual payment as an expense is a deliberate step.
- See the Recurring Expenses documentation module for full cadence and approval detail.
Reminders
- Delivery depends on notification settings.
- The in-app due date remains authoritative.
- Snoozing an alert does not change the obligation.
Reconciliation
Open payable total
Σ open payable amounts in comparable scope
- Check duplicates.
- Review overdue items.
- Compare paid bills to expenses and statements.
- Correct dates and status.
Privacy, advice limits, and what we do not publish
AccountHouse is a household tracking and organisation tool. It is not a bank, payment processor, tax advisor, or investment advisor. Forecasts, health scores, balances, and alerts are informational.
- Household data is scoped to your household; other families cannot see your ledger.
- Public documentation explains product behaviour and calculation concepts, not proprietary internals.
- Exact scoring weights, anomaly thresholds, cryptography parameters beyond high-level algorithms, and operational detection rules are reserved.
- AccountHouse does not pay bills, verify creditors, or guarantee reminder delivery.
Intellectual property boundary
This document describes what AccountHouse calculates and which inputs matter. It does not disclose source algorithms, secret constants, or implementation details sufficient to reconstruct proprietary systems.