[IMP] l10n_sa_{edi}: allow backdating invoices - #237191
Closed
fw-bot wants to merge 1 commit into
Closed
Conversation
Contributor
|
|
Contributor
Author
|
@khom-odoo @gawa-odoo cherrypicking of pull request #229517 failed. stdout: Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?). In the former case, you may want to edit this PR message as well. More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port |
robodoo
added
forwardport
Previously, `l10n_sa_confirmation_datetime` represented the time where the invoice was posted, that meant that we could not backdate invoices, since it would cause disparity between what zatca receives and what we consider in odoo (i.e. `invoice_date`) This commit allows us to set the date component of `l10n_sa_confirmation_datetime` to the `invoice_date` so we can safely backdate invoices. task-5009969 X-original-commit: 8890418
khom-odoo
force-pushed
the
saas-18.4-17.0-l10n_sa_edi-flexible-issue-date-khom-479238-fw
branch
from
November 25, 2025 07:18
832cf84 to
292e204
Compare
Contributor
|
@robodoo r+ |
robodoo
pushed a commit
that referenced
this pull request
Nov 25, 2025
Previously, `l10n_sa_confirmation_datetime` represented the time where the invoice was posted, that meant that we could not backdate invoices, since it would cause disparity between what zatca receives and what we consider in odoo (i.e. `invoice_date`) This commit allows us to set the date component of `l10n_sa_confirmation_datetime` to the `invoice_date` so we can safely backdate invoices. task-5009969 closes #237191 X-original-commit: 8890418 Signed-off-by: Wala Gauthier (gawa) <gawa@odoo.com> Signed-off-by: Omar Khalid (khom) <khom@odoo.com>
fw-bot
deleted the
saas-18.4-17.0-l10n_sa_edi-flexible-issue-date-khom-479238-fw
branch
December 2, 2025 11:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously,
l10n_sa_confirmation_datetimerepresented the time where the invoice was posted,that meant that we could not backdate invoices, since it would cause disparity between
what zatca receives and what we consider in odoo (i.e.
invoice_date)This commit allows us to set the date component of
l10n_sa_confirmation_datetimeto theinvoice_dateso we can safely backdate invoices.task-5009969
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: #236979
Forward-Port-Of: #229517