# Map receiver tax numbers from Peoplevox
URL: https://support.starshipit.com/articles/1793376000001-map-receiver-tax-numbers-from-peoplevox
Canonical: https://support.starshipit.com/articles/1793376000001-map-receiver-tax-numbers-from-peoplevox
Markdown: https://support.starshipit.com/articles/1793376000001-map-receiver-tax-numbers-from-peoplevox.md
Updated: 2026-10-30

> For the complete documentation index, see [llms.txt](https://support.starshipit.com/llms.txt).

> Import receiver tax numbers from Peoplevox sales-order fields and check them before generating shipping labels.

Map Peoplevox sales-order fields to receiver tax numbers in Starshipit so the details are available before label creation. Each mapping identifies the source field, tax type and destination it applies to.

## Before you begin

- [Connect Peoplevox to Starshipit](/articles/360000934795-connect-peoplevox-to-starshipit) and use an account with permission to edit the integration.
- Confirm which Peoplevox sales-order field contains the receiver's number. Supported sources are **Attribute1** to **Attribute5** and **CustomsRegistrationNumber**.
- Confirm the receiver tax type and destination required for your shipment. Courier and service support still applies; see [Receiver tax numbers](/articles/9133191385-receiver-tax-numbers).
- If using **CustomsRegistrationNumber**, confirm your Peoplevox account supports it and includes it in the data sent to Starshipit. An existing allocation subscription must be recreated after saving this mapping.

## Add the mappings in UI 2.0

1. Go to **Settings > Integrations > Peoplevox** and open the connection you use, then select its **Settings** tab.
2. Find **Receiver tax numbers**, then select **Add tax mapping**.
3. Under **Peoplevox field**, select the sales-order field that holds the number.
4. Under **Starshipit tax type**, select the appropriate type. For Mexico RFC, choose **VAT - VAT Registration**. For Brazil CPF/CNPJ, choose **CNP - Brazil CNPJ/CPF Federal Tax**.
5. Under **Destination country**, select the destination the mapping applies to. Use a broader country group only when the same source and tax type are appropriate for those destinations.
6. Add another row for each additional mapping you need. Use only one row for each tax type and destination combination.
7. Select **Save**, then reopen the connection and confirm the rows remain.

These mappings are optional. Leaving the table empty adds no receiver-tax import mapping. To stop using a mapping, select **Remove** on its row and save.

## Recreate an allocation subscription when needed

If you added a **CustomsRegistrationNumber** mapping and already receive orders when stock is allocated:

1. Save the mapping before changing the subscription.
2. On the integration's **Settings** tab, find the allocation subscription controls.
3. Select **Unsubscribe** and confirm it succeeds.
4. Select **Subscribe** and confirm the connection shows a subscription ID again.
5. Check the next planned allocation to confirm the field is included.

Coordinate this change with the team processing orders so they can check allocations made while the subscription was being recreated. You do not need to enable allocation imports if you only receive orders at despatch.

## Understand which number is used

The mappings apply when Peoplevox sends an allocated order or a despatched order, including a label request.

- Blank source values are skipped.
- For the same tax type, a destination-specific mapping takes precedence over a broader group mapping. If its source is blank, a matching broader mapping can supply the value.
- An existing nonblank receiver tax number of the same type that applies to the destination is kept. A mapped value does not replace it.

Saving a mapping does not backfill earlier orders. Check the actual shipment before printing rather than assuming a settings change corrected it.

## Verify before generating a label

1. Use a planned Peoplevox allocation or despatch whose source field is populated and whose destination matches your mapping.
2. Open the resulting order in Starshipit before label creation, where your workflow allows it.
3. Check the receiver tax details against the Peoplevox source: number, tax type and destination.
4. If Peoplevox requests the label automatically at despatch, verify the mapping with your normal controlled test despatch before using it for more orders. Check that the expected receiver tax details and shipping documents are returned.

A successful connection test confirms the connection; it does not prove a particular order supplied the tax number or that the courier accepted it.

## Troubleshooting

| Problem | What to check |
| --- | --- |
| The number is missing | Check the selected sales-order field is populated, the destination matches the mapping, and Peoplevox includes the field in the allocation or despatch data. |
| **CustomsRegistrationNumber** is missing on allocation | Confirm Peoplevox supports the field, then recreate the existing allocation subscription after saving the mapping. |
| An older number remains | Check for an existing applicable receiver tax number of the same type. It is preserved instead of overwritten by the mapping. |
| The settings will not save | Give every row a supported field, tax type and destination. Remove incomplete rows or duplicate tax-type/destination combinations. |
| The courier rejects the number | Confirm the required identifier and service support, then check the order's receiver details before retrying the label request. |

## Related articles

- [Connect Peoplevox to Starshipit](/articles/360000934795-connect-peoplevox-to-starshipit)
- [Receiver tax numbers](/articles/9133191385-receiver-tax-numbers)
- [Troubleshoot Peoplevox](/articles/90200000000502-troubleshoot-peoplevox)