What's New - January 12, 2026

Dissection Validation on GL Accounts

Overview

We’ve introduced Dissection Validation on GL Accounts to help ensure financial data is entered completely and accurately before it’s posted. This update adds automatic checks during posting to prevent invoices, journals, or supplier payments from being recorded without the required dissections.

What is it?

Dissection Validation is a new control that enforces required accounting dimensions such as Department, Employee, Client, Job, or Task Type based on the GL account being used.

If a GL account is marked as requiring one or more dissections, the system now validates that those fields are completed before allowing the transaction to post.

Why it matters

Incomplete dissections can lead to inaccurate reporting, rework, and compliance issues. This update helps by:

• Preventing postings with missing required information

• Making validation rules consistent across invoices, journals, and payments

• Clearly explaining what’s missing and why posting is blocked

The result is cleaner data and fewer downstream corrections.

How it works

When you post a transaction, the system checks each line’s GL account:

• If the GL account is configured to require specific dissections (such as Department or Employee), the system validates that those values are populated.

• If one or more required dissections are missing, posting is blocked.

• A clear, user-friendly message explains exactly what’s required.

Example error message:

"Invoice 123456 could not be posted – GL Account No. 70034 requires Department dissection"
"Invoice 123456 could not be posted – GL Account No. 70034 requires Employee dissection"

If multiple dissections are missing, all required messages are shown at once so issues can be resolved in a single step.

This validation applies consistently to:

• Supplier Invoices

• Journals

• Supplier Payments

When is it needed?

This feature is especially useful if your organization:

• Enforces strict financial reporting by department, client, job, or employee

• Uses different GL accounts with different dissection requirements

• Wants to prevent incomplete or inconsistent postings at the source

Once configured, this is a one-time setup that continues to protect data quality automatically.

---

 

Show Insertion Month on Receivables Aging Report

Overview

We’ve added the ability to display the Insertion Month (Media Month of Service) on the Receivables Aging Report. This enhancement is designed to better support media agencies that prioritize collections and payments based on the month media runs, rather than just invoice dates.

What is it?

The Receivables Aging Report can now include a new column showing the Insertion Month, derived from the media insertion date. This allows agencies to clearly see when the media activity occurred for each receivable.

If an invoice includes media activity spanning multiple months, the system will display “Various” as the Media Month of Service.

Why it matters

Media agencies often manage cash flow and collections based on insertion month, especially when:

• Pre-billing clients for future media inventory

• Tracking when vendor payments are likely to become due

• Reviewing aging balances where invoice numbers alone don’t indicate the service period

This update helps agencies:

• Prioritize collections more effectively

• Align AR activity with media delivery periods

• Provide clearer statements to advertisers

While agencies transitioning from Mediaocean Ad Serve ERP have been the most vocal about this need, the feature also benefits other media-focused organizations such as Billups.

How it works

• The system determines the Media Month of Service based on the insertion start date.

• For insertions with a date range (for example, January 1–March 31), the Media Month of Service will be the starting month (January in this case), regardless of billing cycle type.

• If multiple months exist on a single invoice, the Media Month of Service will display as “Various.”

• The new column appears on the Receivables Aging Report and can also be included at the end of exported files.

This approach ensures consistency while keeping the report clear and actionable.

When is it needed?

This feature is especially useful if your organization:

• Buys or manages media on behalf of clients

• Pre-bills media to secure funds ahead of vendor payments

• Needs AR visibility by media service period rather than invoice date

For non-media agencies, the column will simply appear as an additional informational field and will not disrupt existing workflows.

 

---

 

Exclude Employees from Daily Working Times

Overview

We’ve added new flexibility to Daily Working Times by allowing specific employees to be excluded, even when the feature is enabled at the office level. This supports organizations with exempt employees who are not required to record start/end times or breaks.

What is it?

A new configuration option allows you to exclude individual employees from Daily Working Times using a simple designation. When an employee is marked as excluded, the Daily Working Times section will no longer appear for them, even if it’s required for their office.

Why it matters

Some organizations, have employees who are exempt from time tracking requirements. Previously, Daily Working Times could only be enabled or disabled at the office level, which meant:

• Exempt employees still saw time entry sections they didn’t need

• Additional confusion and unnecessary steps for certain roles

This update ensures that time tracking requirements can be applied more accurately and fairly, employee by employee.

How it works

• Daily Working Times continues to be controlled at the office level.

• If an employee is designated with “Exclude from Daily Working Times”, the system will override the office setting for that employee.

• For excluded employees, the Daily Working Times section will not appear in My Time.

• All other employees in the office will continue to see and use Daily Working Times as normal.

This approach mirrors existing configuration patterns, keeping setup simple and consistent.

When is it needed?

This feature is ideal if your organization:

• Has exempt or salaried employees who don’t track detailed working times

• Operates in regions or roles where breaks and start/end times aren’t required

• Wants cleaner, role-appropriate time entry especially for mobile users