What's New - March 2nd, 2026

Configurable Timesheet Week Start Day

Overview

You can now choose which day your agency’s timesheet week begins. This flexibility supports different operational schedules, payroll cycles, and global office preferences.
(Previously, Accountability always treated Monday as the start of the week.)

What is it?

A new setting—First day of week for timesheets—lets administrators define whether the week begins on Monday, Saturday, or any other day. Once selected, the system automatically adjusts how weekly time is displayed, submitted, and reported.

Why it matters

Agencies often follow different workweek structures. This enhancement:

Matches timesheets to real operational work cycles
Reduces employee confusion when entering weekly time
Aligns weekly reporting (e.g., Missing Timesheet Report, Weekly Time reports) with actual agency practice
Supports clients or offices with weekend‑based payroll or production schedules

How it works

Choose your week start day in Timesheet Options.
My Time automatically updates to show the correct sequence of days (e.g., Saturday → Friday).
Weekly navigation adjusts so selecting a date loads the correct week based on your chosen start day.
Working‑day shading stays the same employees still see their non‑working days clearly.
Existing submissions remain intact; new submissions follow the new week structure.

(Weekly timesheet behavior historically assumed Monday as the start of the week.)

When is it needed?

Use this option when:

Your agency’s operational week doesn’t start on Monday
Payroll or client schedules follow a weekend‑based week
You're onboarding clients from systems with alternative week structures
You want consistent week definitions across reports and submissions

Pop‑Up Message on Submission for GL Account Dissection

Overview

A new validation pop‑up now prevents users from submitting Journals and Supplier Invoices when required GL account dissection is missing. This enhancement ensures coding issues are caught early before items enter approval workflows saving time and avoiding unnecessary rejections.

What is it?

This update introduces a blocking pop‑up message that appears when a user attempts to submit a Journal or Supplier Invoice that requires department or GL dissection but has not been fully completed.

Previously, this validation occurred only at the point of posting. Now, it triggers upon submission as well, aligning the behavior with Posting and improving accuracy earlier in the workflow.

Why it matters

This enhancement delivers three key benefits:

Prevents avoidable approval delays
Approvers no longer receive items missing required dissections, which previously forced rejections and re‑submissions.
Improves data accuracy at the earliest point
Users are guided to correct GL/department coding before anything enters the approval pipeline.
Supports clean financial posting
Ensures supplier invoices including those created from expense claims are validated consistently with all other Supplier Invoices.

How it works

When a user clicks Submit on a Journal or Supplier Invoice, the system checks whether GL/department dissection is required.
If the required fields are incomplete, a blocking pop‑up message appears, preventing submission.
The behavior matches the existing validation shown during Posting.
Expense Claims remain excluded:
- Users do not select GL accounts on expense claims.
- Department assignment follows task‑type or employee default logic.
- Therefore, no dissection pop‑up appears on expense claim submission.

When is it needed?

This update is especially useful for agencies that:

Use multi‑step approvals for Journals and Supplier Invoices
Rely heavily on department‑level financial reporting
Want to reduce back‑and‑forth between preparers and approvers
Need consistent validation behavior across Posting and now Submission

Time Entry Required Notes (AutoSave Fix)

Overview

Some agencies require employees to enter notes on every timesheet entry. Previously, users could unintentionally bypass this rule because time would auto‑save when navigating between weeks saving hours without notes. This update closes that loophole and ensures required notes are always enforced.

What is it?

This enhancement updates how the My Time screen handles unsaved changes when notes are required:

Users can no longer move from one week to another without entering required notes.
The system now prompts the user before leaving the screen, preventing accidental auto‑save of incomplete entries.
Auto‑save no longer triggers when navigating directly to another page via the menu bar.

The change ensures note requirements are consistently applied during all types of navigation.

Why it matters

This fix addresses three important issues:

Stops accidental missing notes
Previously, time could be recorded without notes if a user switched weeks without hitting Save.
Prevents bad data from posting
Missing notes were only caught at submission, not auto‑save, which led to posted time with blank notes.
Supports agency compliance
For clients who require notes for audit, billing, or compliance reasons, this update ensures those requirements cannot be bypassed even unintentionally.

How it works

When notes are required and a user enters hours, then:
- Switching between weeks triggers a pop‑up reminding them that notes are required.
- They cannot leave the screen until they enter the notes.
When moving to another page through the main menu:
- The system no longer auto‑saves time entries, regardless of whether notes are required.
When notes are not required:
- Switching weeks still auto‑saves normally, without pop‑ups.
Submission rules remain unchanged:
- Users still cannot submit time without required notes.

When is it needed?

This update is especially important for agencies that:

Require notes for client billing or compliance
Have high time entry volume and want to avoid missing notes
Want consistent behavior between Save, Submit, and week‑to‑week navigation
Need to eliminate the risk of time posting without required notes

Company Credit Card Manual Match (Pending Submission Controls)

Overview

Employees can sometimes create Pending Submitted corporate credit card charges that never match to any real bank feed transaction. Previously, these items could not be deleted, unsubmitted, or adjusted creating confusion for employees and administrators because they didn’t appear in Manage Credit Cards or Approve Credit Cards, yet remained visible on the employee’s Corporate Credit Card screen.

This update introduces a fix that allows employees to fully manage and remove unmatched pending submissions.

What is it?

This enhancement adds the ability for employees to delete Pending Submitted corporate card charges when they cannot or will never match to an actual credit card transaction.

Before the update:

Pending Submitted charges were stuck.
They did not appear in admin screens (Manage or Approve).
There was no Reject, Unsubmit, or Delete option available.

After the update:

Employees can now delete their own unmatched pending submissions directly from their Corporate Credit Card screen.
These items no longer block workflows or remain indefinitely in a “limbo” state.

Why it matters

This improvement eliminates a significant workflow frustration:

Prevents clutter in employee credit card lists
Removes dead-end transactions that will never match
Improves data integrity by ensuring only valid submissions remain
Clarifies approval queues, since unmatched items no longer appear hidden from approvers

For agencies using direct bank feeds (e.g., Bank of America), this ensures that manually entered mistakes or duplicate pending entries don’t persist indefinitely.

How it works

If a Pending Submitted corporate credit card charge cannot match to a live bank feed transaction:
- The employee now sees a Delete option on their Corporate Credit Cards screen.
- Clicking Delete removes the pending submission immediately.
These items no longer appear in:
- Manage Credit Cards
- Approve Credit Cards
- Any approval workflow queues
This change does not affect legitimate pending items that do match to imported transactions. Those continue to auto-match and progress as normal.

When is it needed?

This update is valuable when:

An employee mistakenly creates duplicate or incorrect pending credit card entries
A manually entered pending charge will never match to the bank feed
Approvers cannot see a pending charge to reject or unapprove it
Agencies need employees to self-manage erroneous submissions without relying on admin intervention

Excel Export on Tax Codes Search Page

Overview

You can now quickly export your Tax Codes list to Excel, making it easier to review, share, and manage your tax setup outside the system. The export behaves just like other Excel downloads across the platform, providing a consistent and convenient experience.

(This aligns with the standard Excel export behavior used across reports.)

What is it?

A new Excel Export option has been added to the Tax Codes page. When you click the Excel icon, the system instantly downloads an Excel file containing the full list of tax codes or just the filtered results you’re currently viewing.

There is no import option on this page; the feature is designed purely for easy exporting.

Why it matters

This enhancement helps teams:

Review tax codes in a familiar Excel format
Share setup details with finance, compliance, or audit teams
Compare tax configurations between offices or test environments
Gather supporting information quickly when working with Support
Work more efficiently without having to take screenshots or manually rebuild lists

It’s a simple improvement that removes friction from everyday administrative tasks.

How it works

Go to the Tax Codes search page.
Apply filters if you only want to export part of the list.
Click the Excel icon to download your file.
Your Excel file is generated instantly using the same export functionality available in other areas of the system.
- (Exporting to Excel follows the same standard behavior used across platform reports.)

When is it needed?

You’ll find this especially useful when:

Reviewing or updating tax structures
Preparing for audits or year‑end reconciliation
Comparing tax setups across multiple environments
Sharing tax code information within your finance or operations teams
Providing documentation for onboarding or troubleshooting