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)
- if the commercial invoice is attached (LATAM excluded), the commercial invoice attachments must contain the lowest level of cost itemization when submitted via the online portal specified by Google.
- if a supplier incurred Google approved third-party costs by engaging subcontractors or other entities, the supplier will submit both third-party receipts and a matching invoice with line items designated for each subcontractor or freelancer. Receipts need to be easily matched to invoice line items, and include a reconciliation document where there are multiple receipts per line item.
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 and supporting documentation:
You can find Spanish version here.
Send the invoice to [email protected].
For suppliers mandated to provide XML and PDF invoice- Send one XML invoice and PDF support attachment per email.
- Once the email with the pdfs has been sent to [email protected], no subsequent invoices should be sent in the same email thread. Instead, a new email ticket should be created to avoid further invoice processing delays.
- 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.
- Peru XMLs should be encoded in UTF-8 per local guidance and must not have latin characters with accents. Example: Words like DISEÑO, Crédito will lead to invoice rejection.
- The PDF image must be clear, legible and contain complete invoice data, including Purchase Order (PO) number (where applicable), to expedite invoice processing and payment.
- Send one valid PDF invoice attachment per email.
- Send supporting documentation (if required) as a separate attachment(s), with the PDF invoice in the same email.
Exception: If you have been asked to submit an EVE billing sheet, please follow those specific submission procedures, instead.
- 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 RUC/TAX ID Number
Invoice Info
- Invoice Date
- Invoice Description of Goods or Services Supplied
- Invoice Amount (Excluding VAT)
- Invoice Total VAT amount
- Invoice Total Amount (Including VAT)
FAQs/Additional Info
Who must send XML and PDF invoices?
Suppliers who are registered in La Superintendencia Nacional de Aduanas y de Administración Tributaria (SUNAT) sunat.gob.pe.
Who is exempt from sending XML invoices?
Public services and foreign suppliers. These suppliers are exempt from XML but still required to send PDF invoices.
Do I have to include Digital Signature in XML invoices?
Performed through a delegated signature to sign electronic payment receipts guaranteeing the integrity, security and non repudiation of electronic transactions.
What is the correct format of XML invoices?
The standard format used is the XML in UBL V2.1 adopted by the SUNAT.
Technical Instructions | Valid XML Identification
Document Type and Encoding
- The standard XML format used by Peru is the UBL V2.1 file adopted by SUNAT encoded in UTF-8. Document Type recognized is XML_UBL_INVOICE_2.
- Peru invoice XML should start with <Invoice> parent tag as shown below.
- Encoding for the Peru XML should be in “UTF-8” as shown on the first line of the XML below.
- XML must also have “PE:SUNAT” as the Agency Name within the XML to identify XML as a valid XML for validation purposes with SUNAT.
Signature and Certificate
- Peru XML should have a valid Signature and Certificate tag as shown below. Certificates should not have expired, otherwise, they will fail fiscal validation.
- Peru XML should end with tags as shown below:
How to Reference PO number on the invoice
- Recommend <OrderReference> tag to be used for providing PO number on the XML file.
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.