Manual Entry
Hub
Approval workflow features for financial data entry — built with Flowable as the workflow engine to enable structured, auditable multi-step approval chains for sensitive financial data in HighRadius's Consolidation product.
The Problem
In financial consolidation, manual journal entries and adjustments are a necessary but high-risk operation. Without a structured approval process, a single erroneous entry can cascade through consolidated financial statements — impacting regulatory reporting and audit outcomes.
HighRadius's Manual Entry Hub needed a robust approval workflow that could enforce multi-level sign-off, maintain a complete audit trail, and integrate cleanly with the existing Spring Boot backend.
The Solution
I implemented the approval workflow system using Flowable — an open-source BPMN workflow engine that integrates with Spring Boot. Each manual entry submission triggers a Flowable process instance that routes through configurable approval stages.
Approvers at each stage can review, approve, reject, or escalate entries. Every state transition is persisted by Flowable's process engine, giving finance teams a complete, tamper-proof audit trail for every entry.
Tech Stack
Details
| Company | HighRadius |
| Role | SDE-2 |
| Type | Feature Build |
| Domain | Fintech · Workflow |
Key Outcome
Structured, auditable approval chains for every manual financial entry — reducing risk and meeting enterprise compliance requirements.
Approval Workflow
Submit
Finance user submits a manual entry with amount, account, period, and supporting notes.
L1 Review
Team lead reviews the entry for accuracy and business justification. Can approve, reject, or request changes.
L2 Approval
Finance manager provides final approval for entries above threshold. Escalation path for high-value adjustments.
Posted
Approved entry is posted to the consolidation ledger. Flowable marks the process instance complete.
Why Flowable?
BPMN Standard
Workflows defined in industry-standard BPMN 2.0 — readable by both engineers and business analysts.
Spring Boot Native
First-class Spring Boot integration — process engine wires directly into the existing service layer.
Persistent State
Every process instance and task state is persisted — survives restarts, provides full audit history.
Dynamic Routing
Approval paths configurable per entry type, amount threshold, and organizational hierarchy.