> For the complete documentation index, see [llms.txt](https://docs.bullcredtech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bullcredtech.com/api-reference/apis-en/guias/dataprev-maintenance.md). # Dataprev Calendar The CLT payroll-deducted loan calendar is the official schedule that organizes the steps of the process, from simulation to remittance to the bank. It defines when each phase happens: * when the worker can take out the loan * when the company sends the information * when payroll is closed * when the bank receives the remittance Everything happens within specific windows. Therefore, during certain periods of the month, the payroll-deductible margin check may be temporarily unavailable. {% hint style="info" %} **Important** The calendar is updated annually by the government. It defines the operating pace of the CLT payroll-deducted loan, regardless of the bank or the employing company. {% endhint %} ## Why there is a Dataprev outage In CLT payroll-deducted loans, the deduction happens directly on the payroll. For this to work, the ecosystem depends on an operational flow with payroll closing, events in eSocial, FGTS Digital, and remittance to the bank. During this cycle, there is a window in which the margin check may be temporarily unavailable due to maintenance, period rollover, or system processing. In practice, this is the period commonly perceived by the market as "the Dataprev outage". ## How the closing window works For the deduction to appear correctly on the payslip, the company needs to close payroll before a deadline. ### 1. Payroll closing Around the 15th of each month, HR closes payroll. At this point, the month's deductions are calculated and sent to the official systems. After that, new contracts usually do not enter that reference period. ### 2. Issuance and payment of the DAE guide With payroll closed, the company generates and pays the DAE guide. Even before payment, the payroll deduction may already be scheduled in the system as part of the processing for the period. ### 3. Salary credit The salary is paid with the deductions already applied, usually by the 5th business day of the following month. {% hint style="success" %} **Reference period lag** The salary paid in February refers to the month worked in January. This one-month lag is essential to understand when the deduction will appear on the payslip. {% endhint %} ## What this means for the API During maintenance periods or period rollovers, the credit analysis may fail to consult the payroll-deductible margin. When the integration identifies this scenario, the API treats the unavailability as temporary. The expected behaviors are: * the `analysis_status_code` may remain as `NOT_ANALYZED` * the proposal may be routed for retry * the response may contain a friendly message guiding a new attempt after the unavailability window If the source allows Dataprev retry, the proposal tends to move to: * `DATAPREV_FAILED_AWAITING_RETRY` If the source is configured not to allow automatic retry of the Dataprev failure, the proposal may remain in: * `CREDIT_ANALYSIS_FAILED` In these scenarios, reanalysis can be done with: * [POST /proposals/{proposalId}/credit-analysis/retry](/api-reference/apis-en/proposal-flow/post-proposals-credit-analysis-retry.md) {% hint style="warning" %} **Important difference** Temporary Dataprev unavailability is not the same as the absence of a CLT employment link. When the response indicates that the customer was not found in the eligible database, the handling is different and should not be interpreted as a maintenance window. {% endhint %} ## How the partner should behave When there is a Dataprev outage or temporary instability: * do not treat the case as a definitive rejection * persist the proposal identifier for future resumption * track the result via webhook or a query in `GET /proposals/{proposalId}` * run a retry of the analysis after the unavailability window or according to the source's operational strategy ## Complete 2026 Calendar The dates below organize the monthly reference period for the CLT payroll-deducted loan, from simulation to remittance to the bank. | Reference Period | Simulation / Proposals | Bank Submission | Employer Visibility | DET Notification | Simplified eSocial | S-1200 Deadline | FGTS Guide | Bank Remittance | | ---------------- | ---------------------- | --------------- | ------------------- | ---------------- | ------------------ | --------------- | ---------- | --------------- | | `Jan/26` | `21/11-20/12` | `21/11-20/12` | `21/Dec` | `21-25/Dec` | `21-25/Dec` | `01/01-16/02` | `By 20/02` | `By 23/02` | | `Feb/26` | `21/12-20/01` | `21/12-20/01` | `21/Jan` | `21-25/Jan` | `21-25/Jan` | `01/02-16/03` | `By 20/03` | `By 23/03` | | `Mar/26` | `21/01-20/02` | `21/01-20/02` | `21/Feb` | `21-25/Feb` | `21-25/Feb` | `01/03-16/04` | `By 20/04` | `By 23/04` | | `Apr/26` | `21/02-20/03` | `21/02-20/03` | `21/Mar` | `21-25/Mar` | `21-25/Mar` | `01/04-16/05` | `By 20/05` | `By 23/05` | | `May/26` | `21/03-20/04` | `21/03-20/04` | `21/Apr` | `21-25/Apr` | `21-25/Apr` | `01/05-16/06` | `By 20/06` | `By 23/06` | | `Jun/26` | `21/04-20/05` | `21/04-20/05` | `21/May` | `21-25/May` | `21-25/May` | `01/06-15/07` | `By 20/07` | `By 23/07` | | `Jul/26` | `21/05-20/06` | `21/05-20/06` | `21/Jun` | `21-25/Jun` | `21-25/Jun` | `01/07-15/08` | `By 20/08` | `By 23/08` | | `Aug/26` | `21/06-20/07` | `21/06-20/07` | `21/Jul` | `21-25/Jul` | `21-25/Jul` | `01/08-15/09` | `By 20/09` | `By 23/09` | | `Sep/26` | `21/07-20/08` | `21/07-20/08` | `21/Aug` | `21-25/Aug` | `21-25/Aug` | `01/09-15/10` | `By 20/10` | `By 23/10` | | `Oct/26` | `21/08-20/09` | `21/08-20/09` | `21/Sep` | `21-25/Sep` | `21-25/Sep` | `01/10-17/11` | `By 20/11` | `By 23/11` | | `Nov/26` | `21/09-20/10` | `21/09-20/10` | `21/Oct` | `21-25/Oct` | `21-25/Oct` | `01/11-15/12` | `By 20/12` | `By 23/12` | | `Dec/26` | `21/10-20/11` | `21/10-20/11` | `21/Nov` | `21-25/Nov` | `21-25/Nov` | `01/12-15/01` | `By 20/01` | `By 23/01` | ## Practical summary If the analysis falls exactly within the outage window: * the margin check may fail temporarily * this does not mean the customer is automatically rejected * the correct flow is to monitor the proposal status and reprocess the analysis when the window ends To track the result, consult: * [GET /proposals](/api-reference/apis-en/queries/get-proposals.md) * [GET /proposals/{proposalId}](/api-reference/apis-en/queries/get-proposals-by-id.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.bullcredtech.com/api-reference/apis-en/guias/dataprev-maintenance.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.