Email platform suppression-list charging

What is being tested

Were suppressed contacts chargeable under the selected email plan's population rule? The boundary for this investigation is email platform suppression-list charging. Begin with the disputed transaction or population, then identify which suppression-list export establishes the observed position and which audience status history supports the comparison. A difference in totals should not replace this question.

Evidence: suppression-list export

For email platform suppression-list charging, suppression-list export must be linked to audience status history. 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: audience status history

For email platform suppression-list charging, audience status history must be linked to contact pricing terms. 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: contact pricing terms

For email platform suppression-list charging, contact pricing terms must be linked to email platform 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: email platform invoice

For email platform suppression-list charging, email platform invoice must be linked to suppression-list 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

Separate subscribed, unsubscribed and suppressed states at the contractual measurement event. Build the comparison at the level identified by suppression-list export and retain the governing version from audience status history. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.

Exception conditions

Suppressed records may remain billable under the plan. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked suppression-list export, audience status history, contact pricing terms, email platform 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

Marketing operations validates states and required suppression retention. Document the counted population rather than equating deliverability with entitlement. 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 suppression-list export or audience status history 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 email platform suppression-list charging 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