A financial close workspace for reconciliation preparation, revision-aware manual reviews, prerequisite tasks, exceptions and archived close decisions.

Open an entity close file to prepare reference balances and supporting evidence. Each preparation save creates a new task revision and invalidates the affected task and downstream reviews. A separate review dialog displays the amounts, materiality, supporting reference and readiness causes before a named manual decision. Prerequisite tasks must have current approval. Open exceptions block review and can invalidate previously reviewed work. Close only after period end with all current reviews and no open exceptions; the close decision stores a workpaper and evidence snapshot. Reopening retains the archive and requires fresh task reviews. ToolJet Database stores the records. Names are manual responsibility records, not role-enforced independent approval.
Built for Controllers and finance operations teams coordinating manual period-end work across reporting entities.
Move from reference balances to preparation, current-revision review and a recorded period close.
Prioritize due entity close files and inspect book, support, difference and materiality values in their entity currency.
Create a period for an entity with an owner, period end, close due date and scope.
Prepare workpapers, resolve exceptions, review the current revision and archive a close decision. Reopening requires fresh review.
Add reporting entities with a currency and finance contact; preserve linked period records when contacts change.
Open the next due entity period. Read current-review counts, readiness blockers and a numerical reconciliation queue without consolidating different currencies.
Prepare book and support amounts with up to two decimals, materiality, references and notes. Prerequisites and revision-aware reviews make dependencies explicit.
Raise and resolve linked exceptions. A new exception or preparation revision invalidates affected and downstream approvals while retaining prior review evidence.
Close after the period has ended and every workpaper has a current review. Archive evidence at close; reopening requires reassessment and preserves prior decisions.
The pilot uses 2 tables with fictional records. No external database is needed to explore the source app.
| Table | Sample data | What it stores |
|---|---|---|
| Entities | 3 sample entities | Fictional organizations with finance contacts and USD, EUR or GBP reporting context. |
| Periods | 9 sample periods | Five preserved original examples plus four richer operating, regional, holding-company and archived control examples. Live QA records are excluded. |
English desktop pilot. Fictional operational checklist data only. No ledger integration, accounting posting, bank feeds, accounting assurance, automated reconciliation or financial advice. Reviewer names record manual review; independent approval and access separation are not enforced. Evidence references are text, not uploaded files. Reads are limited to the first 1,000 rows per table and writes stop at that cap. Revision guards detect stale concurrent saves within a period; they do not implement enforced preparer/reviewer separation. Historic v1 sign-offs remain visible but do not count as current v2 approvals. Currency labels are context only; no currency conversion or consolidation is performed.
This design is a starting point. Describe the look you want, add your logo and brand colors, or ask for new features in a prompt. Use the starter prompt to build your own version in the ToolJet AI builder, or use a suggested prompt to modify an app you already have. Review and test the result.
Suggested prompts describe changes you can request. Additional features and translations still need to be built and tested.
Choose ToolJet Cloud, or download the application package to import into your self-hosted instance. Unzip the download, import its application JSON, then follow its README to load the fictional sample data.
Explore the sample records in ToolJet Database, then add your records and configure the workflow for your team.
Describe your preferred design, branding, and new features in the AI builder. Test your workflow, then share your app with the people who need it.