What is the RTV process at Google?
The Return to Vendor (RTV) process is initiated by an Accounts Payable (AP) agent or an invoice approver when an invoice is identified as defective or non-compliant with Google's billing requirements.
When an RTV occurs, our system automatically notifies the supplier via email, with the Purchase Order (PO) owner copied on the correspondence. This notification includes specific invoice details and the reason for the rejection.
Please note that any invoice that has undergone the RTV process will not be processed for posting or payment.
RTV Reasons & Actions to be taken| RTV reason code | Description of Error | Action Required (Step-by-Step Guidance) |
| (001) Missing/Invalid PO | The Purchase Order (PO) number is either missing from the invoice or the number provided does not match a valid Google PO. |
|
| (002) Incorrect bill-to address on Invoice | The "Bill-to" address on your invoice does not match the specific Google entity address listed on your Purchase Order. |
|
| (003) Duplicate Invoice number | Our system indicates that an invoice with this specific number has already been processed or paid. |
|
| (004) Not an Invoice | The document submitted is invalid (e.g., a Statement, Sales Order, Estimate, or Pro-forma) and cannot be processed as a tax invoice. |
|
| (005) Supplier not yet set up | You are not currently listed as an active supplier in Google's records. |
|
| (006) Google VAT/TAX ID missing/incorrect on invoice | Google's VAT or Tax ID is missing from the invoice, or the one provided is incorrect. |
|
| (007) Missing/incorrect currency on invoice | The currency listed on the invoice (e.g. USD) does not match the currency listed on the Purchase Order (e.g. EUR). |
|
| (008) Bill/Ship to mismatch | The "Bill-to" details on the invoice do not match the Google entity/location where goods were actually delivered ("Ship-to"). |
|
| (009) CGST/SGST/IGST/Compensation Cess | The invoice is missing the correct tax split (CGST/SGST/IGST) or the amounts are calculated incorrectly. |
|
| (010) Contract missing - Sponsorship | This is a sponsorship invoice, which requires a signed contract to be attached for processing. |
|
| (011) ETR receipt/ESD signature missing | The invoice is missing the required Electronic Transaction Receipt (ETR) or Electronic Signature (ESD). |
|
| (012) Future dated invoice | The invoice date listed is in the future (later than the current date). |
|
| (013) Google GSTIN missing / Invalid | The invoice does not list Google's GSTIN number, or the number listed is invalid. |
|
| (014) Hard Copy missing | This specific Google entity requires an original hard copy invoice and cannot process electronic files alone. |
|
| (015) HSN (goods) / SAC (services) codes | The invoice is missing the Harmonized System of Nomenclature (HSN) for goods or Service Accounting Code (SAC) for services. |
|
| (016) Illegible invoice | The scanned invoice is blurry, unreadable, or missing an English translation (where required). |
|
| (017) Invoice in non-local language | The invoice language or format does not comply with the local country's regulations. |
|
| (018) Missing Korean E-Tax | Korean invoices with tax require a copy of the electronic tax certificate (E-tax). |
|
| (019) Missing VAT/TAX in Local Currency | The local invoice is in a foreign currency but lacks the VAT/Tax amount equivalent in the local currency. |
|
| (020) Missing/Incorrect GST Rate | The tax rate applied (e.g., 18%) is missing or incorrect for the type of goods/services. |
|
| (021) Missing/incorrect invoice date | The "Invoice Date" field is either empty or invalid. |
|
| (022) Missing/incorrect invoice number | The invoice number is missing or does not follow local sequential numbering rules. |
|
| (025) Missing/Invalid Signature | The invoice requires a valid signature (digital or physical) but one was not found. |
|
| (026) No Conversion Rate/Amount | The invoice is in foreign currency but does not show the exchange rate used for local conversion. |
|
| (027) No Equivalent Amount in local currency | The invoice is missing the local currency equivalent for: Total Excl. Tax, Total Tax, or Total Incl. Tax. |
|
| (028) No supplier name on invoice | Your company name (Supplier Name) is missing from the invoice. |
|
| (029) Non Local Currency | The invoice uses a currency that this specific Google entity cannot process payments for. |
|
| (030) Original Invoice# missing on the credit note | A Credit Note was submitted without referencing the Original Invoice Number it cancels/refunds. |
|
| (031) Others | The rejection reason is specific to this invoice. |
|
| (032) Pages Missing | The file received is incomplete (e.g., received page 1 of 3). |
|
| (034) Supplier GSTIN missing /Invalid | Your (Supplier's) GSTIN number is missing or does not match our records. |
|
| (035) Supplier VAT/TAX ID missing/incorrect on invoice | Your (Supplier's) VAT/Tax ID is missing from the invoice. |
|
| (036) Total Mismatch | The "Total Amount" does not equal the sum of the line items + tax + freight. |
|
| (037) Turkey e-invoice received in hard copy | You submitted a PDF/Hard copy, but you are enrolled in the Turkish Revenue Authority (TRA) Portal. |
|
| (038) VAT/Tax Invoice Not Mentioned / Present | The document lacks the required title "Tax Invoice" or "VAT Invoice". |
|
| (039) VAT/TAX Not Applicable | The invoice includes tax, but the items/service should be tax-exempt. |
|
| (040) VAT/TAX rate incorrect | The tax rate applied is incorrect for the goods/services provided. |
|
| (041) Bill-to mismatch Invoice/PO | The Google entity on the invoice does not match the entity on the PO. |
|
| (042) Price mismatch | The unit price on the invoice is different from the unit price on the PO. |
|
| (043) Missing debit invoice | A Credit Note was received, but the corresponding Debit Note/Invoice has not been processed yet. |
|
| (044) Incorrect amount breakdown | The invoice lacks a clear summary of Net Amount, VAT Amount, and Total Amount. |
|
| (046) Invalid Supplier Legal Name | The Supplier Name on the invoice does not match the name in Google's system. |
|
| (049) Mismatch of information between Ariba flip invoice and the invoice submitted | The data you manually typed into Ariba does not match the PDF invoice you attached. |
|
| (050) Missing Supplier address on the invoice | Your address is missing from the invoice document. |
|
| (051) Missing Supplier PAN number | Your PAN number is missing from the invoice. |
|
| (052) E-invoice requirement is missing | You are enabled for e-invoicing but submitted a standard invoice. |
|
| (053) Supplier Address mismatch | The address on the invoice does not match the address in Google's vendor system. |
|
| (054) Missing GRA document | Ghana VAT compliance requires a GRA document. |
|
| (055) Missing E-invoicing documents | Invoice is issued for a country that mandates e-invoicing and was not submitted in accordance to country-specific requirements. |
|
| (056) Supplier Banking details mismatch | The bank account on the invoice does not match the bank account in Google's system. |
|
| (057) Missing supplier bank details | Google does not have bank details on file for the currency you are billing in. |
|
| (058) Amount mismatch between PRQ and boleto | The payment request amount does not match the Boleto amount. |
|
| (059) Invoice has been rejected by the PO owner | The Google employee who owns the PO rejected the invoice manually. |
|
| (060) Missing KRA QR code and CU Number | The invoice is missing the KRA-generated QR Code and Control Unit number. |
|
| (301) Googler Rejected - Duplicate Invoice or Already Paid | Invoice was rejected by the approver. |
|
| (302) Googler Rejected - Missing/Invalid PO | Invoice was rejected by the approver. |
|
| (303) Googler Rejected - Incorrect Amount | Invoice was rejected by the approver. |
|
| (304) Googler Rejected - Incorrect Invoice Data/Details | Invoice was rejected by the approver. |
|
| (305) Googler Rejected - See Comments | Invoice was rejected by the approver. |
|
| (901) Missing Billing Sheet Attachment | The rejected invoice belongs to Enterprise Validation Engine (EVE) scope and as is missing the billing sheet attachment. |
|
| (902) Invoice and Contract data mismatch | The rejected invoice belongs to Enterprise Validation Engine (EVE) scope and as there is a mismatch between the invoice & the contract data. |
|
| (903) Rejected due to Cut Off Activities | Invoices in Colombia must be submitted to Accounts Payables no later than on the 24th day of the month in which they were issued (e.g. invoice issued on 10th January 2026 must be submitted no later than on 24th January 2026). Invoices submitted past that day are rejected. |
|
| (904) Invoice Failed Local Compliance Validation | Invoice does not meet the local compliance requirements for the given country (e.g. it failed validation in the government portal, XML attachment is missing, etc.) |
|
| (905) Improper Submission Channel | Supplier is mandated to submit the invoices via Ariba (Ariba Mandate); invoices submitted via other channels are automatically RTVed. |
|
| (906) Confirmed Duplicate Invoice | The invoice was identified as a duplicate of a previously submitted invoice. It may happen when the same invoice is submitted multiple times. |
|
Back to top
FAQ
My invoice was RTVed - what do I do?For comprehensive guidance on resolving specific rejection codes, please refer to the table, which provides detailed explanations and recommended actions for each RTV reason.
If your query remains unresolved or you contend that an invoice was returned in error, please reach out for assistance via our Suppliers Help Page.
In instances where an invoice is marked as "Googler rejected" (reasons 301-305), please contact your designated Google Point of Contact (POC) directly for further clarification.
- Ensure the relevant PO number is clearly visible on the invoice document.
- Verify that the currency and bill-to entity specified on your invoice align with your contract.
- Confirm your invoice adheres to the invoicing requirements specific to the country of the Google entity receiving the bill.
- Maintain current supplier information (such as bank details, legal name, and POC email); promptly update your Ariba profile if any changes occur.