Warner Music Group / Professional experience
Make the steps, owners, and controls clear
The problem
Incomplete finance diagrams did not explain who did what, how the steps connected, or where controls fit.
My contribution
I identified gaps, proposed the flow, and validated models, policies, and control links with process owners and subject-matter experts.
Approved models supported implementation, training, reference, and audits where applicable.
02 / See the thinking in practice.
Explore an example.
Illustrative process
Follow one purchase from request to payment.
Select a step to see its risk, safeguard, owner, and evidence.
01 / Request
Check authority before committing spend.
What could go wrong?
A purchase is requested without enough budget or the right approval.
What protects the process?
Check the budget and route the request to the approvers required for its amount.
- Who owns the check?
- Procurement operations
- When does it run?
- Every purchase request
Control detail
Preventive control · budget check and approval matrix. Review exceptions and overrides.
02 / Supplier
Use a supplier the business has approved.
What could go wrong?
An order goes to an unapproved, duplicate, or inactive supplier.
What protects the process?
Validate the supplier before issuing the purchase order. Route new suppliers through a separate review.
- Who owns the check?
- Supplier data team
- When does it run?
- Every order; supplier records reviewed quarterly
Control detail
Preventive control · supplier validation and separate approval for new supplier requests.
03 / Receipt
Confirm delivery before processing the invoice.
What could go wrong?
The business pays for goods or services it never received.
What protects the process?
Require a goods receipt or confirmation from the person who requested the service.
- Who owns the check?
- Receiving team / request owner
- When does it run?
- Every receipt
Control detail
Preventive control · receipt confirmation before invoice posting; review outstanding receipts.
04 / Invoice
Pay for what was ordered and received.
What could go wrong?
An invoice is paid twice, or its amount does not match the order and receipt.
What protects the process?
Compare the purchase order, receipt, and invoice. Flag mismatches and block duplicate invoices.
- Who owns the check?
- Accounts payable
- When does it run?
- Every invoice
Try the invoice check.
Choose a fictional sample. The check should catch the exception.
- Order
- 250
- Received
- 200
- Invoice
- 250
Illustrative amounts in the same currency. This demonstrates an exact-match and duplicate check; real systems also use agreed tolerances and approval rules.
Control detail
Preventive automated control · three-way match with agreed tolerances; duplicate checks use supplier, invoice number, and amount.
05 / Payment
Verify the destination before releasing funds.
What could go wrong?
A payment goes to changed or fraudulent bank details.
What protects the process?
Verify bank-detail changes and require a second approver. Apply the approval rules for the payment run.
- Who owns the check?
- Treasury / accounts payable
- When does it run?
- Every bank-detail change and payment run
Control detail
Preventive control · callback verification for changed bank details, separate approval, and review of bank-change reports.
03 / Bring it back to the role.
What this demonstrates.
I connect a process to responsibilities, exception paths, controls, and the evidence needed to review it.
Project scope and example context
The purchase and invoice records are fictional. Historical scope: 181 models, approximately 120 narratives, and maintenance of an existing 262-control matrix.