Backup
The accounting proof behind the account balance or proposed action.
Method workpapers
One design system for different accounting methods.
Accountable keeps shared components consistent while letting the method engine decide what evidence, schedule, and recommendation each account needs.
Method
Analysis
Common components
Prepaid schedule
Group by name, confirm service dates, months, GL account, and recognition amount.
Schedule, recommended entry, transactions
Accruals / clearing
Use reconciling-account activity and its context entries to explain what remains open.
Rollforward, journal entry, backup, transactions
AP / AR aging
Review open vendor or customer history without changing the common workpaper component language.
Aging support, exceptions, transactions
Cash & bank
Compare book activity to bank evidence and isolate missing or misclassified entries.
Bank support, book detail, exceptions
Debt / fixed assets
Tie balances to source schedules and surface recognition, interest, depreciation, or support gaps.
Schedule support, rollforward, transactions
Component contract
The UI stays familiar even when the accounting changes.
Reviewers should not have to relearn the product every time they open a new method. The component names, spacing, icons, and status language stay consistent.
Back to productJournal entry
The action the reviewer can accept, edit, refresh, or decline.
Transaction list
The GL rows and related evidence that explain the schedule or recommendation.
Technical details
Expandable diagnostics only when a reviewer needs the deeper calculation trail.