Update an e-reporting transaction
PATCH/api/v1/e_reportings/transactions/:id
Updates an existing transaction. When tax_subtotals are provided, they replace all existing ones.
Request
Responses
- 200
- 401
- 404
- 422
The e-reporting transaction was updated with the supplied attributes. Supplying tax_subtotals replaces the full existing set.
The request did not include a valid OAuth 2.0 bearer token.
No e-reporting transaction exists with this ID, or it belongs to a workspace the authenticated OAuth client cannot access.
The transaction payload failed validation - a missing required attribute, a category_code outside TLB1 / TPS1 / TNT1 / TMA1, a transaction_count that is not greater than 0, a date later than the current date, or a currency code - currency_code (TT-86) or any tax_subtotals[].currency_code - that names no ISO 4217 currency. Currency codes are matched case-sensitively against the two code lists Scribee vendors (the UN/CEFACT ISO3AlphaCurrencyCode enumeration unioned with the Peppol BIS ISO4217 list), so eur is refused rather than upcased. That is deliberately stricter than the PPF's own flux 10 rule F10-TX-DEVISE-G1.10, which asserts the three-letter shape alone and states in its own message that referential existence is not controlled. An omitted currency_code is never refused - the column defaults to EUR. The response body carries code: "validation_failed" and reports the failing attributes and error messages as full messages under details.base. A transaction taking part in an instalment reprise, or one the platform counted invoices into itself, cannot be changed at all: that refusal carries code: "operation_failed", a message naming the case, and no details. A transaction written only through this API or a CSV import stays editable.