Confirm Bank Transaction
Record one movement as an incasso, optionally against an invoice (AP-112).
The user's way to write a movement to the ledger. The import records only the certain matches by itself (bank_matching.certain_match); everything else lands here. The matcher ranks and explains; two invoices of the same amount both come back suggested precisely so the question reaches the person who knows the answer. An empty body means standalone income.
The incasso takes the movement's own amount and booked date rather than anything the client sends: the bank is the record of what was received and when, and a body that could restate them would let a typo move the cash-basis estimate away from the statement it is supposed to reconcile with.
409 rather than a second payment when the movement is already confirmed — a double-tap on a slow connection must not double the year's revenue. 422 carries the ledger's own refusal (a debit, an amount outside what an incasso may hold, a booked date in the future).
Request
- Base URL: https://api.taxcompass.it (the document declares no server; this is the origin it was published from)
- URL: https://api.taxcompass.it/api/autopilot/bank/transactions/{transaction_id}/confirm
- Auth: HTTP bearer
Path parameters
Request body
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.