Triniteq PowerEPOS

Triniteq is an Australian point-of-sale company, and PowerEPOS is its hospitality POS. Triniteq sets up a data export for your venue, you enter four things Triniteq gives you, and your sales come across on a schedule — twice a day.

Triniteq calls that export DES, the Data Extraction Service. It's simply the part of PowerEPOS that hands data to other systems. You'll hear the name from Triniteq, but there's nothing for you to install or run.

At a glance

What it's for	Sales and card tips from your PowerEPOS till
How you connect	You paste in four details Triniteq gives you
How often it updates	Twice a day
You will need	Four things from Triniteq: your PowerEPOS organisation code, a service account username and password for Tip Sheet, and the Job ID of the data export Triniteq sets up for the venue. Plus the terminal IDs that belong to this venue, if some terminals in the export shouldn't count

Sales don't arrive instantly

PowerEPOS doesn't send sales to Tip Sheet as they happen — Tip Sheet collects them twice a day. So after connecting, expect your sales on the next scheduled run, or straight away if you run Import Data. If you need tips landing during service rather than after it, Doshii and Tyro Connect update as sales happen.

What comes across

Only closed transactions come across, so nothing arrives while a tab is still open. Each closed transaction becomes one sale in Tip Sheet, and each payment on it becomes one card payment.

• The sale amount, and the tips. In PowerEPOS a tip sits on the payment rather than on the sale, so each payment keeps its own tip and the sale's tip is their total.
• The time the order was opened — not the time it was settled. That's what decides which service the sale falls into, converted from the till's local time to the venue's. Each payment keeps its own paid time.
• The trading date PowerEPOS assigns. An order opened just before midnight and closed after it stays on the trading day it belongs to.
• The terminal the order was created on — the one it was actually taken on. Closing off is often done from a back-office or manager station, so the closing terminal is deliberately ignored. Each card payment separately carries the terminal it was taken on.
• The payment type name and the payment's own ID, kept as the reference. Card numbers aren't in the export, so there's no masked card number.
• The closed order number as the sale's reference, or the transaction ID where there isn't one.
• Service charge, surcharge and cash out, recorded against the card payment wherever the payment carries an amount for them.

The original export is kept against each sale, so a figure can always be traced back to what PowerEPOS sent. Individual menu items are stored for that reason only — Tip Sheet doesn't report on them.

PowerEPOS 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

• Triniteq has to set it up first. Triniteq creates the data export that Tip Sheet runs. Tip Sheet can't create it, and the connection won't save without its Job ID. Ask Triniteq support to set up a Tip Sheet data export for the venue.
• A service account. A PowerEPOS login used by Tip Sheet rather than by a person. Triniteq issues the username and password along with the export.
• Your organisation code. PowerEPOS's identifier for your organisation, supplied at the same time. Nothing connects without it.
• Terminal IDs, only if you need them. Collect these if some terminals in the export 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.

Ask Triniteq for all four at once

Triniteq's own DES documentation sits behind their login, so there's no public page we can point you at. What we can tell you is exactly what Tip Sheet needs: an organisation code, a service account username and password, and the Job ID of a data export set up for your organisation. Ask Triniteq support for those four things together and the rest of this page works as written.

One POS per venue

A venue can have only one POS connected at a time. If Doshii, Lightspeed, Tyro Reporting 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.

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.)

1. Select Connect on the Triniteq PowerEPOS card. The Triniteq PowerEPOS Credentials box opens. There's nothing to approve on the PowerEPOS side — filling this box in is the connection.

2. Paste in the Job ID Triniteq gave you. It's required, and required appears underneath if you try to save without it. (A Known DES Jobs dropdown appears above this box later, once a connection exists. On a first connection, type the ID in.)

3. Leave Filter by Terminal IDs empty to take every terminal in the export. To narrow it, type a terminal ID and press Enter, Tab or a comma — or click outside the box — and it becomes a chip.

4. Fill in Organisation Code, Service Account Username and Service Account Password. All three are required.

5. Select Save. Tip Sheet signs in to PowerEPOS and checks that the Job ID really exists on your organisation. Both have to pass before anything is stored, so a connection that saves is a connection that can import.

If a check fails, the box stays open and tells you which one:

• Could not authenticate with Triniteq PowerEPOS. Check the organisation code and service account username/password. — one of those three is wrong.
• The selected PowerEPOS data export job was not found for this organisation. — the login is fine, but that Job ID isn't on this organisation. Check it with Triniteq.

Otherwise Integration Saved appears and the card turns green, with Manage, Import Data and Disconnect on its menu.

Nothing arrives yet. Sales land on the next scheduled run, or sooner if you run Import Data.

Choose what's included

Everything below is edited from the same box: on the connected card, open the menu and choose Manage.

The export. Job ID decides which export every import runs. Change it and the next import runs the new one, after the same two checks the first connection went through. Once connected, a Known DES Jobs dropdown appears above the box, listing the exports Tip Sheet can see on your organisation — picking one fills the Job ID in for you, which beats typing it. If the dropdown isn't there at all, the list came back empty, which usually means the stored login no longer works.

Terminal IDs. A sale is kept only when the terminal it was created on is in Filter by Terminal IDs. Everything else is dropped during the import and never reaches the tip sheet. Clear the box and save to take every terminal again. Changing the filter doesn't touch what's already been imported — re-import the dates you care about to apply it, which replaces everything Tip Sheet holds for those dates.

A filter you didn't set

A venue can have filters this box doesn't show you — by outlet name, by the closing terminal, or as a list of terminals to leave out rather than keep. 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.

Why the sign-in boxes are blank

Open Manage and you'll find Organisation Code, Service Account Username and Service Account Password all empty and greyed out. Nothing has gone missing. Tip Sheet never sends those three values back to your browser, so it genuinely can't show you what it's holding — and that's true of all three, not just the password.

To change any of them, tick Rotate organisation code / username / password. All three boxes open up, all three start blank, and all three are required. So you have to re-type the organisation code and the username as well, even if only the password has changed — have all three from Triniteq to hand before you start. Leave the tick box alone and the stored details are kept exactly as they are.

Keeping it running

Day to day. Tip Sheet collects the venue's PowerEPOS sales twice a day, covering yesterday and today. Each run asks for a fresh export of those trading dates and replaces what Tip Sheet already holds for them. Because the export is always the current state of those days, reopened tabs, refunds and amendments fix themselves on the next run, and re-running a date never doubles anything up.

Exports take a moment to build. PowerEPOS builds the file when it's asked rather than having one waiting. A day or two takes seconds; a long stretch of history is a much heavier export and can take several minutes. Tip Sheet waits about ten minutes before giving up on one.

Filling in a gap. On the connected card, choose Import Data and confirm Start a historical import of card transactions and tips for this venue?. 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 — there's no confirmation on the card itself. Anything older than two pay periods needs Tip Sheet support.

Locked and paid periods are safe. Any trading date sitting in a locked or paid period is skipped: it isn't collected, and nothing already recorded against it is changed or removed. If a locked stretch falls in the middle of a range you re-import, Tip Sheet does the dates either side and leaves the locked ones alone. Re-import a range that's entirely locked and nothing changes at all.

Disconnecting. Choose Disconnect and confirm Are you sure? This will impact all automated imports. The twice-daily import stops and the card goes back to Connect. It says Integration deleted, but nothing is thrown away — sales already imported, and the tips worked out from them, stay exactly as they are.

Reconnecting. Reconnecting is a brand new connection, so fill in every field: organisation code, username, password and Job ID. The same two checks run, so it either works or tells you why it didn't.

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
The sign-in boxes are blank and won't let you type	Normal — Tip Sheet can't show you what it's holding	Tick Rotate organisation code / username / password, then re-type all three
Could not authenticate with Triniteq PowerEPOS... when you save	One of the three values is wrong, or Triniteq has disabled the service account	Re-check all three against what Triniteq issued. If they look right, ask Triniteq whether the service account is still active
The selected PowerEPOS data export job was not found for this organisation. when you save	The login works but that Job ID isn't on this organisation — a typo, or an export set up under a different organisation	Ask Triniteq to confirm the Job ID for this venue. On a connected venue, pick from Known DES Jobs instead of typing
No sales right after connecting	Expected — nothing arrives until the next scheduled run	Run Import Data if you need the last two pay periods now, otherwise wait
Failed to authenticate with Triniteq PowerEPOS after an import that used to work	Triniteq changed or expired the service account password	Open Manage, tick the rotate box, re-type all three, save, then Import Data
Invalid configuration - Missing data.	The organisation code, username, password or Job ID is missing	Open Manage, tick the rotate box, re-type all three, check the Job ID, save, then re-import
export job did not finish within the allowed time	The export was too big to build inside the ten-minute wait — usually a long stretch of history	Re-import a few days at a time rather than the whole period at once
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
Sales land in the wrong service	A sale belongs to the service it was opened in, so a tab opened late in one service and settled in the next stays with the earlier one	Check your service periods and tip earning hours cover the hours you actually trade
Re-importing changes nothing for some dates	Those trading dates sit in a locked or paid period and are skipped deliberately	Unlock the period if the figures genuinely need correcting, then re-import
A whole trading date is missing, but the POS shows takings	Nothing had been closed off on the POS for that date when the export ran	Close any outstanding tabs on the POS, then re-import that date