Generate e-Invoices for multiple vouchers through Exchange
Generating e-Invoices for multiple vouchers has its benefits. You may be creating numerous vouchers in a day and might want to generate e-Invoice for them in just one shot. In a different scenario, a data entry operator may be creating vouchers and then you may want to verify the vouchers to check if they have the right information for e-Invoice generation under e-Invoice Integration Phase. You can generate e-Invoices for multiple vouchers. In case you face difficulties such as Internet issues power cut, and so on, while generating e-Invoice during voucher creation, you can easily generate e-Invoices for such vouchers along with those ready for e-Invoice generation.
In TallyPrime, you can generate multiple e-Invoices in one shot, after which you get a clear summary of the vouchers for which e-Invoices are generated and those rejected by the e-Invoice System.
- Press Alt+Z (Exchange) > Send for e-Invoicing and press Enter.
The Send for e-Invoicing screen appears with the vouchers in the Ready for e-Invoice Generation section.
If there are vouchers in the Uncertain Transactions (Corrections Needed) section and those required to be reuploaded, then those will appear in the Send for e-Invoicing screen, too. - Press Spacebar to select the vouchers that you want to send for e-Invoicing.
- Press S (Send).
The Exchange Summary appears with vouchers for which e-Invoice is generated. Moreover, if there are some vouchers rejected by the e-Invoice System due to some incorrect information or other such reasons, then you will know the count of those vouchers too:
To view the e-Invoice details of any of the vouchers for which e-Invoice is generated, you can either drill down from the e-Invoice Generated section of the e-Invoice Overview report, or you can open the voucher in the display mode from any ledger vouchers report.
To know how to view e-Invoice details, refer to the View e-Invoice Details section.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article