All templates

Automated Leapfin Journal Entry Approval Routing

When Leapfin marks journal entries as ready for posting, WebRun reads the entry type, amount, and period, determines the correct approver based on your routing rules, drafts an approval request in Gmail for external or formal sign-off, and pings the reviewer in Slack with a summary. No entry is posted to the GL until the approver confirms.

Runs on WebRun · Strict Lockdown policy
When journal entries are flagged for approval in Leapfin WebRunorchestrates each step
1 Leapfin read journal entries ready for approval
2 Slack ping the assigned approver with entry summary
3 Gmail draft formal approval request for large or external entries
In short

How do I automatically route journal entry approvals to the right reviewer?

WebRun reads Leapfin's journal entry approval queue whenever entries are flagged as ready, matches each entry to the correct approver based on type and amount, pings the reviewer in Slack with a summary, and drafts formal approval emails in Gmail for large entries. No entry posts to the GL until a human approves it.

  • No journal entry posts to the GL without explicit human approval
  • Approvers are notified in Slack the moment an entry is ready for review
  • Large or formal entries get a drafted email approval trail for audit purposes

Built for controllers · revenue accounting managers · audit-prep teams · SaaS finance directors

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens app.leapfin.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Leapfin - read journal entries ready for approval
    leapfin.com
    WebRun in Leapfin: read journal entries ready for approval
    WebRun opens Leapfin to read journal entries ready for approval.
    • Open Leapfin and navigate to the journal entry approval queue
    • Read each entry flagged as ready for posting: entry type, amount, period, and associated revenue schedule
    • Determine the approver tier based on your policy: entries above a defined threshold go to the controller; others go to the senior accountant

    Done when Every ready journal entry is matched to an approver based on type and amount.

  3. 2
    Slack - ping the assigned approver with entry summary
    slack.com
    WebRun in Slack: ping the assigned approver with entry summary
    WebRun opens Slack to ping the assigned approver with entry summary.
    • Ping the assigned approver in Slack with a summary of each pending entry: type, amount, period, and a link to review in Leapfin
    • For batches of entries, post a grouped list rather than individual messages
    • Request the approver confirm or flag for revision before the close deadline

    Done when The assigned approver is notified in Slack for every pending journal entry.

  4. 3
    Gmail - draft formal approval request for large or external entries
    gmail.com
    WebRun in Gmail: draft formal approval request for large or external entries
    WebRun opens Gmail to draft formal approval request for large or external entries.
    • For entries exceeding the large-entry threshold or requiring external sign-off, draft a formal approval request email with the full entry details
    • Leave every email as a draft in Gmail for the controller to review and send if needed
    • Do not send any formal approval request without the controller's explicit review

    Done when Formal approval drafts exist in Gmail for all large or external entries, unsent and ready for controller review.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.leapfin.com
ScheduleRuns automatically on this cadence
When journal entries are flagged for approval in Leapfin
DeliveryHow each run's result reaches you
Approval request · Slack
OutputWhat each run produces - Slack approval pings for the assigned reviewer and Gmail drafts for formal or large-entry approvals, all pending human sign-off before GL posting.
Text
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Does WebRun post journal entries to the GL automatically?

No. WebRun routes the approval request and waits for a human sign-off. Posting the entry to the general ledger is always a manual step performed by the approver in Leapfin.

How does it know which approver to route to?

It applies your approval-tier rules: entry type, amount, and period determine the approver. You configure these thresholds once during setup.

What happens if the approver does not respond before the close deadline?

WebRun re-pings the approver in Slack 24 hours before the deadline and alerts the controller if the entry is still unreviewed.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.