- Add
Documents.Document.Create
add complete mietzinsreserve to TenancyAgreement.Create.Accepted message
Add reason to Invoicing.Invoice.Deleted and Invoicing.Invoice.Cancelled messages
Add uniqueness validations to Invoicing.Invoice.Created
- creditorReference + externalReference must be unique
- dmsReference
Add booking details to Invoicing.Invoice.Booked
Invoicing.Order.Created / Updated Messages allow empty orderItems again
- Message property 'delivery_mode' replaces 'persistent' to match the AMQP specification.
- Invoicing.Order.Created#externalReference must be unique
- new message property
correlation_id
documented
Invoicing.Order.Updated
message addedbacklinkUrl
attribute added toInvoicing.Order.Created
message
Invoicing.Order.Created
message changed:description
must contain plain text, html ist not supported anymoreamount
was removed since we have orderItemsorderItems
is mandatory now and requires at least one itemorderItem.accountNumber
must NOT be prefixed with an accounting referenceorderItem.bookingAmount
added (use it instead of amount)orderItem.amount
now has the same meaning asInvoicing.Invoice.Created.invoiceItems.amount
orderItem.bookingText
is now documented (it was already supported before)
- Notification.Case.Closed message added
Corrected API - compliant with SIX SwissQRCode Standard v2.2 - now addInfo
fields are correctly nested within rmtInf
rmtInf: {
tp: ,
ref: ,
addInf: {
ustrd: ,
trailer: ,
strdBkgInf:
}
}
Until v1.16 GREM was non-compliant with SIX SwissQRCode Standard v2.2 it had defined addInf
attributes at the TopLevel of a SwissQRCode invoice
rmtInf: {
tp: ,
ref:
},
addInf: {
ustrd: ,
trailer: ,
strdBkgInf:
}