Accepting a tax ID transfer no longer charges

9 November 2026 — Until now, accepting a transfer in an account with no free additional tax ID seat bought the missing seat and charged it right away. The account giving the company away had already paid that seat until its renewal, so for a few weeks the same tax ID was paid twice. From today, accepting never charges.

• No charge on accept — POST /v1/accounts/{account}/nif-transfers/accept no longer buys seats. If the receiving account has no free additional tax ID seat, the tax ID still moves in and is covered until the next renewal of its additional tax ID subscription. At that renewal the seat is added to the contracted ones and starts being billed, with no proration.
• Two 402 responses fewer — The operation stops answering 402 payment_method_required and 402 additional_nif_charge_failed: there is no charge left that could fail. The plan gates are unchanged, for example 402 additional_nif_plan_required. Both codes remain in the operations that do buy seats, such as creating or activating a company.
• Occupied seats — While the coverage lasts, the covered tax ID does not count in seats.occupied of GET /v1/accounts/{account}/additional-nif-seats. It starts counting when the renewal adds it to the contracted seats.
• Employees — The employees that arrive with the company get the same treatment: they are not charged on accept and their seats are added at the renewal of the receiving account's employee seats.
• MCP tool — accept_nif_transfer behaves the same way.

Your integration keeps working: it just stops receiving two errors. If you opened the billing portal with error.details.payment_setup_url on accept, that branch no longer runs. What the person accepting sees in the app is in Tax ID transfers in the app.