Revenue Allocation - Credit Note, Refunds & Reversals
by devluoicode https://www.devforfuture.com$ 69.40
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4519 |
| Technical Name |
dff_account_revenue_allocation_credit_note |
| 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 | 4519 |
| Technical Name |
dff_account_revenue_allocation_credit_note |
| License | OPL-1 |
| Website | https://www.devforfuture.com |
Revenue Allocation — Credit Note, Refunds & Reversals
Keep deferred revenue schedules accurate when customers receive refunds or end contracts early.
Extends Revenue Allocation & Deferral. When you post a customer credit note against a long-term service invoice, the system automatically updates the remaining recognition schedule according to your business rules — whether the customer terminates the contract, receives a partial refund, or only the last billing periods are affected. Every change is tracked so finance can review, audit, and undo if needed.
What You Gain
- Automatic schedule updates — Post a credit note and future revenue recognition periods adjust without manual spreadsheet work.
- Flexible refund policies — Choose how refunds affect the contract: end it, spread the reduction, or touch only the last periods.
- Built-in controls — The system blocks refunds that exceed what is still available to recognize, protecting your books.
- Clear audit trail — See total refunds, reversed revenue, and a full history of every adjustment on each contract.
- Easy corrections — Return a credit note to draft and schedule changes roll back automatically.
Refund Strategies
Set a default on your allocation templates, or override per contract before the first refund is posted.
Contract Termination
Best when the customer ends the service early. Future recognition periods are cancelled starting from the last period. If the refund is larger than what remains unrecognised, the excess is recorded as a revenue reversal so your deferred balance stays correct.
Equal Spread Across Remaining Periods
Best for a partial refund that should reduce every future billing period by the same amount. The contract continues, but each open period is lowered equally. Any amount beyond the remaining schedule is handled as a revenue reversal.
Proportional Reduction
Best when the refund should shrink each future period in line with its planned amount. Larger periods absorb more of the reduction; smaller periods absorb less. All open periods stay active unless the refund exceeds the full remaining balance.
Cancel Last N Periods Only
Best when the refund only applies to the final one or more billing cycles — for example, a student withdraws before the last semester, or a subscriber cancels the final months. You choose how many future periods to affect on the template or contract.
Smart Contract Matching
Credit notes created from the original invoice are linked to the right revenue contract automatically. When several contracts could match, the system asks you to confirm instead of guessing — so refunds always hit the correct schedule.
Undo and Review
Made a mistake? Set the credit note back to draft and schedule changes are reversed. Accountants can review refund totals, reversed revenue, and the full adjustment history on each contract before closing the period.
Screenshots
Set Your Default Refund Policy
Accounting → Configuration → Revenue Allocation → Revenue Allocation Templates. Choose what happens when a customer refund is posted — and how many final periods to cancel when using the last-N-periods option.
Track Refunds on Each Contract
Accounting → Accounting → Revenue Allocations. After posting a credit note, see total refunds, reversed revenue, and a complete adjustment history for audit and month-end review.
Why Choose This Module
Without This Extension
- Recognition schedules keep running as if nothing changed after a customer refund.
- Finance must manually adjust future periods or post correcting entries outside the schedule.
- No single place to see how much was refunded or reversed on each long-term contract.
With This Extension
- Posting a credit note updates the recognition schedule according to your chosen refund policy.
- Over-refunds are blocked before posting, reducing month-end surprises.
- Full history on each contract, with automatic rollback if the credit note is cancelled or reset to draft.
Typical Business Scenarios
Training & Education
A student withdraws mid-year. Issue a credit note and cancel the remaining tuition recognition periods instead of recognising revenue for months they will not attend.
Subscriptions & SaaS
A customer receives a partial refund on an annual plan. Spread the reduction across remaining months or cancel only the final billing cycles, depending on your refund policy.
Professional Services
A project ends early and part of the deferred fee is returned. Future recognition periods adjust automatically, and auditors can trace every change on the contract.
What Is Included
Included Features
- Four configurable refund strategies on templates and individual contracts.
- Override the refund policy per contract before the first credit note is posted.
- Automatic linking when creating a credit note from the original customer invoice.
- Protection against refunds larger than the remaining recognisable balance.
- Revenue reversal entries when a refund exceeds open schedule periods.
- Refund totals, reversed revenue, and adjustment history on each contract.
- Visible contract link on credit note lines for easy verification.
- Automatic rollback when a credit note is reset to draft or cancelled.
Good to Know
- Customer refunds only — Covers customer credit notes. Supplier bill refunds are not included.
- Deferred revenue contracts — Applies to invoices that use deferred revenue accounts configured in your company settings.
- Prerequisite — Deferred revenue accounts, templates, and at least one active recognition schedule must already be configured.
- Open periods only — Refund strategies adjust future recognition periods. Amounts already recognised in closed periods are handled through reversal entries, not by rewriting past postings.
- Refund policy locks after posting — To use a different strategy, reset the credit note to draft, change the setting, then post again.
How It Works
Set Your Refund Policy
On Revenue Allocation Templates, choose what should happen when a customer refund is posted. You can override this on an individual contract before any refund is processed.
Post the Customer Credit Note
Create the credit note from the original invoice whenever possible. The system links it to the correct revenue contract, checks the refund amount, and updates the recognition schedule.
Review or Correct
Open the revenue contract to review refund totals and adjustment history. If something is wrong, reset the credit note to draft and the schedule restores automatically.
Getting Started
- Configure deferred revenue first: Set deferred revenue accounts and allocation templates, then post at least one customer invoice with an active recognition schedule.
- Choose your refund policy: Set the default on allocation templates (and per contract if needed) before processing live credit notes.
- Test with a sample refund: Create a credit note from a posted invoice and confirm the schedule updates as expected for your business rules.
- Best practice: Always create credit notes from the original customer invoice so the correct contract is linked automatically.
FAQ
When should I use contract termination vs equal spread?
Use contract termination when the customer stops the service and you want to cancel future periods from the end of the schedule. Use equal spread when the customer keeps the service but receives a partial refund that should reduce every remaining period by the same amount.
When should I use proportional reduction vs cancel last N periods?
Use proportional reduction when the refund should shrink every future period but keep their relative sizes (a partial service reduction across the whole contract). Use cancel last N periods when the refund only affects the final one or more billing cycles.
Can the refund exceed what is left to recognise?
No. Posting is blocked if the refund is larger than the allowed balance on the linked contract. Correct the amount on the credit note before posting.
What happens if I reset a credit note to draft?
All schedule adjustments from that credit note are reversed: cancelled periods are restored, amounts return to their pre-refund values, and any reversal entries created by that credit note are removed.
What if several contracts match the same product?
The system stops and asks you to select the correct contract on the credit note line instead of guessing. This prevents refunds from being applied to the wrong schedule.
Can I change the refund policy after a credit note is posted?
The refund policy is locked once a credit note is posted against the contract. To reprocess with a different policy, reset the credit note to draft, change the setting, then post again.
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, credit notes, and journal entries (via dependency)- No extra server, API, or subscription service
Where It Fits
- Extends Revenue Allocation Templates and Revenue Allocation Profiles
- Runs when customer credit notes are posted, reset to draft, or cancelled
- Adds refund balances and Adjustment History on allocation profiles
License and Publisher
- License: OPL-1 (Odoo Proprietary License)
- Publisher: devluoicode
- Website: devforfuture.com
- Support: ngocphat.business@gmail.com
Support and Maintenance
Setup Assistance
Help with installation, dependency resolution, and configuring your refund policies.
Issue Resolution
Priority support for refund processing errors, unexpected schedule behaviour, 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