How is a drafted journal entry reviewed before it posts?

Short answer

A reviewer checks the draft's support, accounts, splits, period, and amounts, then approves, edits, or rejects it. Nothing posts until it is approved.

A drafted journal entry gets the same review whether a staff accountant, a recurring schedule, or an AI agent prepared it. The review confirms the entry is supported, coded correctly, dated in the right period, and ready to post. For drafts an agent prepared, the reviewer also sees how the draft was built, not only the result.

What the reviewer checks on each entry

Check	What the reviewer confirms
Support	The source document is attached and explains the amount
Account mapping	Each line hits the expected GL account and nothing lands in suspense
Splits	Department, class, location, and other dimensions follow policy
Period	The entry date falls in the open period being closed
Amounts	Totals tie to the schedule, register, or invoice, and debits equal credits
Reversal flag	Accruals and estimates are set to reverse in the right period

Red flags that get a closer look

Large swings from prior periods: A recurring entry far off last month's amount usually points to a changed source or an error.
One-off or manual entries: Entries without a recurring pattern carry more judgment and get more scrutiny.
Thin support: A calculation without its source document goes back for documentation before approval.
Edits to history: Corrections are booked as new, traceable entries rather than changes to existing transactions.

The three outcomes

An approved entry moves on to post. An edited entry posts with the reviewer's changes, and the change stays visible in the record. A rejected entry goes back to whoever prepared it, with the reason, and nothing reaches the ledger.

What the approver sees in Ramp Stack

An approver is set on the task: Teammates assign reviewers and approvers to close checklist tasks, so each drafted entry has an approver before the work is finalized.
The draft arrives with its plan and support: The agent first drafts a plan, then prepares the entry with debits, credits, and supporting documentation attached.
Every step is on the record: The Session Audit Log lists each step the agent took in plain English, with the reason and source behind it, so the approver can check how the amount was built instead of recalculating it.
The approver decides: Stack holds its output for human review. The approver can approve the draft as is, edit it, or reject it before anything syncs.
The approved entry syncs: Approval releases the entry to the connected ledger through the native accounting connector, and the entry stays tied to the source data and the work behind it.