> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/aunz-pint-self-billing.md).
# AUNZ PINT SELF-BILLING
AUNZ PINT SELF-BILLING electronic document support in DocBits
{% hint style="info" %}
Check the country guide for version limits, effective configuration and the country explainer. [Australia](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/australia.md). The active family label has no fixed PINT release number. Check customization and profile identifiers; network delivery is a separate integration.
{% endhint %}
| Property | Value |
| -------------------- | ----------------------- |
| **Country / Region** | Australia / New Zealand |
| **Document Types** | Self-Billed Invoice |
| **Format** | UBL 2.1 XML |
| **Standard** | PINT A-NZ Self-Billing |
| **Locale** | `en_AU` |
AUNZ PINT Self-Billing is the self-billing variant of the A-NZ Peppol International invoice model. In self-billing scenarios, the buyer creates the invoice on behalf of the supplier. This document type follows the same PINT A-NZ structure but with reversed party roles — the `AccountingCustomerParty` becomes the invoicing party and the `AccountingSupplierParty` is the party being billed.
## Support Status
| Component | Status |
| ---------------- | ----------- |
| Preview | ✅ Supported |
| Field Extraction | ✅ Supported |
| Transformation | ✅ Supported |
## Default Preview
Default DocBits preview for an AUNZ PINT Self-Billing invoice
## Field Mapping
The field mapping is identical to [AUNZ PINT](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/aunz-pint.md) with the following key difference:
* **Party roles are reversed**: In self-billing, the buyer is the invoicing party and the supplier is the party being billed
* The `CustomizationID` contains `urn:peppol.org:pint:selfbilling-1@aunz` instead of `billing-1@aunz`
For the complete field mapping table, see [AUNZ PINT](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/aunz-pint.md#field-mapping).
## Classification Rule
DocBits detects self-billing documents by matching the `CustomizationID`:
```
urn:peppol.org:pint:selfbilling-1@aunz
```
Both self-billing and regular billing patterns classify under the `PINT A-NZ` electronic document type.
## Related
* [AUNZ PINT](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/aunz-pint.md)
* [Supported Electronic Documents](/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/edi/supported-electronic-documents/aunz-pint-self-billing.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
