PSB is the data table for the Pairing Supplier Buyer data.
| Name | Description | Data Type | Len | Dec. | View lines | View type | Inst. | Visible | Codetable |
|---|---|---|---|---|---|---|---|---|---|
| INR | Internal Unique ID of Pairing Supplier Buyer | Text | 8 | 1 | Edit | Yes | Public | ||
| EXTKEY | Key of Pairing Supplier Buyer | Text | 24 | 1 | Edit | Yes | Public | ||
| NAM | Name of Pairing Supplier Buyer | Text | 40 | 1 | Edit | Yes | Public | ||
| BUYPTYINR | Internal Unique ID Buyer | Text | 8 | 1 | Edit | Yes | Public | ||
| SUPPTYINR | Internal Unique ID of Supplier | Text | 8 | 1 | Edit | Yes | Public | ||
| MINCUR | Currency | Text | 3 | 1 | Edit | Yes | Public | CURTXT | |
| MINAMT | Minimum Amount | Numeric | 18 | 3 | Edit | Yes | Public | ||
| OFFPER | Offer Period | Numeric | 2 | 0 | Edit | Yes | Public | ||
| BILMAXPRC | Percent per Bill | Numeric | 5 | 2 | Edit | Yes | Public | ||
| DISPRC | Dispute % threshold | Numeric | 5 | 2 | Edit | Yes | Public | ||
| MAXPER | Maximum Period | Numeric | 3 | 0 | Edit | Yes | Public | ||
| FEECOD | Fee Code | Text | 6 | 1 | Edit | Yes | Public | FEETXT | |
| OFFERFLG | Offer Flag | Text | 1 | 1 | Edit | Yes | Public | ||
| GRCPER | Grace Period for Due Date | Numeric | 2 | 0 | Edit | Yes | Public | ||
| MINPER | Minimum Period | Numeric | 3 | 0 | Edit | Yes | Public | ||
| VER | Version Counter | Text | 4 | 1 | Edit | Yes | Public | ||
| PFPINR | INR of related finance programm | Text | 8 | 1 | Edit | Yes | Public | ||
| RFDDISPRZ | Dispute % threshold | Numeric | 5 | 2 | Edit | Yes | Public | ||
| SUPBUYID | Supplier's Buyer ID | Text | 40 | 1 | Edit | Yes | Public | ||
| RFTOPNOFF | Financing Diary Offset | Numeric | 3 | 0 | Edit | Yes | Public | ||
| RRTPOPFLG | Generate Payment Advice Note | Text | 1 | 1 | Edit | Yes | Public | ||
| RRTPOPOFF | Payment Advice Note offset | Numeric | 3 | 0 | Edit | Yes | Public | ||
| RRTRPYOFF | Due Date offset | Numeric | 3 | 0 | Edit | Yes | Public | ||
| BOESHWPFX | Bill of Exchange Prefix to show | Text | 10 | 1 | Edit | Yes | Public | ||
| CREFRM | Select Target Transaction for Automatic Processing | Text | 6 | 1 | Edit | Yes | Public | ATPTXT | |
| TYP | Type of Repetition | Text | 1 | 1 | 20 | Edit | Yes | Public | Embedded |
| WDY | Day of the Week | Text | 1 | 1 | 20 | Edit | Yes | Public | Embedded |
| MDY | Day of the Month | Text | 2 | 1 | 40 | Edit | Yes | Public | Embedded |
| CAL | Calendar | Text | 10 | 1 | Edit | Yes | Public | ||
| ETGEXTKEY | Entity Group of Party | Text | 8 | 1 | Edit | Yes | Public | ||
| MAXAGEFND | Maxi Invoice Age at Funding date | Numeric | 3 | 0 | Edit | Yes | Public | ||
| MAXAGESETL | Max Invoice age at Settlement date | Numeric | 3 | 0 | Edit | Yes | Public | ||
| DAYSADV | Advice Note Days Offset | Numeric | 3 | 0 | Edit | Yes | Public | ||
| GENPRMFLG | Generate Promissory Note Flag | Text | 1 | 1 | Edit | Yes | Public | ||
| GENFNRFLG | Generate Funding Request Flag | Text | 1 | 1 | Edit | Yes | Public | ||
| GENADVFLG | Generate Payment Remainder Diary | Text | 1 | 1 | Edit | Yes | Public | ||
| AGRMNTREF | Agreement Reference | Text | 30 | 1 | Edit | Yes | Public | ||
| AGRMNTDAT | Agreement Date | Date | 12 | 0 | Date | Yes | Public | ||
| PRMWITNESSCNT | No of Prom Note witness signatures needed | Text | 1 | 1 | Edit | Yes | Public | Embedded | |
| PRMSIGNTITLE | Title of Signatory | Text | 40 | 1 | Edit | Yes | Public | ||
| PRMSIGNCNT | No of Signatories for Prom Note | Text | 1 | 1 | Edit | Yes | Public | Embedded | |
| FNRSIGNCNT | No of Signatories for Funding Request | Text | 1 | 1 | Edit | Yes | Public | Embedded | |
| FNRWITNESSCNT | No of Funding Request Witness signatures | Text | 1 | 1 | Edit | Yes | Public | Embedded | |
| FNRFMT | Funding Request Format | Text | 4 | 1 | Edit | Yes | Public | Embedded | |
| FNRSIGNTITLE | Title of Signatory | Text | 40 | 1 | Edit | Yes | Public | ||
| GENBOEFLG | Generate Bill of Exchange Flag | Text | 1 | 1 | Edit | Yes | Public | ||
| BOEFMT | Bill Of Exchange Format | Text | 4 | 1 | Edit | Yes | Public | Embedded | |
| BOEPREFIX | Prefix for Counter | Text | 8 | 1 | Edit | Yes | Public | ||
| SYNALWFLG | Syndication Allowed | Text | 1 | 1 | Edit | Yes | Public | ||
| GENBOEOFFFLG | Bill of Exchange Offer | Text | 1 | 1 | Edit | Yes | Public | ||
| BOEKEY | BoE Offer Text block key | Text | 16 | 1 | Edit | Yes | Public | ||
| GENIRRMFLG | Irrevocable Instruction | Text | 1 | 1 | Edit | Yes | Public | ||
| IRRKEY | Irrevocable Instruction Text block key | Text | 16 | 1 | Edit | Yes | Public | ||
| ASDFLG | Assets to be sold flag | Text | 1 | 1 | Edit | Yes | Public | ||
| AUTREPDAYS | Auto repayment days | Numeric | 3 | 0 | Edit | Yes | Public | ||
| AUTREPFLG | Auto repayment flag | Text | 1 | 1 | Edit | Yes | Public | ||
| BUYSUPID | Buyer's Supplier Id | Text | 40 | 1 | Edit | Yes | Public | ||
| CHATO | Own Charges Born By | Text | 3 | 1 | Edit | Yes | Public | Embedded | |
| GETFLDNRM | Field holding the normalized search fields | Text | 50 | 1 | 20 | Edit | Yes | Public |
| Name | Fields | Properties |
|---|---|---|
| PSB_BUYIDX | BUYPTYINR | |
| PSB_INR | INR | Unique |
| PSB_PFPINR | BUYPTYINR, PFPINR | |
| PSB_SUPIDX | SUPPTYINR |
/
INR
Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter PSB. The field INR is used to maintain links from other tables into this table.
Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter of this table. The field INR is used to enable links from other tables to this table.
For contractdata the INR also links the two tables xxD and xxT as associated entries hold the same INR.
This field holds the external key to identify a Pairing Supplier Buyer.
This is the visible name of a Pairing Supplier Buyer. This name is used in selection list and on panels to identify a Pairing Supplier Buyer.
Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter PSB. The field INR is used to maintain links from other tables into this table.
Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter PSB. The field INR is used to maintain links from other tables into this table.
The currency of the amount, below which the finance amount should not be provided.
The amount below which the finance amount should not be provided.
The amount below which the finance amount should not be provided. The amount below which the finance amount should not be provided.
The number of days the offer is valid.
Maximum percentage of the net invoice value for which finance could be offered.
Dispute % threshold: Whether a contract with disputed items counts as past due. If dispute amount as a % of total Funded amount exceeds threshold, then do not show on flip chart when over due. Thus in short words “bigger disputes are not past due”.
The period above which, finance should not be provided. I.e. the finance period should always be less than the days given here.
Code to identify the fee.
This field will be used by the grouping manager in order to create an offer or a direct finance.
Checking this flag enables funding to be done only with an offer.
A number of calendar days before or after the loan due date. The content in this field will be used by the grouping manager to include invoices with different due dates.
The period below which finance should not be provided. I.e. the finance period should always be greater than the days given here.
This field holds the version counter to keep track of the version history of a PSB entry. The individual versions are controlled by entries in the SLG table.
This field holds the version counter used to keep track of the history of an entry of this table. The individual versions are managed by entries in the SLG table.
Unique internal ID of Finance program. Note, this is currently not in use.
Determines whether Contract shows as Overdue. If amount in Dispute is below this % then Contract WILL show as overdue afyer due date
ID number used by the Supplier's own systems for this Buyer.
This field creates a financing Diary x days after offer creation (trn RFTPOP).
Whether to Generate a Payment Advice note to this buyer , informing of them of imminent repayment due. Note will be sent (Payment Advice Note Offset days) days after Batch creation date.
Days from Batch Creation Date. Used to Default Payment Advice Diary date.
Days from Batch Creation Date. Used to Default Due date
allows for a longer prefix than the 8 characters held on the dbcounter table
To allow a shorter counter reference on documents , a prefix value to be shown can be set here
Max Invoice age (days) at Funding date.
Date is measured from Invoice date to Contract Open Date Or , Offer: Intended funding date
The difference between the funding date and the invoice date should not be greater than these given days.
Max Invoice age (days) at Settlement date.
Date is measured from Invoice date to Contract Due Date (not Invoice due date)
The difference between the repayment date and the invoice date should not be greater than these given days.
Offset in days before Due date .
On the relevant date , 'n' days before Contract Due date , a Payment Advice Document should be generated and sent to the Buyer, advising them of the approaching Due date, and the amount due.
A Payment Reminder diary is created from the APF Funding transaction, with date of diary being calculated as Invoice due date minus number of working days provided here.
Switch to determine whether to generate the Promissory Note
On setting this checkbox, a correspondence for 'Promissory Note' is generated in APF Offer (IATPOP) transaction and is sent to the Buyer.
Switch to determine whether to generate the Funding Request
On setting this checkbox, a correspondence for 'Funding Request' is generated in APF Offer (IATPOP) transaction and is sent to the Buyer.
Switch to determine whether to generate the Payment Advice
Enables generation of payment advice
This is the external reference for the agreement between our Customer and Us. It may be quoted on documents.
The reference of the agreement between buyer and supplier.
This is the date that we signed the agreement between our Customer and Us. It may be quoted on documents
The date of the agreement.
Some programs require a Witness signature, some require 2 , and some, none at all. Set this value to control how many appear on the Document.
This field defines the number of witness required in the 'Promissory Note' letter generated in the APF Offer (IATPOP) Transaction. Based on the input provided here, the letter is created with the number of assigned spaces for witness signature.
| Code | Text |
|---|---|
| None | |
| 1 | One |
| 2 | Two |
Who is to Sign the Prom Note Could be : Director, Attorney, Authorised Signatory
The input provided here is used to print the title of the signature in the 'Promissory Note' letter generated in APF Offer transaction.
How many signatures required on the Document. This will control generation of Signatory blocks in the Documents
This field defines the number of signatures required in the 'Promissory Note' letter generated in the APF Offer (IATPOP) transaction. Based on the input provided here, the letter is created with number of assigned spaces for signature.
| Code | Text |
|---|---|
| None | |
| 1 | One |
| 2 | Two |
| Code | Text |
|---|---|
| EMEA | EMEA |
| US | US |
This field defines the number of signatures required in the 'Funding Request' letter generated in the APF Offer (IATPOP) Transaction. Based on the input provided here, the letter is created with number of assigned spaces for signature.
| Code | Text |
|---|---|
| None | |
| 1 | One |
| 2 | Two |
Prom Notes fall into 2 distinct format groups , with different formatting applied to each: EMEA or US
This field defines the number of witness required in the 'Funding Request' letter generated in the APF Offer (IATPOP) Transaction. Based on the input provided here, the letter is created with the number of assigned spaces for witness signature.
| Code | Text |
|---|---|
| None | |
| 1 | One |
| 2 | Two |
Who is to Sign the Funding Request Could be : Director, Attorney, Authorised Signatory
The input provided here is used to print the title of the signature in the 'Funding Request' letter generated in APF Offer transaction.
On setting this checkbox, a correspondence for 'Bill of Exchange' is generated in APF Offer (IATPOP) transaction and is sent to the Buyer.
| Code | Text |
|---|---|
| EMEA | EMEA |
| US | US |
To allow different Pairings to generate their own numbering , set the Counter Key here.
Id number used by the Buyer's own systems for the Supplier.
Default fee payer
Fees to be borne by this party.
| Code | Text |
|---|---|
| BUY | Buyer |
| SUP | Supplier |
| Defaulted by FEE-condition |
Checking the flag enables automatic generation of the repayment transaction IATSET.
The number of days before which auto repayment should be processed.
Asset Distribution Engine flag
When enabled:
Information about fundable/funded invoices of buyers can be generated and sent to other external applications via an interface.
Information about fundable/funded invoices of buyers can be generated and sent to other external applications via an interface.
In APF, the buyer is financed for the approved invoices and based on his upfront approval to pay those invoices on the due date, the supplier receives the discounted amount upfront. Banks can also offer these invoices for sale to investors/ refinancing institutions to reduce their risk exposure. The offer to sell can be for the full portion or for a partial amount. For this offer to sell, information of the funded invoice details needs to be sent in a single file/ message. This can be processed by setting this checkbox. Pre-requisites for generating this file are:
a) For the pairing setup, the checkbox has to be selected. b) An APF Offer (IATPOP) contract has to be created through an incoming xml message imported from the incoming message manager (SWITSK). When an APF Finance (IATOPN) is processed for that offer contract, it enables the service 'SRVASD' and 'SRVRSF' in the Task Manager (MGRTSK). Once both services are successfully run, a JSON file is created with below mentioned details of the contract.
* Own Reference - APF Contract reference * Document Type - e.g. 'Invoice', 'Debit Note' or 'Credit Note' * Document Number - The number of the document (ex: Invoice number) * Document Funding Type - Whether it is funded or not * Document Status - That it is in approved status * Document Base Rate Type - Reference rate / Base rate * Document Base Rate Value - The interest rate for the contract * Document Margin - Margin added to the interest
Field holding the concatenated and normalized sum of all search fields used by quick search. This is one of the fields set in a SdbSetNRMFields method defined in the table definition module.
Field holding the concatenated and normalized sum of all search fields used by quick search. This is one of the fields set in a SdbSetNRMFields method defined in the table definition module.
Switch to determine whether to enable the Participation
Bill of Exchange Offer flag. Please note, this is not in use
Bill of Exchange Offer Text block key. Please note, this is not in use.
Irrevocable Instruction flag. Please note, this is not in use
Irrevocable Instruction Text block key. Please note, this is not in use.
Select Target Transaction for Automatic Processing: it can be either RFTPOP or RFTOPN
This field describes the type of automatic repetition (e.g. daily, weekly, monthly). See embedded codetable for details.
| Code | Text |
|---|---|
| * | every working day |
| + | every day |
| W | every week |
| M | every month |
For 'weekly' repetition only: Day of the week when job is to be executed.
| Code | Text |
|---|---|
| < | first working day |
| > | last working day |
| 2 | Monday |
| 3 | Tuesday |
| 4 | Wednesday |
| 5 | Thursday |
| 6 | Friday |
| 7 | Saturday |
| 1 | Sunday |
For 'monthly' repetition only: Day of the month when SPTCRE is to be executed.
| Code | Text |
|---|---|
| < | first working day |
| > | last working day |
| 1 | first |
| 2 | second |
| 3 | third |
| 4 | forth |
| 5 | fifth |
| 6 | sixth |
| 7 | seventh |
| 8 | eighth |
| 9 | ninth |
| 10 | tenth |
| 11 | eleventh |
| 12 | twelfth |
| 13 | thirteenth |
| 14 | fourteenth |
| 15 | fifteenth |
| 16 | sixteenth |
| 17 | seventeenth |
| 18 | eighteenth |
| 19 | nineteenth |
| 20 | twentieth |
| 21 | twentyfirst |
| 22 | twentysecond |
| 23 | twentythird |
| 24 | twentyfourth |
| 25 | twentyfifth |
| 26 | twentysixth |
| 27 | twentyseventh |
| 28 | twentyeighth |
| 29 | twentyninth |
| 30 | thirtieth |
| 31 | thirtyfirst |
| L | last |
Calendar to be used for calculation of working day for SPTCRE execution.
This table is defined on entity group level with separate entries for each entity group. This field holds the EXTKEY of the entity group which is the logical owner of this entry. This field is filled automatically during insert and is used as filter when accessing the database. Without special implementation only entries of the entity group of the currently active entity are visible to the user.
This field holds the external key of the owning entity group to identify the logical owner of this entry. This field is filled automatically during insert and is used as filter when accessing the database. Without special implementation only entries of the currently active entity group are visible to the user.