Chile Acuse de Recibo Factura Electronica: 8-Day Guide

Chile acuse de recibo factura electronica is the buyer's acknowledgement that the goods or services on an electronic invoice were received. In practice, that means the buyer has moved beyond mere delivery visibility and into a status that affects tax use and later finance actions. The deadline is strict: if the buyer does nothing within 8 calendar days from the invoice's reception by the SII, the receipt is granted automatically. If the buyer files a reclamo instead, the invoice stays in reclaimed status and does not support VAT credit while the dispute remains unresolved.

That timing rule matters most when AP teams treat invoice intake as a monthly control process rather than a one-off portal task. An invoice can arrive operationally, be reviewed internally, and still sit in a legally sensitive state inside Chile's DTE system until the buyer acknowledges it, disputes it, or allows the deadline to pass. For invoices received by the SII near month-end, that gap can change whether the VAT credit is usable in the same reporting period, which is why invoices received in the final 8 days often need manual acknowledgement if the buyer wants same-month tax use.

The key point is that acuse de recibo is not just a generic internal approval note. It is a defined buyer-side event inside the DTE workflow, with downstream consequences for VAT timing, registry status, and whether the invoice is clean enough to move into later receivables or financing processes. Once you read it that way, the rest of the workflow becomes much easier to manage.

Choose the Right Buyer Action: Receipt, Acceptance, or Reclamo

One reason this topic feels confusing is that Chile's buyer-side status events are related, but they do not mean the same thing. AP teams often talk about "accepting the invoice" as if that covers every step. In the Chilean workflow, you need to separate receipt acknowledgement from content acceptance and from a dispute.

Buyer action	What it means	When to use it	Practical effect
Acuse de recibo	You acknowledge that the goods or services tied to the invoice were received	The underlying delivery or service receipt is not in dispute	Starts or confirms the receipt status the tax and assignment workflow relies on
Acceptance of content	You are not objecting to the invoice's substance	The invoice details align with what was supplied and billed	Reduces uncertainty around later commercial use of the invoice
Reclamo	You dispute the invoice or the underlying delivery/service	Quantities, values, timing, or fulfillment are wrong or incomplete	Prevents the invoice from supporting VAT credit while it remains reclaimed

If you are trying to understand how to reject an electronic invoice in Chile, the practical answer is that you do so by lodging a reclamo when there is a real dispute. That could be because the goods were not received, the service was not delivered as billed, the amount is incorrect, or the document does not match the commercial reality. A reclamo is not a soft internal comment. It is a decision with registry consequences.

Another practical distinction matters here: automatic acuse de recibo after the deadline is not the same thing as an active, deliberate review outcome. AP teams should avoid reading "no action taken" as if it were equivalent to a documented internal decision that the invoice content is correct.

This is why the Registro de Aceptacion y Reclamo de un DTE matters. It is the record that distinguishes these events instead of collapsing them into a single "approved" or "rejected" label. For finance teams, the operational lesson is simple: define the business reason for your action before you click anything. Receipt confirms receipt. Acceptance confirms lack of objection to content. Reclamo is the dispute path.

---

How the 8-Day Window Affects VAT Credit and Month-End Close

The 8-day rule matters because Chile links receipt status to credito fiscal timing, not just to document housekeeping. For AP and controllership teams, the real question is not "Did the invoice arrive?" but "What status does it have, on what date, and what does that allow us to do in the close?" That is where the Registro de Compras becomes operationally important.

The highest-risk scenario is month-end. According to SII guidance on when VAT credit can be used after acuse de recibo, unpaid electronic invoices received by the SII in the last 8 days of a month will receive automatic acuse de recibo in the following month unless the buyer records the receipt manually earlier. That means Chile VAT credit invoice receipt timing can slip simply because the buyer let the automatic clock run instead of acknowledging receipt before the period closed.

The workflow implications are easiest to see side by side:

• If the buyer acknowledges receipt in time: the invoice is positioned for same-period VAT treatment, assuming the other requirements are met.
• If the buyer waits for automatic receipt: the status may only mature after month-end, which can push the tax effect into the next period.
• If the buyer files a reclamo: the invoice remains disputed and does not support VAT credit until the issue is resolved.

This is why Chile invoice acceptance VAT credit decisions belong on the AP close calendar. Teams need to monitor invoices received near the end of the month, identify which ones are still awaiting action, and escalate them before the reporting cutoff. Otherwise, a valid supplier invoice can sit in the wrong state at the wrong time, even when nobody questions the underlying transaction.

---

Handle the Dispatch-Guide Scenario Without Misreading the Receipt Date

Some of the confusion around Chilean invoice receipt comes from treating every related document as if it triggered the same deadline. It does not. A guia de despacho may prove that goods were dispatched or delivered before the invoice itself is issued, but that does not erase the need to track when the invoice was actually received by the SII for purposes of the 8-day receipt logic.

For AP teams, this is an important control distinction. You may have operational evidence that the supplier fulfilled the order, yet still need to decide how to handle the invoice once it enters the electronic invoicing flow. If goods were delivered on March 25 but the invoice was only received by the SII on April 2, the 8-day countdown relevant to this article follows the invoice receipt event, not the earlier delivery date. Delivery evidence helps validate the transaction. It does not replace the separate buyer-side receipt event tied to the invoice record.

This is also why Chilean document workflows should be reviewed as a chain rather than as isolated files. The delivery document, the invoice, and any later dispute or acceptance event each answer a different question. Adjacent buyer-side obligations can also surface in related document scenarios, including when buyers must issue a factura de compra electronica, so teams should avoid forcing every case into a single invoice-only checklist.

---

Why Acceptance Status Matters for Factoring and Invoice Cession

Receipt and dispute status affect more than tax timing. They also matter when the invoice may be assigned, financed, or relied on as part of a receivables transaction. In Chile, that is why buyer action around the DTE is not just a clerical step. It shapes whether the invoice looks settled enough to support invoice cession and later factoring activity.

The legal backdrop is Ley 19.983, but the operational takeaway for finance teams is more practical than legalistic: an invoice that remains disputed is a weaker candidate for downstream assignment than one whose receipt and content status are clear. Automatic receipt after the 8-day period can still create that clarity, but only after the deadline has run. If a supplier is seeking earlier financing, timing and status discipline become commercially relevant.

This is one reason AP teams should treat acceptance events as control data. They are part of the same finance record as the invoice date, amount, supplier, and supporting documents. The buyer may not be the party arranging the financing, but the buyer's status choices still affect whether the invoice can move cleanly into the next stage. If you want a regional comparison, how invoice acceptance events affect factoring in Colombia shows the same broader logic in another Latin American e-invoicing environment: acceptance events are not just administrative clicks, they shape receivables usability.

---

Use an AP Checklist to Control Chilean DTE Receipt Status

For most teams, the safest way to manage this workflow is to turn it into a short recurring control:

1. Capture the date the invoice was received by the SII, not just the date the supplier emailed it or the date goods arrived.
2. Match the invoice against supporting documents, including delivery evidence and service confirmation where relevant.
3. Decide whether the case calls for receipt acknowledgement, acceptance of content, or a reclamo based on the actual business facts.
4. Review invoices that entered the system in the final 8 calendar days of the month and escalate any that still need action before close.
5. Track disputed invoices separately so nobody assumes they are available for VAT credit while the issue is unresolved.
6. Flag invoices whose status could later matter for assignment, supplier financing, or audit support.

If you need more background on the surrounding regime, start with Chile's broader DTE compliance framework and then return to this receipt workflow with the tax and timing pieces in mind. Teams that document these steps inside repeatable invoice data extraction workflows usually have a much easier time proving who received what, when it was reviewed, and whether the invoice moved into acceptance or dispute before month-end.