A carrier transaction type is the non-call sibling of the carrier call type. Where carrier call types translate CDR charge bands into your internal call types, carrier transaction types translate the product codes on fixed fee files into your internal transaction types. Between them, the two lists cover every coded value a carrier can send you.
Fixed fee files typically cover everything the carrier charges you for that isn’t a call: line rentals, broadband subscriptions, installations, one-off provisioning fees, router rental, cease charges, and so on. Each line on the file has a product code, and the platform needs to know which of your internal transaction types that code should land against. The internal transaction type then drives:
- Which group the charge appears under on the customer’s invoice (line rental charges grouped together, hardware one-offs grouped separately, and so on).
- Which accounting code is used when exporting invoice data, so wholesale costs flow into the right general-ledger account.
- Which fixed fee tariff rule applies, which determines the retail price charged to the customer.
Typical times you’ll be editing this list:
- New carrier onboarding: add a mapping for every product code in the carrier’s fixed fee catalogue before the first fixed fee file lands, so imports allocate cleanly.
- New product launches: when a carrier introduces a new wholesale product (a new broadband speed tier, a new hardware SKU), add a mapping so the product is billed correctly from day one.
- Reclassifying charges: move a mapping to a different internal transaction type when you change how something appears on invoices (for example, splitting “installation” into “engineer visit” and “provisioning fee”).
What this page covers
- A full field reference for every field on the carrier transaction type record.
- How mappings are used during fixed fee file imports to create carrier transactions.
For the call-traffic equivalent, see Carrier Call Types.
Field Reference
The table below lists every field on the carrier transaction type record.
Identification
Basic identification information for this carrier transaction type.
No fields defined for this section.
Carrier Transaction Type
Configuration mapping carrier products to internal transaction types.
| Field | Description |
|---|---|
| Carrier | The carrier this transaction type mapping applies to |
| Transaction Type | The internal transaction type to map to |
| Charge Band | The carrier product or charge band name |
Notes on key fields
Charge Band
The product code or charge band name as it appears in the carrier’s files, up to 90 characters. This must match exactly what the carrier sends, otherwise the mapping won’t fire.
Transaction Type
When the platform imports non-call charges from the carrier and sees this charge band, it uses the linked internal transaction type. This controls which group the charge appears under on customer invoices and which accounting code applies on invoice exports.