IDENTREGISTER2 Supplier data record 2 IDENTREGISTER3 Supplier data record 3 IDENTITY Provider identity data record PYMT Payment identity data record MVAR Member variation data record DVTR Amounts transfer-out data record FILE-TOTAL File total data record The reported in the Number of records in file field must equal the sum of all records on the data file. 8 When the ATO sends a Remittance advice with details of member credit payments or a Rollover benefits statement for USM credit payments, the provider will concurrently receive super co-contributions, LISC, SG payments, SHA special account payments, USM payments or Government FHSA contributions from the ATO. If some or all of these payments cannot be accepted, this must be reported on a PVA statement and any rejected payments repaid. The ATO has developed processes to enable repayments to be made using BECS direct credit, cheque or BPAY. In some cases, a PVA statement and the repayment may be lodged as separate flows. If this occurs, information must be provided in these message flows to assist the ATO to reconcile the PVA statement with the repayment. A cross field reference convention is used to link the payment and PVA statement flows together. The convention used is based on SuperEC payment conventions. A Payment identity data record has been added to the PVA statement for each provider. To create the link, fields in the Payment identity data record have been matched with corresponding fields relevant to each of the payment methods that may be used. The table below shows how the fields on the Payment identity data record have been mapped to BECS direct credit payment, BPAY and cheque payment fields.
IDENTREGISTER2 Supplier data record 2 IDENTREGISTER3 Supplier data record 3 IDENTITY Provider identity data record PYMT Payment identity data record MVAR Member variation data record DVTR Amounts transfer-out data record FILE-TOTAL File total data record The reported in the Number of records in file field must equal the sum of all records on the data file. 8 When the ATO sends a Remittance advice with details of member credit payments or a Rollover benefits statement for USM credit payments, the provider will concurrently receive super co-contributions, LISC, SG payments, SHA special account payments, USM payments or Government FHSA contributions from the ATO. If some or all of these payments cannot be accepted, this must be reported on a PVA statement and any rejected payments repaid. The ATO has developed processes to enable repayments to be made using BECS direct credit, cheque or BPAY. In some cases, a PVA statement and the repayment may be lodged as separate flows. If this occurs, information must be provided in these message flows to assist the ATO to reconcile the PVA statement with the repayment. A cross field reference convention is used to link the payment and PVA statement flows together. The convention used is based on SuperEC payment conventions. A Payment identity data record has been added to the PVA statement for each provider. To create the link, fields in the Payment identity data record have been matched with corresponding fields relevant to each of the payment methods that may be used. The table below shows how the fields on the Payment identity data record have been mapped to BECS direct credit payment, BPAY and cheque payment fields.
Payment_variation_advice_%28PVA%29_statement_specification_tracked_final_v3.2.1.docx