Thanks for your answer, this seems logical as the invoice business object does seem to have a section_id field in the database. However, in our v7 installation the account_invoice_view.xml does not have this field added. Could it be that the order in which modules are installed matters? For now we will locally fix the view so that we can set the Sales Team manually.

Also, we are using Sales Teams to differentiate between markets but personal is working in all teams and hence have no default Sales Team assigned. It's just a different use case for small companies...

Technically, you will not find that field in account/account_invoice_view.xml because it is added via an inherited view in the sale_crm module, in sale_crm/sale_crm_view.xml. The sale_crm module is automatically installed if you install both sale and crm.

If you can't use a default sales team for your users you'll need to find a different way to automatically assign the right team on each invoice. It could be done via a very small custom module or perhaps by setting appropriate default_section_id values in the context of actions that lead to the creation of an invoice... it really depends on your use case though.

I just checked the view using the debug-functionality, and apparently the section_id is there but invisible: <field name="section_id" invisible="1" modifiers="{'invisible': true}"/> Not sure how it got there though. The sale_crm.account_invoice_form view in the database modifies the view like this: <field name="section_id" groups="base.group_multi_salesteams"/> Anyway, it might just be a glitch: we're working with the bleeding edge version of OpenERP.

Oh you're on trunk, that's why I did not understand :-) In trunk a new setting was recently added in Settings > Configuration > Sales, it's labelled "Organize Sales activities into multiple Sales Teams". You need to check that option and the field will become visible (technically, all users will have an extra group, and the invisible flag will be removed, it's a consequence of the groups attributes to restrict the visibility)

Thanks again! That did it! Now I also learned something about view inheritance and how it is implemented in OpenERP...