Your ERP Changed. Your Reconciliation Process Probably Did Not.

When organisations move to RISE with SAP, their core ERP changes but standard SAP still lacks native functionality for vendor statement reconciliation, balance sheet reconciliation, and cross-entity open item clearing. These gaps carry over into the new environment.

Finance teams spend months planning the technical migration to S/4HANA. They map custom code and test integrations. They retrain users on new processes. Reconciliation processes rarely get the same attention. The assumption is that moving to a newer platform fixes the problem. It does not. The reconciliation gaps that existed on ECC exist on RISE with SAP too, and they surface at exactly the wrong time: month-end close, audit prep, supplier disputes.

What does standard SAP cover for reconciliation?

Standard SAP provides basic clearing functionality within a single company code and general ledger account. For organisations with straightforward structures, this covers a portion of day-to-day transaction processing.

SAP delivers automatic payment programmes, dunning runs, and standard financial reports out of the box. Within a single entity, you can clear open items against incoming payments using standard transaction codes. The system handles bank reconciliation through electronic bank statement processing. These capabilities exist on both ECC and S/4HANA, and they transfer into the RISE environment without modification.

What standard SAP does not do is where the problems sit. There is no native function to reconcile vendor statements against your accounts payable ledger. There is no built-in process for balance sheet account reconciliation at month-end. And while SAP can clear items within one company code, it cannot automate clearing across multiple company codes and account types. For a retailer running dozens of entities, hundreds of suppliers, and thousands of transactions per day, these are not edge cases. They are the core of the finance team’s workload.

S/4HANA introduced the Universal Journal and simplified data models, which improve reporting speed. But the reconciliation functions that were missing in ECC remain missing in S/4HANA. The architecture changed. The functional gap did not.

What reconciliation gaps remain after migrating to RISE?

Four specific reconciliation processes fall outside standard SAP functionality, and all four carry over unchanged into a RISE with SAP environment.

Vendor statement reconciliation

Suppliers send statements. Finance teams need to match those statements against the accounts payable ledger to identify discrepancies, missed invoices, duplicate payments, and timing differences. Standard SAP has no mechanism for this. Most organisations handle it in spreadsheets, downloading data from SAP into Excel and working through line-by-line comparison. After migration to RISE, the same spreadsheet process continues unless the team addresses it separately.

For a retailer managing 300 or more vendor relationships, this manual process consumes days of skilled resource every month.

Balance sheet reconciliation

Month-end balance sheet reconciliation requires finance teams to verify that every account balance is supported and approved with adequate explanation. Standard SAP does not provide a structured workflow for this. Teams typically export trial balance data, build reconciliation templates in Excel, and route approvals via email. The process is slow, error-prone, and difficult to audit.

On RISE, the data model is cleaner. The reconciliation workflow remains manual.

Cross-entity open item clearing

SAP’s standard clearing works within a single company code and GL account. Retailers operating across multiple legal entities, regions, or store groups need to clear intercompany balances, consolidate open items across entities, and match transactions that span organisational boundaries. Standard SAP cannot automate this. Finance teams build workarounds using manual journal entries and custom ABAP reports.

Those custom ABAP reports are often the first casualties of an S/4HANA migration, flagged during the custom code analysis and earmarked for remediation. The clearing gap widens during transition.

Customer remittance processing

Large customers paying against multiple invoices send remittance advices that need matching to open items on the customer account, with simultaneous clearing of the bank account. Standard SAP handles simple one-to-one matching but struggles with complex remittances involving partial payments, deductions, and high line counts. A retailer receiving an 87-line remittance from a major customer faces a manual matching exercise every time.

How SAP-certified add-ons fill the reconciliation gap

SAP’s certification programme exists to validate that third-party software runs correctly within the SAP environment. Certification means the add-on has been tested against SAP’s technical standards, validated for deployment on the specific platform, and approved to run inside the customer’s SAP instance without requiring external connectors or middleware.

For RISE with SAP specifically, this matters because the hosting environment is managed by SAP. Customers cannot install uncertified software into a managed RISE instance without SAP’s involvement. An add-on certified for RISE, such as BEST’s reconciliation modules (SAP certification number 22988 for S/4HANA Cloud Private Edition), deploys directly into the RISE environment. It runs inside SAP. Data stays inside SAP. Users access it through their existing SAP logins and authorisations.

BEST’s four modules address each of the gaps outlined above. Vendor statement reconciliation, balance sheet reconciliation, open item clearing, and customer remittance processing all run natively within SAP. There are no exports, no spreadsheets, no external databases. The audit trail, approval workflows, and management reporting sit within the same system the finance team already uses.

BEST also holds SAP Business Technology Platform certification (number 25513), which supports integration scenarios for organisations using BTP alongside their core S/4HANA instance.

The practical difference for a finance team is straightforward. Instead of downloading data into Excel, reconciling offline, and uploading corrections back into SAP, the entire process happens in one place. At Heineken Beverages, this approach produces a 99% auto-matching rate across more than 700 monthly reconciliations. At Ardagh Glass, an 87-line customer remittance loads and processes in nine seconds.

What finance teams should prioritise during migration

Organisations that have already been through S/4HANA migrations offer consistent lessons about reconciliation planning. Shoprite, Foodstuffs, and Heineken all run large, multi-entity SAP environments with high transaction volumes. Their experience points to four priorities.

Map your current reconciliation processes before you migrate

Many finance teams do not have documented reconciliation processes. The work lives in individual spreadsheets and personal workflows. During migration planning, catalogue every reconciliation process, including who owns it, what tools they use, how long it takes, and where the data comes from. Processes that rely on custom ABAP code need particular attention, because that code may not survive the move to S/4HANA without remediation.

Address reconciliation gaps during migration, not after

Retrofitting reconciliation tools into a live RISE environment is possible but adds cost and disruption. Foodstuffs, a New Zealand retailer, reduced reconciliation staff by 50% and cut the time for 300 vendor reconciliations from 1.5 days to 25 minutes by deploying automated reconciliation as part of their SAP programme. Treating reconciliation as a migration workstream rather than a post-go-live enhancement makes the business case stronger and the implementation simpler.

Test with production-volume data

Reconciliation processes that work in a test environment with 50 transactions often fail at production scale. Bacardi found that online processing delivered 40% more completed reconciliations with greater efficiency compared to their previous batch approach. Volume testing during the migration programme catches these issues before they affect a live month-end close.

Keep everything inside SAP

Every external tool added to the reconciliation process creates a data synchronisation problem and a new security boundary. Auditors will ask where the data sits and who maintains the integration. SAP-certified add-ons that run inside the SAP environment avoid these questions entirely.

Frequently asked questions

Does RISE with SAP include reconciliation tools?

RISE with SAP provides the S/4HANA platform, which includes standard clearing and payment processing within a single company code. It does not include native tools for vendor statement reconciliation, balance sheet reconciliation, or cross-entity open item clearing. These functions require SAP-certified add-on modules.

What changes in reconciliation after S/4HANA migration?

The data model changes with the Universal Journal, and some custom ABAP reports may need remediation. The core reconciliation gaps remain the same. Standard SAP on S/4HANA still lacks vendor statement matching, structured balance sheet reconciliation workflows, and automated cross-entity clearing.

Can I install third-party reconciliation software in a RISE environment?

RISE with SAP is a managed environment. Third-party software must hold SAP certification for S/4HANA Cloud Private Edition to deploy into RISE without additional approvals or workarounds. Certified add-ons deploy directly and run inside the SAP instance.

How long does it take to implement SAP reconciliation add-ons?

Implementation timescales vary by module and complexity, but organisations such as Foodstuffs have deployed vendor reconciliation within their broader SAP programme. Deploying during migration rather than retrofitting post-go-live reduces both cost and disruption.

What reconciliation results can finance teams expect from automation?

Results depend on transaction volumes and data quality. Heineken Beverages achieved a 99% auto-matching rate across 700 monthly reconciliations. Foodstuffs cut reconciliation staff by 50%. Consol Glass processes 87-line customer remittances in nine seconds. These are published, verifiable outcomes from production environments.