A carrier transaction type maps a carrier’s product code to one of your internal transaction types. When the platform imports non-call charges from a carrier, each line contains a product code. This mapping tells the platform which transaction type to use, so charges are classified correctly.
This works in the same way as carrier call types but for non-call charges. For example, a carrier might use “PSTN_LINE” for line rental and “INSTALL_FEE” for installations. You create a mapping for each code so the platform knows how to categorise them.
Key Features
- Translate carrier product codes to your internal transaction types
- Support different code sets per carrier
- Keep non-call charge classification accurate
Field Reference
Carrier Transaction Type
Carrier
The carrier this mapping applies to.
Transaction Type
The internal transaction type that this product code maps to.
Charge Band
The product code or charge band name as it appears in the carrier’s files. Maximum 90 characters. This must match exactly what the carrier sends.