About Notabene

Notabene is building infrastructure that's transforming how money moves in the digital economy. We're evolving beyond our compliance foundations to enable the next generation of digital financial services between regulated institutions with unprecedented efficiency. With nearly 50 employees across 14 countries and having recently closed our Series B round last November with support from leading investors including Y Combinator, DRW, F-Prime, Jump Capital, Castle Island, and Green Visor Capital, we're looking for people like you to help shape the future rails of the crypto industry.

Location

US-based, Remote East Coast. Candidates in the NYC area have a hybrid option.

The impact you will have

Notabene is planning on going through its first external financial statement audit, covering the fiscal years ending January 2026 and January 2027. You will own that process. You will also own the close, the books, and the accounting policy for a two-entity, multi-currency business whose revenue includes subscription fees, usage-based transaction billing, and a payments network take rate that has no clean accounting precedent anywhere.

The accounting function is already substantially built. Close runs, the books are in order, and readiness work for the audit is well underway. What we need is someone to own it, finish it, and take it through the audit, while raising the standard on policy and documentation as the business gets more complex. You will be the most senior accounting voice in the company, reporting to the VP of Finance, with one direct report and a set of external providers. You will not have a large team before late 2027, and that is deliberate. Capacity here comes from better systems and better automation, and you will be the one deciding what those look like.

Within a year you are successful if

Notabene has a clean audit opinion on both fiscal years, with no material weaknesses and no second cycle on auditor requests

The close hits its calendar consistently, starting with the revenue close landing on time

Revenue recognition is documented in a written memo that stands up in fieldwork, rather than living only in the billing system configuration

Multi-entity consolidation and FX translation run cleanly enough to survive audit scrutiny, with intercompany and CTA tied and supported

Payroll allocation across departments and software development capitalization are written policy applied consistently, not judgment applied after the fact

Key accounting controls are documented, operating, and evidenced

At least two accounting processes that are manual today run without a person in the loop, and still hold up under audit

What you will be doing

Audit. Run the readiness assessment, build the remediation plan, contribute the technical view on which firm we engage, and then own the auditor relationship day to day.

Close and reporting. Own the monthly, quarterly, and annual close across Notabene Inc. and Notabene GmbH. Produce GAAP financial statements, consolidations, intercompany eliminations, and FX translation under ASC 830.

Technical accounting. Write the positions and the memos. ASC 606 across three revenue models, ASC 350-40 for internal-use software capitalization, ASC 718 for stock compensation expense, and whatever emerges as stablecoin payment revenue matures.

Revenue and billing systems. Own Tabs as the billing and revenue system of record, including contract configuration, usage data integrity, and the bridge from Tabs to the general ledger.

Cost accounting. Build the payroll allocation method for people whose work splits across functions, and the capitalization policy for development work, so departmental margin reflects where effort actually goes.

Controls. Design and implement controls over revenue, cash, procure to pay, and payroll. Not SOX. Controls that operate, are evidenced, and can be walked by an auditor.

Automation. Evaluate the accounting stack and the processes running on it with a bias toward automation, including agentic tooling where work is rule-bound and high volume. Categorization, reconciliation matching, usage validation, and collections follow-up are the obvious places to start.