Custom Sync Schedule: How NeoTax normalizes to the full month
Custom Sync Schedule: How NeoTax normalizes to the full month
If your ASC 350-40 sync runs before the last day of the month, so you can close early, Neo.Tax still gives you a complete, full-month allocation for every person. Work that happens after the sync is not lost. It carries over into the next month automatically.
Short version:
- Normalization: Each person’s allocations for the month are based on the work captured up to the sync and scaled to cover the full month. You book a full month of cost.
- Carryover: Work that takes place after the sync in that month is added to the next month’s allocations.
- Nothing is double counted. Effort already booked in a closed month never moves and is never counted twice.
When this applies
This applies whenever your monthly sync starts before the month ends. For example, you might sync on October 28 to close on November 2 (see Close Process & Timeline).
If your sync starts on or after the first day of the next month, the sync sees the whole month and nothing carries over.
Part 1: Normalization to the full month
When the sync runs, Neo.Tax sees ticket activity up to the moment the sync starts. For an October 28 sync, that means from September 29 through October 28 (assuming the prior sync ran on September 28th).
To calculate allocations, Neo.Tax:
- Estimates the effort on each ticket for the month (see How Neo.Tax Calculates Allocation Percent).
- Adds up each person’s effort by project.
- Divides each project’s effort by that person’s total project effort for the month.
The result is each person’s share of the month on each project. The shares add up to a full month, minus any company-wide non-project time minimum your team has configured. A few uncaptured days at the end of the month don’t shrink anyone’s allocation, so you can apply a full month of cost.
Example: a consistent schedule never loses or gains days
Say your sync always starts 3 business days before month-end (month end – 3). Each sync then covers the business days since the previous sync:
Month Sync starts Sync covers Business days covered Business days in the month August Thu Aug 27 Jul 30 – Aug 27 21 21 September Mon Sep 28 Aug 28 – Sep 28 22 22 October Wed Oct 28 Sep 29 – Oct 28 22 22 Every sync covers exactly as many business days as its month. The last 2 business days that September’s sync didn’t see (Sep 29–30) are picked up by October’s sync. October’s last 2 (Oct 29–30) are picked up by November’s. Each month’s window is the month shifted a few days earlier, so no work is lost or counted twice.
This holds whenever your sync date is set as a number of business days before month-end. Holidays are left out of this example to keep it simple. Counts can differ in your first month on Neo.Tax or in a month where your sync date changes.
People who had no ticket activity on a project before the sync started have no project allocation for that month.
Part 2: Carryover into the next month
When the next month syncs, the earlier month is locked, so its numbers don’t change. Neo.Tax then looks back at the days after the earlier sync started:
- Tickets completed before the earlier sync started stay entirely in the earlier month. They are not counted again.
- Tickets completed after the earlier sync started, or still in progress, are re-estimated. Any effort that belongs to the end of the earlier month but wasn’t already booked there is added to the first open month.
- Effort already booked in the locked month is never moved or repeated. Only the difference carries forward.
Example: Priya’s ticket PAY-118, worked on before and after the October 28 sync
PAY-118 was started on October 21 and completed on November 3. It was still in progress when the October sync ran.
Oct 21–28 (in the October sync) Oct 29–30 (after the sync) Nov 2–3 Effort 6 days 2 days 2 days Booked in October November (carried over) November
- October close: 6 days. That’s all the October sync could see.
- November: 2 carried-over days + 2 November days = 4 days.
- Total: all 10 days are counted once. October stays exactly as you closed it.
If you connect more than one ticketing system (for example, Jira and GitHub), each system’s carryover is based on that system’s own last sync.
What this means for your close
- Your closed month is final. Carryover never reopens or changes a locked month.
- Each month includes a few days from the end of the month before. If your sync is always the same number of business days before month-end, each month covers exactly as many business days as the month itself.
- Annual totals are complete. Late-month work is booked one month later instead of being lost.
- A higher-than-expected month for one person often means they finished a large piece of work right after the prior month’s sync.
Frequently asked questions
Do I need to do anything to turn this on?
No. Carryover happens automatically whenever the prior sync ran before its month ended.
What if we sync after month-end?
Then the sync already saw the whole month. Nothing carries over, and each month contains only its own work.
Can I include all of the end-of-month work in the original month instead?
Yes, if the period isn’t locked yet. Contact your Neo.Tax customer success manager to re-run that month’s sync after month-end. The re-run recalculates the whole month, so nothing needs to carry forward.
Will editing allocations by hand affect carryover?
Carryover is based on ticket effort. Manual edits to a locked month stay as you made them.