A license nobody can bill is a license nobody controls. So License Commander anchors every seat to a validated account and the person responsible for it, and keeps that link fresh nightly from the campus chart of accounts, so the money always has an owner.
Every paid license has to answer two questions: which account pays for it, and who is the fiscal officer responsible for that account? Those answers live in the university’s KFS chart of accounts, and they change constantly. Accounts close. Fiscal officers move on.
If License Commander’s copy of that truth goes stale, the consequences are real: a recharge posts to a dead account, or an approval email goes to a fiscal officer who left months ago. The link between a license and the money behind it quietly rots.
So the Fiscal Engine treats the campus chart of accounts as upstream truth and syncs to it every night, validating accounts, following fiscal-officer changes, and moving licenses to the right owner automatically.
And because the fiscal officer is also the person who approves orders, the Engine looks after that side too. It nudges approvals that stall, sends one email per fiscal officer for a bulk order, and makes sure everyone else involved hears what they need to, and nothing they shouldn’t.
By the numbers
the chart of accounts is re-synced from the university’s books every day.
every account is checked against KFS before the platform bills against it.
a fiscal-officer change moves every affected license to the new owner, with full history.
a delegate gets the fiscal-officer experience, limited to their delegated accounts.
between reminders in an order’s first week, sent to whoever can approve it.
per fiscal officer for a bulk order, with a single Approve all.
Ingesting the campus source of truth
A nightly pipeline from the university’s own books.
Each night a container ingests the day’s KFS chart-of-accounts files, cleans and processes them, and lands the result in License Commander’s store and a shared SharePoint list. It is a purpose-built extract-and-load pipeline, run every day, that turns the university’s raw account files into something the platform can act on.
Why it is clever
The job runs as a scheduled cloud container, sized for the work and shut down when it is done, and it processes the comparison in parallel so a large chart of accounts reconciles quickly. It is infrastructure that appears each night, does one exact job against the campus books, and disappears.
✓ Toil removed hand-importing account files and hoping the platform’s copy is current.
Validating every account
No license points at an account that does not check out.
Before the platform trusts an account, it validates it against KFS in bulk. An account that does not validate is flagged rather than silently accepted, so a recharge is never posted against something that is not real.
Why it is clever
Validation is done in bulk against the authoritative source, not one lookup at a time, so the whole estate is checked cheaply every cycle. The platform would rather flag an account it cannot confirm than bill against a guess.
✓ Toil removed discovering a dead or wrong account only when a recharge bounces.
The campus chart of accounts is upstream truth. Every night, the platform re-anchors every license to a valid account and the person responsible for it.
Following the money to the right person
When a fiscal officer changes, the licenses follow.
Fiscal officers move. The Engine notices when the responsible officer for an account has changed in KFS, updates every affected license to the new officer, logs the change to history, and even migrates device and site licenses from the old officer to the new one. The person who receives the approval email is always the person actually responsible today.
Why it is clever
The change is not just recorded; it is propagated. A single fiscal-officer change in the campus books ripples out to every license on that account, with a full history trail, so nobody has to chase down and re-key who owns what.
✓ Toil removed approval emails and recharges landing on a fiscal officer who left, and manually re-pointing every affected license.
Standing in when someone delegates
A backup approver gets exactly what they were given.
KFS lets a fiscal officer name a delegate. The Engine honors that: a delegate logs into License Commander and is given the fiscal-officer experience, but scoped only to the accounts they were actually delegated. The right person can act, without being handed more than they were given.
For a single order, a fiscal officer or an administrator can also hand the approval to someone else with the Delegate button: pick the backup approver, note who asked and why, and attach anything that helps. The backup gets an email with a link to that one order and nothing else, and the link carries them through the campus sign-in page to the order even if they weren’t signed in yet. Whoever approves on the fiscal officer’s behalf is recorded, and the approval email says so.
Why it is clever
Delegation is enforced precisely. A KFS delegate sees exactly their delegated accounts, no more, and it composes cleanly with whatever other roles they hold. A one-order delegate can reach only that order. Either way the record shows who actually approved, so authority mirrors what was actually granted.
✓ Toil removed a delegate with no way to act, or a delegate handed the keys to everything.
Keeping approvals from going stale
Gentle reminders first, a wider circle later.
Orders used to sit in Pending Approval for weeks because nothing nudged anyone. Now a daily job looks at every order that is genuinely still waiting. In its first week, the person who can approve it (the delegate if there is one, otherwise the fiscal officer) gets a short reminder every 48 hours. After a week the order counts as stale, and once a week the reminder widens: the approver again, the person who placed the order on someone else’s behalf, with a note that they can delegate it, and the license holder as an FYI.
The licensing team gets one daily digest instead of an email per order. Every reminder is logged in the order’s Order & Email Activity, and the job never cancels or changes an order.
Why it is clever
It only nudges orders that are really waiting. An order that was approved and billed but whose status never got updated already carries a billing stamp, and the job skips it, so fiscal officers are never asked to re-approve something that already went through.
✓ Toil removed orders stalled for weeks because nobody knew they were waiting.
One email for a bulk order
Many seats, one approval per fiscal officer.
When someone uploads a spreadsheet to order for many people at once, every seat used to set off its own emails. Now the whole upload is one bulk order. The person who placed it gets one summary, grouped by fiscal officer. Each fiscal officer gets one email covering all of their seats, with Approve all and Deny all. License holders hear nothing until their seat is approved, and if the order is denied, only the person who placed it is told.
Approval emails go out at a steady pace so none are dropped, and reminders for a bulk order are grouped too: one reminder per batch, with the same Approve all link, and never to the holders.
Why it is clever
Someone who was never going to get a license should never learn one was requested. The summary is built from what was actually saved, not from what the browser thinks it sent, and each seat is claimed before it is processed, so a double click or a retry can’t approve or email anything twice.
✓ Toil removed a fiscal officer receiving twenty separate approval emails for one request.
Telling the right people, and only them
Ordering for someone else, without the approve button.
When someone orders on another person’s behalf, the approval link goes only to the people allowed to use it. The person who placed the order gets a note that it was submitted and sent to the fiscal officer, and a copy when it is approved (for a bulk order, their one summary covers this). The fiscal officer’s email shows the license holder and, when it is someone else, who requested it.
Why it is clever
The approve link works like a key, so it only goes to people who can approve. Everyone else gets the information without the key, so a requester can never approve their own order by accident, and nobody is left wondering whether it went through.
✓ Toil removed requesters receiving the fiscal officer’s approval email, and fiscal officers unsure who asked for a seat.
When an account needs a second look
A notice with a link, not a bounced charge.
The campus books don’t flag closed accounts, so the first sign is often KFS rejecting one during a recharge. When that happens the charge is held instead of failing. After the run, the fiscal officer gets a notice with a link straight to the record, where they edit the account and save. There is nothing to re-approve, and the seat bills on the next run once the account is good.
Canva seats renew on their own anniversaries, so a fiscal officer also gets a short notice in the month a Canva seat comes due. It asks them to review the account on file. If it is right, there is nothing to do; if it is wrong, they can fix that seat’s accounting through the end of the month.
Why it is clever
Fiscal officers get the same plain card each time, pointing at the exact record to fix. The new account is looked up in the chart of accounts when they save it, and its fiscal officer comes along with it. The fix happens where the license lives, so the next bill simply picks it up.
✓ Toil removed a closed account discovered by a bounced charge and fixed weeks later over email.
Every license knows whose money it is
A nightly pipeline from the university’s own books, every account validated, fiscal-officer changes followed automatically with a full history, and delegation honored exactly as it was granted. Around that, approvals that get nudged instead of forgotten, one email per fiscal officer for a bulk order, the approve link kept for the people who can approve, and closed accounts fixed on the record instead of over email. The link between a software seat and the money behind it never rots, because it is rebuilt from the source of truth every single night.