Learn to identify transactions in the bank statements that do not exist in the general ledger. Transactions are made manually on online banking and are not recorded in the general ledger so that they cannot be noticed by management, for example an employee borrowing funds through unauthorized payments. This course gives you the fraud scenario, the SAP data you need from ECC or S/4HANA, the Python code and logic, and a hands-on dashboard with an AI chatbot to test your data literacy.
Video lessons · Quiz included · Certificate of completion
€99,00
30-day satisfaction guarantee · Cancel anytime
Understand the real fraud scenario behind the analysis.
Get the exact SAP data and Python logic to run it.
Practise on a live dashboard with an AI chatbot.
Forget to record bank-out If a fraudster creates unusual payments, it could be that the Electronic Bank Statements (EBS) module…
Bank reconciliation process The bank reconciliation process is normally done monthly as part of month-end closing. The values on the…
House banks The T012 table is the list of house bank accounts. The general ledger account relating to each house…
House banks The T012 table is the list of house bank accounts. The general ledger account relating to each house…
Strategy We can check if there is a risk that bank-out transactions are not posted in three ways: Link the…
Strategy We can check if there is a risk that bank-out transactions are not posted in three ways: Link the…
Use the dashboard below to see if there are any bank movements that were not posted.
Founder, 300Framework · Former Big 4 SAP audit lead
For 25 years I sat on the audit side of SAP — chasing exceptions, untangling P2P breakdowns, explaining to finance teams why their controls weren't catching what they thought.
The 300Framework distills what actually works: the questions that surface real risk, the SAP queries that pull the right data, the workflows that turn findings into fixes. It's the playbook I wish I'd had on day one.
SAP Certified · Big 4 alumna · 189 courses authored · Based in Lisbon
The risk
Transactions are made manually on online banking and are not recorded in the general ledger so that they cannot be noticed by management, for example an employee borrowing funds through unauthorized payments.
What you’ll learn
This course teaches the Unrecorded bank-out analysis from the Treasury area of the 300 Framework (Bank reconciliation): how to identify transactions in the bank statements that do not exist in the general ledger. We start with the real-life fraud scenarios behind it, then give you the accounting and SAP background you need to judge whether the data is genuinely pointing to a problem in the specific context of your organisation.
The data and the code
You’ll get the exact SAP data required to run this analysis from either ECC or S/4HANA — the relevant tables, fields and how to join them — followed by a walk-through of the Python code and its logic: the filters, the joins, the algorithms, and the Artificial Intelligence tools you can layer on to enhance your result set.
Test your skills
Finally, you’ll put it into practice on a real dashboard, answering questions from our chatbot to find the exceptions in the data and choose the most interesting samples to investigate.
Taught by our experts in fraud detection, internal audit, internal control and SAP.
READY WHEN YOU ARE
Get instant access. Lifetime updates within your access period. Cancel anytime.
€99,00
30-day money-back guarantee · Instant access · Certificate included
The methodology behind 25 years of SAP audit excellence.
by Aufinia