Running contract reconciliation

A reconciliation run compares what you are actually managing against what your contracts and licences say you agreed to manage, and records the differences as findings. Runs are retained with their history, so you can see whether the position is improving or drifting.

Findings fall into recognisable shapes. Endpoints under agent management with no matching entitlement. Licences consumed beyond what the agreement covers. Services being delivered with no contractual basis. Contracts approaching renewal with no record of delivered value attached to them.

# Trigger a run and read the summary
curl -X POST https://<your-console-host>/api/reconciliation/run \
  -H "Authorization: Bearer $AEGISONE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"client_id":"<client_id>"}'

curl https://<your-console-host>/api/reconciliation/summary?client_id=<client_id> \
  -H "Authorization: Bearer $AEGISONE_TOKEN"

Treat the first run as a data-quality exercise rather than a commercial one. A first reconciliation against contract records that have not been maintained will produce a large number that is mostly wrong, and acting on it will damage a client relationship for no gain. Work through the findings, correct the entitlement data, and re-run. The second number is the one worth discussing.

When you do raise findings with a client, lead with the record rather than the invoice. "These eleven machines came under management in March and are not on the agreement — here is when each one enrolled" is a factual conversation with an obvious resolution. An unexplained adjustment on an invoice is a dispute.

Findings pointing the other way deserve equal attention. Contracted items you are no longer delivering are a service failure, and finding them yourself is considerably better than the client finding them. Raising both directions in the same conversation also establishes that reconciliation is an accuracy exercise rather than a revenue exercise, which is what makes it survivable as a regular practice.

Run reconciliation on a rhythm rather than when margin looks wrong. Monthly or quarterly keeps the corrections small and unremarkable. Annually turns them into events.