El Salvador Sujeto Excluido Invoice: FSEE Guide

In El Salvador, a Factura de Sujeto Excluido (FSEE) is the buyer-issued invoice used when a VAT taxpayer buys goods or services from a supplier who is excluded from VAT registration. Under El Salvador Tax Code Article 119, the buyer, not the supplier, must issue the document, identify the excluded supplier, describe the goods or services, show the total amount, and include any applicable withholding amounts. If the invoice is issued electronically, it also has to comply with El Salvador's DTE rules.

English-language searches may also describe the same document as an El Salvador sujeto excluido invoice, an El Salvador excluded subject invoice, or an El Salvador factura de sujeto excluido. 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. The buyer-issued format now associated with Legislative Decree 191 matters because it turns what looks like a supplier-side invoicing issue into a buyer-side control process.

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

That is why FSEE is best treated as a finance-operations workflow, not a decree summary. Once the supplier falls into the sujeto excluido category, your team has to recognize the trigger, issue the document from the buyer side, capture the right IDs and transaction details, handle the withholding correctly, validate the invoice if it is electronic, and retain it as part of the purchase and tax support trail.

---

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. That is why El Salvador buyer-issued invoice rules matter to AP and accounting teams: 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 is what makes the El Salvador 13% IVA withholding sujeto excluido workflow distinctive. In several other countries, buyer withholding appears only in narrower cases or at reduced percentages. El Salvador's model is more direct: 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.

This is also why purchases from unregistered taxpayers in El Salvador cannot be treated as a mere document-label issue. Vendor status has to be checked before posting. The buyer has to generate the record. The withholding has to be calculated before payment is finalized. Then the withheld IVA has to be routed into the monthly reporting process. 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.

The Required Fields and IDs on an FSEE

For most teams, the clearest way to apply El Salvador factura de sujeto excluido requirements is as a posting checklist. The document is not just a note for the file. It is the buyer's support for the purchase, the withholding, and the downstream accounting record. If the identification fields or transaction detail are weak, the problem usually shows up later in reconciliation, tax review, or audit support.

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.

That is why El Salvador FSEE requirements work best as a control checklist, not a box-ticking exercise. The document supports the purchase itself, supports the withholding entry, and later feeds downstream reporting. 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.

---

How Electronic FSEE Fits Into El Salvador's DTE Workflow

An electronic FSEE is not just a buyer-prepared invoice saved as a PDF. Inside El Salvador's DTE environment, it is a structured tax document classified as Type 44. That means El Salvador DTE type 44 rules matter as much as the underlying commercial transaction.

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.

For the buyer, the real control point is the downstream record. Your archive, spreadsheet, or ERP record should carry the same identifying data that lets the transaction survive later review: supplier name, NIT or DUI where relevant, the purchase description, the gross amount, the withheld IVA amount, and the DTE validation reference tied to the accepted document. If those pieces do not travel together, the buyer can end up with a technically validated file that is still hard to reconcile.

That bookkeeping layer is often the missing piece in shorter explainers. Many summaries mention the rule or the DTE category, but not how the accepted Type 44 document should move into the buyer's records. If you need system-wide background first, the broader DTE system, document types, and Sello de Recepcion workflow in El Salvador gives that context. The FSEE is the buyer-issued branch of the same electronic control structure.

Invalidation, Corrections, and Identification Edge Cases

The FSEE should also be treated as its own post-issue control process. Current DTE guidance described in local practice places the electronic FSEE in the longer invalidation window, commonly described as 90 calendar days, and the practical clock runs from the Sello de Recepcion timestamp. That is materially different from the short correction windows finance teams may know from standard B2B DTE documents.

The operational takeaway is simple: correction is not a silent spreadsheet edit. If the issued electronic document contains a material error, such as 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. Updating an AP schedule without correcting the tax document does not solve the compliance problem.

That timing point matters because the deadline is anchored to the accepted electronic record, not the day the mistake is discovered internally. A review file should therefore keep the original accepted document, the reason for correction, the invalidation support, the replacement FSEE if one is issued, and the corrected accounting support that ties back to the same transaction.

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

How FSEE Differs From Buyer-Issued Models in Costa Rica, Chile, and Colombia

If your team works across Latin America, do not assume the FSEE is just another translated buyer-created invoice. El Salvador's model is distinctive because it combines three things in one workflow: a buyer-issued document for purchases from excluded subjects, a full 13% IVA withholding, and a dedicated place inside the DTE system.

That makes regional comparisons useful, but dangerous if they are treated as templates:

Country	Buyer-issued document	Main practical difference from El Salvador
El Salvador	FSEE	Buyer issues the document for purchases from a sujeto excluido, with 13% IVA withholding and DTE handling
Costa Rica	Factura electronica de compra	Buyer-issued logic exists, but the trigger and system handling are not the same as El Salvador's excluded-subject rule
Chile	Factura de compra electronica	Buyer issuance can interact with change-of-subject logic and different IVA-retention treatment
Colombia	Documento soporte	The document supports purchases from non-invoicing suppliers, but the purpose and tax handling differ from El Salvador's FSEE workflow

The comparison matters mainly as a warning. Costa Rica, Chile, and Colombia offer useful reference points, but they are not plug-in templates for El Salvador. If you are also reviewing a nearby buyer-issued invoice model for purchases from non-standard suppliers, use it to understand the family resemblance, then stop and confirm the local trigger, the local withholding rule, and the local e-invoicing path before you copy any workflow into El Salvador.

Before you post or approve an FSEE, verify:

• Supplier status: confirm the counterparty is treated as a sujeto excluido for the transaction.
• Required identifiers: confirm the supplier name, address, and NIT, DUI, or equivalent ID are complete.
• Withholding treatment: confirm the 13% IVA withholding has been calculated and shown correctly.
• DTE validation: confirm the FSEE was transmitted and accepted within El Salvador's DTE environment.
• Retention and reporting: confirm the document, proof of validation, and withholding support are retained so the transaction can survive audit and month-end review.