Code lists
Stay organized with collections
Save and categorize content based on your preferences.
This section describes the enumerated types used throughout the invoice
request and response documents. The UBL standard does not define enum types
as part of its standard. Therefore, we use defined enums where possible,
based on publicly used standards, extending these standards with our custom
values only when necessary.
Batch file status code
This enumerated type provides further clarification for the response file
error handling for the
<ApplicationResponseBatch>/<FileStatus>.
| Status Code |
Description |
Expected Actions |
| S |
No issue, file processed |
Success |
| E |
File processing error (Decryption error, can't open file) |
Manual Intervention |
| D |
Duplicate file |
No action needed |
Status reason code
This enumerated type provides further clarification for the cbc:StatusReasonCode
field. We use a combination of the Status Reason codes
and Status Clarification Reason codes
from Peppol BIS 3.0 standard,
supplemented with our own definitions where necessary.
| Status Reason Code |
Description |
Expected Actions (Entity Specific) |
| NON |
No issue |
Success |
| REF |
Incorrect References (incorrect or missing buyer tax information) |
Failure + Revise/Rebill |
| TER |
Past time constraint to process the invoice. Note: Google extension |
Failure + Revise/Rebill |
| SVE |
Invoice Request Syntax Violation, Invalid format, missing information |
Manual Intervention |
| CER |
Communication/Transient Error - vendor will retry the request. Note: Google extension |
Wait & See |
| OTH |
Reason for status is not defined by code |
Manual Intervention |
| PEN |
Invoice generation pending. Note: Google extension |
Wait & See |
| COM |
Permanent Communication Failure - vendor will NOT retry the request. Note: Google extension |
Manual Intervention |
| REJ |
Backend system rejection, fatal |
Manual Intervention |
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-11-14 UTC.
[[["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 documentation outlines enumerated types for invoice requests and responses, clarifying file and status codes.\u003c/p\u003e\n"],["\u003cp\u003eIt leverages public standards like Peppol, extending them with custom values when necessary for Google-specific needs.\u003c/p\u003e\n"],["\u003cp\u003eBatch file status codes indicate successful processing, errors requiring manual intervention, or duplicate files.\u003c/p\u003e\n"],["\u003cp\u003eStatus reason codes provide details about invoice processing outcomes, including success, rejections, and pending statuses.\u003c/p\u003e\n"],["\u003cp\u003eThese codes guide users on expected actions, such as revising invoices or waiting for further processing.\u003c/p\u003e\n"]]],[],null,["# Code lists\n\nThis section describes the enumerated types used throughout the invoice\nrequest and response documents. The UBL standard does not define enum types\nas part of its standard. Therefore, we use defined enums where possible,\nbased on publicly used standards, extending these standards with our custom\nvalues only when necessary.\n\nBatch file status code\n----------------------\n\nThis enumerated type provides further clarification for the response file\nerror handling for the\n[`\u003cApplicationResponseBatch\u003e/\u003cFileStatus\u003e`](/invoice-vendor-interface/schema/invoice-response/batching).\n\n| Status Code | Description | Expected Actions |\n|-------------|-----------------------------------------------------------|---------------------|\n| S | No issue, file processed | Success |\n| E | File processing error (Decryption error, can't open file) | Manual Intervention |\n| D | Duplicate file | No action needed |\n\nStatus reason code\n------------------\n\nThis enumerated type provides further clarification for the [`cbc:StatusReasonCode`](/invoice-vendor-interface/schema/invoice-response/response-schema#31_response)\nfield. We use a combination of the [Status Reason codes](https://docs.peppol.eu/poacc/upgrade-3/codelist/StatusReason/)\nand [Status Clarification Reason codes](https://docs.peppol.eu/poacc/upgrade-3/codelist/OPStatusReason/)\nfrom [Peppol BIS 3.0 standard](https://docs.peppol.eu/poacc/upgrade-3/),\nsupplemented with our own definitions where necessary.\n\n| Status Reason Code | Description | Expected Actions (Entity Specific) |\n|--------------------|---------------------------------------------------------------------------------------------|------------------------------------|\n| NON | No issue | Success |\n| REF | Incorrect References (incorrect or missing buyer tax information) | Failure + Revise/Rebill |\n| TER | Past time constraint to process the invoice. Note: Google extension | Failure + Revise/Rebill |\n| SVE | Invoice Request Syntax Violation, Invalid format, missing information | Manual Intervention |\n| CER | Communication/Transient Error - vendor will retry the request. Note: Google extension | Wait \\& See |\n| OTH | Reason for status is not defined by code | Manual Intervention |\n| PEN | Invoice generation pending. Note: Google extension | Wait \\& See |\n| COM | Permanent Communication Failure - vendor will NOT retry the request. Note: Google extension | Manual Intervention |\n| REJ | Backend system rejection, fatal | Manual Intervention |"]]
