The Review & Approval Flow

From Draft to Posted

Requesting Validation

1. Create the journal entry/vendor bill as normal.
2. Click Request Validation — Quickenerp checks every configured tier's domain and creates a pending Review for each tier this record actually matches.
3. The record cannot be posted until all required reviews are approved.

Reviewing

A reviewer sees pending reviews assigned to them (and notifications, if enabled). They can:

• Approve – moves to the next tier in sequence, or clears for posting if it was the last.
• Reject – sends it back; the requester must address the issue and request validation again.

Auditability

Every review — who approved/rejected, when, and any comments — is logged on the record's chatter, giving a permanent audit trail of who signed off on every entry that required it. This is exactly the kind of evidence an external auditor or the Journal Audit Trail screen (Finance Insights course) looks for.

Best Practices

• Keep thresholds meaningful — requiring approval on every tiny entry trains people to rubber-stamp without really reviewing.
• Make sure a reviewer group always has at least one active member — a tier pointing at an empty/inactive user blocks posting indefinitely.
• Review your tier definitions periodically as thresholds/organisational structure change — a stale rule set is either too strict (bottlenecking normal work) or too loose (no longer catching what it should).