Commercial Profile
Currency, platform fee, tax identity, and payout country — the money rules behind every Order
The commercial profile is where an Organization declares how it charges. It decides which currency a Pass is priced in, how tax is split, how much Ulsav keeps, and which country receives the payout.
Set it before you publish a priced Event. The preferred currency locks after the first paid Order; every other field stays editable, and each Order keeps the values it was priced with.
The defaults you start with
Currency
INR
Three-letter ISO code
Platform fee
3.5% + ₹10
350 bps plus 1,000 minor units
Fee bearer
Buyer
Buyer pays the fee on top
Tax
IND, 18%, exclusive
1,800 bps added to the price
A free Event ignores both.
What each field controls
| Field | Rule | Used for |
|---|---|---|
| Preferred currency | A valid three-letter currency code | Every Pass price, Order total, refund, invoice |
| Platform fee (bps) | 0 to 10,000 basis points | Ulsav's percentage cut per line |
| Platform fee (fixed) | Zero or more minor units | Ulsav's flat cut per unit |
| Fee bearer | Buyer or organizer | Whether the fee is added to the buyer total or deducted from your net |
| Tax country | Three-letter country code | Chooses the tax engine and the invoice format |
| Tax state | Two letters, or an Indian state code | Chooses intra-state versus inter-state tax |
| Tax city | Up to 120 characters | Printed on invoices |
| Tax identifier | Up to 32 characters | Your GSTIN or local equivalent |
| Tax rate | 0 to 10,000 basis points | The rate applied to the taxable base |
| Tax inclusive | On or off | Whether displayed prices already contain tax |
| Payout country | Three letters, optional | Where settlement is sent |
Empty values fall back to INR, buyer, and IND, so a half-configured Organization behaves predictably instead of failing at checkout.
The currency locks
You can change the preferred currency freely until the first confirmed paid Order. After that, the currency is fixed.
| Attempt | Result |
|---|---|
| Change currency before any paid Order | Allowed |
| Re-send the same currency | Allowed, no-op |
| Change currency after a paid Order | Rejected as invalid |
Past Orders and invoices keep their original currency, so a switch would leave the ledger adding amounts that do not belong together.
Event-level currency does not exist: Passes denominate in the Organization's currency, and a different one is rejected rather than converted.
Who can change it
Editing needs the Organization-update Capability. The three fee fields need the Owner Role, because they decide how much Ulsav keeps; tax identity, tax rate, and payout country do not.
A worked example
Vidyut sells a ₹2,000 pass in Karnataka, same-state venue, 18% exclusive tax, fee borne by the buyer.
Pass price (P)
₹2,000.00
GST at 18% (T)
Same state, so it splits into CGST 9% and SGST 9%
₹360.00
Platform fee: 3.5% of ₹2,360
₹82.60
Fixed fee per unit
₹10.00
GST on the fee at 18% (G)
₹92.60 × 18%, rounded to the nearest paisa
₹16.67
Buyer pays (B)
₹2,469.27
Amounts in rupees. P is the price, T the tax, F the platform fee (3.5% of the taxed subtotal plus ₹10), and G the 18% tax on the fee.
With the fee borne by the organizer, the buyer pays ₹2,360 and the Organization nets ₹2,250.73.
How tax is decided
The tax engine looks at two states: yours and the Event's.
| Situation | Result |
|---|---|
| Indian Organization, online Event | Intra-state split: CGST plus SGST, or CGST plus UTGST in a union territory |
| Indian Organization, same-state venue | Intra-state split |
| Indian Organization, different-state venue | Inter-state: IGST at the full rate |
| Indian Organization, venue state missing | Generic single tax until a state is supplied |
| Indian Organization, your own tax state missing | Generic single tax, even for an online Event |
| Non-Indian Organization | Generic single tax at the configured rate |
A paid in-person Event in India cannot publish without a venue state, because the place of supply would be unknown. Online Events never need one.
The rate is the same in every mode; the name and the split change, which is why an invoice can say IGST where a cart said "tax".
What readers get wrong
- The fee is charged per unit. Two passes mean two fixed fees, not one.
- The fee is taxed. In India the platform fee carries its own 18% GST, and that amount is part of the buyer total when the buyer bears the fee.
- Inclusive pricing moves the base. The displayed price already contains tax, so the taxable base is derived from it.
Related
- Pricing and tax — the same rules written as reference
- Passes — what the currency applies to
- Orders — where the fee and tax become final amounts
- Organizations — the rest of the workspace settings