← Back to Controls

OTC-11

Business Process:
Order to Cash
Sub-Process:
Billing
Control Type:
Preventative
Execution Type:
Automated
Effective Date:
Aug. 5, 2026

Control Description

The system automatically processes eligible unblocked deliveries via a scheduled nightly batch job to generate customer invoices, concurrently creating automated general ledger postings for trade accounts receivable and product revenue

Risk

If eligible deliveries are not processed accurately or completely into invoices and G/L postings through the automated batch job, revenue and trade receivables could be misstated (incomplete, inaccurate, or recorded in the wrong period). This could lead to material misstatements in financial reports and undetected discrepancies between shipping logs and accounting records.

Implementation Details

Implementation Details
• Background Job Configuration: Configure a recurring background job in SAP using transaction SM36 (or background scheduling tools like SAP Solution Manager running the billing background program (typically program RV60SBAT or transaction variant VF04

• Configure job monitoring within SAP Solution Manager (Focused Run / Job Management) or setup recipient lists directly in SAP (SM36 / Job definition) to trigger an immediate automated email or system notification to the IT Operations / Finance Application Support team if the job completes with an error status

Test Procedures

Test of Design (TOD)
• Job & Schedule Review: Inspect the background job definition in transaction SM37 or Solution Manager to verify recurrence and program parameters.

Alert Configuration Verification:

• Inspect the Solution Manager Alert Management setup or the job definition attributes (SM36) to confirm that explicit notification distribution lists (e.g., distribution group email addresses) are mapped to trigger upon job cancellation, failure, or negative completion status.

Test of Operating Effectiveness (TOE)
• Job Execution & Exception Log Review: Select a sample of operating dates. Review the execution logs in SM37 / Solution Manager to verify successful completion. For any jobs that failed during the period, inspect the incident/alert logs to verify that an automated notification was successfully dispatched to the designated support group within the defined SLA.

• Select a sample billing document generated by the job (using transaction VF03 or table VBRK).

◘ Click on the accounting document link (or view via transaction FB03 / table BKPF / BSEG) to drill directly into the financial posting.

◘ Expected Result: Verify that the accounting document concurrently debits the correct Trade Accounts Receivable reconciliation account (subledger customer balance updated) and credits the Product Revenue account, proving the automated end-to-end posting occurred without manual intervention.