TecnoSpeed's PlugDFe Electronic tax documentsPlugDFe Suite Tax components
PlugNotas Invoice issuance API
PlugStorage Fiscal Document ManagerSPED XML Automate your SPED Fiscal
DecisionIT Efficiency and safety during tax reform
PlugBank Financial Solutions HubPayment Slip API Issuance, registration, and reconciliation of payment slipsOpen Finance Statement Integration of bank statements and card invoicesAPI Pix Pix payment integrationAccounts payable Automation of the entire financial routine
Generating the SPED file requires in-depth knowledge of accounting and tax assessment, with hundreds of records and fields to be filled in. Every detail counts, and a single error can lead to serious tax problems for your clients.
With our SPED module integrated with PlugStorage, when you send the XMLs of issued and received notes, we will interpret them and generate a good part of the SPED file — with more software and less effort.
Creation of SPED blocks from the note XMLs stored in PlugStorage.
100% via API, compatible with any programming language that can make HTTP requests.
ICMS, IPI, PIS, and Cofins reconciliation within the same solution.
Sending of blocks H and K, bookkeeping of incoming notes, electronic payment links (Record 1601), LMC movement data, and configurable DePara rules.
More than 25,000 rules and validations executed during the SPED file generation.
Centralized and secure storage of XMLs, with included query for incoming notes.
Because it's integrated with PlugStorage, you have access to additional functionalities such as consulting designated notes, as well as complete security and control over your clients' fiscal documents.
Designed to provide a smooth implementation in various development environments.
Ongoing maintenance to ensure compliance with frequent changes in legislation.
Error responses are clearly decoded, speeding up precise corrections.
Developer-to-developer technical support to guide your integration and assist with Brazilian tax authority rules.
The SPED XML engine directly extracts supplier and customer data, product registration, invoice item information, taxations, applied.
Some information is not part of the fiscal XML structure and needs to be sent via API. These include: stock and inventory data (Blocks H and K), tax balances from previous periods, ICMS, IPI, PIS, and Cofins adjustments, electronic payment links (Record 1601), and, for gas stations, LMC movement data.
The workflow follows these steps: storing XMLs in PlugStorage → recording of entry notes → sending supplementary data (balances, adjustments, inventory) → initiating reconciliation via API → monitoring status and pending items → generating the final SPED file. All steps are triggered via REST routes.
Yes. It is possible to configure Webhooks per SPED client to receive automatic notifications about processing events, without needing to actively check the calculation status.
Free content produced by those who live and breathe the fiscal world day to day.
Tax and fiscal legislation, and everything a developer needs to follow to keep software compliant — explained by experts.
Prepare your software now. Practical content for IT managers and developers to navigate the changes of the biggest tax reform in decades.
