Output File Format - NZ Transport Agency
Output File Formats - Vehicle Records
Output file Vehicle records are structured as follows:
Entries in the type column have the following meaning
- 9 = numeric digits from 0 to 9
- X = any characters
Vehicle records are placed in the output file after the header record. For each vehicle that was queried, a separate vehicle record is given.
A vehicle record will be present even if the query on that vehicle was unsuccessful, in which case one or more error codes will be present in the ‘Message Code’ fields.
A vehicle may have more than one message that is appropriate. Up to three message codes can be returned.
Vehicle records have two Data Output Options:
- Basic Output.
- Extended Output.
Header Record
|Field |Type |Length |Values/Comment |
|Record Type |9 |1 |Value e.g. value 2 “Current Details” |
|Account No. |9 |9 |Motochek account I-SID |
|Account Name |X |56 | |
|Date Query Received |9 |8 |ddmmccyy format |
|Time Query Received |9 |4 |hhmm format |
|Date Query Processed |9 |8 |ddmmccyy format |
|Time Query Processed |9 |4 |hhmm format |
|Message Code |9 |2 |Blank if no error or exception |
|Message Text |x |164 |Blank if no second error or exception |
All transactions shall have the following standard details.
|Field |Type |Length |Values/Comment |
|Record Type |9 |1 |“2” for “Current details” query |
| | | |“3” for “Registered person as-at” query |
|Plate No. |X |6 | |
|Replacement Plate |X |6 |Plate has changed and this is now the plate registered against |
| | | |the vehicle |
| | | | |
| | | |Note: not required/returned for Stolen Vehicle or Confirm |
| | | |registered person queries |
|VIN |X |17 | |
|Message Code 1 |9 |2 |00” if no error or exception |
|Message Code 2 |9 |2 |00” if no second error or exception |
|Message Code 3 |9 |2 |00” if no third error or exception |
|Year Of Manufacture |9 |4 | |
|Make |X |20 |Note: not required/returned for Stolen Vehicle or Confirm |
| | | |registered person queries |
|Model |X |20 |Note: not required/returned for Stolen Vehicle or Confirm |
| | | |registered person queries |
|Submodel |X |20 |Note: not required/returned for Stolen Vehicle or Confirm |
| | | |registered person queries |
|Date Query Processed |9 |8 |DDMMCCYY format |
Detail Record Basic Option - Applies to Current details and Registered person as-at-date transactions only
|Field |Type |Length |Values/Comment |
|Registered Person Name |X |56 |for “Enforcement” access, this is the registered person at the |
| | | |“date of offence”; |
| | | |for “Authorised” access, this is always the current registered |
| | | |person |
|Trading As/Representing |X |56 |ditto |
|Joint Owner Indicator |X |1 |"Y", "N" |
|Sex/Company |X |1 |See Codes - Table - SEXT |
|Date Of Birth Of Registered Person*** |9 |8 |DDMMCCYY format |
| | | |Set to blanks for “Authorised/Standard” access |
|Physical Address Property Name |X |35 |Physical address for the person in the ‘Registered Person Name’ |
| | | |field |
|Physical Address Flat Floor Number |X |8 |Ditto |
|Physical Address Street Number |X |8 |Ditto |
|Physical Address Street Name |X |40 |Ditto |
|Physical Address RD Number |X |7 |Ditto |
|Physical Address Suburb |X |35 |Ditto |
|Physical Address Town |X |40 |Ditto |
|Physical Address Postcode |X |8 |Ditto |
|Mailing Address Property Name |X |35 |Mailing address for the person in the ‘Registered Person Name’ |
| | | |field |
|Mailing Address Flat Floor Name |X |8 |Ditto |
|Mailing Address Street Number |X |8 |Ditto |
|Mailing Address Street Name |X |40 |Ditto |
|Mailing Address Box Bag Rd |X |3 |Ditto |
|Mailing Address Box Bag Number |X |7 |Ditto |
|Mailing Address RD Number |X |7 |Ditto |
|Mailing Address Suburb |X |35 |Ditto |
|Mailing Address Town |X |40 |Ditto |
|Mailing Address Postcode |X |8 |Ditto |
|Gone No Address |X |1 |"Y", "N" |
|Ownership Status |X |1 |See Codes - Table - OWNS |
|Ticket Number |X |6 |Enforcement users only |
|Query Date For "Owner As At" |9 |8 |DDMMCCYY format |
| | | |Date of offence for Enforcement queries |
|Acquisition Date (Ownership) |9 |8 |DDMMCCYY format |
|Registration Status |X |1 |See Codes - Table - REGS |
|Licence Expiry Date |9 |8 |DDMMCCYY format |
|Licence Type |X |1 |See Codes - Table - LICT |
|Date Of Issue For Latest Licence |9 |8 |DDMMCCYY format |
|Time Of Issue For Latest Licence |9 |4 |hhmm 24 hour format (hour and minute) |
|Continuous Licence |X |1 |“Y”, “N” |
|Main Colour |X |6 | |
|Second Colour |X |6 | |
|CC Rating |9 |5 | |
|Body Style |X |3 |e.g. “HA” = “Hatchback” |
|Subject To WOF |X |1 |“Y”, “N” |
| | | |Depends on fee code and weight |
|Date Of Latest WOF Inspection |9 |8 |DDMMCCYY format |
|Result Of Latest WOF Inspection |X |1 | |
|Expiry Date Of Last Successful WOF |9 |8 |DDMMCCYY format |
|Subject To COF Inspection |X |1 |“Y”, “N” |
| | | |Depends on fee code and weight |
|Date Of Latest COF Inspection |9 |8 |DDMMCCYY format |
|Result Of Latest COF Inspection |X |1 | |
|Expiry Date Of Last Successful COF |9 |8 |DDMMCCYY format |
|Subject To RUC |X |1 |“Y”, “N”. |
| | | |(Either Fuel Type = “02” or GVM >= 3500 |
|Imported Damaged |X |1 |“Y”, “N”. |
| | | |Depends on if the vehicle has been imported damaged. |
|Cancellation reason code |X |1 |See Codes – Table - CRES |
|Registered Overseas |X |1 |“Y” or “N” |
| | | |Depends on if the vehicle has been 1st registered overseas. |
|Day of first Registration Overseas |9 |2 |This may contain a zero, or a valid day. |
|Month of first Registration Overseas |9 |2 |This may contain a zero, or a valid month number. |
|Year of first Registration Overseas |9 |4 |CCYY format |
| | | |This may contain a zero, or a valid year. |
|Inspection Agent |X |56 |Inspection agent Trading name, for particular enforcement |
| | | |queries. |
Extended Format Option - Applies to Current details and Registered person as-at-date transactions only.
The Extended Vehicle record Output is structured as follows and will be added to the end of the basic output if the query has been requested with the "Extended Data" option.
|Field |Type |Length |Values/Comment |
|Joint Owner Name No. 1 |X |56 |for “Enforcement” access, this is the Joint Registered person |
| | | |at the “date of offence”; |
| | | |for “Authorised” access, this is always the current Joint |
| | | |Registered person |
|Joint Owner Name No. 2 |X |56 |ditto |
|Joint Owner Name No. 3 |X |56 |ditto |
|Fleet/Lease Ownership |X |1 | F(leet), L(ease), blank |
|Fleet/Lease Owner |X |56 | |
|Chassis No. |X |17 | |
|Reported Stolen |X |1 |“Y”, “N” |
|Date Reported Stolen |9 |8 |Reserved for future use |
|Reliable Odometer |X |1 |“Y”, “N” |
|Power |9 |3 |(kW).Show blank for 0. |
|Country Of Origin |X |3 |See Codes - Table - CTRY |
|Previous Country Of Registration |X |3 |See Codes - Table - CTRY |
|Assembly Type |9 |1 |See Codes - Table - ASSM |
|Engine No. |X |17 | |
|Gross Vehicle Mass |9 |6 |(Kg). Show blank for 3499, 3501, 5999. |
|No. Of Seats |9 |3 | |
|Fuel Type |9 |2 |See Codes - Table - FUEL |
|Alternative Fuel Type |9 |2 |See Codes - Table - FUEL |
|Date of first Registration In NZ |9 |8 |DDMMCCYY format |
|Cause Of Latest Registration |X |1 |“New”, “Used”, “Reregistered” |
|Date of Latest Registration |9 |8 |DDMMCCYY format |
|Plate Type |X |2 |See Codes - Table - PLTY |
|Vehicle Type |9 |2 |See Codes - Table - VTYP |
|Vehicle Usage |9 |2 |See Codes - Table - USGE |
|Latest Odometer Reading |9 |6 | |
|Odometer Unit |X |1 | |
|Date Of Odometer Reading |9 |8 |DDMMCCYY format |
|Odometer Source |X |2 |See Codes – Table - ODSC |
| | | |Data in remaining fields not given for vehicle types 01, 07, |
| | | |11, 12 (i.e. they are only shown for heavy vehicles) |
|Maximum Rated Towed Mass For Unbraked Trailer|9 |5 |(Kg) |
|Maximum Rated Towed Mass For Braked Trailer |9 |5 |(Kg) |
|Tare Weight |9 |6 |(Kg) |
|No. Of Axles |9 |1 | |
|Axle Type |X |2 |See Codes - Table - AXLE |
|Wheelbase |9 |4 | |
|Front Axle Group Rating |9 |5 | |
|Rear Axle Group Rating |9 |5 | |
Latest RUC Licence and RUC Licence History Transactions
The following applies to RUC transactions only, for the RUC Licence history query the latest 10 records will be returned repeating same fields as below for each record.
Note: Extended format is not available for these transactions.
|Field |Type |Length |Values/Comment |
|RUC Licence Type |X |1 |D(Distance) licence |
| | | |T(Time) licence |
| | | |S(Supplementary) licence |
|RUC Vehicle Type |9 |3 | |
|RUC Licence Issue Date |9 |8 |DDMMCCYY format |
|RUC Licence Start |9 |8 |If distance licence, start distance kms (or miles if odometer or |
| | | |hubodometer is miles) |
| | | |If time licence, start date in format ddmmccyy. |
|RUC Licence End |9 |8 |If distance licence, end distance kms (or miles if odometer or |
| | | |hubodometer is miles) |
| | | |If time licence, expiry date in format ddmmccyy. |
|Hubodometer Make |X |2 | |
|Hubodometer Serial Number |X |10 | |
|Odometer Unit |X |1 |K (kilometres) |
| | | |M (Miles) |
| | | |N (non-applicable) or |
| | | |space |
|RUC Vehicle Licence Weight |9 |3 |(tonnes) |
Vehicle usage history - The following applies to the vehicle usage history transaction only, the detail will repeat up to maximum 100 times
|Field |Type |Length |Values/Comment |
|Vehicle Usage |9 |2 |See codes table - USGE |
|Effective Date |9 |8 | |
|Ticket Number |X |6 |Returned as submitted in request (optional used for Enforcement |
| | | |users) |
Confirm registered person
|Field |Type |Length |Values/Comment |
|Last Name |X |56 |As supplied in the request |
|First Name |X |56 |As supplied in the request |
|Organisation Name |X |56 |As supplied in the request |
|Date of birth |9 |8 |As supplied in the request |
|Driver licence |X |8 |As supplied in the request |
|Confirmed |X |1 |Y/N |
|Ticket Number |X |6 |Returned as submitted in request (optional used for Enforcement |
| | | |users) |
Check Vehicle Stolen Transaction
|Field |Type |Length |Values/Comment |
|Reported Stolen |X |1 |“Y”, “N” |
|Ticket Number |X |6 |Returned as submitted in request (optional used for Enforcement |
| | | |users) |
Error Messages Exceptions and Special Actions
Messages for errors and exception conditions found during processing will be placed in the output file in place of a result, as follows.
Header Errors
Vehicle Errors and Exceptions
Header Errors
Along with a text message in the ‘Message Text’ field, a numeric message code will be given in the ‘Message Code’ field. When the error pertains to all the output, only a header record will be returned (e.g. “Empty query file”).
|Message Code |Message Text |
|11 |Invalid file format |
|12 |Invalid type |
|13 |Input file empty |
|46 |Unknown Account Number |
|51 |No Active Bank Account found |
|62 |Identity is not active |
|90 |Transaction not implemented |
|91 |Transaction Type not available in text format |
|98 |You are not authorised to access |
Vehicle Error Messages and Exceptions
Vehicle error messages and exceptions are listed in the following table –
When the error or exception condition pertains to a particular vehicle query, one or more codes are returned in the ‘Message Code’ fields.
Sometimes, information about a vehicle can still be given.
If no information can be given then one of the plate no. or VIN will always be returned to match whichever value was given in the corresponding input record. i.e. if a plate number was specified this will be returned with the message code but no VIN, or, if a VIN was specified then this will be returned in the ‘VIN’ field but no plate number.
|Message Code |Error/Exception Condition |
|21 |Plate/VIN invalid |
|22 |No Information |
|23 |Apply to TRC in writing |
|24 |Registration cancelled |
|25 |VIN has never been registered |
|26 |Plate has changed |
|27 |As At Date required |
|28 |Multiple owners as at requested date |
|29 |No owner recorded for requested date |
|31 |Not currently registered |
|32 |Plate not attached at requested date |
|41 |No licence found |
|42 |As At Date must not be greater than today |
|43 |Invalid Date |
|44 |Plate has not been used |
|45 |Unknown query type |
|47 |Motochek User Details not found |
|53 |No Plate or VIN supplied |
|55 |Invalid Cert Type |
|56 |Trade plate – not valid for MR32 |
|58 |Invalid Suburb/Town combo |
|61 |More than 20 previous plates |
|62 |Account Inactive |
|63 |Plate was also attached to another vehicle at query date |
|64 |Trade Plate - not registered against a vehicle |
|66 |Invalid Date of Birth |
|71 |Vehicle is not subject to RUC. |
|72 |No Odometer History records |
|73 |Duplicate Request |
|87 |No Vehicle Usage History found |
|88 |Registration must be active |
|89 |No RUC Licences found |
|90 |Please supply either Last Name or Organisation Name not both |
|92 |First Name not supplied |
|93 |Last Name or Organisation Name not supplied |
|95 |Enter PLATE or VIN – not both |
|96 |Trader/Plate Relationship record not found |
|97 |Registration Cancelled/Lapsed |
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related download
- chapter 9 code tables
- cprs setup guide veterans affairs
- this is a text file named readme
- ece 4110 internetwork programming
- data innovation instructional implementation guide
- ny edi 997 functional acknowledgment
- click on the trmserv icon and a trmserv
- output file format nz transport agency
- introduction small business administration
Related searches
- file format example
- pdf file format basic structure
- all file format opener
- office file format converter
- best file format for documents
- pdf file format tutorial
- pdf file format explained
- sequence file format in hive
- microsoft file format crossword
- printable file format crossword
- microsoft file format converter download
- file format converter free download