Billing and plans
LedgerSync uses Stripe Billing for its own subscription plans. This is separate from the Stripe accounting-source connector and is enforced on both the UI and API.
What is counted
- - Imported transactions
- - Client workspaces
- - Source connections
- - Accounting destinations
- - Active sync schedules
- - Team members and approval activity where packaging applies
When you approach a limit
- - Soft overage mode allows the action but creates warnings and upgrade prompts.
- - Hard overage mode blocks the action at the API and UI.
- - Usage summaries are scoped to the active organization and billing period.
Billing mode
Billing can be disabled or run in Stripe test mode while you evaluate the app. Customer payment details are handled by Stripe and are not stored directly in LedgerSync.
Related articles
Keep moving through setup with the next most relevant guides.
Getting started with LedgerSync
Connect your accounting destination, connect Shopify or Stripe, import sample data, and generate your first sync preview.
Approval workflows
Route previews through firm reviewers or client approvers before any sandbox posting step is available.
LedgerSync FAQ
Quick answers about setup order, sync preview, sandbox posting, billing mode, reviewer access, and operational safety.
Troubleshooting common setup and sync issues
Resolve OAuth, shop-domain, realm ID, tenant selection, missing mappings, blocked previews, webhook failures, and worker issues.
Need help? Contact support
Support is the best next step when OAuth, imports, mappings, or reviewer access are blocked.