Solutions AP Assure AP Accurate AP Automate AP Assist AP Analyse AP Service Pricing Integrations About Us Resources Blog Videos Case Studies Request a Demo
Guide

SAP supplier statement reconciliation: using the data extract you already have

How a mining company reused its existing SAP data extract with AP Accurate, reducing reconciliation workload by 80% and increasing coverage to 92%.

Introducing supplier statement reconciliation software does not always mean building a new connection to SAP.

For one South African mining company, the starting point was a data extract already supporting its reconciliation process. AP Accurate was configured to work with that extract, allowing the business to replace its existing reconciliation system without rebuilding the SAP data feed.

The result was an 80% reduction in reconciliation workload, with reconciliation coverage increasing to 92%.

The change also helped address a familiar month-end problem: too many supplier statements arriving at once.

The challenge: replace the reconciliation system without rebuilding the SAP feed

The mining company wanted to improve supplier statement reconciliation while retaining its established SAP extraction process.

That distinction mattered. Changing the application used to reconcile statements did not necessarily require changing how SAP supplied the underlying records.

The company also faced a timing problem. Statements arriving on the final day of the month concentrated matching, investigation and document chasing into an already busy period.

The objective was to reduce that workload and extend reconciliation coverage without disrupting the existing data extraction process.

How the existing SAP data extract was used

The company already had a process for extracting SAP records for reconciliation.

Rather than replacing that process, AP Accurate was configured to work with its output. The extract continued to provide the accounting data against which supplier statement lines could be compared.

This retained the established SAP data feed while changing the reconciliation work performed after the data became available.

The case study does not specify the extract’s file format, SAP transaction codes or individual fields. The important implementation point is that the existing output was usable by AP Accurate, so a replacement feed did not need to be built.

The extract supplied the business’s records

Supplier statement reconciliation needs two views of the account:

  • The supplier’s statement, showing the transactions and balance it considers outstanding.
  • The corresponding records from the customer’s accounting system.

In this implementation, the existing SAP extract supplied the accounting side of that comparison.

AP Accurate used those records alongside supplier statements to perform reconciliation and highlight differences requiring attention.

AP Accurate replaced the reconciliation work around the data

Retaining the extract did not mean retaining the manual workload.

AP Accurate automated routine reconciliation activity, while statement reminders and missing document chasing helped keep the process moving.

This allowed the business to improve how statements were collected, compared and followed up without first redesigning its SAP extraction process.

What another SAP team should check before reusing an extract

An existing extract is a useful starting point. Its suitability still needs to be assessed against the reconciliation scope.

For another organisation, the review should establish:

Which records are included?
The data needs to cover the suppliers, entities and transactions being reconciled.

Can transactions be identified consistently?
Supplier identifiers, document references, amounts and currencies need to be understood and mapped correctly.

What does each status mean?
An open item, a cleared item and a document awaiting processing can represent different positions. Those distinctions affect how statement differences are interpreted.

How current is the extract?
A statement dated after the extract may include transactions that have not yet appeared in the supplied data. The reconciliation needs to recognise those timing differences.

What sits outside the extract?
Payment allocation checks or GRNI investigations may require additional records. A supplier transaction extract should not be assumed to contain everything needed for every control.

These are scoping questions for a new implementation, rather than a description of the mining company’s specific extract.

Finding the month-end bottleneck

The SAP feed was only one part of the process.

AP Analyse identified a concentration of supplier statements arriving at month-end. This created a surge of work just when the finance team was trying to complete its reporting.

Faster matching alone would not address the timing of that demand.

AP Accurate automated statement reminders and missing document chasing, helping the team obtain statements and supporting documents throughout the month.

That gave the team more opportunity to investigate differences before the final-day rush.

The results: less work and broader coverage

The mining company reported:

MeasureReported result
Reconciliation workloadReduced by 80%
Reconciliation coverageIncreased to 92%
SAP data extractionExisting extract retained
Month-end workloadActivity spread more evenly through the month

The workload reduction and increased coverage are distinct outcomes.

Reducing the effort involved in reconciliation creates capacity. Extending coverage means more supplier accounts can benefit from the checks.

For this customer, retaining the SAP feed supported the transition, while automation and earlier supplier follow-up improved the ongoing process.

Read the original mining customer case study (PDF), or explore all customer case studies.

What this means for SAP finance teams

If supplier reconciliation still depends on spreadsheets, repeated matching and email chasing, it is worth looking at the data your business already produces.

An established SAP extract may provide a practical route into a proof of concept. That allows your team to assess the reconciliation results before deciding whether any changes to the feed are needed.

The mining case study demonstrates one successful implementation using an existing extract. It does not mean every SAP extract will be suitable without review, or that every customer will achieve the same results.

The first step is to compare your available data with the work you want to automate.

See what AP Accurate can do with your SAP data

AP Accurate helps finance teams collect supplier statements, reconcile them against accounting records and chase missing documents.

For SAP users, that can begin with a review of an existing extract and a representative set of supplier statements.

We can then agree a free proof of concept using your own data, show the matches and exceptions, and discuss what a production process would require.

Based on an anonymous South African mining customer case study supplied by 360° AP. Individual outcomes vary.

← Back to blog

See AP Accurate working with your own data.

Let’s explore how much time your team could save on supplier statement reconciliation.

Get a Free Statement Reconciliation Review