Senior Technical Business Integration Manager (Finance) - Melville, NY

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are" and "Position Overview". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: Who We Are (company description), Position Overview (role description), Success in this Role (maybe part of responsibilities), What You'll Do (Essential Functions, Key Responsibilities), Key Competencies, Minimum Qualifications, Preferred Qualifications, Education, Position Type and Expected Hours of Work (Schedule), Travel Requirements, What's In It For You (Benefits), Compensation (Pay), Other Duties, Work Environment, Physical Demands, AAP/EEO Statement (remove), Privacy Statement (remove), etc. We need to remove boilerplate: EEO, Privacy, etc. Also remove duplicated lines. We need to keep substantive info: company description, role overview, responsibilities list, competencies, qualifications (minimum and preferred), education, schedule (full-time, Monday-Friday, core hours, flexibility, occasional evening/weekend), travel (30-35%), benefits (health, dental, vision insurance, competitive 401(k) matching, Paid Time Off), compensation (salary range $100k-$120k, commensurate with experience). However note: we should not create Pay section if content is just "commensurate with experience"? Actually they gave a range and then "commensurate with experience". The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state a salary range, so we can include Pay section with that range. The phrase "commensurate with experience" is filler but we have actual range; we can include the range and maybe note that it's commensurate with experience? The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not include that phrase if it's just filler. We can include the range and maybe omit the phrase. So Pay section:

Pay

Good faith annual salary range for this position is $100,000 to $120,000 USD.

Schedule: they gave "Position Type and Expected Hours of Work This is a full-time position, Monday through Friday, during normal core business hours. Flexibility is required to support global customers, and occasional evening and weekend work may be required as job duties demand." That's substantive. So Schedule section. Benefits: they list "Health, dental, and vision insurance Competitive 401(k) matching Paid Time Off". Also earlier "What's In It For You Join a growing company where core platform integrations are central to delivering impactful client and business outcomes Opportunity to build expertise across both operational and financial workflows Health, dental, and vision insurance Competitive 401(k) matching Paid Time Off". So we can include Benefits section with those items. We also need About the role? Could combine Who We Are and Position Overview into About the role? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have About the role (company description + position overview). Responsibilities (Key Responsibilities list). Requirements (maybe Minimum Qualifications). Qualifications (maybe Preferred Qualifications). Skills (Key Competencies). Benefits, Pay, Schedule. We must not repeat job title as heading. No job ID. We need to preserve all substantive info; not invent or summarize away detail. So we need to keep details like specific ERP systems, etc. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to avoid duplication. Let's extract sections: About the role: combine Who We Are and Position Overview (maybe also Success in this Role? but that's more about success metrics). Could include as part of About the role. Responsibilities: list of Key Responsibilities (the bullet list under "Essential Functions: Reasonable accommodations may be made..." then "Key Responsibilities" then many items). We'll need to capture each as

• . Also maybe include "Success in this Role" items? Those are more like success metrics; could be part of Responsibilities or separate but we can incorporate. Requirements: Minimum Qualifications (the list after "Minimum Qualifications What You'll Bring"). Qualifications: Preferred Qualifications (the list after "Preferred Qualifications"). Skills: Key Competencies (list after "Key Competencies"). Benefits: list from What's In It For You. Pay: salary range. Schedule: Position Type and Expected Hours of Work + Travel Requirements? Travel could be part of Schedule or separate but we only have Schedule heading allowed; we could include travel within Schedule section as extra sentence. We must not create sections for things like Work Environment, Physical Demands, Other Duties, etc unless they have substantive content and we have headings for them? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add other headings like Work Environment. So we need to fold that info into existing sections if relevant, or drop if not needed? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info somewhere. If we cannot add a new heading, we must incorporate it into existing sections, maybe as part of About the role or Responsibilities. For example, Work Environment could be added to About the role as a sentence. Physical Demands could be added to Responsibilities? Might be odd but we can include as a note. Other Duties could be added to Responsibilities. The instruction says preserve ALL substantive information; we must not drop it. So we need to embed those details somewhere. Thus we need to include Work Environment, Physical Demands, Other Duties within appropriate sections (maybe About the role or Responsibilities). We'll add them as prose paragraphs under appropriate headings. We must not include boilerplate like EEO, Privacy, etc. Now let's extract content. Who We Are: "Accommodations Plus International (API) is a technology and services company focused on driving innovation across the travel and transportation industry. We partner with organizations in the airline, cruise, and rail sectors to deliver solutions that improve layover operations, enhance customer experience, and support long-term growth. Our mission is to make layovers simpler and more efficient for crew members—and we bring that to life through deep industry expertise and a practical, results-driven approach. Today, API’s platform powers over 18 million crew room nights each year for 100+ airlines and travel operators worldwide. Our Global Reach ensures that airline crews are rested, transported, and connected so global aviation runs on time. At API, we’re building a culture rooted in succeeding and thriving together. It’s a place where people are encouraged to take ownership, develop their skills, and contribute to work that matters. If you’re looking to grow your career in a company that values steady progress, real impact, and long-term development, we’d like to meet you!" Position Overview: "This role is responsible for gathering and documenting accounting business rules to support implementation of the API eInvoice product within client environments. It includes supporting the Implementation project team with fact-finding, client data (GL, cost and BU codes), process flows, and detailed requirements tied to ERP systems such as Oracle, SAP, Microsoft Dynamics, Sage, and NetSuite. These requirements inform product configuration and, at times, new feature development. The role is key to delivering financial operations, billing, and eInvoicing solutions across enterprise environments, bridging clients, finance, technology, and delivery teams to ensure successful implementation. The ideal candidate has experience in accounting or AP/AR, ERP systems, and client-facing implementations across the project lifecycle." Success in this Role: "Delivers project milestones and client deliverables on time through effective planning, prioritization, and risk management across complex implementations.Conducts strong discovery to deliver accurate, complete requirementsDemonstrates strong, clear communication across clients and internal teams to ensure alignment" We can combine. Key Responsibilities list (under Essential Functions). Let's extract each bullet: - Lead requirements gathering sessions with clients and internal stakeholders to capture business, accounting, billing, and invoicing needs. - Define, analyze, and document business and functional requirements related to accounting systems and eInvoicing platforms. - Ensure requirements accurately reflect contractual terms, billing rules, and financial controls. - Maintain clear requirements traceability throughout design, build, test, and deployment phases - Apply practical knowledge of accounts payable/receivable processes, invoicing cycles, and accounting methodologies. - Validate that system configurations align with contractual billing rules and financial governance requirements. - Conduct audits and detailed reviews of invoices to ensure accuracy, compliance, and adherence to contractual agreements. - Analyze reservations, supporting documentation, and invoice calculations using tools such as Excel. - Support implementation and integration of ERP and accounting systems in enterprise environments, including Oracle, SAP, Microsoft Dynamics, Sage, NetSuite - Collaborate with technical teams to ensure accurate data flow between ERP, eInvoicing, and billing platforms. - Participate in API‑based eInvoicing product demonstrations for clients where required. - Apply understanding of the Software Development Lifecycle (SDLC) and exposure to Agile/Scrum methodologies. - Attend and contribute to project meetings and delivery checkpoints. - Execute assigned tasks in line with project schedules and proactively report risks, issues, or delays. - Operate comfortably in a client‑facing role, engaging with airline, rail, hospitality, or large corporate partners. - Manage vendor interactions related to invoicing, reconciliation, and payments. - Maintain strong, professional relationships while balancing client expectations and contractual obligations. - Deliver comprehensive training sessions to new client partners on billing and eInvoicing processes, as well as any refresher training and ongoing support to existing clients. - Extend hands‑on support during initial invoice submissions to ensure correct invoicing and timely payment receipt. - Support issue resolution through analysis, stakeholder coordination, and documentation. Key Competencies: - Experience working on accounting or financial system projects, covering full project lifecycle. - Hands‑on experience in accounts payable/receivable or similar accounting environments. - Exposure to one or more ERP platforms: Oracle, SAP, Microsoft Dynamics, Sage, or NetSuite. - Strong experience gathering and documenting business and functional requirements, drafting user stories with immaculate details. - Proven ability to work in client‑facing roles within project or implementation teams. - Solid analytical skills with the ability to validate and reconcile financial data. - Proficiency in Excel and financial analysis tools. Minimum Qualifications (What You'll Bring): List: - 6+ years of experience with strong grounding in product ownership and product management principles, combined with a clear understanding of regional complexities across North American and European FinOps environments. - Experience working on accounting or financial system projects, covering full project lifecycle. - Hands‑on experience in accounts payable/receivable or similar accounting environments. - Strong experience gathering and documenting business and functional requirements, drafting user stories with immaculate details. - Proven ability to work in client‑facing roles within project or implementation teams. - Solid analytical skills with the ability to validate