Stay organized with collections
Save and categorize content based on your preferences.
This document is designed to guide service providers through the integration
process, explaining how the system works and what is required for a successful
integration.
Integration overview
Our system generates invoice data, serialized to XML objects, and sends these to
service providers (hereafter referred to as vendors). Vendors process these
invoice objects by interacting with government systems for e-invoicing or
e-reporting purposes, receive government responses, and then format these
responses back into a format that our system can understand.
Key components:
Google invoice schema: Outlines how Google presents invoice data.
Application response: Specifies the format vendors should use to send
data back to Google.
Request batching: Describes the process for sending multiple invoice
objects within a single XML wrapper.
Response batching: Indicates that responses from vendors should also be
batched for efficient processing.
An illustrative diagram is provided to show how this workflow:
UBL 2.4 specification
As part of our integration framework, Google adheres to the Universal Business
Language (UBL) version 2.4 specification to standardize the format for invoices
and application responses. This ensures efficient and reliable data exchange
between Google and our vendors.
To begin integrating with Google's Invoice System, vendors should first
familiarize themselves with the invoice request schema and the batching process
used for data exchange.
While Google's implementation adheres to the UBL 2.4 specification it also
incorporates specific adaptations to optimize the exchange of e-invoicing
documents with our vendors.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-11-14 UTC."],[[["\u003cp\u003eThis guide outlines the integration process for service providers to connect with Google's Invoice System, explaining how the system functions and the requirements for successful data exchange.\u003c/p\u003e\n"],["\u003cp\u003eGoogle's system generates invoice data in XML format based on a specific schema, which vendors process by interacting with government e-invoicing systems and sending formatted responses back to Google.\u003c/p\u003e\n"],["\u003cp\u003eThe integration framework utilizes the UBL 2.4 specification for standardized data exchange, ensuring seamless communication between Google and vendors.\u003c/p\u003e\n"],["\u003cp\u003eVendors should review the provided schemas and sample files to understand the invoice request and response formats before initiating the integration process.\u003c/p\u003e\n"],["\u003cp\u003eGoogle's implementation, while adhering to UBL 2.4, includes specific adaptations to streamline the e-invoicing process with its vendors.\u003c/p\u003e\n"]]],[],null,["# Introduction to e-invoice vendor integration\n\nThis document is designed to guide service providers through the integration\nprocess, explaining how the system works and what is required for a successful\nintegration.\n\nIntegration overview\n--------------------\n\nOur system generates invoice data, serialized to XML objects, and sends these to\nservice providers (hereafter referred to as vendors). Vendors process these\ninvoice objects by interacting with government systems for e-invoicing or\ne-reporting purposes, receive government responses, and then format these\nresponses back into a format that our system can understand.\n\n### Key components:\n\n- **Google invoice schema**: Outlines how Google presents invoice data.\n- **Application response**: Specifies the format vendors should use to send data back to Google.\n- **Request batching**: Describes the process for sending multiple invoice objects within a single XML wrapper.\n- **Response batching**: Indicates that responses from vendors should also be batched for efficient processing.\n\nAn illustrative diagram is provided to show how this workflow:\n\n\n\u003cbr /\u003e\n\nUBL 2.4 specification\n---------------------\n\nAs part of our integration framework, Google adheres to the Universal Business\nLanguage (UBL) version 2.4 specification to standardize the format for invoices\nand application responses. This ensures efficient and reliable data exchange\nbetween Google and our vendors.\n\nFor detailed information on UBL 2.4, refer to the [UBL 2.4\nSpecification](https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html).\n\nGetting started\n---------------\n\nTo begin integrating with Google's Invoice System, vendors should first\nfamiliarize themselves with the invoice request schema and the batching process\nused for data exchange.\n\n- **Review invoice request schema** : [Invoice request XML schema](/invoice-vendor-interface/schema/invoice-request/invoice-schema)\n- **Understand response schema** : [Application response XML schema](/invoice-vendor-interface/schema/invoice-response/response-schema)\n- **Explore e-invoice samples** : [E-Invoice XML files and vendor responses repository](/invoice-vendor-interface/samples/request)\n\nWhile Google's implementation adheres to the UBL 2.4 specification it also\nincorporates specific adaptations to optimize the exchange of e-invoicing\ndocuments with our vendors."]]
