Schedules and webhooks
Schedules and webhooks help LedgerSync stay current without bypassing review. Webhooks trigger imports and normalization, workers build previews, and approvals can still be required before posting.
How auto-sync works
- - Schedules enqueue import, normalization, and preview generation jobs.
- - Webhooks are signature-validated before they are stored and queued.
- - Approvals may still be required depending on client policy and environment flags.
What happens on failure
- - Jobs retry with backoff and attempt limits.
- - Repeated provider 429 responses trigger quota-aware delays instead of infinite retries.
- - Dead-letter or failed jobs appear in the operations workspace for manual review.
Important safety note
Auto-sync can generate previews automatically, but it does not override the sandbox-only posting restrictions or the approval flow.
Related articles
Keep moving through setup with the next most relevant guides.
Approval workflows
Route previews through firm reviewers or client approvers before any sandbox posting step is available.
Understand sync preview
Compare daily summary and per-transaction preview modes, review blocking issues, and understand what will post later.
Security and privacy
Review token encryption, role-based access, audit logs, exports, rate limits, and webhook verification.
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.