Senior Bookkeeper — Multi-Station Accounting
EMS Unlimited · Omaha, NE · 1 mo ago
AccountingFull-time
We need to output HTML fragment with sections: About the role? Actually we have company description, job description, responsibilities, qualifications, compensation & benefits, etc. We must use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We only include sections that have real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO etc. Also remove duplicated lines.
We need to preserve all substantive information. Let's parse content.
Company Description: About EMS Unlimited ... This is description of company. Could be placed under "About the role"? Actually "About the role" heading is for role description. But we have company description separate. Could we put under "About the role"? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have other headings, but likely they expect only those headings. Safer to include company description under "About the role" heading.
- Responsibilities: we have bullet list of duties (What you'll do). Also repeated paragraphs. We'll combine.
- Requirements: qualifications required.
- Skills: maybe list of skills like Excel, QuickBooks, etc. Could be part of qualifications.
- Benefits: we have "Compensation & Benefits Salary commensurate with experience. Comprehensive benefits administered through the company's PEO — full W-2 employment, no contractor arrangements." Also "...do it again tomorrow." That's fluff. We need to include only if specific content. Salary commensurate with experience is vague; we should not create Pay section unless posting actually states them. It says "Salary commensurate with experience." That's not specific; we should not create Pay section because it's not a specific number or range. Benefits: "Comprehensive benefits administered through the company's PEO — full W-2 employment, no contractor arrangements." That's somewhat specific but still vague. However we can include Benefits section if there is real content. It says "Comprehensive benefits administered through the company's PEO — full W-2 employment, no contractor arrangements." That's something. We'll include Benefits.
- Pay: we should not include because only "Salary commensurate with experience." That's not specific; rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits we have some statement; we can include Benefits. Pay we should omit.
- Schedule: not mentioned; omit.
- Skills: we could list Excel, QuickBooks Online, etc. Might be part of Qualifications. But we could create Skills section if we have specific skills. The posting mentions: Hands-on proficiency in QuickBooks Online, Strong general ledger, AP/AR, and bank/card reconciliation experience, Solid Excel skills (pivot tables, lookups), Comfortable owning books independently, Experience with corporate card/expense platforms, Exposure to government/federal contract accounting, QuickBooks ProAdvisor certification, Healthcare/EMS/ambulance/transportation industry background, Associate's or Bachelor's degree in Accounting or Finance (a plus). Those are qualifications/requirements/skills. We could split: Requirements (required qualifications), Skills (preferred/nice-to-have). But instruction: Use headings as given; we can decide.
We need to avoid duplication. The posting repeats paragraphs; we need to preserve all substantive information but not duplicate. We'll consolidate.
Let's extract substantive content:
Company description (About EMS Unlimited):
- EMS Unlimited is a paramedic-owned ambulance and medical transport company providing Advanced Life Support, Basic Life Support, and Critical Care Transport across Colorado, Nebraska, Kansas, Arizona, and Montana.
- Founded in 2012 by a working paramedic.
- Grew from special-events medical staffing outfit into multi-state operator running ambulance stations, a wildland fire and disaster response team under federal USDA Forest Service agreements, and hospital-based staffing contracts.
- In the last year: stood up a new federal ambulance contract at Fort Leavenworth, KS, launched Station 137 in Omaha and Station 237 in Aurora with plans for more in 2027.
- On top of a wildfire response division whose revenue swings depending on fire season.
- Keeping that financial picture accurate, current, and station-by-station isn't a side task here. It's the job.
Role description (Senior Bookkeeper):
- Own the company's day-to-day books across all stations and cost centers.
- Not a single-entity, single-checkbook job; reconciling and coding across multiple bank accounts, a company-wide corporate card program, and eleven separate station/cost-center ledgers.
- Business with real complexity and real revenue seasonality.
- Role sits between "bookkeeper" and "controller".
- Won't be setting financial strategy, running payroll, or managing other staff (that's Fractional CFO's and Payroll team's lane).
- Will own making sure every dollar, at every station, is coded right, reconciled on time, and ready to report on.
- Specific duties:
- Own the general ledger in QuickBooks Online across all EMS Unlimited stations and cost centers, keeping station-level P&Ls clean and current.
- Code and reconcile corporate card activity (Divvy/BILL Spend & Expense) by station, and manage accounts payable through Bill.com for check-required vendors.
- Perform monthly bank and credit card reconciliations across multiple accounts.
- Maintain the company's debt schedule — tracking balances, payment timing, and maturity dates across several active lending facilities.
- Support monthly close and deliver accurate, audit-ready financials to the Fractional CFO/CAO.
- Coordinate with the payroll team on payroll-related GL entries (you won't run payroll — Payroll & Benefits is handled separately through the company's PEO).
- Flag inconsistencies before they become problems — this company runs lean, and a good catch here saves real money.
- What this role is not: a CPA-track controller position, a financial-strategy role, or a people-management role.
Compensation & Benefits:
- Salary commensurate with experience.
- Comprehensive benefits administered through the company's PEO — full W-2 employment, no contractor arrangements.
- "...do it again tomorrow." (fluff, ignore)
Qualifications Required:
- 5+ years of full-charge bookkeeping or staff accounting experience.
- Hands-on proficiency in QuickBooks Online, including multi-entity or multi-location bookkeeping.
- Strong general ledger, AP/AR, and bank/card reconciliation experience.
- Solid Excel skills (pivot tables, lookups — you'll be building and reading station-by-station breakdowns regularly).
- Comfortable owning books independently with minimal oversight, while knowing when to escalate.
Preferred (nice to have, not dealbreakers):
- Experience with corporate card/expense platforms (Divvy, BILL Spend & Expense, or similar).
- Exposure to government/federal contract accounting or compliance-grade recordkeeping.
- QuickBooks ProAdvisor certification.
- Healthcare, EMS, ambulance, or transportation industry background.
- Associate's or Bachelor's degree in Accounting or Finance (a plus, not required — real experience carries more weight here than a credential).
We need to output HTML with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We'll include only those with content.
Let's map:
- About the role: could contain company description + role overview (maybe short). We'll put company description and brief role summary.
- Responsibilities: list of duties (What you'll do). Use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We only include sections that have real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO etc. Also remove duplicated lines.
We need to preserve all substantive information. Let's parse content.
Company Description: About EMS Unlimited ... This is description of company. Could be placed under "About the role"? Actually "About the role" heading is for role description. But we have company description separate. Could we put under "About the role"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
We have:
- Company description: could go under "About the role"? Might be better as a brief intro before sections, but we cannot add arbitrary headings not listed. We could put company description in a
before any heading? The instruction says output ONLY the HTML fragment, no /. It didn't forbid having a
before headings. It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have other headings, but likely they expect only those headings. Safer to include company description under "About the role" heading.
- Responsibilities: we have bullet list of duties (What you'll do). Also repeated paragraphs. We'll combine.
- Requirements: qualifications required.
- Skills: maybe list of skills like Excel, QuickBooks, etc. Could be part of qualifications.
- Benefits: we have "Compensation & Benefits Salary commensurate with experience. Comprehensive benefits administered through the company's PEO — full W-2 employment, no contractor arrangements." Also "...do it again tomorrow." That's fluff. We need to include only if specific content. Salary commensurate with experience is vague; we should not create Pay section unless posting actually states them. It says "Salary commensurate with experience." That's not specific; we should not create Pay section because it's not a specific number or range. Benefits: "Comprehensive benefits administered through the company's PEO — full W-2 employment, no contractor arrangements." That's somewhat specific but still vague. However we can include Benefits section if there is real content. It says "Comprehensive benefits administered through the company's PEO — full W-2 employment, no contractor arrangements." That's something. We'll include Benefits.
- Pay: we should not include because only "Salary commensurate with experience." That's not specific; rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits we have some statement; we can include Benefits. Pay we should omit.
- Schedule: not mentioned; omit.
- Skills: we could list Excel, QuickBooks Online, etc. Might be part of Qualifications. But we could create Skills section if we have specific skills. The posting mentions: Hands-on proficiency in QuickBooks Online, Strong general ledger, AP/AR, and bank/card reconciliation experience, Solid Excel skills (pivot tables, lookups), Comfortable owning books independently, Experience with corporate card/expense platforms, Exposure to government/federal contract accounting, QuickBooks ProAdvisor certification, Healthcare/EMS/ambulance/transportation industry background, Associate's or Bachelor's degree in Accounting or Finance (a plus). Those are qualifications/requirements/skills. We could split: Requirements (required qualifications), Skills (preferred/nice-to-have). But instruction: Use headings as given; we can decide.
We need to avoid duplication. The posting repeats paragraphs; we need to preserve all substantive information but not duplicate. We'll consolidate.
Let's extract substantive content:
Company description (About EMS Unlimited):
- EMS Unlimited is a paramedic-owned ambulance and medical transport company providing Advanced Life Support, Basic Life Support, and Critical Care Transport across Colorado, Nebraska, Kansas, Arizona, and Montana.
- Founded in 2012 by a working paramedic.
- Grew from special-events medical staffing outfit into multi-state operator running ambulance stations, a wildland fire and disaster response team under federal USDA Forest Service agreements, and hospital-based staffing contracts.
- In the last year: stood up a new federal ambulance contract at Fort Leavenworth, KS, launched Station 137 in Omaha and Station 237 in Aurora with plans for more in 2027.
- On top of a wildfire response division whose revenue swings depending on fire season.
- Keeping that financial picture accurate, current, and station-by-station isn't a side task here. It's the job.
Role description (Senior Bookkeeper):
- Own the company's day-to-day books across all stations and cost centers.
- Not a single-entity, single-checkbook job; reconciling and coding across multiple bank accounts, a company-wide corporate card program, and eleven separate station/cost-center ledgers.
- Business with real complexity and real revenue seasonality.
- Role sits between "bookkeeper" and "controller".
- Won't be setting financial strategy, running payroll, or managing other staff (that's Fractional CFO's and Payroll team's lane).
- Will own making sure every dollar, at every station, is coded right, reconciled on time, and ready to report on.
- Specific duties:
- Own the general ledger in QuickBooks Online across all EMS Unlimited stations and cost centers, keeping station-level P&Ls clean and current.
- Code and reconcile corporate card activity (Divvy/BILL Spend & Expense) by station, and manage accounts payable through Bill.com for check-required vendors.
- Perform monthly bank and credit card reconciliations across multiple accounts.
- Maintain the company's debt schedule — tracking balances, payment timing, and maturity dates across several active lending facilities.
- Support monthly close and deliver accurate, audit-ready financials to the Fractional CFO/CAO.
- Coordinate with the payroll team on payroll-related GL entries (you won't run payroll — Payroll & Benefits is handled separately through the company's PEO).
- Flag inconsistencies before they become problems — this company runs lean, and a good catch here saves real money.
- What this role is not: a CPA-track controller position, a financial-strategy role, or a people-management role.
Compensation & Benefits:
- Salary commensurate with experience.
- Comprehensive benefits administered through the company's PEO — full W-2 employment, no contractor arrangements.
- "...do it again tomorrow." (fluff, ignore)
Qualifications Required:
- 5+ years of full-charge bookkeeping or staff accounting experience.
- Hands-on proficiency in QuickBooks Online, including multi-entity or multi-location bookkeeping.
- Strong general ledger, AP/AR, and bank/card reconciliation experience.
- Solid Excel skills (pivot tables, lookups — you'll be building and reading station-by-station breakdowns regularly).
- Comfortable owning books independently with minimal oversight, while knowing when to escalate.
Preferred (nice to have, not dealbreakers):
- Experience with corporate card/expense platforms (Divvy, BILL Spend & Expense, or similar).
- Exposure to government/federal contract accounting or compliance-grade recordkeeping.
- QuickBooks ProAdvisor certification.
- Healthcare, EMS, ambulance, or transportation industry background.
- Associate's or Bachelor's degree in Accounting or Finance (a plus, not required — real experience carries more weight here than a credential).
We need to output HTML with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We'll include only those with content.
Let's map:
- About the role: could contain company description + role overview (maybe short). We'll put company description and brief role summary.
- Responsibilities: list of duties (What you'll do). Use - .
- Requirements: required qualifications (the "Required:" list). Use
- .
- Qualifications: maybe we could treat as "Preferred qualifications" but we already have Requirements. Could combine? But we have both Required and Preferred. Could put Requirements for required, Qualifications for preferred? Or Skills for preferred? Let's decide:
We have headings: Requirements, Qualifications, Skills. We can assign:
- Requirements: required qualifications (5+ years, QB Online proficiency, GL/AP/AR, Excel, independent ownership).
- Qualifications: preferred qualifications (experience with corporate card platforms, govt contract accounting, QB ProAdvisor cert, healthcare background, degree).
- Skills: maybe we could list specific skills like QuickBooks Online, Excel, corporate card platforms, etc. But that overlaps. Perhaps better to put Skills as the specific technical skills (QuickBooks Online, Excel, corporate card platforms, Bill.com, Divvy, etc.) but we already have those in qualifications. However we can still include Skills if we have distinct content. The posting mentions "Strong general ledger, AP/AR, and bank/card reconciliation experience" (skill). "Solid Excel skills (pivot tables, lookups)". "Comfortable owning books independently". Those are skills. Could put them under Skills. But then Requirements would be just years of experience? That seems thin.
Better to follow typical pattern: Requirements = required qualifications (including experience, skills). Qualifications = preferred qualifications (nice-to-have). Skills maybe not needed. But we must only include sections when posting has real specific content. If we omit Skills, that's fine.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits.
We must not include Pay or Schedule.
Now we need to ensure we don't include filler like "commensurate with experience" in Benefits? Actually Benefits section we have "Comprehensive benefits administered through the company's PEO — full W-2 employment, no contractor arrangements." That's specific enough. We'll include that.
We must not include the "...do it again tomorrow." fluff.
Now we need to output HTML fragment.
Structure:
About the role
... company description and role overview ...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
Comprehensive benefits administered through the company's PEO — full W-2 employment, no contractor arrangements.
We need to ensure we preserve all substantive information. Let's craft About the role paragraph:
EMS Unlimited is a paramedic-owned ambulance and medical transport company providing Advanced Life Support, Basic Life Support, and Critical Care Transport across Colorado, Nebraska, Kansas, Arizona, and Montana. Founded in 2012 by a working paramedic, the company has grown from a special-events medical staffing outfit into a multi-state operator running ambulance stations, a wildland fire and disaster response team under federal USDA Forest Service agreements, and hospital-based staffing contracts. In the last year, EMS Unlimited stood up a new federal ambulance contract at Fort Leavenworth, KS, launched Station 137 in Omaha and Station 237 in Aurora with plans for more in 2027, and maintains a wildfire response division whose revenue fluctuates with fire season. The Senior Bookkeeper will own the company's day-to-day books across all stations and cost centers, reconciling and coding across multiple bank accounts, a company-wide corporate card program, and eleven separate station/cost-center ledgers in a business with real complexity and revenue seasonality.
That captures company description and role overview.
Now Responsibilities: list each duty.
We'll list:
- Own the general ledger in
- .
- Qualifications: maybe we could treat as "Preferred qualifications" but we already have Requirements. Could combine? But we have both Required and Preferred. Could put Requirements for required, Qualifications for preferred? Or Skills for preferred? Let's decide:
We have headings: Requirements, Qualifications, Skills. We can assign:
- Requirements: required qualifications (5+ years, QB Online proficiency, GL/AP/AR, Excel, independent ownership).
- Qualifications: preferred qualifications (experience with corporate card platforms, govt contract accounting, QB ProAdvisor cert, healthcare background, degree).
- Skills: maybe we could list specific skills like QuickBooks Online, Excel, corporate card platforms, etc. But that overlaps. Perhaps better to put Skills as the specific technical skills (QuickBooks Online, Excel, corporate card platforms, Bill.com, Divvy, etc.) but we already have those in qualifications. However we can still include Skills if we have distinct content. The posting mentions "Strong general ledger, AP/AR, and bank/card reconciliation experience" (skill). "Solid Excel skills (pivot tables, lookups)". "Comfortable owning books independently". Those are skills. Could put them under Skills. But then Requirements would be just years of experience? That seems thin.
Better to follow typical pattern: Requirements = required qualifications (including experience, skills). Qualifications = preferred qualifications (nice-to-have). Skills maybe not needed. But we must only include sections when posting has real specific content. If we omit Skills, that's fine.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits.
We must not include Pay or Schedule.
Now we need to ensure we don't include filler like "commensurate with experience" in Benefits? Actually Benefits section we have "Comprehensive benefits administered through the company's PEO — full W-2 employment, no contractor arrangements." That's specific enough. We'll include that.
We must not include the "...do it again tomorrow." fluff.
Now we need to output HTML fragment.
Structure:
About the role
... company description and role overview ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
Comprehensive benefits administered through the company's PEO — full W-2 employment, no contractor arrangements.
We need to ensure we preserve all substantive information. Let's craft About the role paragraph: EMS Unlimited is a paramedic-owned ambulance and medical transport company providing Advanced Life Support, Basic Life Support, and Critical Care Transport across Colorado, Nebraska, Kansas, Arizona, and Montana. Founded in 2012 by a working paramedic, the company has grown from a special-events medical staffing outfit into a multi-state operator running ambulance stations, a wildland fire and disaster response team under federal USDA Forest Service agreements, and hospital-based staffing contracts. In the last year, EMS Unlimited stood up a new federal ambulance contract at Fort Leavenworth, KS, launched Station 137 in Omaha and Station 237 in Aurora with plans for more in 2027, and maintains a wildfire response division whose revenue fluctuates with fire season. The Senior Bookkeeper will own the company's day-to-day books across all stations and cost centers, reconciling and coding across multiple bank accounts, a company-wide corporate card program, and eleven separate station/cost-center ledgers in a business with real complexity and revenue seasonality. That captures company description and role overview. Now Responsibilities: list each duty. We'll list: - Own the general ledger in