Reconcile a partner's records against the agreement you signed, assemble the evidence behind each discrepancy, and surface every configured dispute window with the time left — a named settlement manager decides what is filed.
Ingesting partner statements, usage records and rate schedules from supported settlement, mediation or file sources.
02
Normalising record identity across the two sides, and carrying each line forward with the file it came from.
Reason
03
Matching the partner's records against your own for the same period, route and trunk group.
04
Applying the rates, effective dates and settlement terms configured from that one agreement.
05
Calculating what the agreement says is owed, and showing the arithmetic behind each line.
Decide
06
Assembling the evidence pack for a discrepancy, with the records and versions it rests on.
07
Surfacing each dispute, notice and audit window with the time left before it closes.
Out
08
Retaining the reconciliation, the evidence, the manager's decision and the outcome against the settlement.
09
Executing write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent reconciles and evidences; a named settlement manager decides what is filed, withdrawn or settled, and the carrier stays the party to the agreement.
Example workflow
One settlement period, end to end
AgentHuman
1Partner statement receivedSettlement statement, usage records, or a wholesale-billing extract
2Records matchedUsage detail, route and trunk group, rate schedule and agreement version, each with its source
3Discrepancy proposedAmount, evidence, window and confidence
4Controls appliedAgreement-version checks, bilateral data scope, window arithmetic and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is filed at any of them — the agent is reconciling, and the manager's lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the settlement manager to decide.
Low confidence
Adds a wholesale analyst read first.
Manager approval
The discrepancy is held with its evidence, its window and the confidence.
Approve · Amend · Send to analyst review
Approved — released to file▼
6Settlement systems updatedOnly where write access and approval policy allow it
7Outcome evaluatedDispute outcome, evidence sufficiency, window margin and amounts recovered
Amendments
Every amendment a manager makes is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Filing, withdrawing or settling a dispute claim.
Agreeing a rate or a commercial term with a partner.
Characterising traffic, jurisdiction or usage factors.
Withholding or suspending payment of a billed amount.
Automation boundaryAgent acts unaided
✓Reconcile the partner's records against the agreement on file.
✓Calculate what that agreement says is owed, line by line.
✓Assemble the evidence pack for a discrepancy, with its sources.
✓Surface every configured window with the time left on it.
Any write happens inside the boundaries agreed at implementation, never ahead of approval.
Writing off, waiving or crediting an open claim.
Declaring a partner an access-stimulating carrier.
Using data from outside your own agreements and records.
Changes to agreement, rate or window configuration.
Example output
One disputed line, annotated
Everything the agent proposes is attached to the records it was drawn from.
Reconciliation output · single lineIllustrative example
Partner
Disputed line
Amount claimed
Agreement version
Confidence
Window status
Regional interconnect
Tandem switching billed on transit minutes
$18,400.00
ICA amendment 7
91%
Open — flagged before expiry
As receivedTaken from both carriers' records and the agreement on file — nothing on this side is inferred by the agent.
Records usedPartner statement lineYour own usage recordsRate schedule in force
Why this is disputedThe agreement's rate for that trunk group is not the rate billed.
ActionApproveAmendSend to analyst review
What the score decidesBelow the configured threshold the discrepancy picks up an analyst read before it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every billed lineFrom both carriers' records
03Reconciliation
Match against the agreement
Draw on your own records and the rates, terms and windows configured from that one agreement — never another partner's.
01Approved path
Reconcile, and watch the window
Routine matching across statements and usage records arrives already done.
02Human review
A missed window cannot be reopened
Once a dispute window closes the claim is extinguished, not reduced — so the time left is put in front of the manager.
04Build an evidence trail
The dispute, the records it rests on and the manager who filed it stay on the settlement.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
An aggregate amendment rate is one number covering every agreement at once; the slice view is where a single settlement type shows up carrying most of the rework. Nestack reports the manager-amendment rate by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
International settlement
7.2%
3.7×
Review
Roaming usage records
4.5%
2.3×
Review
Transit and tandem billing
2.7%
1.4×
Watch
Domestic reciprocal compensation
1.8%
0.9×
Normal
Bar: amendment-rate lift vs. the domestic reciprocal-compensation baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
The loop closes on a test, not a memo
The cycle does not end in a post-mortem. It ends in a case the next release has to clear, and that suite is what the next settlement run is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Manager-amendment rate rises in a settlement slice.
02Diagnose
Read the two record sets and the agreement behind them until the cause narrows to one.
03Improve
Each change carries a version and the disputes that forced it.
04Verify
Release waits on the affected cases going green again.
05Learn
The case is kept for good, and the dispute playbook is rewritten.
Learn → DetectThe return edge. The next run is detected against 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, records, reconciliation workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Settlement workflow discovery and boundary definition.
02Record and rate-source assessment.
03Agreement, rate-schedule and dispute-window mapping.
04Record ingestion and normalisation.
05Reconciliation and evidence logic.
06Confidence scoring and window routing.
07Manager approval workflow.
08Settlement-system integration.
09Dispute-window regression cases.
10Guardrails and filing controls.
11Settlement-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 partner, one agreementProductionProduction settlement systemsAdvancedMultiple partners / regimes
Introduced at Pilot
Reconciliation to your agreement✓✓✓
Manager approval✓✓✓
Reconciliation-quality baseline✓✓✓
Introduced at Production
Reporting by partner and route—✓✓
Dispute workflow in your systems—✓✓
Approved write-back—✓✓
Settlement-system integration—✓✓
Introduced at Advanced
Multi-regime settlement rules——✓
Multi-stage wholesale approvals——✓
High settlement volume——✓
Multi-agreement settlement 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 interconnection and roaming agreements→Agreement, rate-schedule and window mappingWeek 1
02Representative settlement periods→Record ingestion, normalisation and the reconciliation baselineWeek 2
03Your dispute process and escalation ladder→Dispute-process mapping and automation-boundary definitionWeek 1
04Access to relevant APIs, feeds or exports→Record and rate-source assessment, then integration setupWeek 2
05Disputes you would not want filed→Window cases and the evaluation suiteWeek 4
06What must reach a manager before a claim is filed→Confidence scoring, window routing, guardrails and approval controlsWeek 3
07Named settlement managers to review claims→Manager approval 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
The bands sit on the weeks the work occupies, which is why the fifth carries two kinds at once.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Settlement workflow discovery, agreement mapping and the automation boundaryW2Record and rate-source integration and the reconciliation baselineW3Reconciliation workflow, confidence logic and approval controlsW4Evaluation suite, window cases and failure-mode testingW5Settlement-system integration, pilot partners and targeted correctionsW6One settlement cycle reconciled under the wholesale desk, then handover
Reading the bandA bar covers the weeks its work is named in, and nothing else. The week 5 overlap is real, not padding.
At the end of W6The cycle closes the validation and Agent Care takes over monitoring.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Telecom AI agent
Build a settlement agent around your wholesale agreements.
A settlement agent is only as accurate as the agreements behind it. You bring the agreements, the rate schedules and the dispute windows; we map the reconciliation workflow and name what the manager keeps.
