Thursday, 2 November 2023

 Collections issue?

Problem statement: In many companies the data for the receipts has not been entered bill wise. There is a need to adjust the ledger entries against the bill entries.


The system has been designed to work across multiple companies. 

with various outstanding bills in the Tally system. There is direct integration with Tally. The data capture can also be done using Turbodata. The following method can be used for resolving the same:


a.) Check for a given  party whether the bill entries are pending or not. This can be done by doing the comparison between 2 reports from Turbodata

Trial balance analysis with ledger flattening(Ledger Balance)

Payable and receivable snapshot with ledger flattening(Payableandreceivable_snapshot). 

The ledger  hierarchies shall help verify of the bills belong to the correct group parent.

If there is a difference between the closing ledger balance and total from the bill details then bill adjustment needs  to be done.


b.) Look at the complete cash flow statement(debit entries)  from the Ledgerview(here 'isvoid' and 'iscancelled' vouchers are to be excluded). 

The filter conditions include the following:

At the ledger_3 filter use 'Cash' Bank statement'. 

This indicates that there has been cash outflow movement for the given party(partyledgername would need to be chosen). We would consider the debit entries of cash and bank  for the same.




c.) Select those entries in part b.) that are not part of the voucherledgerbill movements. For the same the entire voucher ledger bill history for the set of firms shall need to be extracted.

The extract has been given in the object voucherledgerbill. The comparison shall be done using masterid and companyname.

After the above analysis we shall get the following 2 set of entries:

i.) Debit cash and bank ledger entries not adjusted against any bill(Ledgerview)

ii.) Debit  cash and bank ledger entries not associated with any bill(Voucherledgerbill)

Manual interface: Based on the unadjusted entries for the parties, the client to indicate which ledger movements are for the bill and which ledger movements are not associated with any bill. The Turbodata interface shall help with the same. The client team will help with the same.



The ledger payments not adjusted against the bills shall then be extracted from the ledger movement.


Usage of Turbodata(SQL Server):Hereafter we insert the data into Turbodata SQL Server module. The bill entries in the database are adjusted based on the ledger movement and the bill due dates. We look at partyledgername, bill amount, bill due dates for automated adjustment


Usage of the python data capture script to confirm the adjustment for each bill: Turbodata input forms shall then be used to adjust the amount for each bill. On approval by the required authorities the data shall be entered into Turbodata and Tally friendly Excel module


Note: the logic for post dated checks and on accounts balances shall need to be indicated by the end client.

The adjustment against each bill shall need to be done at the Turbodata data capture level.


For basic extraction please contact the following


Name: Apoorv Chaturvedi

email: support@turbodatatool.com;support@mndatasolutions.com

Phone:+91-8802466356


No comments:

Post a Comment

Initial and Incremental data Load Template by M&N Business Intelligence-SAP Data Services

  INCREMENTAL LOAD/CREATION OF DIMENSION TABLE LOGIC AT SAP DATA SERVICES END CLIENT In this particular document we shall be looking at the ...