Reconcile payouts against your ledger
A reconciliation summary that names the specific rows to look at, not just a total that is off. Built for whoever matches the payment processor to the accounting sheet each week.
Stripe
Google Sheets
4 steps2 integrationsRuns on demand
Payout totals rarely match line by line. What it costs while the work is still done by hand.
- 01Payout totals rarely match line by line.
- 02Fees and refunds are recorded differently in each system.
- 03Finding the one mismatched row takes the whole afternoon.
- Pull payouts3 payouts · $48,210
- Pull ledger412 rows · July sheet
- Match rows409 matched · 3 unmatched
- Write summaryadd_worksheet · 3 rows listed
One workflow, four steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Pull the payout records.Stripe
- 02Pull the corresponding ledger rows.Google Sheets
- 03Match them and isolate what does not reconcile.ModuleX
- 04Write a reconciliation summary with the unmatched rows listed.Google Sheets
The workflow is an editable graph. Reading runs freely; write a reconciliation summary with the unmatched rows listed waits for your opt-in approval until you loosen it. The graph is the receipt.
The mismatch, isolated. Paste this into ModuleX chat, or hit Use this workflow.
reconcile payouts against your ledger: pull the payout records; pull the corresponding ledger rows; match them and isolate what does not reconcile; write a reconciliation summary with the unmatched rows listed. Ask me before anything is sent or written.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.
Reconcile payouts against your ledger. A reconciliation summary that names the specific rows to look at, not just a total that is off.
- stripe · list_charges
- google sheets · add_rows
A reconciliation summary that names the specific rows to look at, not just a total that is off.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
- Categorise card spend without the month-end scrambleA categorised transaction list plus a short list of the entries that genuinely need a human. Built for a finance lead reconciling a month of transactions from memory.
Assemble the month-end close digestA month-end digest in a consistent shape, assembled from the systems of record. Built for a finance team that rebuilds the same summary every month by hand.
Route a purchase request to the right approverA request that reached the right person, with a record of who approved what. Built for an operations manager who is the bottleneck on every small purchase.
About this use case.
It writes a summary; changes to your ledger stay with you.