Invoicing Requirements by Country

Please make sure your invoice is accurate and complete. A few tips to keep in mind:

• send invoices after Google has received the goods or service
• reference Google's Purchase Order (PO) number, PO line number and Invoice Number on the invoice
• ensure invoice information matches information on the PO. This includes for example ‘Bill-to’ & ‘Ship-to’ locations, item description, price, and currency
• ensure the invoice date is not in the future and the invoice date reflects the date services were rendered and not the date services were first quoted
• make sure you are entering appropriate taxes in your invoices at the time of invoice submission (Including e-invoices).

The primary reasons invoices are returned to vendor are:

• A mismatch of information between the invoice and purchase order (e.g. entity, PO number, supplier name, amount, PO currency, line items)
• Missing information
• Credit memo does not reference PO number or the original invoice number

Select your bill-to country to see Google invoice requirements:

How to submit your invoice:

You can find the Spanish version here.

 

Send the invoice to [e-mail]

For suppliers mandated to provide XML and PDF invoice

• Send one XML invoice and PDF support attachment per email.
• XML invoice file must be registered with government authority and must have valid signature and unexpired certificate within it per country requirements.
• Provide Purchase Order (PO) number within the XML file as part of the locally defined recommended tags so that the invoice can be tied back to the correct PO, approved and processed in a timely manner. The PO number must also be referenced in the PDF.
• Do not zip or password protect attachments or files.
• Do not provide Application Response XML files or XML stylesheet files (files with *.css or *.xsl file extensions) along with invoice XML.
• Do not send the PDF support document and invoice XML document in separate emails.
• Do not send Guías de Despacho as a support document.
• XMLs must not have latin characters with accents. Example: Words like DISEÑO, Crédito will lead to invoice rejection.
• Chile XMLs should be encoded in ISO-8859-1 per local guidance.

For suppliers not mandated to send XML invoices

• The PDF image must be clear, legible and contain complete invoice data, including PO number (where applicable), to expedite invoice processing and payment.
• Send one valid PDF invoice attachment per email.
• Send supporting documentation (if required) as an attachment with the PDF invoice in the same email. 
• Do not zip or password protect the file.
• Do not send separate emails for PDF invoice and any supporting documentation files.

Invoices must include the following to be processed:

 

Supplier Info

• Supplier Name
• Supplier VAT ID Number
• Supplier Legal Mailing Address

Google Info

• Google Bill-To Entity
• Google Bill-To Address
• Google VAT ID Number

Invoice Info

• Invoice Date
• Invoice Description of Goods or Services Supplied
• Invoice Amount in Local Currency
• Invoice Amount (Excluding VAT)
• Invoice Total VAT amount
• Invoice Total Amount (Including VAT)
• The word "Invoice" displayed

FAQs/Additional Info

 

Who must send XML and PDF invoices?

Suppliers registered in the SII- Servicio de Impuestos Internos homer.sii.cl.

Who is exempt from sending XML invoices?

Natural persons (Services delivered with Boleta Honorario) and foreign suppliers (exempt from XML but still required to send PDF invoices).

Do I have to include digital signature in XML invoices?

Digital signatures with a proprietary certificate in XMLDsig format are mandatory.

What is the correct format of XML invoices?

The standard XML format used by Chile is DTE, Normalized XML file adopted by SII encoded in ISO-8859-1.

Technical Instructions | Valid XML Identification

Document Type and Encoding

• The standard XML format used by Chile is DTE, Normalized XML file adopted by SII encoded in ISO-8859-1.
• A Chile supplier invoice XML must have either the <EnvioDTE> parent tag as shown below or <DTE> parent tag as shown in the subsequent screenshot. They work as a container and are needed for technical validation for a valid XML.
• Encoding for the Chile XML should be in “ISO-8859-1” as shown on the first line of the XML below.
• Below is an example with <DTE> parent tag.
• XML may also have this text within <DTE> tag - xmlns="http://www.sii.cl/SiiDte"

Signature and Certificate

• Chile XML should have a valid Signature and Certificate tag as shown below.
• Certificates should not have expired, otherwise, they will fail invoice validation.
• Chile XML should end with tags as shown below.

How to Reference PO number on the invoice

• Recommend <Referencia><FolioRef> tag to be used for providing PO number on the XML file.

Extra Tags Like “Personalizados”

Chile XML should not have extra tags similar to <Personalizados> tag structure being sent at the end of the XML that SII does not approve and is outside the Chile DTE XML schema - example shown below. These extra tags cause issues with XML validation with SII. Invoice will be rejected if validation fails due to these extra tags.

 

For more information on how to update your account information or submit an invoice through the Ariba network, please go to Transacting over the Ariba network.