Business management · Tax Reporting & SPED
Double entry, a chart of accounts ready for tax layouts, ledger, balances, statements, LALUR, and tax calculations feed ECD, ECF, and EFD-Contribuições directly in the system. Each file is generated with a preview, inconsistency warnings, record counts, a SHA-256 hash, and download history. The tax calendar completes the cycle with owner, due date, and proof of delivery, while official validation, digital signing, and filing stay in the Receita Federal's PVA.
The problem and the fix
If any of these situations sounds familiar, it is because they happen in almost every graduation company, until the right system comes in.
The accounting team receives spreadsheets and has to rebuild the ledger before even starting the filing.
Bookkeeping comes from activity in the ERP itself, in double entry, with entry, lines, description, cost center, and a navigable source. ECD and ECF read the same base that produces the journal, ledger, trial balance, and statements.
An account without a type or a Receita Federal reference only shows up as an error when the deadline is almost over.
The chart of accounts stores the SPED type, summary or detail account, short code, and referential account. Generation lists incomplete accounts before the file ever reaches the PVA.
The ECD requires a chart, balances, entries, and signatories that are scattered across different systems.
The file brings together company identification, chart of accounts, referential mapping, period balances, entries, lines, statements, terms, and accountant details from records that already exist.
The ECF does not connect with the Lucro Real calculation, and the LALUR is redone in a spreadsheet.
The ECF starts from the balance sheet and the income statement, takes additions, exclusions, tax losses, and negative base from the LALUR and LACS, and builds blocks M and N when the tax bridge is available.
PIS and COFINS calculated in one place are typed again into the EFD-Contribuições.
The EFD-Contribuições reads the period's tax calculations and generates the PIS and COFINS consolidation records, warning you when there is no calculation or when the regime normally exempts the filing.
The company knows it filed, but cannot prove which file, who generated it, and which receipt matches the period.
Each generation stores period, layout, author, time, line count, warnings, content, and hash. The calendar records owner, status, and proof of delivery, without confusing generation with filing.
In practice
Everyday situations at graduation companies, from the problem to the result, using the modules on this page.
The accountant received twelve monthly spreadsheets and spent days reconciling the chart of accounts, balances, and entries before opening the PVA.
With the accounting period closed, the company generated the ECD using the active chart, the year's balances, and all posted entries. Before download, the system flagged an account without a SPED type and the accountant's CPF not yet set up.
The issues were fixed at the source, and a new generation produced the file with its own hash, ready for validation, signing, and filing in the PVA.
The IRPJ and CSLL calculation was correct, but additions, exclusions, and tax losses were tracked in a parallel spreadsheet with no link to the result.
The LALUR recorded part A, the part B balances, and the capped offset. At generation, the ECF brought together the referential chart, balance sheet, income statement, and the tax bridge in blocks M and N.
The accountant received the file along with the trail explaining how the accounting result became the tax base, leaving in the PVA only the non-accounting blocks that depend on outside information.
Every month, the calculation totals were copied by hand into another tool, creating cent-level differences and review rework.
Generation pulled the base, rate, and amount due directly from the period's PIS and COFINS calculations and built the matching tax records.
The file reached the PVA with the same numbers as the calculation trail, and any missing calculation now shows up as an explicit warning before import.
ECD, ECF, EFD-Contribuições, DCTFWeb, and regime filings had owners and deadlines scattered across messages and personal calendars.
The catalog generated the annual calendar based on regime and frequency. Each filing got an owner, due date, status, and an attached receipt or protocol.
Leadership can now see pending and late items by period, without treating a generated file as if it had already been officially filed.
How it works
Every step is a real module, and what comes out of one goes into the next without anyone typing it again.
Module by module
10 modules and 80 features on this page, all running on the same class, graduate and event records.
The filing comes from real bookkeeping, not a spreadsheet assembled at year end.
Each account already carries the attributes digital bookkeeping requires.
Chart, balances, entries, and statements combined in a text file for review in the PVA.
Accounting result, referential chart, and tax calculation connected in the same file.
The path from accounting profit to the taxable base is documented and reproducible.
PIS and COFINS come from the same tax calculation that backs the calculation trail.
Deadline, owner, status, and proof for every filing in a yearly view.
The base for supplementary returns is prepared without pretending to file automatically.
Every generation can be reviewed, traced, and reproduced before it goes to the Receita Federal.
SPED comes at the end of a controlled close, not as a substitute for one.
Compare the modules and choose the setup that fits your operation.