Docoon Invoice Terms of Use

1. DEFINITIONS

“Third-Party Archiving” refers to the archiving service subscribed to by the Licensee, under which the third-party archiver retains the Organization’s Electronic Documents and Electronic Invoices for a period of ten (10) years, unless the contractual relationship between the Parties is terminated early.

“Anomalies” means any technical anomaly or malfunction that prevents the use of the Solution’s features and/or Services.

“Organization Account” means the account created by the Licensee that allows the Organization to access the Solution and the Services.

“Terms of Use” or “TOU” refers to this document and Appendix 1.

“Content” means the content made available through the Solution, including, but not limited to, data, databases, software, source code, offers, text, photos, audio tracks, logos, and design, excluding Data.

“Licensee” means the company from which the Organization has purchased the offering that provides access to the Solution and the Services.

“Recipient” means the third party to whom an Electronic Document (invoice, pay stub, etc.) is sent and who is not a party to the contractual relationship between the Parties.

“Electronic document” means any electronic file, including invoices, pay stubs, contracts, and leases in PDF, XML, or other formats, to which an electronic signature is attached that guarantees its authenticity and integrity within the meaning of Article 289, Section VII, Paragraph 2 of the General Tax Code.

“Data” refers to pay stubs, contracts, electronic invoices, and other supporting documents.

“Electronic invoice” means any electronic file in PDF, XML, Factur-x, CII, or UBL format that is accompanied by an electronic signature guaranteeing its authenticity and integrity, as defined in Article 289, Section VII, Paragraph 2 of the General Tax Code.

“E-invoicing flow” or “electronic invoicing flow” refers to a supplier invoice or customer invoice that passes through the AP system.

“Format(s) and Platform(s)” refers to the structured formats recognized by applicable regulations for transmitting an e-invoicing data stream.

“Maintenance” means any maintenance work performed on the Solution and the Services.

“Authorization” refers to the authorization that must be signed by any Organization in order to use the PA Service.

“PA” refers to the approved platform that has been assigned registration number 19 and is governed by Article 242 nonies B of the General Tax Code.

“Power of Attorney” refers to the power of attorney that must be signed by any organization wishing to obtain an electronic certificate issued in its name and on its behalf.

“Software package” means a standard computer program developed for use by multiple Organizations, the technical and functional characteristics of which are defined in the Documentation.

“Service(s)” means the Service(s) described in Exhibit 1, including the offering that provides access to the PA.

“PA Service” or “Authorized Platform Service” refers specifically to the Authorized Platform Service described in Article 2 of Annex 1.

“Solution” means the solution comprising the Software Package, applications, databases, operating systems, hosting infrastructure, computer hardware, and electronic communications.

“Device” means the computer, smartphone, or tablet from which the Organization accesses the Solution and Services.

“Organization” means any legal entity authorized to access the Solution and the Services under the terms set forth in these Terms of Use.

“Party” refers, in the singular, individually to the Licensee or the Organization, and, in the plural, jointly to the Licensee and the Organization.

“User” means any individual acting on behalf of and for the account of an Organization.

2. PURPOSE

The purpose of these Terms of Use is to define the terms and conditions governing access to and use of the Solution and related Services offered by the Licensee to Organizations.

Access to and use of the Solution imply full acceptance of these Terms of Use.

These Terms of Use apply for the entire duration of the contractual relationship between the Licensee and the Organization. The deletion of the Organization Account or the termination of the contractual relationship shall result in the termination of these Terms of Use.

3. ACCESS TO THE SOLUTION AND SERVICES

3.1. Technical Requirements

The device must be connected to a Wi-Fi network or a mobile network.

In order to provide the PA Service, the Organization is required to provide the Licensee with a public address and to comply with the technical requirements detailed in Appendix 1.

3.2. Access Procedures

Access to the Solution and Services is limited to Organizations that have subscribed to the offering through the Licensee.

The Licensee will provide the Organizations with the access procedures.

The Licensee is responsible for creating and managing Organization Accounts and user credentials.

The Organization is solely responsible for the management and confidentiality of its login credentials.

4. DESCRIPTION OF SERVICES

4.1. Digitization Services

It is proposed that the Organization provide services for the digitization and transmission of electronic documents as described in Article 1 of Annex 1.

Using these Services enables the Organization to send and/or receive electronic documents, track deliveries to recipients, and manage rejected deliveries.

This service may include a third-party archiving service. In such cases, electronic documents are retained for a period of three (3) years before being returned to the Organization.

4.2. Authorized Platform Services

The Organization is being offered Authorized Platform Services in accordance with Article 242 nonies B of the French General Tax Code, as described in Article 2 of Annex 1.

5. AVAILABILITY OF SERVICES AND SUPPORT FOR USING THE SOLUTION

5.1. Except in cases of force majeure, network malfunctions, malfunctions of the tools used by the Organization, or the need to perform maintenance on the Solution and Services, the Services are available 24 hours a day, 7 days a week.

If scheduled maintenance is required, the Licensee shall provide the Organization with advance notice. As far as possible, such maintenance operations shall be performed at times unlikely to interfere with the Organizations’ use of the Solution and Services. These provisions apply only to scheduled maintenance, without prejudice to the possibility of performing or having performed emergency maintenance at any time.

5.2. Technical support for any issues encountered by an Organization in using the Solution and Services is provided by the Licensee in accordance with the procedure communicated to the Organization.

6. THE ORGANIZATION’S OBLIGATIONS

6.1. The Organization acknowledges that the Solution and the Services are intended for professional use. The Organization agrees to use the Solution and the Services in accordance with their intended purpose and strictly within the framework of and in compliance with these Terms of Use. In particular, the Organization warrants the accuracy, integrity, and authenticity of all data transmitted through the Solution.

In this context, the Organization undertakes to:
– Provide all information necessary for the proper functioning of the Services and the Solution;
– Comply with the technical requirements detailed in Appendix 1 and any other instructions communicated by the Licensee via any medium;
– Stay informed of updates to these technical requirements to account for technical, legal, and/or regulatory changes;
– Guarantee the accuracy of the information contained in the Mandate, particularly the address;
– Ensure that the invoices submitted comply with the Socles Formats;
– Ensure the correct use of expected events and statuses as described in Article 2.3(d) of Annex 1;
– Integrate, if necessary, the mandatory APIs as described in Article 2.3(c) of Annex 1.

6.2. The Organization is solely responsible for maintaining its computerized accounting records in accordance with applicable laws and regulations, as well as for retaining electronic documents, unless the Services expressly include a third-party archiving service.

6.3. In general, the Organization is hereby notified that it is required to comply with its obligations as a taxpayer under the General Tax Code. The Organization remains responsible for ensuring that the content, data, and related disclosures comply with applicable laws and regulations, as well as for fulfilling its tax obligations.

In any event, the Organization undertakes to comply with all the obligations and instructions set forth in Annex 1.

6.4. All data and information transmitted by the Organization via the Solution remain the exclusive property of the Organization.

The Organization shall indemnify the Solution Provider and the PA against any claims, actions, and/or proceedings brought by any third party arising from the content of the message and/or the information transmitted by the Organization.

6.5. The Organization agrees not to infringe upon the intellectual property rights associated with the Solution, its Content, and its architecture.

6.6. The Organization acknowledges that all transactions conducted through the Organization Account are deemed to have been carried out by the Organization.

The Organization’s use of the password constitutes authentication.

6.7. The Organization is liable for all actions taken by any User through its Organization Account. Consequently, the Organization may not rely on the fact that one of its agents committed a fault unrelated to their duties.

7. INTELLECTUAL PROPERTY

7.1. The Distributed Solution is classified as a work of the mind under the Intellectual Property Code, as are its architecture and Content. As such, they are protected by exclusive exploitation rights under copyright law.

The Solution consists of software owned by a third-party publisher, over which the publisher holds exclusive copyrights and the rights associated with such ownership.

7.2. The Organization is granted a license to use the Solution, strictly limited to the use of the Services.

This right of use is granted to the Organization on a personal, non-exclusive, non-transferable basis and is limited to the duration of the contractual relationship with the Licensee.

8. PERSONAL INFORMATION

8.1. The Organization’s use of the Solution and Services may involve the processing of Personal Data.

In this context, the Organization acts as the data controller within the meaning of European Regulation (EU) 2016/679 of April 27, 2016, on the protection of personal data (hereinafter the “GDPR”) for the Personal Data it transmits via the Solution, and the Licensee acts as a data processor for such processing.

8.2. Access to the Solution and the Services requires the Licensee to engage subcontractors.

For more information, the Organization is invited to consult the subcontract or any equivalent agreement entered into with the Licensee.

9. MISCELLANEOUS PROVISIONS

9.1. If one or more provisions of these Terms of Use are deemed invalid or declared as such pursuant to a treaty, law, or regulation, or as a result of a final decision by a competent court, the remaining provisions shall remain in full force and effect.

9.2. No act, delay in taking action, or any other conduct—whether passive or active—on the part of either Party shall be deemed to constitute a waiver by that Party of any of the rights and remedies to which it is entitled under the Terms of Service, unless such waiver is set forth in a written document signed by a duly authorized representative.

9.3. In the event of a conflict between the title of a clause and the content of that clause, the content of the clause shall prevail.

10. GOVERNING LAW

Only the French version of the Terms of Use shall be binding on the Parties and shall prevail in the event of a dispute. Translated versions are provided for informational purposes only.

These Terms of Use are governed by and construed in accordance with French laws and regulations.

In the event of a dispute regarding the formation, validity, performance, or interpretation of these Terms of Use, an attempt must be made to resolve the matter amicably.

In the absence of an amicable settlement, exclusive jurisdiction is conferred upon the Commercial Court of Paris.

APPENDIX 1 – DESCRIPTION OF THE SOLUTION AND SERVICES

Article 1. Description of Digitization Services

The purpose of this document is to provide an electronic invoice transmission service as defined in Article 289, Section VII, Paragraph 2 of the General Tax Code and Electronic Documents.

1.1. Implementation

The implementation steps are as follows:
– Signature of the Power of Attorney by the Organization;
– Calibration;
– If the Third-Party Archiving Option is selected, the Organization’s signature on the Power of Attorney authorizing the Licensee to destroy the electronic documents after the expiration of the ten (10)-year period, unless otherwise instructed or a request for return is made by the Organization prior to the expiration of the aforementioned period.

1.2. Compliance

1.2.1. The compliance of invoices created and transmitted is based on the certification policy of the electronic certification service provider. By signing the Power of Attorney, the Organization declares that it accepts the service provider’s certification policy for the electronic certificate.

In the event that the Organization has not signed the Power of Attorney for an electronic signature certificate, the service provider is designated by the Organization, provided that:
– the electronic signature system must comply with the requirements of Article 289 VII of the General Tax Code:
– the electronic signature is based on the electronic certificate issued by the electronic certification service provider. The Licensee declares that they are familiar with and accept this provider’s certification policy without reservation.

1.2.2. The service provider designated to perform electronic certification of Electronic Documents is solely responsible for the signing, transmission, and timestamping of the Data provided by the Organization and is in no way responsible for the content of Electronic Invoices and Electronic Documents (legal notices, consistency between the amounts in the readable format and the metadata fields provided, etc.) or for the accuracy of the invoice.

1.3. Timestamping

The Organization hereby declares that it has reviewed the service provider’s time-stamping policy and accepts it without reservation.

1.4. Verification of the electronic signature

The recipient of the invoice must be able to verify the authenticity and integrity of the invoice using the data contained in the certificate attached to the signature upon receipt, as well as at any time during the period specified in Article L. 102 B of the General Tax Code.

Since the Solution has no control over the Recipient, it cannot be held liable for the Recipient’s failure to verify the information.

1.5. Retention and Processing of Invoices and Supporting Documents

The invoices provided serve as the original invoices.

The Solution ensures that invoices sent electronically are stored in their original format (PDF, XML, or other) on digital media.

Retention also applies to the electronic signature associated with the invoices, as well as the electronic certificate attached to the electronic signature verification data.

The retention of electronic invoices is ensured:
– By default, through a third-party archiving service, for three (3) years;

If the Third-Party Archiving service is subscribed to, the archiving of electronic documents is designed to ensure their preservation for a period of ten (10) years. Unless otherwise expressly agreed, this Third-Party Archiving service is not provided on behalf of the Recipients.

The matter is being handled in France, in accordance with Article L 102 C, paragraph 2, of the Code of Tax Procedures.

1.6. Restitution

The Organization is required to contact the Licensee to determine the terms and conditions of the reversibility procedure.

1.7. Access

Under certain conditions, Organizations may download all stored Data.

1.8. Control

The Organization acknowledges and agrees that officials from the General Tax Directorate may have access to Data during audits conducted to verify the service’s compliance with the technical standards set forth in Article 96F-I of Annex III of the General Tax Code

1.9. Batch transmission

The Solution will be able to transmit documents in batches for the same Organization and the same Recipient.

1.10. Obligations of All Organizations

In the event of a dispute regarding the contents of the invoices, it is the Organization’s responsibility to issue a corrected invoice.

The Organization remains liable for any VAT due, where applicable, pursuant to Article 283(3) of the General Tax Code, when such VAT has been incorrectly charged.

The Organization retains full responsibility for its billing obligations and the resulting VAT implications.
In this regard, the Organization is solely responsible for:
 reporting the VAT collected;
 remitting the tax indicated on the issued invoices to the Treasury;
 immediately requesting a duplicate of the invoice if it has not been received;
 reporting any changes to the information regarding its business identification.

The Organization remains responsible for the accuracy of the information to be included on invoices, in accordance with Article 289 of the General Tax Code, without prejudice to Articles L 441-3 et seq. of the Commercial Code.

1.11. CHORUS Removal

Here is a list of the information we must provide to Chorus when submitting an invoice via API. Please note that if any information is incorrect, the invoice will be immediately rejected by the system, with no option to provide additional details.

This is the minimum information required to upload and submit an invoice.
In addition to this information, for each client, we store the supplier’s Chorus ID as well as a technical account (username and password) created by the client and provided to us for API uploads.

The total amount including tax is calculated using this formula:
Total Amount Including Tax = Total Excluding Tax After Discount + Total VAT After Discount – Total Discount Including Tax

All amounts must be provided with six decimal places.

General Information
• Invoice Number
• Invoice Date

Recipient
• Recipient's SIRET number
• Depending on the recipient, you may need to specify the recipient's department

Supplier section
• The supplier’s Chorus ID (this is the client’s organization ID in Chorus)
• (Optional) The ID of the existing service in the supplier’s account

Billing Header Section
• The header code (4 possible values: A1_SUPPLIER_INVOICE, A2_SUPPLIER_INVOICE_ALREADY_PAID, A9_SUBCONTRACTOR_INVOICE, A12_CO-CONTRACTOR_INVOICE)
• The validating entity code (required if the framework code is A9 or A12)
• The validating entity’s department code (required if the framework code is A9 or A12)

Reference section
• Currency (example: EUR)
• Invoice type (INVOICE or CREDIT NOTE)
• VAT type (4 options: VAT_ON_DEBIT, VAT_ON_CASH_RECEIPT, EXEMPTION, NO_VAT)
• Reason for exemption if the VAT type is EXEMPTION
• Contract number (the recipient may reject the invoice if this is required)
• The purchase order number (only if the recipient requires it)
• The original invoice number (only if the invoice type is CREDIT NOTE)
• The payment method (6 options: CASH, CHECK, DIRECT DEBIT, BANK TRANSFER, OTHER, DEFERRED)

VAT Summary Section: Each VAT line contains:
• Manually entered VAT rate
• Base amount excluding tax per rate (= Sum (Amount excluding tax after overall discount))
• Total VAT per VAT rate (= Sum (Amount excluding tax after overall discount) x (VAT rate / 100))

Total amount
• Total before tax after discount
• Total including tax after discount
• Total discount including tax
• Reason for total discount (if applicable)
• Total due

Article 2. Description of the Authorized Platform Service

Section 2.1. Description of the Authorized Platform Service

Définitions / Glossaire applicable à cet article :
• Licencié a le même sens que défini ci-avant.
• Mandat PA, Mandat Plateforme Agréée ou Mandat Peppol a le même sens que défini ci-avant de sorte qu’il désigne le document signé par un représentant de l’Organisation (le mandant) définissant le cadre du mandat donné à la PA (le mandataire) pour l’échange sécurisé et fiable de données. Pour les Organisations domiciliées en France, le Mandat PA fait référence à l’accord formel décrit dans l’article 289 Ter du CGI. En conséquence, le Mandat PA a pour objet l’émission et la réception des factures et de tous documents qui sont pris en charge par le réseau Peppol et/ou sont expressément listés par l’article 289 ter du Code général des impôts.
• Organisation a le même sens que défini ci-avant de sorte qu’elle désigne toute personne morale autorisée à utiliser le Service PA. Une Organisation est un Utilisateur final Peppol.
• PA a le même sens que défini ci-avant étant précisé que la Plateforme Agréée est considérée comme un Point d’Accès Peppol pour toutes les Organisations qu’elles soient domiciliées en France ou à l’étranger. Pour les Organisations domiciliées en France, la Plateforme Agréée fait référence à la définition de l’article 242 nonies B du CGI.
• Point d’Accès Peppol désigne l’entité autorisée à fournir des services Peppol.
• Réseau Peppol désigne le réseau logique permettant l’échange sécurisé et fiable de données entre Utilisateurs finaux Peppol via les Point d’Accès Peppol.
• Service PA a le même sens que celui défini ci-avant.
• Utilisateur final Peppol désigne une entité identifiée ou identifiable qui est responsable du contenu commercial des jeux de données (datasets) échangé (par envoi et/ou par réception) avec une autre entité utilisant les services Peppol sur le réseau Peppol.
Objet
1. La présente annexe a pour objet de décrire le Service PA.
Description du Service PA pour toutes les Organisations, qu’elles soient domiciliées en France ou ailleurs :
2. La PA met à disposition un service Point d’Accès Peppol pour les Organisations domiciliées dans les pays désignés par le Licencié.
3. La PA propose aux Organisations :
– une API conforme à la norme XP Z12-013 ;
– la gestion des Formats Socles à savoir UBL, CII, Factur-X ;
– les résultats des tests annuels de conformité effectués sur demande au Licencié ;
– l’archivage systématique et sécurisé du Mandat PA. Cet archivage inclut les données attestant de son intégrité (fichier de preuve à savoir OTP/horodatage) ainsi que l’Organisation à laquelle le Mandat PA est rattaché.
Description complémentaire du Service PA pour les Organisations domiciliées en France :
4. La PA met à disposition un Service PA conforme à l’article 242 nonies E décrivant les services attendus d’une PA (article 2.2 « Extrait de l’article 242 nonies E décrivant les services attendus d’une Plateforme Agréée ») ;
5. La PA fournira sur demande une preuve d’immatriculation selon l’article 242 nonies B au plus tard avant le début de la mise en place de la facturation électronique obligatoire en France et de procéder à son renouvellement selon l’article 242 nonies C ;
6. La PA conserve les données de facturation et de e-reporting de leur réception par la PA jusqu’à leur correcte émission auprès du concentrateur et de la PA réceptrice jusqu’à l’expiration de la troisième année afin de garantir le respect du II de l’article L102 B du livre des procédures fiscales. Durant ce laps de temps, la PA garantit l’authenticité de l’origine, l’intégrité du contenu et la lisibilité de ces données.
Obligations des Organisations, domiciliés en France ou ailleurs :
7. L’Organisation est informée que pour utiliser le Service de Plateforme Agréée, elle sera tenue de signer un Mandat PA. Lorsque l’Organisation est un assujetti à la TVA au sens du Code général des impôts, le Mandat PA doit être signé pour chaque entité juridique redevable de la TVA.
8. L’Organisation déclare et reconnait que :
a. L’Organisation reste entièrement responsable du contenu commercial des ensembles de données échangés, y compris de leur conformité à la législation en vigueur ainsi que tout engagement commercial qui en résulte.
b. En cas de fraude, de spam ou d’autres actes criminels constatés par ou au nom de l’Organisation, l’Organisation sera exclue du réseau Peppol.
c. Points de contacts Peppol. Adresse email désignée pour toute communication officielle adressée à
Autorité de coordination Peppol: openpeppol@peppol.eu
d. Lorsque l’Organisation est domiciliée en France, la PA propose des services complémentaires de signature électronique ou d’archivage permettant de respecter l’article 289 du code général des impôts. Si l’Organisation n’utilise pas ces offres complémentaires, l’Organisation est tenue de mettre en place un des moyens prévus au VII de l’article 289 du code général des impôts (Piste d’Audit fiable, EDI fiscal etc..). Si l’Organisation n’utilise pas la solution d’Archivage Tiers mise à disposition par la PA, l’Organisation doit s’assurer que la solution d’archivage mise en place permet de répondre au V de l’article 289 du code général des impôts jusqu’à la fin de la période de conservation.
Article 2.2. Extrait de l’article 242 nonies E décrivant les services attendus d’une Plateforme Agréée
Les opérateurs de plateformes de dématérialisation partenaires sont tenus de proposer les services suivants :
1° Permettre à leurs utilisateurs de saisir, déposer, émettre ou transmettre leurs factures électroniques dans des conditions de nature à en garantir l’authenticité de l’origine, l’intégrité du contenu et la lisibilité, ainsi que les données mentionnées aux articles 242 nonies J et 242 nonies P »
2° Effectuer les contrôles mentionnés à l’article 242 nonies K et identifier les destinataires des factures électroniques au moyen de l’annuaire central
3° Fournir et mettre à jour les informations relatives à leurs utilisateurs nécessaires au fonctionnement de l’annuaire central ;
4° Assurer la transmission des factures électroniques aux plateformes de dématérialisation partenaires choisies par leurs destinataires ou au portail public de facturation, selon les modalités d’interopérabilité définies à l’article 242 nonies I et dans des conditions de nature à en garantir l’authenticité de l’origine, l’intégrité du contenu et la lisibilité à compter de leur émission jusqu’à la fin de la période de conservation ;
5° Recevoir et mettre à disposition de leurs destinataires les factures électroniques adressées par les autres plateformes de dématérialisation partenaires ou le portail public de facturation ;
6° Assurer la gestion des statuts de traitement des factures électroniques en garantissant :
a) La mise à disposition à leurs utilisateurs des informations relatives à ces statuts ;
b) La possibilité pour leurs utilisateurs de mettre à jour les informations relatives aux statuts de traitement lorsqu’il y a lieu ;
c) La transmission des informations relatives aux statuts de traitement au portail public de facturation ainsi qu’aux plateformes de dématérialisation partenaires des parties aux transactions ;
7° Extraire les données de facturation destinées à l’administration fiscale en application des dispositions du II de l’article 289 bis du code général des impôts et en assurer la transmission au portail public de facturation dans les conditions et modalités prévues aux articles 242 nonies J à 242 nonies L ;

Section 2.3. Terms and Conditions for Access to the PA Service and the Organization of Data Flows

a. Definitions / Glossary applicable to this article

The glossary referred to in Article 2.1 above is supplemented by the following definitions:

“Flux” refers collectively to all Fluxes, that is, Fluxes 1, 2, 6, and 10.

“Flux 1” refers to the regulatory invoice data stream, in UBL or CII syntax format, generated from Flux 2.

“Flux 2” refers to the flow of electronic invoices related to domestic business-to-business (B2B) or business-to-government (B2G) transactions, in one of the structured formats (UBL, CII, Factur-X).

“Flux 6” refers to the lifecycle flow in the CDAR syntax format. The lifecycle conveys the statuses of business objects, which are necessary for all stakeholders in the billing chain to track the progress of processing.

“Flux 10” refers to the data transmission stream for transaction and payment data related to international business-to-business transactions (B2Bi, Bi2B, and Bi2Bi) or transactions with non-taxable entities (B2C).

“Format(s) Platform(s)” has the same meaning as defined above.

“PPF” refers to the Public Billing Portal.

b. Accepted invoice formats

• For Stream 2

To use the PA Service, the Organization must submit its invoices in one of the core formats recognized by the regulations in the XP Z12-012 standard.

Invoices must also comply with the profiles applicable to these formats: EN16931, EN16931 EXTENDED-CTC-FR, or BASICWL. BASICWL is a profile specific to Factur-X and is scheduled to remain in effect until September 2027, subject to regulatory changes.

The Organization may provide an invoice in a structured JSON format, subject to prior contractual agreement and the completeness of the required regulatory data. This JSON format allows for the compliant extraction of the data needed to create a Flux 2.

• For Flow 6
Life cycle statuses are managed according to the format and principles associated with the life cycle flow and are defined in the XP Z12-012 standard using the CDAR format.

• For Flux 10
: The Organization must submit invoices in accordance with the format and principles defined in the XP Z12-013 standard under the name FRR.

When the subscribed scope allows for it and if the required regulatory data is available:
– Invoices in Flow 2 can be converted to Flow 10.1, which corresponds to international B2B transaction flows;
– If the applicable threshold is less than 1,000 invoices per month per SIREN, Flow 2 invoices can be converted to Flow 10.3, which corresponds to B2C transaction flows. For example, the required regulatory data excludes cases involving VAT on the margin.

• Data feeds not in Socles formats
Only data feeds submitted in one of the Socles formats (which excludes simple, unstructured PDFs) and containing all the required regulatory data are accepted by the PA Service. Any invoice submitted that does not meet these requirements is automatically rejected.

To verify the format and profile of the transmitted data stream, compliance checks are performed whenever an invoice is submitted. If the invoice is rejected, it must be resubmitted after the compliance issues have been corrected.

c. API integration

Depending on the terms of access to the PA, the obligations listed below apply to Organizations, specifically when the PA Service and the Solution are integrated into the Organization’s business software.

The APIs provided by the PA implement the standardized Flow API in accordance with the requirements of the XP Z12-013 standard.

Additional endpoints, not described in XP Z12-013, may be exposed by the PA to facilitate integration and provide additional functionality. These endpoints are optional and do not affect the compliance of standardized routes.

When required by the terms of access to the PA, the mandatory integration of APIs allows you to:
– Deploy the PA Solution and Service,
– Submit a Flow 2, Flow 6, or Flow 10,
– Search for Flow 2, Flow 6, or Flow 10,
– Retrieve a Flow 2, Flow 6, or Flow 10,
– Integrate the Flows into the Organization’s business application.

To integrate these feeds into its application, the organization will have access to technical support and technical documentation.

The Organization remains solely responsible for the proper implementation, configuration, and correct use of API calls. Consequently, the Organization is solely liable for any failures, transmission errors, data flow anomalies, or service outages resulting from incorrect, incomplete, or non-compliant implementation.

d. Obligation to report to the authorities

• Flow 1
For e-invoicing flows, the PA transmits the data required by the tax authorities to the PPF in the form of Flow 1. This flow is generated from Flow 2. The Organization is solely responsible for the accuracy and reliability of the source data.

• Workflow 6
The diagram below summarizes the lifecycle of an invoice.