Overview
The Transactions page's Type filter shows 12 transaction types. Not all of them represent money changing hands, so only some count toward your Revenue figure, and a slightly different set counts toward Completion Rate. This article explains what each transaction type means and how it's treated in your reporting.
Applies to
| Product | Juno Portal |
| Feature | Transactions — Type filter; Dashboard Revenue and Completion Rate |
| Audience | Finance and operations teams |
What you'll achieve
You'll know what each transaction type means, and whether it's included in your Revenue figure, your Completion Rate, both, or neither — so a figure that looks lower (or higher) than expected can be explained rather than questioned.
Transaction types and how they're treated
| Type | Category | Counts as Revenue | Counts in Completion Rate |
| Sales Completion | Success | Yes | Yes — counts as a completed payment |
| Direct Settlement | Success | Yes | Yes — counts as a completed payment |
| Authorization | Pending | No | Yes — counts as an attempted payment |
| Top Up Authorization | Pending | No | Yes — counts as an attempted payment |
| Void | Reversed | No | Yes — counts as an attempted payment |
| Cancel Reservation | Aborted | No | Yes — counts as an attempted payment |
| Refund | Adjustment | No | No |
| Reversal | Adjustment | No | No |
| Authorization Release | Release | No | No |
| Terminal Tokenization | System | No | No |
| MOTO Tokenization | System | No | No |
| End Of Day | System | No | No |
How Revenue is calculated
Revenue is the total of Sales Completion and Direct Settlement transactions only. Every other transaction type — including Authorization, Void, and Cancel Reservation — is excluded, because no funds have actually settled for those.
How Completion Rate is calculated
Completion Rate compares how many attempted payments actually completed against the total number attempted. The types that count as a completed payment are Sales Completion and Direct Settlement; the types that count as an attempt (whether or not it completed) also include Authorization, Top Up Authorization, Void, and Cancel Reservation.
Authorization Release is deliberately left out of this calculation. It represents an authorisation hold expiring naturally — for example, because it was never captured — rather than a customer actively cancelling, so it isn't treated the same as a Void or a Cancel Reservation.
Refunds and reversals
Refund and Reversal transactions aren't included in the Revenue figure or Completion Rate — they're tracked separately as adjustments. They do appear as negative amounts in the standalone-adjustments view of Shift Reports, so you can still see their impact there.
System events
Terminal Tokenization, MOTO Tokenization, and End Of Day are non-payment system events — they don't represent money moving, so they're excluded from every financial figure on the Dashboard and in Shift Reports.
Why you won't see a payment counted twice
If a payment starts as an Authorization and later becomes a Sales Completion, it's counted once — as Sales Completion. You won't see the same payment reflected twice as it moves through its lifecycle.
Expected result
You can explain why your Revenue and Completion Rate figures include or exclude a given transaction, and where to look if you need to see the impact of a refund or reversal.
Need more help?
If a Revenue or Completion Rate figure doesn't match what you expect after checking this article, contact 934 Support through Help & Support in the Portal or at support@weare934.com with the property, date range, and the figure you're questioning.
Comments
0 comments
Article is closed for comments.