FINANCE

Approved reimbursement to ledger payout record

When a reimbursement is approved via webhook, validates the payout details and writes a finalized payable record to your Postgres finance database, then notifies the employee.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerwebhook
Steps4
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerApproval decision posted to webhookHTTP webhook
  • LogicVerify approved and dedupe by expense id
  • ActionInsert finalized payable into Postgres finance databasePostgreSQLPostgres
  • OutputNotify employee in Slack that payout is queuedSlack

What it does

Closes the loop after approval. When an approval decision is submitted from your review tool, this workflow confirms the amount and payee, records a finalized payable in your Postgres finance database for the next payout run, and tells the employee their reimbursement is queued.

When to use it

Use this as the last stage of an expense pipeline, after a receipt has been parsed and approved upstream. It is for teams that settle reimbursements through their own database or accounting export and want a clean, idempotent payable record.

How it works

  1. 1An approval decision posts to the workflow webhook with the expense id, amount, and payee.
  2. 2A logic step verifies the decision is Approved and that no payable already exists for that expense id, preventing duplicates.
  3. 3The workflow inserts a finalized payable row into the Postgres finance database with amount, payee, and a queued status.
  4. 4A confirmation is sent to the employee in Slack noting the reimbursement is scheduled for the next payout.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.