FINANCE

Sync Resolved Stripe Dispute Outcomes to the Finance Ledger

When a Stripe dispute closes, records whether it was won or lost, reconciles the amount and fees against the order in Postgres.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerStripe dispute closed webhookStripeStripe
  • ActionRead outcome, amount, and fee from StripeStripeStripe
  • ActionUpdate order ledger in PostgresPostgreSQLPostgres
  • LogicBucket as recovered or confirmed loss
  • OutputEmail daily won/lost summary via OutlookOutlook

What it does

This workflow closes the loop after a dispute resolves. It captures the final win or loss, writes the outcome and recovered or forfeited amount to your order ledger, and gives finance a running picture of dispute performance and recovered revenue.

When to use it

Use it when you need accurate books on chargeback losses and recoveries, and want visibility into how your dispute responses are actually performing over time.

How it works

  1. 1A Stripe `charge.dispute.closed` webhook fires when a dispute reaches a final status.
  2. 2The workflow reads the outcome (won or lost), disputed amount, and dispute fee.
  3. 3It updates the matching order in Postgres with the resolution, net financial impact, and close date.
  4. 4A logic step buckets the result into recovered revenue or confirmed loss for reporting.
  5. 5Once per day it sends finance an Outlook summary of the day's closed disputes, win rate, and total recovered.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect StripeCustomers, subscriptions, payments.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect OutlookMail, calendar, contacts.
  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.