Skip to content
Aletyx Marketplace
en
Talk to us
Finance ops Starts from form submission

Expense report review

Check claims against policy limits, route exceptions to a reviewer and log the result to a sheet.

Forms and human tasks Google Sheets Microsoft Outlook
Browse extensions Talk to us
How it runs

5 steps, from form submission to outcome

    • if exception → Human task
    • if within_policy → Append or update a row
Example recordPress play to follow one record through the flow.

See how “Expense report review” runs inside a governed flow.

0 / 5
  1. Trigger: On form submission. An employee submits an expense claim through a form.
  2. Decision: Check against policy limits. A governed decision checks the claim against policy limits.
  3. Action: Human task. Claims outside policy go to a reviewer.
  4. Action: Append or update a row. The result is logged to a sheet.
  5. Action: Send Outlook mail. The claimant gets the outcome by e-mail.

Step by step

  1. 1
    Trigger On form submission

    An employee submits an expense claim through a form.

  2. 2
    Decision Check against policy limits

    A governed decision checks the claim against policy limits.

  3. 3
    Action Human task

    Claims outside policy go to a reviewer.

  4. 4
    Action Append or update a row

    The result is logged to a sheet.

  5. 5
    Action Send Outlook mail

    The claimant gets the outcome by e-mail.

Governed by design

The decision step is a DMN model: rules your team can read, test and version, instead of logic hidden in code. Runs record the model or flow version that produced the outcome, so answers stay explainable.

Related use cases

Browse all →