Senior Business Systems Specialist

We need to output HTML fragment with sections: h3 headings for sections present. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Equal Employment Opportunity Statement", "Reasonable Accommodations", "We're Here to Help", etc. Also remove "Office Guidelines", "Our Belonging Philosophy", "A Few Of Our Best Benefits" maybe keep benefits if they have specifics. The posting includes benefits list: Dog-friendly office in SoHo, Market-competitive compensation and equity packages, Comprehensive Healthcare, Dental, and Vision, Company supported mental health benefits, 12 week paid parental leave, Competitive 401k plan with company match, Flexible PTO, Discounted fresh food for your pup, Your pet interrupting video calls (and in-person meetings) is now a feature, not a bug. Those are specifics, so we can include Benefits section. Pay: The posting includes "NYC Pay Range $160,000—$170,000 USD". Also earlier: "For this role the anticipated hiring base compensation range is USD annual and the compensation offered will include a robust market competitive package of base and equity." So we have pay info: range $160k-170k. So we should include Pay section. Schedule: Office Guidelines says "We ask all team members to be in office 4 - 5 days a week". That's schedule info. So we can include Schedule section. We need sections: About the role? The posting includes "Who We Are", "What We Stand For and Where You’ll Come In", "How You'll Make An Impact", "We're Excited About You Because". Also "Office Guidelines", "Our Belonging Philosophy", "A Few Of Our Best Benefits". We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should use those headings only if we have content. We need to decide which content goes where. - About the role: could be the description of role: "The Senior Business Systems Specialist is responsible for the technical implementation, configuration, and integration of our core business systems including NetSuite, Coupa, and various retail partners across the organization. You will build and maintain integrations between NetSuite and marketplace/vendor platforms with Retail partners and procurement systems (Coupa), configure workflows to meet business requirements, troubleshoot data and integration issues, and ensure data integrity across connected systems. You'll partner with engineering, accounting and operations to manage technical project timelines, document system architecture, and drive adoption through hands-on technical enablement, delivering projects on time, within scope, and aligned to stakeholder requirements." That seems like responsibilities. Could be About the role (overview) and Responsibilities separate. But we need to avoid thin sections. Perhaps combine overview and responsibilities under Responsibilities? However we have separate headings allowed. We need to include sections only when posting has real specific content. We have content for Responsibilities (list of duties). Also we have Requirements/Qualifications/Skills from "We're Excited About You Because". That includes experience, tools, etc. Could split into Requirements (experience) and Skills (tools). But we need to avoid thin sections. Might combine Requirements and Skills into one? But headings are prescribed; we can use multiple if content exists. Let's see. We have: - Experience: 7+ years experience operating in and maintaining financial tools and deep experience integrating NetSuite with third-party tools and managing complex data pipelines into and out of an ERP. - Advanced familiarity with multiple of the following tools: ERP systems, payment processors, transportation management systems, procure to pay platforms, IPAAS, tax software, demand planning tools. - Hands-on experience with NetSuite, including SuiteScript (SuiteScript 2.x), SuiteFlow, SuiteAnalytics/saved searches, and customizing records, forms, and workflows. - Experience building and maintaining API integrations (REST/SOAP), including authentication, error handling, and data mapping between systems. - Familiarity with EDI standards and marketplace integration requirements for various retailers. - Demonstrated experience with SQL skills for querying, validating, and troubleshooting data across integrated systems as well as an understanding of data structures and schema design to maintain integrity across connected platforms. - Experience with version control (e.g., Git) and basic scripting (JavaScript, Python) for automation and integration support. - Skilled communicator and ability to absorb and distill complexity into simple terms to drive decision making. - Owner, expert-level problem-solving skills, can prioritize tasks effectively, strong attention to detail, focus on efficiency. - Love dogs! These could be split into Requirements (experience) and Skills (technical). But we also have "We're Excited About You Because" heading. Could treat that as Requirements/Qualifications. We also have "How You'll Make An Impact" which lists specific impact items: Serve as NetSuite functional and technical SME, architect dashboards, gather requirements, collaborate with engineering, own order-to-cash systems architecture, analyze systems, implement automation, contribute to roadmap, manage configurations, develop SOPs, lead enablement sessions. Those are responsibilities/duties. Thus we can have: - Responsibilities: combine the "How You'll Make An Impact" list (maybe also the earlier description). Use

• . - Requirements: maybe the experience (7+ years, etc). Could be a
  . - Skills: maybe the technical tools list (NetSuite, SuiteScript, etc). Could be a
  . But we need to avoid duplication. Let's decide: Responsibilities: list from "How You'll Make An Impact" plus maybe the initial description (but that overlaps). We'll include the list from "How You'll Make An Impact" as responsibilities. Requirements: list of experience: "7+ years experience operating in and maintaining financial tools and deep experience integrating NetSuite with third-party tools and managing complex data pipelines into and out of an ERP." plus maybe "advanced familiarity with multiple of the following tools: ERP systems, payment processors, transportation management systems, procure to pay platforms, IPAAS, tax software, demand planning tools." That's more like skills though. Hmm. Better: Requirements: the experience and maybe the love dogs? But love dogs is not a requirement. Skills: technical skills: NetSuite, SuiteScript, SuiteFlow, SuiteAnalytics, API integrations, EDI, SQL, version control, scripting. We could also include "advanced familiarity with multiple of the following tools: ERP systems, payment processors, transportation management systems, procure to pay platforms, IPAAS, tax software, demand planning tools." as Skills. Thus: - Requirements: 7+ years experience operating in and maintaining financial tools and deep experience integrating NetSuite with third-party tools and managing complex data pipelines into and out of an ERP. (maybe also "Love dogs!" but that's not a requirement). Could be a single

  or

  with one item. - Skills: list of technical proficiencies. But we need to avoid thin sections. If Requirements only has one bullet, maybe we combine Requirements and Skills into one section called "Requirements & Skills"? But headings are fixed; we cannot create custom heading. We could still use Requirements heading with a
  containing multiple items (including experience and skills). That would be okay: we can put all bullet points under Requirements. Then we might not need Skills heading. However we also have Benefits, Pay, Schedule sections. Thus we can have: - About the role: maybe a brief paragraph summarizing role (the "Who We Are" and "What We Stand For and Where You’ll Come In" includes company mission; but About the role could be a short description of the role: "The Senior Business Systems Specialist is responsible for the technical implementation, configuration, and integration of our core business systems including NetSuite, Coupa, and various retail partners across the organization." We'll put that as About the role. - Responsibilities: list from "How You'll Make An Impact". - Requirements: list of experience and skills (combined). Could be bullet list. - Benefits: list of benefits. - Pay: the NYC Pay Range. - Schedule: office guideline 4-5 days a week. We must not include sections like Qualifications if we combine into Requirements. We must not repeat job title. We must not include boilerplate: remove "Who We Are", "What We Stand For and Where You’ll Come In", "How You'll Make An Impact", "We're Excited About You Because", "Office Guidelines", "Our Belonging Philosophy", "A Few Of Our Best Benefits", "Equal Employment Opportunity Statement", etc. We'll extract content. Now produce HTML fragment:

  About the role

  The Senior Business Systems Specialist is responsible for the technical implementation, configuration, and integration of our core business systems including NetSuite, Coupa, and various retail partners across the organization. You will build and maintain integrations between NetSuite and marketplace/vendor platforms with Retail partners and procurement systems (Coupa), configure workflows to meet business requirements, troubleshoot data and integration issues, and ensure data integrity across connected systems. You'll partner with engineering, accounting and operations to manage technical project timelines, document system architecture, and drive adoption through hands-on technical enablement, delivering projects on time, within scope, and aligned to stakeholder requirements.

  Responsibilities

  • Serve as the NetSuite functional and technical SME, providing guidance on system architecture, data integrity, and best practices for financial systems.
  • Architect and maintain advanced dashboards, saved searches, and custom reports in NetSuite and dedicated BI tooling (Looker, Sigma, etc) to support real-time financial and inventory visibility across the organization.
  • Gather requirements and lead a group of cross-functional stakeholders to architect, implement and support scalable technical solutions, including full system implementations.
  • Collaborate with TFD’s engineering function on custom solutions inside and adjacent to our financial systems.
  • Own the order-to-cash systems architecture for retail and marketplace channels.
  • Analyze existing financial and operational systems to identify inefficiencies and drive the implementation of automated, scalable solutions, and champion.
  • Implement automation and workflow optimizations using SuiteFlow, SuiteScript, and custom integrations.
  • Contribute to the roadmap of financial tooling across TFD with respect to system stability, scalability, and anticipating the needs of the future.
  • Manage financial system configurations, role permissions, and upgrade cycles; coordinate testing, deployment, and post-go-live support with cross-functional stakeholders.
  • Develop and maintain SOPs, process documentation, and training materials to ensure scalable adoption of integrated financial tools.
  • Lead enablement sessions and provide hands-on training to finance, operations, and business users on new features, customizations, and process enhancements.

  Requirements

  • 7+ years experience operating in and maintaining financial tools and deep experience integrating NetSuite with third-party tools and managing complex data pipelines into and out of an ERP.
  • Advanced familiarity with multiple of the following tools: ERP systems, payment processors, transportation management systems, procure to pay platforms, IPAAS, tax software, demand planning tools.
  • Hands-on experience with NetSuite, including SuiteScript (SuiteScript 2.x), SuiteFlow, SuiteAnalytics/saved searches, and customizing records, forms, and workflows.
  • Experience building and maintaining API integrations (REST/SOAP), including authentication, error handling, and data mapping between systems.
  • Familiarity with EDI standards and marketplace integration requirements for various retailers.
  • Demonstrated experience with SQL skills for querying, validating, and troubleshooting data across integrated systems as well as an understanding of data structures and schema design to maintain integrity across connected platforms.
  • Experience with version control (e.g., Git) and basic scripting (JavaScript, Python) for automation and integration support.
  • Skilled communicator with the ability to