Odoo ZATCA Phase 2 Expert Needed — Diagnose and Fix BR-KSA-80 XML Error
$10-50 USD
Posted 1 minute ago
•
Ends in 6 days
$10-50 USD
Paid on delivery
We use Odoo in Saudi Arabia and need an experienced Odoo/ZATCA developer to diagnose and resolve this validation error: BR-KSA-80: The Pre-Paid amount (BT-113) must equal the sum of the Prepayment VAT category Taxable Amount (KSA-31) and Prepayment VAT Category Tax Amount (KSA-32). Background: The original invoice XML declares PrepaidAmount = 0.00. It declares the full invoice total as payable. Payment was registered after invoice creation and should not be treated as the cause of the original error. The XML includes TaxSubtotal elements within ordinary invoice lines. Please investigate whether these contribute to the validation issue; this is a hypothesis, not a confirmed root cause. Scope: Identify the Odoo version, installed Saudi EDI module, and any relevant customizations. Reproduce the issue and establish the root cause from the actual submitted XML and validation response. Determine whether the solution is configuration, an applicable official update, or a narrowly scoped code fix. Implement and test the correction in a staging environment. Demonstrate that regenerated XML passes the relevant ZATCA validation without altering legitimate invoice amounts or creating artificial down payments. Provide a brief explanation, changed files or module, test evidence, deployment instructions, and rollback steps. Required experience: Odoo backend/Python development. Saudi ZATCA Phase 2 integration. UBL XML and ZATCA business-rule validation. Experience with our installed Odoo version and integration module. Please include a relevant previous project and explain your proposed diagnostic approach. Production changes require prior approval.
Project ID: 40819002
About the project
16 proposals
Open for bidding
Remote project
Active 5 secs ago
Place your bid
Bid amount Email addressBenefits of bidding on Freelancer
Set your budget and timeframe
It's free to sign up and bid on jobs
16 freelancers are bidding on average $32 USD for this job


Hi, I'm a senior developer with 10+ years of experience building and troubleshooting Odoo integrations, and I've worked directly with ZATCA Phase 2 implementations in Saudi Arabia—including similar BR-KSA-80 validation failures tied to prepayment logic and XML structure issues. I'll start by reviewing your Odoo version, the installed Saudi EDI module, and the actual submitted XML alongside the ZATCA validation response to pinpoint whether the root cause is in invoice line TaxSubtotal declarations, prepayment amount calculation, or module configuration. Once I've reproduced the error in a staging environment, I'll determine whether the fix is a configuration adjustment, an official module update, or a targeted code change—then implement and test it to confirm the regenerated XML passes validation without altering legitimate invoice totals. I'll document the root cause, provide the exact files or modules changed, include test evidence showing the corrected XML, and give you clear deployment and rollback steps. I'm available now and will stay on for any adjustments or questions after the fix goes live.


Hi - Adelman here from Texas BR-KSA-80 XML validation failure - the important part is tracing the prepayment totals back to the exact Odoo-generated XML, not changing invoice amounts to force validation. I’d start by checking your Odoo version, Saudi EDI module, customizations, submitted XML, and ZATCA response. Then I’d trace BT-113 against KSA-31 and KSA-32, reproduce the issue in staging, and determine whether the cause is configuration, an official module update, or a targeted Python/XML fix. I’d test the regenerated XML and provide the change details, deployment steps, and rollback instructions before any production release. Which Odoo version and Saudi EDI module are currently installed? Looking forward to work with you.


that br-ksa-80 error on your odoo invoices in saudi arabia, i can dig into it and get it fixed i can do this for you and get your regenerated xml passing zatca validation i'll stay on it until the error is gone and your real invoice amounts are left alone which odoo version and saudi edi module are you running right now? happy to chat more whenever suits you Sela


Hi, I have 10+ years of experience building and debugging Python backends, REST integrations, and data-driven business logic in production systems. For Odoo ZATCA Phase 2 Expert Needed — Diagnose and Fix BR-KSA-80 XML Error, I’ll first identify your Odoo version, the installed Saudi EDI/ZATCA Phase 2 module, and any XML/custom tax logic that could affect BT-113/KSA-31/KSA-32. Then I’ll reproduce the failure by regenerating the exact submitted UBL XML and aligning it with the ZATCA validation response, focusing on how prepaid/payment timing and TaxSubtotal placement impacts rule BR-KSA-80. Once the root cause is confirmed, I’ll implement a narrowly scoped config/code change, validate it on staging, and ensure regenerated XML passes without altering legitimate amounts. You’ll get a clear root-cause write-up, changed module/files, test evidence, deployment steps, and rollback instructions after approval. Best, Razmik


Hello, I’m Kristián Lauko, with 10+ years of experience in Debugging, Software Development, and Odoo backend/Python work, including XML-driven integrations and business-rule validation. I understand the issue: BR-KSA-80 is being triggered in your Saudi Odoo invoice XML, and the goal is to find the real cause from the submitted XML and ZATCA response, not to guess. I would first identify the Odoo version, Saudi EDI module, and any customizations, then reproduce the error in staging, inspect the generated UBL XML, and verify whether the TaxSubtotal entries or another mapping issue are causing the validation failure. From there, I’d apply the smallest safe fix, retest the regenerated XML, and provide clear notes on the change, deployment, and rollback. I have extensive experience with Odoo modules, Python debugging, and invoice/XML validation workflows, including diagnosing integration issues where the output looked correct but failed external compliance checks. I’d keep communication clear throughout the work and share progress, findings, and any blockers promptly. I’d be glad to hear from you and discuss the setup. Thanks, Kristián Lauko


Hi, <ODOO ZATCA PHASE 2 BR-KSA-80 XML VALIDATION FIX> — the main goal is to identify why the generated invoice XML violates the prepayment VAT calculation rule and correct the actual root cause without changing legitimate invoice amounts. I would inspect your Odoo version, Saudi EDI module, customizations, submitted UBL XML, and ZATCA validation response. I would then trace how BT-113, KSA-31, and KSA-32 are generated, including the TaxSubtotal elements, to identify the exact source of the mismatch. I would implement the narrowest appropriate fix in staging, regenerate the XML, verify ZATCA validation, and provide test evidence, deployment instructions, and rollback steps before any production changes. Which Odoo version and Saudi EDI module are you currently using, and can you share the rejected XML and validation response? Looking forward to working with you.


HELLO, "BR-KSA-80" - tracing the prepayment VAT mismatch to its actual source in Odoo’s generated ZATCA XML, without changing legitimate invoice totals. I'll first identify your Odoo version, Saudi EDI module and customizations, then reproduce the failure using the original XML and ZATCA response. I'll compare BT-113 with KSA-31 and KSA-32, inspect the TaxSubtotal structure and trace how the XML is generated. Once the root cause is confirmed, I'll apply the smallest appropriate configuration, official update or code correction in staging and verify the regenerated XML before recommending production deployment. I'll also document changed files, test evidence, deployment and rollback steps. Can you provide the Odoo version, the submitted XML and the complete ZATCA validation response? THANKS


Hi, The inability to correctly validate and submit invoice XML due to the BR-KSA-80 error is indeed a crucial issue. The prepayment amount mismatch can often be traced back to either misconfigured XML templates or incorrect data aggregation. Here's how I'd do it: - Identify the Odoo version and any installed Saudi EDI modules to understand the configuration. - Analyze the XML structure, especially the TaxSubtotal elements, to see how they interact with the prepaid amount. - Regenerate the XML and validate against ZATCA rules to confirm compliance and document any changes made. I can have a working version of the core XML validation ready on a test link within a day. What specific version of Odoo are you currently using? Toqeer S
内容来自 Freelancer News,版权归原作者所有。
阅读原文 ↗