Modelo 347 in Spain: Annual Operations Declaration Guide

Modelo 347 is Spain's annual informative declaration (declaración informativa) that requires every business and professional to report all operations with any single third party exceeding €3,005.06 (VAT included) during a calendar year. The declaration is filed with Spain's Tax Agency, the Agencia Tributaria (AEAT), and serves as one of the country's primary tools for detecting unreported income and VAT fraud.

The €3,005.06 threshold is not arbitrary. It is the euro equivalent of 500,000 Spanish pesetas, converted at the fixed rate established when Spain adopted the euro in 2002. The figure has never been rounded or adjusted, which is why it remains an odd number more than two decades later.

What makes Modelo 347 unusual among EU reporting requirements is its dual-reporting mechanism: both the buyer and the seller must independently declare the same transactions. If your company pays a supplier €15,000 over the course of a year, you report that total on your Modelo 347, and the supplier reports the same €15,000 on theirs. The AEAT then cross-references both declarations. When the figures do not match, the agency flags the discrepancy for investigation. This mirror-image design makes Modelo 347 one of Spain's most effective compliance instruments because evasion requires both parties to coordinate their misreporting.

The legal basis for the declaration sits in Article 93 of Spain's General Tax Law (Ley General Tributaria) and the detailed filing rules established by Royal Decree 1065/2007.

Who must file: any business, self-employed professional (autónomo), or entity whose aggregate operations with a single counterparty exceed €3,005.06 in a calendar year. The obligation applies regardless of whether the filer is the buyer or the seller in those transactions. Covered operations span a broad range:

Sales and purchases of goods
Provision and receipt of services
Lease payments and receipts
Subsidies received
Insurance operations

The threshold is calculated per counterparty across the full calendar year, not per invoice. A business that issues twelve monthly invoices of €300 each to the same client has reached €3,600 in aggregate and must report that relationship. The per-transaction amounts are irrelevant; only the annual cumulative total with each third party matters.

The €3,005.06 Threshold: From Pesetas to Euros

Why €3,005.06 and not a round number? Before Spain adopted the euro, the threshold stood at 500,000 Spanish pesetas. At the fixed conversion rate of 1 EUR = 166.386 ESP, that translated to exactly €3,005.06. The figure has never been updated, leaving every business in Spain measuring its obligations against a remnant of a currency retired over two decades ago.

How the Threshold Calculation Works

The rules for determining whether a counterparty crosses the €3,005.06 line are straightforward, but each one matters:

Aggregate all transactions with a single counterparty across the full calendar year. You are not evaluating individual invoices. You are evaluating the cumulative total per NIF (tax identification number) from January 1 through December 31.
Include VAT in the total. The relevant figure is the gross amount, not the net. A €2,800 net invoice with 21% IVA becomes €3,388 for Modelo 347 purposes. Failing to include VAT when measuring against the threshold is one of the most common preparation errors.
Once the aggregate exceeds €3,005.06, you must declare every transaction with that counterparty. This is an all-or-nothing rule. You do not report only the amount above the threshold. If the total crosses the line, all transactions with that counterparty for the entire year become reportable.
Break down the annual total by calendar quarter. Even though the threshold is measured annually, the declaration itself requires a quarterly split of the reported amounts (Q1, Q2, Q3, Q4).

Worked Example: Two Suppliers, Two Outcomes

Consider a consulting firm in Madrid that works with two regular suppliers during 2025.

Supplier A (office supplies) invoices the following gross amounts (VAT included):

Q1: €800
Q2: €650
Q3: €900
Q4: €750
Annual total: €3,100

Since €3,100 exceeds the €3,005.06 threshold, the firm must report all four quarters of transactions with Supplier A in its Modelo 347 filing, broken down as shown above.

Supplier B (courier services) invoices:

Q1: €700
Q2: €800
Q3: €600
Q4: €800
Annual total: €2,900

Since €2,900 falls below €3,005.06, there is no reporting obligation for Supplier B. None of these transactions appear in the declaration.

Note the narrow margin. Supplier A exceeded the threshold by less than €95. A single additional invoice from Supplier B in any quarter would have pushed that relationship over the line as well. This is why tracking cumulative counterparty totals throughout the year, rather than checking only at year-end, prevents last-minute surprises when the filing deadline approaches.

Dual Reporting: How Spain Cross-References Buyer and Seller Declarations

What makes Modelo 347 distinctive among EU tax declarations is its dual-reporting architecture. Both the buyer and the seller must independently report transactions exceeding the threshold with the same counterparty. AEAT then cross-references these parallel declarations to detect discrepancies, creating a self-policing system where both parties have a direct incentive to report accurately.

The mechanism works through NIF (Número de Identificación Fiscal) matching. Consider a straightforward scenario: Company A invoices Company B for a total of €12,000 during the calendar year. In its Modelo 347 filing, Company A declares, "I invoiced Company B a total of €12,000." Separately, Company B files its own declaration stating, "I received invoices totaling €12,000 from Company A." AEAT matches both declarations using the NIF identifiers. When the reported amounts align, no further action is taken. When they differ, both parties may receive an inquiry requesting clarification and supporting documentation.

Underreporting or omitting a counterparty carries real risk. Even if one party fails to declare, the other party's filing will flag the relationship to AEAT. Neither side controls both halves of the data, so any attempt to suppress transaction volumes is likely to surface as a mismatch.

Handling timing discrepancies. One of the most common sources of legitimate mismatches involves year-end invoicing. An invoice issued by Company A on December 28 may not be recorded in Company B's accounting system until January of the following year. Company A reports the transaction in its current-year Modelo 347, while Company B includes it in the next year's filing. The result is a genuine discrepancy between their respective declarations for the same tax period.

AEAT generally recognizes these timing differences as normal business occurrences, but they can still generate a query. Businesses should retain clear documentation, such as invoice dates, delivery confirmations, and accounting entry timestamps, to explain any year-end timing gaps if questioned. Proactively reconciling December transactions with key counterparties before filing can reduce the likelihood of unnecessary inquiries.

This dual-reporting approach is not unique to Spain in concept. Other EU member states have implemented similar cross-referencing mechanisms to strengthen tax compliance. The Czech Republic's kontrolní hlášení VAT control statement, for instance, requires detailed transaction-level reporting that enables the Czech tax authority to perform comparable cross-referencing, though that system operates on a monthly cycle rather than Spain's annual one. The shared principle is the same: when both sides of a transaction report independently, the data becomes far more difficult to manipulate.

Required Data and Quarterly Breakdown

For each counterparty that crosses the €3,005.06 threshold, businesses must report a specific set of data fields in their Modelo 347 declaration. Missing or incomplete information on any single counterparty can trigger discrepancies when AEAT cross-references declarations, so accuracy here is non-negotiable.

The required data per counterparty includes:

NIF (Número de Identificación Fiscal): The tax identification number of the counterparty. For Spanish entities this is the standard CIF or NIF; for EU counterparties, the intra-community VAT number applies.
Full name or business name: The legal name exactly as registered with AEAT, not a trade name or abbreviation.
Province code: The two-digit code corresponding to the counterparty's registered province within Spain.
Total annual amount (including VAT): The aggregate value of all operations with that counterparty during the calendar year, VAT included.
Quarterly breakdown: The annual total disaggregated into four calendar quarters (Q1: January–March, Q2: April–June, Q3: July–September, Q4: October–December).
Cash payment flag: A specific indication if cash payments received from or made to that counterparty exceed €6,000 during the calendar year.

The quarterly breakdown requirement is where many businesses encounter difficulties. AEAT does not accept a single annual figure per counterparty. Instead, the total must be split across Q1 through Q4 based on when each transaction occurred. Accounting systems need to track the timing of every invoice and payment throughout the year, not just a running annual aggregate. Businesses that reconcile supplier and customer accounts only at year-end often find themselves reconstructing quarterly totals retroactively, a process that is both time-consuming and error-prone.

Cash payment reporting above €6,000 is a separate obligation layered on top of the standard counterparty data. If the total cash payments (not total operations, specifically cash) with any single counterparty exceed €6,000 in the calendar year, this must be explicitly flagged within the declaration. Spain introduced this requirement as part of its anti-fraud measures to increase visibility into large cash transactions. The flag applies regardless of the total transaction volume with that counterparty; even if total operations are well above the €3,005.06 threshold, the cash-specific reporting only activates when cash payments alone surpass €6,000.

The declaration is filed electronically through AEAT's Sede Electrónica platform. Access requires either a digital certificate (certificado digital) or a Cl@ve PIN. The electronic submission format accommodates all per-counterparty fields listed above, including the quarterly amounts and the cash payment indicator, in a structured record layout. Paper filing is not available for Form 347; all submissions must go through the electronic channel.

Filing Deadline, Penalties, and Enforcement

Modelo 347 must be filed by the last day of February following the calendar year being reported. Operations carried out during 2026, for example, must be declared by February 28, 2027. When February 28 falls on a weekend or public holiday, the deadline extends to the next business day.

Penalty Structure

AEAT applies a structured penalty regime for Modelo 347 non-compliance, calculated per data item rather than as a flat fine:

€20 per missing or incorrect data item reported in the declaration
Minimum penalty of €300 per declaration, regardless of how few errors exist
Maximum penalty of €20,000 per declaration, capping exposure for large-volume filers

The timing of your filing relative to AEAT contact significantly affects the penalty amount:

Late filing before AEAT requests the declaration: Penalties are reduced by 50%. A declaration containing 30 errors that would normally trigger a €600 penalty (30 × €20) would instead result in a €300 charge.
Late filing after AEAT has formally requested the declaration: Full penalties apply with no reduction. At this stage, AEAT considers the omission to have moved beyond a simple oversight.

Voluntary corrections submitted before AEAT initiates any inquiry generally receive more favorable treatment than amendments prompted by an official request or investigation. A complementary declaration (declaración complementaria) adds previously omitted counterparties or amounts to the original filing, while a substitutive declaration (declaración sustitutiva) replaces the entire original. Filing either on your own initiative demonstrates good faith and typically results in reduced sanctions compared to corrections made under regulatory pressure.

Enforcement Reality

These penalties are not theoretical. According to Spain's Tax Agency annual report, in 2024 Spain's Tax Agency concluded nearly 2 million internal tax control activities, representing a 4.39% increase over the previous year. Informative declarations like Modelo 347 feed directly into these control processes, providing AEAT with the cross-referencing data it needs to flag discrepancies between buyers and sellers. When your declared figures do not match those reported by your counterparties, automated systems can generate verification requests without any human analyst needing to manually review your file.

Exemptions and Modelo 347's Place in the Spanish Tax Reporting Ecosystem

Modelo 347 does not apply universally. Several categories of businesses and transactions are explicitly exempt from the annual declaration, and understanding these exemptions requires mapping how Modelo 347 fits within Spain's broader tax reporting infrastructure.

Who Is Exempt from Filing

Businesses enrolled in SII (Suministro Inmediato de Información). SII participants submit detailed invoice records to AEAT within four calendar days of issuance or receipt. Because this data already flows to the tax authority in near-real-time, filing an annual Modelo 347 would be redundant. Large companies, those in the REDEME VAT refund register, and entities in certain VAT groups are required to use SII and are therefore automatically exempt from Modelo 347. One important nuance: if a business joins SII partway through the year, it must still file Modelo 347 covering the portion of the year before SII enrollment began. Only the months under SII reporting are excluded.

Businesses in the Basque Country and Navarra. The foral tax regimes of País Vasco (Álava, Bizkaia, Gipuzkoa) and Navarra operate their own tax administrations with equivalent declaration requirements. Businesses subject to these regional tax authorities file under their respective foral rules rather than submitting Modelo 347 to AEAT.

Intra-EU operations reported via Modelo 349. Transactions already declared through the Modelo 349 recapitulative statement for intra-Community supplies and acquisitions are excluded from Modelo 347. This prevents double reporting of the same operations. For businesses with significant cross-border EU trade, this exclusion can substantially reduce the scope of their Modelo 347 filing, since those counterparty volumes are already captured in the EU declaration framework.

Certain public entities. Specific government bodies and public-sector organizations that are already subject to other reporting obligations may be exempt.

Sub-threshold relationships. Any counterparty relationship where total annual operations (IVA included) do not reach €3,005.06 falls outside the filing requirement entirely.

Foreign companies with Spanish operations. A non-Spanish company operating in Spain through a registered establishment (establecimiento permanente) must file Modelo 347 for its Spanish operations using its assigned Spanish NIF. Transactions between the establishment and its foreign parent or affiliates count toward the threshold unless they are already reported via Modelo 349 as intra-EU supplies. For non-EU counterparties, the declaration uses the counterparty's foreign tax identification number with the appropriate country prefix.

How SII and Modelo 347 Interact

The SII system, introduced in 2017, represents Spain's shift toward continuous digital tax reporting. Rather than waiting for an annual declaration, SII captures invoice-level detail on a rolling basis. For AEAT, SII data is strictly superior to Modelo 347 data: it arrives faster, contains more granular information, and enables real-time cross-referencing.

The Modelo 347 SII exemption exists for exactly this reason. Requiring both would create duplicate reporting with no additional compliance value. However, the exemption only applies to businesses that are themselves SII participants. If your counterparty is on SII but you are not, you still must include transactions with that counterparty in your own Modelo 347 filing.

VeriFactu and the Evolving Reporting Framework

Spain's VeriFactu system for invoice verification adds another layer to the reporting ecosystem. VeriFactu establishes technical requirements for invoicing software, ensuring that invoice records are generated in a compliant, tamper-resistant format and can be transmitted to AEAT. As of the 2026-2027 implementation timeline, both Modelo 347 and VeriFactu obligations coexist for non-SII businesses. VeriFactu captures invoice data electronically at the point of creation, but it does not yet replace the annual aggregation that Modelo 347 provides.

Over time, as VeriFactu adoption broadens and AEAT gains access to more granular electronic invoice data in real time, the rationale for a separate annual declaration weakens. For now, however, the annual declaration remains mandatory for all businesses not covered by an explicit exemption.

Modelo 349 and Reduced Filing Scope

Businesses engaged in intra-EU trade should pay particular attention to the Modelo 349 exclusion. If you supply goods or services to EU counterparties and report those transactions on Modelo 349, those same amounts should not appear in your Modelo 347. This is a common source of confusion during preparation: the same invoice cannot be reported on both declarations.

In practice, this means that a business with a mix of domestic and EU clients will file Modelo 347 only for the domestic (and non-EU international) counterparties exceeding the threshold. The EU portion is handled entirely through Modelo 349.

Spain is not alone in demanding detailed transaction-level data for tax compliance. Across the EU, member states have developed their own electronic reporting systems with varying approaches. Portugal's e-Fatura electronic invoicing system, for example, takes a different path toward similar objectives, requiring real-time invoice communication to the Portuguese tax authority. Modelo 347 sits at the traditional end of that spectrum, functioning as an annual reconciliation tool that Spain continues to maintain alongside its more modern SII and VeriFactu systems.

Preparing Your Invoice Data for Modelo 347

Modelo 347 demands a specific kind of data work: aggregating every transaction with each counterparty, identified by NIF, across a full calendar year, broken down by quarter, with VAT included in the totals and cash payments above €6,000 flagged separately. For a business with ten suppliers and twenty clients, this is manageable. For an organization dealing with hundreds of counterparties, varying invoice formats, and mixed payment methods, it becomes a serious data management exercise.

The most effective approach is to treat Modelo 347 preparation as a year-round process rather than a January scramble.

Maintain running counterparty tallies. Track cumulative transaction values per NIF throughout the year. Each time you process an invoice, update the running total for that counterparty. By December, you already know which relationships have crossed the €3,005.06 threshold and which are approaching it.

Record the quarter at the point of transaction. Every invoice should be tagged with its corresponding quarter (Q1 through Q4) when it enters your system. Retroactively sorting hundreds of invoices by date range in January is both time-consuming and error-prone.

Segregate cash payments from the start. Flag cash transactions separately from bank transfers and card payments as they occur. Isolating cash payments after the fact, particularly when a single counterparty pays through multiple methods, is one of the most common sources of filing errors.

Reconcile against key counterparties before filing. Because Modelo 347 operates as a dual-reporting system, discrepancies between your declaration and your counterparty's will be detected. For your highest-volume relationships, compare your aggregated figures with your counterparty's records. This is far less painful in December than after the Agencia Tributaria sends a requerimiento.

Several complications arise regularly in practice. Suppliers operating through multiple branches may use different NIFs for what is effectively the same commercial relationship. Each NIF must be reported separately. Credit notes should reduce the counterparty total in the quarter the credit note is issued, not the quarter of the original invoice. And invoices received in late December but not processed until January create timing mismatches. The general rule is that the transaction date governs the reporting period, but the practical reality of processing delays means these boundary cases need explicit attention during reconciliation.

Businesses handling large volumes of invoices from diverse suppliers often rely on invoice data extraction tools to maintain organized, searchable records that support the kind of per-counterparty aggregation Modelo 347 requires. Whatever system you use, the underlying principle is the same: structure your invoice data around counterparty NIFs and quarterly periods from the moment each transaction is recorded, so that when the filing deadline arrives, the declaration is an output of your existing records rather than a reconstruction project.