Human NexusASTRALEDGER
System Overview, an executive pre-read.
Prepared by Human Nexus for Navigator Group. Reflects the ASTRALEDGER codebase as provided on 17 June 2026.
Human NexusSystem Overview, an executive pre-read.
Prepared by Human Nexus for Navigator Group. Reflects the ASTRALEDGER codebase as provided on 17 June 2026.
Human NexusSystem Overview, an executive pre-read.
Prepared by Human Nexus for Navigator Group. Reflects the ASTRALEDGER codebase as provided on 17 June 2026.
Human NexusThe operator sets two inputs each cycle. The billing month and the last invoice number. The system does the rest.
Same inputs always produce the same output.
Human NexusBuild, validate, host on an interim basis, and hand over ASTRALEDGER, the monthly invoicing engine for Navigator's four clinical programs.
Human NexusAll four programs built, tested, and confirmed working. ARC, the final outstanding item, was completed and the tool finalised. Validation carried out with Halkin BP. Migration documentation prepared.
Original scope metTable-driven maintenance
Rates, codes, and tables are controlled, so changes are made by editing a table, not code.
Full insurer breadth
NSW Workers Comp, CTP, Worksafe Victoria, WorkCover QLD, TAC, WA, SA, QBE, CGU, and Acenda, each routed correctly.
Payer-specific outputs
QBE TYRO card-claim file, WorkCover QLD with GST in its own columns, ARC chronic injury tab, onboarded and not-yet-onboarded splits.
Direct Xero integration and review step
Web application with on-screen preview before export, plus login and user management.
Engineered for performance and trust
Incremental and cached Salesforce extraction. Deterministic and auditable end to end.
Human NexusEach attended session is a billable event. ASTRALEDGER does the matching, pricing, and formatting from controlled tables and fixed rules, then produces files that import directly into Xero.
Speed
A monthly cycle that took significant manual effort now runs in a controlled sequence.
Accuracy
Pricing and routing come from tables, not memory. Fixed rules where rules apply.
Auditability
Every figure is traceable. The process is repeatable.
Human NexusProgram membership is decided by the Salesforce record type, not by judgement. Acronym expansions are inferred and marked to confirm with the business.
Human NexusSalesforce feeds Step one. Step one produces the period data. Step two builds the invoices. Step three produces the Xero-ready workbook.
Extract from Salesforce
Operator picks the billing month. The system pulls relevant cases, sessions, contacts, clinicians, and accounts, filtered to the program and attended sessions in the month. Prior history is loaded for tiered pricing. Loading is incremental.
Create invoices
Operator enters the last invoice number used. For each session the engine looks up fee code, rate, tax treatment, and accounting code, applies tiered pricing, assigns the next invoice number, and routes the line to the correct payer.
Export
The system writes a single Excel workbook with one tab per insurer or output type, structured to import into Xero. A person reviews the preview before export.
In, billing month
In, last invoice number used
Out, PROGRAM_Navigator_Output_date_time.xlsx
Human NexusVolatile business knowledge lives in tables the business owns and can change. Stable processing logic lives in code.
Salesforce
Source of truth for clinical activity. Read for cases, sessions, contacts, users, and accounts. Read only.
Lookup tables
The lookup pack. Clinicians and provider numbers, insurers and Xero names, GL and cost centre codes, codes and rates. EI and ARC carry extra tables.
Database overlay
PostgreSQL with editable copies of the lookup tables. A built-in Manage Lookups screen for browser editing, menu entry currently turned off.
Operator parameters
Two each cycle. The billing month and the last invoice number used.
Human NexusSession to line item
Speciality and session type select the row in the codes and rates table. The rate is taken from the table, not the Salesforce record.
Tax
Fixed rule. GST on Income multiplies by 1.1. GST Free Income adds none. The 10 percent rate is fixed.
Invoice numbering
Operator enters the last number used. The engine increments by one for each new invoice, in one continuous sequence across all outputs.
Prior-visit tiers
Counts of prior sessions or assessments select the correct fee tier. Same history always produces the same tier.
Payer routing
Lines routed by insurer and scheme. QBE card-funded goes to a TYRO file. WorkCover QLD goes to a Queensland export with its own GST columns.
Xero shape
Final lines arranged in the exact column layout Xero expects, including contact name, invoice number, dates, description, quantity, unit amount, account code, tax type, and tracking.
Human NexusThree sessions become one invoice.
A patient attends three psychology sessions in June under a Navigator Claim, onboarded. Step one pulls the three attended sessions. Step two looks up the psychology fee code and rate, finds tax treatment GST on Income, prices each session at the table rate plus 10 percent GST, assigns the next invoice number, builds a header, and writes one line per session. Step three places the invoice on the correct insurer tab, ready for Xero. No rate or GST typed by hand.
Tiers shift, payers split, one run.
NPPP tier. A patient has had four prior sessions. The engine reads the count and selects the next fee tier. Past the threshold it would select the 6 plus tier.
EI cumulative. Two assessments in prior months and one this month adds to three, selecting the correct QBE month tier. Next month, at four, it steps up.
Payers. A QBE card-funded session routes into the TYRO claim file, grossed up for GST and flagged taxable. A WorkCover Queensland session routes into the Queensland export with amount including GST and the GST amount in their own columns.
Human NexusReviewed on screen before export. Nothing leaves the system automatically.
PROGRAM_Navigator_Output_date_time.xlsxPreview shown for illustration. Actual figures come from controlled tables.
Human NexusPython and Flask, served by Waitress. Data handling with pandas. Salesforce via simple_salesforce. PostgreSQL for tables and users. Excel via openpyxl. Access via Flask-Login.
Web browser
Four program tabs. NPPP, NSP, EI, ARC.
Flask + Waitress, Flask-Login
Salesforce
CRM data, read only
PostgreSQL
Codes, rates, GL, tax, insurers, clinicians, users. Edited via Manage Lookups.
Host filesystem
Working files, previews, export workbooks. Per-program Excel lookup packs.
Human NexusConfirmed across the entire codebase, both extraction and the invoice engine. No machine learning. No predictive model. No randomness. No sampling. No statistical estimation.
Any number can be traced to the table row or rule that produced it. A run can be repeated and will match.
Determinism guarantees the system faithfully applies the tables and rules it is given.
It does not guarantee the tables are correct or that the Salesforce data is clean. Keeping the tables and source data correct is an ongoing business responsibility.
Human NexusSingle source of truth for rates and codes
Codes and rates exist in PostgreSQL and in Excel lookup packs. Previews and EI read from the database. NPPP, NSP, and ARC currently read from Excel. Converge on one source. This is the most important item.
Credentials and configuration
Move all connection strings into Navigator's secrets management and rotate. Set the session secret from the environment.
Access control
Login enforcement is on. Provision real users and retire any default accounts before go-live.
Single-operator design
Working data is held in memory per process. Designed for one operator per monthly cycle. Concurrent users would require a deliberate change.
Rates set in code
A limited set of rates live in code, including SA Police, IPNS, NSW Police pilot, flat fees for not-yet-onboarded patients, and some ARC and EI rates. Changing these requires a code change.
Double-billing control point
Always confirm the correct billing month and the correct last invoice number before running.
Human NexusThe original scope is met in full. Determinism, auditability, and the operational depth Navigator's billing mix requires are in place.
Walk the handover checklist with Navigator's finance, technology, and transformation leads.
Agree the single source of truth for rates and codes, then schedule the credentials and user provisioning cutover.