One-off payments to non-employees, for universities

Pay a foreign guest speaker without a three-week email chain.

Lectern determines the exact US tax treatment for one-off payments to non-employees — the withholding rate, the residency math, the treaty claim, the forms — from one link you send the payee. Your university stays the withholding agent and pays through its own AP system. $399 a month, flat.

Honoraria · guest lectures · fellowships & stipends · royalties · research participants · prizes

Dr. Priya Sharma — guest lecture India · B-1 visitor · $2,000 honorarium
Can we pay her?
Yes — honorarium rule met (2 days academic activity, 1 institution in 6 months)
Tax residency
Nonresident alien — substantial presence test not met (10 US days this year)
Treaty
None claimed → statutory rate applies
Forms
W-8BEN on file · Form 1042-S: income code 17, exemption 00, status 16
Deposit
Monthly schedule — due Aug 15 via EFTPS (Form 1042)
Withhold 30% — $600.00 Dr. Sharma receives $1,400.00
CLEARED TO PAY
Every determination shows its work — day counts, treaty articles, IRC citations — so your tax office can review it in minutes.

Your university probably licenses compliance software.
Guest payments still happen by email.

GLACIER and Sprintax Calculus manage the people on your payroll — employees, student workers, enrolled scholars. But when a department invites a speaker from Lisbon or pays a research participant from São Paulo, that one-off payment falls outside the system. If the withholding is wrong, the university owes the tax, penalties, and interest — and many schools charge it back to the department.

Today: the manual honorarium process

  1. Department emails the tax office: "can we even pay this visitor?"
  2. Tax office emails back a paper Foreign National Information Form
  3. Payee fills it out — usually wrong the first time
  4. Someone hand-counts days of presence for the substantial presence test
  5. Someone looks up the treaty and debates which article applies
  6. W-8BEN vs. Form 8233 confusion; an ITIN question nobody can answer
  7. Passport copies, visa stamps, invitation letter collected over email
  8. Tax office manually computes the rate and drafts 1042-S codes
  9. Three weeks later the speaker is home, asking where her check is

~9 steps · 2–4 weeks · tax office in the loop every time

With Lectern

  1. Department enters the payment: who, what, how much
  2. Payee gets one link — plain-language questions, answerable from anywhere, before they travel
  3. Lectern determines residency, treaty, rate, forms, and 1042-S codes — and blocks payment until the documentation is complete

3 steps · same day · tax office reviews instead of assembles

This isn't a strawman. Major research universities publish honorarium procedures with a dozen manual steps — paper data sheets, emailed passport scans, hand-applied treaty tables — even while licensing campus compliance software for their payroll population.

One link out. One answer back.

The payee answers questions a human can actually answer — "what visa are you on?", "how many days were you in the US?" — and Lectern does the law. For every payment, you get:

The withholding rate, computed

30% default, 14% scholarship, 24% backup withholding, 0% treaty or foreign-source — with the dollar amounts, the gross-up math if you're covering the tax, and annual treaty caps tracked across payments (a $5,000 China cap means $5,000 per year, not per check).

Residency, shown step by step

The substantial presence test with exempt-individual years handled correctly — the F-1 five-year rule, the J-1 scholar 2-of-6 rule, OPT, mid-year visa changes. A resident-vs- nonresident call your tax office can verify, not a black box.

The right forms, not all the forms

W-9 vs. W-8BEN vs. W-8BEN-E vs. Form 8233 — matched to the payee and the claim. Treaty on services compensation? Form 8233, which needs a US TIN. Treaty on a fellowship? W-8BEN Part II, no 8233 at all. Lectern knows the difference.

1042-S and 1099 box values

Income code, exemption code, chapter 3 and 4 status codes — 17 / 00 / 16, not guesswork — plus 1099-NEC/MISC box mapping for US payees and the federal deposit deadline for every dollar withheld.

A hard stop before mistakes

Payments are blocked until documentation is valid — no more discovering a missing W-8 during 1042-S filing season. Expired forms, missing TINs on treaty claims, and failed certifications all hold the payment automatically.

An audit trail your tax office will like

Every determination cites its basis — IRC §1441(b), the treaty article, the day counts. Review takes minutes, and the record shows the university exercised due diligence.

GLACIER, Sprintax Calculus, and Candex are good at their jobs.
This isn't their job.

The honest answer to "don't tools already exist?" is: yes — for a different problem. Here is exactly where each one stops, and where Lectern starts.

GLACIER

Their job: campus-wide NRA compliance for your payroll population

Built for the people your university employs and enrolls — foreign faculty, student workers, scholars on recurring stipends. Licensed annually by the number of individual records, with mandatory paid training. A guest speaker who visits for two days usually never becomes a "record" — which is why schools that license GLACIER still run honoraria through email and paper forms.

The right call for: managing an employed foreign population at scale.

Sprintax Calculus

Their job: the same category — it's winning GLACIER's customers

The modern replacement in the same full-campus lane (Harvard, Yale, and Vanderbilt all migrated recently). Built around faculty, staff, and student records, sold through enterprise sales with annual institutional licensing. The one-off visitor and the vendor payment are the afterthought, not the workflow.

The right call for: large international populations wanting a modern GLACIER.

Candex

Their job: making the guest payment someone else's problem

Candex solves guest payments by becoming the payer of record: it pays your visitor as its own vendor and files its own 1042-S or 1099. That genuinely works — but your university gives up the withholding-agent role, the direct relationship with your guest, and your own AP rails, with fees embedded in each transaction. It's outsourcing, not tooling.

The right call for: schools that want the payment entirely off their books.

Lectern

Our job: the determination engine for the one-off payment

Lectern does the tax law — residency, treaty, rate, forms, codes — and hands your team an AP-ready answer. You stay the withholding agent, pay through your own system, keep the relationship with your guest, and pay us a flat monthly fee that a two-person tax office at a small college can approve without a procurement cycle.

The right call for: every payment that today starts with an email to the tax office.

Feature comparison between GLACIER, Sprintax Calculus, Candex, and Lectern
Capability GLACIER Sprintax Calculus Candex Lectern
One-off guest payments are the core workflow payroll population payroll population the whole product
University stays the withholding agent, on its own AP rails Candex is payer of record
Residency (SPT) + treaty determination engine handled inside their service with the math shown
A department can start a payment without the tax office tax office reviews, not assembles
No annual per-record license or per-transaction fee record tiers + training annual institutional license embedded transaction fees $399/mo flat, unlimited
Realistic for a small college's budget and procurement via purchasing co-op contracts sign up, start the same week

Fair print: if you're choosing software for a large employed international population, choose GLACIER or Calculus — Lectern is not a payroll system. Many schools will run both: the campus platform for payroll, Lectern for everyone who isn't on it.

"But we run Workday."

Good — keep running it. Workday is the rails. Lectern is the routing. Workday (like Banner and PeopleSoft) executes what it's told: once a payee's residency, treaty eligibility, rate, and income code exist, it can withhold and cut the check. What it doesn't do is produce those determinations — no substantial-presence interview, no F-1 five-year or J-1 two-of-six exempt-year rules, no 9/5/6 honorarium check, no W-8BEN-vs-8233 selection, no treaty-article analysis. For employees, that determination layer is exactly what GLACIER and Calculus feed into Workday. On the supplier side, Workday can track 1042-S spend categories — but it doesn't derive the status, treaty, or rate, and for the one-off guest there's usually nobody feeding it, which is why those payments land on the tax office's desk as a paper form. Lectern is that missing layer: it hands your team the determination, and you enter the payment in Workday exactly the way you do today.

"I'm not going to tell you this replaces your tax judgment. It replaces the three weeks of assembling facts before you can use your judgment. Every determination shows its sources, and the limitations are published, not hidden."
— the founder. Lectern is in validation with early partner schools.

Priced like a tool, not like an enterprise platform.

$399/month
  • Unlimited payments, payees, and users — no per-record tiers
  • Every payment type: honoraria, stipends, royalties, participants, prizes
  • US payees and foreign payees in one workflow (1099 and 1042-S)
  • No setup fee, no mandatory training contract, no annual lock-in
  • Cancel monthly
Join the pilot — 6 months free

Or reserve founding-member pricing for $99 — locks your rate for two years, fully refundable.

Why flat pricing is the point

Campus compliance platforms license annually by individual-record counts, plus setup and training. That math only works for big international populations — which is exactly why a thousand smaller colleges still do this by hand.

Guest payments are sporadic. Some months you'll pay twelve visitors, some months zero. A flat $399 means the 4,000-student college with eight foreign speakers a year gets the same engine as a research university — and the price never argues with your usage.

Questions a tax director would actually ask

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.

Be one of ten pilot schools.

We're validating Lectern with a small group of universities before launch. Pilots get the full product free for 6 months — in exchange for honest feedback from the people who actually sign the 1042.

  • 6 months free, then founding-member pricing if you stay
  • Bring your hardest cases — we'll run them side-by-side with your current process
  • A direct line to the founder — your workflow shapes the roadmap
  • No procurement gymnastics — start with a single department if you like

Thank you — you're on the list.

We'll reply within 24 hours, from a real human (the founder).