Assemble the support behind a royalty return — quantities reconciled from weighbridge to invoice, deductions evidenced, the amendment history — for the named officer who lodges. The fiscal filing, not the tenement clock.
A period-level reconciliation figure can read as clean while a few commodity and sales-type slices carry most of the returned lines. Nestack reports the return rate by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Related-party concentrate sales
7.4%
3.6×
Review
Provisionally priced shipments
5.1%
2.5×
Review
Iron ore under determination
3.8%
1.9×
Watch
Final-priced domestic sales
2.5%
1.2×
Normal
Bar: return-rate lift vs. domestic final-priced baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
Each cycle leaves one more test behind
A cycle closes when the amended return is a regression case. That suite is what the next return lodged is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Return rate rises for one commodity slice.
02Diagnose
The quarter that was lodged on time and re-opened long after the team had moved on is read back until the cause narrows to one.
03Improve
The change goes out with a number, and the returns behind it travel with it.
04Verify
Nothing lodges while one touched return case is still red.
05Learn
It is kept for good, and the deduction rules are amended in the same commit.
Learn → DetectThe return edge. Detection next period starts from a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, return workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Royalty workflow discovery and boundary mapping.
02Weighbridge and sales source assessment.
03Quantity, deduction and lodgement-calendar mapping.
04Record ingestion and reconciliation.
05Pack assembly and source binding.
06Confidence scoring and exception routing.
07Officer review workflow.
08Weighbridge and sales-system integration.
09Quantity and deduction cases.
10Guardrails and lodgement controls.
11Return-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne commodity, one periodProductionProduction source systemsAdvancedMultiple states / entities
Introduced at Pilot
Return support and reconciliation✓✓✓
Officer lodgement approval✓✓✓
Quantity-reconciliation baseline✓✓✓
Introduced at Production
Reporting by commodity—✓✓
Exception workflow in your systems—✓✓
Approved write-back—✓✓
Weighbridge-and-sales integration—✓✓
Introduced at Advanced
Multi-jurisdiction deduction rules——✓
Multi-stage commercial approvals——✓
High shipment volume——✓
Multi-state return controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your commodity list and return periods→Quantity, deduction and calendar rule mappingWeek 1
02Representative prior lodged returns→Record ingestion, reconciliation and the assembly baselineWeek 2
03Your deduction policy and evidence standards→Return-support mapping and automation-boundary definitionWeek 1
04Access to relevant APIs, feeds or exports→Weighbridge and sales-system assessment, then integration setupWeek 2
05Returns you would not want audited→Amendment cases and failure-mode testingWeek 4
06What no lodged return may leave unsupported→Confidence scoring, exception routing, guardrails and lodgement controlsWeek 3
07Named officers to review the return pack→Officer review workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Bands here are measured in weeks of real work, and that measurement is what puts two into week five.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Royalty workflow discovery, rule mapping and the automation boundaryW2Source integration and the reconciliation baselineW3Assembly workflow, confidence logic and lodgement controlsW4Evaluation suite, deduction checks and failure-mode testingW5Sales-system integration, a pilot period and targeted correctionsW6One return period run under the commercial manager, then Agent Care handover
Reading the bandA bar covers only the weeks its own work is named in. The week 5 overlap is real, not padding.
At the end of W6When the return period validates, Agent Care takes the agent on.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Mining AI agent
Build the support behind the return before the period closes.
Show us your despatch records, your deduction basis and who lodges. The commercial manager who presses submit is the person an auditor will ask, years later, what each tonne on that return was drawn from.
