---
title: "Fetch the e-reporting summary for a party"
method: GET
path: "/apps/gov-fr/v1/reports/{silo_entry_id}"
---

# Fetch the e-reporting summary for a party

`GET /apps/gov-fr/v1/reports/{silo_entry_id}`

## Request

- Base URL: `https://api.invopop.com`
- URL: `https://api.invopop.com/apps/gov-fr/v1/reports/{silo_entry_id}`
- Auth: none required
- TypeScript: <https://skmtc.dev/invopop/apis/access-service-api/docs/apps/gov-fr/v1/reports/:silo_entry_id/get.ts> (a function with typed inputs; its response is checked against the schema)

Returns the current Flux 10 e-reporting status for the party
identified by the silo entry, one block per report kind:

- `tx` — **transactions**.
- `py` — **payments**.

## Path parameters

- `silo_entry_id` string, required

## Response `200`

Reporting summary for the party.

- ReportingSummary: A party's Flux 10 e-reporting status across all report kinds.
  - `silo_entry_id` string, required: Silo entry (party) the summary is for.
  - `siren` string, required: 9-digit French SIREN of the party.
  - `enabled` boolean, required: Whether e-reporting is currently enabled for the party.
  - `regime` 'real_normal_monthly' | 'real_normal_quarterly' | 'simplified' | 'vat_franchise': VAT regime driving the reporting cadences. Omitted when reporting is not enabled. - `real_normal_monthly` - Réel normal mensuel. - `real_normal_quarterly` - Réel normal trimestriel. - `simplified` - Réel simplifié. - `vat_franchise` - Franchise en base.
  - `kinds` ReportingKindStatus[], required: Per-kind status blocks. Empty when reporting is not enabled.
    - `kind` 'tx' | 'py', required: Report kind: - `tx` - Transactions (invoice data). - `py` - Payments.
    - `cadence` 'ten_day' | 'monthly' | 'bimonthly', required: How often reports are filed for this kind, derived from the VAT regime: - `ten_day` - Every ten days. - `monthly` - Once per calendar month. - `bimonthly` - Once every two calendar months.
    - `open_period_start` string, required: First day of the window currently being accumulated, as `YYYY-MM-DD`.
    - `open_period_end` string, required: Last day (inclusive) of the currently open window, as `YYYY-MM-DD`.
    - `next_due_period_start` string, required: First day of the next window a report will be generated for, as `YYYY-MM-DD`.
    - `next_due_period_end` string, required: Last day (inclusive) of the next-due window, as `YYYY-MM-DD`.
    - `next_due_deadline` string, date-time, required: Filing deadline for the next-due window (Europe/Paris).
    - `last_period_end` string: End date of the most recently processed window, as `YYYY-MM-DD`. Omitted when none has been processed.
    - `last_filed_period` ReportingPeriod: One Flux 10 submission window for a `(kind, role)` tuple. Corrective re-submissions of the same window are separate periods sharing the window dates but with an incrementing `sequence`.
      - `id` string, required: Unique identifier of the period.
      - `siren` string, required: 9-digit French SIREN of the reporting party.
      - `flux_kind` 'tx' | 'py', required: Report kind: - `tx` - Transactions (invoice data). - `py` - Payments.
      - `role` 'seller' | 'buyer' | '', required: Role the reporting party plays for the transactions in this period. Empty for B2C-only periods. - `seller` - The party is the supplier. - `buyer` - The party is the customer.
      - `period_start` string, required: First day of the reporting window, as `YYYY-MM-DD`.
      - `period_end` string, required: Last day (inclusive) of the reporting window, as `YYYY-MM-DD`.
      - `sequence` integer, required: Submission sequence for the window. `1` is the initial report; higher values are corrective re-submissions.
      - `previous_period_id` string: ID of the prior sequence for the same window. Omitted for sequence 1.
      - `status` 'generated' | 'submitted' | 'filed' | 'rejected', required: Lifecycle status of the period: - `generated` - XML built, not yet sent to the PPF. - `submitted` - Sent to the PPF, awaiting acknowledgement. - `filed` - Accepted by the PPF. - `rejected` - Rejected by the PPF.
      - `flux_code` string: PPF flux filename assigned when the report was submitted. Omitted before submission.
      - `ack_ref` string: PPF acknowledgement status code once received (`300` filed, `301` rejected). Omitted while awaiting acknowledgement.
      - `submitted_at` string, date-time: When the report was submitted to the PPF. Omitted before submission.
      - `created_at` string, date-time, required: When the period was created.
      - `updated_at` string, date-time, required: When the period was last updated.

## Other responses

- `400`: The request is malformed or missing required parameters.
- `401`: Missing or invalid authentication token.
- `404`: The referenced silo entry or its party registration could not be found. The party must be registered before submitting the OTP.
- `500`: An unexpected server-side error occurred.

---

[API](https://skmtc.dev/invopop/apis/access-service-api.md) - [All operations](https://skmtc.dev/invopop/apis/access-service-api/llms.txt) - [OpenAPI document](https://skmtc.dev/invopop/apis/access-service-api/revisions/fc954f96ea62?raw)