Update an e-invoicing business region
Updates an e-invoicing business region by key. The key can be the unique ID or number of an e-invoicing business region.
Note: This operation is available only if you have the E-Invoicing feature in Early Adopter phase enabled.
Authentication
Use Bearer {{token}} in the Authorization header for authentication.
Path parameters
The unqiue ID or number of the e-invoicing business region that you want to update.
Headers
Include the Accept-Encoding: gzip header to compress responses as a gzipped file. It can significantly reduce the bandwidth required for a response.
If specified, Zuora automatically compresses responses that contain over 1000 bytes of data, and the response contains a Content-Encoding header with the compression algorithm so that your client can decompress it.
Include the Content-Encoding: gzip header to compress a request. With this header specified, you should upload a gzipped file for the request payload instead of sending the JSON payload.
A custom identifier for tracing the API call. If you set a value for this header, Zuora returns the same value in the response headers. This header enables you to associate your system process identifiers with Zuora API calls, to assist with troubleshooting in the event of an issue.
The value of this field must use the US-ASCII character set and must not include any of the following characters: colon (:), semicolon (;), double quote ("), and quote (').
An entity ID. If you have Zuora Multi-entity enabled and the OAuth token is valid for more than one entity, you must use this header to specify which entity to perform the operation in. If the OAuth token is only valid for a single entity, or you do not have Zuora Multi-entity enabled, you should not set this header.
Comma separated IDs. If you have Zuora Multi-Org enabled, you can use this header to specify which orgs to perform the operation in. If you do not have Zuora Multi-Org enabled, you should not set this header.
The IDs must be a sub-set of the user’s accessible orgs. If you specify an org that the user does not have access to, the operation fails. This header is important in Multi-Org (MO) setups because it defines the organization context under which the API should operate—mainly used for read access or data visibility filtering. If the header is not set, the operation is performed in scope of the user’s accessible orgs.
The minor API version.
For a list of available minor versions, see API upgrades.
Request
The specify the unique identifier number of the legal entity or person that you do business with.
For example, you must use a GSTIN for India and Tax Identification Number (TIN) for Saudi Arabia.
The name of the Seller contact to receive e-invoicing data.
The short name of a country or region where you must comply with e-invoicing requirements. For example, IN for India. For the full list of country names and codes, see View countries or regions.
Whether the e-invoicing service provider signs PDF files for billing documents.
The X-coordinate to determine where the digital signature box is displayed on PDF files for billing documents.
The Y-coordinate to determine where the digital signature box is displayed on PDF files for billing documents.
The email address of the Seller contact to receive e-invoicing data.
The Seller’s electronic address, to which the application-level response to the e-invoice file might be delivered.
The business phone number of the Seller contact to receive e-invoicing data.
Container for e-invoicing response field mappings that map values from Sovos response data to fields on the EInvoiceData object in Zuora. Each response field mapping consists of a field name and a field path.
Note that this field is applicable only to the Sovos service provider.
For more information, see Configure e-invoicing response field mappings.
This field controls whether the invoice should be supported by the process type or not. For some countries, this field is required to be set to true. For more information, see Manage country-specific configurations.
This field controls whether the credit memo should be supported by the process type or not. For some countries, this field is required to be set to true. For more information, see Manage country-specific configurations.
This field controls whether the debit memo should be supported by the process type or not. For some countries, this field is required to be set to true. For more information, see Manage country-specific configurations.
The documents belonging to the e-invoicing business region.
The documents belonging to the e-invoicing business region.
The documents belonging to the e-invoicing business region.
The unique ID of the e-invoicing service provider that is associated to the business region.
The Seller’s VAT identifier (also known as Seller VAT identification number) or the local identification (defined by the Seller’s address) of the Seller for tax purposes, or a reference that enables the Seller to state the registered tax status.
You can define the file format for each business category as shwown in the following example:
fileFormat” : {
“B2B” : [ “XML” ],
“B2C” : [ ],
“B2G” : [ “XML” ]
}
Note: This field is optional; however, if you use Avalara integration, it becomes a mandatory field.
Response headers
This header is returned if you specify the Accept-Encoding: gzip request header and the response contains over 1000 bytes of data.
Note that only the following MIME types support gzipped responses:
application/jsonapplication/xmltext/htmltext/csvtext/plain
The request limit quota for the time window closest to exhaustion. See rate limits for more information.
The number of requests remaining in the time window closest to quota exhaustion. See rate limits for more information.
The number of seconds until the quota resets for the time window closest to quota exhaustion. See rate limits for more information.
The type of the concurrency limit, which can be Default, High-volume transactions, or Object Query.
For more information, see Concurrent request limits.
The total number of the permitted concurrent requests.
For more information, see Concurrent request limits.
The remaining number of the permitted concurrent requests.
For more information, see Concurrent request limits.
Response
The unique ID of the e-invoicing business region.
The short name of a country or region where you must comply with e-invoicing requirements. For example, IN for India. For the full list of country names and codes, see View countries or regions.
The specify the unique identifier number of the legal entity or person that you do business with.
For example, you must use a GSTIN for India and Tax Identification Number (TIN) for Saudi Arabia.
The Seller’s electronic address, to which the application-level response to the e-invoice file might be delivered.
The identification scheme identifier of the Seller’s electronic address.
The Seller’s VAT identifier (also known as Seller VAT identification number) or the local identification (defined by the Seller’s address) of the Seller for tax purposes, or a reference that enables the Seller to state the registered tax status.
The first line of the Seller’s address, which is often a street address or business name.
The second line of the Seller’s address, which is often the name of a building.
The name of the Seller contact to receive e-invoicing data.
The business phone number of the Seller contact to receive e-invoicing data.
The email address of the Seller contact to receive e-invoicing data.
The unique ID of the e-invoicing service provider that is associated to the business region.
The unique number of the e-invoicing business region.
Whether the e-invoicing service provider signs PDF files for billing documents.
The X-coordinate to determine where the digital signature box is displayed on PDF files for billing documents.
The Y-coordinate to determine where the digital signature box is displayed on PDF files for billing documents.
Container for e-invoicing response field mappings that map values from the e-invoicing service provider’s response data to fields on the EInvoiceData object in Zuora. Each response field mapping consists of a field name and a field path.
Note: This field is applicable only to the Sovos or Avalara service provider.
For more information, see Configure e-invoicing response field mappings.
The process type of the e-invoicing business region.
- If the service provider is Sovos, the process type is
ClearanceorClearanceWithCancellation. - If the service provider is Avalara, the process type is
ClearanceorPEPPOLNetwork. - If the service provider is PEPPOL, the process type is
Unknown.
The documents belonging to the e-invoicing business region.
The documents belonging to the e-invoicing business region.
The documents belonging to the e-invoicing business region.
The file format for each business category. An example response is ”[ “application/xml”, “application/vnd.oasis.ubl+xml” ]”