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:
For Hard Copy invoices:Please provide soft copy via email to [email protected] and mail the hard copy to the following address:
| Attention to | Sorting facility address |
|---|---|
| Verónica Rámos | Centro Profesional Presidente Ave. Revolución y calle Circunvalación Col. San Benito, edificios B y C, San Salvador |
- 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 JSON invoice and PDF support attachment per email.
- Send supporting documentation (if required) as a separate attachment(s), with the PDF invoice in the same email.
- JSON invoice file must be registered with government authority and must have valid signature and unexpired certificate within it per country requirements.
- Creation Date [Fecha de Generación]
- Creation Code [Código de Generación]
- Example of Extract of numbering conventions
- Provide Purchase Order (PO) number within the JSON 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.
- Do not zip or password protect attachments or files.
- Do not provide Application Response JSON files or JSON stylesheet files (files with *.css or *.xsl file extensions) along with invoice JSON.
- Do not send the PDF invoice, JSON document and any other supporting document in separated emails.
- JSONs must not have latin characters with accents. Example: Words like DISEÑO, Crédito will lead to invoice rejection.
Exception: If you have been asked to submit an EVE billing sheet, please follow those specific submission procedures, instead.
Invoices must include the following to be processed:
Supplier Info
- Supplier’s Registered Name
- Supplier’s Tax ID Number
- Supplier’s Registered Address
Google Info
- Google Bill-To Entity
- Google Bill-To Address
- Google Tax ID Number
- Google PO number
Invoice Info
- NIT
- Document Serial
- Correlative NBR
- Invoice Date
- Invoice Number
- Invoice Description of Goods including quantity and unit or Nature of Services Supplied
- Quantity and Unit Cost
- Invoice Amount (Excluding Tax), broken down to VATable, Zero-Rated, and Exempt Sales (if applicable)
- Invoice Tax Amount & Rate
- Invoice Total Amount (Including Tax)
- Invoice Currency
- Word "Invoice" displayed