Scribd
Upload
12 views2 pages

Clarifications

Uploaded by

Jeevan Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
12 views2 pages

Clarifications

Uploaded by

Jeevan Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

1.

How does validation of Beneficiary happens in Tally Product (Client), if the


feature is removed from Client ?
• Beneficiary validation will be done by the backend during the payment flow.
We are removing the pre validation module from the client as for some banks
the beneficiaries are at the user level and not the corporate level.
• Design detailing for bene validation will be shared once completed – currently
in progress.
2. I don’t see payment failure related buckets like Rejected, On HOLD in the new
design UI, Is it deliberate or a miss?
• It is a deliberate choice to only have grouped buckets in the summary view
and drill down will have collapsible sub buckets as follow
o Payments with actions required – Incorrect/ Incomplete Details,
Mismatch with master, On hold (As no on hold transactions were there
the bucket was missing in the view provided in the PPT.)
o Ready for sending to bank will not have any sub buckets
o Sent to bank will have 3 collapsible sub buckets – In progress,
Unsuccessful, Successful
3. In the consolidated view, are we going to provide drilldown from Totals row? If
so, if a company has good no. of transactions, then there is a possibility of total
row being hidden due to vertical scroll. Wherever we display Total at the
bottom of the product, we did not allow drilldown, this aspect has to be verified
and decided.
• Yes, We will provide the drill down from total column.
• Total row is given in the data section below the list of banks as we are
anticipating in most use cases the number of bank will be in the range of 3 to
10.
• However this point is noted. and we will consider to have total row as a fixed
at the bottom. Drill down into such total row will be a deviation from pattern.
We will discuss and come back.
4. Why consolidated view have 2 buttons F4 Bank & F5 Ledger. Isn't both serve
the same purpose ?
• F4: Bank is basically to filter the transaction for a particular debit bank ledger
• F5: Ledger is to filter transaction for particular credit ledger. (Will rename F5:
Ledger to “Payee Ledger”.) – To be verified during TE
5. Drilldown from Action Required bucket lists both Errors & Warnings.
• What is the behaviour of Accept as is button as it is not applicable for
Errors.
o When user tries to accept transactions with incomplete/ Incorrect
details client will show an error “ Mandatory details are missing for the
transaction” / “Transaction(s) contains incorrect details”/ “Transaction
has incomplete/ Incorrect details”
• Rules like selection of vouchers of errors & warnings and clicking on
Accept as is needs to be decided.
o Single transaction only with mismatches – Can be accepted as is
o Multiple transactions only with mismatches – Can be accepted as is
o Single transaction with incomplete incorrect details – “Mandatory
details are missing for the transaction” / “Transaction(s) contains
incorrect details”
o Multiple transactions with incomplete incorrect details : “Transaction
has incomplete/ Incorrect details”
o Multiple transactions across incomplete and mismatch : “Error :
Transaction has incomplete/ Incorrect details”. No transaction will get
accepted
• What is the need of Set Status button here as No payments can be part of
ePayments without resolving Errors or Warnings marked as Accept as is.
o Set status is ability to mark transactions as processed/ reconciled as
payments might have been done outside tally and user has created a
voucher just for recording purpose
• Are we not allowing marking Vouchers as Excluded ?
o Ability to exclude vouchers will not be supported anymore. This aspect
of exclusion is catered to with the help of set status
6. In Recon Report, What should happen to ePayments related buckets, if
ePayments are not enabled for selected Bank.
• For banks where e payments are not enabled the bifurcation will not be shown
in the recon summary view.
• Also for banks with e payments enabled such bifurcation will be visible with
F12 config to show e payments transactions in a summary view
• Will get back with detailing of all the scenarios
7. In Preview Report, using Basis of Values, if Include Warning vouchers are
selected, Are the vouchers with Warnings show warning details in Explode by
default ?
• Yes, Voucher will have warnings in explode by default. Indicating which
details are not matching with the master.
• Will take the call on whether to show transaction with mismatch within
collapsible section or in a flat list view with “transactions without warning”.

You might also like