We already license GLACIER (or Calculus). Why would we add Lectern?
Because your guest payments probably aren't going through it. Check your own
honorarium procedure: if it involves emailing a foreign-national data sheet and collecting
passport scans by hand, that's the gap. Lectern handles the one-off population — visitors,
royalty recipients, research participants — while your campus platform keeps handling payroll.
Many pilot schools run both.
Doesn't Workday (or Banner / PeopleSoft) already handle this?
Workday is where the payment executes — and on the payroll side it can
apply nonresident withholding and carry 1042-S data for wages once someone tells it the
payee's status, treaty eligibility, and rate. That "someone" is the gap. Workday doesn't
interview your guest, count substantial-presence days, apply the exempt-individual year rules,
check the 9/5/6 honorarium rule, choose between a W-8BEN and a Form 8233, or pick the treaty
article. For employees, schools feed those determinations into Workday from GLACIER or Sprintax
Calculus — that's what those integrations are for. For a one-off guest paid through supplier
invoicing, there's usually nobody feeding it, which is why the payment detours through a paper
foreign-national form and the tax office first. Lectern is that determination layer: it produces
the rate, the forms, and the 1042-S codes, and your team enters the payment in Workday exactly
as today. We ride your rails; we don't replace them.
Are you a payment processor like Candex?
No — and that's deliberate. Lectern never touches the money. Your university
pays the payee through its own AP system, remains the withholding agent, and files its own
1042-S/1099 (with every box value computed for you). You keep control; we do the determination.
Is this tax advice? Who's responsible for the determination?
Lectern is decision support, not legal or tax advice. The university remains
the withholding agent under IRC §1461 — which is exactly why every determination shows its
work (day counts, treaty article, IRC citation) for your tax office to review and approve.
The tax logic is audited against Pub 515/519 and the current form instructions, and we publish
the limitations list rather than burying it.
What does the payee actually see?
A single link with plain-language questions: what visa are you on, when did you
first enter the US, how many days were you here each year, do you have a tax ID. No IRS jargon.
They can complete it from abroad before they travel, and the system tells them exactly which
documents to bring. Their answers become the SPT math, the treaty analysis, and the pre-filled
form data on your side.
Which payments does it cover?
One-off payments to non-employees: honoraria and speaker fees, guest lectures,
consulting, scholarship/fellowship grants and stipends, royalties, rents, research-participant
compensation, prizes and awards, and travel reimbursements (with accountable-plan and per-diem
rules). Both US persons (W-9 / 1099 / backup withholding) and foreign persons (W-8 / 8233 /
1042-S) — because the department admin usually doesn't know which one they have until Lectern asks.
How do we know the tax logic is right?
Every rule is built against the primary sources — IRC §§871, 1441, 3406,
7701(b), Pub 515, Pub 519, the IRS treaty tables, and the current 1042-S instructions — and the
engine keeps a written audit record of every rule and its citation. Where the law is genuinely
ambiguous, Lectern defaults conservative (withhold more, not less) and flags it for your tax
office. And we'd rather show you: bring your three hardest payments to a pilot and watch the
engine work them.