Guidis Reinf

How to use Claude Code to prepare EFD-Reinf submissions

Use Claude Code with the assessment files on your machine to cross-check documents, highlight doubts, organize the submission data and only then move on to transmission, receipts and technical tracking of EFD-Reinf through the Guidis Reinf API.

When it makes sense

The gain shows up when the team already has XML, PDF, spreadsheets, CSV and other supporting documents, but still needs to cross-check data, resolve divergences and prepare a real API call with less manual rework.

Claude Code comes in before transmission. The intent is not to skip human review: it is to read the files first, consult the public OpenAPI, surface uncertain fields and turn the assessment into reviewable submission data before the API call.

  • Assessment files first - Claude Code can read XML, PDF, Excel, CSV and supporting documents before organizing the submission data in the integration.
  • Public contract as reference - Claude Code consults the public OpenAPI and the API documentation before building or fixing calls.
  • Confirmation before submitting - after assembling, Claude Code can point out gaps, ask for confirmation and only then proceed with submission and reading returns.

Step by step

  1. Create the API key - generate it under Administration > Access Control > API Integrations and keep it safe, as it is shown only once.
  2. Obtain the access token - exchange the API key for a token at POST /api/integracao/token before any Claude Code call.
  3. Validate the context and read the files - start with GET /v1/integracao/contexto and only then ask Claude Code to read the assessment files and the flow documents.
  4. Assemble, review and submit - use the public OpenAPI to organize the submission data, review taxpayer, environment and period, and only then transmit.

Practical example

First make sure you have the account API key and token:

POST /api/integracao/token
Authorization: Bearer YOUR_API_KEY

Base prompt for the assisted assembly:

Read the assessment files for this routine on my machine, consult the public OpenAPI of Guidis Reinf, organize the data of the flow I need to submit and highlight any uncertain field before preparing the API call.

After transmission, use the same integration to check receipts, returns, status and operational evidence.

When there is a gap, taxpayer ID divergence, ambiguous period or incomplete supporting document, ask Claude Code to stop and formulate the confirmation question before preparing the final call.

See also the full API documentation and the Codex version.