IOSOR

IOSOR Learn

Inbound invoice week: MO vs MT mix on the same export

Reconcile inbound MO keyword volume and outbound MT delivery rows on a single white-label prepaid CPaaS export during invoice week.

Inbound invoice week: MO vs MT mix on the same export.

Invoice week ledger reconciliation

Invoice week requires balancing mobile originated keyword traffic against mobile terminated delivery records within a single transaction ledger. White-label operators reviewing client usage must match inbound payloads to outbound MT rows without relying on external upstream platforms. Every message carries a cost, and precise ledger data ensures that prepaid balances reflect exact consumption before automated top-ups trigger.

MO keyword load versus MT rows

Inbound keyword load represents user engagement through shortcodes or longcodes, whereas outbound MT rows account for automated system replies, alerts, or OTP tokens. Reconciling both on the same export reveals campaign efficiency and prevents billing discrepancies. Operators managing accounts near the USD 1,000/month threshold must audit these splits carefully to avoid margin erosion on high-frequency messaging flows.

Export data structures and formats

Traffic Type Payload Direction Ledger Unit Pricing Model
MO Keyword Inbound Request Prepaid Event
MT Message Outbound DLR Status Per-Segment
STOP/HELP Inbound Compliance Policy Rule

Regulatory compliance and safety

Maintaining proper opt-out mechanics is mandatory for all blended campaigns. Reviewing STOP and HELP keyword processing ensures adherence to regional frameworks. For further details on handling opt-outs, consult the STOP and HELP policy guide. Compliance failures can halt campaigns instantly, disrupting the entire revenue ledger.

Traffic analysis and margin protection

Separating mobile originated messages from mobile terminated delivery receipts clarifies platform profitability. Analyzing Inbound volume review: keyword load that drains the wallet trends helps operators forecast capacity requirements without maintaining physical inventory. Prepaid tenants operate on a USD 20 prepaid floor, ensuring zero unsecured credit exposure across client accounts.

Start with IOSOR

Pull one invoice-week export. Split every row into MO event or MT debit before the PDF leaves. Prove no inbound event is billed as an outbound line. If a two-way thread shares one correlation, show two tagged lines, not one blended count. This is a mix-split for finance, not a flood throttle and not a gateway lock.

IOSOR takeaway

Invoice week is a mix-split. MO is an event; MT is a debit. Same file, two kinds of line.

Do: tag every row MO or MT before the invoice goes out. Don't: fold MO count into MT spend and call it volume.

Was this guide helpful?

Related guides