Electronic reporting specification - ATO Let`s Talk

Transcription

SPECIFICATION
SOFTWARE
DEVELOPERS
DECEMBER 2015
UNCLASSIFIED
FORMAT
AUDIENCE
DATE
CLASSIFICATION
Electronic
reporting
specification
Business transactions made through payment systems (BTTPS)
report version 1.0.0
UNCLASSIFIED
For further information or
questions call 13 28 66
UNCLASSIFIED
ELECTRONIC REPORTING SPECIFICATION – BUSINESS
TRANSACTIONS MADE THROUGH PAYMENT SYSTEMS REPORT
ACRONYMS
Acronym
Expanded
ABN
Australian business number
ABR
Australian business register
ACN
Australian company number
ATO
Australian Taxation Office
UNCLASSIFIED
I
UNCLASSIFIED
DEFINITIONS
Term
Reporting
party
Description
The organisation or entity that is providing the electronic sales facility and
thereby has the reporting obligation to the ATO.
Reporting parties can include financial institutions, third party payment
processors and specialised payment providers.
Intermediary
The supplier or organisation sending the data to the Australian Taxation
Office (ATO).
Business
A business in Australia who collect payments for goods and services
through electronic payment systems. This includes payments made through;
 Financial Institutions
- Merchant acquiring system
- BPAY
 Specialised payment providers such as PayPal and Third Party Payment
Processor
- Merchant payments
- BPAY payments
- Direct Debit payments
- PayPal
UNCLASSIFIED
II
UNCLASSIFIED
TABLE OF CONTENTS
1 Introduction ............................................................................................................................ 1
About Business transactions made through payment systems ............................................. 1
Who should use this specification ......................................................................................... 1
Lodging via the internet ........................................................................................................ 1
2 Legal requirements................................................................................................................. 2
Reporting obligations ............................................................................................................ 2
Extension of time to lodge..................................................................................................... 2
Privacy.................................................................................................................................. 3
3 Reporting procedures ............................................................................................................. 4
Reporting for the first time..................................................................................................... 4
Test facility ........................................................................................................................... 4
Accessing the test facility ................................................................................................... 5
Reporting electronically ........................................................................................................ 5
Getting started ................................................................................................................... 6
Backup of data...................................................................................................................... 6
4 Data file format ....................................................................................................................... 7
File structure diagram ........................................................................................................... 7
File content ........................................................................................................................... 8
Sort order of the report data file ............................................................................................ 8
File structure example .......................................................................................................... 9
5 Record specifications ............................................................................................................10
File name.............................................................................................................................10
CR, LF and EOF markers ..................................................................................................10
Description of terms used in data record specifications .......................................................12
Intermediary data record ......................................................................................................15
Reporting party identity data record .....................................................................................16
Business data record ...........................................................................................................17
Transaction Period summary data record ............................................................................18
File total data record ............................................................................................................18
6 Data field definitions and validation rules...............................................................................19
Reporting address details ....................................................................................................19
Reporting of name fields ......................................................................................................20
Currency for reporting ..........................................................................................................20
Field definitions and edit rules .............................................................................................21
7 Example of data file structure ................................................................................................31
Intermediary data record ......................................................................................................31
Reporting party identity data record .....................................................................................32
Business data record ...........................................................................................................33
Transaction summary data record .......................................................................................34
File total data record ............................................................................................................34
8 Amendments .........................................................................................................................35
Reporting to the ATO ...........................................................................................................35
9 Algorithms .............................................................................................................................36
ABN algorithm .....................................................................................................................36
ABN look up ........................................................................................................................36
UNCLASSIFIED
III
UNCLASSIFIED
10 Currency codes - ISO 4217 .................................................................................................37
Currency, fund and precious metal codes .........................................................................37
11 More information .................................................................................................................45
Electronic specifications ....................................................................................................45
Other enquiries .................................................................................................................45
Software developers homepage ........................................................................................45
UNCLASSIFIED
IV
UNCLASSIFIED
1 INTRODUCTION
ABOUT BUSINESS TRANSACTIONS MADE THROUGH PAYMENT SYSTEMS
The Australian Taxation Office (ATO) requests and collects data from various financial
institutions, PayPal and specialised payment providers relating to electronic sales of goods and
services made by Australian businesses. The data will be electronically matched with data held
by the ATO to identify businesses that are non-compliant with registration, reporting, lodgment
and payment obligations under taxation law.
The information provided to the ATO will improve the pre-filling of tax returns and making tax
time simpler for taxpayers. The measure will also improve compliance and provide a level
playing field for Australian taxpayers by enabling the ATO to expand its data matching with third
party information.
WHO SHOULD USE THIS SPECIFICATION
This specification is to be used in the development of software for the lodgment of electronic
Business transactions made through payment systems (BTTPS) for the 2016-17 and
subsequent financial years.
This specification is not intended to, nor does it provide a guide to the relevant legislation.
LODGING VIA THE INTERNET
Suppliers lodge the BTTPS via the internet using the Business portal, Tax agent portal or BAS
agent portal. Electronic lodgment enables suppliers to:
 reduce paperwork,
 provide a secure way for reports to be lodged,
 provide an online receipt when the report is lodged,
 ensure that all of the necessary fields to lodge the report have been completed, via in-built
checks, and
 be available 24 hours a day, 7 days a week.
UNCLASSIFIED
1
UNCLASSIFIED
2 LEGAL REQUIREMENTS
REPORTING OBLIGATIONS
Under Taxation Administration Act 1953, details of business identity and transaction data of all
business transactions made through payment systems must be reported to the ATO for the
year being reported.
Where transaction data is amended or additional transactions (for the same financial year) are
made after the original report has been supplied to the ATO, additional reports containing this
information are to be supplied to the ATO in accordance with these specifications. See section
8 Amendments.
EXTENSION OF TIME TO LODGE
If you are unable to lodge a BTTPS by the specified due date, you may apply before the report
due date for an extension of time to lodge. If additional time is required to lodge the BTTPS
electronically, phone 13 28 66.
Confirmations of extensions granted and the expected lodgment date which is set at the time
will be provided by email. Generally, further extensions after the set date will not be granted.
UNCLASSIFIED
2
UNCLASSIFIED
PRIVACY
The Privacy Act 1988 limits the collection, storage, use and disclosure of personal information
about individuals by the ATO, other Commonwealth Government departments and agencies.
New private sector provisions in the Privacy Act also regulate the way many private sector
organisations collect, use, secure and disclose personal information. The private sector
provisions aim to give people greater control over the way information about them is handled in
the private sector by requiring organisations to comply with ten national privacy principles.
These principles give individuals the right to know what information an organisation holds about
them and a right to correct that information if it is wrong.
The Privacy Commissioner’s Guidelines to the Australian Privacy Principles and other relevant
information sheets are available at www.oaic.gov.au.
It is the responsibility of private sector organisations to obtain their own advice on the effect of
privacy law, including the Australian Privacy Principles on their operations.
REGISTRATION WITH THE TAX PRACTITIONERS BOARD
Under the Tax Agent Services Act 2009 (TASA), entities that provide a tax agent service for a
fee or reward are required to be registered with the Tax Practitioners Board (TPB). The TPB
has released an information sheet to assist software providers who provide tax related software
systems to understand the operation and impact of the tax agent services regime. In particular,
the information sheet:


provides guidance on which situations may or may not require registration with the TPB as
a tax or BAS agent; and
outlines procedures and processes that software providers need to have in place (where
relevant) to ensure that they are not regarded as providing a tax agent service.
Therefore it is important for all software providers to be aware of the requirements of the TASA
and, if appropriate, comply with the obligations that exist within it.
For more information go to the Tax practitioner board website
UNCLASSIFIED
3
UNCLASSIFIED
3 REPORTING PROCEDURES
REPORTING FOR THE FIRST TIME
Software developers developing reporting software for the electronic generation of the BTTPS
should refer to this specification when developing the application. Information is also available
on the Software developer’s homepage at http://softwaredevelopers.ato.gov.au.
The Software developers homepage is maintained by the ATO on behalf of, and in consultation
with, the software development industry and business advisers. It facilitates the development
and listing of software which may assist businesses to meet their tax obligations.
Commercial software developers are required to register on the Software developers
homepage if they wish to list their products. Developers who do not wish to list products do not
need to register in order to access information. Subscribing for email updates is recommended
so software developers can be notified of significant issues.
TEST FACILITY
A test facility is provided to software developers to self-test the contents of test files. It is
accessed using a user ID and password.
The test facility supports testing of files that comply with the latest versions of electronic
reporting specifications. It cannot be used to make lodgments to the ATO.
The same validation process will be applied to files checked in the test facility and files that will
be lodged via the ATO portals.
To test a file:
1 Prepare the files using software developed in accordance with the published reporting
specifications.
2 Log in to the test facility using the user ID and password.
3 Select Send data located in the left hand menu.
4 Select Browse to locate the file and then select OK.
5 Select Send to submit the file to the ATO, where it will be checked for format compatibility
and data quality.
6 Select Transaction history to confirm the file has been uploaded. This can be done while
the file is being validated for errors and warnings.
7 When the validation is complete select Download from the Transaction history screen to
download the validation report confirming the data is in a valid format or detailing any errors
found.
UNCLASSIFIED
4
UNCLASSIFIED
Accessing the test facility
To obtain a user ID and password for the test facility, complete the File transfer test facility
registration form at http://softwaredevelopers.ato.gov.au/bulktest. The test facility can be
accessed from the same location.


For support in the use of the test facility, including password reset:
email ATOBulkDataTransfer@ato.gov.au, or
phone (02) 6216 4004 between 8.30am and 4.30pm, Monday to Friday AEST.
REPORTING ELECTRONICALLY
Suppliers are able to lodge the BTTPS electronically via the Business portal, Tax agent portal
or BAS agent portal where the data file has been prepared and stored locally.
On screen confirmation will be provided once the file has been sent. The ATO will perform data
quality and format compatibility checks after the data file is sent. If the user selects the email
acknowledgement option in the Lodge file process, an email will be provided confirming that the
files have been successfully lodged with the ATO. A validation report will be available in the
portal to advise if the report was successfully validated or if there are any problems.
The security features of the portals address the most commonly held concerns over internetbased electronic dealings, namely:
 authentication (the sender is who they say they are),
 confidentiality (the communication can only be read by the intended recipient),
 integrity (the transmission cannot be altered without detection while in transit), and
 non-repudiation (there is a record of the transmission and content).
UNCLASSIFIED
5
UNCLASSIFIED
Getting started
Access to the portals requires:
 an Australian business number (ABN) – apply online at www.abr.gov.au, and
 an AUSkey – register online at www.auskey.abr.gov.au.
For more information about AUSkey go to: www.ato.gov.au/onlineservices.
AUSkey is an online security credential used to protect the client’s security and privacy when
using ATO online services.
Every person associated with the business who wants to deal with the ATO online on behalf of
that ABN will need an AUSkey. Users can have full or limited access to information, which can
be changed anytime by using Access Manager in the portal.
The portals can be accessed from the online services box in the right hand menu of the ATO
website at www.ato.gov.au.
BACKUP OF DATA
It is the responsibility of the reporting party to keep effective records as part of their tax
reporting obligations. A backup copy of the data sent to the ATO should be kept by either the
reporting party or the intermediary, so that the report can be re–submitted if necessary.
UNCLASSIFIED
6
UNCLASSIFIED
4 DATA FILE FORMAT
FILE STRUCTURE DIAGRAM
Intermediary
data record
1-1
Reporting
Party data
record
1-M
Business
data record
1-M
Transaction
Period Summary
data record
1-M
File total
data record
1-1
Key:
1-1
Record must occur once and only once
1-M
Record must occur once, but may occur many times
Physical record type
UNCLASSIFIED
7
UNCLASSIFIED
FILE CONTENT
The Intermediary data record (page 15) must be the first record on each data file. It must be
reported once only and must be followed directly by the first Reporting party identity data
record.
The first Reporting party identity data record (page 16) contains information about the entity
reporting the data. It must appear as the second record on the data file and is to be followed by
the Business data record.
The Business data record (page 17) contains information about the business being reported on.
It must immediately follow each Reporting party identity data record.
The Transaction period summary data record (page 18) contains information about the monthly
transactions per business. The first Transaction period summary data record must immediately
follow the relevant Business data record. This record must be repeated for each month being
reported and each currency type being reported.
The File total data record (page 18) must be the last record on the file (dataset) to indicate the
end of the data. It contains the total number of records in the data file
SORT ORDER OF THE REPORT DATA FILE
The sort order of the report data file must be as follows:
 the Intermediary data record
 then the Reporting party identity data record
 then the Business data record
 then the Transaction period summary data record
If there is another report from a different reporting party to be provided on the same file, then
Reporting party, Business and Transaction period summary data record(s) for the next entity
must follow the last Transaction period summary data record.
If the reporting party is reporting multiple business transaction summary data on the same file,
then the Business and Transaction period summary data record(s) should be repeated after the
previous Business data record.
Transaction period summary data records must be repeated per business for each separate
month reported and each separate currency being reported.

the File total data record must be placed at the end of the file
UNCLASSIFIED
8
UNCLASSIFIED
FILE STRUCTURE EXAMPLE
Intermediary data record
Reporting party identity data record
(Provider A)
Business data record 1
Transaction period summary data record 1
(Provider B)
Repeat the above structure - from Reporting party identity data record - for other Business’
being reported on the same file.
File total data record
UNCLASSIFIED
9
UNCLASSIFIED
5 RECORD SPECIFICATIONS
FILE NAME
To assist with easy identification of the BTTPS file it is recommended that it be given a
meaningful name and must only contain characters from the range A-Z, 0-9, space,
apostrophe, hyphen and full stop.
CR, LF and EOF markers
The ATO prefers data to be supplied without carriage–return (CR), linefeed (LF) or end–of–file
(EOF) markers. However, if these characters cannot be removed, the following rules apply:
EOF (if supplied)
(a)
one and only one EOF character is to be supplied and must be the last character of the
file.
(b)
if CR/LF characters are used, one EOF character may also be supplied as the last
character of the file. In this case, the last three characters of the file will be CR/LF/EOF
(in that order).
CR/LF (if supplied)
(c)
if CR/LF characters are supplied, they must always occur together as a coupled pair
and be on the end of each record, or
(d)
the CR/LF coupled pair of characters may occur on the last record as the last two
characters only. In this case, all preceding records must not have CR/LF characters. A
special case can occur if only one coupled pair CR/LF is used in conjunction with an
EOF character where the last three characters will be CR/LF/EOF (see (b) above).
CR/LF and EOF characters are not part of the data supplied and, if used, must be additional
characters to the record length.
Record length (character position 1-4) in all records must be set to 1400.
A simple check can be used to ensure that the record length of a fixed length file is correct. The
length of the file supplied to the ATO must be a multiple of the fixed record length.
For example, for files that do not contain CR/LF at the end of each record:
BIDR file record length is 1400 characters
Length of the file = 16800
16800/1400 = 12 and 0 remainder
Therefore the file is OK
If length of the file BIDR = 16802
16802/1400 = 12 and 2 remainder
Therefore, there is an error in the file
UNCLASSIFIED
10
UNCLASSIFIED
For example, for files that contain CR/LF at the end of each record. This is only a check of the
file length and the 1402 characters must only be used for division. All record lengths in the data
must be 1400.
BIDR file record length is 1402 characters (record 1400 + CR/LF 2)
Length of the file =16824
16824/1402 = 12 and 0 remainder
Therefore the file is OK
If length of the file = 14022
14022/1402 = 10 and 2 remainder
Therefore, there is an error in the file
If an error in the division occurs, the file must be corrected before it is sent to the ATO.
Examples of errors that may occur:
 One or more of the records is longer or shorter than the fixed length of 1400 characters
 There are characters at the end of the file that need to be removed. For example:
– an extra end– of– file marker
– an additional CR/LF (if providing CR/LF there should only be one CR/LF at the end of
the file) (see above), or
– binary zeros.
UNCLASSIFIED
11
UNCLASSIFIED
DESCRIPTION OF TERMS USED IN DATA RECORD SPECIFICATIONS
The following tables show data records and their elements. The tables contain the following
standard columns:
Character position – the start and end position of the field in the record.
Field length – the length of the data item in bytes.
Field format – the format type of the field.
A
is alphabetic (A-Z) – one byte per character. Alphabetic fields must be left justified and
characters not used must be blank filled.
For example, SMITH in a ten character field would be reported as SMITHbbbbb
The character b is used to indicate blanks.
AN
is alphanumeric –one byte per character. Alphanumeric fields must be left justified and
characters not used must be blank filled.
For example, 10 FIRST STREET in a 20 character alphanumeric field would be
reported as 10bFIRSTbSTREETbbbbb
The character b is used above to indicate blanks.
In addition, unless stated elsewhere in this specification, all other standard keyboard
characters are accepted in alphanumeric fields.
D
is a date in CCYYMMDD ISO 8601 format. One byte per digit. If the day or month
components are less than 10, insert a leading zero.
For example:
 26 March 2016 would be reported as 20160326
 9 November 2015 would be reported as 20151109
If the date is mandatory it must be a valid date, otherwise see date under the optional
field type.
DT
is a date time in CCYY-MM-DDThh:mm:ss.ffTZD ISO 8601 format. If the day or month
components are less than 10, insert a leading zero. Times are expressed in local time,
together with a time zone offset in hours and minutes.
CCYY
MM
DD
T
= four-digit year followed by a hyphen
= two-digit month followed by a hyphen (01-=January, etc.)
= two-digit day of month (01 through 31)
= T indicates the beginning of the time element, as specified in ISO 8601
UNCLASSIFIED
12
UNCLASSIFIED
hh
= two digits of hour followed by a colon (00 through 23) (am/pm NOT allowed)
mm
= two digits of minute followed by a colon (00 through 59)
ss
= two digits of second followed by a fullstop (00 through 59)
ff
= two digits representing a decimal fraction of a second
TZD = time zone designator (+hh:mm or -hh:mm)
Exactly the components shown in the example below must be present with the specific
punctuation.
For example:
 5 November, 2015, 8:15:30.40 am, AU Eastern Standard Time would be reported
as 2015-11-05T08:15:30.40+10:00

18 January, 2015, 1:30:00.00 pm, AU Eastern Standard Time would be reported
as 2015-01-18T13:30:00.00+10:00
If the date is mandatory it must be a valid date, otherwise see date under the optional
field type on the next page.
N
is numeric (0-9) – one byte per digit. Numeric fields must be right justified and zero
filled.
For example, 123456789 in an 11 digit field would be reported as 00123456789.
All whole dollar amount fields are to be reported as dollar fields and must not contain
decimal points, commas or other non-numeric characters (for example $+-). The
amount must be reported in whole dollars. If an amount includes cents, the cents must
be truncated (or disregarded).
NS
For example, in an 11 character numeric (dollar amount) field:
 $1234.99 would be reported as 00000001234
 $122.16 would be reported as 00000000122
 $567.00 would be reported as 00000000567, and
 $00.00 would be reported as 00000000000.

is numeric special (0–9 and blank) – one byte per character. Numeric special fields
must be right justified and characters not used must be blank filled.
All amount fields are to be reported as dollar fields and must not contain decimal points,
commas or other non–numeric characters (for example $+– ). The amount must be
reported in whole dollars.
For example, in a 13 character numeric (amount) field:
 $1234.99 would be reported as bbbbbbbbb1234 (the character b is used to indicate
blanks).
No entry in this field would be reported as blanks
UNCLASSIFIED
13
UNCLASSIFIED
Field type – codes used are:
M
Mandatory field that must be provided. For single character mandatory fields, a blank
(space) is NOT a valid value.
ALPHA: field must not start with a blank or be blank filled
ALPHANUMERIC: field must not start with a blank or be blank filled
NUMERIC: field must not start with a blank and may be zero filled
DATE: field must not be zero filled.
O
Optional field that must be made available by the software developer for the entity to
complete. Entities must complete the field if the data is available.
ALPHA: if not present, field must be blank filled
ALPHANUMERIC: if not present, field must be blank filled
NUMERIC: if not present, field must be zero filled
DATE: if not present, field must be zero filled.
C
Conditional field that must be made available by the software developer for the entity to
complete. Entities must complete the field as specified.
S
For use by the ATO. It must be blank filled and must not contain binary zeros.
Field name – a brief description of the field.
Reference number – the definition reference number. These definitions can be found in Data
field definitions and edit rules (page 19).
UNCLASSIFIED
14
UNCLASSIFIED
INTERMEDIARY DATA RECORD
Character
position
1-4
5-17
Field
Field
length format
4
N
Field
type
M
13
AN
M
10
AN
M
28-38
39-66
11
N
M
28
DT
M
67-82
83-282
283-332
333-334
335-349
350-387
388-425
426-452
16
200
50
2
15
38
38
AN
AN
AN
AN
AN
AN
AN
O
M
M
M
M
M
O
27
AN
M
453-455
456-459
460-479
480-555
556-1400
3
4
20
76
845
A
N
AN
AN
A
M
M
C
O
S
18-27
UNCLASSIFIED
Field name
Record length (=1400)
Record identifier
(=IDENTREGISTER)
Report specification version number
(=BTPSV001.0)
Date timestamp report created
(CCYY-MM-DDThh:mm:ss.ffTZD)
File reference
Name
Contact name
Phone number area code
Phone number
Street address line 1
Street address suburb, town or
locality
Street address state or territory
Street address postcode
Street address country
Email address
Filler
Reference
number
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
6.9
6.10
6.11
6.11
6.12
6.13
6.14
6.15
6.16
6.17
15
UNCLASSIFIED
REPORTING PARTY IDENTITY DATA RECORD
Character
position
1-4
5-8
9-16
Field
length
4
4
8
Field
format
N
A
D
Field
type
M
M
M
17-24
8
D
M
25-35
36-38
39-238
239-314
315-352
353-390
391-417
418-420
421-424
425-444
445-482
483-520
521-547
11
3
200
76
38
38
27
3
4
20
38
38
27
N
N
AN
AN
AN
AN
AN
A
N
AN
AN
AN
AN
M
M
M
O
M
O
M
M
M
C
M
O
M
548-550
551-554
555-574
575-612
613-614
615-630
631-706
3
4
20
38
2
16
76
A
N
AN
AN
AN
AN
AN
M
M
C
M
M
M
O
Record identifier (=RPDR)
Reporting period start date
(CCYYMMDD)
Reporting period end date
(CCYYMMDD)
Branch number
Registered name
Trading name
Street address suburb, town or locality
Postal address line 1
Postal address suburb, town or
locality
Postal address state or territory
Postal address postcode
Postal address country
Contact name
Phone number
Email address
707-786
787-1400
80
614
AN
A
M
S
Software product type
Filler
UNCLASSIFIED
Field name
Reference
number
6.1
6.18
6.19
6.20
6.4
6.21
6.22
6.23
6.11
6.11
6.12
6.13
6.14
6.15
6.24
6.24
6.25
6.26
6.27
6.28
6.8
6.9
6.10
6.16
6.29
6.17
16
UNCLASSIFIED
BUSINESS DATA RECORD
Character
position
1-4
5-8
9-33
34-41
Field
length
4
4
25
8
Field
format
N
A
AN
D
Field
type
M
M
M
M
42-71
72-101
102-131
132-139
140-150
151-159
160-359
360-559
560-597
598-635
636-662
30
30
30
8
11
9
200
200
38
38
27
AN
AN
AN
D
N
N
AN
AN
AN
AN
AN
C
C
C
C
C
C
C
C
C
O
C
663-665
666-669
670-689
690-727
728-765
766-792
3
4
20
38
38
27
A
N
AN
AN
AN
AN
C
C
C
C
O
C
793-795
796-799
800-819
820-857
858-859
860-875
876-951
952-971
972-1071
1072-1072
1073-1400
3
4
20
38
2
16
76
20
100
1
328
A
N
AN
AN
AN
AN
AN
AN
AN
A
A
C
C
C
O
O
O
O
O
O
M
S
UNCLASSIFIED
Field name
Record identifier (=BIDR)
Customer Reference Number
Payment facility commencement
date (CCYYMMDD)
Surname or family name
First given name
Second given name
Date of birth (CCYYMMDD)
Registered name
Trading name
Street address suburb, town or
locality
Postal address suburb, town or
locality
Contact name
Contact phone number area code
Contact phone number
Contact email address
Group level merchant ID
Business category description
Lodgment type (=A,O or C)
Filler
Reference
number
6.1
6.30
6.31
6.32
6.33
6.34
6.35
6.36
6.4
6.37
6.22
6.23
6.11
6.11
6.12
6.13
6.14
6.15
6.24
6.24
6.25
6.26
6.27
6.28
6.8
6.9
6.10
6.16
6.38
6.39
6.40
6.17
17
UNCLASSIFIED
TRANSACTION PERIOD SUMMARY DATA RECORD
A separate Transaction period summary data record is required for each foreign currency
being reported.
Character
position
1-4
5-8
9-48
49-73
74-103
104-109
110-139
140-147
Field
length
4
4
40
25
30
6
30
8
Field
format
N
A
AN
AN
AN
N
N
D
Field
type
M
M
M
M
M
M
M
M
148-155
8
D
M
156-158
159-171
172-184
185-197
198-210
211-223
224-236
237-256
257-1400
3
13
13
13
13
13
13
20
1144
N
N
N
N
N
N
N
N
A
M
M
M
M
M
M
M
M
S
Field name
Record identifier (=TSDR)
Payment system description
Payment system account number
Settlement bank account name
Settlement BSB number
Settlement bank account number
Transaction period start date
(CCYYMMDD)
Transaction period end date
(CCYYMMDD)
Transaction currency
Gross payment amount
Gross count of payment transactions
Total Refund amount
Total Refund count
Total cash out only amount
Total cash out only count
Cash out component amount
Filler
Reference
number
6.1
6.41
6.42
6.43
6.44
6.45
6.46
6.47
6.48
6.49
6.50
6.51
6.52
6.53
6.54
6.55
6.56
6.17
FILE TOTAL DATA RECORD
Character
position
1-4
5-14
15-24
25-35
36-46
47-57
58-1400
Field
length
4
10
10
11
11
11
1343
Field
format
N
AN
N
N
N
N
A
UNCLASSIFIED
Field
type
M
M
M
M
M
M
S
Field name
Record Identifier (=FILE-TOTAL)
Number of records on file
Count of RPDRs on file
Count of BIDRs on file
Count of TSDRs on file
Filler
Reference
number
6.1
6.57
6.58
6.59
6.60
6.61
6.17
18
UNCLASSIFIED
6 DATA FIELD DEFINITIONS AND VALIDATION RULES
REPORTING ADDRESS DETAILS
It is important that address information provided in the reports supports the issue of
correspondence to suppliers and entities. Address fields in all records provide for a standard
structure in reporting with two fields (two lines) of 38 characters provided for the street address
information. There are separate fields for suburb, town and locality, state or territory, postcode
and country.
Where address fields are mandatory, they must not contain a blank at the beginning of the field,
nor may they contain two blanks between words.
Where the street address is longer than two lines, C/- (care of) lines are to be omitted.
The suburb, town or locality; state or territory; postcode; and country must be supplied in the
separate fields provided and must not be included in the first or second address line fields.
The state or territory field contains the relevant state or territory for the address. The field must
be set to one of the codes shown below:
ACT
NSW
NT
QLD
SA
TAS
VIC
WA
OTH
Australian Capital Territory
New South Wales
Northern Territory
Queensland
South Australia
Tasmania
Victoria
Western Australia
Overseas Address
No other abbreviations are acceptable. The postcode field should only contain numeric
values from 0000 to 9999. If the field is mandatory, then a valid postcode must be reported (for
example 0000 is not a valid postcode).
For an overseas address:





The postcode field must always be set to 9999,
The street address must be provided in the first and second address line fields,
The town, state or region and area code must be reported in the suburb, town or locality
field,
The state field must always be set to OTH, and
The name of the overseas country is to be provided in the country field.
UNCLASSIFIED
19
UNCLASSIFIED
For example, the overseas member's residential address is 275 Central Park West, Apartment
14F, New York, New York, USA 10024. It would be reported as shown below:
Character
position
350-387
388-425
426-452
453-455
456-459
460-479
Field
length
38
38
27
3
4
20
Field name
Content
275 CENTRAL PARK WEST
APARTMENT 14F
NEW YORK NY 10024
OTH
9999
USA
If the reporting party has captured more than one address, overseas and one of those is an
Australian address, then the Australian address (including the postcode) must be reported
rather than the overseas address.
REPORTING OF NAME FIELDS
For contact persons and signatories, the components of the individual’s name – surname or
family name, first given name, and second given name must be reported in the fields as
specified. Titles, prefixes and suffixes (for example, Ms, Mr, Dr, and OBE) should not be
included when reporting names.
Supplier and trading names are to be reported in full with one space between words and any
initials that occur in the name. However, care must be taken with some non-individual names to
differentiate between initials and actual words.
For example, W.R. and J.B. Smith (a partnership) would be reported as
WbRbANDbJbBbSMITH, but ABC Driving School Pty Ltd would be reported as
ABCbDRIVINGbSCHOOLbPTYbLTD (the character b is used to indicate blanks).
Where the individual has a legal single name only, the First given name and Second given
name fields must be blank filled. The legal single name must be provided in the Surname or
family name field.
Where name fields are reported, they must not contain a blank at the beginning of the field, nor
may they contain two spaces between words.
CURRENCY FOR REPORTING
All amounts recorded must be reported in Australian whole dollars. Any cents are to be
truncated.
UNCLASSIFIED
20
UNCLASSIFIED
FIELD DEFINITIONS AND EDIT RULES
6.1
Record length – must be set to 1400.
6.2
Record identifier – must be set to IDENTREGISTER.
6.3
Report specification version number – must be set to the version number of the
specification that the report corresponds to. For reports produced using this specification this
field must be set to BTPSV001.0
6.4
Australian business number – the ABN of the organisation and must be a valid ABN.
In the Intermediary data record this is the ABN of the organisation sending the data (the
intermediary).
In the Reporting party identity data record this is the ABN of the organisation that has the
obligation to lodge the report.
In the Business data record this is the non-individual organisation involved in the transaction.
The ABN reported in this field must correspond to the name that is reported in the same
record.
6.5
Date timestamp report created – the date and time the report was created. It must be
provided in the format CCYY-MM-DDThh:mm:ss.ffTZD.
For example:
 5 November, 2016, 8:15:30.40 am, AU Eastern Standard Time would be reported as
2016-11-05T08:15:30.40+10:00
 18 January, 2016, 1:30:00.00 pm, AU Eastern Standard Time would be reported as
2016-01-18T13:30:00.00+10:00
6.6
File reference – used to record the supplier’s own reference number. This number can
then be used by the ATO in the event of any problems or questions about information
contained in the lodgment. The supplier may find the use of such a reference useful if
submitting a number of reports to the ATO.
6.7
Name – the name of the organisation.
In the Intermediary data record this is the organisation sending the data (the intermediary). If
the intermediary is a computer service provider supplying data on behalf of the reporting party,
then the name of the computer service provider must appear in this field.
In the Reporting party identity data record this is the organisation that the report is for.
UNCLASSIFIED
21
UNCLASSIFIED
The name reported in this field must correspond to the ABN that is reported in the same
record. This should be the name that appears on the ABR for that organisation.
In the Business data record this field is a conditional field, one or more of the following
fields must be provided for each Business data record:
- Surname or family name, First given name, Second given name and Date of birth or
- Name and Business trading name
Reporting parties must complete the field if the data is available.
6.8
data.
Contact name – the name of a person in the organisation responsible for the file or the
6.9
Phone number area code – the Australian area code as used in conjunction with
telephone numbers.
6.10
Phone number – the telephone number for the nominated contact person.
For example:
 the telephone number excluding the area code (1234b5678), or
 a mobile phone number (23b123b456).
The character b is used above to indicate blanks.
6.11 Street address – lines 1 and 2 must only contain the street address (excluding suburb,
town or locality, state or territory, postcode and country). It may not be necessary to use both
lines. If the second line is not used then the field must be blank filled.
For the Business data record, this field must be completed if postal address line 1 field is
blank.
6.12 Street address suburb, town or locality – the suburb, town or locality for the street
address.
blank.
If the Street address line 1 is present then this field must be present
6.13 Street address state or territory – the state or territory for the street address. The field
must be set to one of the appropriate codes (see page 19).
UNCLASSIFIED
22
UNCLASSIFIED
blank.
6.14 Street address postcode – the postcode for the street address. If an overseas address
is specified, then this field must be set to 9999.
blank.
6.15 Street address country – the country for the street address. This field may be left
blank if the country is Australia. If the Street address postcode is 9999 then a country other
than Australia must be entered.
blank.
6.16 Email address – may be used to provide the nominated contact persons email
address. The ATO can communicate with Intermediaries, Reporting parties or authorised
contact persons using email and it is expected that some correspondence may be issued this
way. If present, this must be a valid email address (@ must be positioned after the first
character and before the last character).
6.17
Filler – for use by the ATO. It must be blank filled.
6.18
Record identifier – must be set to RPDR.
6.19 Reporting period start date – the start date for the report period which covers the
businesses transactions. It must be provided in the format CCYYMMDD.
The reporting period will determine the maximum number of Transaction summary data records
permitted.
This field must be less than or equal to the field Date timestamp report created.
6.20 Reporting period end date - the end date for the report period which covers the
businesses transactions. It must be provided in the format CCYYMMDD.
The reporting period will determine the maximum number of Transaction summary data records
permitted.
This field must be equal to or greater than the Reporting period start date field.
6.21 Branch number – the branch number of the financial institution providing the report. If
the financial institution does not have a branch number this field must be set to 001.
UNCLASSIFIED
23
UNCLASSIFIED
6.22 Registered name – the full name of the reporting party as it appears on the Australian
business register (ABR).
6.23 Trading name – the full trading name of the business. If the business does not have a
trading name then this field must be blank filled.
For example:
ABC Holdings Pty Ltd is the registered name for an organisation trading as Australian
Investments. The Reporting party registered name field would contain ABC Holding Pty Ltd and
the Reporting party trading name field would contain Australian Investments.
6.24 Postal address – lines 1 and 2 contain the postal address (excluding suburb, town or
locality, state or territory, postcode and country). It may not be necessary to use both lines. If
the second line is not used then the field must be blank filled. If line 1 is blank then line 2 must
also be blank.
For the Business data record, this field must be completed if street address fields are blank
filled.
For the Reporting party identity data record, this field must be completed.
6.25 Postal address suburb, town or locality – the suburb, town or locality for the postal
address. If Postal address line 1 is present then this field is mandatory. If Postal address line 1
is blank then this field must also be blank.
For the Business data record, this field must be completed if street address line 1 field is
blank.
6.26 Postal address state or territory – the state or territory for the postal address. This
field must be set to one of the appropriate codes (see page 19). If Postal address line 1 is
present then this field is mandatory. If Postal address line 1 is blank then this field must also be
blank filled.
blank.
6.27 Postal address postcode – the postcode for the postal address. If an overseas
address is specified, then this field must be set to 9999. If Postal address line 1 is blank then
this field must be zero filled.
UNCLASSIFIED
24
UNCLASSIFIED
blank.
6.28 Postal address country – the country for the postal address. This field may be left
blank if the country is Australia. If the Postal address postcode field is 9999 then a country
other than Australia must be entered. If Postal address line 1 is blank then this field must be
blank.
blank.
6.29 Software product type – the registered name of the software product and the version
(if applicable) used to compile the report.
If the product has not been developed in-house, then populate this field with COMMERCIAL,
followed by the name of the software developer, the software product and the software version
number.
If the product has been developed in-house, then populate this field with INHOUSE followed by
the name of the organisation that developed the software. If a contractor or consultant was
used, the name of the company will need to be provided.
6.30
Record identifier – must be set to BIDR.
6.31 Customer Reference Number – this field must contain the unique business ID used by
the reporting party to identify the business.
6.32 Payment facility commencement date – the businesses’ services registration
commencement date or open date. It must be provided in the format CCYYMMDD.
6.33 Surname or family name – this field must contain the surname or family name of the
individual primary account owner. Where the individual has a legal single name only, this field
must be completed.
This is a conditional field, one of more of the following fields must be provided for each
Business data record:
- First given name, Second given name and Date of birth
- Business Registered name
- Business Trading name
UNCLASSIFIED
25
UNCLASSIFIED
If First given name, Second given name or Date of birth is present, this field must be
provided.
Reporting parties must complete this field if the data is available.
6.34 First given name – this field must contain the first name or first initial of the individual
primary account owner.
This is a conditional field, one or more of the following fields must be provided for each
- Surname or family name, Second given name and Date of birth
If Surname or family name, Second given name or Date of birth is present, this field must be
provided.
Where the individual has a legal single name only, this field must be zero filled. The legal
single name must be provided in the Surname or family name field.
6.35 Second given name – the second given name of the individual primary account owner
must be provided in this field. If only the individual’s second initial is known, it should be
provided in this field. If the individual has no second given name or it is not known to the
provider, this field must be blank filled.
Where an individual has more than two given names, the third and subsequent given names or
initials are not to be provided.
- Surname or family name, First given name and Date of birth
If Surname or family name, First given name or Date of birth is present, this field must be
provided.
UNCLASSIFIED
26
UNCLASSIFIED
6.36 Date of birth – the date of birth of the individual primary account owner in the format
CCYYMMDD.
For example, if the individual’s date of birth is 29 June 1946, it would be reported as 19460629.
- Surname or family name, First given name and Second given name
If Surname or family name, First given name or Second given name is present, this field
must be provided.
6.37
Australian company number – the ACN of the business. This must be a valid ACN.
If Business Australian business number is blank, this field must be provided.
6.38 Group level merchant ID – This is the reporting party’s internal identifier of the
business category code group Relationship ID/Parent ID.
6.39 Business category description – the business category description is a classification
designating the principle trade, profession or line of business in which a business is engaged.
6.40 Lodgment type – the indicator to identify whether the record contains original,
amended or cancelled data. This field must be set to one of the following:
A – the file contains amended data that is correcting what has previously been reported.
O – the file contains original data that is being reported for the first time.
C – the file contains cancelled data that has been previously reported incorrectly.
6.41
Record identifier – must be set to TSDR.
6.42 Payment system description – a brief description of the payment system that
facilitates the transactions being reported in the Transaction period summary data record.
For example:
BPAY – BPAY biller transactions
UNCLASSIFIED
27
UNCLASSIFIED
This description will be displayed on ATO systems to assist business’ to reconcile their
transaction summaries against the reporting party records.
Do not include month in the payment system description
6.43 Payment system account number – this is the account number allocated to the
business by the reporter that relates to the Payment system identifier.
For example:
Payments processed through the following with the reported Payment system identifier, the
Payment system account number will be:
BPAY scheme = Biller ID
Merchant acquiring system = Merchant ID
6.44
Settlement bank account name – the client/business’ settlement account name.
6.45 Settlement BSB number – the business’ settlement account BSB number. If more than
one BSB is known then record the latest information.
6.46 Settlement bank account number – the business’ settlement account number. If more
than one account number is known then record the latest information.
6.47 Transaction period start date – the start date for the transaction period. It must be in
the format CCYYMMDD. For example, if the information reported is for the period 1 July 2015
to 31 July 2015, report 20150701 in this field.
This date must be equal to or after the date reported in the Reporting period start date field
and before the date reported in the Reporting period end date field.
6.48 Transaction period end date - the end date for the transaction period. It must be in
the format CCYYMMDD. For example, if the information reported on the file is for the period 1
July 2015 to 31 July 2015, report 20150731 in this field.
This date must be after the date reported in the Reporting period start date field and equal
to or before the date reported in the Reporting period end date field.
This field must be within the same month as the date reported in the Transaction period
start date field. For example, if Transaction period start date field is 20150701, the Transaction
period end date field must be between 20150702 to 20150731.
6.49 Transaction currency – the currency of the transactions being reported.
See 10 Currency codes - ISO 4217
6.50
Gross payment amount – total monthly amount of all purchase/sale transactions.
UNCLASSIFIED
28
UNCLASSIFIED
The amount must be reported in whole dollars with cents truncated. For example, $27,592.25
would be reported as 00000027592.
This field is numeric and must not contain decimal points, commas or $+- or other non-numeric
characters. It is right justified and zero filled. Zero is a valid value.
6.51 Gross count of payment transactions – total monthly count of all purchase/sale
transactions.
6.52 Total refund amount – total monthly credit and debit refund amounts for refund
transactions.
6.53
Total refund count – total monthly count of ALL credit and debit refund transactions.
6.54
Total cash out only amount – total monthly cash out only amounts.
If the business does not offer cash out facility, this field can be zero filled.
6.55
Total cash out only count – total monthly count of cash out only amounts.
6.56 Cash out component amount – total monthly amount of cash out where cash out is a
component of a combined purchase.
6.57
Record identifier – must be set to FILE-TOTAL
UNCLASSIFIED
29
UNCLASSIFIED
6.58 Number of total records on file – the total count of all data records in the file, including
those appearing more than once. All the following will be counted:
IDENTREGISTER
RPDR
BIDR
TSDR
FILE-TOTAL
Business data record
Transaction period summary data record
The value reported in the Number of records in file field must equal the sum of all records
on the data file.
6.59 Count of RPDRs on file – the total count of all Reporting party identity data records
only in the file.
6.60
Count of BIDRs on file – the total count of all Business data records only in the file.
6.61 Count of TSDRs on file – the total count of all Transaction period summary data
records only in the file.
UNCLASSIFIED
30
UNCLASSIFIED
7 EXAMPLE OF DATA FILE STRUCTURE
Rosewood Bank Limited supplies its own data. It is submitting an annual return for one
business.
The data file would be structured as follows:
Type of record
Business data record
Transaction period summary data record
Number
1
1
1
12
1
Following are sample records for Rosewood Bank Limited.
INTERMEDIARY DATA RECORD
Character
position
1-4
5-17
18-27
28-38
39-66
67-82
83-282
283-332
333-334
335-349
350-387
388-425
426-452
453-455
456-459
460-479
480-555
556-1400
Field name
Contents
Record length
Record identifier
Report specification version number
Date timestamp report created
File reference
Name
Contact name
Phone number
Email address
Filler
1400
IDENTREGISTER
BTPSV001.0
48123456789
2015-07-05T08:15:30,40+10:00
123456
ROSEWOOD BANK LIMITED
ARIA MONTGOMERY
07
33221144
4 SPENCER STREET
Blank fill
ROSEWOOD
QLD
4340
Blank fill
aria@rosewood.com.au
Blank fill
UNCLASSIFIED
31
UNCLASSIFIED
REPORTING PARTY IDENTITY DATA RECORD
Character
position
1-4
5-8
9-16
17-24
25-35
36-38
39-238
Field name
Contents
Record identifier (=RPDR)
Reporting period start date (CCYYMMDD)
Reporting period end date (CCYYMMDD)
Branch number
Registered name
239-314
315-352
353-390
391-417
418-420
421-424
425-444
445-482
483-520
521-547
548-550
551-554
555-574
575-612
613-614
615-630
631-706
707-786
Trading name
Postal address suburb, town or locality
Contact name
Phone number
Email address
Software product type
787-1400
Filler
1400
RPDR
20140701
20150630
48123456789
001
ROSEWOOD BANK
LIMITED
Blank fill
4 SPENCER STREET
Blank fill
ROSEWOOD
QLD
4340
Blank fill
PO BOX 17
Blank fill
ROSEWOOD
QLD
4340
Blank fill
ARIA MONTGOMERY
07
33221144
aria@rosewood.com.au
INHOUSE FITZ
SOFTWARE V1.0
Blank fill
UNCLASSIFIED
32
UNCLASSIFIED
BUSINESS DATA RECORD
Character
position
1-4
5-8
9-33
34-41
42-71
72-101
102-131
132-139
140-150
151-159
160-359
360-559
560-597
598-635
636-662
663-665
666-669
670-689
690-727
728-765
766-792
793-795
796-799
800-819
820-857
858-859
860-875
876-951
952-971
972-1071
Field name
Contents
Record identifier (=BIDR)
Customer Reference Number
Payment facility commencement date (CCYYMMDD)
Surname or family name
First given name
Second given name
Date of birth (CCYYMMDD)
Registered name
Trading name
Postal address suburb, town or locality
Contact name
Contact phone number area code
Contact phone number
Contact email address
Group level merchant ID
Business category description
1072-1072
1073-1400
Lodgment type (=A,O or C)
Filler
1400
BIDR
679876543211234
20010310
MARIN
HANNA
AIMEE
19780403
123242526
00000000000
REAR WINDOW BREW
AEROPOSTALE
3 EZRA COURT
Blank fill
ROSEWOOD
QLD
4340
Blank fill
PO BOX 32
Blank fill
ROSEWOOD
QLD
4340
Blank fill
ALISON DILAURENTIS
04
32999888
A.Dilaurentis@brew.com
00000000000000000522
MENS AND WOMENS
CLOTHING STORES
O
Blank fill
UNCLASSIFIED
33
UNCLASSIFIED
TRANSACTION SUMMARY DATA RECORD
Character
position
1-4
5-8
9-48
Field name
Contents
Record identifier (=TSDR)
Payment system description
49-73
74-103
104-109
110-139
140-147
148-155
156-158
159-171
172-184
185-197
198-210
211-223
224-236
237-256
257-1400
Payment system account number
Settlement bank account name
Settlement BSB number
Settlement bank account number
Transaction period start date (CCYYMMDD)
Transaction period end date (CCYYMMDD)
Transaction currency
Gross payment amount
Gross count of payment transactions
Total Refund amount
Total Refund count
Total cash out only amount
Total cash out only count
Cash out component amount
Filler
1400
TSDR
Merchant Acquiring
System
679876543211234
REAR WINDOW BREW
064455
66778899
20140701
20140731
AUD
00000069815
00000000000000005815
00000000102
00000000000000000003
00000006950
00000000000000000199
00000000000000012203
Blank fill
The further 11 transaction summary data records would follow.
FILE TOTAL DATA RECORD
Character
position
1-4
5-14
15-24
25-34
35-44
45-54
55-1400
Field name
Contents
Record length
Record Identifier
Number of total records on file
Count of RPDRs on file
Count of BIDRs on file
Count of TSDRs on file
Filler
1400
FILE-TOTAL
0000000016
0000000001
0000000001
0000000012
Blank fill
UNCLASSIFIED
34
UNCLASSIFIED
8 AMENDMENTS
REPORTING TO THE ATO
Reporting parties can report amended records to the ATO electronically. The Business
transactions made through payment systems report data file format, specified in this document
(i.e. the Intermediary data record, Reporting party identity data record, Business data record,
Transaction period summary data record and File total data record) is to be used.
Where an entity needs to amend fields in the report, to correct an error after the electronic
report has been lodged with the ATO, the corrected fields should be reported to the ATO in
another report data file for the same reporting period.
The following information should be recorded in the amended report:



Intermediary, reporting party and business details exactly the same as they were on the
original report, unless this information is being corrected or amended,
all amounts that have not changed, exactly the same as they were in the original report,
and
any amounts that were reported incorrectly should be reported as the corrected amount.
For example if $200 was reported in the Gross payment amount field originally but it should
have been reported as $400, the amount of $400 should be reported for Gross payment
amount field in the report.
All the business records sent to the ATO for the first time, must have ‘O’ recorded in the
Lodgment type field.
Amended records must have ‘A’ recorded in the Lodgment type field.
The data file may contain amended business, transaction data records and any additional
original business or transaction data records that were not reported in a prior report data file for
the same reporting period.
The data file must not contain original business or transaction data records that have
already been sent to the ATO and have not changed.
Original data records contained in the data file and not previously sent to the ATO, must
have O recorded in the Lodgment type field.
Cancelled records must have C recorded in the Lodgment type field. Cancelled records are
used in the situation where a transaction was reported to the ATO in error. Cancelled records
must contain the same information that was provided in the original lodgment.
UNCLASSIFIED
35
UNCLASSIFIED
9 ALGORITHMS
ABN ALGORITHM
The ABN algorithm is a mathematical formula that tests the validity of numbers quoted as
ABNs. Use of the algorithm is required, as it will minimise ABN errors and may subsequently
reduce the need for contact between your clients and the ATO. It is available from
www.ato.gov.au by searching for ABN format.
ABN LOOK UP
The ABN Lookup is a facility that allows organisations to check details provided to them by their
clients. The information that can be checked is publicly available information. The system
allows organisations to confirm that the ABN provided to them is the correct one.
Whilst organisations are not required to check the details provided to them, it is good business
practice to do so.
More information about the ABN Lookup facility is available from www.ato.gov.au by
searching for ABN Lookup or directly from www.business.gov.au.
UNCLASSIFIED
36
UNCLASSIFIED
10 CURRENCY CODES - ISO 4217
Currency, fund and precious metal codes
Entity
Currency
AFGHANISTAN
ÅLAND ISLANDS
ALBANIA
ALGERIA
AMERICAN SAMOA
ANDORRA
ANGOLA
ANGUILLA
ANTARCTICA
ANTIGUA AND BARBUDA
ARGENTINA
ARMENIA
ARUBA
AUSTRALIA
AUSTRIA
AZERBAIJAN
BAHAMAS (THE)
BAHRAIN
BANGLADESH
BARBADOS
BELARUS
BELGIUM
BELIZE
BENIN
BERMUDA
BHUTAN
BHUTAN
BOLIVIA (PLURINATIONAL STATE
OF)
BOLIVIA (PLURINATIONAL STATE
OF)
BONAIRE, SINT EUSTATIUS AND
SABA
BOSNIA AND HERZEGOVINA
BOTSWANA
BOUVET ISLAND
BRAZIL
BRITISH INDIAN OCEAN TERRITORY
(THE)
Afghani
Euro
Lek
Algerian Dinar
US Dollar
Euro
Kwanza
East Caribbean Dollar
No universal currency
Argentine Peso
Armenian Dram
Aruban Florin
Australian Dollar
Euro
Azerbaijanian Manat
Bahamian Dollar
Bahraini Dinar
Taka
Barbados Dollar
Belarussian Ruble
Euro
Belize Dollar
CFA Franc BCEAO
Bermudian Dollar
Ngultrum
Indian Rupee
Boliviano
UNCLASSIFIED
Alphabetic
code
AFN
EUR
ALL
DZD
USD
EUR
AOA
XCD
XCD
ARS
AMD
AWG
AUD
EUR
AZN
BSD
BHD
BDT
BBD
BYR
EUR
BZD
XOF
BMD
BTN
INR
BOB
Mvdol
BOV
US Dollar
USD
Convertible Mark
Pula
Norwegian Krone
Brazilian Real
US Dollar
BAM
BWP
NOK
BRL
USD
37
UNCLASSIFIED
Entity
Currency
BRUNEI DARUSSALAM
BULGARIA
BURKINA FASO
BURUNDI
CABO VERDE
CAMBODIA
CAMEROON
CANADA
CAYMAN ISLANDS (THE)
CENTRAL AFRICAN REPUBLIC (THE)
CHAD
CHILE
CHILE
CHINA
CHRISTMAS ISLAND
COCOS (KEELING) ISLANDS (THE)
COLOMBIA
COLOMBIA
COMOROS (THE)
CONGO (THE DEMOCRATIC
REPUBLIC OF THE)
CONGO (THE)
Brunei Dollar
Bulgarian Lev
CFA Franc BCEAO
Burundi Franc
Cabo Verde Escudo
Riel
CFA Franc BEAC
Canadian Dollar
Cayman Islands Dollar
CFA Franc BEAC
CFA Franc BEAC
Unidad de Fomento
Chilean Peso
Yuan Renminbi
Australian Dollar
Australian Dollar
Colombian Peso
Unidad de Valor Real
Comoro Franc
Congolese Franc
Alphabetic
code
BND
BGN
XOF
BIF
CVE
KHR
XAF
CAD
KYD
XAF
XAF
CLF
CLP
CNY
AUD
AUD
COP
COU
KMF
CDF
CFA Franc BEAC
XAF
COOK ISLANDS (THE)
COSTA RICA
CÔTE D'IVOIRE
CROATIA
CUBA
CUBA
CURAÇAO
CYPRUS
CZECH REPUBLIC (THE)
DENMARK
DJIBOUTI
DOMINICA
DOMINICAN REPUBLIC (THE)
ECUADOR
EGYPT
EL SALVADOR
EL SALVADOR
EQUATORIAL GUINEA
ERITREA
ESTONIA
ETHIOPIA
New Zealand Dollar
Costa Rican Colon
CFA Franc BCEAO
Kuna
Peso Convertible
Cuban Peso
Netherlands Antillean Guilder
Euro
Czech Koruna
Danish Krone
Djibouti Franc
Dominican Peso
US Dollar
Egyptian Pound
El Salvador Colon
US Dollar
CFA Franc BEAC
Nakfa
Euro
Ethiopian Birr
NZD
CRC
XOF
HRK
CUC
CUP
ANG
EUR
CZK
DKK
DJF
XCD
DOP
USD
EGP
SVC
USD
XAF
ERN
EUR
ETB
UNCLASSIFIED
38
UNCLASSIFIED
Entity
Currency
EUROPEAN UNION
FALKLAND ISLANDS (THE)
[MALVINAS]
FAROE ISLANDS (THE)
FIJI
FINLAND
FRANCE
FRENCH GUIANA
FRENCH POLYNESIA
FRENCH SOUTHERN TERRITORIES
(THE)
GABON
GAMBIA (THE)
GEORGIA
GERMANY
GHANA
GIBRALTAR
GREECE
GREENLAND
GRENADA
GUADELOUPE
GUAM
GUATEMALA
GUERNSEY
GUINEA
GUINEA-BISSAU
GUYANA
HAITI
HAITI
HEARD ISLAND AND McDONALD
ISLANDS
HOLY SEE (THE)
HONDURAS
HONG KONG
HUNGARY
ICELAND
INDIA
INDONESIA
INTERNATIONAL MONETARY FUND
(IMF)
IRAN (ISLAMIC REPUBLIC OF)
IRAQ
IRELAND
Euro
Falkland Islands Pound
Alphabetic
code
EUR
FKP
Danish Krone
Fiji Dollar
Euro
Euro
Euro
CFP Franc
Euro
DKK
FJD
EUR
EUR
EUR
XPF
EUR
CFA Franc BEAC
Dalasi
Lari
Euro
Ghana Cedi
Gibraltar Pound
Euro
Danish Krone
Euro
US Dollar
Quetzal
Pound Sterling
Guinea Franc
CFA Franc BCEAO
Guyana Dollar
Gourde
US Dollar
Australian Dollar
XAF
GMD
GEL
EUR
GHS
GIP
EUR
DKK
XCD
EUR
USD
GTQ
GBP
GNF
XOF
GYD
HTG
USD
AUD
Euro
Lempira
Hong Kong Dollar
Forint
Iceland Krona
Indian Rupee
Rupiah
SDR (Special Drawing Right)
EUR
HNL
HKD
HUF
ISK
INR
IDR
XDR
Iranian Rial
Iraqi Dinar
Euro
IRR
IQD
EUR
UNCLASSIFIED
39
UNCLASSIFIED
Entity
Currency
ISLE OF MAN
ISRAEL
ITALY
JAMAICA
JAPAN
JERSEY
JORDAN
KAZAKHSTAN
KENYA
KIRIBATI
KOREA (THE DEMOCRATIC
PEOPLE’S REPUBLIC OF)
KOREA (THE REPUBLIC OF)
KUWAIT
KYRGYZSTAN
LAO PEOPLE’S DEMOCRATIC
REPUBLIC (THE)
LATVIA
LEBANON
LESOTHO
LESOTHO
LIBERIA
LIBYA
LIECHTENSTEIN
LITHUANIA
LUXEMBOURG
MACAO
MACEDONIA (THE FORMER
YUGOSLAV REPUBLIC OF)
MADAGASCAR
MALAWI
MALAYSIA
MALDIVES
MALI
MALTA
MARSHALL ISLANDS (THE)
MARTINIQUE
MAURITANIA
MAURITIUS
MAYOTTE
MEMBER COUNTRIES OF THE
AFRICAN DEVELOPMENT BANK
GROUP
MEXICO
Pound Sterling
New Israeli Sheqel
Euro
Jamaican Dollar
Yen
Pound Sterling
Jordanian Dinar
Tenge
Kenyan Shilling
Australian Dollar
North Korean Won
Alphabetic
code
GBP
ILS
EUR
JMD
JPY
GBP
JOD
KZT
KES
AUD
KPW
Won
Kuwaiti Dinar
Som
Kip
KRW
KWD
KGS
LAK
Euro
Lebanese Pound
Loti
Rand
Liberian Dollar
Libyan Dinar
Swiss Franc
Euro
Euro
Pataca
Denar
EUR
LBP
LSL
ZAR
LRD
LYD
CHF
EUR
EUR
MOP
MKD
Malagasy Ariary
Kwacha
Malaysian Ringgit
Rufiyaa
CFA Franc BCEAO
Euro
US Dollar
Euro
Ouguiya
Mauritius Rupee
Euro
ADB Unit of Account
MGA
MWK
MYR
MVR
XOF
EUR
USD
EUR
MRO
MUR
EUR
XUA
Mexican Peso
MXN
UNCLASSIFIED
40
UNCLASSIFIED
Entity
Currency
MEXICO
Mexican Unidad de Inversion
(UDI)
US Dollar
MICRONESIA (FEDERATED STATES
OF)
MOLDOVA (THE REPUBLIC OF)
MONACO
MONGOLIA
MONTENEGRO
MONTSERRAT
MOROCCO
MOZAMBIQUE
MYANMAR
NAMIBIA
NAMIBIA
NAURU
NEPAL
NETHERLANDS (THE)
NEW CALEDONIA
NEW ZEALAND
NICARAGUA
NIGER (THE)
NIGERIA
NIUE
NORFOLK ISLAND
NORTHERN MARIANA ISLANDS
(THE)
NORWAY
OMAN
PAKISTAN
PALAU
PALESTINE, STATE OF
PANAMA
PANAMA
PAPUA NEW GUINEA
PARAGUAY
PERU
PHILIPPINES (THE)
PITCAIRN
POLAND
PORTUGAL
PUERTO RICO
QATAR
RÉUNION
UNCLASSIFIED
Alphabetic
code
MXV
USD
Moldovan Leu
Euro
Tugrik
Euro
Moroccan Dirham
Mozambique Metical
Kyat
Namibia Dollar
Rand
Australian Dollar
Nepalese Rupee
Euro
CFP Franc
New Zealand Dollar
Cordoba Oro
CFA Franc BCEAO
Naira
New Zealand Dollar
Australian Dollar
US Dollar
MDL
EUR
MNT
EUR
XCD
MAD
MZN
MMK
NAD
ZAR
AUD
NPR
EUR
XPF
NZD
NIO
XOF
NGN
NZD
AUD
USD
Norwegian Krone
Rial Omani
Pakistan Rupee
US Dollar
Balboa
US Dollar
Kina
Guarani
Nuevo Sol
Philippine Peso
New Zealand Dollar
Zloty
Euro
US Dollar
Qatari Rial
Euro
NOK
OMR
PKR
USD
PAB
USD
PGK
PYG
PEN
PHP
NZD
PLN
EUR
USD
QAR
EUR
41
UNCLASSIFIED
Entity
Currency
ROMANIA
RUSSIAN FEDERATION (THE)
RWANDA
SAINT BARTHÉLEMY
SAINT HELENA, ASCENSION AND
TRISTAN DA CUNHA
SAINT KITTS AND NEVIS
SAINT LUCIA
SAINT MARTIN (FRENCH PART)
SAINT PIERRE AND MIQUELON
SAINT VINCENT AND THE
GRENADINES
SAMOA
SAN MARINO
SAO TOME AND PRINCIPE
SAUDI ARABIA
SENEGAL
SERBIA
SEYCHELLES
SIERRA LEONE
SINGAPORE
SINT MAARTEN (DUTCH PART)
SISTEMA UNITARIO DE
COMPENSACION REGIONAL DE
PAGOS "SUCRE"
SLOVAKIA
SLOVENIA
SOLOMON ISLANDS
SOMALIA
SOUTH AFRICA
SOUTH GEORGIA AND THE SOUTH
SANDWICH ISLANDS
SOUTH SUDAN
SPAIN
SRI LANKA
SUDAN (THE)
SURINAME
SVALBARD AND JAN MAYEN
SWAZILAND
SWEDEN
SWITZERLAND
SWITZERLAND
SWITZERLAND
SYRIAN ARAB REPUBLIC
Romanian Leu
Russian Ruble
Rwanda Franc
Euro
Saint Helena Pound
Alphabetic
code
RON
RUB
RWF
EUR
SHP
Euro
Euro
XCD
XCD
EUR
EUR
XCD
Tala
Euro
Dobra
Saudi Riyal
CFA Franc BCEAO
Serbian Dinar
Seychelles Rupee
Leone
Singapore Dollar
Netherlands Antillean Guilder
Sucre
WST
EUR
STD
SAR
XOF
RSD
SCR
SLL
SGD
ANG
XSU
Euro
Euro
Solomon Islands Dollar
Somali Shilling
Rand
EUR
EUR
SBD
SOS
ZAR
South Sudanese Pound
Euro
Sri Lanka Rupee
Sudanese Pound
Surinam Dollar
Norwegian Krone
Lilangeni
Swedish Krona
WIR Euro
Swiss Franc
WIR Franc
Syrian Pound
SSP
EUR
LKR
SDG
SRD
NOK
SZL
SEK
CHE
CHF
CHW
SYP
UNCLASSIFIED
42
UNCLASSIFIED
Entity
Currency
TAIWAN (PROVINCE OF CHINA)
TAJIKISTAN
TANZANIA, UNITED REPUBLIC OF
THAILAND
TIMOR-LESTE
TOGO
TOKELAU
TONGA
TRINIDAD AND TOBAGO
TUNISIA
TURKEY
TURKMENISTAN
TURKS AND CAICOS ISLANDS (THE)
TUVALU
UGANDA
UKRAINE
UNITED ARAB EMIRATES (THE)
UNITED KINGDOM OF GREAT
BRITAIN AND NORTHERN IRELAND
(THE)
UNITED STATES MINOR OUTLYING
ISLANDS (THE)
UNITED STATES OF AMERICA (THE)
UNITED STATES OF AMERICA (THE)
URUGUAY
New Taiwan Dollar
Somoni
Tanzanian Shilling
Baht
US Dollar
CFA Franc BCEAO
New Zealand Dollar
Pa’anga
Trinidad and Tobago Dollar
Tunisian Dinar
Turkish Lira
Turkmenistan New Manat
US Dollar
Australian Dollar
Uganda Shilling
Hryvnia
UAE Dirham
Pound Sterling
Alphabetic
code
TWD
TJS
TZS
THB
USD
XOF
NZD
TOP
TTD
TND
TRY
TMT
USD
AUD
UGX
UAH
AED
GBP
US Dollar
USD
US Dollar
US Dollar (Next day)
Uruguay Peso en Unidades
Indexadas (URUIURUI)
Peso Uruguayo
Uzbekistan Sum
Vatu
Bolivar
USD
USN
UYI
Dong
US Dollar
US Dollar
CFP Franc
Moroccan Dirham
Yemeni Rial
Zambian Kwacha
Zimbabwe Dollar
Bond Markets Unit European
Composite Unit (EURCO)
Monetary Unit (E.M.U.-6)
VND
USD
USD
XPF
MAD
YER
ZMW
ZWL
XBA
URUGUAY
UZBEKISTAN
VANUATU
VENEZUELA (BOLIVARIAN
REPUBLIC OF)
VIET NAM
VIRGIN ISLANDS (BRITISH)
VIRGIN ISLANDS (U.S.)
WALLIS AND FUTUNA
WESTERN SAHARA
YEMEN
ZAMBIA
ZIMBABWE
ZZ01_Bond Markets Unit
European_EURCO
European_EMU-6
UNCLASSIFIED
UYU
UZS
VUV
VEF
XBB
43
UNCLASSIFIED
Entity
Currency
European_EUA-9
European_EUA-17
ZZ06_Testing_Code
Unit of Account 9 (E.U.A.-9)
Unit of Account 17 (E.U.A.-17)
Codes specifically reserved for
testing purposes
The codes assigned for
transactions where no currency
is involved
Gold
Palladium
Platinum
Silver
ZZ07_No_Currency
ZZ08_Gold
ZZ09_Palladium
ZZ10_Platinum
ZZ11_Silver
UNCLASSIFIED
Alphabetic
code
XBC
XBD
XTS
XXX
XAU
XPD
XPT
XAG
44
UNCLASSIFIED
11 MORE INFORMATION
Electronic specifications
If anything in this specification needs clarification, direct your enquiries to:
 phone 13 28 66
 email ato–ereporting@ato.gov.au
Other enquiries
All other enquiries relating to Business transactions made through payment systems please
contact 13 28 66.
Software developers homepage
Software developers, both in– house and commercial, who are developing electronic taxable
payments reporting software, should use this specification for developing their application.
The Software developers homepage website at http://softwaredevelopers.ato.gov.au has
been designed to facilitate a partnership between the software development industry and the
ATO and provides the following:



a self– testing model allowing software developers to check their product, package,
program or system against ATO test scenarios or relevant format testing,
access to information relevant to all software developers to assist in the development of
tax– related software, and
a software product register which tax agents and businesses can access to find products
that will assist in meeting tax– related obligations.
Lodging the Declaration of Compliance automatically lists the product(s) on the Software
developers homepage Product register. Software developers that have listed their product on
the Product register may direct users to the website at http://softwaredevelopers.ato.gov.au
for confirmation that the product has met ATO requirements. Developers who do not need to
register in order to list products may still receive emails detailing significant issues by using the
subscription service available from the site. Registering or subscribing for updates is
recommended for both in– house and commercial software developers.
For more information on the Software developers homepage website, contact the Software
Industry Partnership Office (SIPO):
 phone 1300 139 052, or
 email SIPO@ato.gov.au.
UNCLASSIFIED
45

Electronic reporting specification - ATO Let`s Talk

Transcription

Similar documents

ERL-0631-GD PR

Presentation - Hunter - USPHS Scientific and Training Symposium

Microbial Forensics

Wittstruck_NDIA_Presentation - National Defense Industrial

Cyber Security Metrics

dw802

RE/MAX vs. THE INDUSTRY

Small-scale Waste to Energy

Sarbains Oxley reveals financial anomalies in audits

—Think Brighter“ Cards