English
What customer need does this solve?
Cash advances rarely end as cleanly as they start. Employees may spend exactly as planned, spend less and need to return cash, or overspend and need higher approval. If finance staff decide each path manually, the process becomes slow, inconsistent, and difficult to audit.
The customer need is to keep finance control clear without making every settlement a long coordination exercise.
What the solution should solve
The solution should calculate variance and route the case based on transparent rules. In the demo, the Rule Engine screen is opened before any approval action, showing the three rules that govern the Pending Finance Review stage: overspending above 10 million VND escalates to the CEO, underspending asks the requester to return cash, and normal cases are cleared automatically.
Only after the rule configuration is visible does the workflow run. An employee submits a settlement with a 12 million VND overspend, Finance opens the case, and the interface shows the computed route and reason before approval sends it to the CEO. The important part is that branching lives in data, not inside the form or hard-coded approval screen.
Trade-offs and alternatives
The benefit is consistent policy execution and less manual judgment for routine cases. The trade-off is rule ownership: finance and operations must agree on thresholds, priority order, and exception handling.
Alternatives include manual finance review for every settlement, hard-coded workflow branches, or spreadsheet-based reconciliation. Manual review is safe but slow. Hard-coded logic is predictable but expensive to change. Spreadsheets are familiar but weak on approval history and accountability.
Conclusion
Advance settlement is a practical place to prove configurable workflow control. The business gets speed for normal cases, escalation for risk, and a clear audit trail for every branch.