Banking Starter Pack
Overview
This documentation lists all scenarios defined in the Banking starter pack. To use a starter pack, ensure that you have already completed the steps in Use a starter pack.
Customer onboarding test scenarios
| Test scenarios | Service type | Description and Query |
|---|---|---|
| Create a customer |
| Creates a user with the following details using API:
|
| Create an account and contract |
| Creates a bank account with the following details using API:
|
| Create parent-child relationship |
| Links a child’s account to their parent’s account. |
| Update customer details |
| Updates the details of a customer. The Person ID number value cannot be updated, but the following can be:
|
| Update account details |
| Updates the details of an account. The
|
Pricing set-up test scenarios
| Test scenarios | Service type | Description and Query |
|---|---|---|
| Assign price list at a customer level |
| Assigns a list of standard prices for items to a customer, including the following details:
|
| Assign price list at an account level |
| Assigns a list of standard prices for items to an account, including the following details:
|
| Assign override pricing at a customer level |
| Assigns a price list that overrides any existing price list assigned to the customer. |
| Assign override pricing at an account level |
| Assigns a price list that overrides any existing price list assigned to an account. |
Billing test scenarios
| Test scenarios | Service type | Description |
|---|---|---|
| Generate bill from billing batches |
| Generates a bill using the account name. For batch testing, it runs the following batches in order:
|
| Generate bill from application |
| Runs the following batches in order:
|
Payment test scenarios
| Test scenarios | Service type | Description and Query |
|---|---|---|
| Create payment |
| Creates a payment for the already generated bill. For UI: For API: |
General ledger test scenarios
| Test scenarios | Service type | Description |
|---|---|---|
| Link general ledger (GL) to account |
| Runs the following batches in order:
|
SFTP test scenarios
The following scenarios support file uploads for SFTP and Batch service types:
- Create price list
- Define price list-price item
- Assign price list
- Onboard a customer
- Create person hierarchy
- Create account
- Create invoice
- Upload feed management
//Input - Account Identifier, Bill ID
SELECT TP.ACCT_NBR
,TP.BILL_ID
,TO_CHAR(MAX(TP.CRE_DTTM), 'MM-DD-YYYY') AS BILL_DATE
,TP.BILL_AMOUNT
,TO_CHAR(TP.LATEST_PAYMENT_DATE, 'MM-DD-YYYY') AS LATEST_PAYMENT_DATE
,TP.LATEST_PAYMENT_AMOUNT
,TP.TOTAL_PAYMENT_STATUS
,TP.TOTAL_PAID_AMOUNT
,(TP.BILL_AMOUNT - TP.TOTAL_PAID_AMOUNT) AS OUTSTANDING_PAYMENT
FROM (
SELECT B.ACCT_NBR
,A.BILL_ID
,A.ORIG_BILL_AMT AS BILL_AMOUNT
,SUM(D.PAY_AMT) OVER (PARTITION BY A.BILL_ID) AS TOTAL_PAID_AMOUNT
,C.DESCR AS TOTAL_PAYMENT_STATUS
,A.CRE_DTTM
,D.PAY_AMT AS LATEST_PAYMENT_AMOUNT
,E.CRE_DTTM LATEST_PAYMENT_DATE
,ROW_NUMBER() OVER (
PARTITION BY A.BILL_ID ORDER BY E.CRE_DTTM DESC
) AS RN
FROM C1_BILL_DTLS_VW A
INNER JOIN CI_ACCT_NBR B ON A.ACCT_ID = B.ACCT_ID
INNER JOIN CI_PAY D ON D.ACCT_ID = A.ACCT_ID
INNER JOIN CI_LOOKUP_VAL_L C ON C.FIELD_NAME = 'PAY_STATUS_FLG'
AND C.FIELD_VALUE = D.PAY_STATUS_FLG
INNER JOIN CI_PAY_EVENT E ON E.PAY_EVENT_ID = D.PAY_EVENT_ID
WHERE TRIM(B.ACCT_NBR) = TRIM(:F1 --Account Identifier)
AND A.BILL_ID = ${ :F2 -- Bill ID}
) TP
WHERE TP.RN = 1
GROUP BY TP.ACCT_NBR
,TP.BILL_ID
,TP.BILL_AMOUNT
,TP.LATEST_PAYMENT_DATE
,TP.LATEST_PAYMENT_AMOUNT
,TP.TOTAL_PAYMENT_STATUS
,TP.TOTAL_PAID_AMOUNT
ORDER BY BILL_DATE DESC FETCH FIRST 1 ROW ONLY
Report generation
| Available reports | Available service type | Description |
|---|---|---|
| Aging Detail Report |
| Generates a Form of Payment (FOP) report based on aging details. |
| Payment Detail Report |
| Generates a Form of Payment (FOP) report based on payment details. |
| Payment Summary Report |
| Generates a Form of Payment (FOP) summary report. |
| Adjustment Detail Report |
| Generates a Form of Payment (FOP) report with adjustment details. |