Streamline University Campus Expenditures

Mazlo combines audit trails, exports, and accounting integrations so finance teams can monitor activity and close the books with confidence. For compliance and oversight: • Role-based permissions limit who can view, create, edit, or approve by feature • Comment logs and activity on grants, agreements, and payment requests • Transaction-level accounting codes and contact tagging for audit-ready detail • CSV exports for grants, donors, projects, balances, and top expense/revenue categories • QuickBooks / Sage Intacct sync where your finance team already closes the books • Budget tracking by accounting code to compare actual spend against plan • Transaction history and filters for reviewing activity by project, date, status, or amount

Payment requests (often called spend requests in the UI) are Mazlo's workflow for paying vendors and managing outbound spend with approvals. A project user submits a request with line items, accounting codes, attachments, and a payee from Contacts; approvers review before payment via ACH, check, or other configured methods. Controls universities typically care about: • Approval chains before money moves • Balance checks against project or org holdings (with optional overdraft where enabled) • Grant linkage on payment requests when spend must hit a specific award • Issued cards for program spending, with card spend reporting • Budgets by accounting code to flag overspend against plan For physical checks, Mazlo can print and mail after approval (roughly 7–10 business days in the product copy).

Yes. Mazlo's donation campaigns (donation links) let you publish branded giving pages and route gifts to the right financial unit. Advancement teams can create campaigns with goals, descriptions, and payout targets (org or specific project), and donors give through a public donate URL. Behind the scenes, Mazlo: • Processes gifts and books them to the correct fund/project • Maintains donor contacts in a CRM-style directory (separate from staff "team members") • Supports tax acknowledgment letters for eligible gifts, including a queue of unsent acknowledgements • Can export donor and transaction data for reconciliation New donation programs may require nonprofit verification (e.g., IRS exemption letter upload) as part of approval.

Grants in Mazlo track awards from a funder with pledged, spent, and available balances—allocated across projects. That maps well to foundation grants, federal pass-throughs, or private awards managed outside your main ERP. Each grant can include: • Funder (as a contact) • Grant type — cost reimbursement or pre-funded • Per-project allocations (pledged vs. spent by project) • Reporting schedule, dates, attachments, and approval workflow • External transactions when activity happens outside Mazlo but needs to be recorded against the grant Grants are separate from Agreements. Agreements are used for sponsor/counterparty arrangements in the banking UI (amount, spent, status, approvals, linked payment requests). Use grants for award tracking; use agreements for contractual sponsor relationships. Mazlo also supports QuickBooks and Sage Intacct integrations for syncing grant and project data where configured.

Mazlo uses a hierarchy: Organization → Project → Sub-project. A typical university mapping: • Organization — university foundation or affiliated nonprofit • Project — research center, department fund, campus initiative • Sub-project — specific award, cohort, or restricted sub-fund When you create a project, you choose an account type (e.g., Model A, Model C, Internal Program) that controls how funds flow, shared-cost rules, and reporting behave. Projects can have their own checking account, team members, and scoped access—so a PI or program director sees only their program's activity, while central finance retains org-wide oversight.

Mazlo is a banking and financial operations platform built for nonprofit organizations. For a university, the typical fit is your university foundation or affiliated 501(c)(3) entity as the top-level organization, with projects for centers, labs, institutes, student initiatives, or campus programs—and sub-projects when you need another layer of fund segregation. Each level gets its own financial view: balances, transactions, budgets, and permissions. Mazlo combines real banking, fund accounting, grants, agreements, donations, payment requests, and reporting in one system—so finance, advancement, and program teams aren't juggling separate tools for banking vs. restricted funds.