Revenue Allocation — Multi-Invoice Unified Profiles
by devluoicode https://www.devforfuture.com$ 59.35
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4147 |
| Technical Name |
dff_account_revenue_allocation_multi_invoice |
| License | OPL-1 |
| Website | https://www.devforfuture.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4147 |
| Technical Name |
dff_account_revenue_allocation_multi_invoice |
| License | OPL-1 |
| Website | https://www.devforfuture.com |
Revenue Allocation — Multi-Invoice Unified Profiles
One deferred-revenue profile shared across multiple customer invoices for the same business source line.
Extends Revenue Allocation & Deferral. When several customer invoices belong to the same contract line, project task, or sales order line, this module pools their deferred revenue under one recognition profile. Post invoices in any order, rescale draft schedule lines as the invoiced pool grows, and protect shared profiles from unsafe invoice resets or deletions.
What You Gain
- Single Profile per Source Line — Multiple customer invoices link to one allocation profile instead of duplicate schedules per invoice.
- Live Planned Revenue — Target Planned Revenue sums all related deferred invoice lines (draft and posted) and drives schedule generation.
- Automatic Schedule Resync — Draft schedule lines rescale when a new invoice is posted, cancelled, or reset, preserving posted recognition amounts.
- Posted-Pool Recognition Caps — Clear messages when cumulative recognition would exceed the posted deferred revenue pool until the next invoice is posted.
- Data Integrity Guards — Blocks deleting linked invoices, resetting invoices when the profile is Done, and reducing planned revenue below already recognized amounts.
Core Features
Unified Profile Pooling
When a new customer invoice line shares the same source document line and allocation template, the system reuses the existing profile instead of creating a second schedule. The profile stores an Allocation Source reference to the originating business line.
Target Planned Revenue
Target Planned Revenue on the allocation profile shows the live sum of all related customer invoice lines on configured deferred revenue accounts. Schedule generation and rescaling use this amount so partial billing and down payments stay aligned with the full contract.
Draft Schedule Rescaling
When the invoice pool changes, remaining draft schedule lines rescale proportionally to the template percentages. Already posted recognition lines are preserved. Posting is blocked if the new planned total would fall below amounts already recognized.
Recognition Pool Caps
For unified profiles, cumulative recognition is capped by the posted deferred revenue pool from all linked customer invoices. Auto-post skips with a clear message when the next milestone invoice is required; manual posting shows the same cap in an error dialog.
Source Document Hooks
Ships a reusable source-document mixin and invoice-line hooks so business lines (contract lines, order lines, project tasks) can register as the Allocation Source for unified grouping without duplicating allocation logic.
Invoice & Profile Protection
Cannot delete a customer invoice already linked to a recognition profile. Cannot reset an invoice to draft when its profile is Done. Resetting a shared invoice detaches only its schedule lines; the profile survives while other posted invoices remain linked.
Screenshots
Unified Allocation Profile
Accounting → Accounting → Revenue Allocations. One profile with Allocation Source, Target Planned Revenue, and multiple linked customer invoices pooled under the same recognition schedule.
Schedule After Multiple Invoices
Draft schedule lines on the same profile after posting a second customer invoice. Remaining periods rescale to the updated Target Planned Revenue while posted recognition lines stay unchanged.
Why Choose This Module
Revenue Allocation Alone
- Creates one recognition profile per customer invoice line by default.
- Partial billing and milestone invoicing produce duplicate schedules for the same contract line.
- Planned revenue on each profile reflects only that invoice, not the full multi-invoice contract.
With Multi-Invoice Extension
- One profile per business source line across all related customer invoices.
- Target Planned Revenue tracks the full deferred pool; draft periods rescale automatically.
- Recognition caps and invoice protection keep multi-invoice milestone billing auditable end to end.
Scope of Delivery
Included Features
- Allocation Source reference on unified revenue allocation profiles.
- Target Planned Revenue on profile form and list views.
- Profile reuse when posting additional customer invoices for the same source line and template.
- Automatic draft schedule rescaling when the invoice pool changes (post, cancel, reset).
- Posted deferred-revenue pool caps with user-facing auto-post skip and manual post error messages.
- Manual allocation wizard reuses sibling profiles on the same source line.
- Blocks Mark Done while draft customer invoices remain on the source document.
- Invoice delete and reset-to-draft protection rules for linked profiles.
- Source-document mixin and invoice-line hooks for unified grouping on registered business lines.
Explicit Limitations
- Hub module — Does not add Sales Order or Project screens by itself. Invoices are grouped when their lines resolve to a registered Allocation Source on the business document.
- Deferred Revenue Lines Only — Pooling applies to customer invoice product lines on configured deferred revenue accounts.
- Prerequisite — Deferred revenue accounts, templates, and periods must already be configured.
- Posted Recognition Floor — Cannot reduce planned revenue below amounts already posted on schedule lines.
- Single Profile per Source — Multiple profiles on the same source line block manual allocation until data is resolved.
- No Extra Settings Screen — Company deferred-revenue configuration remains in accounting settings.
How It Works
Configure Deferred Revenue
Set Deferred Revenue Accounts and allocation templates in Accounting settings. Each business source line that should share one profile must register as an Allocation Source when invoices are posted.
Post Customer Invoices
Create and post customer invoices for the same source line (down payment, partial amount, or milestone). Auto-allocation or the Allocate action on invoice lines links each line to the shared profile. Post order does not matter.
Review Unified Profile
Open Accounting → Accounting → Revenue Allocations. Confirm Target Planned Revenue, review rescaling on draft schedule lines, and recognize revenue as milestones are invoiced. Use Recompute Amounts if counters need a manual refresh.
Implementation Notes
- Deferred accounts: Ensure customer invoice lines post to accounts listed under Deferred Revenue Accounts in company settings.
- Same template per source: Profile reuse matches on source document line plus allocation template. Use consistent templates across milestones on the same contract line.
- Recognition timing: When posted invoices cover only part of the contract, schedule auto-post may wait until the next invoice increases the posted deferred pool.
- Done profiles: Re-open a Done profile before resetting any linked customer invoice to draft.
- Uninstall note: Uninstalling does not delete posted journal entries. New multi-invoice grouping stops; existing profiles keep their stored source links until manually cleaned up.
FAQ
How are multiple invoices linked to one profile?
Each unified profile stores an Allocation Source pointing to the originating business line. When a new customer invoice line resolves to the same source and template, it joins the existing profile instead of creating a duplicate schedule.
What happens when I post a second invoice?
The invoice line joins the existing profile. Target Planned Revenue increases, and remaining draft schedule lines rescale to the new total while posted recognition lines stay unchanged. If no schedule exists yet, one is generated once a posted deferred line exists.
Why was auto-posting skipped on a schedule line?
On unified profiles, cumulative recognition cannot exceed the posted deferred revenue pool from all linked customer invoices. Post the next milestone invoice to increase the pool, then recognition can proceed for that period.
Can I reset one invoice to draft on a shared profile?
Yes, unless the profile is Done. Resetting detaches that invoice's schedule line links and rescales draft periods for the remaining pool. The shared profile is deleted only when no other non-draft invoices reference it.
What is the difference between Target Planned Revenue and Posted Deferred Pool?
Target Planned Revenue includes draft and posted invoice lines on deferred accounts — it drives the full contract schedule. The posted deferred pool includes only posted invoices and caps how much revenue can be recognized until the next invoice is posted.
Technical Details
Platform
- Odoo 18.0 Community and Enterprise
- Multi-company environments supported (inherits base module record rules)
- Runs inside your existing Odoo database
Required Apps
dff_account_revenue_allocation— deferred revenue scheduling (required)account— customer invoices and journal entries (via dependency)- No extra server, API, or subscription service
Where It Fits
- Extends Revenue Allocation Profiles form and list views
- Hooks customer invoice posting, cancellation, reset-to-draft, and delete flows
- Extends the manual Allocate wizard to reuse sibling profiles
License and Publisher
- License: OPL-1 (Odoo Proprietary License)
- Publisher: devluoicode
- Website: devforfuture.com
- Support: ngocphat.business@gmail.com
Support and Maintenance
Installation Support
Help with installation, dependency resolution, and initial module configuration on your database.
Bug Resolution
Priority support for functional errors, traceback issues, and bug fixes related to this module.
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