AuditSR · Audit of regressive income tax and account balances
The tax withheld on each benefit, recalculated by the accumulation period of each contribution
AuditSR rebuilds each participant's history of contributions, returns and payments and recalculates, month by month, the income tax due under the regressive regime of Lei 11.053/2004, the law that set the declining tax table for supplementary pensions, using the PEPS (first in, first out) and PMP (weighted average term) methods. The report sets side by side the rate and amount the fund withheld and those the calculation indicates, benefit by benefit.
AuditSR
Audit of regressive income tax and account balances.
- Who it is for
- Closed pension funds (EFPC) and the audit firms that work for them
- What it covers
- Recalculation of regressive income tax by PEPS and PMP, rebuilt account balances and audit modules for balances, savings reserve and contributions
- Legal basis
- Lei 11.053/2004, as amended by Lei 14.803/2024
- How it is delivered
- Web portal per fund, with spreadsheet import and scheduled upload by the fund
The rate on each payment depends on the date of each contribution
Under the regressive regime, the rate falls with the time each contribution stayed in the plan. To know whether a month's withholding is right, the calculation has to be redone with the participant's entire history.
The bracket changes every two years
The table runs from 35% down to 10%, in steps of 5 points for every two years of accumulation. An error of a few months in counting the period changes the bracket and the rate of every subsequent payment.
The history spans decades and systems
Contributions, returns and benefits of the same participant sit in old payrolls, in more than one system and in spreadsheets. Contributions made through 2004 follow a counting rule of their own.
The error repeats every month
A wrong rate at the award repeats in every income payment. By the time someone notices, the difference has built up for years, upward or downward.
Under-withholding falls on the fund
The fund is the paying source. In a tax inspection, the tax that was not withheld is charged to the fund, with an assessment penalty.
Regulation and official data
Lei 11.053/2004 sets the regressive table: 35% for an accumulation period of up to 2 years, falling 5 points every 2 years, down to 10% above 10 years. The tax withheld is final.
Source: Lei nº 11.053/2004, art. 1, items I to VI and § 2 (opens in a new tab).
For contributions made through December 31, 2004, the accumulation period counts from January 1, 2005. For later contributions, it counts from the date of the deposit.
Source: Lei nº 11.053/2004, art. 2, § 3 (opens in a new tab).
A paying source that fails to withhold the tax is subject to a 75% penalty on the total or on the difference not withheld, applied in an ex officio assessment.
Sources: Lei nº 10.426/2002, art. 9 (opens in a new tab); Lei nº 9.430/1996, art. 44, I (opens in a new tab).
In the 12 months through June 2026, closed pension funds paid R$ 96.6 billion in single-payment and continuing benefits. Tax withholding applies to each of these payments.
Where the recalculation changes the result
Situations that come up in the routine of a fund with defined contribution or variable contribution plans, and what AuditSR does in each one.
Participant with contributions made before 2005
The participant has contributed since the 1990s and opted for the regressive regime. If the count starts from the actual date of the old deposits, the rate comes out lower than the law allows.
Source: Lei nº 11.053/2004, art. 2, § 3 (opens in a new tab).
What the system does
The engine counts contributions made through December 31, 2004 from January 1, 2005, and later ones from the date of each deposit. The ledger shows which contribution each portion of the period came from.
Withdrawal or fixed-term benefit
Each payment draws on contributions of different ages. Applying a single rate, counted from the enrollment date, gives a tax different from the one due.
What the system does
Under the PEPS method, each payment draws first on the oldest contributions, and each portion drawn pays the rate for its own period. The month's effective rate is the total tax divided by the benefit.
Lifetime income
With lifetime income, the accumulation period keeps running after the award. The rate set on the benefit start date becomes outdated as the years go by.
What the system does
Under the PMP method, the system calculates the average term of the contributions, weighted by amount, up to the benefit start date and adds, for each month paid, the time elapsed since then. The month's rate comes from that term.
Preparing the fund for a tax inspection
The fund wants to know, before the Federal Revenue Service (Receita Federal) does, whether it withheld less than it should in any period, and how much. With under-withholding, the difference is charged to the paying source with a penalty.
Sources: Lei nº 10.426/2002, art. 9 (opens in a new tab); Lei nº 9.430/1996, art. 44, I (opens in a new tab).
What the system does
The tax recalculation report lists, by registration number and month, the rate and tax withheld next to the recalculated ones. The differences filter isolates only the divergent payments in the chosen period.
Beneficiary who complains about the withholding
A beneficiary questions the tax deducted from the benefit. Since the tax withheld under the regressive regime is final, the difference does not go through the beneficiary's annual tax return adjustment.
Source: Lei nº 11.053/2004, art. 1, § 2 (opens in a new tab).
What the system does
The participant ledger shows inflows, outflows, balance and tax withheld against recalculated for each month. The Recalculate button redoes the calculation for that participant only, on the spot, without waiting for the portfolio run.
Regime option made at the award
Since Lei 14.803/2024, the participant can opt for the regressive regime until the benefit is obtained or the first withdrawal, irrevocably. The fund needs to know which regime applies to each participant.
Sources: Lei nº 11.053/2004, art. 1, § 6 (opens in a new tab); Lei nº 14.803/2024 (opens in a new tab).
What the system does
The participant record keeps the history of each participant's tax regime (regressive PEPS, regressive PMP or progressive). The recalculation covers the regressive regime and applies the method recorded for the participant.
Account balance that does not reconcile
Before a withdrawal, a portability transfer or a tax calculation, the fund needs to confirm that the individual balance matches the contributions and the return of the participant's investment profile.
What the system does
The account balance report rebuilds the reserve month by month: each contribution enters the balance, which earns returns by the factor of the investment profile. The audit modules redo the DC account balance by monthly rate or by unit value change.
Savings reserve of a long-standing participant
When a participant who has contributed since the 1980s leaves, the savings reserve has to be redone from the first month, with amounts in cruzeiro, cruzado, cruzado novo, cruzeiro real and real.
What the system does
The savings reserve module rebuilds the reserve month by month, across the currency changes and applying the adjustment indexes of each period, up to the amount in reais on the calculation date.
Contribution dispute between fund and sponsor
The fund and the sponsor disagree on the contribution amount due for a period, for different groups of participants, such as active participants and beneficiaries.
What the system does
The contribution differences module determines the amount due per participant group defined by the regulations, updates the amounts by factor and issues a statement per participant.
What AuditSR does
From data loading to the differences report, on the same data and with the origin of each value kept.
Import and repository
All data first enters a review area and only then goes to the history used in the calculation.
- Five template files: participants, contributions, benefits, events and returns
- Batches by type, with status New, Processing, Updated or Failed and a processing log
- Lines received in the batch, with the associated participant and the status of each one
- Document ID and registration number normalized, forming the key that links all files
- Contributions in the same month added together, and lines already in the history ignored
- Deletion of the latest batch of each type, which reverses its effects and leaves the participants ready for recalculation
Participant ledger
The book of inflows and outflows that supports the recalculation.
- Individual, employer, additional and extraordinary contributions as inflows
- Balance accumulated and credited with returns month by month by the factor of the investment profile
- History of the return profile: conservative, moderate, aggressive or single
- Benefits paid as outflows, with the rate and tax actually withheld
- Each line points to the origin of the value in the imported history
Regressive tax recalculation
Rate and tax recalculated on each benefit paid.
- Accumulation period measured in years, from the date of each deposit
- Contributions through December 31, 2004 counted from January 1, 2005
- PEPS method for withdrawals and fixed-term benefits
- PMP method for lifetime income, with the weighted average term up to the benefit start date
- Exemption or deduction events of the month subtracted from the recalculated tax
- Recalculation of a single participant from their own screen, without waiting for the portfolio run
Account balance and failure queue
- Rebuilt reserve statement by period and registration number: transaction, return factor and balance
- List of participants whose calculation failed for lack of contributions, benefits or ledger
- Count of records in the repository against the history, by data type
- Forced loading of benefits, contributions and events and a new recalculation from the queue
- Comparison between what arrived in the import and each participant's stored history
Balance and contribution audit modules
Audit engagements configured with the rules of each plan's regulations.
- DC account balance rebuilt by monthly rate or by unit value change, in result groups
- Configurable contribution cut-off date in the month for crediting returns
- Savings reserve redone month by month since the 1980s, across the currency changes
- Contribution differences between fund and sponsor by participant group, updated by factor
- Regressive tax recalculation by PEPS or PMP within the same engagement
Supporting records
- Sponsors, with state and municipality from the IBGE table
- Pension plans and the default return profile of each one
- Return profiles and their monthly return series
- Benefit payroll items
- Regressive rate tables by period bracket
- Participants with registration number, document ID, plan, hire, enrollment and benefit start dates
From the fund's file to the differences report
Each stage records its status, and the dashboard shows how much is left in each one.
- 01
Send the data
The fund sends the spreadsheets through the portal or through the scheduled upload application. The data reaches the repository as one batch per type, without touching the history.
- 02
Promote to the history
Processing reads the batches from oldest to newest, normalizes document ID, registration number and rates, links each line to the participant and discards what already exists in the history.
- 03
Build the ledger
For each participant, contributions become inflows credited with returns month by month, and benefits paid become outflows, with the rate and tax withheld.
- 04
Recalculate the tax
The engine applies PEPS or PMP according to the participant's regime, deducts the month's events and stores the recalculated rate and tax next to the withheld ones.
- 05
Handle failures and review the results
Participants with missing data go to the failed calculations queue. Once the data is corrected, the participant returns to the ledger and is recalculated. The reports come from the same ledger.
Reports and documents
Portal reports are extracted in CSV; the audit modules issue their documents in PDF.
| Document | For whom | Contents |
|---|---|---|
| Tax recalculation | Auditors, controllership, tax team | By registration number and month: benefit, rate and tax withheld, recalculated rate and tax. Filter by period and by differences. |
| Account balance | Auditors, actuaries, benefits team | Reserve rebuilt by period and registration number: date, transaction amount, return factor and balance. |
| Participant ledger | Participant service, benefits team | Inflows, outflows, payroll item, status and tax withheld against recalculated for one participant, month by month. |
| Failed calculations | Team that sends the data | Participants who could not be calculated, with the count of records in the repository and in the history by data type. |
| Progress dashboard | Audit engagement management | Total participants, how many under PEPS and under PMP, and the progress of each processing stage, with the queue and the percentage completed. |
| Contribution differences statement | Fund and sponsor | Per participant: the contributions due in each period, updated by factor, according to the group the participant belongs to. |
| Rebuilt savings reserve | Benefits team, legal team | Monthly evolution of the reserve since the first contribution, with the currency of each period, the adjustment index and the converted amount. |
Swipe the table sideways to see all columns.
How data comes in and goes out
Template spreadsheets through the portal
The five files have an official template with an instructions tab. The fund extracts the data from its pension ERP, fills in the templates and sends them in Excel.
Scheduled upload by the fund
An application installed at the fund reads the spreadsheets from a folder, or database queries configured during implementation, sends the data on the scheduled day and time and releases the calculation on the server when the upload ends.
Results extraction
Tax recalculation, account balance, failures and the lines of each batch are exported in CSV for the audit spreadsheet.
Access and logging
- Each fund sees only its own data; every screen filters by the user's fund
- Administrator, Manager and Operator profiles for the fund's team, and separate access for the auditors
- Passwords stored as hashes and reset by a link sent by email, valid for two hours
- Key-based pairing between the server and the fund's upload application
- Each batch keeps its origin, status and processing log
- The history changes only through the promotion of batches, which can be reversed from the most recent backward
Implementation
Each implementation is parameterized for the fund: plans, sponsors, return profiles and series, payroll items, regressive tables and the format in which data leaves the pension ERP. The audit modules receive the specific rules of each plan's regulations. Datacoder supports the initial load and the review of the first results.
- Setup of the fund, plans and sponsors
- Monthly return series by investment profile
- Mapping of the pension ERP data to the five template files
- Rules from the regulations in the balance, savings reserve and contribution modules
- Upload schedule in the fund's application, when loading is automatic
- First load, handling of the failure queue and review of the reports