Frequently asked questions.

General

​Yes, our API allows you to process invoices from various sources, including traditional Electronic Data Interchange (EDI) systems. We offer a one-stop e-invoicing solution that supports eReporting (CTC) for many countries and eInvoicing through networks like Peppol, DBNAlliance, legacy EDI networks, or email. ​

By integrating with our RESTful API, you can connect your financial system to multiple e-invoicing networks and tax authorities, enabling the sending and receiving of compliant e-invoices globally. ​This integration ensures that your system can handle invoices from various sources, including EDI, by converting them into the appropriate formats required by different regions and compliance standards.

If you are unable to integrate the API yourself, we can help you find a suitable Storecove integrator. You can see a list of our integrators on our website, or you can contact us to ask assistance with forwarding you to an integration partner. 

The specifications per country are listed here.

You can reset your password here. After submitting your e-mail address, you will receive an email to reset your password.

To determine if an invoice was not sent and to identify the cause of the issue using Storecove's API, you can utilize the following methods:​

1. Retrieve Submission Status: After submitting an invoice, Storecove provides a unique guid for the submission. You can use this guid to check the status of the invoice submission.

  • API Call: Make a GET request to the following endpoint, replacing GUID_HERE with your actual guid: api.storecove.com/api/v2/document_submissions/GUID_HERE
  • Response: The response will include details about the submission status. If the invoice was not sent successfully, the status will indicate the failure, and an errors array will provide specific error messages explaining what went wrong.​

2. Configure Webhooks: Storecove supports webhooks to notify you about various events, including the success or failure of invoice submissions. By setting up webhooks, you can receive real-time updates on the status of your invoices.

  • Setup: Define a webhook URL in your application where Storecove can send POST requests with event information. Ensure your endpoint can handle these requests and process the data accordingly.​
  • Event Handling: Upon an invoice submission failure, Storecove will send a payload to your webhook URL containing details about the error, allowing you to take appropriate action.​

3. Monitor the Storecove Dashboard: You can also monitor the status of your invoice submissions through the Storecove user interface.

  • Access: Log in to your Storecove account and navigate to the "Invoice Submissions" section.​
  • Status Tracking: This section provides a list of your submitted invoices along with their current statuses. You can view details of any failed submissions to understand the reasons for failure.​

By implementing these methods, you can effectively track the status of your invoice submissions and promptly address any issues that may arise.

Storecove supports a wide range of global e-invoice formats. By connecting through a single data format, such as JSON or UBL, Storecove automatically converts your source data into the appropriate local syntax required by the recipient's country. ​

Some of the specific e-invoice formats supported include:

  • ANSI X12 810 – Used in the United States for electronic invoicing via EDI.
  • CII (Cross-Industry Invoice) – A UN/CEFACT XML schema for electronic invoices, used in France.
  • EHF (Elektronisk Handelsformat) – The standard electronic invoicing format in Norway.
  • FacturaE – The mandatory electronic invoicing format in Spain.
  • Factur-X – A hybrid e-invoice format combining XML data and PDF, used in France.
  • FatturaPA – The required electronic invoicing format for public administrations in Italy.
  • Finvoice 3.0 – Used in Finland for structured invoicing.
  • InvoiceNow – The e-invoicing format used in Singapore.
  • ISO 20022 – A standardized format used in Switzerland, ensuring QR-bill compliance with banking standards.
  • ISDOC – The electronic invoicing format used in the Czech Republic.
  • NemHandel/OIOUBL – The electronic invoicing standard in Denmark.
  • Peppol BIS Billing 3.0 – A widely adopted standard across Europe and internationally for e-invoicing.
  • Svefaktura – The e-invoicing standard used in Sweden.
  • TEAPPSXML 3.0 – Another structured electronic invoicing format used in Finland.
  • UBL (Universal Business Language) – A common XML standard for business documents, including invoices, used in multiple countries.
  • UBL BIS V3 - Compliant with the European standard EN 16931 and utilized within the Peppol network for electronic invoicing.
  • XRechnung – A standardized XML-based format for e-invoicing in Germany.
  • ZUGFeRD – A hybrid e-invoice format combining structured XML data with human-readable PDFs, used in Germany.

This extensive format support ensures that businesses can send and receive e-invoices globally without worrying about regional format incompatibilities. ​

Storecove supports a wide range of countries for e-invoicing and e-reporting. Below is the full list of currently supported countries.

For insights into upcoming developments and future expansions, download our Roadmap 2025

  • Australia
  • Austria​
  • Belgium​
  • Canada​
  • Denmark​
  • Finland​
  • France​
  • Germany​
  • Iceland
  • India​
  • Ireland​
  • Italy​
  • Japan​
  • Latvia​
  • Lithuania​
  • Luxembourg​
  • Malaysia​
  • Malta​
  • Netherlands​
  • New Zealand​
  • Norway​
  • Poland​
  • Portugal
  • Romania​
  • Singapore​
  • Spain
  • Sweden​
  • Switzerland​
  • United Kingdom
  • United States

Our e-invoicing solution supports integration with several e-invoicing networks, including:​

Additionally, we enable connectivity to legacy EDI networks and supports e-invoicing via email.

​Yes, you can test the Storecove RESTful API before entering into a formal agreement by following these steps:​

  1. Request a Test Account: Contact us to request a test account.
  2. Create an API Key: After setting up your test account, generate an API key through the Storecove admin panel. This key is necessary for authenticating your API requests. ​
  3. Start Testing in Sandbox Mode: Utilize the sandbox environment to test the API's functionalities without affecting live data. This allows you to simulate real-world scenarios and ensure compatibility with your systems. ​
  4. Review API Documentation: Familiarize yourself with our API documentation to understand the available endpoints and their functionalities. ​
  5. Transition to Production: Once you are satisfied with the testing phase and decide to proceed, your production account will be activated upon receipt of the signed contract. ​

Technical

To create legal entities in the Storecove user interface (UI), follow these steps:

  1. Navigate to the Senders page in your Storecove account.​
  2. Click on the option to add or create a new legal entity.​
  3. Enter the necessary details for the legal entity, including Company Name (the official name of your organization), Country (select the country where your entity is registered), Participant Identifiers (add relevant identifiers such as VAT numbers or other national registration numbers). The UI will guide you on which identifiers are required based on the selected country.
  4. After entering all required information, submit the legal entity for approval (approval may take up to one day.).
  5. Once approved, a unique legalEntityId will be assigned to your entity.​ This ID is essential for subsequent API interactions, such as sending invoices.​

For more detailed information, we recommend you to read our API Documentation.

​Yes, if your Legal Entity is still under validation, it can affect your testing. After creating a Legal Entity, it can take up to a day for Storecove to approve it. During this approval period, certain functionalities, such as sending invoices, may not be fully operational. It's recommended to wait for the approval to complete before proceeding with testing that involves the Legal Entity.

​The error message "missing required identifier, must have MY:EIF" indicates that your invoice submission is missing a mandatory identifier specific to Malaysia. In the context of Malaysian e-invoicing, "MY:EIF" refers to the required Entity Identification Framework. This identifier is essential for the proper processing and validation of e-invoices within Malaysia's tax and regulatory systems.

Possible Causes and Solutions:

  • Missing or Incorrect Supplier Identifier: The invoice lacks the supplier’s Entity Identification Framework (EIF) number or it's incorrect. Include the correct supplier EIF number in the invoice.
  • Missing or Incorrect Buyer Identifier: The buyer’s EIF number is missing or incorrectly entered. Verify and correctly format the buyer’s EIF number.
  • Formatting Issues: The EIF number does not meet Malaysia’s required format. Ensure the EIF number follows Malaysia’s formatting standards.

By addressing the missing or incorrect "MY:EIF" identifier, you can resolve the error and ensure successful invoice submissions within Malaysia's e-invoicing framework.

If you require further assistance, please contact us here

Peppol

To connect to the Peppol network using our services, follow these steps:

  1. Request a test account: Contact us to request a test account.
  2. Register Your Legal Entity: Navigate to the 'Senders' section in your dashboard. Enter your company's details, including name, address, and country. Provide relevant public identifiers, such as VAT or Chamber of Commerce numbers. Then, submit the information for validation; approval typically takes up to one day.
  3. Integrate Your System: Use our RESTful JSON API to connect your ERP or financial system to the Peppol network. Follow our API documentation to configure endpoints, authentication, and data formats.
  4. Send and Receive E-Invoices: Once integrated, send e-invoices by submitting them through the API. We manage routing and delivery via the Peppol network. To receive e-invoices, ensure your Peppol ID is registered and active; incoming invoices will be processed and delivered to your system.

For detailed guidance, refer to our API documentation and support resources.

We enable you to send and receive a variety of electronic documents through the Peppol network, including:

  • Invoices: Standardized electronic invoices compliant with Peppol BIS Billing 3.0.​
  • Credit Notes: Documents issued to correct or adjust previously sent invoices.​
  • Orders: Electronic purchase orders facilitating procurement processes.​
  • Order Responses: Confirmations or updates regarding received orders.​
  • Message Level Responses: Acknowledgments confirming the receipt and processing status of exchanged documents.

Contact us for more information or if you require further Peppol assistance. 

Germany

Examples per country can be found here. Here you can choose the correct JSON that belongs to the country of your Legal entity.

Storecove supports the following e-invoice formats in Germany: 

  • UBL BIS V3 - Compliant with the European standard EN 16931 and utilized within the Peppol network for electronic invoicing.
  • XRechnung – The official XML-based e-invoicing format mandated for B2G (business-to-government) transactions in Germany.
  • ZUGFeRD – A hybrid format combining structured XML data with a human-readable PDF, commonly used in B2B (business-to-business) and B2G transactions.

These formats ensure compliance with German e-invoicing regulations and facilitate interoperability across different business sectors. 

You can process incoming invoices via the API, ZugFerd, UBL and Xrechnung

Poland

Yes, if you want to start receiving e-invoices in Poland as a Polish company, you must first complete the onboarding process. This includes registering with KSeF (Krajowy System e-Faktur) to allow Storecove to receive invoices on your behalf. 

For more details or assistance with the registration process, please contact us.

Romania

Our API facilitates the submission of e-invoices to Romania's National Agency for Fiscal Administration (ANAF) through the RO e-Factura system. Here's how the process works:​

  1. Integration with our API: Connect your ERP or financial system to our RESTful JSON API. This integration enables the transmission of e-invoices to the RO e-Factura platform, ensuring compliance with Romanian regulations. ​
  2. Invoice Preparation: Format your invoices in XML, adhering to Romania's RO_CIUS guidelines, which are compliant with the European standard EN 16931.
  3. Submission via our API: Once integrated, our API manages the delivery of your e-invoices to ANAF, ensuring they meet all necessary validation and compliance requirements. ​

You can also find more information about sending in Romania here or in our Technical Factsheet.

Singapore

The registration for this Peppol ID is managed by one of our customers. The business owner can request deregistration directly by contacting them, providing their UEN, and requesting removal from the Peppol Network.

United States

​To connect to the DBNAlliance its open exchange network using our services, follow these steps:​

  1. Request a Test Account: Visit our DBNAlliance integration page and request a test account to begin integration.
  2. Obtain an API Key: After setting up your test account, generate an API key through our admin panel. This key is necessary for authenticating your API requests.​
  3. Review API Documentation:Familiarize yourself with our API documentation to understand the available endpoints and their functionalities.​
  4. Develop and Test Your Integration: Implement the API endpoints in your application and conduct thorough testing to ensure proper functionality.​
  5. Transition to Production: Once testing is complete and your integration is functioning correctly, contact our support team to convert your account to 'production' API keys, allowing for live operations.​

Belgium

Starting January 1, 2026, all Belgian VAT-registered businesses must issue and receive structured electronic invoices for B2B transactions. This mandate does not apply to B2C transactions but requires businesses to be capable of receiving e-invoices from suppliers.

Belgium utilizes the Peppol (Pan-European Public Procurement Online) network for e-invoicing, ensuring secure and standardized electronic document exchanges. 

As a certified PEPPOL Access Point, we can help with integrating your ERP or financial system with the PEPPOL network.

​Yes. As of March 1, 2024, Belgium mandated the use of electronic invoicing via the Peppol network for Business-to-Government (B2G) transactions. This requirement ensures that businesses supplying goods or services to government entities must issue invoices electronically through the Peppol system.​

Starting from January 1, 2026, Belgium will mandate the use of structured electronic invoices for nearly all business-to-business (B2B) transactions between VAT-registered companies. The Pan-European Public Procurement Online (Peppol) network, utilizing the Peppol-BIS format, will serve as the default standard for exchanging these electronic invoices.

As a certified PEPPOL Access Point, we can help with integrating your ERP or financial system with the PEPPOL network. Contact us for more information or request a test account

Italy

To connect to Italy's Sistema di Interscambio (SDI) for electronic invoicing using our services, follow these steps:

  1. Create a Storecove Account: Request a test account to access our e-invoicing services.
  2. Register Your Legal Entity: Navigate to the 'Senders' section in your Storecove dashboard, and enter your company details, including name, address, and country. Provide relevant public identifiers, such as VAT or Chamber of Commerce numbers. Submit the information for validation (approval typically takes up to one day).
  3. Integrate with Storecove’s API: Use Storecove’s RESTful JSON API to connect your ERP or financial system to SDI. Follow our API documentation to configure endpoints, authentication, and data formats. We will handle format conversions, ensuring compliance with Italian e-invoicing standards.
  4. Send and Receive E-Invoices via SDI: Once integrated, send e-invoices through Storecove’s API, after which we will manage routing and delivery via SDI. To receive e-invoices, ensure your SDI credentials are registered and active; incoming invoices will be processed and delivered to your system.

For more details, refer to our API documentation or contact support for assistance.