Upload
jabar-ali
View
567
Download
6
Embed Size (px)
DESCRIPTION
.
Citation preview
PAYMENT PROCESSING REQUEST FUNCTIONALITY-
In 11i we used Payment batches to pay for multiple invoices same time. In
R12, PPR is the replacement of Payment batches. R12 PPR process enables
payment Administrator to select multiple invoices for payment by selection
criteria and he can pause the invoice selection and payment build process.
During the invoice selection review, payment manager can review the
invoice selected; if the invoices were validated or approved and hence did
not get included in the payment process request. He can add or remove the
invoices in the Payment process and also can check the cash requirements
for the full payment. Payment manager can also dismiss the individual
documents or payments if necessary, and restart the payment build process.
Steps in Pay run Process-
Managing a Pay run involves 3 main processes
Selection of the invoices for payment
Grouping the invoices into payments
Building the payment instruction files to either print checks or send
instructions to bank.
There are four steps in the processing of PPR:-
Document selection – Handled by Payables(AP)
Build Payments – Handled by Payments(IBY)
Format Payments – Handled by Payments(IBY)
Confirm Payments – Handled by Payables(AP)
Submitting a Single Payment Process Request
Mandatory fields – Payment Process Request name, pay through date,
Payment date, and Exchange rate type.
Under Processing tab, options are available to stop the process after
document selection/payment and also how to create the payment
instructions:
1. Maximize Credits.
2. Stop Process for review after scheduled payment selection.
3. Calculate payment withholding and interest during scheduled payment
selection.
4. Stop process for review after creation of proposed payments.
Click on submit to submit the Payment process request.
Document Selection – Payables
This process calls AP_AUTOSELECT_PKG.
When a payment process request is submitted, a record is inserted in
AP_INV_SELECTION_CRITERIA_ALL with a checkrun_name i.e payment
process request name. Invoices are then selected based on the due date,
discount date, paygroup, and other criteria provided by the user while
submitting the PPR.
The AP_SELECTED_INVOICES_ALL table is populated with the selected
invoices and AP_UNSELECTED_INVOICES_ALL table by the unselected
invoices.
Note: After selecting the documents, the invoices are locked to prevent
other check runs from selecting the same invoices.
If the PPR has been setup to ‘Stop Process for Review after Scheduled
Payment Selection’, the process stops for user review.
Then the status of the PPR is set to Invoices Pending Review.
If the ‘Stop Process for Review after Scheduled Payment Selection’
was not enabled, at the end of invoice selection, build program is submitted
automatically.
If no invoices met the selection criteria and no payment schedules selected
for payment, the PPR is cancelled automatically and the status of the PPR is
set to “Cancelled – No Invoices Selected”. Then void all invoices
For others, the actions available are
a) Terminate the PPR
b) Modify / proceed to submit the PPR and start the build process.
Build Payments – Payments
Call IBY_DISBURSE_SUBMIT_PUB_PKG
Build payment creates records in IBY_PAY_SERVICE_REQUESTS with
call_app_pay_service_req_code = checkrun_name.
A payment process request is a group of documents payable that a source
product submits to Oracle Payments for payment service processing. This
table contains the parameters like Calling application identifier, Internal
bank account, Allow zero payments flag, etc. selected in the Payment
Process Request.
PAYMENT_SERVICE_REQUEST_ID NUMBER
System generated
primary key
CALLING_APP_ID NUMBER
Source product
Identifier
CALL_APP_PAY_SERVICE_REQ_CODE
VARCHAR
2
Source product’s
payment process
request Identifier. Since
the source product’s
Identifiers may be
alphanumeric, even
numeric document
Identifiers are stored as
VARCHAR2.
PAYMENT_SERVICE_REQUEST_STAT
US
VARCHAR
2
Payment process
request status. Values
from the lookup
IBY_REQUEST_STATUS
ES include
PAYMENTS_CREATED.
PROCESS_TYPE VARCHAR
2
Specifies the process by
which documents
payable are built into
payments and payments
into payment
instructions. Values
from the lookup
IBY_PROCESS_TYPES
include STANDARD,
IMMEDIATE, and
MANUAL.
ALLOW_ZERO_PAYMENTS_FLAG
VARCHAR
2
Y or N flag that indicates
whether zero payments
are allowed for this
payment request. If set
to N, any zero value
payments created for
this payment request is
failed.
INTERNAL_BANK_ACCOUNT_ID NUMBER
Internal bank account
identifier
MAXIMUM_PAYMENT_AMOUNT NUMBER
Maximum payment
amount used to override
default maximum
payment amount
MINIMUM_PAYMENT_AMOUNT NUMBER
Minimum payment
amount used to override
default minimum
payment amount
Note: The displayed status of the PPR is generated by ibyvutlb.pls
Following are the possible values of
PAYMENT_SERVICE_REQUEST_STATUS column-
DOCUMENTS_VALIDATED
INFORMATION_REQUIRED
INSERTED
PAYMENTS_CREATED
PENDING_REVIEW
TERMINATED
VALIDATION_FAILED
COMPLETED
In 11i AP_SELECTED_INVOICE_CHECKS_ALL table is populated by
the Build Payment process.
The Build Program also populates IBY_DOCS_PAYABLE_ALL table
IBY_DOCS_PAYABLE_ALL- This table contains the documents payable
which are updated by system while processing “Build Payments” program.
A document payable is a supplier invoice or similar document that needs to
be paid. In addition, this table contains whatever document information is
necessary for payment processing.
This table contains transaction details, document details, payer, payee, etc.”
Name Datatype Comments
PAY_PROC_TRXN_TYPE_CODE
VARCHAR
2
Type of payment processing
transaction or document
CALLING_APP_ID NUMBER Calling product Identifier
CALLING_APP_DOC_REF_NUMB
ER
VARCHAR
2
Reference number entered by
user of the source product.
Need not be unique
DOCUMENT_PAYABLE_ID NUMBER
Oracle Payments’ unique
internal document payable
Identifier
PAYMENT_FUNCTION
VARCHAR
2
Function or purpose of the
payment. Values from the
lookup
IBY_PAYMENT_FUNCTIONS
include SUPPLIER_PAYMENT,
CUSTOMER_REFUNDS, and
others.
PAYMENT_DATE DATE Payment date
DOCUMENT_DATE DATE Date of document
DOCUMENT_TYPE VARCHAR
2
Type of document payable.
Values from the
IBY_DOCUMENT_TYPES
lookup include INVOICE.
DOCUMENT_STATUS
VARCHAR
2
Document status. Values from
the lookup
IBY_DOCS_PAYABLE_STATUS
ES include PAYMENT
CREATED.
DOCUMENT_CURRENCY_CODE
VARCHAR
2 Document currency code
DOCUMENT_AMOUNT NUMBER
Total amount in document
currency
PAYMENT_CURRENCY_CODE
VARCHAR
2 Payment currency code
PAYMENT_AMOUNT NUMBER
Amount to be paid in payment
currency
PAYMENT_SERVICE_REQUEST_I
D NUMBER
Identifier of the payment
process request in which this
document was submitted
PAYMENT_METHOD_CODE
VARCHAR
2 Payment method Identifier
EXCLUSIVE_PAYMENT_FLAG
VARCHAR
2
Y or N flag indicating whether
this document payable should
not be grouped with any other
documents payable.
CALLING_APP_DOC_UNIQUE_RE
F1
VARCHAR
2
Source product’s first unique
document payable Identifier
CALLING_APP_DOC_UNIQUE_RE
F2
VARCHAR
2
Source product’s second
unique document payable
Identifier (Invoice_id)
CALLING_APP_DOC_UNIQUE_RE VARCHAR Source product’s third unique
F3 2
document payable
Identifier(Payment_number)
CALLING_APP_DOC_UNIQUE_RE
F4
VARCHAR
2
Source product’s fourth
unique document payable
Identifier
CALLING_APP_DOC_UNIQUE_RE
F5
VARCHAR
2
Source product’s fifth unique
document payable Identifier
A. Internal Bank Account/Payment Process Profile Assignment:
Call IBY_ASSIGN_PUB
If the payment process request has the internal bank account and payment
profile assigned to it, the same is assigned to all the documents in the
PPR.If a default internal bank account and PPP were not provided when
submitting the PPR, Oracle Payments attempts to default the values. If it
cannot find a default value for all the documents, the PPR is set to
INFORMATION REQUIRED status. The display status of the PPR is
“Information Required – Pending Action”
User should complete the missing information and Run Payment Process to
continue.
B. Document Validation
Call IBY_VALIDATIONSETS_PUB
During this step, Oracle Payments validates all the documents using
Payment Method based validations and then payment format based
validations.b.1 – If all the documents pass validation, all the documents are
set to a status of VALIDATED and the request status is set to ‘Documents
Validated’.b.2 – If there are any validation failures, Oracle Payments uses
the system option used while submitting the PPR to determine the next
action.The DOCUMENT_REJECTION_LEVEL_CODE of the PPR can have the
following values which determine how the document processing will
continue when there is a validation failureb.2.1 – REQUEST
The status of the payment process request is updated to ‘Failed Document
Validation’. Oracle Payments calls the calling application and AP releases
the rejected documents so they can be paid through another Payment
process request.
b.2.2 – DOCUMENT
Oracle Payments rejects all documents that failed validation. Oracle
Payments then calls the calling application and AP releases the rejected
documents so they can be paid through another Payment process request.
The rest of the documents are set to VALIDATED status and the ppr is set to
‘Documents Validated’ status.
b.2.3 – PAYEE
Oracle Payments rejects all documents for the supplier that had one or
more documents that failed validation. Oracle Payments calls the calling
application and AP releases the rejected documents so they can be paid
through another Payment process request. The rest of the documents are
set to VALIDATED status and the ppr is set to ‘Documents Validated’ status.
c. Create Payments
Call IBY_PAYGROUP_PUBThe validated documents are then grouped into
proposed payments based on the grouping rules, both users defined and
hard coded.
Example: If exclusive_payment_flag = Y on a document, it is paid on a
separate payment.
It then numbers the payments (internal identifier not the check numbering)
and validates the created payments.Records are inserted into
IBY_PAYMENTS_ALL that holds the payment information for the selected
documents.The build program then updates
theIBY_DOCS_PAYABLE_ALL table with the payment_id and
formatting_payment_id values that corresponding to the payment that pays
the document.
IBY_PAYMENTS_ALL
This table contains all the payments created by system while processing
“Build Payments”. A Payment can be single check or an electronic fund
transfer between first party payer and third party payee. A row in this table
corresponds to one or more documents payable. Payments are built by
grouping documents payable according to Oracle Payments’ grouping rules.
This table also stores information of payments at grouping level. The groups
can be Single, Mixed and grouped as defined in Payment Process Profile for
the purpose of SEPA.
The payment details are displayed on the Payments tab of the Funds
Disbursement Process Home page.
Name Datatype Comments
PAYMENT_ID NUMBER
Unique internal Identifier for this record.
Generated using a database sequence.
PAYMENT_METHOD_CODE
VARCHAR
2
Payment method used for making the
payments.
PAYMENT_SERVICE_REQUEST_ID NUMBER
Payment service request Id and it is the
foreign key to the table
iby_pay_service_requests.
PROCESS_TYPE
VARCHAR
2
Specifies the process by which the
payment is built into a payment
instruction. Values, from the lookup
IBY_PROCESS_TYPES, include
STANDARD, IMMEDIATE, and MANUAL.
PAYMENT_STATUS
VARCHAR
2
The status of the Payment. Values are
derived from the lookup
IBY_PAYMENT_STATUSES. The possible
values are CREATED, FORMATTED,
TRANSMITTED, VOID_BY_OVERFLOW,
REJECTED, FORMATTED, VOID, etc.
PAYMENTS_COMPLETE_FLAG
VARCHAR
2
Y or N flag that indicates if the payment is
complete
PAYMENT_FUNCTION
VARCHAR
2
Function or purpose of the payment.
Values from the lookup
IBY_PAYMENT_FUNCTIONS include
SUPPLIER_PAYMENT,
CUSTOMER_REFUNDS, and others.
PAYMENT_AMOUNT NUMBER Amount of the payment
PAYMENT_CURRENCY_CODE
VARCHAR
2 Currency of the payment
BILL_PAYABLE_FLAG
VARCHAR
2
Y or N flag indicating whether a payment is
a bill payable, that is, a future dated
payment
EXCLUSIVE_PAYMENT_FLAG
VARCHAR
2
Y or N flag indicating whether this
payment is made up of a single document
payable that was meant to be paid alone
SEPARATE_REMIT_ADVICE_REQ_FL
AG
VARCHAR
2
Y or N flag indicating whether a separate
remittance advice needs to be generated
for a payment.
INTERNAL_BANK_ACCOUNT_ID NUMBER
Internal bank account id used for making
the payment.
ORG_ID NUMBER
Unique internal identifier of the Operating
Unit. Validated against
HR_OPERATING_UNITS.ORGANIZATION_
ID.
ORG_TYPE
VARCHAR
2
Organization type. Values, from the lookup
IBY_ORGANIZATION_TYPES Include
Operating Unit, Business Group, and Legal
Entity
LEGAL_ENTITY_ID NUMBER Legal entity identifier
The PAYMENT_REJECTION_LEVEL_CODE can have the following values
which determine how the payment processing will continue when there is a
validation failure
Request – Entire PPR is rejected. Oracle Payments raises a business event
that calls AP to release the documents. The status of the payment process
request and proposed payments is updated to ‘REJECTED’.
Payment – Payments that failed validation are rejected and AP releases the
documents that belong to the payment that failed validation. The other
payments are accepted. The accepted payments get a status of ‘CREATED’.
None – Payments that failed Validation are set to ‘Failed Validation’ and
allows for user intervention. Status of the PPR is set to ‘PENDING REVIEW’
If in the PPR setup, ‘Stop Process for Review After Creation of Proposed
Payments’ is enabled, the PPR status is set to ‘Pending Proposed Payment
Review’. This status prevents further processing until user takes action. If
this option to stop for review is not enabled, the status of the PPR is set to
‘Payments Created’. In this status, payment instruction can be created for
the PPR.
Format Payments – PaymentsCall IBY_PAYINTSR_PUB, IBY_CHECKNUMBER_PUB
When a PPR is submitted, there are two options
The CREATE_PMT_INSTRUCTIONS_FLAG can be a Y or N
Y – Payment Instruction will be automatically created after payments are
created.
N – Application waits for standard request submission for Payment
Instruction.
The table IBY_PAYMENT_INSTRUCTIONS_ALL stores the payment
instruction information.
If the PPR is setup to automatically submit instruction, the
payment_service_request_id will be populated in
iby_payment_instructions_all because the instruction will be specific to the
PPR In this case, the instruction can be linked to the PPR using
PAYMENT_SERVICE_REQUEST_ID
If the PPR processing is setup for the user to submit the instruction as a
standard request, then when the instruction is submitted, then the
instruction is linked to the PPR through the payments selected by the
instruction.
The link in this case will be through
iby_payments_all.payment_instruction_id
Key Columns of IBY_PAYMENT_INSTRUCTIONS_ALL table
Payment_instruction_id
Payment_profile_id
Payment_instruction_status
Payments_complete_code
Payment_count
Print_instruction_immed_flag
Transmit_instr_immed_flag
Internal_bank_account_id
Payment_document_id
Payment_date
Payment_reason_code
Payment_currency_code
Format:
The following processing occurs during the format step.
a) Number the payments – Check Numbering
b) Create XML Extract message
c) Pass the extract to XML publisher
d) Oracle XML Publisher (BI publisher) applies the format template
e) BI publisher formats and stores the output
f) Oracle Payments then updates the status of the Payment Instruction and
the Payments. If successful, the status of Payments and Instruction is
‘Formatted’.
Print Checks:
a) Users can load stationery into the printer and print checks at this stage.
b) Determine if the checks printed ok. If not reprint
Confirm Payments – Payables
Call AP_PMT_CALLOUT_PKG
Record Print Status of the checks to confirm the payments. Oracle
Payments callsap_pmt_callout_pkg.payment_completed to confirm the
payments.
This does the following:
a) Assigns sequence/values – Document sequencing.
b) Creates data in AP_CHECKS_ALL with appropriate data from IBY tables.
Checkrun_name = ppr name and checkrun_id = checkrun_id from IBY table.
c) Data inserted into AP_INVOICE_PAYMENTS_ALL for the corresponding
checks.
d) AP_PAYMENT_SCHEDULES_ALL for the invoices are updated to indicate
the payment details and status.
e) The documents paid in this PPR are released by setting the checkrun_id
on the payment schedules to null.
f) AP_INVOICES_ALL is updated to show payment status
g) Data is deleted from the AP_SELECTED_INVOICES_ALL
h) Data is deleted from AP_UNSELECTED_INVOICES_ALL
Payment Process Request (PPR) Status and Descriptions in R12
Payment Process Request is one of the new comers in R12, which normally transitions through the
different stages of processing, the PPR will display a "Status" to let you know where in the process the
PPR has progressed to, and what's going on with it. There are more number of statuses associated with
PPR. Here in this post we tried to give most witnessed statuses and their details.
PPR PROCESS
STATUSES Description
NEW This status indicates that the PPR has been
successfully submitted for processing, and the
AutoSelect program is digesting the criteria provided
by the user on the header of the PPR in preparation of
the automatic selection the invoices and memos
related to that criteria.
SELECTING INVOICES
This status indicates that the AutoSelect program is
selecting the eligible invoices/memos for the payment
batch based on Due Date, Discount Date, Pay Group,
and other criteria provided by the user on the header
of the PPR
CANCELLED - NO
INVOICES SELECTED
If no invoices or memos met the selection criteria
provided by the user on the header of the PPR, the
PPR is automatically terminated and the status
changes to this status.
MISSING..." STATUSES
Other statuses may appear at this point in the process
if the user failed to included required information on
the PPR header, such as "Missing Exchange Rates",
etc.
INVOICES SELECTED
After selecting the documents (invoices/memos), they
are locked to prevent other checkruns from selecting
the same documents
INVOICES PENDING
REVIEW
This status will only appear if you selected the "Stop
Process for Review After Scheduled Payment
Selection" option on the Processing tab of the PPR
header. This status means that the PPR process has
stopped, and is waiting for you to review the invoices
and memos that were selected for payment (and
make any changes to the batch, as needed). Click on
the Take Action icon to be taken to the Review
Proposed Payments window
CALCULATING SPECIAL
AMOUNTS
This status will only appear if you selected the
"Calculate Payment Withholding and Interest During
the Scheduled Payment Selection" option on the
Processing tab of the PPR header. This status means
that interest and withholding tax are being calculated
and applied, as necessary, to the invoices and memos
selected for this payment batch
ASSEMBLING/ An "interim" status, it appears after the calculation for
ASSEMBLED PAYMENTS
interest and withholding has been completed, and the
Build Payments program is starting. It may appear
again later after the user provides any required bank
account and PPP information for the invoices/memos
("documents") selected
INFORMATION
REQUIRED - PENDING
ACTION
This status appears if you did not provide a default
Internal (Disbursement) Bank Account and/or PPP on
the header of the PPR. In that case, you need to click
on the Take Action icon to be taken to a form where
you can decide which internal bank account and PPP
should be used for each invoice and memo selected
for payment
PENDING PROPOSED
PAYMENT REVIEW
This status will only appear if you selected the "Stop
Process for Review After Creation of Proposed
Payments" option on the Processing tab of the PPR
header. In this case, the system is waiting for you to
review (and modify, if needed) the proposed
payments for this batch. Click on the Take Action icon
to be taken to the "Review Proposed Payments"
window
FORMATTING
This status indicates that the proposed payments
have been turned into payment instruction files. At
this point, you will want to click on the Show link to
view the new associated payment instruction file(s).
Each payment instruction file with have their own PI
Reference Number. If you have both electronic and
paper ("check") payments involved in this payment
batch, you will see a payment instruction file for each
type of payment method
CONFIRMED PAYMENT
Once the payment instructions have been
transmitted/printed and confirmed, the Status of the
PPR changes to this status to indicate a successfully
completed payment batch (PPR)
TERMINATED If the user terminates a PPR anytime prior to
confirmation of the payments (using the Terminate
icon), the status will change to "Terminated", and the
PPR is permanently closed
R12 Payment Process Request(PPR) in Payment Manager
In 11i, we used Payment Batches to pay multiple invoices same time. In R12, PPR is the replacement for 11i Payment Batches. Release 12 payment setup enables a Payment Administrator to select multiple invoices for payment by selection criteria and he can pause the invoice selection and payment build process . During the invoice selection review, payment manager can review the selected invoices, the invoices that met the criteria but were either not validated or were not approved and hence did not get included in the payment process request. He can adjust the invoice selection by adding or removing the invoices and can also review the cash requirements. While reviewing the payments, payment manager can dismiss individual documents or payments if necessary, and restart the payment build process.
Frequently Used Terms..Oracle PaymentsOracle Payments is an e-Business Suite module Payables will leverage to group invoices into payments, create instructions, and print or communicate with the bank. Payment Manager(OA page) is the function you can access it from Payables respondibilty.Navigation Path: Payables->Payments:Entry->Payment Manager
Pay RunA business action to select multiple invoices on a regular basis to be processed for payment. This may also be referred to as creating and processing payment batches and, in this release, managing a payment process request through completion
Payment Process Request The payment process request is the selection of invoices into a group for payment processing.
Payment InstructionInformation compiled from one or more payment process requests that is formatted and either transmitted to a financial institution for payment or used in-house to print check documents..
TemplateTemplates provide a way to store section criteria, payment attributes, and processing rules that can be reused for single pay runs or scheduled pay runs.
Payment Manger PageThere are five tabs under payment manger.
1.HomeThe Home tab on Payment Manager Dashboard presents the useful information for a Payment Manager to:#Monitor the progress of the recent pay run processes #Highlight any payment processes that require attention and automatically prompt to take appropriate actions.#Shortcuts and Tabs for initiating, reviewing and adjusting proposed funds disbursements
2.TemplatesUsing Payment Manager dashboard, a Payment Manager can perform all the tasks associated with pay run process. In the Template tab he can click the “Create” button to create new templates. He can also query a template and then use it to submit or schedule the payment process requests and run cash requirements before a pay run.
3.Payment Process Requests(PPR)Payment Process Requests tab can be used to submit a single payment process request or schedule the repeating payment process requests. The pending action on the payment process request can be performed using “Start Action” icon and the payment request can be cancelled using “Cancel” icon. Clicking on the Payment Process request name, payment manager can drill down to the details.
#Process Automation tab in PPRThe pay run process itself provides for processing steps that you can pause for review based on
your needs. In Process Automation tab, the payment manager can specify up front whether the pay run process should pause for review or if the payment process will be fully automated. Of course, if issues arise during processing that require user input, the process will pause regardless of these options.
##Processing options in Process Automation tab
###Maximize Credits: If Maximize Credits checkbox is enabled then during invoice selection, if there is any credit for a payee, after interest and payment withholding calculations the system will group all scheduled payments for the payee site together to be paid on one payment, and if the sum is negative, the system will reduce the credit amount so the sum is zero.###Stop Process for Review After Scheduled Payment Selection ###Calculate Payment Withholding and Interest During Scheduled Payment Selection ###Stop Process for Review After Creation of Proposed Payments###Create Payment Instructions optionIf the user wants immediate payment instructions creation, the user can set this option to start the payment instruction program immediately when the payment process request has a Completed status. This option has an additional function: It ensures that payments from this payment process request will not be combined with payments from other payment process requests when the system builds the payment instructions. Or, the user can set the option to wait until the Payment Instruction Program is submitted, typically, in this case an enterprise would schedule the Payment Instruction Program to run periodically. An enterprise would choose this option to take all built payments from multiple payment process requests and build fewer payment instructions.
4.Payment InstructionsPayment Manager can use the Payment Instructions tab to review the status of the payment instructions and if required, can perform any subsequent actions. He can also drill down into the
details of the payment instruction and can void all the payments in the instruction.
5.PaymentsPayment Manager can use the Payments tab to review the status of the payments created by his payment process requests. He can also can drill down into the details of the payments to stop or void the payments.
Steps in Pay Run ProcessManaging a Pay Run involves 3 main processes: 1)Selection of the invoices for payment 2)Grouping the invoices into payments3)Building the payment instruction files to either print checks or send instructions to the bank.
Follow red mark numbers in the picture to get the sequence of process steps in Pay Run Process
Pay Run Process
1. Invoice SelectionAfter user submits PPR, the Payment Process request completes with the status “Invoices Pending Review” if it has been configured to pause after the invoice selection. Clicking on “Start Action” icon
navigates the user to the “Selected Scheduled Payments” page.
On the “Selected Scheduled Payments” page, Payment Manager can review the total count of selected scheduled payments. Amount remaining , discounts, payment amount, and interest due can also be reviewed for each currency in the payment process request.
The page also lists all the invoices along with their details. Payment Manager can add or remove the scheduled payments or modify the Discounts and payment amounts.
Clicking on the “View Unselected” takes the Payment Manager to a “Unselected Scheduled Payments” page that gives the following information:Counts for invoices that were never validated and that failed validationsCounts for invoices that require approval and where approval is rejectedCounts of invoices on Scheduled Payment Hold and Supplier Site holdCounts where Payee total is zero or less and where Discount rate is too lowCount of Unselected Payment Schedules, Total Amount, and Discount per currency List of Invoices with invoice information and reason for not getting selected
Payment Manager can add more Scheduled Payments by clicking on the “Add Scheduled Payments”, and choosing the search criteria for the documents payables from the list of values.
Once the Payment Manager is done reviewing the payment process request, he can click on the “Submit” button to initiate the Payment creation process. This action also generates the Scheduled Payment Selection Report again.
The Payment Process will complete with the status “Information Required – Pending Action” if certain information required for the payment creation was missing on scheduled payments. Clicking on “Start Action” icon navigates the user to the “Complete Document Assignments” page.
2.Grouping into Payments The Payment Process request completes with the status “Pending Proposed Payment Review” if it has been configured to pause after the creation of proposed payments. The payment process request also displays the count for documents that were rejected during payment creation. Clicking on “Start Action” icon navigates the user to the “Review Proposed Payments” page.
In the Review Proposed Payments page, payment manager can review the payment information for the selected scheduled payments.
After reviewing, payment manager can then specify the action “Run Payment Process” to submit
the Payment build process. After this action, the payment process request has the status of “Assembled Payments”.
Payment Manager can drill down to view payment details by clicking on the Payment Process request link. He can view the number of payments, documents, and Total Payment Amount per currency. Individual payments are also listed along with more information. By selecting the radio button of a payment, payment manager can view the scheduled payments that got included in that payment.
Clicking on “Rejected and Removed Items”, Payment manager can navigate to see the details for scheduled payments that got rejected/removed.
Rejected and Removed Items page lists the rejected document payables, and clicking on the reference number link you can view the details of the document and the reason it got rejected.
3.Building Payment InstructionsFor creating Printed payment instructions, Payment Manager can specify the criteria for selecting payments and printing information. The criteria can include the Payment Process profile, Currency, Internal Bank Account, Payment Document, Payment Process Request, etc.