Tyro Reporting
Tyro is an Australian payments provider, and its EFTPOS terminals record the tip on every card payment they take. Tyro Reporting is the reporting side of that. Once a day, Tip Sheet signs in to Tyro with a username and password you enter, collects a day's card payments for each of the venue's merchant IDs, and turns them into the sales and card tips on the tip sheet.
At a glance
| What it's for | Sales and card tips taken on your Tyro EFTPOS terminals |
| How you connect | You paste in details Tyro gives you |
| How often it updates | Once a day — yesterday's takings, the next morning |
| You will need | Your Tyro reporting username and password, every Tyro merchant ID the venue trades under, and — only if some terminals shouldn't count — the terminal IDs that belong to this venue |
Tyro Reporting or Tyro Connect?
Two different Tyro products. A venue uses one or the other, never both.
| Tyro Connect | Tyro Reporting | |
|---|---|---|
| When sales appear | Within minutes, as they happen | Once a day — yesterday's takings, the next morning |
| Use it when | Your POS is connected to Tyro Connect | Your POS isn't on Tyro Connect, or the venue trades under more than one Tyro merchant ID |
| What you enter | Nothing — Tip Sheet support sets it up | Your Tyro reporting username and password |
Tyro Reporting is the only one of the two that covers a venue trading under several merchant IDs. Tyro Connect brings across your POS's own order detail as well, which Tyro Reporting doesn't have.
A venue can have only one POS connected at a time. If Doshii, Lightspeed or Tyro Connect is already connected, the other cards are greyed out with Only one integration is possible at a time. Disconnect the current one first.
What comes across
Each Tyro card payment becomes one sale and one card payment in Tip Sheet, carrying:
- The sale amount and the tip — the tip is what the venue's card tips are built from.
- The date and time, in the venue's local time, which decides the service it belongs to.
- The terminal it was taken on, the card type and masked card number (for example
visaandXXXXXXXXXXXX4170), and the Tyro reference, kept as the sale reference. - Surcharge, as a service charge on the payment, and cash out, as a cash-out adjustment.
- The merchant ID it came from, on every row, so takings can always be traced back.
A payment taken before the day's first service starts counts on the previous trading day, so late-night takings land on the night they were earned.
Tyro Reporting brings takings only. Who worked and for how long comes from your timesheet integration, and cash tips are still entered by hand in the venue view.
Before you start
- Reporting details from Tyro. Tip Sheet can't issue these. You need a Tyro username and password with reporting access, and the same login has to reach every merchant ID below.
- Your merchant IDs. One for each Tyro merchant facility the venue trades under. You can read the merchant ID (MID) and terminal ID (TID) off the terminal itself — Menu → Merchant Information — and Tyro support can confirm them for you.
- Terminal IDs, only if you need them. Collect these if some terminals under those merchant IDs belong to a different venue, or shouldn't count towards this venue's tips.
- Permission to change integrations for the venue. Without it, every card on the Integrations tab is faded and won't respond.
How reporting access is requested and issued is Tyro's own process, and it varies by account. If the venue doesn't already have a reporting login, ask your Tyro account manager or Tyro support for one before you start.
Connecting it
In the admin view, open Venues, choose the venue, then the Integrations tab, and scroll to POS Integration. (The section isn't shown for dependent venues.)
-
Select Connect on the Tyro Reporting card. The Tyro Credentials box opens.
-
Add every merchant ID the venue trades under to Merchant IDs. Type one and press Enter, Tab or a comma — or click outside the box — and it becomes a chip. At least one is required: Save does nothing while the box is empty, and Add at least one merchant ID appears underneath.
-
Fill in User and Password with your Tyro reporting login.
-
Leave Filter by Terminal IDs empty to take every terminal under every merchant ID. To narrow it, add terminal IDs as chips the same way.
-
Select Save. Integration Saved appears and the card turns green, with Manage, Import Data and Disconnect on its menu.
Tip Sheet never sends the stored password back to your browser, so it genuinely can't show you the one it's holding. That's why Password is blank every time you open the box. When you're editing a connection that already works, leaving it blank keeps the stored password as it is.
Choose what's included
Both lists are edited from the same box: on the connected card, open the menu and choose Manage.
Merchant IDs. The full list Tip Sheet collects from. Add one and the next import includes it; remove one and future imports skip it. Takings already imported stay put until you re-import those dates — a re-import replaces everything Tip Sheet holds for the dates it covers, so a removed merchant's rows disappear from them.
Terminal IDs. Whatever is in Filter by Terminal IDs applies to every merchant ID in the list — one shared list, not one per merchant. Payments from terminals that aren't in it are dropped during the import and never reach the tip sheet. Clear the box and save to take every terminal again.
A venue can have per-merchant terminal rules that this box doesn't show you. If you save from here, what you saved replaces them. Check with Tip Sheet support before changing the terminal filter on a venue that was set up with anything unusual.
More than one merchant
Running several merchant IDs through one venue is what separates Tyro Reporting from Tyro Connect, so it's worth knowing how it behaves.
- One login for all of them. If a merchant ID isn't reachable with that username and password, it can't be collected here.
- Every row is tagged with the merchant it came from, so takings from different merchant facilities stay apart once they're merged.
- All or nothing. If any one merchant fails, the whole day fails and is undone — you never get half a day. But one bad merchant ID stops the good ones landing too, so remove any that no longer trades rather than leaving it in the list.
Keeping it running
Day to day. Tip Sheet brings in the venue's Tyro takings once a day, a day at a time, using the venue's timezone to decide which day that is. Each run replaces what it already holds for that date, so re-running a date never doubles anything up.
Filling in a gap. On the connected card, choose Import Data and confirm Import card transactions for last two weeks (pay periods)?. Tip Sheet re-collects the last two tip periods and works the tips out again. It runs in the background; watch its progress at the bottom left and in the notifications bell. Anything older than two pay periods needs Tip Sheet support.
Changing the login or the merchants. Open Manage, change what you need and save. Leave Password blank to keep the stored one; type a new one to replace it.
Disconnecting. Choose Disconnect and confirm Are you sure? This will impact all automated imports. The daily import stops and the card goes back to Connect. It says Integration deleted, but nothing is thrown away — takings already imported, and the tips worked out from them, stay exactly as they are.
Reconnecting is a brand new connection, not a resumption. Fill in every field, including the Password box. If you leave Password blank on a reconnection, it's saved with no password at all, and every import from then on fails. This is the most common reason a reconnected venue quietly stops getting takings. (Leaving it blank is only safe when you're editing a connection that is already working.)
The audit trail. Connecting, changing and disconnecting are recorded against the venue, as are Import Data runs you start by hand.
If something looks wrong
| What you see | Why | What to do |
|---|---|---|
| Connect is greyed out, tooltip Only one integration is possible at a time | Another POS is already connected | Disconnect that one first — a venue takes one POS |
| Every card on the Integrations tab is faded | You can't change integrations for this venue | Ask a business owner or Tip Sheet support |
| Add at least one merchant ID appears and Save does nothing | The ID was typed but never turned into a chip | Press Enter, Tab or a comma after typing, or click outside the box, then save |
| Invalid configuration - Missing data. after an import | The username, password or a merchant ID is missing — usually after reconnecting without re-typing the password | Open Manage, re-enter User and Password, check the merchant IDs, save, then Import Data |
| An import fails and nothing lands for the day | One merchant ID couldn't be reached, so the whole day was undone | Check every merchant ID works with that login, remove any that no longer trade, then re-import |
| Some terminals arrive, others never do | A terminal filter is set and they aren't in it | Open Manage and check the chips, or clear the box, then re-import those dates |
| Far fewer takings than the venue took, or none for a date | The terminal filter is excluding them, or those terminals trade under a merchant ID that isn't listed | Clear Filter by Terminal IDs and re-import that date. If still short, check the MID and TID on the terminal |
| Tips land on the day before you expected | Payments taken before the day's first service starts count on the previous trading day — deliberately | Check your service periods and tip earning hours cover the hours you actually trade |