Technology Leverage

General Description
In this page, it shows the number of manual postings done during closing. With this, there is an aim to reduce the manual posting by 40% when compared versus 2018. Another indicator is the number of Swift Enabled bank accounts. It is target to have more than 80% of bank accounts being Swift Enabled.

Reduction of Manual Entries

Number of manual journal entries processed in SAP during the peak time (including CO manual postings) excluding RPA postings

Extraction of manual postings from the 4 ERPs: PF1, WP1, PI1 and PE1 - FB03 transaction
Period range: peak time => entry date from D-3 to D4
Criteria: manual document types, as per doc type matrix
Exclusions:

automatic reversals (FB08 transaction)
Purchasing scope transactions using Finance doc types: MIRO, MR8M
RPA user id: PT99376135, RPA_RTR_6, RPA_RTR_7
BECICC user (for PI1)
Batch inputs sessions (*Batch*)

Comparison between month of KPI reporting vs baseline

Target:

Reduction of manual entries by 40% when compared to previous year (Dec Y-1 as reference)

Refresh:

Monthly

Calculation of Swift Enabled Bank Accounts

% of bank accounts which are linked to Swifnet. Bank statements (MT940) are received on daily basis via Swift network, then uploaded and accounted automatically in ERPs. Payments ar processed in SAP and delivered STP to bank via Swift network

Legal Entity with control >50% => Source: AODOCS GAR List (column "Control %")
Total number of Bank Accounts => Source: Dilitrust report extracted to excel

Some filters are applied:

Multicurrency = Main Account

Account status <> Closed, Closing Process, transferred

sub status <> technical account

Total number of Swift Accounts => Source: SAP

Bank accounts which enable to receive electronic bank statements (MT940 message from Swift secured network)

Calculation: total number of Swift accounts / the total number of bank accounts

Sources
Manual file compiled by Finance. Underlying data coming from ERP (PF1, WP1, PI1 and PE1 )	https://docs.google.com/spreadsheets/d/12OLkXx9xGxummBRkMVNSm1ry2iNh1CLRVOa3gOnjQr4/edit#gid=1999081534
Refresh frequency	Monthly

Page tree

Frances Zhang

WW Solutions:

Marie-Line Ardito

Regional Animator:

Stephane Bourgeaud-Lignot/Emma Glasson (EMEA)

Karina Tsuji (LATAM & NAM)

Lilian Cheong (APAC)

In this page, it shows the number of manual postings done during closing. With this, there is an aim to reduce the manual posting by 40% when compared versus 2018. Another indicator is the number of Swift Enabled bank accounts. It is target to have more than 80% of bank accounts being Swift Enabled.

Number of manual journal entries processed in SAP during the peak time (including CO manual postings) excluding RPA postings

Extraction of manual postings from the 4 ERPs: PF1, WP1, PI1 and PE1 - FB03 transaction

Period range: peak time => entry date from D-3 to D4

Criteria: manual document types, as per doc type matrix

Exclusions:

automatic reversals (FB08 transaction)

Purchasing scope transactions using Finance doc types: MIRO, MR8M

RPA user id: PT99376135, RPA_RTR_6, RPA_RTR_7

BECICC user (for PI1)

Batch inputs sessions (Batch)

Comparison between month of KPI reporting vs baseline

% of bank accounts which are linked to Swifnet. Bank statements (MT940) are received on daily basis via Swift network, then uploaded and accounted automatically in ERPs. Payments ar processed in SAP and delivered STP to bank via Swift network

Legal Entity with control >50% => Source: AODOCS GAR List (column "Control %")

Total number of Bank Accounts => Source: Dilitrust report extracted to excel

Some filters are applied:

Multicurrency = Main Account

Account status <> Closed, Closing Process, transferred

sub status <> technical account

Total number of Swift Accounts => Source: SAP

Bank accounts which enable to receive electronic bank statements (MT940 message from Swift secured network)

Calculation: total number of Swift accounts / the total number of bank accounts

Manual file compiled by Finance. Underlying data coming from ERP (PF1, WP1, PI1 and PE1 )

https://docs.google.com/spreadsheets/d/12OLkXx9xGxummBRkMVNSm1ry2iNh1CLRVOa3gOnjQr4/edit#gid=1999081534

Refresh frequency

Monthly

Page tree

Technology Leverage

Frances Zhang

WW Solutions:

Marie-Line Ardito

Regional Animator:

Stephane Bourgeaud-Lignot/Emma Glasson (EMEA)

Karina Tsuji (LATAM & NAM)

Lilian Cheong (APAC)

Number of manual journal entries processed in SAP during the peak time (including CO manual postings) excluding RPA postings

Extraction of manual postings from the 4 ERPs: PF1, WP1, PI1 and PE1 - FB03 transaction

Period range: peak time => entry date from D-3 to D4

Criteria: manual document types, as per doc type matrix

Exclusions:

automatic reversals (FB08 transaction)

Purchasing scope transactions using Finance doc types: MIRO, MR8M

RPA user id: PT99376135, RPA_RTR_6, RPA_RTR_7

BECICC user (for PI1)

Batch inputs sessions (*Batch*)

Comparison between month of KPI reporting vs baseline

% of bank accounts which are linked to Swifnet. Bank statements (MT940) are received on daily basis via Swift network, then uploaded and accounted automatically in ERPs. Payments ar processed in SAP and delivered STP to bank via Swift network

Legal Entity with control >50% => Source: AODOCS GAR List (column "Control %")

Total number of Bank Accounts => Source: Dilitrust report extracted to excel

Some filters are applied:

Multicurrency = Main Account

Account status <> Closed, Closing Process, transferred

sub status <> technical account

Total number of Swift Accounts => Source: SAP

Bank accounts which enable to receive electronic bank statements (MT940 message from Swift secured network)

Calculation: total number of Swift accounts / the total number of bank accounts

Manual file compiled by Finance. Underlying data coming from ERP (PF1, WP1, PI1 and PE1 )

https://docs.google.com/spreadsheets/d/12OLkXx9xGxummBRkMVNSm1ry2iNh1CLRVOa3gOnjQr4/edit#gid=1999081534

Refresh frequency

Monthly

Batch inputs sessions (Batch)