# Business level response

# Introduction

NOTE: Business level response is often referred to as application response and should not be confused with technical receipts/acknowledgements/message level response.

A message that has been received and accepted for processing may call for an action on the receiver’s behalf. That receiver’s action may need to be reported back to a relevant party.

An example is that a technically correct invoice may be received but the receiver decides to reject the invoice for any business reason such as incorrect reference, missing purchase order number etc.

The key nature of these responses is that they report a business decision that is made on the message instance received.

# Example

Peppol BIS Invoice Response 3.1 example
<?xml version="1.0" encoding="UTF-8"?>
<ApplicationResponse xmlns="urn:oasis:names:specification:ubl:schema:xsd:ApplicationResponse-2" xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
    <cbc:CustomizationID>urn:fdc:peppol.eu:poacc:trns:invoice_response:3</cbc:CustomizationID>
    <cbc:ProfileID>urn:fdc:peppol.eu:poacc:bis:invoice_response:3</cbc:ProfileID>
    <cbc:ID>IMR-001</cbc:ID>
    <cbc:IssueDate>2021-11-01</cbc:IssueDate>
    <cbc:IssueTime>12:00:00</cbc:IssueTime>
    <cbc:Note>Free text</cbc:Note>
    <cac:SenderParty>
        <cbc:EndpointID schemeID="0088">5798000012349</cbc:EndpointID>
        <cac:PartyIdentification>
            <cbc:ID schemeID="0184">DK88776655</cbc:ID>
        </cac:PartyIdentification>
        <cac:PartyLegalEntity>
            <cbc:RegistrationName>Buyer organization</cbc:RegistrationName>
        </cac:PartyLegalEntity>
        <cac:Contact>
            <cbc:Name>Jens Jensen</cbc:Name>
            <cbc:Telephone>23232323</cbc:Telephone>
            <cbc:ElectronicMail>jj@test-company.dk</cbc:ElectronicMail>
        </cac:Contact>
    </cac:SenderParty>
    <cac:ReceiverParty>
        <cbc:EndpointID schemeID="0088">7330001000000</cbc:EndpointID>
        <cac:PartyIdentification>
            <cbc:ID schemeID="0192">987654325</cbc:ID>
        </cac:PartyIdentification>
        <cac:PartyLegalEntity>
            <cbc:RegistrationName>Seller company</cbc:RegistrationName>
        </cac:PartyLegalEntity>
    </cac:ReceiverParty>
    <cac:DocumentResponse>
        <cac:Response>
            <cbc:ResponseCode>RE</cbc:ResponseCode>
            <cbc:EffectiveDate>2018-09-24</cbc:EffectiveDate>
            <cac:Status>
                <cbc:StatusReasonCode listID="OPStatusAction">NOA</cbc:StatusReasonCode>
                <cbc:StatusReason>VAT Reference not found</cbc:StatusReason>
                <cac:Condition>
                    <cbc:AttributeID>BT-48</cbc:AttributeID>
                    <cbc:Description>EU123456789</cbc:Description>
                </cac:Condition>
            </cac:Status>
        </cac:Response>
        <cac:DocumentReference>
            <cbc:ID>inv021</cbc:ID>
            <cbc:IssueDate>2018-09-22</cbc:IssueDate>
            <cbc:DocumentTypeCode>380</cbc:DocumentTypeCode>
        </cac:DocumentReference>
        <cac:IssuerParty>
            <cac:PartyIdentification>
                <cbc:ID schemeID="0192">123456785</cbc:ID>
            </cac:PartyIdentification>
            <cac:PartyName>
                <cbc:Name>Test Company AS</cbc:Name>
            </cac:PartyName>
        </cac:IssuerParty>
    </cac:DocumentResponse>
</ApplicationResponse>

# Recommended formats

Below is a list of business level response formats recommended by us.

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/

# Supported formats

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

# OIOUBL Application Response

Specification

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

# 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.