01 · Compliance
Audit the RM submission
Walk the Schedule 15.2 and Guidelines 6A-7B catalogue on every run. Record Pass, Fail, N/A and Gap with the evidence beside the result.
For NZ electricity traders
Every RM submission audited. Code compliance you can show.
TOU Router™ audits every Reconciliation Manager submission against Schedule 15.2 and Guidelines 6A-7B. A daily issues register feeds early fixes and Gap close-out. NZX AV reports and network invoice files come out as Outputs of the same run.
How it fits
Start with compliance. Work the issues. Produce the outputs.
The run has a clear order. Audit is the control. Issues are the work to resolve. NZX AV files and network invoice files are outputs of that controlled run.
02 · Issues
Clear the work behind the result
Use the issues register to investigate exceptions, close Gaps and keep the operator trail together before due day or audit handover.
03 · Outputs
Produce the files the run supports
Build NZX AV submissions and network invoice files from the validated portfolio month - outputs of the run, not separate product stories.
01 · Compliance
RM submissions audit on every run - not once a year.
Built-in audit walks the full Schedule 15.2 / Guidelines 6A-7B catalogue against each submission. Results are Pass, Fail, N/A or Gap. Gaps stay honest until they are investigated, evidenced and closed.
✓
Code checks in the run path
The audit sits where the submission is built, so compliance is part of the work rather than an annual reconstruction.
✓
Pass, Fail, N/A and Gap
Proven checks Pass. Failed checks Fail. Out-of-scope work is N/A. Missing evidence stays visible as a Gap.
✓
Audit CSV per run
Export the result for the audit pack, with a repeatable record for the portfolio month.
Annual EA scramble is not a compliance system. TOU Router™ puts the audit into every RM submission run.
02 · Issues
The supporting issues trail - before due day.
The issues register supports the compliance run. It gives operators one place to find the exceptions behind Fail and Gap results, fix what can be fixed, and preserve the decision trail.
Registry alignment
Surface ICP and participant timing problems that can affect the month.
Metering gaps
Find missing or stale half-hour data before it reaches the submission.
Invoice mapping
Review network invoice mappings and exceptions against the portfolio.
Register mapping
Catch meter registers mapped to the wrong price component code.
03 · Outputs
NZX AV and network invoice files - outputs of the run.
Once the portfolio month has been checked and its issues worked, TOU Router™ produces the files the operational process needs.
Output A
NZX (AV) submissions
Build the portfolio AV reports from validated ICP half-hour data for the reconciliation period.
AV-090 · HHRVOLHalf-hour volume submission information for the reconciliation period.
AV-140 · HHRAGGRAggregated volume per ICP - monthly HHR ICP aggregates.
AV-110 · ICPDAYSICP days submission information for the portfolio and consumption period.
AV-140 is aggregated volume per ICP. ICP days are AV-110.
Output B
Network invoice files
Network invoice files from the same controlled portfolio month - mapping and register checks already worked in Issues.
Controlled portfolio monthSame ICP half-hour run that sits behind the audit.
Mapping & register checksWorked in Issues before the file goes out.
Review and exportHand off with the run and issues trail intact.
Network invoices are a run output - compliance and issue resolution come first.
In the app
Open the month. See the finding. Show the evidence.
Operators see the full catalogue result in Outputs, with the status and basis on each finding. The audit CSV, supporting Issues and run outputs stay in the same desktop workspace.
Example portfolio month · RM submissions audit · Schedule 15.2 / Guidelines 6A-7B
Architecture on purpose
Your submission data stays with you.
TOU Router™ is a desktop application for reconciliation and network billing operators. Portfolio files, audit results, NZX AV files and network invoice outputs stay on machines you control.
Trader-controlled data
Submission files, registry extracts and audit evidence stay on your hardware and inside your operational controls.
One operator workspace
Compliance, its supporting Issues and the resulting Outputs stay together for the portfolio month.
Built for the NZ Code
Built by people who work with Registry codes, reconciliation revisions, interposed arrangements and Schedule 15.2.
221b Limited
Walk through an RM audit on a portfolio month.
See the compliance run, the Issues that support it, and the NZX AV and network invoice Outputs it produces. Or ask about a short pilot on one reconciliation period.
Malcolm Souness · Director, 221b Limited
221b.co.nz · NZBN 9429042009948