Identity-directory dormant-account pricing

What is being tested

Were disabled directory identities included when the contract defines a different billable activity boundary? The boundary for this investigation is identity-directory dormant-account pricing. Begin with the disputed transaction or population, then identify which directory status export establishes the observed position and which authentication-count summary supports the comparison. A difference in totals should not replace this question.

Evidence: directory status export

For identity-directory dormant-account pricing, directory status export must be linked to authentication-count summary. Document the observation window, units, inclusion criteria and export version. Identify gaps and corrected events before using the total. Keep raw observations separate from derived quantities so a reviewer can reproduce the population without assuming every logged event is independently chargeable.

Evidence: authentication-count summary

For identity-directory dormant-account pricing, authentication-count summary must be linked to identity pricing definition. Document the observation window, units, inclusion criteria and export version. Identify gaps and corrected events before using the total. Keep raw observations separate from derived quantities so a reviewer can reproduce the population without assuming every logged event is independently chargeable.

Evidence: identity pricing definition

For identity-directory dormant-account pricing, identity pricing definition must be linked to identity invoice. Retain the applicable wording, effective dates and scope of covered transactions. Identify the event or population that controls the calculation. Do not silently replace a contractual definition with a dashboard label, customary practice or the latest published rule.

Evidence: identity invoice

For identity-directory dormant-account pricing, identity invoice must be linked to directory status export. Keep the issued document version and line-level quantity, currency and service period. A header total cannot establish which component is being tested. Retain later corrections as linked versions, so a replacement does not create a second liability.

Reconciliation logic

Reconcile disabled status, measured authentication activity and the contractual counting interval for each pseudonymous identity. Build the comparison at the level identified by directory status export and retain the governing version from authentication-count summary. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.

Exception conditions

A disabled account can have earlier activity in the measured month. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked directory status export, authentication-count summary, identity pricing definition, identity invoice. Document the conflicting input or rule. A plausible operational explanation requires validation, but it should not be discarded to maximize an apparent financial difference.

Human review and outcome

The identity administrator validates event timing and synchronization delay. Return an activity-status bridge instead of cancelling accounts from a snapshot. Keep the reviewer's reason and source references with that disposition. A supported correction should be followed to the revised record or settlement; an accepted explanation can close the question with no adjustment. Missing authority or evidence should remain an open task rather than a confirmed recovery.

Limitations and processing boundary

Do not infer license removability from activity alone or describe a proposed configuration change as confirmed savings. The authoritative spend, license and contract producer is not complete; customer evidence and processing validation are prerequisites to production conclusions. In this scenario, absence of directory status export or authentication-count summary limits whether the comparison can be completed. The review method describes what people should validate, not a promise that AuditRes automatically detects or executes this specific outcome.

AuditRes pathway

Discuss identity-directory dormant-account pricing in the Technology Spend workspace. Review current plans, the shared platform and secure evidence requirements; use the existing contact path to confirm the sources and validation this scope requires.

AuditRes Technology Spend: Available for onboarding. Public previews use synthetic demonstration data; production processing remains gated until applicable customer sources and authoritative processors are connected and validated.

Neighboring financial questions

Technology Spend resource hub · All guides in this evidence collection