Billing raised item tracker item properties are the configurable fields that define what a raised billing item tracks, such as its type, amount, status, and associated account or invoice. These properties determine how the tracker behaves, what data it captures, and how it integrates with your billing workflow.
What Is a Raised Item Tracker?
A raised item tracker is a tool used in billing systems to monitor items that have been added or “raised” after an initial invoice or order. It is common in subscription management, professional services, and utility billing, where charges can change mid-cycle. The tracker logs each raised item, its properties, and its lifecycle—from creation to payment or adjustment.
For example, a SaaS company might raise an item for extra storage a customer purchased mid-month. The tracker records the item’s name, quantity, price, and the date it was raised, then feeds that into the next invoice.
Core Item Properties
Every raised item tracker has a set of standard properties. These are the fields you’ll see most often:
- Item ID – a unique identifier for the raised item.
- Item Type – the category, such as product, service, fee, or discount.
- Description – a human-readable label or note.
- Quantity – the number of units.
- Unit Price – the cost per unit.
- Total Amount – quantity times unit price, plus any taxes or adjustments.
- Status – e.g., pending, approved, invoiced, paid, or voided.
- Raised Date – when the item was added.
- Effective Date – when the charge applies (useful for proration).
- Associated Account or Invoice – the customer or document the item belongs to.
These properties are the backbone of the tracker. Without them, you can’t report on or reconcile raised items.
How Item Properties Are Used
Properties aren’t just for display—they drive logic. For instance:
- Proration: The effective date and quantity let the system calculate a partial charge for a mid-cycle addition.
- Approval workflows: Status determines whether an item needs manager approval before it’s added to an invoice.
- Revenue recognition: Item type and effective date help finance teams recognize revenue in the correct period.
- Audit trails: Raised date and user ID (if tracked) provide a history of changes.
In a well-designed tracker, each property is a column in a database table or a field in an API object. That structure allows you to query, filter, and export the data.
Custom vs. Default Properties
Most billing platforms let you add custom properties beyond the defaults. Defaults cover the basics; custom fields handle your unique needs. For example, a law firm might add a “matter number” property, while a hosting company might add “server region.”
When deciding which properties to include, think about:
- What reports do you need? (e.g., by client, by product line)
- What calculations must be automated? (e.g., tax, commission)
- What compliance requirements exist? (e.g., audit fields)
Too many properties create clutter; too few limit flexibility. Start with the core set and add only what you’ll actually use.
Common Problems and How to Avoid Them
Even with good properties, issues arise. Here are frequent pitfalls:
- Duplicate items: Without a unique ID, the same charge may be raised twice. Always enforce a unique identifier.
- Inconsistent statuses: If statuses aren’t standardized, reports break. Use a fixed list (pending, approved, etc.) rather than free text.
- Missing effective dates: Proration fails if the effective date is blank. Make it required.
- Currency mix-ups: If you operate in multiple currencies, store the currency code as a property.
A common misconception is that the tracker itself calculates taxes. In most systems, taxes are applied later, at invoice generation, using the item’s total amount and tax rules. The tracker just stores the raw data.
Choosing the Right Tracker for Your Needs
Not all trackers are equal. When evaluating one, consider:
- Integration: Does it connect to your invoicing and accounting software?
- API access: Can you programmatically read and write item properties?
- Reporting: Can you build custom reports on the properties?
- Scalability: Will it handle thousands of raised items without slowing down?
For small businesses, a spreadsheet might suffice. For larger operations, a dedicated billing module is better. The key is matching the tracker’s complexity to your actual volume and reporting needs.
Template for Tracking Raised Items
Below is a generic template you can adapt. It includes the essential properties as columns.
| Item ID | Item Type | Description | Quantity | Unit Price | Total Amount | Status | Raised Date | Effective Date | Account/Invoice # |
|---|---|---|---|---|---|---|---|---|---|
Sample (fictional): Item ID: ITM-1042 | Type: Service | Description: Extra support hours | Qty: 3 | Unit Price: $50.00 | Total: $150.00 | Status: Approved | Raised: 2025-03-14 | Effective: 2025-03-15 | Acct: INV-2091
Copy the table into a spreadsheet or database. Adjust the columns to fit your business.
Frequently Asked Questions
Can I change an item’s properties after it’s been raised?
Yes, but it depends on the system. Some trackers allow edits only while the status is “pending.” Once invoiced, changes require a credit or new item. Always check your platform’s rules.
How do I handle refunds or cancellations of raised items?
Typically, you create a negative item (a credit) with the same properties but a negative amount. The tracker then shows a net total. Some systems have a “void” status instead.
What’s the difference between a raised item and a line item?
A line item is part of an original invoice. A raised item is added after that invoice—either as an adjustment or a new charge. The tracker specifically monitors these post-invoice additions.
Do I need a separate tracker for each type of item?
Not necessarily. A single tracker with an “item type” property can handle all types. Separate trackers are useful if different types have very different properties (e.g., one for products, one for hourly services).
How long should I keep raised item data?
Keep it as long as your accounting records require—often 7 years for tax purposes. Check local regulations. After that, archive or delete to save storage.
Alternatives to a Dedicated Tracker
If your billing system lacks a built-in tracker, you can use:
- Spreadsheets – simple, but error-prone with high volume.
- Accounting software add-ons – many tools have modules for adjustments.
- Custom database – full control, but requires development.
Each has trade-offs. Spreadsheets are fine for a handful of items; a database is better for scale. Choose based on your volume and need for automation.