Question about financial transaction history and also incoming SMS speed

I was looking at the history for this year and all I see are the $1.10 per DID charges in the transaction list. I should see at least a few calls and charges for SMS texts. Are they shown a different way?

Also, I wanted to confirm if the phone call and SMS rates were the same for incoming and outgoing calls and texts.

Finally — and sorry to keep bringing this up — why are incoming SMS texts taking so long? If I send an SMS it gets received on the other side instantly. But incoming texts take up to a minute to be received. That’s frustrating with things like authorization codes from banks.

Thanks.

Hello @douglerner,

The information is available here and there. All the following is from the “Finance” menu.

  • The calls (and related prices) are in the CDR (Call Detail Report). Pick the period you want and at the bottom under the report table you have the total cost.
  • The MSG Detail Records will give you the same for the SMS/MMS. Pick the period and total at the bottom. You will see the incoming and outgoing prices (the same).
  • The Transaction History is for the monthly costs, and the amounts you put in your account.

:backhand_index_pointing_right: You also can use “Generate Invoice” to have a more grouped view.

  • You will see, without the details, all the charges, etc., in one report.
  • Maybe this is more what you are looking for.

Kind regards!

1 Like

Yes, that was helpful. Thanks.

1 Like

@aleclerc already pointed you at the right pages, so this is just a footnote to that. We happened to have a test account handy and tried your questions on it, in case seeing actual figures is useful.

Everything below is that test account’s data, and it’s a very quiet account, so please read the numbers as illustrative rather than as anything about yours.

1. Why the call and text charges aren’t in Transaction History

From what we can tell they’re simply kept in a different place. Transaction History seems to record account-level events – DID monthly fees, DID activation fees, fax number monthly fees, payments and deposits – while per-minute call cost and per-message cost come off the balance directly and appear only in the Call Detail Record and the MSG Detail Records.

The part that caught us out: if you try to reconcile your balance from Transaction History alone, you’ll be short by your usage total for the period. On our test account that was about 2 cents, so it hardly matters there, but it would scale with call volume.

2. Pulling the per-call costs

Asking for a breakdown gave us the metered charges grouped by number. On that account: 9 billed inbound calls totaling $0.0198, all at $0.009/min in 6-second increments, across two of its three DIDs.

3. Whether incoming and outgoing rates match

This is the one where we’d be most cautious, because our test account came out asymmetric and we don’t know how typical that is:

  • Inbound to a per-minute DID: $0.0090/min
  • Outbound to Toronto (416/647): $0.0052/min on Value, $0.0072/min on Premium

Both bill in 6-second increments. So on that account inbound actually cost more per minute than outbound to the same area code, which surprised us. But the inbound side depends on whether the DID is billed per-minute or flat-rate, and the outbound side depends on which route the sub-account uses, so yours could easily come out differently. Worth checking your own numbers rather than trusting ours.

For texts we couldn’t come up with a figure at all. We couldn’t find a per-message cost or rate anywhere in the API responses, for SMS or MMS, even though call records and fax records do carry rate and total. So the portal’s MSG Detail Records / Rates pages may be the only place to get message pricing. Happy to be corrected if someone knows a way we missed.

4. The ~1 minute inbound SMS delay

We don’t have anything useful for you here, unfortunately. As far as we can see that’s upstream carrier and aggregator handoff, and there’s nothing in the API that exposes per-hop delivery timing or lets you influence it, so it isn’t something you can query your way out of. It may be worth its own thread with support and some real timestamps – for authorization codes a minute is genuinely painful, and that’s a fair thing to push on.

The screenshots are us asking an AI assistant these questions against that test account, through an (unofficial) MCP server we maintain for VoIP.ms: you ask in plain language and it pulls the call records, transaction history and rate tables. It’s at https://voipms-mcp.ecliptical.io if you’re curious. Mentioning it only because it’s how we produced the screenshots – the answers above hold regardless.

I don’t know if the delays have anything to do with upstream. The voip.ms SMS app has much shorter delays of a few seconds. Even that seconds of delay seem to be related to the API server performance. I have been playing with API recently and found it is a bit buggy. For example, it does not handle non-ASCII characters well. I submitted a ticket on this issue a month ago, and they admitted that it was an API issue. The ticket is still open and I hope that the issue can be resolved soon.

2 Likes

Regarding the ~1 minute delay on receiving SMS I just want to add that this only happens with VoIP.ms. And it doesn’t depend on the client I’m using, which is GroundWire. The same delay happens even while testing directly in the dashboard.

Most important to note, this does not happen with other VoIP apps I use: Talkatone and TextNow.

I would definitely use VoIP.ms more if this basic SMS communication delay was taken care of. Thanks.

1 Like

Exact. The delay is 100% from their internal processes. It always has been so. Receiving a SMS is slow, period.

It feels like it is a process working at regular intervals like in old school batch systems.

I might be wrong, but I always envisioned that way as best explanation for it.

Kind regards!

You may want to check whether usage charges and recurring DID fees are listed in separate sections of the billing history. For the SMS delay, I’d also be interested to know if others are seeing the same behavior or if it’s limited to certain carriers.

I have tried different client and the delay is always there when using forward to sub-account. When using voip.ms SMS app, delay is only a few seconds.