IOSOR Learn
DID Second Month: Full MRC when the UTC Calendar Rolls
Understand the transition from initial prorated DID costs to the full monthly recurring charge (MRC) triggered by the UTC calendar roll on the 1st of the month.
Navigating the lifecycle of a virtual number requires a clear understanding of how the billing cycle shifts from the initial acquisition to the recurring maintenance phase. Unlike the first day of service, which follows specific DID first-month setup and prorate math, the second month introduces the standard Monthly Recurring Charge (MRC) in its entirety. This transition is strictly governed by the UTC calendar, ensuring a synchronized billing event across all global assets assigned to your account.
The UTC Transition from Prorate to Full Rent
When a number is first assigned via JIT (Just-In-Time) provisioning, the system calculates a partial fee based on the remaining days in the current month. However, as soon as the clock strikes 00:00 UTC on the first day of the new month, the DID invoice week: prorate rows vs full calendar month logic shifts. The system no longer looks at the specific day of the month the number was acquired; it simply identifies the asset as active and applies the full monthly rate.
Prepaid Balance Logic on the First of the Month
IOSOR operates on a strict prepaid model. To maintain service continuity, the system must have sufficient funds to cover the full MRC of all active DIDs at the moment of the UTC roll. If the balance falls below the required amount, the system may trigger automated suspension protocols to prevent negative equity. It is essential to maintain the USD 20 prepaid floor to ensure that high-volume number blocks do not exhaust the account balance during the midnight transition. This buffer is your safety net.
Comparing Initial Setup vs Recurring Cycles
| Billing Event | Timing | Calculation Type | Impact |
|---|---|---|---|
| Initial Assignment | JIT Request | Setup + Prorate | Immediate Deduction |
| Second Month Roll | 1st 00:00 UTC | Full MRC | Recurring Deduction |
| Subsequent Months | 1st 00:00 UTC | Full MRC | Stability Phase |
| Soft Review | Monthly | Usage Audit | Account Health |
Scaling Thresholds and Balance Reviews
As your operations grow, the total MRC for your DID inventory may increase significantly. For accounts where the total monthly recurring costs or usage fees approach a soft review near USD 1,000/month, our financial team performs a routine audit. This review is designed to ensure that the prepaid architecture is optimized for your traffic patterns, whether you are focusing on high-volume SMS, OTP delivery, or voice services. Maintaining a healthy buffer above the USD 20 floor is the best way to avoid service interruptions.
Technical Webhooks and Number Status
To automate your accounting, you can utilize webhooks that trigger upon successful MRC deductions. When the system processes the full rent on the 1st UTC, a ledger entry is generated for every active asset. Monitoring these events allows your internal systems to reconcile costs in real-time without manual intervention. If a webhook fails to fire, check your endpoint connectivity immediately.
Start with IOSOR
At 00:00 UTC on the 1st the rent row becomes full MRC for every still-assigned DID. First month was setup plus remaining days. Export the calendar roll so finance does not expect another prorate on the same number.
IOSOR takeaway
Second month is full calendar MRC, not leftover-day math.
Do: fund full rent before the UTC 1st. Don’t: budget second month as another prorate.
Was this guide helpful?
Related guides
- Second-owner DID handover: who may assign and release
Master operational boundaries, JIT provisioning, and prepaid financial thresholds during second-owner DID handovers.
- Spend Cap Per DID: Rent Plus MT Burn On One Number
Control per-number exposure in your white-label CPaaS with a combined spend cap for MRC and outbound mobile terminated traffic.
- Inbound webhook routing on DID: MO without owner loses STOP
Route inbound webhooks to the owning account securely. Prevent orphan MO events and missed opt-outs in white-label prepaid CPaaS.