Payment Transaction - Deletion Restriction
$ 5.62
$ 5.62
v
17.0
0
Deleting a transaction still linked to a payment is refused, with both documents named - so the payment trail stays complete.
Payment Transaction - Deletion Restriction (technical name to_payment_transaction_protection) is an Odoo 17.0 app for Odoo Community and Odoo Enterprise and Viindoo Cloud, built for accountant, administrator, auditor, support.
The facts of Payment Transaction - Deletion Restriction, version 0.1, in one place. Published by Viindoo.
One rule, in one place.
Each online payment points at the transaction that produced it - and that link is now protected.
Configuration is unchanged; only deletion of a referenced transaction is refused.
Deleting a transaction referred to by a payment is refused
The message names the transaction and the payment
Applies to bulk deletions too
Nothing changes about how transactions are created or processed
No configuration
Payments, refunds and their states are untouched
Everything below was taken on a database seeded with real business data, on this series - not a mock-up and not a screenshot from an older version.
Providers
Read this before you buy. Everything below is something the app deliberately leaves to another app or to you.
Accounting documents have their own rules; this guards the transaction side.
A test transaction nothing points at is not part of a trail.
Housekeeping is your process - this keeps it from breaking references.
How transactions are created stays the provider's.
Apps from the same stack, built to fit this one:
Keeps the provider record behind every online payment.
Is stopped before a cleanup breaks the payment trail.
Follows a payment to the transaction that produced it.
Can still find the gateway reference weeks later.
Deleting a transaction still linked to a payment is refused, with both documents named - so the payment trail stays complete.
It does not stop deleting payments. Accounting documents have their own rules; this guards the transaction side. Unreferenced transactions can still be deleted. A test transaction nothing points at is not part of a trail. It is not an archiving policy. Housekeeping is your process - this keeps it from breaking references. It does not change provider behaviour. How transactions are created stays the provider's.
Accountant: Keeps the provider record behind every online payment. Administrator: Is stopped before a cleanup breaks the payment trail. Auditor: Follows a payment to the transaction that produced it. Support: Can still find the gateway reference weeks later.
Odoo 17.0 - Odoo Community, Odoo Enterprise, Viindoo Cloud. Upgrades to a newer Odoo series are a separate purchase for that series.
It installs on top of: account_payment. Odoo installs them with it.
One rule, in one place.
Payment Lines (to_account_payment): One payment split across accounts. Reconciliation Widget (viin_account_reconciliation): Matching those payments against invoices. PayPal Currencies (to_paypal_unsupported_currencies): Another rough edge in the payment layer.
Yes - the Live Preview button at the top of this page opens the module's own screen on a working database.
Write to apps.support@viindoo.com with your Odoo version and the technical name to_payment_transaction_protection; pre-sales questions go to sales@viindoo.com.
A payment transaction that a payment refers to cannot be deleted
For questions, implementation support, or consulting services, contact Viindoo.
When contacting us, please include:
For faster troubleshooting, please provide:
Upgrades to a newer Odoo series are a separate purchase for that series.
Assume that a customer purchases a product through the Paypal payment portal. When the payment is successful, the system will automatically generate a payment transaction associated with the invoice or sale order sent to the customer. So how will the system behave when the user intentionally deletes this payment transaction?
Navigate to Accounting > Configuration > Payments > Payment Transactions to view the generated transaction.
At this time, the system also automatically generates a payment associated with this transaction.
On the payment transaction associated with the payment, you select Action > Delete, the system will display an error message.
Note: Activating Developer Mode (debug mode) to check payment transactions.
This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file).
You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one).
It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software.
The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
We use cookies to provide you a better user experience on this website. Cookie Policy