Neo.Tax Help Center

ASC 350-40 matching & capitalization settings

What each ASC 350-40 Matching Settings option does, how it changes the capitalizable pool, and how to choose a setting for your company.

What are the matching settings?

These settings determine how much of your team’s work is eligible for capitalization, and how conservative the attribution is.

There is no single correct configuration. The right choice depends on your goals for capitalization, your prior capitalization level, how clean your ticketing data is, and how the results compare to the method you used before Neo.Tax.

Settings changes take effect on the next sync. They only apply to new work being matched. Tickets already assigned to a project are not re-matched.

Setting What it controls More capitalization Less capitalization
Ticket Group Level Which level of your ticket hierarchy is treated as a group — —
Matching Aggressiveness The confidence level a match needs before it is applied More aggressive More conservative
Match Parentless Tickets Whether tickets outside a group can be matched Match Don’t Match
Workstreams to Exclude Jira projects, Linear teams, or repos that are never matched Fewer exclusions More exclusions
Minimum Non-Project Time The share of each person’s month that is always reserved for non-project time Lower minimum Higher minimum

Ticket Group Level

The ticket group level is the level of your ticket hierarchy that Neo.Tax treats as a single unit of work, for example EPIC. Each group is matched to at most one capitalizable project, and every ticket inside the group follows it to that project.

Choose the level where your teams consistently organize work around a single initiative. For most Jira customers this is the Epic.


Matching Aggressiveness

Every match Neo.Tax makes comes with a confidence level: how certain the system is that the work belongs to that project. You can see the confidence level and the reasoning for each match in the Project drawer.

Matching Aggressiveness sets the confidence threshold a match must meet before it is applied to a capitalizable project.

The two options

More conservative: highest-confidence matches only. Work is attached to a capitalizable project only when the match is high confidence: the ticket group’s name, description, and team clearly line up with a single project. Anything less certain is routed to the workstream’s Miscellaneous/Ops project. This favors precision. What is capitalized is very likely to be correct, but some genuine project work will be left out.

More aggressive: high- and medium-confidence matches. Work is attached when the match is high confidence or medium confidence: the work plausibly belongs to the project but the signal is weaker, for example a vague epic name or a description that fits more than one project. This favors recall. More real project work is captured, at the cost of some matches that a reviewer may want to move.

How it affects capitalization

At the margin, More aggressive attaches more work to capitalizable projects, which increases capitalization. The extra work comes entirely from medium-confidence matches that More conservative would have sent to Miscellaneous/Ops. Nothing that matches under More conservative is lost when you switch to More aggressive.

Which should I choose?

The recommendation depends on two things:

  1. Your target capitalization. If you have a capitalization rate or dollar amount you expect to land near (for example, based on prior periods or your auditor’s expectations), compare the results of each option to it.
  2. Your baseline matching results compared to your prior method. Run a sync and compare the capitalized amount to what your previous method (spreadsheets, manager surveys, or time tracking) produced for the same period.

As a rule of thumb:

  • If More conservative results come in below your prior method or target, switch to More aggressive to capture project work that is being routed to Miscellaneous/Ops.
  • If results are in line with or above your prior method or target, stay on More conservative to keep the most defensible set of matches.
  • If you choose More aggressive, review a sample of the medium-confidence matches each period. Moving a ticket or epic to the correct project teaches the system and improves future matches for your account.

Match Parentless Tickets

A parentless ticket is a ticket that does not belong to a ticket group, for example a Story or Task with no parent Epic. In most ticketing systems a meaningful share of real project work is logged this way, because ticketing hygiene varies across teams and individuals.

The two options

Don’t Match: epics (ticket groups) only. Only ticket groups are matched to capitalizable projects. Every parentless ticket is routed to its workstream’s Miscellaneous/Ops project, regardless of what the work is. This keeps attribution tied to how your teams organized the work, but it limits the pool of work available for capitalization to tickets that sit inside an epic.

Match: include individual tickets. Parentless tickets are also matched, using one of two approaches depending on the workstream:

  • Workstreams that have ticket groups: each parentless ticket is matched on its own, and can only be assigned to a capitalizable project that ticket groups in the same workstream have already matched to. A stray ticket on a team that is building Project A can join Project A, but it can’t start a new, unrelated project.
  • Workstreams with no ticket groups: the workstream is treated as one unit and matched to the single best project as a whole.

In both cases, only feature work is eligible. Maintenance, bug fixes, and operational tickets are routed to Miscellaneous/Ops.

How it affects capitalization

Match is the more aggressive option. It considers all tickets, not just those in epics, so it can only increase the amount of work attached to capitalizable projects. Don’t Match is more conservative and limits the available capitalization pool.

Which should I choose?

Most companies should choose Match. Ticketing hygiene is rarely consistent across every team: some engineers file everything under an epic, others log project work as standalone tasks. With Don’t Match, capitalization depends on filing habits rather than the work itself, and a team that skips epics will appear to have no capitalizable work.

Choose Don’t Match if your teams reliably put all project work under epics, or if you want the most conservative possible attribution.


Workstreams to Exclude from Matching

A workstream is a team-level container in your ticketing system: a Jira project, a Linear team, or a GitHub/GitLab repository. Use Workstreams to Exclude from Matching to keep specific teams or projects in your ticketing system out of capitalization entirely.

Tickets in excluded workstreams are:

  • Never matched to a capitalizable project, regardless of the Matching Aggressiveness or Match Parentless Tickets settings.
  • Still effort-estimated and assigned to the people who worked on them, so each person’s allocation stays complete.
  • Always routed to the workstream’s own Miscellaneous/Ops project.

When to exclude a workstream

Exclude workstreams whose work should never be capitalized, for example:

  • IT, help desk, or internal tooling support
  • Customer support or escalation queues
  • SRE, on-call, or incident management
  • Data requests, reporting, or other operational queues

Excluding these is the most reliable way to keep non-capitalizable work out of capitalizable projects. It works regardless of how individual tickets are written.

How to exclude a workstream

  1. Click Select workstreams to exclude.
  2. Choose each Jira project, Linear team, or repository to exclude.
  3. Save. The exclusion applies from the next sync.

Excluding a workstream (a team or project in your ticketing system) is different from excluding a capitalizable project (an entry on your project list). To stop new work from being matched to a specific capitalizable project, turn off its Next Sync Matching toggle instead. See Match projects for ASC 350-40.


Minimum Non-Project Time

Not all of a person’s month is spent on project work. Meetings, planning, code review, hiring, training, and administrative work rarely show up as tickets. Minimum Non-Project Time reserves a fixed share of every person’s month for this work before any time is allocated to projects.

How it works

The minimum applies to every person, every month. For example, with a 10% minimum:

  • 10% of each person’s month is assigned to non-project time.
  • The remaining 90% is distributed across that person’s projects, capitalized and expensed, based on their ticket activity.
  • No one can be more than 90% capitalized in any month.

If a person has no tickets with effort in a month, 100% of their month is non-project time, regardless of the minimum.

Each person’s time always totals 100% across non-project time, capitalized projects, and expensed projects.

How it affects capitalization

The minimum sets a ceiling on capitalization: a person can be at most 100% minus the minimum capitalized. A higher minimum lowers capitalization for everyone whose work is mostly on capitalizable projects. A lower minimum (or none) allows more capitalization. People who already have substantial expensed or non-project work are affected less, or not at all.

Which should I choose?

  • If your prior method assumed a fixed share of time for meetings and overhead (for example, “engineers spend at most 85% of their time on projects”), set the minimum to match it so your results stay comparable.
  • If your auditors expect an explicit allowance for non-project activity, a minimum gives you a documented, consistently applied control.
  • If you have no prior assumption, you can leave it unset. Time without project tickets is still assigned to non-project time.

To set or change the minimum, contact your Neo.Tax team. It takes effect from the next sync.


Capitalization Status Custom Fields (Jira only)

If your team already tracks capitalization status on Jira tickets with a custom field, Neo.Tax can use that field directly. This option is only available for companies with a single Jira integration.


For most companies we recommend starting with:

  • Ticket Group Level: Epic
  • Matching Aggressiveness: start with More conservative, then switch to More aggressive if results fall short of your prior method or target
  • Match Parentless Tickets: Match
  • Workstreams to Exclude: support, IT, SRE, and other teams that never do capitalizable work
  • Minimum Non-Project Time: match the overhead assumption in your prior method, if it had one; otherwise leave it unset

Your Neo.Tax team will review the first sync with you and help tune these settings against your target.


Still have questions? Reach out to your Neo.Tax contact or email support@neo.tax.

Esc
↑ ↓ to move Enter to open