Transaction DBIPFP
This transaction is used to maintain programs that will be used in connection with Approved Payable Finance .

The following transactions can be started from here by clicking the icons in the list below for:

Adding Program
Modifying Program
Deleting Program
printing Pairing Setup.
creating Program List
showing Version Log of the modifications to the Program Setup.

Program
A Program is an agreement between the bank and the buyer where the terms and conditions are agreed upon and then the bank pays the supplier on behalf of the buyer.

The buyer enters into an agreement with the bank and then invites its suppliers to join the program. The supplier then onboards to the Supply Chain Finance program with the bank, when the terms and conditions are agreed upon. Once the onboarding process is done and when the program is activated, the supplier can then request for discounting of the approved invoices from the buyer.

In most cases, these programs are Auto discounting, meaning the discount happens as soon as the invoices are uploaded. In some cases, the programs are Manual discounting, meaning the invoices are stored in the system until the supplier manually selects them for discounting.

When the supplier requests for discounting, the bank pays the discounted amount to the supplier immediately and the buyer then pays back the discount amount to the bank on maturity date.

In DOKA, we use the program as a superset of settings and validations for how the Invoices are handled within a Pairing. The values set for a Pairing apply to the Buyer, but can be overridden for a particular Buyer/Supplier Pairing. 

Values able to be configured are: 
Discounting option:  Auto or Manual.  If Auto, then all invoices added to the front end will be sent through to DOKA automatically to be processed. If manual, the supplier must select and request. 

Maximum Finance %:  The percentage of each Invoice that will be financed up front.  If less than 100% the remainder is passed on to the supplier when the Buyer pays. 
Min Payment term; used for grouping*. Invoices with term greater than this will be eligible for grouping.  
Max Payment term; used for grouping. Invoices with term less than than this will be eligible for grouping.
Minimum Amount; used for grouping.  Invoices with value greater than this will be eligible for grouping.

Maximum Invoice age at Funding Date; Will flag as an error if the Invoice date is > X days ago on the day we make the funding (usually today) 
Maximum Invoice age at Repayment Date; Will flag as an error if the Invoice date is > X days ago on the day it is Due to be repaid (usually the Invoice due date)  

Fee payer; who pays ? Buyer or Supplier. Will feed in to the settlement tab in DOKA. 

Auto repayment flag; Will the repayment transaction (e.g. IATSET) be diarised and processed STP ?
Auto repayment days; an offset to cater for processing time. Is the days before due date that the auto repayment should start, so that it finishes on the correct date.  Usually 0, 1 or 2. 

Generate Payment Reminder Diary:  If ticked, a reminder to the buyer will be sent as a message.  
Payment Reminder Notice days: how many days before Due date the reminder should be sent.

Assets sold. For info only. Flags that this program can be part of a Fund-and-Sell redistribution  to third parties. 

*Grouping is used when we have invoices uploaded that are not part of a ready made funding request.  
We can look in the pool of Invoices and group them by Buyer/ Supplier/ Currency then create a Funding transaction based on those. One use case would be to send an Offer to the supplier ; "would you like these financed?" If yes then it proceeds.  
With ready made requests coming from the front end, this grouping need not be used.

Status Handling:

Pending: when the user is still preparing the data
Waiting: when the entry is signed by the maker and is waiting to be released.
Active: when the entry is released and the data is sent to external front end system such as RIVO.

Process
When starting the transaction, the “Search Panel” is displayed. The buyer and/or program number can be entered or selection field can be left empty.  The programs which meets the selection criteria, or all programs (in case of empty selection field) are displayed in the selection list.

The + icon on the top menu bar will navigate the user to Adding Program where a new program can be created. Once the program is created, the user is returned to the CREPFP transaction and status of the Program is set to “Pending”.

The “Program Fee Conditions” grid displays the fee conditions associated to the program.

The user can add fees for the selected program by clicking the +- icon on the top right corner of the grid which will start the Add Condition transaction with condition set as “Program” and Program No. field is defaulted to the selected program. 

The “Program Limit” grid displays the limit associated to the program.

The user can add limits for the selected program by clicking the +- icon on the top right corner of the grid which will start the Adding a Limit transaction with Type as “Liability per Program” and Program No. field is defaulted to the selected program. 

Once all the three details, Program, Fees & Limits of the program is saved, the user can sign the process mentioning all relevant information is now updated using tick icon. This sets the status of the Program to “Waiting” and is now available for a checker to release the program details.

A different user must then login and use the same icon to check and release the transaction. Upon release, it will generate and send the message to the external connected interface such as RIVO. The sent documents will be listed in panel Fees & Limit, under the “Send Requests of Program” grid. The “Send Requests of Program” displays the sent requests of the program including details like the Medium, External Key, Document name, creation date and the releaser. Clicking the view Icon will display the XML file.

An additional functionality of the transaction includes the scenario where an individual entry such of a program, fee or limit is waiting for a 4-eye static data release, a label stating that the entry is waiting to be released will be visible to the user.