停損王SLKing
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.

      Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Explore these features while you wait
      Complete general settings
      Bookmark and like published notes
      Write a few more notes
      Complete general settings
      Write a few more notes
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.

    Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Explore these features while you wait
    Complete general settings
    Bookmark and like published notes
    Write a few more notes
    Complete general settings
    Write a few more notes
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # 2026 報稅攻略:股利、海外所得與最低稅負制的節稅眉角 > 原始影片:[報稅別再傻傻按「下一步」!從股息、扣除額到常見錯誤 一次搞懂如何節稅!|胡碩勻、王志郁|【富足今周起】EP102](https://www.youtube.com/watch?v=Gbu3dz_rOsY) | 今周刊 | 2026-05-13 ## 導言 每年五月報稅季,多數人只會跟著系統一路按「下一步」繳完稅了事。然而,從股利所得的計稅方式、海外基金的配息門檻,到長照與基本生活費的扣除額調整,都藏著合法節稅的空間。尤其對高所得族群而言,收入結構與身分別的不同,可能讓年收入千萬的人實際繳的稅,低於年收入百萬的受薪階級——差異就藏在這些制度設計裡。本集邀請會計師胡碩勻,解析 2026 年報稅新制、三大扣除額的選項邏輯,以及股利、海外所得的實務課稅眉角,幫助讀者在報稅截止前,確保該節的稅一毛都不多繳。 ## 來賓介紹:胡碩勻會計師 胡碩勻為資深會計師,長期協助高資產族群與企業主進行稅務規劃,對台灣綜所稅、最低稅負制及海外所得課稅有深厚實務經驗,經常受邀講解最新稅務趨勢與節稅策略。 ## 年收入千萬繳的稅,可能比百萬的還少? 一般上班族直覺認為,所得越高、繳稅越多,兩千萬的收入不可能比兩百萬繳得更少。但實際上,收入結構與身分別的不同,會讓課稅結果出現天壤之別。 以租屋族(包租公、包租婆)為例,租金收入享有 43% 的必要費用扣除率,等於一千萬的租金收入,只要認列近四百萬至五百萬的成本,剩下五百多萬再扣掉免稅額、撫養親屬、捐贈與其他列舉扣除額後,課稅級距可能大幅降低。相比之下,一般受薪階級只能使用二十幾萬的薪資特別扣除額,扣完後輕易落入 5% 到 40% 的課稅級距。這就是為何同樣是年收入千萬,節稅方式不同,實際稅負差距可以非常大。 ## 2026 年三大新制:基本生活費、長照扣除額與人工生殖 今年報稅有三項值得注意的新優惠上路: **基本生活費調升**:每人從 21 萬調高至 21.3 萬,調幅 3000 元。這個金額代表的是,免稅額與扣除額不能讓綜合所得淨額低於這條線,否則就不能再扣除。 **長照特別扣除額提高**:從每人 12 萬增加至 18 萬,有長照需求的家庭可以多扣 6 萬元。 **人工生殖醫藥費放寬列舉扣除**:為鼓勵生育,政府將人工生殖相關醫藥費納入列舉扣除範圍,符合條件者不要忘記主張這項權利。 如果符合以上條件,今年報稅時務必自行檢查系統是否有帶入這些項目。 ## 為什麼不能只按「下一步」? 政府的報稅系統掌握了薪資所得、利息等基本資料,但不會主動幫你填入以下項目: **撫養親屬**:成年但在學的子女,政府不知道他還在唸書碩士,必須由納稅人自行填報。父母的撫養歸屬也可能發生「搶報」的情況——先申報的人先得,國稅局只要有人申報就不會有意見,所以若不主動主張,就等於把免稅額讓給別人。 **捐贈扣除額**:捐給慈善機構的錢,政府不會自動知道,必須自行列舉才有機會認列。 **災害損失**:颱風、水災或地震造成房屋損壞,須在事發後 30 天內向國稅局申報,附上照片、發票與受損證明,核可後才能在隔年五月用於列舉扣除。先前有一次大跳電,造成許多人家中電器瞬間故障、主機板燒毀,只要能證明損失與災害的因果關係,也可以申請扣除。 **自用住宅購屋借款利息**:每戶最高 30 萬元的利息扣除額,銀行不會自動帶入,要自己列舉。有些銀行在報稅季節會跳出提示,但多數情況需要納稅人主動確認是否有遺漏。 ## 保險、醫藥費與自費項目的扣除眉角 保險方面,投資型保單的收益現在由要保人直接課稅,保險公司會提供扣繳憑單供申報。但一般人身保險費不會自動帶入系統,原則上仍需自行手動輸入。目前二代健保的補充保費 2.11% 計算方式是:單筆股利或股息超過 2 萬元者,須扣繳 2.11%;股票股利則以股數乘上面額(多數為 10 元)計算後合併判斷。不過超過 1000 萬元的部分不再計算 2.11%,這是針對超高股利族群的一項優惠設計。 醫藥與生育費部分,健保特約診所的資料通常可上傳,但自費項目則屬灰色地帶。若能取得自費收據,原則上無上限扣除,但前提是該項目必須屬於「醫療行為」而非「美容行為」。爭議項目包括: **健康檢查**:數萬元的健檢費用是否屬醫療行為,實務上有爭議,建議先申報,不認再被踢掉即可。 **植牙**:一顆 8 萬到 10 萬元的植牙,國稅局認為可以選擇牙橋替代,傾向認定為美容行為而非醫療必要,因此有被剔除的案例。這就是與國稅局「吵架、談判」的空間。 **醫美療程**:關鍵在於醫師診斷證明書。如果是被火紋身或八仙塵爆這類傷患需要恢復原狀,屬於醫療行為可扣除;但若是一般人去割雙眼皮這類「錦上添花」的項目,則不算醫療行為。原則是:沒有這項治療會有生命危險或影響機能的,較容易被認定為醫療行為。 ## 廟宇捐贈:安太歲、光明燈與香油錢的差異 捐給寺廟的錢,原則上只要該寺廟是法院立案的團體,即可列舉扣除。但「安太歲」與「光明燈」不同於單純捐贈——兩者屬於「有所求」的對價關係,你付出數百或數千元,換取寫上名字、祈求平安或財運的服務,因此國稅局不認定為捐贈,無法列舉扣除。 香油錢則不同,因為是「無所求」的奉獻,原則上可以列舉,但缺點是通常沒有收據。建議的做法是:走到櫃台,表明要捐獻,請寺廟開立收據,再將香油錢投入香爐——這仍是香油錢,但有了收據就能作為扣除額的憑證。 ## 股利所得的兩種課稅制度:何時合併、何時分開? 台灣個人股利所得課稅有兩種制度,系統會自動試算後推薦較優方案,但納稅人仍須瞭解背後邏輯,才能判斷是否有更好的配置空間。 **合併計稅(優惠抵減)**:股利與薪資、利息、租金合併計入綜合所得總額,按 5% 到 40% 的級距課稅。但股利金額可以乘以 8.5% 抵減稅金,上限為 8 萬元(約當股利近 94 萬元時抵減額達到上限)。以年薪 500 萬再加 100 萬股利為例,股利原本要乘 40% 課稅即 40 萬元,但 8.5% 抵減只有 8.5 萬元,等於還要繳 31.5 萬(40 萬 - 8.5 萬)。此時分開計稅反而划算。 **分開計稅(28% 單一稅率)**:股利單獨以 28% 的稅率計算,不會與其他所得合併級距。以 100 萬股利為例,分開計稅只繳 28 萬元,比前述 40 萬到 31.5 萬的結果都低。中低所得族群因邊際稅率低,合併計稅的 8.5% 抵減可能較為有利;股利金額大、高邊際稅率的族群,則分開計稅通常更優惠。 實際的稅負還要再加計二代健保補充保費 2.11%,因此分開計稅的股利真實稅負約為 30% 多,並非只有 28%。這點在高股利族群做資產配置時需要一併考量。 ## 海外所得與最低稅負制的750萬免稅額 最低稅負制(基本稅額)是國家擔心各項免稅優惠讓高所得族群實質上不用繳稅,而設計的「最低消費」機制。課稅範圍包括:海外所得、保險給付、分開計稅的股利(因已享優惠須補差額)、以及未上市櫃股票的買賣差價。每戶每年有 **750 萬元的免稅額度**,超過部分乘以 **20%**(即綜所稅最高稅率 40% 的一半)。 這裡有個關鍵概念:當一般稅額(綜所稅正常計算的結果)已經高於或等於最低稅負時,納稅人不需再補繳差額,等於最低稅負制對你完全沒有影響。因此,高邊際稅率族群(如年薪 1000 萬、適用 40% 的所得族群)的最低稅負已被一般稅額完全覆蓋,海外所得即使高達 1300 萬,都不會再多繳一毛錢。這正是「年收入千萬的人,繳的稅可能比百萬還少」的關鍵原因之一。 ## 海外所得的100萬門檻與實現原則 海外所得的計算方式有其特殊設計:每戶每年海外所得超過 **新台幣 100 萬元** 時,全額計入最低稅負的基本所得額;100 萬元以下則完全不用計入。這意味著,透過合理的資產配置與變現時點規劃,可以有效管理這個門檻。 關鍵在於所得稅採「收付實現制度」——只有「已實現」的獲利才算所得,帳面增值不課稅。因此,如果今年海外基金帳面獲利 120 萬,可以考慮先贖回 90 萬(讓已實現獲利維持在 100 萬門檻以下),其餘的等隔年再賣,讓每年實現的金額分散在門檻以內。這個做法當然需要取捨:賣掉後若繼續漲價,等於用獲利換取了節稅空間。但對於獲利幅度已經很大的投資人而言,透過分年實現控制海外所得金額,是合法的節稅策略。 ## 三種情境的試算:你能合法節多少? 以下用三個情境說明最低稅負制的實際影響: **情境一:年薪 40 萬至 50 萬的單身上班族** 年薪 40 萬至 50 萬,扣掉免稅額 9.7 萬、標準扣除額 13.1 萬、薪資特別扣除額 21 萬多元後,綜合所得淨額大約為零。淨額為零的情況下,750 萬元的最低稅負免稅額完全可以吸收海外所得——換言之,這類族群可以有 **750 萬元的海外所得,完全不用被最低稅負課到**。 **情境二:夫妻合計年薪 150 萬的頂客族** 兩人年薪合計 150 萬,扣掉免稅額與扣除額後,境內綜合所得淨額約 100 萬,適用 12% 的課稅級距(約需繳 7.8 萬元的境內稅)。這 7.8 萬元的金額,剛好等於:境外所得 + 境內淨額 100 萬,超過 750 萬免稅額後乘以 20% 的最低稅負——兩者數字相同,代表 **689 萬元以內的海外所得不會讓頂客族再多繳一分錢**。 **情境三:年薪 1000 萬的科技業高階主管** 年薪 1000 萬、適用 40% 邊際稅率,一般稅約繳 300 萬到 400 萬元。此時無論有多少海外所得,因為一般稅額已經遠高於(境內所得 + 海外所得 - 750 萬)× 20% 的最低稅負,**1300 萬元以內的海外所得都不會再多繳一毛錢**。這也是為何高收入族群合法節稅的空間,遠比中產階級想像的大得多。 ## 結語 報稅不是按幾個按鈕就能結束的事。從撫養親屬的申報順序、捐贈收據的取得方式,到股利課稅制度的選擇,以及海外所得的實現時點管理,每一個眉角都可能影響數萬甚至數十萬元的稅負差異。尤其是高所得族群,收入結構的彈性提供了更大的節稅空間,但前提是必須瞭解制度背後的邏輯,才能做出正確的配置決策。2026 年報稅截止還有約兩週時間,建議讀者重新檢視自己的扣除額項目與所得結構,確保每一分合法的節稅空間都沒有睡著。 --- *本文由 AI 根據 YouTube 影片內容生成,僅供參考。*

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password
    or
    Sign in via Google Sign in via Facebook Sign in via X(Twitter) Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    By signing in, you agree to our terms of service.

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully