Security & Audit

Validation that can be inspected

Prefiler’s financial conclusions are tested against expected deterministic outcomes. Validation status, test scope, jurisdiction coverage, and known limitations are presented separately so implementation maturity is not overstated.

1. Automated Test Coverage

Prefiler's codebase runs continuous integration tests on every pull request and commit. The test runner compiles and validates all core calculation modules, database transaction layers, and jurisdiction rule-packs.

Passing Test Suite Metrics

• Test files executed: 66 files
• Assertions evaluated: 548 tests
• Failures: 0 (100% stable baseline)
• Environment: Node.js v22 (stateless container)

2. End-to-End Fixture Validation

The core engine is rigorously evaluated against a 20-case adversarial corpus (`canonical-evaluation.test.ts`). This golden corpus injects synthetic corrupted ledger data, mixed currencies, mismatched balances, and out-of-sequence transactions.

Expected Adversarial Behaviors Checked:

• Currency mismatch: Block start if ledger & bank currencies differ.
• Gaps in balances: Detect and highlight ledger discontinuities.
• Out-of-range transactions: Flag lines beyond selected filing periods.

3. Real-Data Ingestion Validation

Every transaction uploaded, whether CSV or parsed PDF text layers, must pass mathematical balance continuity. The engine reconstructs the running balance and asserts that the calculated closing sum matches the statement's reported value with a 0-paise absolute tolerance.

4. Professional Oversight (Human-in-the-Loop)

Prefiler operates as a decision-support verification engine. Calculations, reconciliation states, and risk indicators are indicative outputs. Final review, accounting adjustments, s.44ADA or s.194I tax classifications, and filing determinations require qualified professional CA oversight.

Known Limitations & Scopes

Prefiler's deterministic algorithms are versioned and strictly bounded. Currently:

Text quality: Low-resolution scanned images or skewed camera photos may degrade Vision OCR transcription. Always review coordinates with warning flags.
Write-back: Prefiler operates in a read-only context. It does not write journals back into external Host ledger systems.
Regulatory sync: Rule engines are pinned to specific statutory filing years (e.g., IN-FY-2025-26). Retroactive ruleset updates require explicitly selecting the corresponding pack.

Initiate Technical Evaluation

Contact our technical team to schedule a walkthrough, request API schema specifications, or review private dedicated deployment options.

Schedule Technical Walkthrough Review API Contracts