Forum Discussion
Olivier_Tassinari
Déchiffreur de rythmes
Déchiffreur de rythmesregistration_number outdated
Hi, we found a bug: the `registration_number` column seems to be completely out of sync for our accounts. We have many examples where the value in this Redshift database doesn't match the value in the "Supplier ID" field of the UI:
This is problematic because we are trying to prepare for the e-invoice reporting obligations. We can't rely on the current state of the "Verification" feature of Pennylane, as it only covers French customers or suppliers, but we barely do any business in France; we are only incorporated there, so we need to support the other EU and non-EU countries.
We waited +48 h, so the problem is not a sync delay between the Pennylane database and the Redshift database.
Bonjour Olivier_Tassinari
The public data-sharing documentation defines registration_number on the suppliers model as "the supplier's official registration number, for example SIREN in France." It is designed to be used together with a separate registration_country_alpha2 column, since the same legal entity can have a postal address in one country and a registration address in another — the registration number combined with its country code, not the number alone, is what uniquely identifies a supplier record in this model.
1 Réponse
- Angélique_
Pennylaneur
Bonjour Olivier_Tassinari
The public data-sharing documentation defines registration_number on the suppliers model as "the supplier's official registration number, for example SIREN in France." It is designed to be used together with a separate registration_country_alpha2 column, since the same legal entity can have a postal address in one country and a registration address in another — the registration number combined with its country code, not the number alone, is what uniquely identifies a supplier record in this model.
