How It Works

AccScript turns national-accounting assumptions into executable production logic.

Instead of keeping balancing decisions only in manual edits, spreadsheet operations, or expert memory, AccScript allows national accountants to express assumptions in a structured script that can be validated, executed, reviewed, modified, and reused.

Production workflow

From official inputs to reproducible outputs.

01

Prepare official inputs

The NSO prepares the required product data, reference files, nomenclature tables, and production inputs used by the national accounts workflow.

02

Write AccScript logic

The national accountant expresses assumptions, references, and balancing rules in a structured script designed around national-accounting language.

03

Validate before execution

The engine checks syntax, structure, references, and accounting constraints before executing the workflow.

04

Execute and generate outputs

AccScript runs the logic, applies the balancing rules, and generates reproducible outputs for review and comparison.

05

Review, compare, and rerun

If an assumption changes, the user modifies the script and reruns the workflow instead of manually rebuilding the whole operation.

Engine overview

A structured execution chain.

The internal engine follows a clear sequence: read the script, structure it, validate it, execute it, and return understandable errors when something needs correction.

Lexer

Reads the raw script and turns it into structured tokens.

Parser

Organizes the tokens into a structured representation of the script.

Validator

Checks whether the script respects AccScript rules and expected national-accounting logic.

Interpreter

Executes the validated logic and produces the required outputs.

Error system

Returns clear error codes, messages, and hints to help the user correct the script.

Scenario testing

Testing a new assumption becomes a low-cost operation.

In a manual workflow, changing an assumption may require repeating many operations. With AccScript, the assumption is changed directly in the script, then the workflow is rerun and the new result can be compared with previous outputs.

Simple logic

// Change assumption
// Re-run script
// Compare output
// Keep full production trace

Expected benefits

Designed to support expert work, not replace it.

Faster testing of assumptions
Clearer production logic
Reduced manual repetition
Improved knowledge transfer
Better review and audit trail
More reproducible national accounts workflows