Peer-to-peer test cases

An overview of peer-to-peer test cases.

Last updated 15 January 2018

Send and receive IRR and IRER

IRR test cases

Table 12: IRR1.1 Valid single member IRR message
Fund A		Fund B
IRR1.1.FNDA.01	Fund A Send IRR
		IRR1.1.FNDB.01	Fund B Receive IRR
		IRR1.1.FNDB.02	Fund B Send RTR
IRR1.1.FNDA.02	Fund A Receive RTR
IRR1.1.FNDA.03	Fund A Send RTOR
		IRR1.1.FNDB.03	Fund B Receive RTOR

Table 13: IRR1.2 Valid multiple member IRR message
Fund A		Fund B
IRR1.2.FNDA.01	Fund A Send IRR
		IRR1.2.FNDB.01	Fund B Receive IRR
		IRR1.2.FNDB.02	Fund B Send RTR
IRR1.2.FNDA.02	Fund A Receive RTR
IRR1.2.FNDA.03	Fund A Send RTOR
		IRR1.2.FNDB.03	Fund B Receive RTOR

Note: it is optional to send a multiple member IRR but all funds must test that they can receive a multiple member IRR

Table 14: IRR1.3 Valid IRR message with Other Details tuple populated with an agreed value between peers
Fund A		Fund B
IRR1.3.FNDA.01	Fund A Send IRR
		IRR1.3.FNDB.01	Fund B Receive IRR
		IRR1.3.FNDB.02	Fund B Send RTR
IRR1.3.FNDA.02	Fund A Receive RTR
IRR1.3.FNDA.03	Fund A Send RTOR
		IRR1.3.FNDB.03	Fund B Receive RTOR

Note: optional to send, mandatory to receive

Table 15: IRR1.4 Valid IRR message with Record Count populated
Fund A		Fund B
IRR1.4.FNDA.01	Fund A Send IRR
		IRR1.4.FNDB.01	Fund B Receive IRR
		IRR1.4.FNDB.02	Fund B Send RTR
IRR1.4.FNDA.02	Fund A Receive RTR
IRR1.4.FNDA.03	Fund A Send RTOR
		IRR1.4.FNDB.03	Fund B Receive RTOR

IRER test cases

Table 16: IRER2.1 IRER Business error – member doesn’t exist, SUPER.GEN.GEN.21 - Member not found with supplied information
Fund A		Fund B
IRER2.1.FNDA.01	Fund A Send IRR
		IRER2.1.FNDB.01	Fund B Receive IRR
IRER2.1.FNDA.02	Fund A Receive IRER

Table 17: IRER2.2 IRER message with Context ID included
Fund A		Fund B
IRER2.2.FNDA.01	Fund A Send IRR
		IRER2.2.FNDB.01	Fund B Receive IRR
IRER2.2.FNDA.02	Fund A Receive IRER

Note: optional to send, mandatory to receive

Send and receive RTR and RTOR

RTR test cases

Table 18: RTR3.1 Valid single member RTR message
Fund A		Fund B
RTR3.1.FNDA.01	Fund A Send RTR
		RTR3.1.FNDB.01	Fund B Receive RTR
		RTR3.1.FNDB.02	Fund B Receive RTOR
RTR3.1.FNDA.02	Fund A Receive RTOR

Table 19: RTR3.2 Valid multiple member RTR message successfully
Fund A		Fund B
RTR3.2.FNDA.01	Fund A Send RTR
		RTR3.2.FNDB.01	Fund B Receive RTR
		RTR3.2.FNDB.02	Fund B Receive RTOR
RTR3.2.FNDA.02	Fund A Receive RTOR

Note: optional to send, mandatory to receive

Table 20: RTR3.3 Valid member rollover with no TFN processed (using Member ID)
Fund A		Fund B
RTR3.3.FNDA.01	Fund A Send RTR
		RTR3.3.FNDB.01	Fund B Receive RTR
		RTR3.3.FNDB.02	Fund B Receive RTOR
RTR3.3.FNDA.02	Fund A Receive RTOR

Table 21: RTR3.4 Valid member rollover transaction, Other Details tuples provided
Fund A		Fund B
RTR3.4.FNDA.01	Fund A Send RTR
		RTR3.4.FNDB.01	Fund B Receive RTR
		RTR3.4.FNDB.02	Fund B Receive RTOR
RTR3.4.FNDA.02	Fund A Receive RTOR

Note: optional to send, mandatory to receive

Table 22: RTR3.5 Valid member rollover transaction, Record count populated
Fund A		Fund B
RTR3.5.FNDA.01	Fund A Send RTR
		RTR3.5.FNDB.01	Fund B Receive RTR
		RTR3.5.FNDB.02	Fund B Receive RTOR
RTR3.5.FNDA.02	Fund A Receive RTOR

RTOR test cases

Table 23: RTOR4.1 Rollover processed successfully
Fund A		Fund B
RTOR4.1.FNDA.01	Fund A Send RTR
		RTOR4.1.FNDB.01	Fund B Receive RTR
		RTOR4.1.FNDB.02	Fund B Receive RTOR
RTOR4.1.FNDA.02	Fund A Receive RTOR

Table 24: RTOR4.2 Business error: - Member level refund because member doesn’t exist, SUPER.GEN.GEN.21 - Member not found with supplied information
Fund A		Fund B
RTOR4.2.FNDA.01	Fund A Send RTR
		RTOR4.2.FNDB.01	Fund B Receive RTR
		RTOR4.2.FNDB.02	Fund B Receive RTOR
RTOR4.2.FNDA.02	Fund A Receive RTOR

Table 25: RTOR4.3 RTOR with Context ID included
Fund A		Fund B
RTOR4.3.FNDA.01	Fund A Send RTR
		RTOR4.3.FNDB.01	Fund B Receive RTR
		RTOR4.3.FNDB.02	Fund B Receive RTOR
RTOR4.3.FNDA.02	Fund A Receive RTOR

Note: optional to send, mandatory to receive

Version 1 & version 2 test cases

Refer to Versioning scenarios for versioning scenario diagrams.

Table 26: RTOR4.1 Rollover processed successfully
Fund A		Fund B
RTOR4.1.FNDA.01	Fund A Receive RTR
		RTOR4.1.FNDB.01	Fund B Send RTR
		RTOR4.1.FNDB.02	Fund B Send RTOR
RTOR4.1.FNDA.02	Fund A Receive RTOR

Table 27: RTOR4.2 Business error: - Member level refund because member doesn’t exist, SUPER.GEN.GEN.21 - Member not found with supplied information
Fund A		Fund B
RTOR4.2.FNDA.01	Fund A Receive RTR
		RTOR4.2.FNDB.01	Fund B Send RTR
		RTOR4.2.FNDB.02	Fund B Send RTOR
RTOR4.2.FNDA.02	Fund A Receive RTOR

Table 28: RTOR4.3 RTOR with Context ID included
Fund A		Fund B
RTOR4.3.FNDA.01	Fund A Receive RTR
		RTOR4.3.FNDB.01	Fund B Send RTR
		RTOR4.3.FNDB.02	Fund B Send RTOR
RTOR4.3.FNDA.02	Fund A Receive RTOR

Note: optional to send, mandatory to receive

Send and receive USM and USMOR messages

USM test cases

Table 29: USM6.1 Valid single member USM rollover
ATO		Fund A
USM6.1.ATO.01	ATO Send USM
		USM6.1.FNDA.01	Fund A receive USM
		USM6.1.FNDA.02	Fund A Send USMOR
USM6.1.ATO.02	ATO Receive USMOR

Table 30: USM6.2 Valid multiple member USM rollovers
ATO		Fund A
USM6.2.ATO.01	ATO Send USM
		USM6.2.FNDA.01	Fund A receive USM
		USM6.2.FNDA.02	Fund A Send USMOR
USM6.2.ATO.02	ATO Receive USMOR

Table 31: USM6.3 Valid member USM rollover with no TFN, including Member ID
ATO		Fund A
USM6.3.ATO.01	ATO Send USM
		USM6.3.FNDA.01	Fund A receive USM
		USM6.3.FNDA.02	Fund A Send USMOR
USM6.3.ATO.02	ATO Receive USMOR

Table 32: USM6.4 Valid member USM rollover with Other Details tuple populated
ATO		Fund A
USM6.4.ATO.01	ATO Send USM
		USM6.1.FNDA.01	Fund A receive USM
		USM6.1.FNDA.02	Fund A Send USMOR
USM6.1.ATO.02	ATO Receive USMOR

Table 33: USM6.5 Valid member USM message with all fields populated that will be sent in a normal message
ATO		Fund A
USM6.5.ATO.01	ATO Send USM
		USM6.5.FNDA.01	Fund A receive USM
		USM6.5.FNDA.02	Fund A Send USMOR
USM6.5.ATO.02	ATO Receive USMOR

Table 34: USM6.6 Valid member USM message with only the minimum number of mandatory fields populated
ATO		Fund A
USM6.6.ATO.01	ATO Send USM
		USM6.6.FNDA.01	Fund A receive USM
		USM6.6.FNDA.02	Fund A Send USMOR
USM6.6.ATO.02	ATO Receive USMOR

Table 35: USM6.7 Valid member USM message with Record Count populated
ATO		Fund A
USM6.7.ATO.01	ATO Send USM
		USM6.7.FNDA.01	Fund A receive USM
		USM6.7.FNDA.02	Fund A Send USMOR
USM6.7.ATO.02	ATO Receive USMOR

USMOR test cases

Table 36: USMOR7.1 USM rollover processed successfully
ATO		Fund A
USMOR7.1.ATO.01	ATO Send USM
		USMOR7.1.FNDA.01	USMOR7.1.FNDA.01 Fund A Receive USM
		USMOR7.1.FNDA.02	Fund A Send USMOR

Table 37: USMOR7.2 Business error: - Member level refund because member doesn’t exist, SUPER.GEN.GEN.21 - Member not found with supplied information
ATO		Fund A
USMOR7.2.ATO.01	ATO Send USM
		USMOR7.2.FNDA.01	USMOR7.1.FNDA.01 Fund A Receive USM
		USMOR7.2.FNDA.02	Fund A Send USMOR

Table 38: USMOR7.3 USMOR with Context ID included
ATO		Fund A
USMOR7.1.ATO.01	ATO Send USM
		USMOR7.1.FNDA.01	USMOR7.1.FNDA.01 Fund A Receive USM
		USMOR7.1.FNDA.02	Fund A Send USMOR

Note: mandatory to send and receive

Send and receive EPF

EPF test cases

Table 39: EPF8.1 Valid Single member EPF message
ATO		Fund A
EPF8.1.ATO.01	ATO Send EPF
		EPF8.1.FNDA.01	Fund A Receive EPF

Table 40: EPF.8.2 Valid EPF message with Other Details tuples populated with agreed value (OPTIONAL)
ATO		Fund A
EPF8.2.ATO.01	ATO Send EPF
		EPF8.2.FNDA.01	Fund A Receive EPF

Table 41: EPF 8.3 Valid EPF message with Record Count populated
ATO		Fund A
EPF8.3.ATO.01	ATO Send EPF
		EPF8.3.FNDA.01	Fund A Receive EPF

Table 42 EPF 8.4 ATO sends EPF v1 and Fund is v1
ATO		Fund A
EPF8.4.ATO.01	ATO Send EPF
		EPF8.4.FNDA.01	Fund A Receive EPF

Table 43: EPF 8.5 ATO sends EPF v1 and Fund is v2 (INCORRECT)
ATO		Fund A
EPF8.5.ATO.01	ATO Send EPF
		EPF8.5.FNDA.01	Fund A Receive EPF

Table 44: EPF 8.6 ATO sends EPF v2 and Fund is v2
ATO		Fund A
EPF8.6.ATO.01	ATO Send EPF
		EPF8.6.FNDA.01	Fund A Receive EPF

Table 45: EPF 8.7 ATO sends EPF v2 and Fund is v1 (INCORRECT)
ATO		Fund A
EPF8.6.ATO.01	ATO Send EPF
		EPF8.6.FNDA.01	Fund A Receive EPF

QC50524