Skip to main content
Glama
cmendezs

mcp-facture-electronique-fr

submit_transaction_report

Submit e-reporting flows (international B2B, B2C) to French DGFiP Approved Platform by building and posting FRR XML payloads.

Instructions

Submit a DGFiP Flux 10.1 / 10.3 transaction e-reporting flow.

Builds a FRR XML payload conforming to DGFiP Spécifications Externes v3.2 (transaction.xsd / ereporting.xsd) and submits it to the Approved Platform via POST /v1/flows with flowSyntax="FRR".

Use for:

  • International B2B outbound sales (processing_rule=B2BInt, flow_type=IndividualCustomerTransactionReport)

  • International B2B inbound purchases (processing_rule=B2BInt, flow_type=UnitarySupplierTransactionReport)

  • B2C individual transactions (processing_rule=B2C, flow_type=IndividualCustomerTransactionReport)

  • Aggregated B2C reports (processing_rule=B2C, flow_type=AggregatedCustomerTransactionReport)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transmission_idYesTT-1: Unique identifier for this transmission (generated by sender).
issue_datetimeYesTT-3: Transmission creation timestamp, e.g. '20250115T120000+0100'.
type_codeYesTT-4: Transmission type code, e.g. '380' (invoice report).
sender_idYesTT-8: Identifier of the CS/PDP platform submitting the report.
sender_id_schemeYesTT-7: ID scheme for sender, e.g. 'SIREN', 'SIRET', 'TVA', '0088'.
sender_nameYesTT-9: Legal name of the sender platform.
sender_role_codeYesTT-10: Sender role code. Use 'CS' (Compatible Solution), 'PDP', 'OD' (obligataire délégant), or 'MOA' (assujetti).
issuer_idYesTT-13: SIREN or SIRET of the French taxable entity (déclarant).
issuer_id_schemeYesTT-12: ID scheme for issuer, typically 'SIREN' or 'SIRET'.
issuer_nameYesTT-14: Legal name of the declarant.
issuer_role_codeYesTT-15: Issuer role code. Use 'MOA' (assujetti / declarant) or 'OD' (obligataire délégant).
period_startYesTT-17: Report period start date in ISO 8601 format (e.g. '2025-01-01').
period_endYesTT-18: Report period end date in ISO 8601 format (e.g. '2025-01-31').
invoices_jsonYesJSON array of invoice transaction records. Each invoice in the `invoices` JSON list must have: Required fields: id TT-19 Invoice number / identifier issue_date TT-20 Issue date (ISO 8601, e.g. "2025-01-15") type_code TT-21 Invoice type: "380" (invoice), "381" (credit note), "389" (self-billed) currency_code TT-22 ISO 4217 currency code (e.g. "EUR", "USD") business_process_id TT-28 Business process ID (e.g. "A1", "A2") business_process_type_id TT-29 Process type: "EREP" (e-reporting), "EINV" (e-invoicing) seller_company_id TT-33 Seller identifier (SIREN, SIRET, VAT number, etc.) seller_company_id_scheme TT-33-1 Scheme: "SIREN", "SIRET", "0088" (GLN), "TVA", etc. monetary_total_tax_amount TT-52 Total VAT amount (decimal string, e.g. "200.00") monetary_total_currency TT-202 Currency code for the tax amount (e.g. "EUR") tax_subtotals TT-54..59 List of VAT breakdown objects (see below) Optional fields: due_date TT-201 Payment due date (ISO 8601) tax_due_date_type_code TT-24 VAT due date code ("3" cash, "4" invoice date, "5" delivery) tax_exclusive_amount TT-51 Total amount excluding VAT seller_tax_registration_id TT-34 Seller VAT number (e.g. "FR12345678901") seller_tax_registration_id_qualifier TT-34-0 Qualifier (default "VA") seller_country TT-35 ISO 3166-1 alpha-2 country code buyer_company_id TT-36 Buyer identifier (for international B2B) buyer_company_id_scheme TT-37 Buyer ID scheme buyer_tax_registration_id TT-38 Buyer VAT number buyer_tax_registration_id_qualifier TT-38-0 Qualifier (default "VA") buyer_country TT-39 Buyer country code tax_subtotals list entries: taxable_amount TT-54 Tax base amount (decimal string) tax_amount TT-55 VAT amount for this category (decimal string) tax_percent TT-57 VAT rate (decimal, e.g. "20.0", "5.5", "0.0") code TT-56 (optional) VAT category code: "S" standard, "Z" zero, "E" exempt exemption_reason TT-58 (optional) Exemption reason text exemption_reason_code TT-59 (optional) Exemption reason code
flow_typeYesXP Z12-013 FlowType for this e-reporting submission: IndividualCustomerTransactionReport — Flux 10.1 individual B2C or intl B2B AggregatedCustomerTransactionReport — Flux 10.3 aggregated B2C UnitarySupplierTransactionReport — Flux 10.1 intl B2B purchases MultiFlowReport — mixed flow types
processing_ruleYesXP Z12-013 ProcessingRule: B2BInt — international B2B e-reporting B2C — B2C e-reporting
transmission_nameNoTT-2: Optional human-readable name for the transmission.
tracking_idNoOptional external tracking identifier for this flow.
confirmation_tokenNoConfirmation token returned by a prior pending response.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions building and submitting XML to an approved platform, but fails to disclose any behavioral traits such as validation steps, error handling, side effects, required permissions, rate limits, or response format. The description is too minimal given the tool's complexity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively concise, uses a bullet list for use cases, and front-loads the main action. Each sentence provides value. Could be slightly more structured, but overall earns its place without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (19 params, 16 required) and presence of output schema, the description covers purpose and supported scenarios. However, it lacks details on prerequisites, failure modes, and integration with sibling tools. The output is not described, but output schema mitigates this.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed parameter descriptions. The tool description adds overarching use-case context but does not enhance individual parameter meaning beyond the schema. Baseline score of 3 is appropriate as schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: submitting a DGFiP Flux 10.1/10.3 transaction e-reporting flow. It specifies the XML format (FRR), version (v3.2), endpoint (POST /v1/flows with flowSyntax="FRR"), and enumerates specific use cases (B2B intl, B2C). This distinguishes it from siblings like submit_payment_report.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly lists four use cases with corresponding processing_rule and flow_type values, providing clear context. However, it does not explicitly state when not to use this tool or offer comparisons to siblings (e.g., submit_lifecycle_status), so it lacks exclusion guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cmendezs/mcp-facture-electronique-fr'

If you have feedback or need assistance with the MCP directory API, please join our Discord server