23
Best Practices for Effective DSO Management and Reductions in Past Due Receivables Paul J. Clausen Corporate Director, Customer Financial Services

Best Practices for Effective DSO Management and Reductions in Past Due Receivables Paul J. Clausen Corporate Director, Customer Financial Services

Embed Size (px)

Citation preview

Best Practices for Effective DSO Management and Reductions in Past Due Receivables

Best Practices for Effective DSO Management and Reductions in Past Due ReceivablesPaul J. Clausen

Corporate Director, Customer Financial Services

Emerson OverviewEmerson Overview• Founded in 1890 – in business for 124 yrs

• Diversified global manufacturing and technology company.

• Business grouped by segments:• Process Management• Climate Technologies• Network Power• Industrial Automation• Commercial & Residential Solutions

– Emerson has approximately 135,000 employees and 235 manufacturing locations worldwide.

• Headquartered in St Louis, Missouri, USA• Publicly traded (NYSE : EMR)• Global product and market leadership• Recognized for engineering capabilities,

outstanding management process, and record of consistent long-term performance

• Sales of US$24.7 billion in fiscal year 2013

St. Louis headquartersSt. Louis headquarters

2

FY 2013 Sales By Business Segment FY 2013 Sales By Business Segment

SalesFY 2013 FY 2012 Δ $'s Δ %

Process Management $8,610 $7,899 $711 9.0 %Network Power 6,155 6,399 (244) (3.8)%Industrial Automation 4,885 5,188 (303) (5.8)%Climate Technologies 3,876 3,766 110 2.9 %Comm. & Res. Solutions 1,864 1,877 (13) (0.7)%

$25,390 $25,129 $261 1.0 %Eliminations (721) (717) (4) 0.6 %Total $24,669 $24,412 $257 1.1 %

3

Diversified Portfolio of CompaniesContinuous Portfolio Management Drives Growth!

FY13 Sales by GeographyFY13 Sales by Geography

44%

20%

24%

6% 6%

US & CanadaEuropeAsiaLatin AmericaMiddle East/Africa

37% Emerging Markets

4

Operating Cash Flow Drives Shareholder ValueOperating Cash Flow Drives Shareholder Value

FY2009 FY2010 FY2011 FY2012 FY2013

3.13.3 3.2 3.1

3.6

56%

63%

OCFShldr Payout

$ in Billions

5

Receivable LandscapeReceivable Landscape 32 Reporting Business Units that operate

autonomously– Each have their own President, CFO etc.

• Credit function reports to BU CFO

Business systems vary across the operating units

– Oracle

– SAP

– JDE

– Various other ERP platforms (some home grown)

Operate globally in 78 countries– Transactions in local language and

currency

– Majority of collections are supported in best cost locations

MANILA

CLUJ

XIAN

BEST COST RESOURCE UTILIZATION FOR COLLECTIONS

6

Perfect Execution….Perfect Execution…. A challenge to everyone in the company to better

understand our customers and then work and think in different ways and at new levels on their behalf

A cultural transformation that…– Reduces complexity

– Breaks down silos

– Strengthens collaboration across our organization

How Does Perfect(Ex) Apply to Receivables Management?

7

Our Receivables Effort Has Been Broad...Our Receivables Effort Has Been Broad...

Implement Corporate Sponsored Software Tools To Support The Effort …

Involve Executives To Call On Key

Accounts…

Utilize Best Cost Resources & Shared Services…8

Managing Disputes

Collections

Processing Payments

Billing

Credit Risk & Exposure

Sale

s Pol

icy

& S

uppo

rt Account R

eviews

Executive Oversight

Current Focus Evaluates Processes & Execution…Current Focus Evaluates Processes & Execution…

Methodology: Best-Practice Benchmarking− Emerson & Industry− 47 Elements Examined

1. Cash Cycle Elements

2. Supportive Processes

9

So What Happened in FY2013….So What Happened in FY2013…. Incorporating the principles of Perfect Execution, we developed a process of

evaluating a business unit’s performance based on defined best practices– Best Practices were cross functional and looked at all elements of the cash cycle

Understand and evaluate a B.U.’s processes, structure and overall approach to DSO management

Focus on Past Due reduction

Provide a set of recommendations (roadmap) for improvement

Credit policies and execution

Cross functional interaction that supports receivables

Executive involvement and focus given to DSO management

Understanding reasons for past dues and corrective actions employed

Dispute management processes and analysis

Establish what sales policies are in place that support receivables

Is there automation in place and how is it used to support Receivables

OBJECTIVES

CONSIDERATIONS

10

DSO Prioritization / Performance Model…DSO Prioritization / Performance Model…

Credit Risk & Exposure

Billing ProcessSupportive Sales Policy

& Interaction

MU

ST

HAV

ES Effective Credit Risk Policy Frequent Invoicing

Credit/Sales Proactive Efforts on Terms Approval Consequences For Slow Paying Customers

Processing Receipts

Managing Collections

Account Reviews

MU

ST

HAV

ES Rapid Remittance Posting Policy & Escalation Procedures

Frequent Customer Contact Sales, Credit, CS Collaboration

Managing Disputes

Managing Disputes

MU

ST

HAV

ES Early X-Functional

Communication

Root Cause Analysis & Corrective Action Taken

Actions Tracked

EXECUTION

POLICY

BUSINESS PROCESS

FOCUS

ON

EXECUTIVE OVERSIGHT

Perfect(Ex )

Projects?

Comprehensive Policies, Finance Lead, Supported Cross Functionally, & With Executive Meetings…

11

To Support the Objectives, on Site Visits Were Required With The Business Units…To Support the Objectives, on Site Visits Were Required With The Business Units…

Review various materials requested from the B.U. prior to an on-site visit– Written policies covering risk, collections and dispute management

– Standard terms and conditions

– Standard payment terms

– Most recently completed ICQ• Sales and AR tabs only

Documents reviewed on-site:– Organization structure of Finance

• Including the Credit function

– Key management organization structure

– Paretos for past due and or dispute reasons

– KPI’s produced to measure:• Collections productivity

• Past Due issues

• Dispute Issues

• Progress on corrective actions presented at most recent Pres. Council, Perfect (Ex) or Profit Reviews

The analysis is completed using Benchmarking tool while on site

ANALYSIS METHODOLOGY

Includes Actions to Resolve

12

What is The Benchmarking Tool?What is The Benchmarking Tool? Compares a B.U.’s performance to industry & Emerson best

practices for the elements of the cash cycle– Credit risk, billing, processing receipts, collections, managing disputes….

– Identifies gaps and opportunities

Also considers sales policy and support, customer account reviews, executive oversight and influence on receivables management

Identifies “Must Have” capabilities to build a foundation for performance in DSO management

– “DSO Performance Pyramid”

Considers the degree of automation employed to support processes

– Is data being collected, analyzed and actioned?BEST PRACTICE DSO MANAGEMENT IS NOT JUST A

FUNCTION OF FINANCE…IT IS AN ORGANIZATIONAL ISSUE

13

Benchmarking TemplateBenchmarking TemplateOversight

Business Unit: Emerson Network Power - Asia Region: DeviationsDate: July 22 - 24, 2013 = Essential Collection

Pre-Collection /"Foundation"

PROCESS BEST PRACTICES BEST PRACTICE EXPLANATION SCORE

MANAGING CREDIT RISK & EXPOSURE Credit Mgr/Dept Head

1 A defined credit risk management policy is utilized.Policy that defines establishing credit for new and existing customers, limits of authority (LOA), credit hold process, escalation and terms management.

2Regular and periodic account reviews are performed, and credit risks scorecards are utilized.

There is a continuous process for monitoring customer accounts to enable ongoing adjustments of credit assessment. Credit risk scorecards use multiple factors to categorize risk and to establish credit limits.

3 Credit limit controls are in place.There are tight controls of credit limits that are maintained in the ERP system. Exceptions are approved based on the credit policy LOA.

4 Effective customer data management is in place.Ownership and governance of customer master data is defined and includes Credit department as part of the process.

5Account updates and credit risk changes are shared and coordinated with other business units.

Within the business group, as well as across business groups or corporate where there is a common customer.

BILLING PROCESS Credit Mgr/Dept Head

6There is no ambiguity between payment terms and conditions on customer contract or PO and the payment terms in the ERP system.

Invoices are consistent with PO's and contracts.

7 Frequent invoicing. Invoices are issued at time of shipment, when services are performed, or acceptance as defined in contract .

8 Standard invoice format.There are clear and concise invoices with formats that are designed to minimize errors made by customers A/P, lockbox banks, and cash application personnel.

9 Automated invoice delivery processes are in place.Utilization of automated processes to deliver invoice to customer in the most effi cient and timely manner possible. Processes should minimize reliance on postal service delivery as primary method of delivery for invoices and related trade documents.

SUPPORTIVE SALES POLICY & INTERACTION Credit Mgr/Dept Head Sales Mgr/Head* CFO** GM***

10Credit Manager meets with Sales to review importance of DSO and Emerson focus on cash flow.

Credit Managers participate in sales meetings and other opportunities to communicate importance of cash flow and expectations to ensure customers pay Emerson according to agreed upon terms. *

PRE-COLLECTION

No evidence to support credit is engaged

Some interaction takes place

Interaction does take place and evidence supports that credit is part of annual sales meetings,

training and collaboration efforts

Invoices manually generated via Excel

ERP generated but with exceptions

ERP generated, no exceptions

No automation in place Some automation (EDI)

Fully automated process with established program to drive

customers to electronic delivery vs. paper based delivery

No Process exists to ensure consistency

Process but with exceptions

Process functioning without exceptions

No defined processProcess but with

exceptionsDaily invoicing, no exceptions

Ownership and governance not defined

Credit approves bill to customer set-up before

entered in ERP

Credit Dept. owns customer master, customers not set-up

without a P.O. Policy and governance in place

No sharingSome sharing, no

formalized processDocumented process with evidence it is functioning

CURRENT ASSESSMENT - DEGREE OF ADOPTIONInstructions: Please enter the number (1, 2, or 3) that best describes the current degree of adoption for each of the best practices listed below.

1 2 3

DSO - BEST PRACTICES ASSESSMENT

No credit limits in placeCredit limits in place in

ERP system

Credit limit exceptions process in place and documented in policy

and evidence it is functioning

No Policy Policy inadequatePolicy in place with evidence to

support

No reviewsReviews take place; no

scorecard

Reviews take place minimum of quarterly, and scorecards utilized

w/ multiple scoring factors

46 Identified best practices– Cross functional

– Follows the DSO Performance Model

Assessment is based on 3 point scale– Assesses the degree to which the BU has adopted a particular best practice.

• Not intended to be critical of current processes or procedures

Recommendations are based on degree of adoption– Short term focus on the “must haves”

– Long term focus on strategic initiatives14

From The Visit, Develop Priority Based Actions For BU’s, Roadmap for Improvement…From The Visit, Develop Priority Based Actions For BU’s, Roadmap for Improvement…

MANAGING CREDIT RISK & EXPOSURE

1 A defined credit risk management policy is utilized.

2Regular and periodic account reviews are performed, and credit risks scorecards are utilized.

3 Credit limit controls are in place.

4 Effective customer data management is in place.

5Account updates and credit risk changes are shared and coordinated with other business units.

BILLING PROCESS

6There is no ambiguity between payment terms and conditions on customer contract or PO and the payment terms in the ERP system.

7 Frequent invoicing.

8 Standard invoice format.

9 Automated invoice delivery processes are in place.

RECOMMENDATIONSPRE-COLLECTION

There is no structured policy that defines how credit risk is managed by the shared services team. Customers are set-up before an order is received with a default credit limit of $1,000 USD. The only review that takes place is when an order is entered >$1,000. The analysts get a notification on their credit review screen. The only reviews that take place are when an order exceeds the credit limit, an eRAM packet is pulled and the score is updated based on the seeded EMR Scorecard in eRAM. RECOMMENDATION: Establish a comprehensive Risk Management policy that defines process flows and expectations on managing Risk, Order Hold Management, Account Reviews, Escalation Procedures and limits of authority for approving limits and overriding credit decisions.

Current process only requires a customer review when a customer exceeds their credit limit. RECOMMENDATION: Establish a process as part of the Risk Policy whereby regular and periodic reviews are taking place. Utilizing the account refresh tools available in eRAM is a best practice for updating customer risk information. Utilizing the scorecards in eRAM, and using the Filters function in eRAM, will allow for segmenting the customer base based on Risk Bands. Changes in Risk can then be highlighted to adjust collections policy and strategy based on this changes in Risk. For higher volume customers, financial statement reviews should be conducted on an annual basis at a minimum. For those customers that are publicly traded, there is a Corporate resource available in Manila for doing these analysis for the B.U. Adjustments to the review frequency are determined based on this analysis. (i.e. Quarterly, semi-annual or annual).

The current ERP system does have functionality to place an order on hold if the customer credit limit is exceeded. However, Customer set-up is controlled by another functional area. Current procedure is that if the customer set-up is for a "Bill to" or "Sold to" entity, the entry personnel are instructed to default the limit to $1,000. There is no control in place to ensure that the credit limit value being entered is correct. RECOMMENDATION: The Credit function should have control of customer records being entered into the ERP system if the usage is for a "Bill to" or "Sold to" entity. ,This allows the Credit function to ensure that the proper credit limit is established at the time of set-up, that we are not creating redundant records in the ERP system and that the proper relationships are defined for those customers that have multiple locations.

Refer to #3 above. In reviewing the customer set-up process with both Credit and Customer Service, ownership for the customer set-up process is not clear. Customer Service was of the understanding that Credit controlled this process; the Credit function indicated it was done in Costa Rica, but were not aware of ownership for the process. RECOMMENDATION: Establish a procedure and policy for approving and entering customer data into the ERP system. The policy should define the Credit function as having ownership for Bill to and Sold to customer set-ups to control the credit limit and terms set-up. The policy also should define governance and standards to keep the database clean and minimize redundancy. The customer data model should also be defined as part of this policy/process. As you migrate to Oracle, managing customers in the TCA model can be complex, but offers tremendous flexibility in how you manage customer data in the Oracle environment. Best Practice is to define the model, define ownership, restrict access to add and change records, establish a standards policy, and governance.

With the establishment of the Shared Services Credit function for ENP North America, the legacy Services, ERS/HVM and Product credit and collections are managed by the Shared Services organization. There is significant overlap in the customer base between service and product. However, prior to the consolidation under shared services, there was no evidence of sharing customer data across business units within the ENPS group or Emerson. RECOMMENDATION: As part of your policy development, expectations about establishing a discipline to share data about problem customers across the business group, and Emerson is a best practice.

Contract review process is driven by legal, and all T&C's are managed and approved with the exception of payment terms. Credit is only brought into the process when contract specify's non-standard terms. At that point, there is no opportunity for Credit to engage in other T&C issues that may impact the collection process. RECOMMENDATION: Best practice engages the credit function up front during the negotiation process. The collections process in many cases uncovers contract language that impedes our ability to collect payments when due. Involving the Credit function in the contract negotiation process provides the opportunity to identify restrictive language that impedes collections as well as resolving payment terms issues before the contract is signed. Develop a template or checklist that includes all functional areas of responsibility to sign off before the contract is signed will ensure we are aligned internally on the customer expectation and our ability to meet those expectations. We should have organizational alignment on payment terms issues before the contract is stamped and returned to the customer.

Current ERP system generates an invoice file daily that produces a print invoice daily for all customers for Services and Product. Printed invoices are sorted in Columbus and those customers that are on web invoices or require manual invoices due to AIA summary billing or other customer requirements are pulled so that a manual invoice or web portal invoice can be entered to the customers web site. RECOMMENDATION: Short term, recommend having web portal invoice documents printed in Costa Rica. The current practice is they are printed in Columbus, sorted, and then scanned and e-mailed to the team in Costa Rica to input into the web portals. There is no tracking of this process and therefore no assurance that the invoices are being loaded to the web portals in a timely manner. Long term: Consider implementing the BillTrust solution. They have web services interfaces that will automate the process of web presentment. Implementing BillTrust will also standardize the invoice presentment process as Services utilizes Eaton Forms and Product is using traditional mail services to send invoices. Implementing BillTrust now will allow for easier implementation when the business migrates to Oracle as part of the next age project. At that time, all the set-up work, design templates and web portal services will already be established, and the Oracle work will only involve the pointing of the print queue to the BillTrust portal. For other manual documents, other than AIA invoice requirements, this is the result of shipping from multiple ship points at different times when customer requirement is for a single shipment and single invoice as stated on the P.O. This is a business process issue and should be managed cross functionally in the organization to identify a suitable business process that aligns with customer expectation and eliminates the manual processes currently in place to generate these invoice documents.

No recommendations at this time. Invoice formats are different between the businesses (Services, Product, ERS/HVM). Suggest looking at this if you adopt recommendation in #7 above and utilize the BillTrust services for invoice formats. This allows you to develop common look and feel across the businesses in your invoice documents.

See recommendation in #7 above. Automating the process will allow you to track when the customer is getting the invoice document, eliminate delays, minimize impacts of USPS delays, and provides for a direct link to invoice documents from the GetPaid collections automation software.

Short Term Actions Long Term Actions To Receivables Excellence

Communicate Findings And Recommendations To Key BU Personnel (President, CFO, Financial Services/Credit Personnel)

15

What Have We Learned Thus Far?What Have We Learned Thus Far?

Benchmarking ReviewsBenchmarking Reviews In FY2013 we Conducted 8

Reviews– North America

– Columbia

– Brazil

– Mexico

– Costa Rica

– Manila

– Australia

– Singapore

In Q1 FY2014 we have conducted 8 & 2 Follow-up Reviews

– Europe HQ

– United Kingdom

– Spain

– Italy

– Turkey

– France (2)

– Hong Kong

Extensive Reviews on site, usually 2 – 3 Days

Meet with:– General Manager or President

– CFO

– VP Sales

– Operations

– Billing

– Customer Service

– Credit Manager and staff

360° Format one on one interviews

17

A Comprehensive Credit Policy Is The “Foundation” For Good DSO’s… A Comprehensive Credit Policy Is The “Foundation” For Good DSO’s… Key Elements Of The Policy:− Clarifies Options Available If Credit

Limit Cannot Be Granted (For Past Dues & Limit Overages)

− Covers New & Existing Customers.− Clearly Defines Escalation Processes

− Who Does What, When…− When To Stop Shipments…− Final Authority Levels

− Defines Collections Process− Who to Contact− When to make the contact− Contact method− Follow-up and Escalation

procedures − Covers Dispute Management Process− Specifies Non-Standard T&C’s Approval

Process With Limits Of Authority− Clarifies Process Flow, Documentation,

& Data Required For Approval

• Do The BU’s Have Documented Policies Covering These Elements?

• Are They Using Automation Tools?

18

Cross-Functionally Defined Processes Are Necessary To Support The Effort…Cross-Functionally Defined Processes Are Necessary To Support The Effort…

Best Practice Example

− Cross-Functional Processes Should Cover:

• Contact Frequency• Escalations • Dispute Resolution

− Identified & Agreed To Cross Functionally

− Expectations Understood− Cover Multiple Customer

Segmentations

• Are Roadmaps Utilized?• Do Sales, Operations, & Executive Personnel

Know Their Roles & When To Get Involved?19

Elements Of a Collections Policy:

Minimizing Disputes Improves Timely Collections, Improves Customer Satisfaction… Minimizing Disputes Improves Timely Collections, Improves Customer Satisfaction…

Example Of The Challenge

− Quick Resolution Policies Are Needed

− Track By Type & Reason Code

− A Higher-Level Roll-Up Tracking Document For Executives

− Root-Cause Analysis For Major Issues Required

• Are Disputes Being Tracked?• Are There Business Process Improvement Projects To

Correct?

20

Knowing Reasons for Past Dues is Key:

Executive Oversight Is Imperative…Executive Oversight Is Imperative…

− Not Just The CFO’s Job− Key Executives Should Be

Assigned To Relationship / Strategic Accounts

− Regularly Scheduled Business Process Meetings Should Be Conducted

• e.g. S&OP• Aging Reviews• Disputed Items Review

− Reporting Must Be Targeted and Specific

• Why is it past due• Action needed to resolve• Who owns the action• Expected resolution date

Account Name TermsLast Pmt Method Total AR 1-7 8-30 31-60 61-90 91+ Total Past Due Comments

UOP LLC NET30 Electronic 516,905 0 356,985 0 0 0 356,9851. Needs Certification document 2. Docs being prepared by Engineering. 3. Mr. Smith 4. July 25th

BARIVEN SA NET30 Electronic 242,303 0 6,228 7,464 150,026 78,585 242,3031. Chronic Past Due 2. Executive visit 3. Mr. Garcie 4. Meeting planned in August

SAUDI POLYMERS CO NET30 Electronic 353,219 0 112,675 0 0 0 112,6751. Goods received late 2. Docs e-mailed to customer 3. Collector 4. July 20th

VALTRONICS SALES INC NET30 Electronic 348,187 45,829 53,957 (2,735) 0 0 97,0511. Liquidated Damages, product late 2. Negotiate settlement. 3. Mr. Rep 4. not commited

BARIVEN SA ADVANCE Electronic 80,305 0 80,305 0 0 0 80,305 See #2 above

GOVERNMENT SCIENTIFIC SOURCE INC

NET30 Electronic 79,067 0 0 0 0 79,067 79,0671. Warranty Dispute 2. Need engineer to review on site 3. Mr. Jones 4. Aug. 5th

CHEROKEE MEASUREMENT AND CONTROL INC

NET30 Check 363,718 78,119 0 0 0 0 78,1191. Month end cutoff 2. Payment promised 3. Collector 4. July 10th

GENERAL ELECTRIC CO NET30 Electronic 815,649 106,360 (22,573) 5,000 (26,827) 0 61,9601. Web billing 2. Invoices submitted late 3. Collector 4. Payment promised

BERRY PETROLEUM CO NET30 61,671 0 61,671 0 0 0 61,6711. Documents required 2. Need NOA certifcicate 3. Customer Service 4. Not committed

LAURENTIDE CONTROLS LTD

NET30 Electronic 104,886 58,042 0 0 0 0 58,0421. Month end cutoff 2. Payment promised 3. Collector 4. July 10th

TECNOSTEAM ENERGY SA PANAMA

NET30 38,000 38,000 0 0 0 0 38,0001. Month end cutoff 2. Payment

promised 3. Collector 4. July 10thTotal Top 20 Past Due Accounts 3,003,910 326,351 649,248 9,729 123,199 157,652 1,266,178Grand Total 3,003,910 326,351 649,248 9,729 123,199 157,652 1,266,178Grand Total % 10.9% 21.6% 0.3% 4.1% 5.2% 42.2%

• What Executive Lead Meetings Are Held? When?

21

Institutionalize the Process Through Regular Scheduled Meetings with Key Executives

Summary….Summary…. The DSO Performance model defines those best practices

in each element of the cash cycle that enable best in class performance– Assessing business units adoption of these best practices

provides the roadmap for driving improvements

Applying the principles of Perfect Execution to the receivables effort has enabled:– Cross functional focus on receivables management

– Adoption of best practices to reduce complexity and drive process efficiency

– Collaboration across the elements of the cash cycle to improve customer service and better understand our customers

22

Thank You!Thank You!Questions?