Personal Property Securities Register

Personal Property Securities Register

B2G Mailbox Notifications

Version 1.2

Document State: For external use

Version release: R3

UNCLASSIFIED

Table of Contents

Table of Contents

1Introduction

1.1Purpose

1.2Audience

1.3Scope

1.4Acronyms

1.5Reference Documents

2Notification Types Overview

2.1Notification Types

2.2XML Schema Definition (XSD)

2.3Versioning Considerations

2.4Use of Reference Types

3B2G Mailbox Message Datatypes

3.1Common Notification Message Classes

3.2Common Verification Statement Classes

3.3VerificationStatementRegistrationCreatedType

3.4VerificationStatementRegistrationAmendedType

3.5VerificationStatementRegistrationDischargedType

3.6VerificationStatementRegistrationRemovedType

3.7VerificationStatementChangeOfAddressForServiceType

3.8VerificationStatementChangeOfSecuredPartyGroupType

3.9VerificationStatementChangeOfSecuredPartyGroupSingleType

3.10RegistrationTokenIssuedType

3.11RegistrationTokenResetType

3.12RegistrationTokensResetType

3.13SecuredPartyGroupAccessCodeIssuedType

3.14SecuredPartyGroupAccessCodeResetType

3.15SecuredPartyGroupAccessCodeChangedType

3.16SecuredPartyGroupNumberType

3.17CriticalNoticeType

4Reference Types

4.1CollateralClassType

4.2CollateralType

4.3ExtendedBooleanType

4.4GrantorType

4.5IdentifierVerificationStatusType

4.6NevdisVehicleIdentifierType

4.7NotificationType

4.8OrganisationNumberType

4.9SecuredPartyType

4.10SerialNumberType

1Introduction

1.1Purpose

PPSR provides a B2G Channel that allows customers to develop their own systems that interact with PPSR using SOAP based web services. The B2G Channel provides a B2G Mailbox as a means for PPSR to securely deliver notification messages to B2G Account Customers using the B2G Channel.

The purpose of this document is to describe each of the notification messages that PPSR will provide for B2G Account Customers through their B2G Mailbox.

1.2Audience

The audience for this document is primarily those customerswho will use the PPSR B2G Channel and need to build systems to process PPSR notification messages from their B2G Mailbox.

1.3Scope

The scope of this document is limited to the following:

Defining each type of notification message
Describing the elements that make up each notification message

Separate to this document, an XML schema definition file (XSD) is available to precisely describe the structure of the notification messages. The XSD will be published and made available on the PPSR public website (

The details of how a B2G Account Customer can retrieve these notification messages from their B2G Mailbox are not in this document. These details are described in the PPSR B2G Interface Specification.

1.4Acronyms

ABN / Australian Business Number
ABR / Australian Business Register
ACN / Australian Company Number
ARBN / Australian Registered Business Number
ARSN / Australian Registered Scheme Number
ASIC / Australian Securities and Investments Commission
B2G / Business To Government
HTML / HyperText Markup Language
PDF / Portable Document Format
PPSR / Personal Property Securities Register
SOAP / Simple Object Access Protocol
XSD / XML Schema Definition

1.5Reference Documents

Audiences should also read:

PPSR - B2G Interface Specification
PPSR - Graphic Design - Verification Statements

PPSR B2G Mailbox Notifications (R3)Page 1 of 75

UNCLASSIFIED

2Notification Types Overview

2.1Notification Types

The following table lists each of the distinct types of notification messages that can be provided in the B2G Mailbox and the filter criteria that are specific to each notification type.

Notification Type / Description / Filters (specific to that type)
VerificationStatementRegistrationCreated / A Verification Statement for a new Registration. / The Timestamp of the Message
Message ID Range
Change Number
Giving of Notice Identifier
Original Customer’s Request Message Id
Registration Number
Secured Party Group Number
VerificationStatementRegistrationAmended / A Verification Statement for a Registration that has been amended. / The Timestamp of the Message
Message ID Range
Change Number
Giving of Notice Identifier
Original Customer’s Request Message Id
Registration Number
Secured Party Group Number
VerificationStatementRegistrationDischarged / A Verification Statement for a Registration that has been discharged. / The Timestamp of the Message
Message ID Range
Change Number
Giving of Notice Identifier
Original Customer’s Request Message Id
Registration Number
Secured Party Group Number
VerificationStatementRegistrationRemoved / A Verification Statement for a Registration that has been removed from the Register by the Registrar. / The Timestamp of the Message
Message ID Range
Change Number
Giving of Notice Identifier
Registration Number
Secured Party Group Number
VerificationStatementChangeOfAddressForService / A Verification Statement when a Secured Party Group has changed their Address for Service. / The Timestamp of the Message
Message ID Range
Original Customer’s Request Message Id
Secured Party Group Number
VerificationStatementChangeOfSecuredPartyGroup / A Verification Statement when a Secured Party Group has transferred all Registrations to another Secured Party Group. / The Timestamp of the Message
Message ID Range
Original Customer’s Request Message Id
Secured Party Group Number
VerificationStatementChangeOfSecuredPartyGroupSingle / A Verification Statement when a Secured Party Group has transferred a single Registration to another Secured Party Group. / The Timestamp of the Message
Message ID Range
Change Number
Giving of Notice Identifier
Original Customer’s Request Message Id
Registration Number
Secured Party Group Number
ReissueVerificationStatementRegistrationCreated / Reissue of a Verification Statement for a new Registration. / The Timestamp of the Message
Message ID Range
Change Number
Giving of Notice Identifier
Original Customer’s Request Message Id
Registration Number
Secured Party Group Number
ReissueVerificationStatementRegistrationAmended / Reissue of a Verification Statement for a Registration that has been amended. / The Timestamp of the Message
Message ID Range
Change Number
Giving of Notice Identifier
Original Customer’s Request Message Id
Registration Number
Secured Party Group Number
ReissueVerificationStatementRegistrationDischarged / Reissue of a Verification Statement for a Registration that has been discharged. / The Timestamp of the Message
Message ID Range
Change Number
Giving of Notice Identifier
Original Customer’s Request Message Id
Registration Number
Secured Party Group Number
ReissueVerificationStatementRegistrationRemoved / Reissue of a Verification Statement for a Registration that has been removed from the Register by the Registrar. / The Timestamp of the Message
Message ID Range
Change Number
Giving of Notice Identifier
Original Customer’s Request Message Id
Registration Number
Secured Party Group Number
ReissueVerificationStatementChangeOfAddressForService / Reissue of a Verification Statement when a Secured Party Group has changed their Address for Service. / The Timestamp of the Message
Message ID Range
Original Customer’s Request Message Id
Secured Party Group Number
ReissueVerificationStatementChangeOfSecuredPartyGroup / Reissue of a Verification Statement when a Secured Party Group has transferred all Registrations to another Secured Party Group. / The Timestamp of the Message
Message ID Range
Original Customer’s Request Message Id
Secured Party Group Number
ReissueVerificationStatementChangeOfSecuredPartyGroupSingle / Reissue of a Verification Statement when a Secured Party Group has transferred a single Registration to another Secured Party Group. / The Timestamp of the Message
Message ID Range
Change Number
Giving of Notice Identifier
Original Customer’s Request Message Id
Registration Number
Secured Party Group Number
RegistrationTokenIssued / A Registration Token issued for a new Registration. / The Timestamp of the Message
Message ID Range
Giving of Notice Identifier
Original Customer’s Request Message Id
Registration Number
RegistrationTokenReset / A new Registration Token issued for an existing Registration when the Registration Token has been reset. / The Timestamp of the Message
Message ID Range
Giving of Notice Identifier
Original Customer’s Request Message Id
Registration Number
RegistrationTokensReset / New Registration Tokens issued for existing Registrations when the Registrations for a Secured Party Group are transferred to another Secured Party Group. / The Timestamp of the Message
Message ID Range
SecuredPartyGroupAccessCodeIssued / A Secured Party Group Access Code issued for a new Secured Party Group. / The Timestamp of the Message
Message ID Range
Original Customer’s Request Message Id
Secured Party Group Number
SecuredPartyGroupAccessCodeReset / A new Secured Party Group Access Code issued for an existing Secured Party Group when the Secured Party Group Access Code has been reset. / The Timestamp of the Message
Message ID Range
Original Customer’s Request Message Id
Secured Party Group Number
SecuredPartyGroupAccessCodeChanged / A new Secured Party Group Access Code when the Secured Party Group has changed their Secured Party Group Access Code to a new value chosen by the Secured Party Group. / The Timestamp of the Message
Message ID Range
Original Customer’s Request Message Id
Secured Party Group Number
SecuredPartyGroupNumber / A Secured Party Group Number sent to a Secured Party Group Address for Service for a Secured Party Group that has forgotten their Secured Party Group Number. / The Timestamp of the Message
Message ID Range
Original Customer’s Request Message Id
Secured Party Group Number
CriticalNotice / A new Critical Notice sent to a B2G Account Customer. / The Timestamp of the Message
Message ID Range

PPSR B2G Mailbox Notifications (R3)Page 1 of 75

UNCLASSIFIED

The value of the notification type in the above table will be the value of the NotificationType element within the B2GMailboxMessage element returned by the Retrieve Messages operation of the B2G Mailbox Service of the PPSR B2G interface.

The XML for each of these notification types is described in detail in section3B2G Mailbox Message Datatypes.

Most of the notification types are provided in the B2G Mailbox of the B2G Account Customer because the Account Customer Number of the B2G Account Customer is defined in the Address for Service of one or more Secured Party Groups. These include the following notification types:

Verification Statements for new and altered Registrations:
VerificationStatementRegistrationCreated
VerificationStatementRegistrationAmended
VerificationStatementRegistrationDischarged
VerificationStatementRegistrationRemoved
VerificationStatementChangeOfAddressForService
VerificationStatementChangeOfSecuredPartyGroup
VerificationStatementChangeOfSecuredPartyGroupSingle
ReissueVerificationStatementRegistrationCreated
ReissueVerificationStatementRegistrationAmended
ReissueVerificationStatementRegistrationDischarged
ReissueVerificationStatementRegistrationRemoved
ReissueVerificationStatementChangeOfAddressForService
ReissueVerificationStatementChangeOfSecuredPartyGroup
ReissueVerificationStatementChangeOfSecuredPartyGroupSingle
Registration Tokens:
RegistrationTokenIssued
RegistrationTokenReset
RegistrationTokensReset
Secured Party Group Numbers and Access Codes:
SecuredPartyGroupAccessCodeIssued
SecuredPartyGroupAccessCodeReset
SecuredPartyGroupAccessCodeChanged
SecuredPartyGroupNumber

Other notification types that are provided in the B2G Mailbox are related to the Account Customer simply being a B2G Account Customer, rather than being the Address for Service of a Secured Party Group. These include the following notification types:

System Messages and Notices from the Registrar’s Office:
CriticalNotice

2.2XML Schema Definition (XSD)

The schema definitions for the notification types are provided in an XML Schema Definition (XSD) file. The XSD file can be used by B2G Account Customers to build software to automate the processing of the notification messages provided in the B2G Mailbox.

2.2.1XML Namespace for Notifications

PPSR uses a single XML namespace for defining all data elements that make up the notifications provided through the B2G Mailbox. The name of the namespace is .

2.3Versioning Considerations

Over time, changes may need to be made to the notification messages provided through the B2G Mailbox. These may include:

the addition of a new notification type
additional information provided for an existing notification type

2.3.1New Notification Types

When a new type of notification message needs to be provided through the B2G Mailbox, a new notification type will be added to the namespace to describe the schema of the new notification type. An update to the notifications XSD will be published and made available on the PPSR public website (

It will be up to each B2G Account Customer to determine when and if they make use of the new XSD and provide processing for the new notification type.

2.3.2Additional Information for an Existing Notification Type

If additional information is provided for an existing notification type,new elements will be added to the schema definition for the notification type. An update to the notifications XSD will be published and made available on the PPSR public website (

It will be up to each B2G Account Customer to determine when and if they make use of the new XSD and provide processing for the new elements. To ensure a B2G Account Customer’s system continues to process messages for the existing notification type until they make use of the new XSD, B2G Account Customers need to ensure they support ‘lax’ processing of the XML in notification messages (i.e. that they can continue to process messages even if there are elements in a message that were not originally defined in the schema).

To ensure correct processing of messages when new elements are added, new elements will always be added in sequence after existing elements.

2.4Use of Reference Types

PPSR uses reference data types that have a restricted list of available values (see section 4Reference Types). Where these reference data types are used in the namespace they are defined as type xs:string, and the text of the values for reference data types in notification messages will be the value as defined in section 4Reference Types.

PPSR B2G Mailbox Notifications (R3)Page 1 of 75

UNCLASSIFIED

3B2G Mailbox Message Datatypes

A B2G Mailbox Message retrieved using the Retrieve Messages operation of the B2G Mailbox service (refer to the document “PPSR - 7.6.6.3 - B2G Interface Specification”) has the following schema:

Each B2G Mailbox Message describes both message metadata and message content. The metadata includes data items such as a unique Message Id for the message, the date/time the message was added to the B2G Mailbox and the notification type. The message content is returned as XML. The structure of the XML in each B2G Mailbox Message depends on the NotificationType of the message (see section 4.7NotificationType).

A B2G Mailbox Message contains message content in the Message element of the B2GMailboxMessage. The Message element’s XML datatype is defined as follows:

<xs:element name="Message" nillable="true">

<xs:complexType>

<xs:sequence>

<xs:any minOccurs="0" processContents="lax" />

</xs:sequence>

</xs:complexType>

</xs:element>

This allows the Message element to contain any XML. The actual datatype of the content contained in the Message element will depend on the NotificationType of the message. These are shown in the following table:

Notification Type / XML Datatype of Message Content
VerificationStatementRegistrationCreated
ReissueVerificationStatementRegistrationCreated / VerificationStatementRegistrationCreatedType
VerificationStatementRegistrationAmended
ReissueVerificationStatementRegistrationAmended / VerificationStatementRegistrationAmendedType
VerificationStatementRegistrationDischarged
ReissueVerificationStatementRegistrationDischarged / VerificationStatementRegistrationDischargedType
VerificationStatementRegistrationRemoved
ReissueVerificationStatementRegistrationRemoved / VerificationStatementRegistrationRemovedType
VerificationStatementChangeOfAddressForService
ReissueVerificationStatementChangeOfAddressForService / VerificationStatementChangeOfAddressForServiceType
VerificationStatementChangeOfSecuredPartyGroup
ReissueVerificationStatementChangeOfSecuredPartyGroup / VerificationStatementChangeOfSecuredPartyGroupType
VerificationStatementChangeOfSecuredPartyGroupSingle
ReissueVerificationStatementChangeOfSecuredPartyGroupSingle / VerificationStatementChangeOfSecuredPartyGroupSingleType
RegistrationTokenIssued / RegistrationTokenIssuedType
RegistrationTokenReset / RegistrationTokenResetType
RegistrationTokensReset / RegistrationTokensResetType
SecuredPartyGroupAccessCodeIssued / SecuredPartyGroupAccessCodeIssuedType
SecuredPartyGroupAccessCodeReset / SecuredPartyGroupAccessCodeResetType
SecuredPartyGroupAccessCodeChanged / SecuredPartyGroupAccessCodeChangedType
SecuredPartyGroupNumber / SecuredPartyGroupNumberType
CriticalNotice / CriticalNoticeType

Each of these datatypes is described below.

Note on Verification Statements in the B2G Mailbox

A number of the Notification Types are for Verification Statements. Messages for these Notification Types will always contain a PDF version of the Verification Statement.

Verification Statement messages also contain the content of the Verification Statement as XML in the Message element. This allows the B2G Account Customer’s application to process the data in the Verification Statement.

If a Verification Statement is reissued, exactly the same PDF file that was originally issued is provided in the B2G Mailbox. Exactly the same XML that was originally provided will also be provided if a Verification Statement is reissued. Therefore the same XML datatype is used for the message content for both the original issue and the reissue of a Verification Statement. The B2G Account Customer can determine from the Notification Type whether a Verification Statement in their B2G Mailbox is the original issue of the Verification Statement or a result of a request to reissue the Verification Statement.

If the B2G Account Customer wants to present the data in the Verification Statement to a user, the presentation of the data must be in an approved form. The document “PPSR - 22.4.1.2 - Graphic Design - Verification Statements” is the definitive source of Verification Statement data items and should be read in conjunction with this document.

3.1Common Notification Message Classes

3.1.1NotificationMessageBase

NotificationMessageBase is the base class for all B2G Mailbox Messages. This class provides fields that are common to all B2G Mailbox Messages.

Class / Req. / Element / Type / Notes
NotificationMessageBase / 1..1 / Environment / string(50) / The PPSR system environment (e.g. Production, Discovery) from which the message has been sent. See the document “PPSR - 7.6.6.3 - B2G Interface Specification”.

3.2Common Verification Statement Classes

The following classes are used by multiple Verification Statements.

3.2.1CollateralRegistrationForVerificationStatement

Class / Req. / Element / Type / Notes
CollateralRegistrationForVerificationStatement / 1..1 / RegistrationDetails / RegistrationDetails / The registration details for the registration.
See section 3.2.2RegistrationDetails.
0..* / Grantors / List<Grantor> / The Grantors for the registration.
See section 3.2.7Grantor.
1..1 / CollateralDetails / CollateralDetails / The collateral details for the registration.
See section 3.2.3CollateralDetails.
1..1 / SecuredParties / List<SecuredPartyWithVerificationStatus> / The Secured Parties for the registration.
See section 3.2.5SecuredPartyWithVerificationStatus.
1..1 / AddressForService / AddressForService / The Address for Service for the registration.
See section 3.2.8AddressForService.
0..1 / NevdisVerification / NevdisData / If the collateral is for the Collateral Class of Motor Vehicle and is being described by a Serial Number type of VIN or Chassis Number, and NEVDIS has been called, this will contain the data retrieved from NEVDIS.
See section 3.2.13NevdisDatafor details of the NEVDIS data.

3.2.2RegistrationDetails

Class / Req. / Element / Type / Notes
RegistrationDetails / 1..1 / RegistrationNumber / string(20) / The Registration Number of the registration.
1..1 / ChangeNumber / long / The Change Number of the version of the registration after the event for which the Verification Statement is produced.
0..1 / EarlierRegistrationNumber / string(20) / The Registration Number of an earlier registration where the earlier registration relates to the same security interest.
1..1 / RegistrationKind / string(200) / The RegistrationKind of the registration.
The primary purpose of the PPSR is to allow for registration of collateral that is subject to a security interest. However, existing registers that are replaced by PPSR (such as state-based registers of encumbered vehicles) allow for additional interests in collateral to be registered. For example, police forces registering hoon liens. The majority of registrations in PPSR will be for security interests, however PPSR also allows for registration of other kinds of interest.
0..1 / GivingOfNoticeIdentifier / string(50) / An optional identifier that a Secured Party Group has specified for the registration.
1..1 / RegistrationStartTime / dateTime / The date and time the registration was first registered in PPSR.
0..1 / RegistrationEndTime / dateTime / The date and time that the registration will expire. This will be null if the end time of the registration is not stated.
1..1 / RegistrationChangeTime / dateTime / The date and time that the registration was amended.
The date and time that the registration was last changed, which could be the time the registration was created, amended, discharged, removed, transferred, address for service changed.
1..1 / IsSubordinate / boolean / Whether the registration is subordinate to another security interest. A value of “true” indicates the registration is subordinate to another security interest. A value of “false” indicates that whether or not the registration is subordinate to another security interest is not stated.
1..1 / IsTransitional / boolean / Indicates if the registration is for an interest that existed prior to the registration commencement time of PPSR.
1..1 / IsMigrated / boolean / Indicates if the registration was migrated from an existing register.
0..1 / MigrationDetail / MigrationDetail / If the registration is a migrated registration (IsMigrated will be “true”), this will contain further details that relate to migrated registrations.
See section 3.2.10MigrationDetail.