The equity platform entry that never ties out

Neither NetSuite nor Acumatica documents a stock-based compensation module. Not a gap in your configuration, not something a consultant failed to switch on. There is no module.

That single fact explains something people usually assume is their own fault: the equity expense journal is manual at every company you have worked at, and it has been manual at every company anyone you know has worked at. It is manual because the ledger has nowhere to put grant data, and the cap table platform has no reason to produce a journal shaped like your chart of accounts.

What each side actually holds

The equity platform holds grants, tranches, vesting schedules, exercises, cancellations, and a fair value per grant. It can usually produce an expense report by period. That report is correct, and it is not a journal.

The ledger holds accounts, departments, classes, and locations. It can import a journal. What it cannot do is take a grant register and derive one.

Between those sits the thing everyone builds: a workbook that reads an export, applies a departmental split, sums to a set of accounts, and produces something you can paste into an import template. That workbook is the system of record for a number in your financial statements, and it usually belongs to one person.

Why it drifts

Four reasons, in roughly the order they bite.

The export changes shape. A platform upgrade adds a column, renames another, or changes how cancellations are represented. The workbook keeps working and starts being subtly wrong, because a lookup that used to match now matches something else.

Departments come from somewhere else. The equity platform knows who holds a grant. It usually does not know, or does not reliably know, which cost centre they sit in this month. That mapping lives in the HR system, and the workbook holds a copy of it that was accurate when it was pasted.

Corrections are retrospective. A grant date is amended, a vest is backdated, a cancellation is processed late. The platform restates its own history cleanly. The workbook has already produced eight journals from the old version.

Nobody reconciles it forward. The check that gets done is usually "does this period look reasonable". The check that catches drift is "does cumulative expense per grant, per the ledger, equal cumulative expense per grant, per the platform". That second one is rarely done because in a workbook it is genuinely hard.

What tying out actually requires

Not a better spreadsheet. Three structural things.

Tranche-level attribution. Expense attaches to a tranche, not to a grant. A four-year grant with a one-year cliff and monthly vesting thereafter is not one schedule, and treating it as one is what makes forfeitures messy later.

Effective-dated department assignment. Not who is in which department now, but who was in which department in each period. That is what makes a mid-year move produce two correct allocations instead of one wrong one.

A rollforward that closes. Opening balance, additions from new grants, expense for the period, reversals from forfeitures, closing balance. If that statement does not tie without adjustment, something upstream is wrong and the rollforward is the thing that tells you.

The realistic path

You are not going to get a module, because neither vendor ships one. The choice is between a workbook and a purpose-built layer that sits between the platform and the ledger.

What that layer has to do is narrow: read grant and tranche data, hold effective-dated assignments, apply attribution, produce the journal, and keep the rollforward. It does not need to price options, because the platform does that. It does not need to be an equity administration system, because you already have one.

Its actual job is to make the number reproducible. Two years from now, somebody will ask why the September figure was what it was. The answer should be a query, not an archaeology exercise.