---
title: "Importing NPANXX Data"
slug: "importing-npanxx-data"
updated: 2026-07-23T11:14:43Z
published: 2026-08-10T20:23:40Z
canonical: "help.idibilling.com/importing-npanxx-data"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.idibilling.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Importing NPANXX Data

> [!NOTE]
> Note
> 
> If your company is an IDI SaaS customer, your Billing Specialist imports the NPANXX data.

In order to properly rate usage, the IDI platform's NPANXX table must be kept up to date. The IDI platform uses its Background Processes Service to import the NPANXX information.

The process starts as soon as the file is placed in the appropriate import folder in the eFramNET directory of the server: `InfoDirections\eFrameNET\Environments\environmentName\serverName_BackgroundProcess\NpaNxx Import\In`. The Background Processes Service processes the file, adding and updating records in the NPANXX table. After a file is processed, it is moved into a `\Done `folder. A log file in the `\Error` folder contain status and error messages that the administrator can use to trouble-shoot the process, if necessary.

Your company needs determine whether to purchase CCMI's `tmf.dat` file or Telcordia's `tpm.dat` file for NPANXX import.

> [!NOTE]
> Note
> 
> Telcordia’s proprietary RAO information (which is used for LEC billing) and the Bell ID (which is used to provision local service via Neustar) are not included in the `tmf.dat` file. You must purchase Telcordia’s `tpm.dat` file to import that information.

You can manage NPANXX information from the IDI Desktop Client.

See also:

[Searching the NPANXX Table](/v1/docs/searching-the-npanxx-table)

[LATAs, NPAs, and States](/v1/docs/latas-npas-states-and-zones)

[Unmatched LATAs,NPAs, and States](/v1/docs/unmatched-latas-npas-and-states)

[NPANXX Splits](/v1/docs/npanxx-splits)