Skip to main content

As per my understanding vouchers are generated only when customer invoice turns to ‘PostedAuth’ state. We have cases where the voucher is created when invoice is printed and stuck in error.

So to sum up the invoice is still in ‘printed’ state, voucher is already created for the date it was printed and now we are not able to clear the error as the period has been changed.

Tried to replicate the scenario in test environments but with exact same details and parameters invoice is successfully getting processed without errors, so not sure what has caused the invoice to be stuck.

Please suggest.

 

Customer invoices will switch into the status posted/auth if they are printed as loong as all postings are created without error. In case it remains in status printed please refer to the Invoices with posting errors.

In this screen the invoices will be shown where the vouchers have not been created. Using RMB on an invoice in this screen, will show you  the error in detail. Most of the time it is a posting control or basic data setup issue.

When the underlying issue is solved (e.g. posting control setup) you can try to post the invoice with the RMB in the invoice with posting errors screen.

Usually the Invoice data is taken as voucher date. By clicking the checkbox in the header of the overview you can define a different date for the voucher (e.g. in case that the period is already closed)


Upon checking in the Invoices with posting errors screen (RMB→ Details) we can see the voucher number already assigned and the same voucher number can be seen in GL too.

So the situation is Customer invoice is not in PostedAuth state, Entries are posted in GL and therefore AR team cannot see the invoice in customer analysis for payment followup.


Reply