Synoria AI CorporationAutonomous software company
Accounting & Finance

Which shifts were paid short

A shift is not paid at a rate, it is paid in bands, and three of them are places money quietly goes missing. A 90-minute shift where the minimum engagement is three hours is three hours of pay. A shift from 5pm to 11pm with an evening loading from 7pm is two hours ordinary and four hours evening, not six hours of either. And a Sunday evening is paid at the Sunday rate, not Sunday plus evening. Paste the roster with what was actually paid and this shows which shifts fall short and which rule made them short — and what a single flat rate per shift would have said instead, so the difference is a number.

← All products
Accounting & Finance

Small cafes, restaurants and bars that roster casuals across evenings, weekends and public holidays, and whoever checks the pay run afterwards.

How it works

  1. Enter your base rate, casual loading, and whether the loading and penalty are added together or applied one on the other.
  2. Enter the penalty percentages you use and the time the evening loading starts; list your public holiday dates.
  3. Enter the minimum engagement and the ordinary hours per day before overtime.
  4. Paste one line per shift: date;start;finish;unpaid break;casual or permanent;amount paid.
  5. Read which shifts fall short, and what a single flat rate would have cost.

What you gain

  • Finds every shift that was paid at the wrong rate — split across the wrong pay bands, or paid for hours worked instead of the minimum engagement — and shows exactly how much was underpaid.

Screenshot

Which shifts were paid short

Technical details

Standard24.99 USD · 1500 requests · 31-day license · one-time payment · 31-day access
Pro49.98 USD · 6000 requests · 31-day license · one-time payment · 31-day access
Isolationdedicated instance per license
Usage meteringLLM usage metered per license
Accessweb sign-in with license key

How to set up & use

  1. Buy the license — your key (lic_...) appears on the order page and in your email.
  2. Sign in at app.synoriaai.com with your license key.
  3. No installation — the product runs in your browser, on your own isolated instance.
  4. 1. Open the calculator and enter your base hourly rate (e.g., 25.00).
  5. 2. Set your loading percentage and choose how loadings and penalties combine (additive or stacked).
  6. 3. Enter the evening start time and its loading, plus Saturday, Sunday, and holiday penalty percentages.
  7. 4. Set the minimum engagement in minutes (e.g., 180 for 3 hours) and the overtime threshold (e.g., 480 minutes) with its penalty.
  8. 5. Enter a shift's start and end times; the tool splits it across bands and shows the correct pay, plus what a flat rate would have given.

Frequently asked questions

Does this tool store my shift data or rates?

No. All inputs stay in your browser; nothing is sent to a server, so your pay rates and shift details are not saved or transmitted.

Does it include award rates automatically?

No. You enter all rates—minimum engagement, loadings, penalties, overtime threshold, and combining order—because these vary by year, classification, state, and award.

What does it not calculate?

It only calculates pay for a single shift based on your entered rules. It does not handle leave, deductions, or multiple-shift totals, and it does not apply any specific award automatically.

With USDT or USDC stablecoins on one of the payment networks shown at checkout. You scan a QR code with the exact amount pre-filled — no card and no wallet connection is required.
The payment is detected on-chain and matched to your order by its unique amount. After confirmations complete, your license key is generated and your own product instance is prepared; the order page updates by itself.
No. You make a one-time stablecoin payment for a 31-day license with a fixed request quota. There is no auto-renewal — to keep using the product, you simply purchase again.
Each plan includes a fixed number of requests for the license period. A small overage allowance is defined beyond that; once it is used up, requests pause until a new license is purchased.
Yes. Every license runs in its own isolated instance with its own data directory — customers never share an instance or data.
On-chain payments are never lost. Keep your order number and contact support; the payment can always be matched to your order.
Each product is built for its target market and uses that market's language; this storefront is available in 9 languages.

Related products