BASIS Package Custom development

SAP Access and Payment Risk Audit Pack

Short answer: A six-component pack that brings together the controls asked most often in the yearly IT and finance audit: users with critical authorizations, segregation of duties conflicts, expiring role assignments, automatic locking of leavers' SAP users, duplicate vendor invoices and bank details change control. Installation is a single transport.

Installation and adaptation
XL · 17–25 working days
Version
1.0
What's in the package
6 components
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

Why a package?

An auditor asks about two kinds of risk: who can access what, and whether that access can turn into a payment. When authorization reports are prepared in IT and duplicate invoice and bank change checks in finance, the same user's traces on both sides are never combined. The pack runs the six controls with one company code and user group selection; the audit file is prepared in one go, leavers' users are locked on their leaving day, and the controls continue all year as scheduled jobs.

Who uses it? Internal audit, IT security and authorization teams, financial controllers and compliance teams preparing for the external audit.

What's in the package

Access: critical authorizations such as SAP_ALL, debugging and table maintenance

Access: conflicting authorizations based on the company's control matrix

BASIS Report Custom ALV report

Segregation of Duties (SoD) Conflict Report by User

A custom ALV report that lists users who can run conflicting activities together (for example changing vendor master data and running the payment …

USR02 · AGR_USERS · AGR_1251 · TSTC

Access: role assignments that are expiring or expired but still on the user

BASIS Report Custom ALV report

Expiring and Expired Role Assignments Report

A custom ALV report that lists role assignments whose validity ends within the next N days or that have ended but are still on the user, with the …

AGR_USERS · AGR_TEXTS · AGR_DEFINE · AGR_1016

Access: locking leavers' users on their leaving day

HCM Program Custom Background program

Automatic SAP User Lock Job for Leaving Employees

A background job that, on the leaving date, automatically locks the SAP users stored in infotype 0105 for employees with a recorded leaving action and …

PA0000 · PA0001 · PA0105 · USR02

Payment: possible duplicate invoices, including differently typed references

FI Report Custom ALV report

Duplicate Vendor Invoice Check Report

A custom ALV report that compares posted vendor invoices by reference number, amount and document date and lists possible duplicates in groups. …

BSIP · BKPF · LFA1 · BSIK

Payment: bank details changes and payments made right after them

What you receive

  • Transport request: ABAP source code, transaction codes and message class
  • Settings tables for critical authorization and segregation of duties rules
  • Background job variants and email distribution settings
  • Installation and user guide (TR/EN)
  • Rule set and authorization adjustment for your system
  • User training
Compatibility
SAP ECC 6.0 and S/4HANA (on-premise and Private Edition). The leaver lock job needs SAP HCM personnel administration in the same system with SAP user IDs stored in infotype 0105. On S/4HANA, vendor invoice line items are read through the compatibility views.
License
One-time license; the source code stays with you. Optional yearly support and updates.

Version history

  1. v1.0 First release: five control reports, the user lock job and a shared user group and company code selection.

Features

  • Delivered as a transport request
  • Runs as a background job The lock job can run every night, and the access and payment controls every week.
  • Send the result by email Locked users are reported to the security team, suspicious bank changes to the financial controller.
  • Export to Excel All control results are exported to Excel for the audit file.
  • Double-click drill-down to the document Rows drill down to the user, the role, the invoice or the change document.

Frequently asked questions

Does the pack replace a GRC solution?

No. The pack offers ready-made controls for companies that do not use a separate GRC product, or that use one but need quick, targeted lists for the audit. Rule sets are filled from your own control matrix.

What happens to the lock job if we do not use HCM?

The lock job reads leaving information from SAP HCM. For systems without HCM, reading the leaver list from a file is assessed separately for this component.

Does the duplicate invoice check stop the payment?

No. The report lists possible duplicates in groups; the decision to block a payment and the action itself stay with the finance team.

Related reports

BASIS Package Custom

Basis Daily System Check Pack

A five-component pack that turns the Basis team's morning check into one list: cancelled and long-running background jobs, scheduled jobs running …

5 components · v1.0

CA Package Custom

Business Partner Master Data Quality Pack

A four-component pack for keeping customer and vendor master data clean: mass business partner creation from Excel with a duplicate check, duplicate …

4 components · v1.0

HCM Package Custom

Salary Review and Pay Equity Pack

A three-component pack that supports the periodic salary review from start to finish: gender pay gap analysis by pay grade and job, mass upload of …

3 components · v1.0

Let us install this package on your system

Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.

Related report: SAP Access and Payment Risk Audit Pack