Senior Manager, Revenue Accounting and Billing Operations

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include boilerplate like EEO, etc. Must preserve all substantive info. We need to parse the posting. Company Overview: maybe not needed as a heading? The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include sections only if posting has real specific content for them. We have "About The Role" section: we can map to

About the role

with paragraph(s) containing that content. Then "Key Responsibilities": map to Responsibilities. Then "Basic Qualifications": map to Requirements? Or Qualifications? The instruction says Requirements and Qualifications separate headings. Usually Basic Qualifications go under Requirements or Qualifications. Preferred Qualifications go under Qualifications? We'll need to decide. We have "Basic Qualifications" list and "Preferred Qualifications". Could treat Basic Qualifications as Requirements, Preferred as Qualifications. Or combine? The instruction: Prefer a few substantive sections over many thin ones. But we need to follow headings list. We'll include Requirements (basic) and Qualifications (preferred). Also Skills maybe from "Advanced proficiency with financial systems..." etc. Could be part of Requirements. But we have a Skills heading; maybe we can extract skills from the posting: "Advanced proficiency with financial systems (NetSuite, NetSuite ARM, Salesforce) and advanced Excel skills", "Demonstrated proficiency with AI tools (Claude, ChatGPT, Copilot)", "Strong written and verbal communication skills". Could put under Skills. Benefits: The posting includes a paragraph about benefits: "ID.me offers comprehensive medical, dental, vision, health savings account, flexible spending accounts..., basic and voluntary life and AD&D insurance, 401(k) with company match, parental leave, ability to participate in unlimited paid time off..., short and long-term disability insurance, accident and critical illness insurance, referral bonus policy, employee assistance program, pet insurance, travel assistant program, wellbeing and childcare discounts, benefit advocates, and a learning and development benefit." That's substantive. So Benefits section. Pay: The posting includes "U.S. Pay Range $150,509—$167,845 USD Mountain View, CA Pay Range $176,333—$199,070 USD". Also mention base salary does not include bonus etc. So we have pay info. So Pay section. Schedule: The posting includes "This position works from one of our offices Mountain View, CA, McLean, VA, New York. NY office five days per week." Also earlier: "ID.me is a full-time, in-office culture. Unless a specific job description explicitly states otherwise, all roles are on-site five days per week at one of our offices in McLean, VA; Mountain View, CA; New York City, NY; or Tampa, FL." So schedule: full-time, in-office, five days per week. So we can include Schedule section. We must not include boilerplate like EEO, privacy, etc. Also must not include application instructions. We must preserve all substantive information; do not invent or summarize away detail. So we need to include the details from About the role, Responsibilities, Requirements (basic qualifications), Qualifications (preferred), Skills (maybe we can extract), Benefits, Pay, Schedule. We must not repeat job title as heading. So no heading for Senior Manager, Revenue Accounting & Billing Operations. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Skills

• ...
...

Benefits

• ...
...

Pay

...

Schedule

...

We need to ensure we don't include filler like "commensurate with experience". Not present. We must preserve all substantive info. Let's extract. About the role paragraph(s): The posting has multiple paragraphs under "About The Role". Let's capture them. From the text: "ID.me is looking for a Senior Manager, Revenue Accounting & Billing Operations to own our revenue and billing function end-to-end as we scale toward IPO readiness. Reporting directly to the Senior Director of Accounting & Financial Operations, you'll own the full order-to-cash cycle — from how a deal is structured and booked in Salesforce, through usage capture and invoicing, to revenue recognition, deferred revenue, AR, and the monthly close. This is a builder role for someone who wants to fix the system, not just operate it. This is a builder's role. We've grown quickly across multiple verticals, and there's real opportunity now to design the billing and revenue infrastructure that carries us through our next stage of scale. You'll lead that build: automating billing vertical by vertical, partnering with Revenue Operations and the Salesforce team to get data right at the source, and working with the Data team to own the integrity and efficiency of the billing data pipeline. You'll also work directly with the leadership team to get full value from the finance systems we already own, and to design the data structure that makes reporting, analysis, and operating metrics automatic rather than assembled by hand. If you like leaving a process meaningfully better than you found it — and having the autonomy and support to do it — this is that role. You'll lead a team of three and be expected to bring ideas and then execute them. We want someone who is proactive, comfortable getting into the weeds of a usage file or a Salesforce field definition, and equally comfortable presenting a recognition position or an automation roadmap to leadership. Deep experience with revenue recognition in a usage-based or consumption-based billing model is essential; this is the core complexity of our business. This position works from one of our offices Mountain View, CA, McLean, VA, New York. NY office five days per week." We can keep that as paragraph(s). Might split into two paragraphs for readability but not required. Responsibilities: Under "Key Responsibilities". There are bullet-like sentences but not formatted as list. We need to convert to

• . Let's extract each responsibility sentence. The text: "Own the end-to-end revenue and billing cycle Own the full order-to-cash cycle — deal booking and contract intake, usage and consumption data capture, invoicing, collections support, revenue recognition, deferred revenue, and AR — across all verticals and product lines. Own revenue recognition for usage-based arrangements, including variable consideration, minimum commitments and overages, tiered and volume pricing, true-ups, and breakage, and author the ASC 606 memos that document and support those positions. Own the monthly and quarterly revenue close, including journal entries, reconciliations, the ASC 606 revenue sub-ledger (subscription, usage, professional services, billing), revenue-by-customer/vertical schedules, and month-over-month fluctuation analysis. Own billing accuracy and timeliness across verticals, including invoice preparation and review, customer billing inquiries, dispute resolution, and collections partnership. Support external audits as the primary revenue and billing point of contact, and lead revenue-related SOX and IPO readiness — control design, documentation, and testing support. Automate it — vertical by vertical Lead the accounting automation roadmap for revenue and billing: identify the highest-effort manual processes, build the business case, and deliver the automation — hands-on, not just as a project sponsor. Automate billing end-to-end for every vertical, eliminating spreadsheet-based and manual invoicing in favor of systematic, auditable, scalable processes. Partner with the Senior Director to optimize the finance tool stack we already own (NetSuite, NetSuite ARM, Salesforce, Snowflake, Sigma, and Closing tool)— getting full value from existing investments before adding new systems, and leading evaluation when a gap is real. Apply AI tools (Claude) to revenue, billing, and close workflows, and serve as a subject matter expert for AI adoption across the accounting team. Fix the data, upstream Partner with Revenue Operations and the Salesforce team to enforce data hygiene at the source — define the required fields, validation rules, and booking standards needed for clean recognition and billing, and push back on deal and booking practices that create downstream cleanup. Partner with the Data team to own billing data integrity and efficiency, including usage data completeness and accuracy, reconciliation between source systems and the billing engine, and the controls that prove it. Build the data structure the organization needs — consistent customer, product, vertical, and contract dimensions — so revenue reporting, analysis, and operating metrics can be generated automatically rather than assembled by hand. Review deal structures with Sales, Revenue Operations, and Legal before close, so recognition and billing treatment is settled upfront rather than discovered during close. Lead the team Manage and develop the revenue team, setting priorities, raising the technical bar, and building a function that scales with transaction volume and deal complexity. Be a thought leader for the broader team: bring ideas about how the close, the controls, and the reporting should work, and then own the execution. Be a team player — support the growth of peers across accounting and financial operations, and step in where the team needs help, including outside your direct scope. Own revenue accounting and billing policy, keeping it current with new accounting standards, new pricing models, and new verticals or product lines." We need to turn each line into
• . Some lines are headings like "Own the end-to-end revenue and billing cycle" then a sentence. We'll treat each bullet as separate
• . Might combine some but okay. Requirements (Basic Qualifications): list: "Bachelor's degree in Accounting or Finance 8+ years of progressive revenue accounting experience, including at least 2 years directly managing accounting staff Deep expertise in ASC 606 and SaaS revenue recognition, with direct, hands-on experience recognizing revenue in a usage-based or consumption-based billing model (variable consideration, minimums and overages, tiered pricing, true-ups) Demonstrated ownership of an end-to-end billing or order-to-cash process, not just the accounting entries Track record of delivering accounting automation — specific processes you identified, designed, and shipped, with measurable reduction in manual effort or close time Experience working directly with Revenue Operations, Salesforce administrators, or Data/Engineering teams on data quality, system configuration, or data pipelines Advanced proficiency with financial systems (NetSuite, NetSuite ARM, Salesforce) and advanced Excel skills, including comfort working with large data sets Demonstrated proficiency with AI tools (Claude, ChatGPT, Copilot) to drive accounting process improvement Proactive operator — brings problems forward with a proposed solution, and is willing to get into the detail to prove it works Strong written and verbal communication skills, with the ability to translate technical accounting and systems issues for non-accounting stakeholders and leadership" We'll put each as
• . Qualifications (Preferred Qualifications): list: "CPA Big 4 or comparable public accounting experience Experience in a high-growth, pre-IPO or newly public SaaS or technology company Experience implementing or materially re-architecting a billing system or revenue sub-ledger Working knowledge of SQL, or experience building reporting data models and partnering on a data warehouse/BI implementation (e.g., BigQuery, Snowflake, Looker, Tableau) Exposure to SOX readiness, audit remediation, or public-company control environments Familiarity with Workiva or similar SOX/controls documentation tooling" We'll put each as
• . Skills: We could extract from the posting: "Advanced proficiency with