carf-dac8-crypto-asset-reporting

To reconcile CARF and DAC8 XML crypto transaction reports, parse and normalize the exchange-reported XML inputs against your user transaction records to identify discrepancy deltas. The process applies configurable matching tolerances for timestamp, quantity, and fiat value to classify discrepancies and generate audit-ready markdown and JSON outputs.

Yes, you can merge US 1099-DA CSV records with DAC8 XML files using the optional 1099-DA bridge mode. This functionality merges the CSV records with CARF and DAC8 data using configurable matching tolerances to support dual-report crypto tax workflows.

No, CARF and DAC8 crypto tax reconciliation uses a deterministic local-first processing workflow by default, meaning no external database is required. However, you can optionally enable SerenDB persistence by configuring a SERENDB_URL environment variable if you need to store the reconciliation results.

Cross-jurisdiction crypto tax discrepancies are flagged for CPA escalation by detecting jurisdiction and deadline notes within the parsed transaction records. The reconciliation process then specifically flags material and judgment-sensitive items for review in the final structured markdown and JSON reports.

To start reconciling CARF XML files, you need your CARF XML input, an exported user transactions CSV, and you must explicitly acknowledge the required risk disclaimer. This first-run risk disclaimer gating ensures you understand the limitations before generating any audit-ready reconciliation outputs.