> ## Documentation Index > Fetch the complete documentation index at: https://docs-pos.solya.app/llms.txt > Use this file to discover all available pages before exploring further. # Export the FEC accounting file > Returns the French FEC (Fichier des Écritures Comptables) for a date period over the per-ticket sales read model. REQUIRES `from` and `to` as `YYYY-MM-DD` with `from <= to`; a missing, malformed or inverted period returns 400. `format` defaults to `json` (the structured payload documented here: balanced entries + preview totals + the ready-to-download text); `format=file` instead streams the raw, legal tab-delimited FEC text as a `text/plain` attachment (`FEC__.txt`). Optionally narrow to a single `store`. ## OpenAPI ````yaml /openapi.json get /v1/finance/fec openapi: 3.0.3 info: title: Solya POS API version: 1.0.0 description: >- The Solya POS backend HTTP surface. Every documented operation is agent-ready: it carries an `operationId`, an agent-facing `description`, the `pos.*` scopes it enforces (`x-required-permissions`) and an `x-agent-tier`. Success responses return the payload as raw JSON; failures return the `ErrorResponse` envelope (`{ error: { code, message, statusCode } }`). servers: - url: / description: The backend, relative to its deployed origin. security: [] paths: /v1/finance/fec: get: tags: - Finance summary: Export the FEC accounting file description: >- Returns the French FEC (Fichier des Écritures Comptables) for a date period over the per-ticket sales read model. REQUIRES `from` and `to` as `YYYY-MM-DD` with `from <= to`; a missing, malformed or inverted period returns 400. `format` defaults to `json` (the structured payload documented here: balanced entries + preview totals + the ready-to-download text); `format=file` instead streams the raw, legal tab-delimited FEC text as a `text/plain` attachment (`FEC__.txt`). Optionally narrow to a single `store`. operationId: exportFec parameters: - schema: type: string in: query name: from required: false - schema: type: string in: query name: to required: false - schema: type: string in: query name: store required: false - schema: type: string in: query name: format required: false responses: '200': description: >- The structured FEC export: balanced entries, preview totals and the FEC text. content: application/json: schema: type: object properties: from: type: string to: type: string entryCount: type: integer minimum: -9007199254740991 maximum: 9007199254740991 totalDebitCents: type: integer minimum: -9007199254740991 maximum: 9007199254740991 totalCreditCents: type: integer minimum: -9007199254740991 maximum: 9007199254740991 balanced: type: boolean fileName: type: string content: type: string entries: type: array items: type: object properties: journalCode: type: string journalLabel: type: string entryNumber: type: string entryDate: type: string accountNumber: type: string accountLabel: type: string entryLabel: type: string documentRef: type: string debit: type: integer minimum: -9007199254740991 maximum: 9007199254740991 credit: type: integer minimum: -9007199254740991 maximum: 9007199254740991 required: - journalCode - journalLabel - entryNumber - entryDate - accountNumber - accountLabel - entryLabel - documentRef - debit - credit additionalProperties: false required: - from - to - entryCount - totalDebitCents - totalCreditCents - balanced - fileName - content - entries additionalProperties: false description: >- The structured FEC export: balanced entries, preview totals and the FEC text. example: from: '2026-07-28' to: '2026-07-28' entryCount: 3 totalDebitCents: 3600 totalCreditCents: 3600 balanced: true fileName: FEC_20260728_20260728.txt content: "JournalCode\tJournalLib\tEcritureNum\tEcritureDate\tCompteNum\tCompteLib\tCompAuxNum\tCompAuxLib\tPieceRef\tPieceDate\tEcritureLib\tDebit\tCredit\tEcritureLet\tDateLet\tValidDate\tMontantdevise\tIdevise" entries: - journalCode: VE journalLabel: Journal des ventes entryNumber: T-fec-1 entryDate: '2026-07-28T10:00:00.000Z' accountNumber: '411000' accountLabel: Trade receivables entryLabel: T-fec-1 documentRef: T-fec-1 debit: 3600 credit: 0 - journalCode: VE journalLabel: Journal des ventes entryNumber: T-fec-1 entryDate: '2026-07-28T10:00:00.000Z' accountNumber: '707000' accountLabel: Sales of goods entryLabel: T-fec-1 documentRef: T-fec-1 debit: 0 credit: 3000 - journalCode: VE journalLabel: Journal des ventes entryNumber: T-fec-1 entryDate: '2026-07-28T10:00:00.000Z' accountNumber: '445710' accountLabel: Collected VAT entryLabel: T-fec-1 documentRef: T-fec-1 debit: 0 credit: 600 '400': description: >- The request failed schema validation; `error.fieldErrors` lists the fields. content: application/json: schema: $ref: '#/components/schemas/ValidationErrorResponse' '401': description: No valid credential was presented — send a bearer token. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: The actor is authenticated but lacks the required `pos.*` scope. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: An unexpected server error — safe to retry idempotent requests. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - bearerAuth: [] components: schemas: ValidationErrorResponse: type: object required: - error additionalProperties: false description: >- A `VALIDATION_FAILED` envelope carrying the offending fields in `fieldErrors`. properties: error: type: object required: - code - message - statusCode additionalProperties: false properties: code: type: string enum: - VALIDATION_FAILED message: type: string statusCode: type: integer fieldErrors: type: array description: >- One entry per rejected field: the field path and why it was rejected. items: type: object required: - field - message additionalProperties: false properties: field: type: string description: Dot-path of the offending field. message: type: string description: Why the field was rejected. ErrorResponse: type: object required: - error additionalProperties: false description: The uniform failure envelope every non-2xx response returns. properties: error: type: object required: - code - message - statusCode additionalProperties: false properties: code: type: string enum: - VALIDATION_FAILED - UNAUTHORIZED - FORBIDDEN - NOT_FOUND - CONFLICT - BUSINESS_RULE_VIOLATION - INTERNAL_ERROR description: >- Machine-readable kernel `ResultCode` — branch on this, not on `message`. message: type: string description: >- Human-readable explanation. Safe to surface; never leaks server internals. statusCode: type: integer description: >- The HTTP status, mirrored into the body so a client need not read headers. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- `Authorization: Bearer `. Accepts EITHER a Keycloak access token (scopes-in-token) OR an opaque POS session token; both resolve to the same `pos.*` scope vocabulary the route guards enforce. ````