What are Messaging Billing Detail Records?
Messaging Billing Detail Records (BDRs) provide a detailed view of billable messages (segments) associated with your service account. You can use them to reconcile your invoice.
How do I download Messaging BDRs?
Log in to the Bandwidth App.
In the side navigation bar, select Insights.
Select Reports and click Charges.
Under Type, select Messaging.
Under Report Name, select Messaging BDRs.
Under Service Month, select the month associated with the charges you want to download. You can choose any month up to 13 months back. For the current month, you can download all available records month-to-date. Please note that data may be delayed by a few hours.
Under Region, select whether you want to download the data for the US or the EU.
Under Breakdown, select one of the following options for how you want your data to be separated into more than one file:
Automatic is selected by default. When the downloaded data exceeds file row limits, it can be separated into multiple files, allowing access to all data.
Select Location to download separate files for each Location associated with the service account.
Select Sub-Account to download separate files for each Sub-Account associated with the service account.
Open the Advanced Filters drop-down menu to filter your data by additional criteria:
Use the Campaign ID drop-down menu to filter for a specific 10DLC Campaign.
Use the Sub-Account ID drop-down menu to filter for specific Sub-Account(s) associated with your service account.
Use Location ID to filter for specific Location(s) within your Sub-Account(s).
Click Download Report to begin processing. Once the status in the table below changes to Completed, click the icon under Actions to download the CSV copy of the report (it will be available for 5 days). All reports for this category from the last 30 days will also appear here.
Messaging BDR report field descriptions
The following table contains the descriptions and example values of the fields in the Messaging BDRs report.
Note: All times are in UTC (Coordinated Universal Time).
Field | Description | Example Value |
Invoice Month | This represents the month associated with the charges. | 11-2023 |
Message Date & Time | This indicates when the message was sent (for outbound messages) and received (for inbound messages). This is when the billable event occurred.
Note: Since each record represents a segment, a segmented message could have different service periods for billing. | 2023-11-01T00:07:45.622Z |
MDR ID | This is a unique identifier for each segment of a message, which aids in the identification of the message segment if needed.
Note: Each segment of a message has an individual MDR ID. | 00000000-0000-0000-000000000000 |
Message ID | This is a unique identifier given to a message. All segments in a message will have the same Message ID. You may use this ID during troubleshooting to identify the message throughout Bandwidth’s systems. | 00000000-0000-0000-000000000000 |
Service Account ID | This is the Account ID associated with your Bandwidth App service account. MDRs are aggregated by individual service accounts. | 1234567 |
Rate | This represents the rate applied to this charge. | 0.00 |
Charge | This represents the total charge. Each line in the Messaging BDR report represents a billable message (MMS) or message segment (SMS), so the Rate & Charge are often the same value.
Note: Any discounting you may have contracted for will not be reflected in the rate you see in the BDRs for the Primary Charge Type, as that is done at the time of invoicing. The Surcharge Charge Type will reflect the correct rate. | 0.00 |
Charge Type | This represents whether the charge is for the message or a surcharge associated with the message. Primary = Message and Surcharge = Surcharge. | Primary, Surcharge |
Product Name | This represents the description for the charge that will match the description on the invoice. | Local A2P SMS Outbound |
From Number | This is the number that initiated the message. It'll follow the E.164 format. | 15555551234 |
To Number | This is the number that is receiving the message. It'll follow the E.164 format. | 525556667777 |
Message Direction | This represents the direction of the messaging: inbound or outbound. | INBOUND, OUTBOUND |
Message Type | This is the type of messaging being used. This will be populated as SMS or MMS. | sms, mms |
Message Status | This field shows the summary status of a message at the time of billing. Messages are billed on the attempt to send and the attempt to receive. Only billable statuses will be reflected here, as only billable messages are included in this report.
Outbound message statuses:
SENT: The message was successfully sent from Bandwidth. This becomes a terminal status when a delivery receipt (DLR) isn't received from the upstream provider because the customer didn't request it, the upstream provider didn't send it, or Bandwidth didn't receive it during the open window.
DELIVERED: Bandwidth received a DLR that indicates the message was delivered successfully.
UNDELIVERED: Bandwidth received a DLR that indicates the message failed or was rejected. The error code associated with the message indicates the specific issue.
Inbound message statuses:
DELIVERED: DLR was received, indicating the message was delivered successfully.
ACCEPTED: The message was accepted by the customer. | SENT |
Zone | This is the Zone associated with the reach of your message.
Based on the Destination Carrier and Country, SMS messages reach the specific zone listed in this field. For more information about Bandwidth’s Messaging Reach, visit this support article. | 0-5 |
Source Country | This is the country of the text message sender. This is the country of the “from” number or the message sender. | US |
Destination Country | This is the country of the “to” number or the message recipient. The “to” number is the Destination TN. | US |
Source State | This is the state of the text message sender. This is the state of the “from” number or the message sender. | NC |
Destination State | This is the state of the “to” number or the message recipient. | NC |
Carrier Name | This field helps you understand the carrier associated with the message. Carrier Name may not be present if Bandwidth rejects the message.
Note: Any carriers not explicitly called out in this article will be marked as "Other" in the MDRs and BDRs. | Please review this article for a list of all carriers you may see in the MDR/BDR reporting. |
Campaign ID | This field is specific to 10DLC messaging. If you’re contracted and approved to run 10DLC campaigns, this is the Campaign ID assigned to your campaign. This field will be blank if it doesn't apply to you. | user-specific |
Campaign Class | This is the AT&T campaign class assigned to your campaign. | A, B, C, D, E, F, T, G, P, Q, X, Z |
Segment Number | This is the segment number of the long message. You can use this field and the attribute Message Segments to determine the segment this record represents – for example: 1 of 2, 2 of 2. | 1 |
Message Segments | This is the number of segments the long message is broken into when sent or received. A single message may be broken into multiple segments for delivery as dictated by the underlying messaging protocol. The number of characters at which segmentation occurs varies depending on the type of characters used in the message body. To learn more about character encoding, see this support article. | 5 |
Length of Message | This is the length of the messages sent. If the message is across segments, it will show each segment's length. | 80 |
Location ID | This explains which of your Locations the message was associated with. | 536863 |
Location Name | This explains which of your Locations the message was associated with. | Location ABC |
Sub-Account ID | This field explains which Sub-Account the message was associated with. | 987654 |
Sub-Account Name | This field explains which Sub-Account the message was associated with. | Sub-Account ABC |
Back Bill (Y/N) | This indicates whether the message was backbilled. This occurs when a message is billed outside of its normal service period. | Y, N |
Global Account Number | This is the Global Account Number associated with you as the customer. If you have multiple service accounts (AccountIds), this helps identify you as a single customer. | BW-0000000 |
Sub-Account Customer ID | This represents an optional field, Customer ID, associated with a specific Sub-Account. This customer-specific value can be added to Sub-Account(s) to tag usage and charges. | 123456 |
Sub-Account Customer Name | This represents an optional field, Customer Name, associated with a specific Sub-Account. This customer-specific value can be added to Sub-Account(s) to tag usage and charges. | Name Example |