Oman Fawtara Credit / Debit Note
OTA Fawtara credit & debit notes for Odoo — reversal references, adjustment reason codes and PINT note re-issuance
Extend the Oman Tax Authority Fawtara e-invoicing connector with complete credit note and debit note flows. Every refund or supplementary adjustment is issued as a PINT UBL 2.1 note that references the original cleared invoice, carries a coded adjustment reason and the original OTA clearance UUID — and can be re-issued through your accredited service provider when needed.
Adjustment reason codes
A curated UNTDID / OTA-aligned reason list — return of goods, post-sale discount, price correction, order cancellation and more — plus the supplementary-charge reasons for debit notes, surfaced as a validated selection stamped on the note. The reason must match the note direction.
Reversal references
The original invoice number, issue date and OTA clearance UUID are copied
from the reversed cleared sale and serialized as the PINT
BillingReference, so the note resolves against the right
original cleared document. An uncleared original is blocked.
Credit vs debit direction
Credit notes build a UBL CreditNote with type code
381; debit notes build a debit note with type code
383. The whole document is produced through the shared
e-Invoice Core Engine UBL builder — identical byte layout across
every country connector.
Note re-issuance
Re-generate and re-submit a rejected or amended note through the accredited service provider with a re-issuance counter and audit log, without losing the e-Invoice document linkage. An over-credit guard stops a credit note exceeding the original cleared total.
Guided note wizard & validation
Issue a Fawtara note straight from a cleared invoice: pick the direction and reason, optionally submit immediately. A dedicated Oman note validation profile layered on the base Fawtara rules checks the reason code, the original reference, the direction and the over-credit guard before anything reaches your provider.
Built on the e-Invoice Core Engine
Requires the shared e-Invoice Core Engine and the Oman Fawtara e-Invoice connector. No engine or base-connector functionality is duplicated. BYOK accredited-provider credentials only: invoice data is transmitted solely to the provider endpoint you configure, stored only on your database, never bundled.
Compatible with Odoo 18 and Odoo 19.
Screenshots
Fawtara Credit Note Referenc
Credit Note Pint Creditnote
Update date: 2026-07-02
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 3673 |
| Technical Name |
l10n_om_fawtara_credit_note |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
Odoo Proprietary License v1.0 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.
Please log in to comment on this module