IOSOR Learn
DLR invoice week: unknown share is not delivered
Examine how unknown delivery receipt shares impact invoice week calculations, pre-funded balances, and carrier status honesty for prepaid CPaaS operations.
Invoice week reprints the unknown share as unknown, never as delivered.
Invoice week uncertainty and the unknown share
When invoice week arrives, prepaid CPaaS operators reconcile their SMS and OTP volumes against delivery receipts. A persistent complication is the unknown share of DLR statuses. If an upstream gateway returns pending or indeterminate codes when carriers fail to confirm final delivery, your billing reports may mask actual network drops. Running a USD 20 prepaid floor protects your treasury from absorbing these invisible losses, but your tenants still demand billing transparency.
Network reality versus carrier status honesty
Carriers occasionally report unknown states instead of hard failures to preserve route metrics or due to protocol translation gaps in SS7 and SMPP bridges. For white-label platforms, this creates a friction point during financial reconciliation. If you bill tenants for messages that languish in an unknown state, disputes spike. Operators must differentiate between genuine transit delays and silent carrier rejections. For deeper investigation into similar reporting gaps, cross-reference our guide on the missing signal.
Financial impact on high-volume traffic
As tenants scale their campaigns past a soft review near USD 1,000/month, unknown DLR percentages distort financial projections. An unconfirmed status cannot be automatically classified as delivered, yet treating every unknown as a hard failure risks false credit issuance. Prepaid platforms must enforce strict reconciliation logic. JIT provisioning and automated prepaid holds ensure that funds are secured before dispatch, preventing uncollectible debt when final delivery states remain unresolved.
Mitigating unconfirmed receipts through policy
Resolving ambiguous billing requires transparent platform rules regarding indeterminate delivery receipts. Tenants need clear guidance on how your engine handles unconfirmed terminal states. Review our documentation on the DLR retry policy to understand how re-queuing interacts with unknown terminal flags. Establishing predictable thresholds prevents tenant churn and maintains trust during audit cycles.
Analyzing volumetric impact after reconciliation
Once invoice week closes, audit the ratio of failed and unknown statuses against historical baselines. Sudden spikes in unconfirmed shares often indicate route degradation or upstream filtering. Pair this analysis with a failed-ratio review to isolate problematic carrier paths before they drain tenant balances and trigger support escalations.
Start with IOSOR for transparent DLR accounting
Open the invoice reprint and split unknown rows from delivered. Stamp the unknown share on the same export finance will sign. Do not convert unknown to delivered to close the week. Map codes if a row is still grey. This is a reprint job, not an incident freeze and not a pilot dashboard.
Related: Standardizing Carrier Error Codes to Fix Misleading Delivery Reports Setting Up Deliverability Threshold Alerts for Reseller Support Teams Prepaid hold before first debit.
IOSOR takeaway
Invoice week reprints unknown as unknown — never as delivered.
Do: reprint with the unknown share visible and signed.
Don’t: relabel unknown as delivered to close the invoice, or treat this as a live freeze.
Was this guide helpful?
Related guides
- Comparing Deliverability Metrics Across Short Code and Toll-Free Routes
Analyze SMS deliverability metrics between short codes and toll-free numbers for white-label CPaaS clients, detailing filtering and DLR tracking.
- Establishing Baseline Deliverability Metrics During New Route Pilots
Run rigorous delivery test suites, analyze carrier performance, and establish baseline messaging metrics before scaling your white-label traffic on new routes.
- Auditing Delivery Rates and Clearing Queues After Network Maintenance
Step-by-step technical playbook for platform managers to verify route health and flush delayed DLR queues safely after carrier and telecom network maintenance windows.