How does Queli Makra prepare Intrastat reports?

Queli Makra gathers the relevant records, applies the configured reporting logic, and prepares a reviewable Intrastat output with classifications and exceptions visible. A responsible compliance expert reviews the result and remains accountable for the final submission.

From operating records to a report draft

Intrastat work often depends on more than one field in one system. The workflow may need ERP transactions, supplier invoices, product information, trade direction, quantities, values, and the customer’s reporting rules. Makra brings the relevant context together, prepares the report fields, and links the output back to the source records.

When a classification is uncertain or a required value is missing, the process keeps that item in an exception route. The compliance reviewer can see which source supports a proposed value and which decision still needs attention. A suggested CN code is a prepared classification, not a declaration that the code is correct without review.

From five days to five minutes

For one automotive parts company, month-end Intrastat work meant going back through hundreds of supplier invoices. Some invoices ran to five pages and dozens of line items. An employee translated each item into Croatian, described the product and prepared the information needed to assign a CN code and net weight.

Makra now starts from the invoices already processed during the month and refreshes the relevant ERP data. It translates the item descriptions, prepares CN-code and weight suggestions and shows the uncertain lines in one review queue. Each confirmed decision becomes part of the company’s classification knowledge, so a familiar item does not return as a blank problem the following month.

The company reports that preparation fell from five days to five minutes. The compliance expert reviews the proposed classifications and confirms the final report.

Where the decision remains human

Makra can prepare the repetitive parts of the report, but the responsible compliance expert decides whether the output is ready to use. The workflow should preserve the report draft, source records, proposed classifications, changes, and approval history. It should also stop where a rule, missing fact, or low-confidence result requires judgment.

Before production, Queli and the customer agree the source systems, reporting period, field mapping, permissions, data region, retention, model configuration and review role. The workflow can then prepare the report from the company’s own records while keeping the final submission with the responsible expert.