# Application response

# Introduction

Application response is a document typically sent by the buyer to report the acceptance, rejection or required changes to an document from a supplier.

The application response message contains information identifying the originating business message such as reference numbers, dates, quantities and monetary amounts. It also provides trading partner information and technical error descriptions with free-form text-format capability.

# Connection to technical response

Application response has an intricate connection to the various technical response documents.

For more information about this, please see the technical response section. More specifically, the message level response and business level response subsections.

# Recommended formats

Below is a list of application response formats recommended by us.

Note

All formats recommended by us are actively maintained, based on open standards, offer good supporting documentation and validation artefacts.

# PUF Invoice Response 1.0

Pagero Universal Format (PUF) is a set of specifications based on Universal Business Language (UBL) that enables the exchange of compliant business documents worldwide via our e-business platform Pagero Online.

PUF Invoice Response is a document type that is applicable to be exchanged between buyer/receiver and supplier/issuer to inform the issuer of an invoice about business decisions.

This is often referred to as business level response.

PUF Invoice Response is developed to be compliant to the UBL 2.3 schema.

PUF Invoice Response 1.0 specification

https://pagero.github.io/puf-invoice-response/

Example files

https://github.com/pagero/puf-invoice-response/tree/master/examples

# Peppol BIS Invoice Response 3.1

Peppol Business Interoperability Specifications (BIS) are technical specifications that can be implemented in existing eProcurement solutions and eBusiness exchange services to make them interoperable between disparate systems.

Peppol BIS defines a set of information elements (business terms) and business rules to ensure that requirements are fulfilled and to clarify any option that would otherwise be left open to implementers to decide on.

They are developed and maintained by OpenPeppol and are one of the most commonly used open standards today.

Specification

https://docs.peppol.eu/poacc/upgrade-3/

Example files

Peppol%20BIS%20Invoice%20Response%203.1

# Supported formats

Below is a list of application response formats supported - but not necessarily recommended - by us.

# OIOUBL Application Response 2.01

Specification

http://www.oioubl.info/Classes/en/ApplicationResponse.html

Example files

OIOUBL%20Application%20Response%202.01

# Customer specific formats

We can build support for any proprietary/closed source format you and your ERP system may require.

For more information, please see the proprietary or closed source formats section.