Payment Request Form – Process Flow

(Requestor)
Oracle PaaS

Initiate Payment Enter Payment Details

(Supplier Details, Payment Submit Payment
Start Request Creation Date, Payment Terms, Search Screen
(Form) Request for approval
Payment Amount etc)

Action 1 : Create and Capture Action 2: Search

the previous
Oracle SaaS (Accounts Payables)

submitted data
Create Payment Request in Approver review Approve
Accounts Payables module Approve /
Email Notification of Reject?
AP Invoice Approval

Reject Inform Requestor

Validate Invoice
above the action

Submit Payment End

Request for approval

1
Action 1 : Create and Capture
Screen 1

All the places

where there is
drop down data
come from ERP

Business Rule 1:
Invoice date cant be
Business Rule 2: more than 90 days old
Invoice Number is user
entered field and
should not have any
special characters
Business Rule 4:
Invoice number will Character length should not be more than 400 ( ERP limitation)
have limit
Business Rule 3:
For each header there has to be one line item
Action 1 : Create and Capture
Screen 1 : contd..
Action 1 : Create and Capture
Screen 2 : Line Items

Business Rule 7:
Based on selected supplier site WHT
All the places applicable decision is taken. ( Yes or No)
where there is Business Rule 8:
drop down data Based on withholding task applicability
come from ERP WHT Borne will be decided.

Business Rule 5: Business Rule 9.

Based on the data
selected in individual There are other rules implemented too,
tabs respective entry which needs to be validated against KWS
get populated in requirements.
another tabs.

This matrix is recorded

in functional interface
doc.

Business Rule 6:
On save ERP API gets executed to validate the combination of GL Account, if
valid then it returns the existing combination id , if not created it created new
ID and return the Code Combination ID.
 Action 1 : Create and Capture
Screen 3 : Summary Screen

This screen, shows all the data entered by

users in pervious screens.

User can edit or modify existing invoice line

items

User can attach one attachment only

User finally submit the data, which is sent to

ERP.

AP invoice once created successfully result is

shown on the screen, if not created
successfully application asks user to submit
again

Business Rule 10.

Assumption 1.
Email of the requestor is shown at the
Invoices are never stored as Draft and if
bottom and upon successful AP invoice
users cancels, he has to do it from scratch.
creation, email is sent to requestor email
id.
Action 2 : Create and Capture
Screen 1 : Search Screen

Search Screen

This screen, shows all the previous submitted

invoices and there status.

The status is ERP status.

This screen has restricted access to limited

people only. Data on this screen shows all the
invoice created so far with no data level
restriction

User has option to download the search

results into a CSV file.

Assumption 2.

Similar Security Matrix will be

implemented at KWS too.