Positive pay edi process in sap
5 likes•2,718 views
Positive Pay is a fraud prevention service where a company provides its bank with a list of issued checks. The bank then matches checks presented for payment against this list, and only pays checks that are on the list. The document discusses how to implement Positive Pay through SAP by generating identification documents containing check information and transmitting them to the bank via an EDI subsystem. Segments in the identification documents contain data like check number, amount, and payee.
Positive pay edi process in sap
- 1. Positive Pay EDI Process in SAP Applies to: Enterprise Resource Planning. For more information, visit the Enterprise Resource Planning homepage. Summary Positive Pay is an anti-fraud service offered by virtually every US commercial bank. It protects companies against altered checks and counterfeit check fraud. Author: Chandra Sekhar Reddy.M Company: Intelligroup Asia Pvt. Ltd., Created on: 19th July 2009 Author Bio Chandra Sekhar Marappareddy is an M.B.A (Finance) from Madras University having over Ten years of varied experience in the field of Finance and Accounts before entering into SAP. Presently working as Consultant - FICO, with Intelligroup and has been part of SAP FICO competency since March 2006. SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 1
- 2. Positive Pay EDI Process in SAP Table of Content Business Requirement: - ....................................................................................................................................3 Solution:- .........................................................................................................................................................3 Steps:...........................................................................................................................................................................3 Conclusion Notes:- .............................................................................................................................................6 Copyright ........................................................................................................... Error! Bookmark not defined. SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 2
- 3. Positive Pay EDI Process in SAP Business Requirement: - To protect business against fraudulent checks. Here's how the Positive Pay works: ABC Company issues approximately 600 checks each Friday. After the checks are cut, ABC Company transmits to their bank, a list of the checks that they issued (check number and dollar amount). This list is imported into Bank's computer. Later, when the checks are presented to Bank for payment, Bank matches each check presented against ABC's previously transmitted lists. If the presented checks' numbers and amounts appear on a previously submitted list, the check is sent through for payment. If both items do not match, the check is not cleared. This article discusses about the procedure in SAP for the implementation of “Pay Positive Pay (PPP)” by EDI (Idocs) for the purpose of Match Pay transmission to EDI sub system and from there to the Partner Bank (Bank of America) in this example. Solution:- Steps: 1) The information to be passed to the Partner(Bank) is decided(like Check Amount, Check Number, Payee Name and Payment Date etc.,) 2) The above information is populated into Idoc segments using a simple Customized abap program. 3) The Idoc segments are mapped to EDI system with the help of EDI team. 4) Partner (Bank) profile for “Inbound” and “Outbound” parameters is defined(Tcode: WE20) 5) Defining Port(Tcode WE21) 6) Maintain link between Idoc type(FIPARQ01) and Message type(FIPAYM) Tcode:WE82 7) A daily job is scheduled to generate and trigger Idocs out of SAP to EDI subsystem from where the check information is sent to the Bank. When an EDI transaction is executed (from SAP to EDI subsystem), the translation software (of EDI subsystem, for E.g. Web Methods) will transform the data into the format defined by the ANSI X.12 standard and transmit this information to an EDI VAN. The EDI VAN is an EDI service provider that transmits messages to their destinations. Destinations are identified by an EDI address that points to an EDI mailbox. The mailboxes store transactions for a subscriber until the translation software connects to the EDI VAN and downloads EDI transactions from their mailboxes. When a transaction is downloaded, the EDI VAN will send a "functional acknowledgment" message to the sender (EDI sub system), and the same is re-transmitted into SAP by the sub system, in order to let the sender (Client) know that the recipient (Bank) has received the PP transmission. The translation software will send any outward-bound EDI transactions to trading partners during the time when the translation software is connected to the EDI network. Sample of SAP Idoc segment: SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 3
- 4. Positive Pay EDI Process in SAP Segment information for PP Outbound Idocs created:- Check issued Idoc contains following Control record information: Basic type FIPARQ01 Message type FIPAYM Message code CHK Partner number NATBK Check voided / canceled Idoc contains following Control record information: Basic type FIPARQ01 Message type FIPAYM Message code CNC Partner number NATBK The Data records for both Message code CHK and CNC are the same, the following is a listing of the segments populated and a brief mapping detail where necessary: Segment type E1FIPRR (FI Idoc: References for payment) Number 2 No. higher segment 0 Hierarchy level 2 GJAHR Fiscal year – This denotes the fiscal year of payment BUZEI Line item number within the accounting document DMBTR Amount in local currency – Represents the check amount in USD Segment type E1FIPRH (FI Idoc: Header data for payment) Number 1 No. higher segment 0 Hierarchy level 1 PYDOC Payment document – This denotes the check number in SAP ZALDT Posting date of the payment document – Same in SAP KONTO Account – Represents the Bank of America Account number on which the above check is drawn Segment type E1FIPRB (FI Idoc: Bank data for payment) Number 3 No. higher segment 0 Hierarchy level 2 BANKK Bank key – This is a constant value “002” for all Idocs Segment type E1FIPRB (FI Idoc: Bank data for payment) SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 4
- 5. Positive Pay EDI Process in SAP Number 4 No. higher segment 0 Hierarchy level 2 BANKK Bank key – This is a constant value “003” for all Idocs Segment type E1FIPRG (FI Idoc: G/L data for payment) Number 5 No. higher segment 0 Hierarchy level 1 HKONT General ledger account – This is a constant value “004” for all Idocs Segment type E1FIPRP FI Idoc: Partner data for payment Number 6 No. higher segment 0 Hierarchy level 2 GPART_TYP Business partner role – “N” denotes a valid payment and “V” denotes a voided check NAME1 Name 1 – Name of the payee as in SAP Sample of Positive Pay Idoc file transmitted to EDI subsystem:- SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 5
- 6. Positive Pay EDI Process in SAP Conclusion Notes:- Though Positive Pay information can be transmitted to Bank through other processes like FTP, EDI(Idocs) process is more sophisticated and secure than others. SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 6
- 7. Positive Pay EDI Process in SAP Related Content For more information, visit the Enterprise Resource Planning homepage SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 7
- 8. Positive Pay EDI Process in SAP SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 8 Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.