This example is relevant for both semiautomatic external and internal reconciliations.
The following open documents exist for a customer:
Document |
Transaction Number |
Posting Date |
Balance Due Amount |
---|---|---|---|
Invoice |
905 |
September 1, 2009 |
100 |
Payment |
906 |
September 1, 2009 |
100 |
Payment |
907 |
September 15, 2009 |
50 |
Payment |
908 |
October 5, 2009 |
50 |
Payment |
909 |
October 10, 2009 |
100 |
Note
If the payments were recorded as incoming payments, you need to perform semiautomatic internal reconciliation. If the payments were recorded as transactions on external statements (statements from a bank or business partner), you need to perform semiautomatic external reconciliation.
To perform semiautomatic reconciliation, you prioritize the following parameters to be considered when SAP Business One generates reconciliation recommendations for the reconciliation:
Parameter |
Priority Weighting |
Max. Deviation |
---|---|---|
Amount |
High |
50 |
Posting date |
High |
30 |
Reference 1 |
Skip |
— |
The Reconciliation Recommendations window displays the recommendations for the invoice:
For the three recommendations displayed, the payment with transaction number 906 is recommended as the best match. Its balance due does not deviate from the invoice balance due, and its posting date does not deviate as well.
Note
Payments with transaction number 908 and 909 do not appear in the recommendations since their posting date deviates by more than 30 days from the posting date of the invoice.