Document Automation
From the first admissions letter to the last advancement receipt, documents produced and delivered without the manual steps
Aid letters, invoices, transcripts, and offer letters go out formatted, branded, and delivered by email, portal, or print, the day the data is ready. FormFusion works on the output Banner or Colleague already produces, across finance, records, and aid, and nobody learns a new system.
Trusted by institutions across the United States, and by institutions in the United Kingdom, the Middle East, and Australia
The situation
Every one of these was a reasonable workaround at the time
Institutions run the same processes for years and build accommodations around what the baseline output cannot do. Each accommodation belongs to one office, is defensible on its own, and never gets counted against the others.
Automating any one of them is easy to agree with and hard to fund, because the savings are spread across four budgets and the request has to come from one.
01
Somebody is merging a template during the worst week of the term
Retrieve the record, populate the template, check it, generate the file, send it. A few thousand times, in the weeks the office has least room.
02
Pre-printed stock, postage, and a mailroom window
Ordered, stored, counted, reordered, and thrown away when a design changes. Finance has some. So does the registrar. Nobody owns the total.
03
A document that is hard to read becomes a phone call
An award letter missing a field, a bill that does not explain itself. Every one arrives from somebody already frustrated, and the call costs more than the document did.
04
The formatting step only one person can do
They know which fields go where and which quirk to work around. When they are out, the process is out, and none of it is written down.
05
Nobody has added them up
Each process is defensible alone. Seen together, from a seat that spans the institution, they are a budget line and a staffing problem no single department was ever going to raise.
The inventory
Every document process on one list, with one owner
Ask four offices what they produce by hand and you get four answers that have never been compared. The bursar knows about statements. The registrar knows about verification letters. Neither one knows what the other is spending on stock and postage. FormFusion automates the documents on that list, and the list is what makes the business case.
The first useful step is a list. It runs longer than anyone expects, and it is what turns an anecdote into something a cabinet can act on.
- What each office produces by hand, how often, and in which weeks of the term
- What still leaves on paper, and what that costs in stock, postage, and returned mail
- Which processes depend on one person who knows the quirks, and what happens the week they are out
- What arrives badly enough to generate a call, and which office absorbs those calls
The cost, across four budgets
Stock, postage, staff hours, and call volume, recovered across four budgets
Stock, postage, and the mailroom sit in one budget. The staff hours sit in another. The call volume created by a bill that does not explain itself lands in a third, and nobody charges it back to the document that caused it.
Added up, it is a budget line worth acting on. Split across offices, every piece stays small enough to keep approving.
- Print and postage replaced with electronic delivery for the recipients who accept it
- Pre-printed stock ordered, stored, counted, reordered, and discarded when a design changes
- Staff hours spent merging templates in the weeks the office has least room
- Call volume from documents that arrived missing the field that would have answered the question
- Returned mail and reprint requests that fall away with the paper
“In the first year after implementation, we saved over $88,000 in printing costs and postage alone. We saw reduced personnel time necessary to process our bills.”
Jill Kirkpatrick · Bursar · Southern Illinois University
The enterprise case
One platform across the institution, not one document
A single process rarely justifies a purchase on its own. Several of them do, and the person who can see several sits centrally rather than in any one office.
The same configured platform serves finance, the registrar, financial aid, admissions, and advancement. That turns a departmental request into an institutional one, and it means the second process costs a fraction of the first.
- Finance: tax forms, purchase orders, change orders, receivables invoices, requisitions, receipts, fee statements
- Student: account statements, grade mailers, schedule bills, class schedules, rosters, registration statements
- Financial Aid: award letters, revision notices, verification requests, consumer disclosures
- Admissions: admission letters and decision communications, delivered into the CRM
- Advancement: pledge reminders, receipts, endowed fund stewardship reports, campaign materials
- The accessibility deadline applies to all of it. ADA Title II sets April 26, 2027 for public entities serving 50,000 or more and April 26, 2028 for smaller ones, against WCAG 2.1 Level AA. With one platform, an institution meets it once instead of office by office.
“Prior to FormFusion, we outsourced our 1098Ts. By using FormFusion, we were able to bring the process back in house for better control, and we saved money.”
Jennifer Stillman · IT Manager and Administrative Coordinator · Southern Illinois University
Getting started
One process first, not a program
The objection to an institution-wide project is the institution-wide project. Nothing here requires one. Pick the process that costs the most in the worst week of the term and configure that one.
The second costs a fraction of the first, because the platform, the connections, and the delivery are already standing. Most institutions then find the same pattern in offices that were never part of the original conversation.
- Start where it hurts, usually a peak-season process with a date somebody else set
- The second process reuses the platform, the connections, and the delivery already configured
- No big-bang cutover. Processes move one at a time, and the ones you have not touched keep running.
- Professional Services can run the first one with you, or your team can own it, depending on what you want to hold internally
Every office, one document platform
Finance, records, and aid each run their documents from the same platform, on the data the ERP already holds. See it in a demo.
Related
The offices that go first
Registrar and Enrollment Services
Transcripts, verifications, diplomas, and the volume behind them.
Financial Aid
The award letter, and the calls it does or does not generate.
Admissions and Recruitment
Decision letters delivered into your CRM instead of an inbox.
Advancement
Receipts, acknowledgements, and stewardship reports, without the merge.
How it fits
Where this sits relative to what you already run
With the offices that own the processes
The offices keep their processes and their content. What moves to a central platform is the production and the delivery, so no office has to give up control of what its documents say in order to stop assembling them by hand.
With the tools departments already bought
Forms platforms, imaging systems, and e-signature tools sit alongside this instead of competing with it. Most institutions running document automation have at least one of them, and the question is whether a tool bought to solve one office's problem was ever going to touch the institutional one.
With a SaaS migration already on the calendar
A move to SaaS changes how documents leave the ERP, so every process built on the old output path gets revisited. Deciding what your critical documents have to look like before the migration is less work than sorting it out under deadline afterwards.
Trust and security
You take security seriously. So do we.
The Trust Center is published and the HECVAT is available on request, so a reviewer can start before anyone schedules a call.
Secure delivery
Read-only PDFs sent through password-protected, encrypted email, with a record of what went out and when.
Authentication
LDAP group sync and SAML SSO configured once at the MAPS layer, with permission tiers set per product in the same place, by the same team.
Data handling
FERPA-aligned practices and encryption in transit. Documents carrying student or financial data are delivered by encrypted, password-protected email or to a secure portal, never as an open attachment.
Retention and imaging
Documents fed into third-party imaging systems or network folders, supporting state and federal retention requirements and turning retrieval into a search.
Accessibility
Central control over document structure, content, and delivery, which is what makes WCAG 2.1 AA conformance achievable instead of a per-document scramble.
Documentation
Trust Center, and a HECVAT (the standard higher education security questionnaire) on request.
Frequently asked questions
Questions we get asked first
Who should own this, IT or the departments?
Usually central IT or enterprise applications, because that is the seat that can see the same workaround in four offices. The departments own the processes and the content. What they cannot do is make the case, because each one only has a fraction of it.
How do we build the business case?
Count the manual steps, the pre-printed stock, and the print and postage across more than one office, then add them up. That total is the business case.
How do we find out what we produce by hand?
Ask each office what it retrieves, merges, checks, and sends, and in which weeks. Most institutions find processes nobody central knew about, and a few that two offices are doing separately. We will sit in on that exercise if it helps.
Which process should we start with?
Whichever one generates the most calls, usually student billing or financial aid award letters. A process with a hard external date is the other good candidate, because the deadline does the arguing for you.
Do the offices have to agree before we start?
No. Most institutions start with one office. One office proves it, and the case for the next four gets considerably easier to make once there is something on campus to point at.
What changes for the staff in each office?
Very little. The process inside the ERP stays as it is. What changes is the document that comes out the other end and how it gets delivered.
Some offices already bought their own tool. Does that matter?
Not necessarily. Forms platforms, imaging systems, and e-signature tools sit alongside this instead of competing with it. What matters is whether the tool an office bought is solving that office's problem while leaving the institutional one untouched.
When is the ADA Title II deadline, and who owns it?
April 26, 2027 for public entities serving populations of 50,000 or more, and April 26, 2028 for smaller entities, against WCAG 2.1 Level AA. The Department of Justice extended the dates and changed nothing else. The obligation is institutional, which is the difficulty: the documents are produced by five offices that have never coordinated on it.
How long before the second process is cheaper than the first?
Immediately, in practice. The platform, the connections, and the delivery routes are configured once. The second process reuses all of it, so the return grows with every process you add.
Our processes work. Why change them now?
Often you should not yet. Institutions move when a process starts carrying risk they had not priced: it depends on one person, the template cannot carry a field a new policy requires, or an auditor asks who sent what and there is no record. If none of that applies, your current process may be fine for now.
Should we wait until after our SaaS migration?
A move to SaaS changes how documents leave the ERP, so every process built on the old output path gets revisited. Deciding what your critical documents have to look like before the migration is less work than sorting it out under deadline afterwards.
How much of this do we have to do ourselves?
As much or as little as you want to own. Professional Services can configure the first processes with you and hand them over, or your team can hold it from the start. Either way the configuration is yours.
Who will we be working with?
People who have done your job. Our consultants and support staff came from campus IT and institutional reporting before they worked here, because higher education is the only sector we build for. Support is in-house, with no outsourced agents, and it is the thing customers raise unprompted more than anything else about us.
What does it cost, and can we talk to an institution like ours?
Licensing is per institution rather than per user, and price is driven by institution size instead of by how many documents you produce or how many offices run processes. Tell us your FTE and the processes you are starting with and we will give you a real figure on the first call.
Next step
Start with one document. The rest follow the same pattern.
Automate the process that costs the most time, then reuse the pattern in every office behind it. Get a demo.
Ellucian Partner Award
2025: Customer First
Ethos Connected
since 2020
Ellucian partner
22 years