The use case is to generate a CSID per branch (not a taxpayer in a VAT Group). So, every branch of a company will have it’s own CSID.
To onboard multiple branches, what fields do we need to define during the CSR generation? As I understand it, it needs to be the Organization Unit Name and Location, whereas the rest of the fields all correspond to the Main Company.
Additionally, when sending the Invoice XML for that particular branch, we need to define the Other Seller ID >> SchemeID=CRN of the particular branch. Now, in this case, do we still include the CompanyID=VAT Number of the Parent Company? And which elements in the XML need to have the Address of the Branch?
Lastly, what can be the reason we receive an email saying, that, “The commercial records below are not linked to the Fatoora Platform” >> with a list of the two branches (same TIN but different CRN).
Dear @Yatin,
Each device or solution that generates E-Invoices must have a CSID unless you use a central server for generating E-Invoice that is simply printed at branch in which case you just need one CSID for server. If you have multiple devices in a branch, each generating E-invoices then each of such devices must have its own CSID.
In order to differentiate between CSRs for different devices in a single branch you can use the field “Common Name” and “Serial Number” which are unique per device.
When invoice pertains to specific branch, then the address should be that of the branch and “Other Seller ID” should contain the any available ID of branch (like CR number or MOMRAH license number). Each taxpayer gets a single VAT Number irrespective of number of branches.
if you have received email stating “The commercial records below are not linked to the Fatoora Platform” main reason would be that you have multiple active CRs but some of those active CRs are not referred in “Other Seller ID” field of invoices you have shared. If some branches with active CRs do not issue invoices, then you just need to reply to email stating the facts that so and so branches do not issue invoices.
In terms of the CSR generation, if we have Company A , and Branch 1; and both of these entities has its own unique CSR:
a) For onboarding Company A,
CommonName:(Unique)
SerialNumber (Unique)
OrganizationIdentifier: Single VAT Number
OrganizationName Company A
OrganizationUnitName Company A
Location: Company A’s location
Industry:Company A’s Industry
b)a) For onboarding Branch 1,
CommonName:(Unique)
SerialNumber (Unique)
OrganizationIdentifier: Single VAT Number
OrganizationName Company A
OrganizationUnitName Branch 1
Location: Branch 1’s location
Industry: Branch 1’s Industry
Thank you again @Ankit_Tiwari , my last follow-up on this thread:
For a VAT Group, assuming we have the Group Representative Member and a VAT Group Member. Both of them have their own unique CSR.
For onboarding the Group Representative Member;
CommonName:(Unique)
SerialNumber (Unique)
OrganizationIdentifier: Group VAT Number
OrganizationName: Group Representative Member Name
OrganizationUnitName TIN of the Group Representative Member
Location: Group Representative Member’s location
Industry: Group Representative Member’s Industry
For onboarding the VAT Group Member;
CommonName:(Unique)
SerialNumber (Unique)
OrganizationIdentifier: Group VAT Number
OrganizationName: VAT Group Member Name
OrganizationUnitName TIN of the VAT Group Member
Location: VAT Group Member’s location
Industry: VAT Group Member’s Industry
Is my understanding correct here as well? I am unsure if we use the OrganizationName = Group Representative Member Name even when doing the onboarding(CSR generation) for a VAT Group Member.
@Yatin your understanding is correct. All you need to be careful about is the VAT Number, it should always be that of the VAT Group (in CSR and also on the invoices). Name, Addresses, Other Seller ID can be that of the individual members of VAT Group.