Skip to content
DisrupsoftDisrupsoft
General

SAP Business One electronic invoicing in Chile: DTE and SII

SAP Business One electronic invoicing in Chile: what the localization covers, how it connects to the SII, CAF folios and what to test before go-live.

SAP Business One electronic invoicing in Chile: DTE and SII

Monday, 9 a.m. A distributor has just moved from its old system to SAP Business One, and the first invoice of the day posts without a single error. By noon the customer calls: nothing has arrived. In the system the invoice has a folio number, but nobody can say whether that folio came from an SII-authorized CAF, whether the XML was sent, or whether it was rejected. The collections lead opens the SII portal and starts issuing invoices by hand "just for now".

With SAP Business One, electronic invoicing and accounting are two separate problems, and when a project goes wrong in Chile it is rarely the accounting. It breaks at the border between the ERP and the SII (Chile's tax authority): who generates the electronic tax document (DTE), where the folios live, and how the SII's response gets back to the original document. This guide covers what the Chilean localization of SAP Business One includes, what it leaves out, and what to test before go-live.

What the Chilean localization of SAP Business One includes

SAP publishes a Chile localization for SAP Business One 10.0. According to that documentation, it covers, among other things:

  • RUT (Chilean tax ID) handling for business partners.
  • Tax setup, tax codes and withholding taxes.
  • Chile-specific sales documents: exempt invoice, bill (boleta), exempt bill and export invoice.
  • Folio number assignment and checks.
  • Sales and purchase ledgers, a withholding tax report, and bills of exchange and postdated checks.

In the company details setup, SAP notes that folio numbering is always on for the Chilean localization.

What you won't find in that documentation is a section on generating, signing and sending DTEs to the SII. SAP Business One does have a generic electronic document framework (the Electronic Document Service, introduced in feature package 2208 of version 10.0), but it behaves differently by country, and you shouldn't assume it covers Chile end to end. In practice, Chilean e-invoicing is usually handled by a partner add-on or by an e-invoicing provider connected to the ERP.

So a "Folio" field on the screen doesn't mean the SII knows that invoice exists.

What the SII requires from any ERP that issues DTEs

The requirements are the same for SAP Business One, Business Central or an in-house system. If you're comparing options, we covered the same ground for Dynamics 365 Business Central and the SII.

SII requirementWhat it means for the project
DTE typesDecide which ones you issue. The official SII format codes include 33 (invoice), 34 (exempt invoice), 46 (purchase invoice), 52 (dispatch guide), 56 (debit note), 61 (credit note) and 110 (export invoice)
Authorized folios (CAF)The SII authorizes folio ranges per document type. Someone has to download them, load them into the solution and watch they don't run out
Stamp and signatureEach DTE is stamped with the CAF data and signed with a valid digital certificate
Sending and trackingSend the XML, keep the tracking number and check the result per document: accepted, accepted with objections, or rejected
Exchange with the recipientDeliver the DTE to the customer and receive their responses at the registered mailbox
Received documentsAccept or dispute supplier invoices on time

That last one often gets left out of scope. The SII's guide to accepting or disputing DTEs says the buyer has 8 calendar days from the invoice's receipt at the SII to accept or dispute it. If nothing happens, the invoice is deemed irrevocably accepted. If your ERP doesn't flag incoming supplier invoices, the clock keeps running anyway.

Four ways to connect SAP Business One to the SII

There's no single architecture. These are the most common, and what each one implies:

OptionUpsideWhat to watch
E-invoicing add-on inside SAP Business OneUsers issue and check status without leaving the ERPCompatibility with every SAP Business One upgrade, and who supports the add-on
Integrated e-invoicing providerThe provider handles CAFs, signing, sending and statusThe integration must write folio and status back to SAP; otherwise you reconcile by hand
Your SAP Business One partner's solutionThey know your database and your other add-onsKeep the ERP partner separate from whoever is accountable for the tax side
In-house developmentFull controlYour team owns schemas, certificates, SII changes and outages

Whichever you pick, there must be exactly one issuer per DTE type. If the add-on and the external provider both think they assign folios, you get duplicates or gaps. If neither does, the sale is posted with no tax document behind it.

Then there's the technical integration. SAP Business One exposes its data through Service Layer and DI API, and a solid integration writes the final folio, the SII status and any rejection reason back onto the invoice. We go into those patterns in our article on integrating systems with ERPs and banks.

Common implementation mistakes

The ones we see most in e-invoicing projects on top of an ERP:

  1. Treating the internal document number as the SII folio. SAP Business One keeps them apart, and the design has to spell out how they relate.
  2. Testing only one standard invoice. The demo works, but production breaks on the first credit note that references an old invoice, or the first dispatch guide that gets invoiced later.
  3. Nobody owns the folios. No one gets the low-folio alert, and on a Friday afternoon issuing stops.
  4. A digital certificate in the name of someone who leaves the company, with the renewal date written down nowhere.
  5. Incomplete master data: business activity, district or customer address loaded wrong in business partners, which ends in rejections.
  6. Leaving supplier invoice reception out. The 8-day dispute window doesn't wait for someone to check the inbox.
  7. Forgetting existing add-ons. If another extension also fires when a document is created or printed, they can step on each other.

What to test before go-live

A good test matrix crosses documents, situations and responses. At a minimum:

  • One taxable invoice and one exempt invoice.
  • A credit note that voids an invoice, and another that only corrects the amount.
  • A dispatch guide that is invoiced later.
  • A bill (boleta), if you sell to consumers.
  • An export invoice, if you export.
  • A deliberate rejection, for example with bad master data.
  • The low-folio warning.
  • Receiving a supplier invoice and accepting or disputing it.

For each case, check that you can follow the document end to end: the invoice in SAP Business One, the folio used, the signed XML, the SII response, the PDF with the stamp, and delivery to the customer. If any step lives only in an email, you're not ready.

Run one last test without the consultant in the room. Your accounting team needs to know where to look for a rejection and who loads new folios. And who to call when sending goes down.

Frequently asked questions

Does SAP Business One issue electronic invoices to the SII without add-ons?

The Chilean localization of SAP Business One covers RUT, taxes, folios and ledgers, but its documentation doesn't describe issuing DTEs to the SII. In most projects that part is handled by an add-on or an e-invoicing provider.

Is the SAP Business One folio number the SII folio?

Not necessarily. The tax folio has to come from a CAF the SII authorized for that document type. The project should document how it maps to the ERP's internal numbering.

What happens if I don't respond to a supplier invoice in time?

According to the SII, if you neither accept nor dispute it within 8 calendar days of its receipt, it is deemed irrevocably accepted. That's why DTE reception belongs in scope.

How we can help

At Disrupsoft we work on SAP Business One with a focus on integration, extensions and support. We can review how your ERP connects to your e-invoicing solution today, make sure the folio and status flow back to the document in SAP, and build dashboards to track rejections and pending items. See our SAP service and tell us where your project stands.

SAP Business OneFacturacion ElectronicaERP PymesIntegracionesImplementacion ERP

← View more articles