Fail-closed accounting workflows: n8n, TypeScript, and a Conta pilot

Description and use

A pilot intercompany balance checker uses n8n orchestration and deterministic TypeScript logic to ensure that reconciliation reports are only produced when data is complete and accurate, clearly indicating data and balance status.

Problem

Accounting reconciliations can finish successfully yet still lack a valid conclusion, leading to misleading reports.

Outcome

The pilot demonstrates deterministic accounting checks, precise numeric handling, and clear failure reporting, but production readiness requires validation against live Conta data and n8n Cloud execution.

Workflow

• Retrieve each company’s account list and initial trial balance
• Retrieve ledger details for every selected account on both sides
• Retrieve both trial balances again
• Validate opening+movement=closing, detail sum=movement, and unchanged totals across retrievals
• Generate Norwegian HTML, CSV, and JSON evidence
• Handle retries with bounded attempts and respect Retry-After
• Produce a report with COMPLETE/BALANCES_AGREE, COMPLETE/DIFFERENCE, or INCOMPLETE status

Evidence

53 deterministic accounting/workflow tests passed.

Source

17 scenarios passed through actual self-hosted n8n 2.39.6 execution on Windows with Node 24.13.1