Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0017797Openbravo ERP09. Financial managementpublic2011-06-27 19:162011-08-12 13:41
Payment Report
0017797: Payment Report: wrong subtotal amounts by status
The Payment Report does not add up properly at subtotal level for the same status. In fact, the report does not differentiate between payments in and out for the same status.
After checking the corresponding wiki information ( [^]) we have detected that there are the same status for both payments in and out. So, the report should differentiate the document type when there is a subtotal.
To reply the bug please follows the following steps in the example:
NOTE: the following example is already created in the client TEST and PRODUCTIVE environment version 2.50+MP28.
Create the following data:
• Payment Method to use: Write transfer (same configuration for payment in/out):
 Payment In Allowed: marked
 Execution Type: Manual
 Upon Reconciliation Use: Cleared Payment Account
• Business partner both: customer and vendor.
• Purchase Invoice - total amount: 150 €. Transaction and accounting date: 20-06-2011
• Sales Invoice – total amount: 200 € Transaction and accounting date: 20-06-2011
Once all these data have been registered into the system follow the following steps:
A. Financial Management || Receivables & Payables || Analysis Tools || Payment Report || Payment Report
1. Filter by:
 Organization: the regarding one
 Business partner: the created above.
 Cover to currency: the regarding to the invoices created
 Payment type: receivables and payables
 Ordering criteria: by date
2. Press button “Search” >> see attached the result:
3. Subtotal Awaiting Payment: once is a sales invoice (354,43 €) and the other is a purchase invoice (117,00 €). However, there is not possible to differentiate both. There should be a column to differentiate if it is a payment in or out. The subtotal for this status should be the subtraction but not the sum.
4. The same happens with other status like Subtotal Remittance in this example: as you can check in this example these remittance payments are AP Payments. Therefore, the subtotal should have to take into account the document type.
The subtotal should have to take into account the document type. The subtotal for an specific status should be the subtraction but not the sum base on the document type.

Finally, is the Grand Total amount should differentiate to amounts: payment in and payment out. This way, there final result should have sense.
No tags attached.
depends on backport 0017940 closed ioritzCia Modules Payment Report: wrong subtotal amounts by status 
? Subtotal Payment Report.bmp (2,219,234) 2011-06-27 19:16
Issue History
2011-06-27 19:16jaime_chamorroNew Issue
2011-06-27 19:16jaime_chamorroAssigned To => mirurita
2011-06-27 19:16jaime_chamorroFile Added: Subtotal Payment Report.bmp
2011-06-30 18:52miruritaAssigned Tomirurita => ioritzCia
2011-07-04 18:22maitePriorityhigh => immediate
2011-07-04 18:22maiteSeveritymajor => critical
2011-07-08 14:10ioritzCiaProjectModules => Openbravo ERP
2011-07-08 14:12ioritzCiaModules => Payment Report
2011-07-08 14:12ioritzCiaCategoryPayment Report => 09. Financial management
2011-07-08 14:13ioritzCiaStatusnew => scheduled
2011-07-08 14:13ioritzCiafix_in_branch => pi
2011-07-11 09:58dalsasuaPriorityimmediate => high
2011-07-11 09:58dalsasuaSeveritycritical => major
2011-07-11 09:58dalsasuafix_in_branchpi =>
2011-07-11 18:55hgbotCheckin
2011-07-11 18:55hgbotNote Added: 0039000
2011-07-11 18:55hgbotStatusscheduled => resolved
2011-07-11 18:55hgbotResolutionopen => fixed
2011-07-11 18:55hgbotFixed in SCM revision => [^]
2011-08-01 14:19hudsonbotCheckin
2011-08-01 14:19hudsonbotNote Added: 0039587
2011-08-12 13:41maiteNote Added: 0040164
2011-08-12 13:41maiteStatusresolved => closed

2011-07-11 18:55   
Repository: erp/devel/pi
Changeset: add1c452cbb91b8504b5a9844126ca015821a0b7
Author: Ioritz Cia <ioritz.cia <at>>
Date: Fri Jul 08 13:57:53 2011 +0200
URL: [^]

Fixes issue 17797: Payment Report: wrong subtotal amounts by status.

M modules/
2011-08-01 14:19   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: [^]

Maturity status: Test
2011-08-12 13:41