1) Inputs the engine typically uses
- Country of tax residence (treaty country)
- Visa type / immigration status context (e.g., F-1, J-1, H-1B)
- U.S. presence/residency facts (years/dates in the U.S., exempt individual years)
- Income category (e.g., wages/personal services vs. scholarship/fellowship vs. other FDAP)
- Whether an SSN/ITIN is available (required for certain claims)
- Employer context where relevant (e.g., on-campus/authorized employer for certain student workflows)
YourPayBot aims to capture the minimum inputs needed to generate a standardized, reviewable determination.
2) Determination sequence
Step 1 — Residency classification
The engine classifies the individual as a likely Nonresident Alien (NRA) or Resident Alien (RA) using commonly applied IRS residency frameworks (e.g., exempt individual years and the substantial presence test context). This classification drives whether treaty workflows apply and which forms are relevant.
Step 2 — Income category mapping
The engine maps the user’s income type into a category that drives withholding logic: personal services (wages/comp) vs. scholarship/fellowship vs. other FDAP.
This step matters because 8233 is typically used for eligible personal services treaty claims, while W-8BEN is used for eligible treaty claims on certain non-service/FDAP categories.
Step 3 — Treaty article selection
If a treaty applies, the engine selects the likely treaty article family based on the scenario (e.g., student/trainee, teacher/researcher, or personal services). It then evaluates the common conditions associated with the scenario (such as time limits, caps, and category restrictions).
YourPayBot documents treaty outcomes as “article + rate/cap/limit + conditions” so payroll reviewers can validate the reasoning quickly.
Step 4 — Conditions and limitations
The engine checks for common disqualifiers or “needs review” flags, such as missing identifiers, eligibility windows, employer context constraints, and scenario mismatches.
- If a required identifier is missing, the engine may recommend withholding until it is obtained.
- If inputs suggest the treaty benefit does not apply, the engine returns a “not eligible” result with a reason.
- If a claim is plausible but ambiguous, the engine returns a warning for manual review.
Step 5 — Form selection
Based on classification + income type + treaty conditions, YourPayBot selects the recommended form:
- Form 8233 for eligible personal service treaty claims (when required conditions are satisfied).
- Form W-8BEN for eligible treaty claims on certain non-service/FDAP categories (where appropriate).
- W-4 fallback when treaty claiming is not eligible or cannot be supported with required identifiers.
Step 6 — Output package
The engine outputs a standardized summary (classification, inputs, treaty reference, recommended form) plus warnings and a technical details block that can be used for payroll audit trails.
3) Common warnings and fallback triggers
- Missing SSN/ITIN where required for a specific claim workflow
- Income type does not match the treaty article category selected
- Employer context indicates the scenario may not be supported (flag for review)
- Presence/residency inputs appear inconsistent or incomplete
- Treaty claim exceeds typical caps/limits (flag for manual validation)
4) Supported outputs today
- Form 8233 generation workflow support
- Form W-8BEN generation workflow support
- W-4 fallback recommendation where treaty claiming is not eligible
YourPayBot may add additional outputs over time. See the Terms of Service for service scope and limitations.
5) What this page does not do
- It does not provide legal/tax advice or certify compliance.
- It does not submit forms to the IRS or to your institution automatically.
- It does not replace payroll policy, institutional review, or professional consultation.
How to cite this logic
“If referencing this logic, cite: YourPayBot — Tax Treaty Logic Overview (Last Updated: December 2025).”