Problem invoices

You can use a problem code to indicate that a problem exists for a sales invoice. If the invoice-to business partner notifies you about a problem with the invoice and does not pay it, you can link a problem code to the invoice.

In the direct debits procedure, problem invoices are ignored. For each problem code, you can set an option to prevent linked invoices from being selected on reminder letters.

Use the Problem/Reason (tfacr0120m000) session to define problem codes. You can define different problem codes for different problems that can arise.

Some examples of problems are:

  • The business partner does not receive all goods
  • The business partner rejects the goods or some of the goods
  • The invoice amount is different from the business partner's order amount

For each problem type, you can indicate whether:

  • Reminders must still be sent that concern this invoice
  • The invoice must still be included in the direct debit selection

To indicate that a certain problem exists for a sales invoice, you can link the appropriate problem code to the invoice. You can manually link a problem code to an invoice:

  • When you register the invoice in the Sales Invoices (tfacr1110s000) session
  • At a later time in the Invoices (cisli3105m000) session

You can remove the problem code from the invoice in one of the above sessions.

Related topics