I need help with what the proper audit assertions would be for each procedure

3.4.1 Audit Objective To identify payments which are suspicious or may be invalid. AUDITING PROCEDURES ASSERTIONS WORK DONE BY (INITIALS) EXTENT OF TESTING 1 Obtain the data files from the client and load onto the PC. Load IDEA and create a project for Accounts Payable for Bright IDEAs Inc. Import the data and agree the total of Accounts Payable: 2 a) Import the Accounts Payable transactions, Completeness Completeness b) Import the Authorized Suppliers details, c) Compute field statistics to verify that the data has been imported correctly, 3 d) Select a control total field for each database, and e) Use Discover to identify trends within the data. Analyze the profile of the number and value of payments by numeric band to identify any unusual trends and to determine high value amounts for extractions. 4 5 Identify high and unusual amounts. Identify further unusual payments from previous analyses including: a) "CASH" in Payee name, b) Round sum amounts, c) Payments authorized by HMV, and d) Payments made on a Sunday. 6 7 Test for duplicate payments and vendors/payees. Test for completeness by testing for gaps in the check number sequence. Identify working days on which no payments were processed. 8 AUDITING PROCEDURES ASSERTIONS WORK DONE BY (INITIALS) EXTENT OF TESTING 9 10 Analyze payment terms and ensure that the payment policy for Bright IDEAs Inc. has been followed. Test the validity of payments to authorized suppliers. Analyze payments by supplier to identify significant changes from the previous year's total. 11