0401·The seller registration number has no valid access token

What this means

Tokens are bound to a specific registration number. A token that is valid in itself will still fail if the invoice names a different seller. This also fires when the seller number is not a valid length.

Why it happens

• A sandbox token was used against the production endpoint, or the reverse.
• One tenant's token was used to submit another tenant's invoice — a real hazard in multi-tenant systems.
• The seller number on the invoice differs from the one the token was issued against.
• The token was never activated because sandbox scenario testing was not completed.

How to fix it

1. 1Store tokens per taxpayer and resolve the token from the invoice's seller, never from global configuration.
2. 2Keep sandbox and production tokens clearly separated and select by environment.
3. 3Confirm the seller number on the invoice matches the registration the token belongs to.
4. 4Check the bearer scheme is present in the authorization header.

Related errors

• 0402The buyer registration number has no valid access token
• 0082The seller is not registered for sales tax
• 0083Seller registration number does not match