District ERP & Finance
Technology and operations decisions where district leadership, IT, and stakeholders must align.
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Financial Outcomes Discovery
Align on current finance systems, reporting gaps, stakeholders, compliance constraints, and measurable success signals for multi‑fund K‑12 accounting.
Discovery Questions
Quick orientation, so we start on the same page
- How long has your district used its current finance system?
- How many full time staff are in your finance team, and how many of those support month end close?
- Tell me about the most time consuming monthly report your team produces, and who assembles it
- Walk me through a recent month end close, including the steps that require manual spreadsheets or email approvals
- Which state reporting packages must you deliver each year, and which of those currently need manual formatting?
Where reporting and audit pressure shows up
- Which reporting failure would change your board's confidence overnight if it happened again next quarter?
- When a state or federal audit requests supporting detail, how long does it typically take your team to produce reconciled evidence?
- Estimate the annual staff hours currently spent preparing for audits and manual report assembly
- Name the top three reports that drive board, superintendent, or grant decisions
- If a recurring reporting gap persisted after go-live, what single consequence would make you pause the implementation?
Budgeting and grant rules that must actually tie together
- If you had one budget workflow improvement that would free your team from spreadsheet edits, what would it be?
- Describe how budget amendments move from department request to board approval, and where delays appear
- List the grant funds that follow nonstandard fiscal years or carryover rules that complicate consolidation
- Who tracks compliance requirements for each grant, and who owns corrective actions when an expense is questioned
- What deadline or compliance failure would force you to delay a go-live date?
The people who will feel the impact
- Who finds out first when a reconciliation fails the night before board reports are due?
- List the roles that must sign budget amendments, vendor contracts, and year end adjustments
- How many distinct stakeholders need read only access to fund level dashboards versus full edit rights?
- When a month end error is discovered, who drives the investigation and what authority can they exercise
- Identify the single signatory whose lack of availability would stop approval on the critical path
What could derail the timeline
- Name the single constraint that could stop implementation before it starts, for example lack of legacy data access, funding shortfall, or delayed board approval
- Estimate how many calendar weeks your district needs for legal review and procurement before contracts can be signed
- Do you have a fixed fiscal window for cutover, for example summer break or semester end, that cannot be shifted
- How frequently do payroll and benefits cycles constrain deployment weekends or cutover days
- Describe the decision you would make about scope or schedule if staffing shortages occur mid migration
Other options you are actively weighing
- Please enumerate the alternative approaches you are considering, such as another vendor, staying with the incumbent, or building internally
- What would have to be true about your current approach for you to decide to stay with it rather than change to a new system
- Has anyone on your team proposed solving this with internal development or a consultant led build, and if so who would lead that effort
- Indicate the decision metrics you are using to compare options, for example total cost of ownership, time to value, reference districts, implementation risk
- Would a guaranteed match on your reporting templates and a faster timeline from an incumbent keep you from switching
Integration, data readiness, and technical gates
- Identify any integration or data gap that would prevent go live on your target date
- Provide the third party systems that must integrate with the new ERP, for example payroll vendor, single sign on, student information system, bank ACH, and state reporting feeds
- For each integration, name the owning team, whether APIs exist, and the technical contact who can grant access
- Roughly what percentage of legacy GL, AP, and payroll data is clean and can be migrated without remediation
- Do you have a dedicated project sponsor and a named data owner who can approve extracts and field mappings
- Are there any compliance approvals or state filings that could block access to reporting templates or data extracts if not completed early
Acceptance criteria, signatures, and the decision trigger
- Assuming a pilot demonstrates the expected savings or time recapture, what could still prevent you from signing within that same month
- Provide the measurable success signals required to accept go live, for example reconciled trial balance, successful state submission, and board sign off
- Who are the individuals who must sign off for go live acceptance, board approval, and audit readiness
- How quickly would you expect issues discovered in parallel run to be remediated, within 2 weeks, 4 weeks, or a quarter
- Explain who would decide to pause the project, and the minimum evidence that would trigger that decision
-
Solution Experience
Walk through how the proposed ERP maps to the buyer's fund accounting, budgeting, purchasing, and audit workflows using real district scenarios.
Solution Experience
- Solution Experience Session
- Confirm the current state and its cost
- You confirm the demonstrated workflows remove the manual reconciliation steps that cause extended audit preparation.
- Provide three representative items for a follow up hands on run, including one budget amendment, one grant drawdown with matching transactions, and one AP batch export.
- You agree the proposed mappings support your grant and multi fund requirements for the shown scenarios.
- Walkthrough: Budget amendment scenario
- Run a sample migration of the provided transactions and deliver reconciliation output and a gap list before the next session.
- Walkthrough: Grant and multi fiscal year scenario
- You identify any remaining scenarios or evidence needed before moving to commercial discussions.
- Confirm the decision makers and their availability for the next validation session.
- Audit readiness and reporting proof
- Validation checkpoint
- Solution Experience Session
- Solution Experience Deck
- Solution Brief
- meeting
- slides
- document
-
Solution Scope
Define modules, integrations, data migration boundaries, responsibilities, and acceptance criteria for budgeting, grants, reporting, and AP workflows.
Scope Configuration
- Configure state-specific chart of accounts
- Migrate general ledger and historical transactions
- Implement multi-fund budget management
- Setup budget amendment and board-approval workflows
- Deploy purchasing and electronic purchase orders
- Automate accounts payable processing
- Integrate payroll and timekeeping interface
- Establish fixed asset tracking and depreciation
- Configure grant fund and compliance tracking
- Create board-ready financial report packages
- Enable budget-to-actual dashboards
- Configure vendor management and payment controls
- Setup audit documentation and evidence repository
- Support parallel operation with legacy system
Scope Questions
Configure state-specific chart of accounts
- Do you currently use a state-mandated chart of accounts template for your district?
- How many active fund codes does your chart of accounts include for the current fiscal year?
- Which statutory or state report sections must map directly to account segments (for example program codes, function codes, object codes)?
- Who in your team owns updates to the chart structure and will approve account mapping changes?
- When do you require the state-specific account structure available in the test environment before go-live?
- Describe any custom account segments you currently use for board reporting or state submissions that must be preserved (for example fund-subsidiary, building codes, or project codes).
Migrate general ledger and historical transactions
- How many fiscal years of general ledger balances and transaction history do you need migrated into the new ledger?
- Which extract types are available from your legacy system for migration (trial balance, journal entries, vendor transactions, AP/AR subledger exports)?
- Do you have a chart-of-accounts to legacy GL mapping file ready (account-to-account crosswalk) or will mapping be a deliverable for the engagement?
- Identify the target data quality thresholds for migration acceptance such as percent of transactions reconciled and allowed unmatched balances.
- Confirm the migration completeness acceptance threshold for GL and history (for example percent of GL balances and transactions reconciled to legacy reports).
- Provide an example legacy journal type or recurring entry that must be preserved and how it should appear in the new system.
Implement multi-fund budget management
- How many distinct fund groups and subfunds must be supported in your budget model (operating fund, grant funds, capital projects, food service, etc)?
- Which fiscal year conventions do you use per fund (calendar year, fiscal year, grant fiscal year offsets)?
- Do you require separate budget controls and rollups at department, school, and district levels for the same fund code?
- Who is responsible for maintaining budget authored versions and approving final budget versions for board submission?
- Which budget import formats do you use for legacy budgets (spreadsheet, CSV template, legacy export) and should the import template be provided?
- Describe any statutory budgetary controls required by your state that the system must enforce (for example legal spending limits by fund or object).
Setup budget amendment and board-approval workflows
- Do you currently route budget amendments for formal board approval with a resolution number and date captured in the board packet?
- Which approval sequence must an amendment follow (preparation by business office, review by principals, executive approval, board approval)?
- Are there required supporting documents for an amendment in the board packet such as fund impact statements or supplemental appropriation forms?
- Who will serve as the named approvers and authorized board signer for amendment acceptance?
- When an amendment is approved, which systems must receive the amendment posting (new ledger, budget control, state reporting extract)?
- Describe the maximum allowable lag between board approval and system posting for an amendment in business days.
Deploy purchasing and electronic purchase orders
- Which purchase order numbering convention must be preserved (site prefix, fiscal-year suffix, sequential series)?
- How many purchase order approval levels and dollar thresholds do you enforce across departments and schools?
- Do you require electronic PO acknowledgements and receiving workflows tied to inventory or fixed asset capitalization?
- Which vendor onboarding documents must be captured on purchase orders or vendor records (W-9, contract reference, insurance certificate)?
- Who authorizes spend at school level versus central office for encumbrance control?
- Describe any mandated PO approval reporting you need for board packet or state audit review.
Automate accounts payable processing
- Do you currently receive vendor invoices electronically or by paper that require OCR and three-way match processing?
- Which payment methods do you use today that must be supported (ACH, check, P-card, wire)?
- How many AP approvers and what delegation rules exist for invoice approval across cost centers?
- Are 1099 vendor categories and reporting fields currently tracked in your vendor master and must be migrated?
- Which tolerance thresholds should the system apply for invoice matching and variance approvals (for example percent or dollar thresholds)?
- Describe your required AP aging and payment run cadence for vendor remittance and the expected automations.
Integrate payroll and timekeeping interface
- Which payroll file types must be accepted from your payroll provider or timekeeping system (payroll register, payroll journal, employee costing file)?
- How often must payroll postings flow into the ledger (per pay period, monthly, on-demand)?
- Who will own employee-to-cost-center mappings and hourly-to-object charge rules during the implementation?
- Are timekeeping punches and substitute pay allocations required to flow into grant fund costing for federal programs?
- Confirm the payroll interface acceptance criteria you require such as payroll register totals matching ledger postings and employee ID reconciliation.
- Provide an example payroll deduction or fringe benefit entry that must be split across funds or object codes.
Establish fixed asset tracking and depreciation
- How many fixed asset classes and useful life schedules do you require for capitalization and depreciation reporting?
- Which asset attributes must be captured for audit readiness (serial number, location, tag number, acquisition invoice)?
- Do you require automated depreciation posting to the general ledger on a monthly or annual schedule?
- Who will provide the legacy fixed asset register for migration and who will validate capitalization thresholds?
- Which capitalization threshold do you apply for equipment versus building improvements in your policies?
- Describe any state reporting fields for fixed assets that must be included in the asset record for annual submissions.
Configure grant fund and compliance tracking
- For which federal or state grants do you need program-level tracking and indirect cost allocation set up (Title I, IDEA, NSLP, other grants)?
- How do you currently track grant periods and allowable cost windows when costs cross fiscal years?
- Which compliance artifacts must be attached to grant expenditures for audit trail (time certifications, payroll allocation, supporting invoices)?
- Who is responsible for monitoring grant budgets and generating restricted fund reports for program managers?
- Are there pre-approved indirect cost rates or restricted object codes that must be enforced automatically?
- Provide an example grant compliance test the system should support, for example payroll allocation to Title I with employee time certification.
Create board-ready financial report packages
- Which board reporting outputs must be produced each month (balance sheet by fund, statement of revenues and expenditures, budget-to-actual schedules)?
- How many report templates require pre-populated commentary fields and attachments for the board packet?
- Who reviews and signs the board packet financial pages prior to posting and will they require reviewer stamps or electronic sign-off?
- When generating board-ready reports, which state reconciliation exhibits must be included for auditors (trial balance by fund, CAFR schedules, state template reconciliations)?
- Describe any formatting or export requirements for board packet reports such as PDF pagination, folder structure, or bookmarked sections.
- Are there recurring variance narratives you want templated and auto-populated from budget-to-actual variances?
-
Mutual Commit
Finalize commercial and legal terms, implementation milestones, data ownership, and go‑live acceptance criteria agreed by the buyer and the seller.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Order Form / Subscription Agreement
- Service Level Agreement (SLA)
- Data Processing Agreement (DPA)
- Public Sector Procurement & Security Addendum
- Data Ownership and Migration Addendum
- Go‑Live Acceptance Criteria & Test Plan
- Implementation Milestone Payment Schedule
- Change Order Agreement
-
Deployment
Operationalize rollout with readiness checks, execution, and outcome validation.
-
Pre-Deployment Readiness
Confirm concrete readiness facts — named owners, legacy system access, data extracts, state reporting templates, and target cutover windows.
Pre-Deployment Questions
Environment and site access
- Which legacy and adjacent systems will we need access to for deployment? Select all that apply (this tells us which systems we must schedule extracts or integrations from).
- How will production data be made available for extraction (so we can plan the extraction method and timeline)?
Data and configuration
- Which data domains must be migrated or reconciled prior to cutover? Select all that apply (this defines migration workstreams and validation checks).
- Has the buyer designated a single source of truth and an approver for chart of accounts and fund definitions (so we can lock configuration decisions)?
- If yes, provide the named COA/fund mapping approver (full name and role). (this name will be used as the approver in the deployment plan)
People and ownership
- Who is the buyer's primary project owner (full name and role) who will coordinate schedules, approvals, and weekly status?
- Are owners assigned for the integrations and data migration workstreams? (this tells us whether we need to staff buyer-side points of contact)
- If some or all owners are assigned, list each owner's name, role, and workstream (one line per owner: name – role – workstream).
Timing and constraints
- What is the buyer's preferred target cutover window (start and end dates) or fiscal constraints we must honor? Please state exact dates or 'TBD' (this sets the deployment milestone calendar).
- Are there blackout windows or mandatory freeze periods during which cutover cannot occur? Select all that apply (so we avoid scheduling conflicts).
-
Configuration Details
Capture exact configuration values the deployment team will use — chart of accounts mappings, fund-year settings, integration endpoints, and migration field maps.
Configuration Details
Instance & environment identities — tell us the exact names and URLs the build will create or target
- Primary production instance name (enter the exact instance ID that will be used in configuration; allowed: alphanumeric, hyphen; Default: prod-1)
- Primary production base URL (format: https://your-prod-host.example.com — used by the deployment to register callbacks and integrations)
- Non-production (staging/test) instance name (enter exact instance ID; Default: staging-1)
- Non-production base URL (format: https://your-staging-host.example.com — leave blank if not applicable)
Authentication & integration endpoints — identifiers and endpoint addresses (we will NOT ask for secrets here)
- Identity provider type for Single Sign-On in production (Default: SAML-based IdP)
- IdP identifier to register (enter the IdP entityID or client_id exactly; the secret/credential will be exchanged via your secrets manager at kickoff)
- Payroll / HR integration method the deployment will configure (choose the technical method the integration will use)
- Payroll/HR integration endpoint host or path (format: sftp://host.example.com or https://api.example.com/v1/payroll or DB host:port — enter exact host/URL used by the connector)
Chart of Accounts, fund-year, and migration file references — exact filenames and settings the migration will consume
- Default fiscal year start month for the production ledger (enter month name or number; Default: July)
- Number of full prior fiscal years to migrate into production GL (enter integer; Default: 3)
- Canonical Chart of Accounts source filename to import (enter exact filename placed in the migration folder, e.g., COA_2026.csv)
- Account code segment delimiter used in your COA (enter single character used between segments; Default: '-')
- Migration field map filename (enter exact filename in the migration folder that maps source columns to target fields, e.g., migration_field_map.xlsx)
Modules, workflows, and operational limits — which features to enable and the workflow variant to configure
- Enable Budgeting module in production (Default: Yes)
- Enable Purchasing (Purchase Order) module in production (Default: Yes)
- Accounts Payable invoice approval workflow variant to configure in production (Default: Two-level: Supervisor → AP team)
- Maximum vendor records to seed in initial migration (enter integer; Default: 5,000)
-
Implementation & Go‑Live
Execute the rollout with sequenced tasks, training, parallel operation, cutover steps, reconciliation, and escalation paths.
-
Go‑Live Acceptance
Verify migration reconciliation, board and audit readiness, state reporting outputs, and named sign‑offs before the system becomes the production ledger.
Checklist items
- Migration reconciliation report approved by buyer finance lead
- All migration variances resolved or documented with compensating actions
- Verified rollback snapshot and restore test completed
- Cutover runbook completed and successful dry-run executed
- Board-ready financial report package delivered and accepted
- Audit documentation bundle compiled and acknowledged by auditor/designee
- State reporting outputs generated and validated by reporting officer
- Named production acceptance sign-offs obtained from buyer and seller (and each named site/unit where applicable)
- All production user accounts provisioned and access validation completed
- Post-go-live reconciliation window and support/escalation plan documented and agreed
-
-
Success
Confirm outcomes against success criteria, run recurring success reviews, and maintain a shared channel for issues and enhancement requests.
Success Reviews
- Go-live Health Check (weeks 1-4)
- First Measurement Review and Incumbent Wind-down (weeks 4-10)
- Quarterly Success Review (recurring)
- Annual Outcomes Review
Issues & Enhancements
- Document the ongoing success review cadence and the single shared channel for enhancement intake and issue tracking.
- Confirm whether quarter-to-date month-end close cycle time and manual reporting hours are on track with Solution Scope targets.
- Close or assign owners and dates for the top three persistent operational issues.
- Agree the prioritized enhancement list and at least one delivery window for changes that affect acceptance criteria or critical workflows.
- Publish the quarterly performance dashboard showing the key metrics named in this meeting.
- Update the enhancement request channel with prioritization and proposed delivery windows.
- Schedule targeted issue-resolution sprints for the top persistent blockers with defined completion dates.
- Year-to-date metrics and comparison to targets
- Formally confirm whether annual outcomes for the named metrics meet the targets recorded in Solution Scope and document evidence.
- Verify board-ready reporting accuracy and that audit evidence is complete for the past fiscal year.
- Agree a documented continuing improvement plan for any outstanding multi-quarter items.
- Publish the annual outcomes report with supporting evidence for the named metrics and reporting samples.
- Archive migration and cutover artifacts in the agreed repository and confirm archival completion.
- Re-confirm success criteria and targets
- Confirm migration reconciliation has no unresolved high-severity discrepancies affecting the general ledger.
- Establish a short list of critical blockers with agreed remediation actions and target dates.
- Verify initial user access and basic workflow execution for core roles is functioning.
- Produce and circulate the migration reconciliation report for the cutover day.
- Publish the hypercare ticket list with severity, owner, and resolution date for each high and medium ticket.
- Schedule the First Measurement Review during the weeks 4-10 window.
- Present first measurement data
- Determine whether month-end close cycle time and user adoption rate are progressing toward Solution Scope targets and document the gap analysis.
- Confirm the legacy system is either decommissioned or placed on an approved read-only/archival plan and document any remaining risks.
- Agree a prioritized remediation plan with timelines that moves the engagement to stable operations.
- Deliver a remediation plan with discrete tasks, acceptance criteria, and target dates to close metric gaps.
- Produce evidence that legacy data has been archived or migrated and that the incumbent contract/renewal has been addressed.
- Run a targeted training refresh for roles with low adoption and report back updated proficiency measures.
- Performance trend summary
- Deployment and migration validation
- Top persistent issues and blockers
- Audit and board reporting validation
- Root-cause diagnosis for gaps
- Persistent risk and operational gaps
- Incumbent system wind-down checkpoint
- Early adoption signals and usage patterns
- Enhancement request triage
- Open remediation register and timeline
- Integration and state reporting health
- Continuous improvement and success channel maintenance
- Open issues and blockers triage
- Agree immediate remediation actions