POST /transactions/correct-with-credit

Creates a CorrectWithCredit business transaction from a metadata structure.

For more flexible handling of document level discounts and informative discounts on unit price use the comparable V2 route

The more parameter of the call informs the server whether additional document attachments are expected or not and then updates the message status. If no more documents will be added, the call sets the status of the message to received. Otherwise, the message remains open and the message status is notset.

The following example contains the minimum JSON body required to create a valid credit note. These elements are mandatory.

{
    "messageHandling": {
        "receiverIdentifier": "KT:2222228899",
        "fallbackEmailAddress": "[email protected]"
    },
    "creditNote": {
	    "creditNoteNo": "CN1234",
	    "issueDate": "2019-05-26T10:15:42.774Z",
	    "currencyCode": "ISK",
	    "supplier": {
	        "vatNumber": "99123",
		    "name": "Test Party One",
	        "identifier": "KT:1111118899",
            "address": {
			    "streetNameAndNumber": "42nd Street 1",
			    "city": "New York",
			    "postalZone": "10036",
			    "countryCode": "US"
		    }
	    },
	    "customer": {
		    "name": "Test Party Two",
		    "identifier": "KT:2222228899",
		    "address": {
			    "streetNameAndNumber": "14th Street 52",
			    "city": "New York",
			    "postalZone": "10011",
			    "countryCode": "US"
		    }
	    },
	    "creditNoteLines": [
		  {
		    "itemNo": "A301",
			"name": "Product A",
			"quantity": 1,
			"unitOfMeasure": {
        	    "unit": "Rec21",
        	    "code": "BX"
            },
			"unitPriceAmount": 1000,
			"taxCategoryType": "StandardRated",
			"taxableAmount": 1000,
			"taxAmount": 240,
			"taxPercentage": 24
		  }
	    ]
	}
}

The request body schema includes all mandatory and optional elements.

For more information about allowed values for metadata elements, see Metadata.