factpulse 3.0.1 → 3.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 620d009c83aa73e0bc26b9eadb4dd66b2c775e9b1a910e41848a9dd84a9213a5
-  data.tar.gz: 55d217c5531c5d1dbdfa92a070efcb29e19ae8db16631c82076ec0857e24c96f
+  metadata.gz: 65c1cffbd2a4bad195565f89a351948891d7a21ba9285c79ec82a4f473c81c62
+  data.tar.gz: a5b525f26223adfe3fb6b724de189b79b8c876a1cd73bc89ec76d056166a94ea
 SHA512:
-  metadata.gz: 1ac95032f68ecc518e353975ba9141aad14ed10c98dc27bf7948ff6a4d33f601d041c85f791c2f06385d2be47c7d5142cc9fa6462335a81e364619acb9cade5b
-  data.tar.gz: d0dcf2e7adc27b7083c14747c347109e65ebb5c2ff6fa41aa6bc5fa861569792c459a64bacadd8cee81f736d1e80a74a516b7f54877e6728cdc49de1be2451a4
+  metadata.gz: 36e9f3719236e58672f688bb8b3c20ffe3836f128eb215913b34549e634c55e49b81f8a92ed4455572a47127fec6aad61def2053d89d2b9a1608abb00619bafd
+  data.tar.gz: 1ba42040938fb701a9c0e728f1d12d9e00cc004212d88da7fce86d5c151be0ba463d365e1f9d843bad6cba0e0626cbb0755b01e7bf767c4e859f252ac9c8181e

data/CHANGELOG.md

@@ -7,7 +7,7 @@ et ce projet adhère au [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
 
 ## [Unreleased]
 
-## [3.0.1] - 2025-12-19
+## [3.0.3] - 2025-12-19
 
 ### Added
 - Version initiale du SDK ruby
@@ -24,5 +24,5 @@ et ce projet adhère au [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
 - Guide d'authentification JWT
 - Configuration avancée (timeout, proxy, debug)
 
-[Unreleased]: https://github.com/factpulse/sdk-ruby/compare/v3.0.1...HEAD
-[3.0.1]: https://github.com/factpulse/sdk-ruby/releases/tag/v3.0.1
+[Unreleased]: https://github.com/factpulse/sdk-ruby/compare/v3.0.3...HEAD
+[3.0.3]: https://github.com/factpulse/sdk-ruby/releases/tag/v3.0.3

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    factpulse (3.0.1)
+    factpulse (3.0.3)
       typhoeus (~> 1.0, >= 1.0.1)
 
 GEM

data/docs/{TaskStatus.md → AsyncTaskStatus.md}

@@ -1,4 +1,4 @@
-# FactPulse::TaskStatus
+# FactPulse::AsyncTaskStatus
 
 ## Properties
 
@@ -13,7 +13,7 @@
 ```ruby
 require 'factpulse'
 
-instance = FactPulse::TaskStatus.new(
+instance = FactPulse::AsyncTaskStatus.new(
   task_id: null,
   status: null,
   result: null

data/docs/ChorusProApi.md

@@ -732,7 +732,7 @@ FactPulse.configure do |config|
 end
 
 api_instance = FactPulse::ChorusProApi.new
-submit_invoice_request = FactPulse::SubmitInvoiceRequest.new({invoice_number: 'invoice_number_example', invoice_date: 'invoice_date_example', structure_id: 37, total_net_amount: FactPulse::TotalNetAmount.new, vat_amount: FactPulse::VatAmount.new, total_gross_amount: FactPulse::TotalGrossAmount.new}) # SubmitInvoiceRequest | 
+submit_invoice_request = FactPulse::SubmitInvoiceRequest.new({invoice_number: 'invoice_number_example', invoice_date: 'invoice_date_example', structure_id: 37, total_net_amount: FactPulse::SubmitNetAmount.new, vat_amount: FactPulse::SubmitVatAmount.new, total_gross_amount: FactPulse::SubmitGrossAmount.new}) # SubmitInvoiceRequest | 
 
 begin
   # Submit an invoice to Chorus Pro

data/docs/InvoiceProcessingApi.md

@@ -167,7 +167,7 @@ end
 
 ## get_task_status_api_v1_processing_tasks_task_id_status_get
 
-> <TaskStatus> get_task_status_api_v1_processing_tasks_task_id_status_get(task_id)
+> <AsyncTaskStatus> get_task_status_api_v1_processing_tasks_task_id_status_get(task_id)
 
 Get task generation status
 
@@ -200,7 +200,7 @@ end
 
 This returns an Array which contains the response data, status code and headers.
 
-> <Array(<TaskStatus>, Integer, Hash)> get_task_status_api_v1_processing_tasks_task_id_status_get_with_http_info(task_id)
+> <Array(<AsyncTaskStatus>, Integer, Hash)> get_task_status_api_v1_processing_tasks_task_id_status_get_with_http_info(task_id)
 
 ```ruby
 begin
@@ -208,7 +208,7 @@ begin
   data, status_code, headers = api_instance.get_task_status_api_v1_processing_tasks_task_id_status_get_with_http_info(task_id)
   p status_code # => 2xx
   p headers # => { ... }
-  p data # => <TaskStatus>
+  p data # => <AsyncTaskStatus>
 rescue FactPulse::ApiError => e
   puts "Error when calling InvoiceProcessingApi->get_task_status_api_v1_processing_tasks_task_id_status_get_with_http_info: #{e}"
 end
@@ -222,7 +222,7 @@ end
 
 ### Return type
 
-[**TaskStatus**](TaskStatus.md)
+[**AsyncTaskStatus**](AsyncTaskStatus.md)
 
 ### Authorization
 

data/docs/PDFXMLVerificationApi.md

@@ -14,7 +14,7 @@ All URIs are relative to *http://localhost*
 
 ## get_verification_status_api_v1_verification_verify_async_task_id_status_get
 
-> <TaskStatus> get_verification_status_api_v1_verification_verify_async_task_id_status_get(task_id)
+> <AsyncTaskStatus> get_verification_status_api_v1_verification_verify_async_task_id_status_get(task_id)
 
 Get status of an asynchronous verification
 
@@ -47,7 +47,7 @@ end
 
 This returns an Array which contains the response data, status code and headers.
 
-> <Array(<TaskStatus>, Integer, Hash)> get_verification_status_api_v1_verification_verify_async_task_id_status_get_with_http_info(task_id)
+> <Array(<AsyncTaskStatus>, Integer, Hash)> get_verification_status_api_v1_verification_verify_async_task_id_status_get_with_http_info(task_id)
 
 ```ruby
 begin
@@ -55,7 +55,7 @@ begin
   data, status_code, headers = api_instance.get_verification_status_api_v1_verification_verify_async_task_id_status_get_with_http_info(task_id)
   p status_code # => 2xx
   p headers # => { ... }
-  p data # => <TaskStatus>
+  p data # => <AsyncTaskStatus>
 rescue FactPulse::ApiError => e
   puts "Error when calling PDFXMLVerificationApi->get_verification_status_api_v1_verification_verify_async_task_id_status_get_with_http_info: #{e}"
 end
@@ -69,7 +69,7 @@ end
 
 ### Return type
 
-[**TaskStatus**](TaskStatus.md)
+[**AsyncTaskStatus**](AsyncTaskStatus.md)
 
 ### Authorization
 
@@ -83,7 +83,7 @@ end
 
 ## get_verification_status_api_v1_verification_verify_async_task_id_status_get_0
 
-> <TaskStatus> get_verification_status_api_v1_verification_verify_async_task_id_status_get_0(task_id)
+> <AsyncTaskStatus> get_verification_status_api_v1_verification_verify_async_task_id_status_get_0(task_id)
 
 Get status of an asynchronous verification
 
@@ -116,7 +116,7 @@ end
 
 This returns an Array which contains the response data, status code and headers.
 
-> <Array(<TaskStatus>, Integer, Hash)> get_verification_status_api_v1_verification_verify_async_task_id_status_get_0_with_http_info(task_id)
+> <Array(<AsyncTaskStatus>, Integer, Hash)> get_verification_status_api_v1_verification_verify_async_task_id_status_get_0_with_http_info(task_id)
 
 ```ruby
 begin
@@ -124,7 +124,7 @@ begin
   data, status_code, headers = api_instance.get_verification_status_api_v1_verification_verify_async_task_id_status_get_0_with_http_info(task_id)
   p status_code # => 2xx
   p headers # => { ... }
-  p data # => <TaskStatus>
+  p data # => <AsyncTaskStatus>
 rescue FactPulse::ApiError => e
   puts "Error when calling PDFXMLVerificationApi->get_verification_status_api_v1_verification_verify_async_task_id_status_get_0_with_http_info: #{e}"
 end
@@ -138,7 +138,7 @@ end
 
 ### Return type
 
-[**TaskStatus**](TaskStatus.md)
+[**AsyncTaskStatus**](AsyncTaskStatus.md)
 
 ### Authorization
 

data/docs/SubmitGrossAmount.md

@@ -0,0 +1,15 @@
+# FactPulse::SubmitGrossAmount
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+
+## Example
+
+```ruby
+require 'factpulse'
+
+instance = FactPulse::SubmitGrossAmount.new()
+```
+

data/docs/SubmitInvoiceRequest.md

@@ -11,9 +11,9 @@
 | **structure_id** | **Integer** | Chorus Pro recipient structure ID |  |
 | **service_code** | **String** |  | [optional] |
 | **engagement_number** | **String** |  | [optional] |
-| **total_net_amount** | [**TotalNetAmount**](TotalNetAmount.md) |  |  |
-| **vat_amount** | [**VatAmount**](VatAmount.md) |  |  |
-| **total_gross_amount** | [**TotalGrossAmount**](TotalGrossAmount.md) |  |  |
+| **total_net_amount** | [**SubmitNetAmount**](SubmitNetAmount.md) |  |  |
+| **vat_amount** | [**SubmitVatAmount**](SubmitVatAmount.md) |  |  |
+| **total_gross_amount** | [**SubmitGrossAmount**](SubmitGrossAmount.md) |  |  |
 | **main_attachment_id** | **Integer** |  | [optional] |
 | **main_attachment_label** | **String** |  | [optional] |
 | **comment** | **String** |  | [optional] |

data/docs/{VatAmount.md → SubmitNetAmount.md}

@@ -1,4 +1,4 @@
-# FactPulse::VatAmount
+# FactPulse::SubmitNetAmount
 
 ## Properties
 
@@ -10,6 +10,6 @@
 ```ruby
 require 'factpulse'
 
-instance = FactPulse::VatAmount.new()
+instance = FactPulse::SubmitNetAmount.new()
 ```
 

data/docs/SubmitVatAmount.md

@@ -0,0 +1,15 @@
+# FactPulse::SubmitVatAmount
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+
+## Example
+
+```ruby
+require 'factpulse'
+
+instance = FactPulse::SubmitVatAmount.new()
+```
+

data/lib/factpulse/api/invoice_processing_api.rb

@@ -172,7 +172,7 @@ module FactPulse
     # Retrieves the progress status of an invoice generation task.  ## Possible states  The `status` field uses the `CeleryStatus` enum with values: - **PENDING, STARTED, SUCCESS, FAILURE, RETRY**  See the `CeleryStatus` schema documentation for details.  ## Business result  When `status=\"SUCCESS\"`, the `result` field contains: - `status`: \"SUCCESS\" or \"ERROR\" (business result) - `content_b64`: Base64 encoded content (if success) - `errorCode`, `errorMessage`, `details`: AFNOR format (if business error)  ## Usage  Poll this endpoint every 2-3 seconds until `status` is `SUCCESS` or `FAILURE`.
     # @param task_id [String] 
     # @param [Hash] opts the optional parameters
-    # @return [TaskStatus]
+    # @return [AsyncTaskStatus]
     def get_task_status_api_v1_processing_tasks_task_id_status_get(task_id, opts = {})
       data, _status_code, _headers = get_task_status_api_v1_processing_tasks_task_id_status_get_with_http_info(task_id, opts)
       data
@@ -182,7 +182,7 @@ module FactPulse
     # Retrieves the progress status of an invoice generation task.  ## Possible states  The `status` field uses the `CeleryStatus` enum with values: - **PENDING, STARTED, SUCCESS, FAILURE, RETRY**  See the `CeleryStatus` schema documentation for details.  ## Business result  When `status=\"SUCCESS\"`, the `result` field contains: - `status`: \"SUCCESS\" or \"ERROR\" (business result) - `content_b64`: Base64 encoded content (if success) - `errorCode`, `errorMessage`, `details`: AFNOR format (if business error)  ## Usage  Poll this endpoint every 2-3 seconds until `status` is `SUCCESS` or `FAILURE`.
     # @param task_id [String] 
     # @param [Hash] opts the optional parameters
-    # @return [Array<(TaskStatus, Integer, Hash)>] TaskStatus data, response status code and response headers
+    # @return [Array<(AsyncTaskStatus, Integer, Hash)>] AsyncTaskStatus data, response status code and response headers
     def get_task_status_api_v1_processing_tasks_task_id_status_get_with_http_info(task_id, opts = {})
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: InvoiceProcessingApi.get_task_status_api_v1_processing_tasks_task_id_status_get ...'
@@ -209,7 +209,7 @@ module FactPulse
       post_body = opts[:debug_body]
 
       # return_type
-      return_type = opts[:debug_return_type] || 'TaskStatus'
+      return_type = opts[:debug_return_type] || 'AsyncTaskStatus'
 
       # auth_names
       auth_names = opts[:debug_auth_names] || ['HTTPBearer']

data/lib/factpulse/api/pdfxml_verification_api.rb

@@ -23,7 +23,7 @@ module FactPulse
     # Retrieves the status and result of an asynchronous verification task.  **Possible statuses:** - `PENDING`: Task waiting in queue - `STARTED`: Task currently running - `SUCCESS`: Task completed successfully (see `result`) - `FAILURE`: System error (unhandled exception)  **Note:** The `result.status` field can be \"SUCCESS\" or \"ERROR\" independently of Celery status (which will always be SUCCESS if the task ran).
     # @param task_id [String] 
     # @param [Hash] opts the optional parameters
-    # @return [TaskStatus]
+    # @return [AsyncTaskStatus]
     def get_verification_status_api_v1_verification_verify_async_task_id_status_get(task_id, opts = {})
       data, _status_code, _headers = get_verification_status_api_v1_verification_verify_async_task_id_status_get_with_http_info(task_id, opts)
       data
@@ -33,7 +33,7 @@ module FactPulse
     # Retrieves the status and result of an asynchronous verification task.  **Possible statuses:** - `PENDING`: Task waiting in queue - `STARTED`: Task currently running - `SUCCESS`: Task completed successfully (see `result`) - `FAILURE`: System error (unhandled exception)  **Note:** The `result.status` field can be \"SUCCESS\" or \"ERROR\" independently of Celery status (which will always be SUCCESS if the task ran).
     # @param task_id [String] 
     # @param [Hash] opts the optional parameters
-    # @return [Array<(TaskStatus, Integer, Hash)>] TaskStatus data, response status code and response headers
+    # @return [Array<(AsyncTaskStatus, Integer, Hash)>] AsyncTaskStatus data, response status code and response headers
     def get_verification_status_api_v1_verification_verify_async_task_id_status_get_with_http_info(task_id, opts = {})
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: PDFXMLVerificationApi.get_verification_status_api_v1_verification_verify_async_task_id_status_get ...'
@@ -60,7 +60,7 @@ module FactPulse
       post_body = opts[:debug_body]
 
       # return_type
-      return_type = opts[:debug_return_type] || 'TaskStatus'
+      return_type = opts[:debug_return_type] || 'AsyncTaskStatus'
 
       # auth_names
       auth_names = opts[:debug_auth_names] || ['HTTPBearer']
@@ -86,7 +86,7 @@ module FactPulse
     # Retrieves the status and result of an asynchronous verification task.  **Possible statuses:** - `PENDING`: Task waiting in queue - `STARTED`: Task currently running - `SUCCESS`: Task completed successfully (see `result`) - `FAILURE`: System error (unhandled exception)  **Note:** The `result.status` field can be \"SUCCESS\" or \"ERROR\" independently of Celery status (which will always be SUCCESS if the task ran).
     # @param task_id [String] 
     # @param [Hash] opts the optional parameters
-    # @return [TaskStatus]
+    # @return [AsyncTaskStatus]
     def get_verification_status_api_v1_verification_verify_async_task_id_status_get_0(task_id, opts = {})
       data, _status_code, _headers = get_verification_status_api_v1_verification_verify_async_task_id_status_get_0_with_http_info(task_id, opts)
       data
@@ -96,7 +96,7 @@ module FactPulse
     # Retrieves the status and result of an asynchronous verification task.  **Possible statuses:** - &#x60;PENDING&#x60;: Task waiting in queue - &#x60;STARTED&#x60;: Task currently running - &#x60;SUCCESS&#x60;: Task completed successfully (see &#x60;result&#x60;) - &#x60;FAILURE&#x60;: System error (unhandled exception)  **Note:** The &#x60;result.status&#x60; field can be \&quot;SUCCESS\&quot; or \&quot;ERROR\&quot; independently of Celery status (which will always be SUCCESS if the task ran).
     # @param task_id [String] 
     # @param [Hash] opts the optional parameters
-    # @return [Array<(TaskStatus, Integer, Hash)>] TaskStatus data, response status code and response headers
+    # @return [Array<(AsyncTaskStatus, Integer, Hash)>] AsyncTaskStatus data, response status code and response headers
     def get_verification_status_api_v1_verification_verify_async_task_id_status_get_0_with_http_info(task_id, opts = {})
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: PDFXMLVerificationApi.get_verification_status_api_v1_verification_verify_async_task_id_status_get_0 ...'
@@ -123,7 +123,7 @@ module FactPulse
       post_body = opts[:debug_body]
 
       # return_type
-      return_type = opts[:debug_return_type] || 'TaskStatus'
+      return_type = opts[:debug_return_type] || 'AsyncTaskStatus'
 
       # auth_names
       auth_names = opts[:debug_auth_names] || ['HTTPBearer']

data/lib/factpulse/models/{task_status.rb → async_task_status.rb}

@@ -15,7 +15,7 @@ require 'time'
 
 module FactPulse
   # Complete description of an async task status.  The `status` field indicates the Celery state of the task. When `status=\"SUCCESS\"`, check `result.status` for the business result (\"SUCCESS\" or \"ERROR\").
-  class TaskStatus < ApiModelBase
+  class AsyncTaskStatus < ApiModelBase
     # Unique task identifier
     attr_accessor :task_id
 
@@ -85,14 +85,14 @@ module FactPulse
     # @param [Hash] attributes Model attributes in the form of hash
     def initialize(attributes = {})
       if (!attributes.is_a?(Hash))
-        fail ArgumentError, "The input argument (attributes) must be a hash in `FactPulse::TaskStatus` initialize method"
+        fail ArgumentError, "The input argument (attributes) must be a hash in `FactPulse::AsyncTaskStatus` initialize method"
       end
 
       # check to see if the attribute exists and convert string to symbol for hash key
       acceptable_attribute_map = self.class.acceptable_attribute_map
       attributes = attributes.each_with_object({}) { |(k, v), h|
         if (!acceptable_attribute_map.key?(k.to_sym))
-          fail ArgumentError, "`#{k}` is not a valid attribute in `FactPulse::TaskStatus`. Please check the name to make sure it's valid. List of attributes: " + acceptable_attribute_map.keys.inspect
+          fail ArgumentError, "`#{k}` is not a valid attribute in `FactPulse::AsyncTaskStatus`. Please check the name to make sure it's valid. List of attributes: " + acceptable_attribute_map.keys.inspect
         end
         h[k.to_sym] = v
       }

data/lib/factpulse/models/submit_gross_amount.rb

@@ -0,0 +1,104 @@
+=begin
+#FactPulse REST API
+
+# REST API for electronic invoicing in France: Factur-X, AFNOR PDP/PA, electronic signatures.  ## 🎯 Main Features  ### 📄 Factur-X Invoice Generation - **Formats**: XML only or PDF/A-3 with embedded XML - **Profiles**: MINIMUM, BASIC, EN16931, EXTENDED - **Standards**: EN 16931 (EU directive 2014/55), ISO 19005-3 (PDF/A-3), CII (UN/CEFACT) - **🆕 Simplified Format**: Generation from SIRET + auto-enrichment (Chorus Pro API + Business Search)  ### ✅ Validation and Compliance - **XML Validation**: Schematron (45 to 210+ rules depending on profile) - **PDF Validation**: PDF/A-3, Factur-X XMP metadata, electronic signatures - **VeraPDF**: Strict PDF/A validation (146+ ISO 19005-3 rules) - **Asynchronous Processing**: Celery support for heavy validations (VeraPDF)  ### 📡 AFNOR PDP/PA Integration (XP Z12-013) - **Flow Submission**: Send invoices to Partner Dematerialization Platforms - **Flow Search**: View submitted invoices - **Download**: Retrieve PDF/A-3 with XML - **Directory Service**: Company search (SIREN/SIRET) - **Multi-client**: Support for multiple PDP configs per user (stored credentials or zero-storage)  ### ✍️ PDF Electronic Signature - **Standards**: PAdES-B-B, PAdES-B-T (RFC 3161 timestamping), PAdES-B-LT (long-term archival) - **eIDAS Levels**: SES (self-signed), AdES (commercial CA), QES (QTSP) - **Validation**: Cryptographic integrity and certificate verification - **Certificate Generation**: Self-signed X.509 certificates for testing  ### 🔄 Asynchronous Processing - **Celery**: Asynchronous generation, validation and signing - **Polling**: Status tracking via `/tasks/{task_id}/status` - **No timeout**: Ideal for large files or heavy validations  ## 🔒 Authentication  All requests require a **JWT token** in the Authorization header: ``` Authorization: Bearer YOUR_JWT_TOKEN ```  ### How to obtain a JWT token?  #### 🔑 Method 1: `/api/token/` API (Recommended)  **URL:** `https://www.factpulse.fr/api/token/`  This method is **recommended** for integration in your applications and CI/CD workflows.  **Prerequisites:** Having set a password on your account  **For users registered via email/password:** - You already have a password, use it directly  **For users registered via OAuth (Google/GitHub):** - You must first set a password at: https://www.factpulse.fr/accounts/password/set/ - Once the password is created, you can use the API  **Request example:** ```bash curl -X POST https://www.factpulse.fr/api/token/ \\   -H \"Content-Type: application/json\" \\   -d '{     \"username\": \"your_email@example.com\",     \"password\": \"your_password\"   }' ```  **Optional `client_uid` parameter:**  To select credentials for a specific client (PA/PDP, Chorus Pro, signing certificates), add `client_uid`:  ```bash curl -X POST https://www.factpulse.fr/api/token/ \\   -H \"Content-Type: application/json\" \\   -d '{     \"username\": \"your_email@example.com\",     \"password\": \"your_password\",     \"client_uid\": \"550e8400-e29b-41d4-a716-446655440000\"   }' ```  The `client_uid` will be included in the JWT and allow the API to automatically use: - AFNOR/PDP credentials configured for this client - Chorus Pro credentials configured for this client - Electronic signature certificates configured for this client  **Response:** ```json {   \"access\": \"eyJ0eXAiOiJKV1QiLCJhbGc...\",  // Access token (validity: 30 min)   \"refresh\": \"eyJ0eXAiOiJKV1QiLCJhbGc...\"  // Refresh token (validity: 7 days) } ```  **Advantages:** - ✅ Full automation (CI/CD, scripts) - ✅ Programmatic token management - ✅ Refresh token support for automatic access renewal - ✅ Easy integration in any language/tool  #### 🖥️ Method 2: Dashboard Generation (Alternative)  **URL:** https://www.factpulse.fr/dashboard/  This method is suitable for quick tests or occasional use via the graphical interface.  **How it works:** - Log in to the dashboard - Use the \"Generate Test Token\" or \"Generate Production Token\" buttons - Works for **all** users (OAuth and email/password), without requiring a password  **Token types:** - **Test Token**: 24h validity, 1000 calls/day quota (free) - **Production Token**: 7 days validity, quota based on your plan  **Advantages:** - ✅ Quick for API testing - ✅ No password required - ✅ Simple visual interface  **Disadvantages:** - ❌ Requires manual action - ❌ No refresh token - ❌ Less suited for automation  ### 📚 Full Documentation  For more information on authentication and API usage: https://www.factpulse.fr/documentation-api/     
+
+The version of the OpenAPI document: 1.0.0
+
+Generated by: https://openapi-generator.tech
+Generator version: 7.18.0-SNAPSHOT
+
+=end
+
+require 'date'
+require 'time'
+
+module FactPulse
+  # Total gross amount
+  module SubmitGrossAmount
+    class << self
+      # List of class defined in anyOf (OpenAPI v3)
+      def openapi_any_of
+        [
+          :'Float',
+          :'String'
+        ]
+      end
+
+      # Builds the object
+      # @param [Mixed] Data to be matched against the list of anyOf items
+      # @return [Object] Returns the model or the data itself
+      def build(data)
+        # Go through the list of anyOf items and attempt to identify the appropriate one.
+        # Note:
+        # - No advanced validation of types in some cases (e.g. "x: { type: string }" will happily match { x: 123 })
+        #   due to the way the deserialization is made in the base_object template (it just casts without verifying).
+        # - TODO: scalar values are de facto behaving as if they were nullable.
+        # - TODO: logging when debugging is set.
+        openapi_any_of.each do |klass|
+          begin
+            next if klass == :AnyType # "nullable: true"
+            return find_and_cast_into_type(klass, data)
+          rescue # rescue all errors so we keep iterating even if the current item lookup raises
+          end
+        end
+
+        openapi_any_of.include?(:AnyType) ? data : nil
+      end
+
+      private
+
+      SchemaMismatchError = Class.new(StandardError)
+
+      # Note: 'File' is missing here because in the regular case we get the data _after_ a call to JSON.parse.
+      def find_and_cast_into_type(klass, data)
+        return if data.nil?
+
+        case klass.to_s
+        when 'Boolean'
+          return data if data.instance_of?(TrueClass) || data.instance_of?(FalseClass)
+        when 'Float'
+          return data if data.instance_of?(Float)
+        when 'Integer'
+          return data if data.instance_of?(Integer)
+        when 'Time'
+          return Time.parse(data)
+        when 'Date'
+          return Date.iso8601(data)
+        when 'String'
+          return data if data.instance_of?(String)
+        when 'Object' # "type: object"
+          return data if data.instance_of?(Hash)
+        when /\AArray<(?<sub_type>.+)>\z/ # "type: array"
+          if data.instance_of?(Array)
+            sub_type = Regexp.last_match[:sub_type]
+            return data.map { |item| find_and_cast_into_type(sub_type, item) }
+          end
+        when /\AHash<String, (?<sub_type>.+)>\z/ # "type: object" with "additionalProperties: { ... }"
+          if data.instance_of?(Hash) && data.keys.all? { |k| k.instance_of?(Symbol) || k.instance_of?(String) }
+            sub_type = Regexp.last_match[:sub_type]
+            return data.each_with_object({}) { |(k, v), hsh| hsh[k] = find_and_cast_into_type(sub_type, v) }
+          end
+        else # model
+          const = FactPulse.const_get(klass)
+          if const
+            if const.respond_to?(:openapi_any_of) # nested anyOf model
+              model = const.build(data)
+              return model if model
+            else
+              # raise if data contains keys that are not known to the model
+              raise if const.respond_to?(:acceptable_attributes) && !(data.keys - const.acceptable_attributes).empty?
+              model = const.build_from_hash(data)
+              return model if model
+            end
+          end
+        end
+
+        raise # if no match by now, raise
+      rescue
+        raise SchemaMismatchError, "#{data} doesn't match the #{klass} type"
+      end
+    end
+  end
+
+end

data/lib/factpulse/models/submit_invoice_request.rb

@@ -90,9 +90,9 @@ module FactPulse
         :'structure_id' => :'Integer',
         :'service_code' => :'String',
         :'engagement_number' => :'String',
-        :'total_net_amount' => :'TotalNetAmount',
-        :'vat_amount' => :'VatAmount',
-        :'total_gross_amount' => :'TotalGrossAmount',
+        :'total_net_amount' => :'SubmitNetAmount',
+        :'vat_amount' => :'SubmitVatAmount',
+        :'total_gross_amount' => :'SubmitGrossAmount',
         :'main_attachment_id' => :'Integer',
         :'main_attachment_label' => :'String',
         :'comment' => :'String',

data/lib/factpulse/models/submit_net_amount.rb

@@ -0,0 +1,104 @@
+=begin
+#FactPulse REST API
+
+# REST API for electronic invoicing in France: Factur-X, AFNOR PDP/PA, electronic signatures.  ## 🎯 Main Features  ### 📄 Factur-X Invoice Generation - **Formats**: XML only or PDF/A-3 with embedded XML - **Profiles**: MINIMUM, BASIC, EN16931, EXTENDED - **Standards**: EN 16931 (EU directive 2014/55), ISO 19005-3 (PDF/A-3), CII (UN/CEFACT) - **🆕 Simplified Format**: Generation from SIRET + auto-enrichment (Chorus Pro API + Business Search)  ### ✅ Validation and Compliance - **XML Validation**: Schematron (45 to 210+ rules depending on profile) - **PDF Validation**: PDF/A-3, Factur-X XMP metadata, electronic signatures - **VeraPDF**: Strict PDF/A validation (146+ ISO 19005-3 rules) - **Asynchronous Processing**: Celery support for heavy validations (VeraPDF)  ### 📡 AFNOR PDP/PA Integration (XP Z12-013) - **Flow Submission**: Send invoices to Partner Dematerialization Platforms - **Flow Search**: View submitted invoices - **Download**: Retrieve PDF/A-3 with XML - **Directory Service**: Company search (SIREN/SIRET) - **Multi-client**: Support for multiple PDP configs per user (stored credentials or zero-storage)  ### ✍️ PDF Electronic Signature - **Standards**: PAdES-B-B, PAdES-B-T (RFC 3161 timestamping), PAdES-B-LT (long-term archival) - **eIDAS Levels**: SES (self-signed), AdES (commercial CA), QES (QTSP) - **Validation**: Cryptographic integrity and certificate verification - **Certificate Generation**: Self-signed X.509 certificates for testing  ### 🔄 Asynchronous Processing - **Celery**: Asynchronous generation, validation and signing - **Polling**: Status tracking via `/tasks/{task_id}/status` - **No timeout**: Ideal for large files or heavy validations  ## 🔒 Authentication  All requests require a **JWT token** in the Authorization header: ``` Authorization: Bearer YOUR_JWT_TOKEN ```  ### How to obtain a JWT token?  #### 🔑 Method 1: `/api/token/` API (Recommended)  **URL:** `https://www.factpulse.fr/api/token/`  This method is **recommended** for integration in your applications and CI/CD workflows.  **Prerequisites:** Having set a password on your account  **For users registered via email/password:** - You already have a password, use it directly  **For users registered via OAuth (Google/GitHub):** - You must first set a password at: https://www.factpulse.fr/accounts/password/set/ - Once the password is created, you can use the API  **Request example:** ```bash curl -X POST https://www.factpulse.fr/api/token/ \\   -H \"Content-Type: application/json\" \\   -d '{     \"username\": \"your_email@example.com\",     \"password\": \"your_password\"   }' ```  **Optional `client_uid` parameter:**  To select credentials for a specific client (PA/PDP, Chorus Pro, signing certificates), add `client_uid`:  ```bash curl -X POST https://www.factpulse.fr/api/token/ \\   -H \"Content-Type: application/json\" \\   -d '{     \"username\": \"your_email@example.com\",     \"password\": \"your_password\",     \"client_uid\": \"550e8400-e29b-41d4-a716-446655440000\"   }' ```  The `client_uid` will be included in the JWT and allow the API to automatically use: - AFNOR/PDP credentials configured for this client - Chorus Pro credentials configured for this client - Electronic signature certificates configured for this client  **Response:** ```json {   \"access\": \"eyJ0eXAiOiJKV1QiLCJhbGc...\",  // Access token (validity: 30 min)   \"refresh\": \"eyJ0eXAiOiJKV1QiLCJhbGc...\"  // Refresh token (validity: 7 days) } ```  **Advantages:** - ✅ Full automation (CI/CD, scripts) - ✅ Programmatic token management - ✅ Refresh token support for automatic access renewal - ✅ Easy integration in any language/tool  #### 🖥️ Method 2: Dashboard Generation (Alternative)  **URL:** https://www.factpulse.fr/dashboard/  This method is suitable for quick tests or occasional use via the graphical interface.  **How it works:** - Log in to the dashboard - Use the \"Generate Test Token\" or \"Generate Production Token\" buttons - Works for **all** users (OAuth and email/password), without requiring a password  **Token types:** - **Test Token**: 24h validity, 1000 calls/day quota (free) - **Production Token**: 7 days validity, quota based on your plan  **Advantages:** - ✅ Quick for API testing - ✅ No password required - ✅ Simple visual interface  **Disadvantages:** - ❌ Requires manual action - ❌ No refresh token - ❌ Less suited for automation  ### 📚 Full Documentation  For more information on authentication and API usage: https://www.factpulse.fr/documentation-api/     
+
+The version of the OpenAPI document: 1.0.0
+
+Generated by: https://openapi-generator.tech
+Generator version: 7.18.0-SNAPSHOT
+
+=end
+
+require 'date'
+require 'time'
+
+module FactPulse
+  # Total net amount
+  module SubmitNetAmount
+    class << self
+      # List of class defined in anyOf (OpenAPI v3)
+      def openapi_any_of
+        [
+          :'Float',
+          :'String'
+        ]
+      end
+
+      # Builds the object
+      # @param [Mixed] Data to be matched against the list of anyOf items
+      # @return [Object] Returns the model or the data itself
+      def build(data)
+        # Go through the list of anyOf items and attempt to identify the appropriate one.
+        # Note:
+        # - No advanced validation of types in some cases (e.g. "x: { type: string }" will happily match { x: 123 })
+        #   due to the way the deserialization is made in the base_object template (it just casts without verifying).
+        # - TODO: scalar values are de facto behaving as if they were nullable.
+        # - TODO: logging when debugging is set.
+        openapi_any_of.each do |klass|
+          begin
+            next if klass == :AnyType # "nullable: true"
+            return find_and_cast_into_type(klass, data)
+          rescue # rescue all errors so we keep iterating even if the current item lookup raises
+          end
+        end
+
+        openapi_any_of.include?(:AnyType) ? data : nil
+      end
+
+      private
+
+      SchemaMismatchError = Class.new(StandardError)
+
+      # Note: 'File' is missing here because in the regular case we get the data _after_ a call to JSON.parse.
+      def find_and_cast_into_type(klass, data)
+        return if data.nil?
+
+        case klass.to_s
+        when 'Boolean'
+          return data if data.instance_of?(TrueClass) || data.instance_of?(FalseClass)
+        when 'Float'
+          return data if data.instance_of?(Float)
+        when 'Integer'
+          return data if data.instance_of?(Integer)
+        when 'Time'
+          return Time.parse(data)
+        when 'Date'
+          return Date.iso8601(data)
+        when 'String'
+          return data if data.instance_of?(String)
+        when 'Object' # "type: object"
+          return data if data.instance_of?(Hash)
+        when /\AArray<(?<sub_type>.+)>\z/ # "type: array"
+          if data.instance_of?(Array)
+            sub_type = Regexp.last_match[:sub_type]
+            return data.map { |item| find_and_cast_into_type(sub_type, item) }
+          end
+        when /\AHash<String, (?<sub_type>.+)>\z/ # "type: object" with "additionalProperties: { ... }"
+          if data.instance_of?(Hash) && data.keys.all? { |k| k.instance_of?(Symbol) || k.instance_of?(String) }
+            sub_type = Regexp.last_match[:sub_type]
+            return data.each_with_object({}) { |(k, v), hsh| hsh[k] = find_and_cast_into_type(sub_type, v) }
+          end
+        else # model
+          const = FactPulse.const_get(klass)
+          if const
+            if const.respond_to?(:openapi_any_of) # nested anyOf model
+              model = const.build(data)
+              return model if model
+            else
+              # raise if data contains keys that are not known to the model
+              raise if const.respond_to?(:acceptable_attributes) && !(data.keys - const.acceptable_attributes).empty?
+              model = const.build_from_hash(data)
+              return model if model
+            end
+          end
+        end
+
+        raise # if no match by now, raise
+      rescue
+        raise SchemaMismatchError, "#{data} doesn't match the #{klass} type"
+      end
+    end
+  end
+
+end

data/lib/factpulse/models/submit_vat_amount.rb

@@ -0,0 +1,104 @@
+=begin
+#FactPulse REST API
+
+# REST API for electronic invoicing in France: Factur-X, AFNOR PDP/PA, electronic signatures.  ## 🎯 Main Features  ### 📄 Factur-X Invoice Generation - **Formats**: XML only or PDF/A-3 with embedded XML - **Profiles**: MINIMUM, BASIC, EN16931, EXTENDED - **Standards**: EN 16931 (EU directive 2014/55), ISO 19005-3 (PDF/A-3), CII (UN/CEFACT) - **🆕 Simplified Format**: Generation from SIRET + auto-enrichment (Chorus Pro API + Business Search)  ### ✅ Validation and Compliance - **XML Validation**: Schematron (45 to 210+ rules depending on profile) - **PDF Validation**: PDF/A-3, Factur-X XMP metadata, electronic signatures - **VeraPDF**: Strict PDF/A validation (146+ ISO 19005-3 rules) - **Asynchronous Processing**: Celery support for heavy validations (VeraPDF)  ### 📡 AFNOR PDP/PA Integration (XP Z12-013) - **Flow Submission**: Send invoices to Partner Dematerialization Platforms - **Flow Search**: View submitted invoices - **Download**: Retrieve PDF/A-3 with XML - **Directory Service**: Company search (SIREN/SIRET) - **Multi-client**: Support for multiple PDP configs per user (stored credentials or zero-storage)  ### ✍️ PDF Electronic Signature - **Standards**: PAdES-B-B, PAdES-B-T (RFC 3161 timestamping), PAdES-B-LT (long-term archival) - **eIDAS Levels**: SES (self-signed), AdES (commercial CA), QES (QTSP) - **Validation**: Cryptographic integrity and certificate verification - **Certificate Generation**: Self-signed X.509 certificates for testing  ### 🔄 Asynchronous Processing - **Celery**: Asynchronous generation, validation and signing - **Polling**: Status tracking via `/tasks/{task_id}/status` - **No timeout**: Ideal for large files or heavy validations  ## 🔒 Authentication  All requests require a **JWT token** in the Authorization header: ``` Authorization: Bearer YOUR_JWT_TOKEN ```  ### How to obtain a JWT token?  #### 🔑 Method 1: `/api/token/` API (Recommended)  **URL:** `https://www.factpulse.fr/api/token/`  This method is **recommended** for integration in your applications and CI/CD workflows.  **Prerequisites:** Having set a password on your account  **For users registered via email/password:** - You already have a password, use it directly  **For users registered via OAuth (Google/GitHub):** - You must first set a password at: https://www.factpulse.fr/accounts/password/set/ - Once the password is created, you can use the API  **Request example:** ```bash curl -X POST https://www.factpulse.fr/api/token/ \\   -H \"Content-Type: application/json\" \\   -d '{     \"username\": \"your_email@example.com\",     \"password\": \"your_password\"   }' ```  **Optional `client_uid` parameter:**  To select credentials for a specific client (PA/PDP, Chorus Pro, signing certificates), add `client_uid`:  ```bash curl -X POST https://www.factpulse.fr/api/token/ \\   -H \"Content-Type: application/json\" \\   -d '{     \"username\": \"your_email@example.com\",     \"password\": \"your_password\",     \"client_uid\": \"550e8400-e29b-41d4-a716-446655440000\"   }' ```  The `client_uid` will be included in the JWT and allow the API to automatically use: - AFNOR/PDP credentials configured for this client - Chorus Pro credentials configured for this client - Electronic signature certificates configured for this client  **Response:** ```json {   \"access\": \"eyJ0eXAiOiJKV1QiLCJhbGc...\",  // Access token (validity: 30 min)   \"refresh\": \"eyJ0eXAiOiJKV1QiLCJhbGc...\"  // Refresh token (validity: 7 days) } ```  **Advantages:** - ✅ Full automation (CI/CD, scripts) - ✅ Programmatic token management - ✅ Refresh token support for automatic access renewal - ✅ Easy integration in any language/tool  #### 🖥️ Method 2: Dashboard Generation (Alternative)  **URL:** https://www.factpulse.fr/dashboard/  This method is suitable for quick tests or occasional use via the graphical interface.  **How it works:** - Log in to the dashboard - Use the \"Generate Test Token\" or \"Generate Production Token\" buttons - Works for **all** users (OAuth and email/password), without requiring a password  **Token types:** - **Test Token**: 24h validity, 1000 calls/day quota (free) - **Production Token**: 7 days validity, quota based on your plan  **Advantages:** - ✅ Quick for API testing - ✅ No password required - ✅ Simple visual interface  **Disadvantages:** - ❌ Requires manual action - ❌ No refresh token - ❌ Less suited for automation  ### 📚 Full Documentation  For more information on authentication and API usage: https://www.factpulse.fr/documentation-api/     
+
+The version of the OpenAPI document: 1.0.0
+
+Generated by: https://openapi-generator.tech
+Generator version: 7.18.0-SNAPSHOT
+
+=end
+
+require 'date'
+require 'time'
+
+module FactPulse
+  # VAT amount
+  module SubmitVatAmount
+    class << self
+      # List of class defined in anyOf (OpenAPI v3)
+      def openapi_any_of
+        [
+          :'Float',
+          :'String'
+        ]
+      end
+
+      # Builds the object
+      # @param [Mixed] Data to be matched against the list of anyOf items
+      # @return [Object] Returns the model or the data itself
+      def build(data)
+        # Go through the list of anyOf items and attempt to identify the appropriate one.
+        # Note:
+        # - No advanced validation of types in some cases (e.g. "x: { type: string }" will happily match { x: 123 })
+        #   due to the way the deserialization is made in the base_object template (it just casts without verifying).
+        # - TODO: scalar values are de facto behaving as if they were nullable.
+        # - TODO: logging when debugging is set.
+        openapi_any_of.each do |klass|
+          begin
+            next if klass == :AnyType # "nullable: true"
+            return find_and_cast_into_type(klass, data)
+          rescue # rescue all errors so we keep iterating even if the current item lookup raises
+          end
+        end
+
+        openapi_any_of.include?(:AnyType) ? data : nil
+      end
+
+      private
+
+      SchemaMismatchError = Class.new(StandardError)
+
+      # Note: 'File' is missing here because in the regular case we get the data _after_ a call to JSON.parse.
+      def find_and_cast_into_type(klass, data)
+        return if data.nil?
+
+        case klass.to_s
+        when 'Boolean'
+          return data if data.instance_of?(TrueClass) || data.instance_of?(FalseClass)
+        when 'Float'
+          return data if data.instance_of?(Float)
+        when 'Integer'
+          return data if data.instance_of?(Integer)
+        when 'Time'
+          return Time.parse(data)
+        when 'Date'
+          return Date.iso8601(data)
+        when 'String'
+          return data if data.instance_of?(String)
+        when 'Object' # "type: object"
+          return data if data.instance_of?(Hash)
+        when /\AArray<(?<sub_type>.+)>\z/ # "type: array"
+          if data.instance_of?(Array)
+            sub_type = Regexp.last_match[:sub_type]
+            return data.map { |item| find_and_cast_into_type(sub_type, item) }
+          end
+        when /\AHash<String, (?<sub_type>.+)>\z/ # "type: object" with "additionalProperties: { ... }"
+          if data.instance_of?(Hash) && data.keys.all? { |k| k.instance_of?(Symbol) || k.instance_of?(String) }
+            sub_type = Regexp.last_match[:sub_type]
+            return data.each_with_object({}) { |(k, v), hsh| hsh[k] = find_and_cast_into_type(sub_type, v) }
+          end
+        else # model
+          const = FactPulse.const_get(klass)
+          if const
+            if const.respond_to?(:openapi_any_of) # nested anyOf model
+              model = const.build(data)
+              return model if model
+            else
+              # raise if data contains keys that are not known to the model
+              raise if const.respond_to?(:acceptable_attributes) && !(data.keys - const.acceptable_attributes).empty?
+              model = const.build_from_hash(data)
+              return model if model
+            end
+          end
+        end
+
+        raise # if no match by now, raise
+      rescue
+        raise SchemaMismatchError, "#{data} doesn't match the #{klass} type"
+      end
+    end
+  end
+
+end

data/lib/factpulse/models/vat_amount.rb

@@ -14,8 +14,8 @@ require 'date'
 require 'time'
 
 module FactPulse
-  # VAT amount
-  module VatAmount
+  # VAT amount for this line. (Accepte number, string ou integer)
+  module VATAmount
     class << self
       # List of class defined in anyOf (OpenAPI v3)
       def openapi_any_of

data/lib/factpulse/version.rb

@@ -11,5 +11,5 @@ Generator version: 7.18.0-SNAPSHOT
 =end
 
 module FactPulse
-  VERSION = '3.0.1'
+  VERSION = '3.0.3'
 end

data/lib/factpulse.rb

@@ -27,6 +27,7 @@ require 'factpulse/models/api_profile'
 require 'factpulse/models/acknowledgment_status'
 require 'factpulse/models/allowance_reason_code'
 require 'factpulse/models/amount_due'
+require 'factpulse/models/async_task_status'
 require 'factpulse/models/bounding_box_schema'
 require 'factpulse/models/celery_status'
 require 'factpulse/models/certificate_info_response'
@@ -104,12 +105,14 @@ require 'factpulse/models/submit_complete_invoice_request'
 require 'factpulse/models/submit_complete_invoice_response'
 require 'factpulse/models/submit_flow_request'
 require 'factpulse/models/submit_flow_response'
+require 'factpulse/models/submit_gross_amount'
 require 'factpulse/models/submit_invoice_request'
 require 'factpulse/models/submit_invoice_response'
+require 'factpulse/models/submit_net_amount'
+require 'factpulse/models/submit_vat_amount'
 require 'factpulse/models/supplementary_attachment'
 require 'factpulse/models/supplier'
 require 'factpulse/models/task_response'
-require 'factpulse/models/task_status'
 require 'factpulse/models/taxable_amount'
 require 'factpulse/models/total_gross_amount'
 require 'factpulse/models/total_net_amount'
@@ -125,7 +128,6 @@ require 'factpulse/models/validation_error_detail'
 require 'factpulse/models/validation_error_loc_inner'
 require 'factpulse/models/validation_error_response'
 require 'factpulse/models/validation_success_response'
-require 'factpulse/models/vat_amount'
 require 'factpulse/models/verification_success_response'
 require 'factpulse/models/verified_field_schema'
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: factpulse
 version: !ruby/object:Gem::Version
-  version: 3.0.1
+  version: 3.0.3
 platform: ruby
 authors:
 - OpenAPI-Generator
@@ -128,6 +128,7 @@ files:
 - docs/AcknowledgmentStatus.md
 - docs/AllowanceReasonCode.md
 - docs/AmountDue.md
+- docs/AsyncTaskStatus.md
 - docs/BoundingBoxSchema.md
 - docs/CeleryStatus.md
 - docs/CertificateInfoResponse.md
@@ -209,12 +210,14 @@ files:
 - docs/SubmitCompleteInvoiceResponse.md
 - docs/SubmitFlowRequest.md
 - docs/SubmitFlowResponse.md
+- docs/SubmitGrossAmount.md
 - docs/SubmitInvoiceRequest.md
 - docs/SubmitInvoiceResponse.md
+- docs/SubmitNetAmount.md
+- docs/SubmitVatAmount.md
 - docs/SupplementaryAttachment.md
 - docs/Supplier.md
 - docs/TaskResponse.md
-- docs/TaskStatus.md
 - docs/TaxableAmount.md
 - docs/TotalGrossAmount.md
 - docs/TotalNetAmount.md
@@ -231,7 +234,6 @@ files:
 - docs/ValidationErrorLocInner.md
 - docs/ValidationErrorResponse.md
 - docs/ValidationSuccessResponse.md
-- docs/VatAmount.md
 - docs/VerificationSuccessResponse.md
 - docs/VerifiedFieldSchema.md
 - factpulse.gemspec
@@ -261,6 +263,7 @@ files:
 - lib/factpulse/models/amount_due.rb
 - lib/factpulse/models/api_error.rb
 - lib/factpulse/models/api_profile.rb
+- lib/factpulse/models/async_task_status.rb
 - lib/factpulse/models/bounding_box_schema.rb
 - lib/factpulse/models/celery_status.rb
 - lib/factpulse/models/certificate_info_response.rb
@@ -338,12 +341,14 @@ files:
 - lib/factpulse/models/submit_complete_invoice_response.rb
 - lib/factpulse/models/submit_flow_request.rb
 - lib/factpulse/models/submit_flow_response.rb
+- lib/factpulse/models/submit_gross_amount.rb
 - lib/factpulse/models/submit_invoice_request.rb
 - lib/factpulse/models/submit_invoice_response.rb
+- lib/factpulse/models/submit_net_amount.rb
+- lib/factpulse/models/submit_vat_amount.rb
 - lib/factpulse/models/supplementary_attachment.rb
 - lib/factpulse/models/supplier.rb
 - lib/factpulse/models/task_response.rb
-- lib/factpulse/models/task_status.rb
 - lib/factpulse/models/taxable_amount.rb
 - lib/factpulse/models/total_gross_amount.rb
 - lib/factpulse/models/total_net_amount.rb