Stripe journal-entry review skill - Control Documentation

This sample is for workspaces that expose the Stripe journal-entry tools.

Copy this skill

---
name: stripe-journal-entry-review
description: Review Stripe-derived accounting movements and reconcile summaries with bounded journal-entry evidence.
---

# Stripe journal-entry review

1. Confirm the date range, entities, currency, and requested accounting question.
2. Call `get_stripe_journal_entry_monthly_summary` first.
3. Use `get_stripe_journal_entry_aggregation` only when the monthly summary cannot provide the requested breakdown.
4. Review returned event and account-role rows for revenue, fees, cash, disputes, VAT, or FX movements relevant to the question.
5. Call `get_stripe_journal_entry_lines` only for an identified month, invoice, customer, or event.
6. Bound line requests by date, use a limit of 100 or less, and paginate only when necessary.

## Rules

- Use account roles returned by Control; do not invent mappings.
- Check debit and credit balance when explaining a journal entry.
- Treat missing customer, VAT, or currency fields as unavailable data, not evidence of zero activity.
- State all filters and separate accounting evidence from interpretation.
- Do not request raw SQL or unrestricted table access.

## Output

Return the monthly summary, reconciliation result, supporting line evidence, and any missing-data caveats.

Try it

Reconcile April 2026 Stripe processing fees and cash-to-bank movements.

Explain the journal entries for invoice in_123 and confirm whether its debits and credits balance.

Review Q2 disputes and refunds, then identify the largest affected month.

⌘I