[IMP] accounting: add implementation/go-live instructions - #19147
Open
dade-odoo wants to merge 1 commit into
Open
[IMP] accounting: add implementation/go-live instructions#19147dade-odoo wants to merge 1 commit into
dade-odoo wants to merge 1 commit into
Conversation
Collaborator
|
|
dade-odoo
force-pushed
the
19.0-accounting-get-started-dade
branch
from
July 29, 2026 13:28
f45a12b to
1ad5a55
Compare
dade-odoo
changed the title
dade-odoo
marked this pull request as ready for review
July 29, 2026 13:29
dade-odoo
force-pushed
the
19.0-accounting-get-started-dade
branch
from
July 29, 2026 14:54
1ad5a55 to
95ecde3
Compare
dade-odoo
force-pushed
the
19.0-accounting-get-started-dade
branch
from
July 30, 2026 08:28
95ecde3 to
f0b4f6f
Compare
dade-odoo
force-pushed
the
19.0-accounting-get-started-dade
branch
from
August 3, 2026 11:05
f0b4f6f to
bc14939
Compare
auva-odoo
requested changes
Aug 5, 2026
auva-odoo
left a comment
auva-odoo
left a comment
Contributor
There was a problem hiding this comment.
Congrats on getting this one out, @dade-odoo! 🎉 I know you've been wanting to finish this for a while, so it must've felt great to finally be able to push it 🤗
In addition to my individual comments below, here are some general points:
- Replace the icon descriptor gear with Actions where appropriate
- Replace hyphens with a colon or period
- Make sure all relevant menuselections list the app's name first
- For import process sections: since this is pretty standard, I'd drop the step-by-step instructions and just keep the menu selection + a general line about importing the file prepared earlier, then referencing the Import section of the Essentials doc. If that doc needs updating, let's do it directly in this PR (it's short) rather than repeating the import process throughout this Get Started doc. Keep anything Accounting Get Started-specific, of course (usually the last step, or parts of the Import Inventory section for example). let me know if you'd like to discuss this
- I think it might be worth going through the whole doc and double-checking for typos/double words. I know (or think) you're not a fan of Grammarly, but it's actually a great tool for this specific task.
Thank you!!
Comment on lines
+13
to
+14
| .. image:: get_started/overview.png | ||
| :alt: The steps of implementing Odoo Accounting. |
Contributor
There was a problem hiding this comment.
I would replace the image with a numbered list (with bullet sub-lists), or maybe a table; I think it'd be more useful (and maybe refs to the relevant sections for all list items)
| Odoo from a different legacy accounting software. The process for companies starting directly with | ||
| Odoo is much simpler but still involves validating the fiscal localization, importing master data, | ||
| and configuring their Accounting settings to meet their business needs. The process for companies | ||
| transitioning to Odoo involves those same steps plus importing their opening entries. |
Contributor
There was a problem hiding this comment.
Suggested change
| transitioning to Odoo involves those same steps plus importing their opening entries. | |
| transitioning to Odoo involves the same steps, as well as importing their opening entries. |
(just want to replace the plus here)
| .. _accounting-setup-periods: | ||
| A fiscal localization package is automatically installed based on the country selected at the | ||
| creation of the database. Some countries have multiple fiscal localization packages for different | ||
| business types, so be sure to verify the fiscal localization package that is set. To do so, go to |
Contributor
There was a problem hiding this comment.
Suggested change
| business types, so be sure to verify the fiscal localization package that is set. To do so, go to | |
| business types, so be sure to verify that the correct package is installed. To do so, go to |
| Accounting Periods | ||
| ------------------ | ||
| .. warning:: | ||
| Selecting another package is only possible if only possible if no journal entry has been posted |
Contributor
There was a problem hiding this comment.
Suggested change
| Selecting another package is only possible if only possible if no journal entry has been posted | |
| Selecting another package is only possible if no journal entry has been posted |
Comment on lines
+63
to
+66
| Master data is data that other records rely on. For example, it's impossible to have an invoice | ||
| without a customer. The customer, or contact, is master data. Because other records rely on master | ||
| data, the order of transferring accounting data into Odoo (whether manually or via import), is | ||
| crucial. |
Contributor
There was a problem hiding this comment.
Suggested change
| Master data is data that other records rely on. For example, it's impossible to have an invoice | |
| without a customer. The customer, or contact, is master data. Because other records rely on master | |
| data, the order of transferring accounting data into Odoo (whether manually or via import), is | |
| crucial. | |
| Master data is data that other records rely on. For example, an invoice requires a customer; | |
| the customer, or contact, is therefore master data. Because other records depend on master data, the order in which accounting data is transferred into Odoo, whether manually or via import, is crucial. |
I though we could improve the style a little bit here (especially the second sentence), but feel free to adapt this further
| - Date the invoice was created (note that an error will occur on import if the year in the | ||
| :guilabel:`Number` and the year in this field are different) | ||
| * - Due Date | ||
| - Date the invoice/bill is due - each invoice can have either a due date or payment terms, but |
Contributor
There was a problem hiding this comment.
Suggested change
| - Date the invoice/bill is due - each invoice can have either a due date or payment terms, but | |
| - Date the invoice/bill is due. Each invoice/bill can have either a due date or payment terms, but |
Comment on lines
+478
to
+480
| If product costs were not already included when the products were created, add them now, either by | ||
| manually updating the :guilabel:`Cost` field on the products themselves, or via an :ref:`import to | ||
| update <essentials/update-data>` it. |
Contributor
There was a problem hiding this comment.
Suggested change
| If product costs were not already included when the products were created, add them now, either by | |
| manually updating the :guilabel:`Cost` field on the products themselves, or via an :ref:`import to | |
| update <essentials/update-data>` it. | |
| If product costs were not already included when the products were created, update them, either manually in the :guilabel:`Cost` field on each product form, or via an :ref:`import <essentials/update-data>`. |
| * - Journal Items/Account | ||
| - The account code and/or name | ||
| * - Journal Items/Debit | ||
| - The debit value of the account in the company's main currency as a positive number. If the |
Contributor
There was a problem hiding this comment.
Could we drop "as a positive number"? it sounds a bit odd to me. I think it might've been added to exclude negative numbers, but if so, I feel like your last sentence already covers that?
Comment on lines
+624
to
+625
| - The credit value of the account in the company's main currency as a positive number. If the | ||
| line has a debit, this field should be left blank. Do not enter `0.00` or a negative value. |
Contributor
There was a problem hiding this comment.
same as above for positive number
Comment on lines
+35
to
+36
| Verify fiscal localization | ||
| -------------------------- |
Contributor
There was a problem hiding this comment.
Since this is the only h3 in this section, i'd consider removing it and replacing it with an intro sentence
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.
taskid-3424310
The Buffalo office has an accounting go-live checklist that is useful for the US but too specific for other localizations and not widely shared. Here we've made it general enough to apply across localizations, made it available to all users by adding it to the documentation, and connected it to the rest of the documentation.