Local Desktop Workflows, with Clear Deployment Boundaries
Desktop workflows are offline-first, while licensing, updates, and hosted/API deployments may use network connectivity.
How TruLedger Handles Processing and Storage
Core Desktop Workflows Run Locally
PDF conversion, invoice generation, receipt generation, and GSTIN structure checks are designed for Windows desktop workflows.
Local Workspace Storage in Desktop Mode
In desktop mode, workspace records are stored locally on the machine.
Browser/API Path Available
If you use a hosted or API deployment, files are processed on server infrastructure for that deployment.
Offline-First for Supported Desktop Tasks
Core desktop tasks are designed to run locally, reducing routine file uploads for everyday workflows.
Licensing and Updates May Connect
Desktop workflows are offline-first, while licensing, updates, and hosted/API deployments may use network connectivity.
Review Outputs Before Operational Use
Users should review exported workbooks and generated documents before filing, accounting entry, or client delivery.
Why Offline Matters for CAs
Desktop-local workflows reduce routine file uploads for core accounting tasks and can be a better fit when you want local handling of day-to-day work.
If you use TruLedger in browser/API deployment mode, files are processed on server infrastructure and should be governed by your server-side policies.
Protect Your Practice
Use TruLedger's Windows desktop workflow when you want local processing for core tasks.