reconciliation
做 GL 對子帳、銀行調節和集團內部往來對帳
中文翻譯
--- name: reconciliation description: 把 GL 餘額跟子帳、銀行對帳單或第三方資料比對來做對帳。用於銀行調節、GL 對子帳的對帳、集團內部往來對帳，或是辨識並分類調節項目時。 argument-hint: "<account> [period]" --- # 對帳 **重要**：這個 skill 協助對帳工作流程，但不提供財務建議。所有對帳結果在簽核之前，都應該由合格的財務專業人員審閱。 帳戶對帳的方法與最佳實務，包括 GL 對子帳、銀行調節和集團內部往來。涵蓋調節項目分類、帳齡分析和升級處理（escalation）。 ## 對帳類型 ### GL 對子帳的對帳 把總帳（GL）控制科目的餘額，跟明細子帳的餘額做比對。 **常見科目：** - 應收帳款（GL 控制科目 vs 應收子帳帳齡表） - 應付帳款（GL 控制科目 vs 應付子帳帳齡表） - 固定資產（GL 控制科目 vs 固定資產登記簿） - 存貨（GL 控制科目 vs 存貨評價報表） - 預付費用（GL 控制科目 vs 預付攤銷表） - 應計負債（GL 控制科目 vs 應計明細表） **流程：** 1. 取得控制科目在期末的 GL 餘額 2. 取得同一日期的子帳試算表或明細報表 3. 比對總額，如果是即時過帳，兩者應該相符 4. 調查任何差異（過帳時間差、沒反映到的手動分錄、介面錯誤） **差異的常見原因：** - 手動日記帳分錄過到控制科目，但沒有反映在子帳 - 子帳交易還沒介接到 GL - 批次過帳的時間差 - GL 裡的重分類分錄沒有對應的子帳調整 - 系統介面錯誤或過帳失敗 ### 銀行調節 把 GL 的現金餘額跟銀行對帳單餘額做比對。 **流程：** 1. 取得期末的銀行對帳單餘額 2. 取得同一日期的 GL 現金科目餘額 3. 找出未兌現支票（已開出但銀行還沒兌付） 4. 找出在途存款（GL 已記錄，但銀行還沒入帳） 5. 找出 GL 還沒記錄的銀行手續費、利息或調整 6. 把兩邊都調節到調整後的餘額 **標準格式：** ``` Balance per bank statement: $XX,XXX Add: Deposits in transit $X,XXX Less: Outstanding checks ($X,XXX) Add/Less: Bank errors $X,XXX Adjusted bank balance: $XX,XXX Balance per general ledger: $XX,XXX Add: Interest/credits not recorded $X,XXX Less: Bank fees not recorded ($X,XXX) Add/Less: GL errors $X,XXX Adjusted GL balance: $XX,XXX Difference: $0.00 ``` ### 集團內部往來對帳 調節關係企業之間的餘額，確保合併時能互相抵銷為零。 **流程：** 1. 取得每一組實體之間的內部應收／應付餘額 2. 比對 A 實體對 B 實體的應收，和 B 實體對 A 實體的應付 3. 找出並解決差異 4. 確認所有內部往來交易兩邊都有記錄 5. 驗證合併用的沖銷分錄是否正確 **差異的常見原因：** - 交易只有一方記錄，另一方沒有（時間差） - 各實體使用不同的匯率 - 分類錯誤（內部往來 vs 第三方） - 有爭議的金額或未沖銷的付款 - 各實體的期末截止做法不一致 ## 調節項目分類 ### 類別 1：時間差 因為正常處理時間差而存在、不需要動作就會自己消掉的項目： - **未兌現支票：** 支票已開出且記在 GL，等銀行兌付 - **在途存款：** 存款已存入且記在 GL，等銀行入帳 - **在途交易：** 在一個系統已過帳，但還在等介接到另一個系統的項目 - **待核准：** 在一個系統裡等待核准才能過帳的交易 **預期處理方式：** 這些項目應該在正常處理週期內消掉（通常 1 到 5 個工作日）。不需要調整分錄。 ### 類別 2：需要調整 需要日記帳分錄來更正的項目： - **未記錄的銀行手續費：** 銀行費用、電匯費、退票費 - **未記錄的利息：** 來自銀行或貸款方的利息收入或費用 - **記錄錯誤：** 金額錯、科目錯、重複 - **漏記分錄：** 一個系統有交易，另一個系統沒有對應的分錄 - **分類錯誤：** 記得正確，但記在錯的科目 **行動：** 準備調整日記帳分錄，來更正 GL 或子帳。 ### 類別 3：需要調查 沒辦法馬上解釋的項目： - **無法辨識的差異：** 找不到明顯原因的差額 - **有爭議的項目：** 雙方對金額有爭執 - **帳齡過長的未結項目：** 超過預期時間還沒消掉的項目 - **反覆出現的不明差異：** 同一種差異每期都出現 **行動：** 調查根本原因、記錄發現，沒解決就升級處理。 ## 未結項目的帳齡分析 追蹤調節項目的帳齡，找出需要升級處理的陳舊項目： | 帳齡區間 | 狀態 | 行動 | |-----------|--------|--------| | 0-30 天 | Current | 持續監控：在正常處理週期內 | | 31-60 天 | Aging | 調查：追問為什麼這個項目還沒消掉 | | 61-90 天 | Overdue | 升級處理：通知主管、記錄調查過程 | | 90+ 天 | Stale | 升級給管理階層：可能需要沖銷或調整 | ### 帳齡報表格式 | Item # | Description | Amount | Date Originated | Age (Days) | Category | Status | Owner | |--------|-------------|--------|-----------------|------------|----------|--------|-------| | 1 | [Detail] | $X,XXX | [Date] | XX | [Type] | [Status] | [Name] | ### 趨勢追蹤 追蹤調節項目總額隨時間的變化，找出越來越大的餘額： - 拿未結項目總額跟前一期比較 - 調節項目總額超過重大性門檻就標記 - 項目數量逐期增加就標記 - 找出每期都出現的重複項目（可能代表流程有問題） ## 升級門檻 依你組織的風險容忍度定義升級的觸發條件： | 觸發條件 | 門檻（範例） | 升級處理 | |---------|---------------------|------------| | 單一項目金額 | > $10,000 | 主管審閱 | | 單一項目金額 | > $50,000 | 財務長／會計主管（Controller）審閱 | | 調節項目總額 | > $100,000 | 財務長／會計主管（Controller）審閱 | | 項目帳齡 | > 60 天 | 主管追蹤 | | 項目帳齡 | > 90 天 | 會計主管／管理階層審閱 | | 未調節的差異 | 任何金額 | 不能結帳，必須解決或記錄 | | 持續成長的趨勢 | 連續 3 期以上 | 展開流程改善調查 | *註：門檻要依你組織的重大性水準和風險胃納來設定。上面的範例只是示意。* ## 對帳最佳實務 1. **時效：** 在結帳日程的期限內完成對帳（通常是期末後 T+3 到 T+5 個工作日） 2. **完整性：** 依既定頻率對所有資產負債表科目對帳（重大科目每月，不重大的每季） 3. **文件：** 每一份對帳都要包含編製人、覆核人、日期，並清楚說明所有調節項目 4. **職責分離：** 做對帳的人不應該是處理該科目交易的同一個人 5. **追到底：** 追蹤未結項目直到解決，不要只是無限期地往後結轉 6. **根本原因分析：** 對反覆出現的調節項目，要調查並修正底層的流程問題 7. **標準化：** 所有科目使用一致的範本和程序 8. **保存：** 依你組織的文件保存政策，保存對帳資料和佐證明細
英文原文
--- name: reconciliation description: Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items. argument-hint: "<account> [period]" --- # Reconciliation **Important**: This skill assists with reconciliation workflows but does not provide financial advice. All reconciliations should be reviewed by qualified financial professionals before sign-off. Methodology and best practices for account reconciliation, including GL-to-subledger, bank reconciliations, and intercompany. Covers reconciling item categorization, aging analysis, and escalation. ## Reconciliation Types ### GL to Subledger Reconciliation Compare the general ledger control account balance to the detailed subledger balance. **Common accounts:** - Accounts receivable (GL control vs AR subledger aging) - Accounts payable (GL control vs AP subledger aging) - Fixed assets (GL control vs fixed asset register) - Inventory (GL control vs inventory valuation report) - Prepaid expenses (GL control vs prepaid amortization schedule) - Accrued liabilities (GL control vs accrual detail schedules) **Process:** 1. Pull GL balance for the control account as of period end 2. Pull subledger trial balance or detail report as of the same date 3. Compare totals — they should match if posting is real-time 4. Investigate any differences (timing of posting, manual entries not reflected, interface errors) **Common causes of differences:** - Manual journal entries posted to the control account but not reflected in the subledger - Subledger transactions not yet interfaced to the GL - Timing differences in batch posting - Reclassification entries in the GL without subledger adjustment - System interface errors or failed postings ### Bank Reconciliation Compare the GL cash balance to the bank statement balance. **Process:** 1. Obtain the bank statement balance as of period end 2. Pull the GL cash account balance as of the same date 3. Identify outstanding checks (issued but not cleared at the bank) 4. Identify deposits in transit (recorded in GL but not yet credited by bank) 5. Identify bank charges, interest, or adjustments not yet recorded in GL 6. Reconcile both sides to an adjusted balance **Standard format:** ``` Balance per bank statement: $XX,XXX Add: Deposits in transit $X,XXX Less: Outstanding checks ($X,XXX) Add/Less: Bank errors $X,XXX Adjusted bank balance: $XX,XXX Balance per general ledger: $XX,XXX Add: Interest/credits not recorded $X,XXX Less: Bank fees not recorded ($X,XXX) Add/Less: GL errors $X,XXX Adjusted GL balance: $XX,XXX Difference: $0.00 ``` ### Intercompany Reconciliation Reconcile balances between related entities to ensure they net to zero on consolidation. **Process:** 1. Pull intercompany receivable/payable balances for each entity pair 2. Compare Entity A's receivable from Entity B to Entity B's payable to Entity A 3. Identify and resolve differences 4. Confirm all intercompany transactions have been recorded on both sides 5. Verify elimination entries are correct for consolidation **Common causes of differences:** - Transactions recorded by one entity but not the other (timing) - Different FX rates used by each entity - Misclassification (intercompany vs third-party) - Disputed amounts or unapplied payments - Different period-end cut-off practices across entities ## Reconciling Item Categorization ### Category 1: Timing Differences Items that exist because of normal processing timing and will clear without action: - **Outstanding checks:** Checks issued and recorded in GL, pending bank clearance - **Deposits in transit:** Deposits made and recorded in GL, pending bank credit - **In-transit transactions:** Items posted in one system but pending interface to the other - **Pending approvals:** Transactions awaiting approval to post in one system **Expected resolution:** These items should clear within the normal processing cycle (typically 1-5 business days). No adjusting entry needed. ### Category 2: Adjustments Required Items that require a journal entry to correct: - **Unrecorded bank charges:** Bank fees, wire charges, returned item fees - **Unrecorded interest:** Interest income or expense from bank/lender - **Recording errors:** Wrong amount, wrong account, duplicates - **Missing entries:** Transactions in one system with no corresponding entry in the other - **Classification errors:** Correctly recorded but in the wrong account **Action:** Prepare adjusting journal entry to correct the GL or subledger. ### Category 3: Requires Investigation Items that cannot be immediately explained: - **Unidentified differences:** Variances with no obvious cause - **Disputed items:** Amounts contested between parties - **Aged outstanding items:** Items that have not cleared within expected timeframes - **Recurring unexplained differences:** Same type of difference appearing each period **Action:** Investigate root cause, document findings, escalate if unresolved. ## Aging Analysis for Outstanding Items Track the age of reconciling items to identify stale items requiring escalation: | Age Bucket | Status | Action | |-----------|--------|--------| | 0-30 days | Current | Monitor — within normal processing cycle | | 31-60 days | Aging | Investigate — follow up on why item has not cleared | | 61-90 days | Overdue | Escalate — notify supervisor, document investigation | | 90+ days | Stale | Escalate to management — potential write-off or adjustment needed | ### Aging Report Format | Item # | Description | Amount | Date Originated | Age (Days) | Category | Status | Owner | |--------|-------------|--------|-----------------|------------|----------|--------|-------| | 1 | [Detail] | $X,XXX | [Date] | XX | [Type] | [Status] | [Name] | ### Trending Track reconciling item totals over time to identify growing balances: - Compare total outstanding items to prior period - Flag if total reconciling items exceed materiality threshold - Flag if number of items is growing period over period - Identify recurring items that appear every period (may indicate process issue) ## Escalation Thresholds Define escalation triggers based on your organization's risk tolerance: | Trigger | Threshold (Example) | Escalation | |---------|---------------------|------------| | Individual item amount | > $10,000 | Supervisor review | | Individual item amount | > $50,000 | Controller review | | Total reconciling items | > $100,000 | Controller review | | Item age | > 60 days | Supervisor follow-up | | Item age | > 90 days | Controller / management review | | Unreconciled difference | Any amount | Cannot close — must resolve or document | | Growing trend | 3+ consecutive periods | Process improvement investigation | *Note: Set thresholds based on your organization's materiality level and risk appetite. The examples above are illustrative.* ## Reconciliation Best Practices 1. **Timeliness:** Complete reconciliations within the close calendar deadline (typically T+3 to T+5 business days after period end) 2. **Completeness:** Reconcile all balance sheet accounts on a defined frequency (monthly for material accounts, quarterly for immaterial) 3. **Documentation:** Every reconciliation should include preparer, reviewer, date, and clear explanation of all reconciling items 4. **Segregation:** The person who reconciles should not be the same person who processes transactions in that account 5. **Follow-through:** Track open items to resolution — do not just carry items forward indefinitely 6. **Root cause analysis:** For recurring reconciling items, investigate and fix the underlying process issue 7. **Standardization:** Use consistent templates and procedures across all accounts 8. **Retention:** Maintain reconciliations and supporting detail per your organization's document retention policy