Start with the close discrepancy queue
An agent creates value by gathering documents, linking records and preparing evidence-backed issues for the responsible team. Choose a scope: incoming invoices without matching receipts, canceled documents still linked to payables or discrepancies between inventory movements and ERP records.
Define company, establishment, period, sources and owner. This roadmap proposes operational support; it does not assume Zild calculates taxes, signs or transmits filings. Tax calculations, classification and tax decisions remain with specialized systems and responsible professionals.
Distinguish filings and source data
ECD is part of SPED and provides digital accounting books such as the journal and general ledger. EFD ICMS/IPI has its own structure: the official guide identifies Block H as physical inventory and Block K as production and inventory control. The informal phrase “inventory SPED” should not be treated as a single obligation independent of these contexts.
Before the pilot, a specialist defines applicable records, layouts and obligations for the establishment and period. Do not generalize requirements across companies. Document the data path: source document, ERP movement, related account or record and working file used for review.
Preserve documents and check critical fields
When structured documents are available, use their fields for checks and preserve the originals. OCR can help with images and receipts, but readable extraction does not establish tax validity. Link identifiers, issuer, recipient, dates, items, units and amounts to the correct record rather than relying only on filenames or free text.
Maintain version, provenance and known document state. Replacements or cancellations should update review queues and relationships traceably. Missing, duplicate or inconsistent fields should create issues; the agent should not approximate fiscal codes or tax classifications.
Reconcile inventory, production and accounting
Synthetic example: opening stock is 100 units, receipts are 40 and issues are 30. Expected stock is 110. A count of 108 leaves a two-unit discrepancy to investigate. This does not authorize an automatic adjustment: check period cutoffs, units, locations, pending documents, production consumption and returns.
Separate physical discrepancies, master-data discrepancies and bookkeeping discrepancies. A correction may require action in multiple systems with separate approval and evidence. The agent can gather the trail and propose an issue category; the owner decides remediation. Do not force figures merely to make different reports match.
Treat tax reform as a controlled change
Federal Revenue’s official guidance organizes timelines and information on tax documents and layouts for consumption tax reform. Consult the version applicable to the operation and date being assessed. Do not turn a news item or agent summary into a calculation rule or universal deadline.
Build an impact matrix: document type, transaction, affected master data, changed field or rule, official source, effective date, responsible system, test and approver. Evaluate effects on procurement, billing, pricing, receipts and reconciliation. Version configuration and test before promotion. This guide does not prescribe rates or determine a specific company’s obligations.
Deliver review evidence and validate the pilot
Each issue should identify the document, period, comparison, discrepancy and owner. Separate proposal, approval and execution. Record how the team confirms that a correction reached the source system rather than only the agent’s report. A validator accepting a file does not by itself prove the substantive correctness of all records.
Use tests for duplicates, cancellations, swapped units, period cutoffs, unauthorized access and changed layouts. Measure meaningful discrepancies found, false alerts, review time and rework. In Zild, validate document ingestion, connectors and permissions available in the environment. Expand when tax and accounting owners accept the evidence and automation boundaries.
Official references
Build an assessment using your numbers
Gather this information to scope the work with Zild. During the conversation, we assess integrations, owners and how to measure outcomes.
- A financial process and its owners
- Current costs, volume and review time
- The correct outcome and approval limits
Describe the process in the form; samples and documents can be prepared later without confidential data.
The form opens with this guide’s title. You can edit everything before sending.