Reference Codes for Tenants and Events
Move over, Prince! The feature formerly known as billing codes has been redesigned and revamped to rock your operational world. Reference Codes provide a flexible, efficient way to track multiple codes across Tenants and Events.
For universities and operators managing complex billing structures, Reference Codes makes it easy to associate structured, labeled codes with Tenants and Events — saving time, improving billing accuracy, and reducing reporting headaches.
Why This Matters
Billing codes have been one of the most heavily used fields in Offstreet and appear on the majority of Events. When only a single billing code field is available, teams were often forced into workarounds that introduce friction and risk:
- Concatenated codes — users string together multiple values with dashes or commas, which then have to be manually split in spreadsheets.
Before

After

- Duplicate Tenants — users create separate Tenants for each billing variation, which complicates setup and reporting.
Before

After

For parking teams
- Saves time on setup — no need to duplicate Tenants for each billing variation.
- Cleaner management — billing codes are clearly labeled and reusable.
- Flexible structure — support any number of fields without engineering changes.
For finance & billing
- Accurate reports — structured data eliminates manual parsing of concatenated fields.
- Faster reconciliation — each billing code appears as its own column, ready for import.
- Fewer errors — reduces the risk of mismatched or missing billing details.
For departments
- Transparency — billing codes map directly to department budgets.
- Confidence — less back-and-forth over whether charges were allocated correctly.
How it works
Reference Codes allow you to store several billing-related values (for example, Dept #, Fund #, Account #, Grant #) as separate, labeled fields. Each label becomes its own column in reports - giving admin and finance teams clean, structured data to work with.
Reference Codes can be configured at two levels:
- Tenant-level — define reusable billing structures that apply to any permit or registration using that Tenant.
- Event-level — customize codes for a specific Event.
In most cases, Tenant-level codes can provide the default billing structure, while Event-level codes can be used for one-off exceptions or special cases.
Setting up Tenant-level Reference Codes
Setting up Event-level Reference Codes
What could I use this for?
Universities
- Track multiple fields such as Dept #, Fund #, Account #, Grant #, and UID or project codes.
- Track unique event codes without clunky workarounds
- Map parking charges directly to departmental budgets.
- Reduce reconciliation delays caused by mismatched or incomplete billing details.
Operators
- Track cost centers, client-specific billing references, or internal location codes.
- Use custom labels that align with each client’s internal billing structure.
- Avoid creating multiple Tenants for the same client just to track different billing combinations
FAQS
Can I customize the labels?
Yes. Labels are fully customizable and can be named to match your organization’s billing structure.
Is there a limit to how many billing codes I can add?
No. You can add as many labeled billing codes as you need for a Tenant or Event.
Do Tenant-level codes automatically apply to all permits and registrations?
Yes. Tenant-level billing codes will appear by default on any permits or registrations created using that Tenant.
What happens to the tenant identifiers and billing codes I already have setup?
Existing codes will be automatically converted to Reference Codes. The Title becomes the Label and the Identifier becomes the Reference Code.
Will this change how reports look?
Yes. Instead of a single concatenated field, each reference code appears as its own column in your reports, labeled according to the names you configured.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article