e-Reconciliation and BA/BS: the short route to fewer period-end surprises

Every finance team knows the scene: the last week of the month-end close, account balances are extracted, reconciliation letters are printed from a Word template, sent by e-mail, and the replies are marked in a spreadsheet as "confirmed / disputed / no reply". BA/BS forms live in a separate table and are compared by hand with the counterparty's declaration. Across hundreds of accounts this stretches the close by days; the real cost surfaces as BA/BS mismatches in a tax inspection. This article walks through turning reconciliation from e-mail traffic into a traceable SAP process.

Why reconciliation always stalls in the same place

The problem is not writing letters; it is tracking the replies. Without a system link between the letter sent and the reply received, who answered, who has a discrepancy and which document caused it can only be read from manually merged tables — and next month the same table is rebuilt from scratch. On the BA/BS side, the gap between the declared amount and the counterparty's declaration is usually a period shift, a credit note or an exchange difference, but finding it requires comparing both parties' document lists line by line.

Process design: bulk generation, electronic dispatch, replies per account

The e-Reconciliation solution we build inside SAP has three steps. First, reconciliation letters and BA/BS forms are generated in bulk from account balances for the selected period — customers, vendors or both, per company code and currency. Second, the documents are sent electronically to the counterparty, and the dispatch record is written to the account. Third, the confirmation or dispute reply is recorded per account; in a dispute, the balance and difference reported by the counterparty are written to the document. Unreconciled accounts drop into a monitoring list with the difference amount and are managed from there throughout the month.

BA/BS: automatic comparison with the counterparty's declaration

The real gain in BA/BS forms is bringing the counterparty's declaration into the system and comparing it automatically with the document list in SAP. When a difference appears, the solution lists which documents exist on one side but not the other; period shifts and credit notes usually reveal themselves there. The BA/BS mismatch is therefore seen before the return is filed, not after, and the correcting entry is posted in time.

Linking the bank side into the same chain

A significant share of reconciliation differences comes from collections and payments reaching the account late. That is why we recommend building e-Reconciliation together with the electronic bank statement solution: bank movements are imported into SAP automatically in MT940 or CAMT.053 format and cleared against customer and vendor accounts by rule; the account balance is current at end of day and the reconciliation letter goes out with the right figure. The same chain starts with direct debit integration and ends with reconciliation.

Tying it into the close calendar

Once the process is built, the most important task is making it a fixed step in the close calendar: letters going out on the second working day after period end, a defined reply window, a reminder rule for accounts with no reply, and the monitoring list on screen in the close meeting. When the process is visible, reconciliation stops being a source of surprises and becomes a routine line in the close.

Conclusion

When reconciliation is built as a system process, three things change: who replied, who has a discrepancy and which document it comes from are answered on one screen; BA/BS mismatches are caught before the return; and the close no longer stalls in e-mail traffic during the last week. The e-Reconciliation solution in our catalogue, together with the electronic bank statement and direct debit solutions, closes this chain end to end.