YiokAI
ProductsAgentsCompanyContact
YiokAI

B2B software products. Payment cost intelligence for Stripe merchants, and infrastructure for AI agents.

Products

  • All Products
  • Agent Gatekeeper
  • Enterprise Products

Company

  • About
  • Enterprise
  • Contact

Resources

  • Blog
  • Agents
  • LeakGuard Docs
  • Free Stripe Tools

© 2026 YIOKAI, LLC

(717) 905-0395|info@yiok.ai
LeakGuard Docs

LeakGuard Docs

Getting Started

Features

DashboardRefundsDisputesMonthly CloseAlerts & Settings
Billing & PlansTroubleshooting
Back to LeakGuard

LeakGuard Docs

Getting Started

Features

DashboardRefundsDisputesMonthly CloseAlerts & Settings
Billing & PlansTroubleshooting
Back to LeakGuard

Features

Monthly Close

A 3-step guided workflow that helps finance teams review payment totals and source status, explain what changed, and export a close pack with notes and verification limits.

What is Monthly Close?

Monthly Close is a structured workflow for reviewing Stripe payment costs at the end of each month. A close pack contains monthly totals, source details, available driver explanations, and notes. Backend source confirmation does not establish independent reconciliation against Stripe payouts; exports disclose missing verification evidence.

Who uses Monthly Close

Finance teams closing the monthly P&L for payment costs.

Controllers gathering payment cost totals for separate ledger and payout reconciliation.

Accountants documenting payment fee expenses for auditors.

Founders reviewing what changed month-over-month before board reporting.

The 3-Step Close Flow

Pro plan required. Generating and downloading close packs (PDF + CSV) requires Pro or Business. Verify and Explain steps are available on all plans as read-only previews.
01

Review source

Verify

Review the selected month's totals, data readiness and snapshot source. Backend source confirmation identifies where the totals came from; it does not verify them against Stripe payouts:

Gross Volume

Gross payment volume reported in the selected monthly snapshot.

Total Fees

Payment fees reported in the selected monthly snapshot.

Net Revenue

Net after fees, refunds and disputes. This is not a comparison with your Stripe payout amount.

If independent balance reconciliation was not captured, the preview discloses that limitation. CSV reports NOT VERIFIED and PDF states that independent reconciliation is missing. Notes do not change the verification status.

02

Understand

Explain

LeakGuard auto-generates a driver narrative explaining what changed month-over-month:

Which cost driver changed the most (volume mix, refund rate, dispute rate, fee rate).

Whether the change was driven by volume growth or a rate increase.

Top segments contributing to the change (by country, payment method, or product).

Tip: The narrative is rule-based and deterministic — every output can be verified against the underlying data. No AI-generated content.
03

Document

Export

Generate a close pack with monthly totals, source details, verification status and notes:

PDF

Formatted report with summary page, driver explanation, and appendix. Each export is stamped with a UUID, timestamp, and data source metadata.

CSV

Structured data file with all reconciliation fields, daily aggregates, and breakdown rows. Use for spreadsheet workflows or data warehouse imports.

Export history: Pro and Business accounts can re-download past close packs from the export history panel — useful for audits or if the original download was lost.

Close Notes and Verification Limits

Add notes to record context for your own close process. Notes document your observations; they do not adjust the reported totals or establish an independent payout match:

Costs reviewed separately

Record costs you reviewed outside the monthly snapshot. Check their treatment in your ledger and Stripe records separately.

Credits and timing context

Document credits or timing differences you identified in your own review, along with the supporting records.

Independent reconciliation

Complete payout and ledger reconciliation separately. A backend-source confirmation or note does not replace independent evidence.

Last updated March 15, 2026