Verify session correlation for finance export: two debits, one ledger story

A signup asked for one OTP. Product saw “one code.” The wallet posted two lines: an SMS (or voice) delivery debit and a Verify session debit. Teams that mash those into “OTP cost” either double-count in the board pack or hide the second row until close. This page is the join key finance can export: one session story across both lines.

IOSOR runs white-label prepaid Verify beside messaging on one ledger. Catalog live is a real channel; in setup is not a free session. Near USD 1,000+ monthly usage, unmatched SMS and Verify rows become commercial review. Pair with OTP delivery vs verify two debits and OTP without chaos. Spend stops: prepaid spend control.

Delivery debit vs verify debit

The journey is one. The money is two. Related, never aliases. The delivery debit covers getting the code to the destination: encoding, segments, corridor, terminal DLR. The Verify session debit covers issue, TTL window, check, expire, and resend policy. If finance only sees SMS, Verify looks “free.” If product only sees Verify, SMS burn looks like “more sessions.” Both rows must carry the same correlation id.

Session ID fields finance must export

A correlation ID that lives only in engineering logs is not an export. Finance must reconstruct from CSV: verify_session_id, related message_id or delivery id, destination, channel, TTL, terminal reason, debit amount and timestamp per row. A weekly dump without that join is a receipt pile. Put the session id on the wallet row, the webhook, and the recon sheet. Idempotency keys stop double-create; correlation keys stop double-blind. Do not mint a new id on every 5xx retry of the same intent.

Resend TTL and duplicate rows

Resend policy decides whether duplicate rows appear. A cooldown that blocks the session but still fires SMS (or the reverse) makes two ledgers argue. TTL expiry should close the same Verify row, not open a ghost session.

Reconciliation before scale

Before you scale, reconcile one week: sessions created versus SMS (or fallback) attempts; terminal DLR versus session terminal; user resends versus system retries, counted apart.

Red flags

• Blended “OTP fee” with no SMS versus session split
• Verify billed like a marketing blast
• Resend button that ignores cooldown on one of the two paths
• Client errors that name upstream brands
• Verify promised while the channel is still in setup
• Weekly export with no session correlation id
• New session id on every transport retry

Start with IOSOR

Export a sample weekly CSV from your verification dashboard and verify that every verify_session_id maps directly to its corresponding delivery message_id records. Configure webhook logging to record session terminal reasons alongside carrier delivery receipts before pushing production updates. Hold any traffic expansion until finance successfully reconciles user-initiated resends against system retry debits across a full seven-day window.

IOSOR takeaway

Tracking verification costs requires separating the session lifecycle from underlying message delivery debits. When finance views authentication fees through a single blended delivery bucket without session correlation, phantom debits and unmapped resend costs corrupt accounting ledgers.

Ensure your finance exports always include the verify_session_id, associated delivery message_id, TTL window, terminal status, and precise debit breakdown per row. Never allow resend policies to fire delivery attempts without updating the original session row or logging explicit correlation IDs.