Revenue Specialist
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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, 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. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
Key sections:
- About the role: The first paragraph(s) describing role: "The Marlene Meyerson Jewish Community Center of Manhattan (MMJCC) is seeking a highly organized, detail-oriented, and analytical Revenue Specialist to join our Finance team. This position plays a critical role in ensuring the accuracy, completeness, and timely recording of the MMJCC's diverse revenue streams, including membership, camp, program services, contributions, grants, special events, and other earned income. Reporting to the VP of Finance, the Revenue Specialist serves as a key liaison between Finance and operational departments, supporting the reconciliation of revenue activity between the MMJCC's CRM, registration, fundraising, and accounting systems. The position is responsible for monitoring revenue transactions, maintaining supporting schedules, preparing reconciliations, and assisting with month-end and year-end close activities. This role is ideal for a finance professional with strong analytical skills, a commitment to accuracy, and an interest in nonprofit accounting. The Revenue Specialist will play an important role in strengthening internal controls, supporting audits, and enhancing financial reporting processes across the organization."
Then there is a paragraph about the organization: "The Marlene Meyerson Jewish Community Center of Manhattan Together with our community, the Marlene Meyerson JCC Manhattan creates a welcoming and vibrant environment where individuals from all walks of life come together to connect, grow, and learn. Rooted in Jewish values, it is a cornerstone of the Upper West Side that provides something for every stage of life through a multifaceted array of offerings-spanning comprehensive children's and family programs, cutting-edge health and wellness, thought-provoking arts and culture, and vital social services. It imagines Jewish life that is inclusive and diverse, creating a supportive space for people of all backgrounds to engage, nurture their well-being, and find a deep sense of belonging."
We could include that under About the role or maybe separate "About the organization". But instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put the description of the role and organization under About the role.
Responsibilities: bullet list of duties.
Requirements: bullet list.
Qualifications: maybe not separate; but we could combine Requirements and Qualifications? The instruction says we can use Qualifications heading if there is content. The posting includes Requirements (experience, degree, skills). There's also "Preferred" items. Could treat Requirements as required, and Qualifications as preferred? But we can just have Requirements section with both required and preferred? The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one section called Requirements (or Qualifications). But we have both headings allowed. Let's see: The posting has "Requirements" bullet list, then "If this role sounds like a good fit for you, please upload a cover letter..." That's application instruction (to remove). Then "What We Offer" bullet list (benefits). Then "WORK SCHEDULE" (schedule). Then "WORK LOCATION" (location). Then "SALARY RANGE" (pay). Then EEO boilerplate (remove). Then "To Apply" (remove). So we have sections: Benefits (What We Offer), Schedule, Pay, Location (maybe not a heading but we could incorporate into a short p). The instruction says include a section ONLY when posting has real, specific content for it. So we can have Benefits, Schedule, Pay. Location maybe not a heading; we can put location in a short p under About the role or separate? But we have no heading for Location; we could just include location in a paragraph under About the role or maybe under a generic "Details". But instruction says use headings from list; we could add a heading "Work Location" but not in list; better to avoid. So we can incorporate location into a paragraph under About the role or maybe under a short p after responsibilities.
We must not include filler like "commensurate with experience" in Pay section? Actually they said never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state Pay: "$75,000 – $90,000 annually, commensurate with experience." That's specific content (range). So we can include Pay section with that range. However they also said never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "commensurate with experience" is considered filler? They gave example of filler text: "commensurate with experience". So we should not include that phrase if it's considered filler. But we need to preserve ALL substantive information; do NOT invent or summarize away detail. The salary range is substantive; the phrase "commensurate with experience" is maybe filler but it's part of the posting. The instruction says 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. It seems they want us to avoid sections that only have filler like "commensurate with experience" without actual numbers. But we have actual numbers; we could include the range and maybe omit the phrase "commensurate with experience" as it's filler. However that would be summarizing away detail? It's not substantive; it's just a qualifier. I'd lean to include the range and maybe drop the phrase. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." Dropping "commensurate with experience" is summarizing away detail? It's not substantive; it's a qualifier but maybe considered filler. I'd keep it? The example of filler includes that phrase, so they want us to not include it. So we should output Pay section with just the range "$75,000 – $90,000 annually". That preserves substantive info (the range) and drops filler.
Schedule: posting says "This is a full-time position. Standard business hours are Monday through Friday. Occasional additional hours may be required during month-end close, year-end audit, budget season, or other peak periods." That's substantive. So Schedule section with that.
Benefits: "What We Offer Supportive, mission-driven work environmentHealth Benefits such as Medical, Dental, and Vision Insurance + morePaid Vacation Time + a generous offering of Federal and Jewish/Secular Holidays403(b) Retirement AccountOpportunities for professional development, mentorship, and leadership investmentAccess to all the JCC's cultural, learning, arts, and film programsFree fitness membership for the pool and health clubDiscounts on other JCC programs". Need to parse into list items.
We should separate each benefit as
- . The text is concatenated without punctuation; we need to split logically. Let's list:
- Supportive, mission-driven work environment
- Health Benefits such as Medical, Dental, and Vision Insurance + more
- Paid Vacation Time + a generous offering of Federal and Jewish/Secular Holidays
- 403(b) Retirement Account
- Opportunities for professional development, mentorship, and leadership investment
- Access to all the JCC's cultural, learning, arts, and film programs
- Free fitness membership for the pool and health club
- Discounts on other JCC programs
We'll make a
with those.
Now Responsibilities: list of duties from the responsibilities paragraph. Let's extract each sentence as a bullet.
Responsibilities paragraph:
"Prepare and maintain reconciliations for membership, camp, program, event, contribution, grant, and other revenue streams, ensuring completeness and accuracy between source systems and the general ledger.
Work closely with operational departments to reconcile activity between DAXKO, fundraising platforms, payment processors, and Sage Intacct (or other accounting systems).
Maintain detailed deferred revenue schedules and prepare monthly rollforwards to support accurate revenue recognition.
Assist with recording contributions, pledges, grants, donor restrictions, and releases from restriction in accordance with nonprofit accounting standards.
Prepare journal entries, account reconciliations, supporting schedules, and variance analyses as part of the monthly close process.
Assist in the preparation of internal financial reports, management schedules, and ad hoc analyses related to revenue and program activity.
Prepare audit schedules and supporting documentation for revenue, deferred revenue, contributions receivable, and net asset accounts.
Support the development and maintenance of strong internal controls surrounding revenue recognition, cash receipts, and reconciliations.
Partner with Program, Membership, Development, Camp, and Operations teams to resolve discrepancies, improve reporting processes, and enhance data integrity.
Identify opportunities to streamline revenue accounting processes, improve reporting capabilities, and strengthen financial controls."
Also there is a sentence: "Please note that this job description is not intended to cover or list in full the activities, duties, or responsibilities required of the employee for this job. Duties, responsibilities, and activities may change at any time with or without notice." That's boilerplate; we should remove as per instruction: remove duplicated lines, application instructions? This is a disclaimer about job description; likely considered boilerplate; we should remove.
Now Requirements: bullet list.
Requirements paragraph:
"Minimum 2–5 years of accounting, revenue accounting, accounts receivable, or nonprofit finance experience
Bachelor's degree in Accounting, Finance, Business Administration, or related field.
Strong understanding of accounting principles, reconciliations, journal entries, and financial reporting.
Ability to analyze large datasets, identify discrepancies, and independently resolve issues.
Advanced proficiency in Microsoft Excel.
Experience with accounting software, CRM platforms, and reporting systems preferred.
Exceptional attention to detail with strong organizational and time-management skills.
Ability to communicate effectively with both finance and non-finance personnel across the organization.
Experience with nonprofit accounting, deferred revenue, contributions, grants, and restricted funds is preferred."
We should treat "preferred" items as still part of requirements; we can keep them.
Now Benefits: as above.
Schedule: as above.
Pay: salary range.
We might also include a short paragraph about location? Not required heading; we could incorporate into About the role paragraph.
Now we must not include application instructions: "If this role sounds like a good fit for you, please upload a cover letter with your resume indicating your interest." Also "To Apply Please visit mmjccm.org/careers to apply. Please submit a cover letter and resume." Remove.
Also remove EEO boilerplate.
Now construct HTML.
We'll start with About the role
then containing the description (both role and organization). Ensure we preserve all substantive info.
Let's craft About the role paragraph:
"The Marlene Meyerson Jewish Community Center of Manhattan (MMJCC) is seeking a highly organized, detail-oriented, and analytical Revenue Specialist to join our Finance team. This position plays a critical role in ensuring the accuracy, completeness, and timely recording of the MMJCC's diverse revenue streams, including membership
for prose. 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, 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Key sections: - About the role: The first paragraph(s) describing role: "The Marlene Meyerson Jewish Community Center of Manhattan (MMJCC) is seeking a highly organized, detail-oriented, and analytical Revenue Specialist to join our Finance team. This position plays a critical role in ensuring the accuracy, completeness, and timely recording of the MMJCC's diverse revenue streams, including membership, camp, program services, contributions, grants, special events, and other earned income. Reporting to the VP of Finance, the Revenue Specialist serves as a key liaison between Finance and operational departments, supporting the reconciliation of revenue activity between the MMJCC's CRM, registration, fundraising, and accounting systems. The position is responsible for monitoring revenue transactions, maintaining supporting schedules, preparing reconciliations, and assisting with month-end and year-end close activities. This role is ideal for a finance professional with strong analytical skills, a commitment to accuracy, and an interest in nonprofit accounting. The Revenue Specialist will play an important role in strengthening internal controls, supporting audits, and enhancing financial reporting processes across the organization." Then there is a paragraph about the organization: "The Marlene Meyerson Jewish Community Center of Manhattan Together with our community, the Marlene Meyerson JCC Manhattan creates a welcoming and vibrant environment where individuals from all walks of life come together to connect, grow, and learn. Rooted in Jewish values, it is a cornerstone of the Upper West Side that provides something for every stage of life through a multifaceted array of offerings-spanning comprehensive children's and family programs, cutting-edge health and wellness, thought-provoking arts and culture, and vital social services. It imagines Jewish life that is inclusive and diverse, creating a supportive space for people of all backgrounds to engage, nurture their well-being, and find a deep sense of belonging." We could include that under About the role or maybe separate "About the organization". But instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put the description of the role and organization under About the role. Responsibilities: bullet list of duties. Requirements: bullet list. Qualifications: maybe not separate; but we could combine Requirements and Qualifications? The instruction says we can use Qualifications heading if there is content. The posting includes Requirements (experience, degree, skills). There's also "Preferred" items. Could treat Requirements as required, and Qualifications as preferred? But we can just have Requirements section with both required and preferred? The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one section called Requirements (or Qualifications). But we have both headings allowed. Let's see: The posting has "Requirements" bullet list, then "If this role sounds like a good fit for you, please upload a cover letter..." That's application instruction (to remove). Then "What We Offer" bullet list (benefits). Then "WORK SCHEDULE" (schedule). Then "WORK LOCATION" (location). Then "SALARY RANGE" (pay). Then EEO boilerplate (remove). Then "To Apply" (remove). So we have sections: Benefits (What We Offer), Schedule, Pay, Location (maybe not a heading but we could incorporate into a short p). The instruction says include a section ONLY when posting has real, specific content for it. So we can have Benefits, Schedule, Pay. Location maybe not a heading; we can put location in a short p under About the role or separate? But we have no heading for Location; we could just include location in a paragraph under About the role or maybe under a generic "Details". But instruction says use headings from list; we could add a heading "Work Location" but not in list; better to avoid. So we can incorporate location into a paragraph under About the role or maybe under a short p after responsibilities. We must not include filler like "commensurate with experience" in Pay section? Actually they said never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state Pay: "$75,000 – $90,000 annually, commensurate with experience." That's specific content (range). So we can include Pay section with that range. However they also said never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "commensurate with experience" is considered filler? They gave example of filler text: "commensurate with experience". So we should not include that phrase if it's considered filler. But we need to preserve ALL substantive information; do NOT invent or summarize away detail. The salary range is substantive; the phrase "commensurate with experience" is maybe filler but it's part of the posting. The instruction says 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. It seems they want us to avoid sections that only have filler like "commensurate with experience" without actual numbers. But we have actual numbers; we could include the range and maybe omit the phrase "commensurate with experience" as it's filler. However that would be summarizing away detail? It's not substantive; it's just a qualifier. I'd lean to include the range and maybe drop the phrase. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." Dropping "commensurate with experience" is summarizing away detail? It's not substantive; it's a qualifier but maybe considered filler. I'd keep it? The example of filler includes that phrase, so they want us to not include it. So we should output Pay section with just the range "$75,000 – $90,000 annually". That preserves substantive info (the range) and drops filler. Schedule: posting says "This is a full-time position. Standard business hours are Monday through Friday. Occasional additional hours may be required during month-end close, year-end audit, budget season, or other peak periods." That's substantive. So Schedule section with that. Benefits: "What We Offer Supportive, mission-driven work environmentHealth Benefits such as Medical, Dental, and Vision Insurance + morePaid Vacation Time + a generous offering of Federal and Jewish/Secular Holidays403(b) Retirement AccountOpportunities for professional development, mentorship, and leadership investmentAccess to all the JCC's cultural, learning, arts, and film programsFree fitness membership for the pool and health clubDiscounts on other JCC programs". Need to parse into list items. We should separate each benefit as
- with those.
Now Responsibilities: list of duties from the responsibilities paragraph. Let's extract each sentence as a bullet.
Responsibilities paragraph:
"Prepare and maintain reconciliations for membership, camp, program, event, contribution, grant, and other revenue streams, ensuring completeness and accuracy between source systems and the general ledger.
Work closely with operational departments to reconcile activity between DAXKO, fundraising platforms, payment processors, and Sage Intacct (or other accounting systems).
Maintain detailed deferred revenue schedules and prepare monthly rollforwards to support accurate revenue recognition.
Assist with recording contributions, pledges, grants, donor restrictions, and releases from restriction in accordance with nonprofit accounting standards.
Prepare journal entries, account reconciliations, supporting schedules, and variance analyses as part of the monthly close process.
Assist in the preparation of internal financial reports, management schedules, and ad hoc analyses related to revenue and program activity.
Prepare audit schedules and supporting documentation for revenue, deferred revenue, contributions receivable, and net asset accounts.
Support the development and maintenance of strong internal controls surrounding revenue recognition, cash receipts, and reconciliations.
Partner with Program, Membership, Development, Camp, and Operations teams to resolve discrepancies, improve reporting processes, and enhance data integrity.
Identify opportunities to streamline revenue accounting processes, improve reporting capabilities, and strengthen financial controls."
Also there is a sentence: "Please note that this job description is not intended to cover or list in full the activities, duties, or responsibilities required of the employee for this job. Duties, responsibilities, and activities may change at any time with or without notice." That's boilerplate; we should remove as per instruction: remove duplicated lines, application instructions? This is a disclaimer about job description; likely considered boilerplate; we should remove.
Now Requirements: bullet list.
Requirements paragraph:
"Minimum 2–5 years of accounting, revenue accounting, accounts receivable, or nonprofit finance experience
Bachelor's degree in Accounting, Finance, Business Administration, or related field.
Strong understanding of accounting principles, reconciliations, journal entries, and financial reporting.
Ability to analyze large datasets, identify discrepancies, and independently resolve issues.
Advanced proficiency in Microsoft Excel.
Experience with accounting software, CRM platforms, and reporting systems preferred.
Exceptional attention to detail with strong organizational and time-management skills.
Ability to communicate effectively with both finance and non-finance personnel across the organization.
Experience with nonprofit accounting, deferred revenue, contributions, grants, and restricted funds is preferred."
We should treat "preferred" items as still part of requirements; we can keep them.
Now Benefits: as above.
Schedule: as above.
Pay: salary range.
We might also include a short paragraph about location? Not required heading; we could incorporate into About the role paragraph.
Now we must not include application instructions: "If this role sounds like a good fit for you, please upload a cover letter with your resume indicating your interest." Also "To Apply Please visit mmjccm.org/careers to apply. Please submit a cover letter and resume." Remove.
Also remove EEO boilerplate.
Now construct HTML.
We'll start with
About the role
thencontaining the description (both role and organization). Ensure we preserve all substantive info. Let's craft About the role paragraph: "The Marlene Meyerson Jewish Community Center of Manhattan (MMJCC) is seeking a highly organized, detail-oriented, and analytical Revenue Specialist to join our Finance team. This position plays a critical role in ensuring the accuracy, completeness, and timely recording of the MMJCC's diverse revenue streams, including membership