IOSOR Learn
DID first-month setup and prorate: client-visible math on prepaid rental
UTC calendar-month prorate, setup plus MRC on the first period, renewal on the 1st, and a client list at least 2× — rent math finance can export from the prepaid wallet.
Finance often reads the first DID invoice as “setup plus a full month,” then argues when the next debit lands on the 1st UTC. The client-visible contract is a UTC calendar month: first charge = setup + prorated MRC for remaining days (today through last day, inclusive); paid-through ends at the next 1st UTC; later renewals bill the full list monthly. List stays at or above a 2× floor. Ordering is JIT: live search, prepaid hold, buy on success, honest assign — local and toll-free rental reality.
IOSOR is white-label prepaid: one wallet, quoted list, no mystery “adjustments,” no platform subscription to warm an empty account. Catalog live vs in setup is independent of rent math — a number in setup for messaging is not a cheaper first month. Near USD 1,000+ monthly usage, rent lines enter commercial review. Pair with USD 20 floor vs volume review and prepaid spend control.
First period: setup plus prorated MRC
Two client-visible parts. Setup is the one-time list to bring the assignment online. Prorated MRC = list monthly × remaining UTC days ÷ days in that month. Inclusive: buy on day D of N → (N − D + 1) / N. A typical US local list floor is USD 10 setup and USD 10.20 monthly. Order on UTC 14 August (31 days): fraction 18/31; prorated MRC ≈ USD 5.92; first charge ≈ USD 15.92. Export setup, fraction, prorated MRC, and paid-through.
| Line | Finance should see | Not this |
|---|---|---|
| First debit | Setup + prorated MRC | Rolling 30-day month or silent full MRC |
| Paid-through | Next 1st UTC | Anniversary on the order weekday |
| Later 1sts | Full list monthly | Second setup or unexplained catch-up |
| List | ≥ 2× floor, quoted | Hidden cost sheet from another brand |
UTC calendar month, not a rolling 30 days
A 30-day clock from the order date fights every finance close. August rent covers through 31 August UTC; September starts 00:00 UTC on the 1st. Office time zones do not rewrite the fraction. JIT hold still happens before the buy — failed orders refund the hold. Catalog in setup does not change the calendar.
Renewal on the 1st: full monthly list
From the next 1st UTC, renewals bill full list monthly and advance paid-through to the following 1st. No second setup on a clean renewal.
Client-visible list and the ≥2× floor
Clients see list, never internal floor arithmetic. Quoted list ≥ 2× the destination floor for that number type.
Red flags
- First invoice billed as setup + full MRC on a mid-month buy
- Rolling 30-day anniversary sold as “calendar month”
- Mystery “adjustments” instead of named prorate fractions
- Second setup charged on a clean 1st renewal
- List below the 2× floor, or floor math dumped into client errors
- Activated badge before assignment, or rent treated as a Live flip while in setup
Start with IOSOR
Quote one local DID and screenshot the setup fee, the monthly list, and the first-charge estimate before you hold. Place the JIT order only after the prepaid hold, then export setup, prorated MRC, the day fraction, and paid-through. Confirm the next UTC 1st bills full monthly with no second setup. Hand that export to finance so renewal math is not a hallway story.
IOSOR takeaway
The first month is setup once plus prorated MRC for the remaining UTC days. The next 1st bills full monthly. The buyer must see that split before the hold.
Do: show the fraction and paid-through on the receipt. Don't: hide the first-charge split or charge setup again on renewal.
Was this guide helpful?
Related guides
- Incident Week Route Failover: Reconciling Rate Discrepancies After Emergency Switching
Master post-incident wallet ledger reconciliation for high-cost secondary carrier failovers on your white-label CPaaS platform.
- Sub-Account Volume Recalibration: Transitioning Clients Beyond Initial Monthly Floors
Adjust client prepaid rate structures and top-up floors once monthly dispatch volume consistently exceeds baseline thresholds.
- Toll-Free Verification Surcharges: Accounting for One-Time Prepaid Registry Fees
Learn how white-label CPaaS platforms debit one-time carrier verification and campaign registry surcharges from child account prepaid balances.