El Salvador Sujeto Excluido Invoice: FSEE Guide

In El Salvador, a Factura de Sujeto Excluido (FSEE) is the buyer-issued invoice an IVA taxpayer uses when buying goods or services from a supplier excluded from IVA registration. El Salvador Tax Code Article 119 requires the buyer to issue the document, identify the supplier, describe the purchase, show the amount and any withholding, and follow DTE rules when the invoice is electronic.

English-language teams may call it a sujeto excluido invoice, an excluded-subject invoice, or simply the Salvadoran FSEE. The label changes, but the practical question does not: when does the buyer have to create the tax document instead of waiting for a standard supplier invoice?

In practice, a sujeto excluido is a supplier outside the ordinary IVA-invoicing flow for the transaction. That can include a person operating below the VAT-registration threshold or a person or entity carrying out activities treated as excluded from IVA.

You most often run into this rule when a business is:

• buying produce or raw inputs from a small farmer who does not issue a standard VAT invoice
• paying an informal supplier for materials, transport, or incidental purchases
• hiring an unregistered individual for field labor, repairs, cleaning, or another ad hoc service

Once the supplier falls into the sujeto excluido category, the buyer has to issue the FSEE, capture the supplier IDs and purchase detail, show the withholding, validate the DTE when electronic, and keep the support with the purchase record.

---

When the Buyer Must Issue the FSEE and Withhold 13% IVA

The decision rule is practical. If you are buying from a sujeto excluido and your company is the IVA taxpayer on the transaction, you should stop waiting for a normal supplier tax invoice and move into a buyer-issued FSEE workflow instead. For AP and accounting teams, the key point is that the compliance burden shifts to the buyer.

Not every small supplier should automatically be treated this way. The point is to confirm the supplier's status and the nature of the transaction before posting the purchase. But once the transaction falls into the regime, the workflow changes in a meaningful way. The buyer creates the document, and the buyer also handles the IVA withholding that goes with it.

Just as important, do not use an FSEE when the supplier should issue the normal tax document for the transaction. As a working rule, the buyer should not substitute an FSEE when:

• the supplier is registered for IVA and can issue its own regular invoice or fiscal document
• the transaction belongs to a different document workflow rather than a purchase from a sujeto excluido
• the buyer has not yet confirmed the supplier's status and is only assuming the counterparty is excluded because it is small or informal

For FSEE transactions, the headline tax consequence is the 13% IVA withholding. That withholding is what makes the FSEE workflow materially different from many buyer-issued invoice regimes: the buyer-issued document and the full IVA withholding are part of the same process.

In operational terms, teams usually need the file to show three values clearly:

• the transaction amount
• the 13% IVA withheld by the buyer
• the amount ultimately settled to the supplier

Those amounts have to reconcile across the document, the payment support, and the tax file. If they do not, the problem rarely stays isolated to one stage. It spills into month-end review, withholding workpapers, and the monthly F-07 return (El Salvador's VAT return).

A compact worked example helps. If the purchase amount is $1,000, the 13% IVA withholding is $130. The FSEE should make the $1,000 transaction amount and the $130 withheld amount explicit, and the payment and tax support should show how that withholding was carried through the buyer's records.

Before posting, confirm the vendor status, generate the FSEE, calculate the withholding, separate it before payment, and carry the withheld IVA into the monthly reporting file. If you need the broader context around withholding mechanics, El Salvador's wider IVA and income-tax withholding rules for invoice payments gives the wider framework, but for an FSEE the core operational point is simpler: the buyer documents the purchase and carries the withholding through to reporting.

A workable buyer sequence looks like this:

1. Verify the supplier's status and confirm the purchase belongs in the sujeto excluido regime.
2. Issue the FSEE as the buyer-issued invoice instead of expecting a normal supplier VAT invoice.
3. Calculate the 13% IVA withholding and show it clearly on the document.
4. Route the transaction through payment and accounting with the withheld amount separated cleanly.
5. Carry the same values into the F-07 support and tax reporting file.

FSEE Fields, DTE Validation, and Records to Retain

For most teams, the clearest way to apply the FSEE rules is as a posting checklist. The document is the buyer's support for the purchase, the withholding, and the downstream accounting record.

The most useful checklist is:

• Excluded supplier name: record the supplier's full legal or commercial name as verified by the buyer.
• Excluded supplier address: include the address that identifies the supplier tied to the transaction.
• Supplier identification number: capture the identifier that actually fits the supplier.
  • NIT is the tax identification number.
  • DUI is the Salvadoran national identity document used for individuals.
  • If neither applies, use a passport or other document that identifies the supplier clearly.
• Issue date: the date should match the transaction and reporting period the buyer is documenting.
• Description of the goods or services: describe what was purchased with enough precision that another reviewer could understand the transaction without guessing.
• Transaction amount: show the total amount of the operation clearly.
• Withholding amount: show the retained IVA as its own field rather than leaving the reviewer to infer it from the payment result.
• Electronic validation reference when applicable: if the FSEE is issued electronically, retain the DTE validation reference and timestamp with the document record.

Line-item detail matters whenever it is needed to make the purchase intelligible. A compliant-looking header is not enough if the body says only "services" or "purchase." The description should tell a reviewer what was bought, in what quantity or scope, and why this specific supplier was treated as a sujeto excluido for the transaction.

A mismatch between the FSEE name, the ID number, the transaction description, and the withholding field creates avoidable exceptions.

One practical warning for English-speaking reviewers: do not import lighter recipient-identification logic from other DTE scenarios into this document. Some transactions in the broader system may have reduced recipient-data requirements in limited situations, but an FSEE still depends on clearly identifying the excluded supplier because the buyer is issuing the document on that supplier's behalf.

If you want a fast approval rule, use this one: no FSEE should be posted until the supplier can be identified, the transaction can be understood from the description, and the total amount ties cleanly to the withholding field.

Inside El Salvador's DTE environment, an electronic FSEE is a structured tax document classified as Type 44. That means the Type 44 DTE rules matter as much as the underlying purchase.

For finance teams, the operational flow usually looks like this:

1. Confirm the supplier's identity details, the description of the goods or services, the transaction amount, and the 13% IVA withholding that belongs on the document.
2. Generate the electronic FSEE in the DTE format required for the document type.
3. Transmit it through the DGII (Direccion General de Impuestos Internos) electronic process.
4. Obtain the Sello de Recepcion that confirms the document was received and validated in the system.
5. Retain the accepted record, along with the validation reference and timestamps, as part of the compliance trail.

That Sello de Recepcion matters, but it does not do every job. It confirms transmission and receipt within the DTE workflow. It does not, by itself, prove that the supplier was correctly treated as a sujeto excluido, that the supplier ID was captured correctly, or that the 13% withholding was calculated on the right base. In other words, DTE validation is a document-control milestone, not a substitute for tax review.

After acceptance, the Type 44 document should move into the buyer's records with the supplier ID, purchase description, gross amount, withheld IVA amount, validation reference, and timestamp. If you need system-wide background first, the broader DTE system, document types, and Sello de Recepcion workflow in El Salvador gives that context.

Invalidation, Corrections, and Identification Edge Cases

Current DTE compliance guidance places electronic FSEE in the longer invalidation group, commonly described as 90 calendar days, with timing tied to the Sello de Recepcion timestamp; verify the current table in the Ministry of Hacienda DTE compliance manual before changing a filed document.

A material error needs formal invalidation and reissuance; changing only the AP schedule does not correct the tax document. If the issued electronic document contains the wrong supplier identity, wrong amount, or wrong withholding figure, the team should follow the formal invalidation and reissuance path required by the DTE workflow.

The deadline is anchored to the accepted electronic record, not the day the mistake is discovered internally. Keep the original accepted document, the reason for correction, any invalidation support, the replacement FSEE if one is issued, and the corrected accounting support.

Identification is another common edge case. Some lower-value DTE scenarios may allow lighter recipient-data handling, but that logic does not remove the need to identify the excluded supplier on an FSEE. The document exists because the buyer is documenting a purchase from a non-VAT-registered counterparty. If the supplier cannot be identified clearly enough for the invoice, the problem needs to be resolved before issue or before the document is relied on as final support.

That is why teams should use a dedicated correction checklist for FSEE transactions:

• confirm the Sello de Recepcion date first
• determine whether the error changes the legal or tax substance of the document
• follow invalidation and reissuance when it does
• keep the corrected accounting and withholding support tied to the same document trail