Less manual work. More time for your business. 7-day free trial
NAP Ready
7-day free trialLogin to the platform
XML and reporting

Invalid VPOS ID in Stripe VAT number XML file

NAP Ready7 min reading
Invalid VPOS ID in XML file
In this post

When checking XML audit files in the NAP Ready validator, we increasingly find the same serious problem:

Invalid VPOS ID

PROC_ID contains Stripe's VAT number.
An immediate revision of Appendix 33 of Ordinance N-18 is required.

This error not a simple technical glitch in the format of the XML file. In most cases, it shows that incorrect information about the virtual POS terminal used was submitted during the registration of the electronic store in the National Revenue Agency.

Instead of the individual identifier associated with the particular merchant, the Stripe VAT number is entered as the virtual POS number.

This is incorrect.

The VAT number identifies Stripe for tax purposes. It does not identify the virtual POS terminal of the particular online store and is not unique to the individual merchant.

What is VPOS ID

When using absentee payments with credit or debit cards, the online merchant must submit to the National Revenue Agency information on the method of payment and the payment service provider used.

According to the information of the NRA, persons who accept absentee card payments submit data on the payment service provider, the virtual POS, payment accounts and other circumstances specified in Appendix No. 33 to Ordinance N-18.

The VPOS ID must allow the specific payment solution to be associated with the specific merchant.

It must not represent:

  • Stripe's VAT number;
  • Stripe's generic company identifier;
  • public number used by multiple stores;
  • random value copied from someone else's publication;
  • the same number for all merchants using Stripe.

The identifier must be determined according to the individual configuration and contractual relationship of the particular merchant with the payment service provider.

Why Stripe's VAT number is not a VPOS ID

The Stripe VAT number is an identifier of the company Stripe itself. It can be seen in invoices, documents, terms and conditions or other company information.

However, this does not make it a virtual POS terminal number.

If 100 different online shops use the same VAT number in the VPOS field, they all practically declare the same identification value for their card payments.

From a data perspective, this creates an obvious problem.

When the information from the audit XML files is subsequently matched with the information submitted via Schedule 33, the same identifier can be found across multiple independent traders.

The NAP Ready Validator already found over 100 stores using the same similar value. This in itself is a clear signal that the number entered cannot be a unique identifier of the virtual POS of the particular store.

What problem can arise during an inspection by the NRA

The XML audit file contains data about sales, payments and payment methods used. The PROC_ID field is used to identify the processor or virtual POS through which the corresponding payment was processed.

When a common value used by multiple merchants is entered in this field, a discrepancy is created between:

  • the specific online store;
  • the declared information in Appendix 33;
  • the payment account actually used;
  • the entries in the XML audit file;
  • the data that can be provided by the payment operator.

If a lookup or match is performed on the Virtual POS ID, the same number can be found in the XML files of a large number of different stores.

This does not necessarily mean that all sales will automatically be counted as a merchant's turnover. Such a statement would be too categorical without information about the specific way in which the NRA processes and collates the data, but it is certain that there will be serious consequences

However, there will certainly be serious ambiguity as to which merchant is behind the respective payments. This may lead to additional checks, the requirement of documents, explanations and the establishment of incorrectly submitted information and most often leads to a full audit (tax and accounting), which will create many headaches.

The NRA explicitly states that the information under Appendix 33 is submitted separately for each electronic store.

Therefore, the use of a common VAT number instead of an individual identifier contradicts the very logic of the submitted data.

The problem is not only in the XML file

When the validator displays:

PROC_ID contains Stripe's VAT number

the first reaction is often to look for a way to manually modify the XML file, but this is not enough!

The XML file shows the information that is configured in the merchant's system. If an incorrect VPOS identifier is submitted in Appendix 33, the problem starts with the store's registration with the National Revenue Agency.

At least three locations need to be checked and agreed upon:

  • The data submitted via Annex 33.
  • The settings of the integration or software that generates the XML file.
  • The PROC_ID value recorded for each card payment.

The three values ​​must correspond to the same actual payment configuration.

Manual replacement in just one XML file does not solve the cause of the error. On next generation, the incorrect value may be written again.

What you should do

If the NAP Ready validator detects an invalid VPOS ID, do not delay the verification.

1. Check the submitted Annex 33

  • Log in to the NRA portal and review the information submitted for the specific e-store.
  • Check the field where the virtual POS number or ID is listed.
  • If a Stripe VAT number is entered there, the information must be corrected.

2. Establish the correct individual value

  • Do not copy value from another online store, account group, forum or random post.
  • Use the data related to your specific Stripe account and how payments are processed for your business.
  • C our detailed guide "Completing Appendix 33 of Ordinance N-18" we've outlined the steps and information that must be submitted when using Stripe and other payment methods.

3. Submit a correction to the National Revenue Agency

  • When you find that the information is incorrect, you must update the e-store registration.
  • Do not expect that adjusting the settings on the site or in the XML generator will automatically change the data already submitted to the NRA.

4. Correct the software settings

  • After updating Appendix 33, check what value the integration uses when populating PROC_ID.
  • It must match the correct ID submitted for your store.

5. Generate a new XML file and verify it

  • After the changes are made, create a new test XML audit file and re-upload it to the free NAP Ready validator.
  • The validator performs not only a check against the structure of the XML and the XSD schema, but also additional logical checks on the values.

Why the unique VPOS ID is so important

The main purpose of the identifier is traceability. From the data it should be clearly established:

  • which merchant received the payment;
  • through which payment provider it was processed;
  • which individual payment configuration it belongs to;
  • which sale and e-shop it refers to.

When multiple stores use the same common number, this traceability is broken.

Stripe's VAT number can correctly identify Stripe as a company, but it cannot distinguish your store from all other Stripe customers. That is why it should not be used as an individual VPOS identifier in PROC_ID.

Check the XML file before it is submitted to the NRA

The worst time to find such an error is after starting a check.

NAP Ready's free validator allows you to check the XML audit file beforehand and find problems that might not be visible when simply opening the file.

If you get a warning about an invalid VPOS ID, take it seriously.

Do not change only the text in the XML file and do not enter any other random number. Check the source of the information, correct Appendix 33 and synchronize the settings of the software used.

The correct VPOS ID must refer to your specific merchant and not to Stripe as an international payment service provider.

It is a small field of great importance. An incorrectly entered value may cast doubt on the relationship between the store, reported sales, and received card payments.

PUBLISHED BY NAP READY

The materials are part of the online store resource library. For a question about a specific NAP Ready setup, you can contact the team.

Ask the team
Cookie settings

Choose which categories to allow. You can change your preferences using the link in the footer.

Privacy Policy