Sender reject vs content filter: status truth for finance

Two prepaid burns look alike on a rough dashboard and are not the same event. A sender / registration reject means the from-identity was not allowed for that corridor or message class — the unit never earned a delivery path. A content filter can accept the job, flash sent/submitted, then block inbox after prepaid moved. Finance that folds both into "delivered" invents a false success rate.

IOSOR is white-label prepaid. Floor USD 20; soft review near USD 1,000/month turns mixed reject labels into night reconciliations. Choice: Sender ID choice before the first campaign. Gate: Sender registration gate before production. Filter: sent is not inbox. Money: Debit rows vs delivery status ledger.

Two failure classes finance must not merge

Same debit can attach to either lane.

Sender / registration reject: identity failed before content

Reject here is an identity gate: unregistered alphanumeric, pending 10DLC, incomplete toll-free verification, or a forbidden from-string for that ISO/class. Fix registration — Sender registration gate before production — not the template. Do not retry identical creative. Hold should release or never open; wrong-path settled debits get an explicit refund linked to the intent. Client status stays rejected — never sent or delivered.

Content filter: handoff can look sent while inbox never arrives

Filter outcomes are deliverability truth after acceptance. Sent/submitted means handoff, not handset — sent is not inbox. Pair with undelivered, rejected, expired. Retrying the same copy burns prepaid twice — change template, list, or sender class first. Never relabel filter as "sender reject," or registration reject as "filtered."

Export columns that keep the lanes honest

One row per intent: fail class (sender_reject | content_filter | other), from-identity id, registration snapshot, template family, debit/release/refund, terminal status, correlation id. Product and finance share that row — Debit rows vs delivery status ledger. If the sheet only shows "failed," reopen until the class is named.

Buyer checklist for reject vs filter truth

1. 2. Filter hits keep sent≠inbox language (sent is not inbox)? 3.

Start with IOSOR

Open your IOSOR reporting exports and inspect the failure classification mapping before running your monthly financial reconciliation. Ensure sender registration rejections and post-handoff content filters write to distinct fail_class columns rather than being grouped under a generic rejected status. Configure webhooks to capture terminal DLR correlation IDs alongside registration snapshots so compliance and finance audit from a single source of truth.

IOSOR takeaway

This article proved that combining sender registration rejections with downstream content filters corrupts both financial ledgers and deliverability analytics. Registration failures occur at the identity gate before message dispatch, while content filters represent post-acceptance network filtering where handoff status differs from inbox delivery.