Solution Design
Solution Design
Section titled “Solution Design”CryptaCount is structured as a three-layer system: a blockchain data ingestion layer, an accounting computation engine, and a reporting and compliance output layer. Each layer is designed to be independently verifiable and auditable.
Three-Layer Design
Section titled “Three-Layer Design”| Layer | Function | Capabilities |
|---|---|---|
| Data Ingestion | Multi-chain blockchain data normalization and sync | 131+ chain coverage, real-time wallet sync, automated transaction parsing, spam detection |
| Accounting Engine | Cost basis calculation, journal generation, fair market value pricing | Eight cost methods, double-entry bookkeeping, five-column rollforward, automated classification |
| Compliance Output | Reporting, tax computation, regulatory mapping | 73-jurisdiction profiles, DAC8/CARF/MiCA alignment, multi-format export |
This separation ensures that raw blockchain data is never directly coupled to reporting logic. The accounting engine operates on normalized, classified transaction data — meaning the same underlying data can produce different outputs depending on the selected cost basis method, reporting currency, or jurisdictional rules without re-fetching or re-processing blockchain data.
Multi-Tenant Design
Section titled “Multi-Tenant Design”The platform implements a full multi-tenant model designed for the workflows of accounting practices, audit firms, and multi-entity businesses.
Account Types
Section titled “Account Types”Four account types define the primary use case and available features:
| Account Type | Primary Use Case | Key Capabilities |
|---|---|---|
| Accountant | Accounting firms managing client crypto books | Multi-client workspaces, journal generation, reporting |
| Auditor | Audit firms verifying client crypto positions | Read-only workspace access, reconciliation tools, audit trail |
| Tax Adviser | Tax advisory practices | Jurisdiction-specific reporting, multi-method comparison |
| Individual | Businesses managing their own crypto accounting | Full workspace control, self-service reporting |
Workspace and Company Hierarchy
Section titled “Workspace and Company Hierarchy”Each account contains one or more workspaces, which serve as the primary organizational unit. Within a workspace, companies represent distinct legal entities — one level of hierarchy. This maps to the real-world structure where an accounting firm (workspace) manages multiple client companies, or a corporate group (workspace) contains several entities.
Workspace-level settings (default cost basis method, reporting currency, reporting period) cascade to all companies within, with company-level overrides available.
Four-Tier Role System
Section titled “Four-Tier Role System”Access control operates through four independent role dimensions:
- Platform Role — System-level access (platform administration)
- Account Type — Determines available features and interface (Accountant, Auditor, Tax Adviser, Individual)
- Workspace Role — Permissions within a workspace (owner, admin, member, viewer)
- Company Role — Permissions within a company (manager, contributor, viewer)
This separation allows fine-grained control. An auditor can be granted read-only access to a specific company within a client’s workspace without gaining access to other companies in the same workspace or any write permissions.
Segregation of Administrative and User Functions
Section titled “Segregation of Administrative and User Functions”The platform maintains separate interfaces for administrative functions versus standard user functions. Administrative operations (user management, system monitoring, data management) are isolated from the accounting workflow. This prevents accidental administrative actions and simplifies the day-to-day experience for accounting professionals.
Consent-Based Workspace Sharing
Section titled “Consent-Based Workspace Sharing”When a business grants workspace access to their auditor or accountant, the sharing model operates on a “no double billing” principle: the business’s existing subscription covers the workspace. The professional (auditor or accountant) accesses the shared workspace through their own account without incurring duplicate charges for the same data.
This mirrors the real-world engagement model where a business pays for their accounting system and grants access to their external accountant or auditor — the accountant doesn’t pay separately for access to each client’s books.
Transparent Plan Enforcement
Section titled “Transparent Plan Enforcement”Subscription plan limits are enforced transparently. When a workspace reaches its plan allocation (wallets, transactions, companies, team members), the platform clearly communicates which limit has been reached and what upgrade resolves it — rather than silently degrading functionality.
Dual-Entity Billing
Section titled “Dual-Entity Billing”The dual-entity corporate structure (CryptaCount Inc. for US, CryptaCount S.à r.l. for EU/ROW) is reflected in the billing system:
- EU customers are billed through the Luxembourg entity with EU VAT handling via Luxembourg’s One-Stop-Shop (OSS) mechanism
- Payments are processed through a PCI-compliant payment platform for both entities
Entity assignment is automatic based on customer jurisdiction and transparent to the end user.