Unit 5 - 22759: Accounting and ERP (B. Wieder) 22/03/2010...

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: 22759: Accounting and ERP (B. Wieder) 22/03/2010 Chapter 7.3: ISSUES IN AR: MASTER DATA MGT & ADVANCED PROCESSES © Bernhard Wieder (occ. Ref. to SAP-AG) 2010 - 133 Master Record Views: Customers Company Code Credit Control Area Credit Data Accounting (Company Code) Data Client General Data Sales and Dist. Data Sales Area © Bernhard Wieder (occ. Ref. to SAP-AG) 2010 - 134 1 22759: Accounting and ERP (B. Wieder) 22/03/2010 Customer Invoices FI-AR: T-CODE FB70 Almost identical with Vendor Invoice, but: identical with Vendor Invoice but: Tax Code S1, S0 GL-item = Revenue (e.g. 800000 domestic revenue) In reality: Rarely used, as – ideally – invoices are produced in SD module and automatically passed on to accounting SD-Billing: Automatic billing of (completed) deliveries based on specifications in sales order. See chapter 9. © Bernhard Wieder (occ. Ref. to SAP-AG) 2010 - 135 Customer Payments Type of Payment Receipt: Handling in SAP ECC: Down payment Enter as down payment (request) (F-29 or F-37) Cash sale Cash Journal (FBCJ) Cash for OI Cash Journal (FBCJ) Cash for OI Clear manually with posting (F-32) Cheque for cash sale Cash Journal (FBCJ) clear manually/automatically Cheque for cash sale Check deposit in Bank Accounting (FF68 etc.) Cheque for OI Check deposit in Bank Accounting (FF68 etc.) Cheque for OI Clear manually with posting (directly into GL account) (F-32) Receipt by bank transfer (no PA) Manual account statement (FF67 etc.) Receipt by bank transfer (no PA) Electronic account statement (FF_5 etc.) Receipt by bank transfer (with prior PA) Enter as payment advice (FBE1) Receipt bank transf. (with prior PA) Enter manually as incoming payment and clear (F-28) Postprocess (Clear) Reconciliation with clearing Reconciliation with clearing Reference in sub-sequent posting © Bernhard Wieder (occ. Ref. to SAP-AG) 2010 - 136 2 22759: Accounting and ERP (B. Wieder) 22/03/2010 Comments on Payments (Customers and Vendors) 2 types of clearing: ‘Post with clearing’: Posting and clearing are one process Account clearing: Existing transactions are matched (and automatic line items are posted, e.g. cash discount) Processing types: Manual Automatic Example 1: Cash Journal Does not clear open items not clear open items Requires manual or automatic account clearing Example 2: Bank Reconciliation (see section 7.1) Posts and clears/tries to clear automatically; Might require ‘post-processing’ if OI and payments do not match © Bernhard Wieder (occ. Ref. to SAP-AG) 2010 - 137 Processing payment differences Within defined Within defined tolerances Automatic cash discount adjustment Automatic posting of unauthorized deductions Manual cash discount adjustment Outside of of Tolerances Partial payment Clear difference manually Residual items Payment on account © Bernhard Wieder (occ. Ref. to SAP-AG) 2010 - 138 3 22759: Accounting and ERP (B. Wieder) 22/03/2010 ‘Dunning’: Payment Reminders in SAP ERP Background: It is commercial reality in every country that some customers do not pay in time or never pay; losses from bad debts are quite substantial in many economies. Failure to pay in time can be a customer decision, customer negligence or often has other reasons, such as communication errors, delays in payment transmission, etc. Therefore, good customer and cash management requires a very balanced approach, i.e. friendly reminders at stage 1/for customers with otherwise good payment behaviour, but more direct and firm communication for other cases. In SAP ERP: SAP ERP: The reminder strategies can be almost completely automated, based on finetuned configuration settings (incl. predefined correspondence forms). Technically, the dunning program (F150) selects the overdue open items, determines the dunning level of the account in question, and creates a dunning notice. It then saves the dunning data determined for the items and accounts affected. © Bernhard Wieder (occ. Ref. to SAP-AG) 2010 - 139 SAP Settings/Procedures for Dunning “Dunning Procedures” setup in the IMG, and entered into the correspondence section of customer master record. The Dunning Run (F150) is a background process, which Dunning Run (F150) is background process which may be executed daily, weekly or even monthly. The Dunning Process involves 3 steps: Enter the dunning parameters and execute the dunning proposal run. The system will suggest action based on the settings, open items, etc. But this ‘dunning proposal list’ can still be overruled by changed settings and new dunning runs. settings and new dunning runs. Only once the dunning results are printed, all the documents and customer master records are updated (to potentially new dunning levels). © Bernhard Wieder (occ. Ref. to SAP-AG) 2010 - 140 4 ...
View Full Document

Ask a homework question - tutors are online