The service of handling deposits/withdrawals on behalf is a common accounting task that frequently needs to be processed, with typical cases such as:
Logistics Companies
- Collection on behalf (Cash on Delivery - COD): The shipping provider collects payment for goods from the recipient on behalf of the seller, then transfers the funds to the seller.
- Payment on behalf: Covers transportation fees, storage fees, or other costs related to goods.
Financial Service Companies
- Collection on behalf: Banks collect payments on behalf of businesses from customers, such as service bills, insurance premiums, or installment payments.
- Payment on behalf: Banks process payments on behalf of businesses, including employee salaries, service fees, or other requested expenses.
The Problem
In business operations, collection/payment on behalf transactions must be managed and accounted for separately from the business’s own revenues and expenses.
This ensures transparency, avoids confusion between financial sources, and complies with legal regulations on accounting and finance.
Principles and Management Practices for Collection/Payment on Behalf Transactions:
- Separate Documentation and Account Recording
- Exclude from Business Revenue and Expenses
- Periodic Reconciliation
- Detailed Reporting
 
Key Features
- Allow record on-behalf partner on the payments.
- Generate on-behalf entries after post payment to transfer receivable/payable from customer/vendor to on-behalf partner automatically.
- Reconcile receivable/payable of Customer/Vendor automatically.
 
Journal Entries
The accounting entries for this transaction will be as follows
Payment Entries
| Account | Debit | Credit | Partner | Matching # | 
| Bank Account | 200 | 0 | Customer A |  | 
| Receivable Account | 0 | 200 | Customer A | A1 | 
 
On-behalf Entries
| Account | Debit | Credit | Partner | Matching # | 
| Receivable Account | 200 | 0 | Customer A | A1 | 
| Payable Account | 0 | 200 | Vendor A |  | 
 
 
Editions Supported
- Community Edition
- Enterprise Edition
 
 
 
							
								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.