Submitting batch files with Tyro Health Online

Tyro Health Online supports bulk transmission of invoices to healthcare funders. Batched invoices are processed individually according to funder rules.

A single batch file can support multiple invoices and claimed items. For all invoices, it’s important to note:

Files must be in a CSV format. Double quoted fields (i.e. using quotes as text qualifiers) are optional, but recommended when dealing with text columns (like descriptions).
Template and example CSV files for each funder are posted on Tyro Health Online.
The first row must be a header record and must conform to template values provided.
Each row’s columns must be ordered according to the header record.
Up to 10,000 rows can be included in a single file.
Fields listed as mandatory for each funder must be complete and valid for successful upload.
After uploading to Tyro Health Online, invoices that pass business rule validation will be created as a Draft in a Ready to submit status. Select those invoices and click submit to process.
Invoices that fail validation will be in an Incomplete status and require attention prior to submission.

Importantly, if you create, open or save the file using Microsoft Excel or other spreadsheet programs, please note that date and time fields may be automatically updated to a format that is not accepted - be sure to save the file in the formats defined below.

Invoice guidelines:

An invoice will result in a single unique Tyro Health Online transaction identifier, invoice date and status;
An invoice will have a single unique invoiceReference as nominated by you;
An invoice will have a single patient and health fund account;
An invoice will have a single provider and payee;
An invoice will have one or more claimed items;
Each claimed item will have at least a unique invoiceReference , and valid : provider.providerNumber , patient . healthFundAccount.membershipNumber , claimItems.itemCode , claimItems.serviceDateString and additional item attributes can

To support invoices with multiple claimed items:

Invoices with the same invoiceReference will be grouped into a single invoice for submission to a funder.
Rows for a unique invoice should be grouped together sequentially and each item should use a unique claimItems.reference for that invoice.
For invoice level (but not item level) attributes that repeat, only the first instance of those values will be used.

For those that create batch files using Microsoft Excel, Apple Numbers or Google Sheets:

All fields should use a format of “Plan Text” or “Text” .
Special care should be taken while entering serviceDate , time of service and other date/time numbered fields as these tools may apply an automatic format different from expected.
Files must be saved/exported as:
- Microsoft Excel - Windows: CSV Comma delimited ( * .csv)
- Microsoft Excel - Mac: Comma-separated Values (.csv)
- Apple Numbers: CSV, Text Encoding: Unicode (UTF-8)
- Google Sheets: Comma-separated values (.csv, current sheet)

QBE invoices

Field	Required?	Format	Example value	Notes	Key constraints
`funder`	Mandatory	Valid values only	qbe	All qbe claims should have the funder set to qbe.
`sequenceNumber`	Optional	Up to 4 numbers	1	Row counter starting with 1. Unique and sequential within a batch file. Used to identify row level errors/mistakes. Leading zeros NOT permitted. If not supplied, the row count will be used to identify processing issues.
`invoiceReference`	Mandatory	Up to 16 characters	20200901ABCD	Your unique invoice/transaction reference. Typically generated from a practice management or accounting system. This value will be traced through to settlement reporting and is separate from any funder defined transaction identifier or claim reference. Where multiple service items exist for an invoice, all rows for a unique invoiceReference will be grouped into a single invoice and the first occurrence of repeating invoice level (but not service level) details will be used. Note: these rows should be grouped sequentially.
`provider.providerNumber`	Mandatory	Up to 16 alphanumeric characters	0065431A	Servicing provider number or other registration identifier which must be valid and active in Tyro Health Online for a given funder. For QBE, a Medicare issued provider number should be used where available. Where a Medicare provider number is not applicable, use the Tyro Health Online-generated provider number allocated during onboarding.	• A unique invoice can include only one provider. • The provider must be registered on Tyro Health Online and enabled for the selected funder.
`patient.identity.dobString`	Mandatory	YYYY-MM-DD	2021-10-27		• Date must be formatted YYYY-MM-DD
`patient.identity.firstName`	Optional	Up to 50 characters	Dominick	Patient first / given name as registered with funder. If patient has only one name, use "Onlyname" as placeholder in firstName field.	• A unique invoice can include only one patient. • Can only contain alpha (A-Z and a-z), numeric (0- 9), space ( ), apostrophe (') and hyphen (- ) characters • Spaces must not appear before or after apostrophes, hyphens, other spaces or the supplied value. • At least one alpha or numeric character required.
`patient.identity.lastname`	Mandatory	Up to 25 characters	Harris	Patient last / family name as registered with the funder.	A unique invoice can include only one patient. • Can only contain alpha (A-Z and a-z), numeric (0- 9), space ( ), apostrophe (') and hyphen (- ) characters • Spaces must not appear before or after apostrophes, hyphens, other spaces or the supplied value. • At least one alpha or numeric character required.
`patient.identity.refId`	Optional, but strongly recommended	Up to 128 characters	3DE2D2BC-17CC-4978-A79D-2151DC417B2F	A unique patient identifier generated by your system. By setting this value you can uniquely search and sort transactions by patient. Future transactions can also be processed using refId rather than providing patient and health fund account details. Any differing patient details for a given refId will update the patient record on Tyro Health Online. To prevent creation of duplicate patient records in Tyro Health Online, set a unique refId per patient.	• A unique invoice can include only one patient.
`patient.healthFundAccount.membershipNumber`		Up to 30 alphanumeric characters	Workers Comp Claims: WCC1PE4000006 Or CTP Claims: CTP SA: 940006867801 CTP NSW: 360006869101 CTP QLD: 710006867601	QBE claim number number
`claimItems.itemCode`	Mandatory	Up to 8 alphanumeric characters	AA020	Any qbe supported paycode
`claimItems.serviceDateString`	Mandatory	YYYY-MM-DD	2020-08-25	Date of service in YYYY-MM-DD format.	• must be a valid date • must be within 2 years as at date of submission • must not be future dated • must not be before patient date of birth
`claimItems.customDescription`	Conditional	Up to 60 characters	“Foam roller to assist with rehab exercises”	If the item code being used has the ability to accept a custom description, you can enter it here. This is typically used on generic item codes that need further elaboration eg item code Aids and Appliances (for rehab aids).
`claimItems.chargeAmount`	Mandatory	Currency notation, up to 6 numeric and 2 decimal digits	50.67	Item per unit pricing. This value will be deemed tax-inclusive if the isTaxable field is set to ‘true’. If isExtendedPrice is set to ‘true’ this will be the aggregate amount for all quantity set.	For example if the price without tax for an item per unit is $9.00, this field would have $9.00 and isTaxable = false if tax is not to be charged. If tax is to be charged, this field would show $9.90 and isTaxable = true.
`qbe.claimItems.isTaxable`	Optional	Boolean	true false	Default is false. When true, It indicates that a GST of 10% is included in the icare.claimItems.price field	Only certain item codes can include GST. Reference qbe provider docs for rules on GST.
`claimItems.quantity`	Optional	Up to 5 digits	1,2, 3 etc	Default is 1.	Note that some items may auto-map quantity to time or period units.
`claimItems.unit`	Optional	Valid values only	each minutes	Default is each. Values include: • each • minutes (only for applicable items)
`claimItems.isExtendedPrice`	Optional	Boolean	true false	Default is false. If set to true, this will indicate the price is extended/aggregate price for all quantities submitted. Otherwise, if set to false or omitted the price field will be multiplied per quantity claimed.	Examples: • if true, and the price is $20.00 with three quantity (effectively $6.66666 per unit) as sent to a funder. • if false, and price is $20.00 with three quantity, each item price is $20.00 which will make extended price $60.00 as sent to a funder.