We’re excited to announce that the latest information is now available on our new site, the Ginesys One Wiki!. Visit the site for up-to-date resources and insights. We look forward to continuing to support you there!
We’re excited to announce that the latest information is now available on our new site, the Ginesys One Wiki!. Visit the site for up-to-date resources and insights. We look forward to continuing to support you there!
#Cash Planning - Summary#
- Aparajita Basu Roy
Report Name | #Cash Planning - Summary# | ||
|---|---|---|---|
Report Location | Finance\Register | ||
Report Type | Register | ||
Report Description | This Report will helpful to have Cash Planning (Summary) for future date. This Report will consider Purchase Invoice, Service Invoice, Sales Invoice, Sale of Service Invoice document as parent document for this report purpose. | ||
Report Objective | The objective of this report to plan future liability with respect to current outstanding and future due date. In this Report Document Amount considered based on the due date of the document. For this report Purchase Invoice, Service Invoice (Purchase), Service Invoice (Sales), Sales Invoice is considered and all the other document’s balance is being considered under column named 'Past Balance' | ||
Target Audience | Finance Manager, Finance Executive, Management | ||
Selections | Name | Selection type | Objective |
Due Date From : | Single | Report to be shown based this document due date from selected by user. This date should be future date w.r.t the date of report running. | |
Due Date To : | Single | Report to be shown based this document due date to selected by user. This date should be future date w.r.t the date of report running. | |
Include Unposted Entries : | Single | If it is True then report will consider all those transctions which is not released/posted yet also. | |
Class Name : | Single | User can opt for particular Sub Ledger Class i.e. Customer, Transporter etc. for specific report purpose. If there is no such specific requirement then ‘ALL’ need to be selected. | |
Ledger | Multiple | User can opt for Ledger (i.e. Party or AR/AP Ledger) for the report purpose. If no such specific selection is required then it can be kept in Blank. | |
Sub Ledger | Multiple | User can opt for Sub Ledger (i.e. Party) [based on selected Ledger above ]for the report purpose. If no such specific selection is required then it can be kept in Blank/Remove. | |
Agent | Multiple | User can opt for Agent of Sub Ledger (i.e. Party) [based on previous selection ]for the report purpose. If no such specific selection is required then it can be kept in Blank. | |
Dependencies | NA | ||
Alternative reports to validate | NA | ||
Sample Output | 
| ||
Data Source Category Used | 01-Master\ARAP Ledger [LV_ARAP_LEDGER] | ||