Friday, July 31, 2026
1 change · saas-18.3
Resolved issues and error corrections
This fix ensures German POS transaction cancellations succeed even when the original transaction record lacks receipt details. It avoids rejection by the fiscal certification service, reducing interruption risk during cancellation workflows while keeping existing receipt information unchanged when available.
Original PR description
When cancelling active transactions, the schema was forwarded as-is from the listed transaction. ACTIVE transactions can have an empty schema, and Fiskaly rejects the cancellation PUT with:
{
"code": "E_TX_NO_TYPE_DEFINED",
"message": "`schema.raw.process_type` must be defined for
updating or finishing a transaction",
"status_code": 409,
"error": "Conflict"
}
Fall back to a minimal CANCELLATION receipt schema when the transaction has no schema, while preserving any schema that is already present.
opw-6345005
Forward-Port-Of: odoo/enterprise#122130