Methods and limitations

What EstateLedger does, and what it does not claim

Trustworthy estate organization depends as much on clear limits as on convenient entry forms.

Data handling

Guest workspaces use browser storage. Optional accounts use Better Auth email/password authentication and one user-owned workspace in Cloudflare D1. Signing in does not upload an existing guest workspace. Upload, reload, import, export, and deletion are explicit controls. Request bodies are size-bounded, payloads are schema-validated, responses are private and uncacheable, and stale hosted writes are rejected instead of overwriting a newer version.

Accounting

Assets and income are charges. Expenses and distributions are credits. The remaining balance is charges minus credits. Amounts are entered as positive currency values and the sign is supplied by the record type, reducing accidental double negatives. Cents totals are checked against JavaScript's safe integer limit.

Statutory estimates

Only California Probate Code section 10800 and New York SCPA section 2307 are implemented. California's schedule runs through $25 million. Above that ceiling, section 10800 says a reasonable amount is determined by the court; EstateLedger reports the additional amount as undetermined and does not invent a total. Unsupported states return no fee estimate instead of using a guessed or generalized schedule.

Not complete in this build

• There is no bank import, shared multi-user editing, custom domain, payment, or checkout path.
• Email verification and password recovery remain unavailable until a transactional mail provider is configured.
• The printable report is a working document, not a court filing or legal advice.
• Product analytics are not used to collect estate records.