# Bill-to PCode

Source: https://developer.avalara.com/products/communications/integration-guides/communications-integration/fku5977262405048/

Guide: Communications

# Bill-to PCode

**Element type: Required**

**Enpoints/models used:** [Location](https://developer.avalara.com/api-reference/communications/v2/models/Location/)

PCodes are numeric identifiers for identifying taxing jurisdictions. PCodes provide the **most accurate** jurisdiction determination for calculating taxes with the AFC tax engine.

Your integration must include a field for entering the customer's PCode. This is specified using the`pcd` field in the [Location](https://developer.avalara.com/api-reference/communications/v2/models/Location/) model. If you would like to learn more about PCodes, refer to the [Obtaining PCodes](https://developer.avalara.com/communications-integration/transactions/jurisdictions/obtaining-pcodes) topic later in this guide.

Note

-   Once you use Avalara to derive the PCode from an address, you can rely on this value. It won’t change. Be sure to revalidate addresses on a periodic basis to make sure the best jurisdiction boundary match is made to an address as boundaries can change over time.

-   For high volume clients using street-address-level geocoding, we make it a requirement to GeoPCode addresses before calculation.

## Example

```
bill": {
  "ctry": "USA",
  "int": true,
  "geo": true,
  "pcd": 1956600,
  "addr": "110 Main St",
  "city": "Eveleth",
  "st": "MN",
  "zip": "55734"
}, 
```