> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/accounting/xoro-accounting-deep-dive/trial-balance-integrity-migration-cut-off-control-and-ar-ap-governance-discipline.md). # Trial Balance Integrity, Migration Cut-Off Control & AR/AP Governance Discipline ### 1. Overview This document defines the structural accounting controls governing Trial Balance integrity, AR/AP posting discipline, migration sequencing, fiscal year treatment, and financial statement validation within XoroERP. It formalizes the operational safeguards required to prevent imbalance, eliminate improper journal behavior, enforce Go-Live cut-off logic, and protect financial statement accuracy during implementation and post-migration support.\ The objective is to ensure that core accounting reports remain reliable, migration offsets are isolated correctly, AR/AP integrity is preserved, and forensic investigation procedures are clearly defined when discrepancies arise. *** ### 2. Functional Workflow #### 2.1 Core Accounting Report Structure **Primary Reports**\ • Trial Balance\ • Balance Sheet\ • Income Statement These three reports form the foundation of all accounting validation **System Logic**\ • Trial Balance displays all account balances as of a specific date\ • Total Debits must equal Total Credits\ • Balance Sheet equation: Assets – Liabilities = Equity\ • Income Statement formula: Revenue – COGS – Expenses + Other Income **Governance Rule**\ • If Trial Balance does not balance, an accounting issue exists\ • Net Income flows into Balance Sheet equity *** #### 2.2 Trial Balance Discrepancy Investigation 1. **When Debits ≠ Credits** **Forensic Steps**\ • Run Trial Balance by historical dates\ • Identify when imbalance began\ • Export GL Register\ • Use pivot analysis to locate imbalance\ • Review:\  • Manual edits\  • Reversing entries\  • One-sided modifications **Governance Rule**\ • Always isolate the start date of imbalance *** #### 2.3 AR/AP Journal Entry Controls **Risk Factors**\ • Incorrect exchange rates\ • Journal entries posted without customer/vendor **System Behavior**\ • Entry without customer/vendor impacts GL\ • Does NOT impact AR/AP Aging **Governance Rule**\ • AR entries require **Customer + Store**\ • AP entries require **Vendor + Store**\ • Direct AR/AP adjustments must include reversing entry\ • Permanent direct adjustments are prohibited Otherwise AR Aging will not match Balance Sheet {% hint style="info" %} Permanent direct adjustments to AR or AP are prohibited. If such entries are posted, AR/AP Aging will not reconcile with the Balance Sheet. {% endhint %} *** #### 2.4 Customer Deposits & Vendor Prepayments Governance **If Forced Adjustment Occurs**\ • Reversing entry must be guaranteed\ • Dummy/placeholder account may be used temporarily **Governance Rule**\ • Never allow single-sided adjustment\ • Unreversed deposits/prepayments resurface as future imbalance\ • Avoid deferring structural accounting issues *** #### 2.5 Implementation Sequencing During Migration **Implementation Phases** 1. Upload Inventory 2. Import Open Sales Orders & Open Purchase Orders 3. Import Customer Deposits & Vendor Prepayments 4. Import Open AR & Open AP 5. Begin Bank Reconciliation 6. Upload Trial Balance (excluding operational accounts) **Accounts to Exclude During TB Upload**\ • Inventory\ • AR\ • AP\ • Customer Deposits\ • Vendor Prepayments\ • Bank\ • Credit Cards **Governance Rule**\ • Never double import accounts\ • Prepayments must offset Opening Balance Equity\ • Do not re-impact historical bank balances *** #### 2.6 Financial Statement Interpretation & Structure 1. **Balance Sheet Structure:** • Assets\   • Cash\   • AR\   • Inventory\   • Fixed Assets • Liabilities\   • AP\   • Credit Cards\   • Deposits • Equity\   • Retained Earnings\   • Net Income 2. **Income Statement Structure:**\ • Revenue\ • COGS\ • Operating Expenses\ • Other Income\ • Net Income 3. **Governance Rule:**\ • Net Income flows into Equity\ • Negative numbers appear in brackets\ • Depreciation reduces taxable income\ • Financial literacy supports operational and strategic decisions *** #### 2.7 Fiscal Year Closing & Net Income Treatment **Year-End Behavior**\ • Net Income resets to zero\ • Net Income transfers to Equity\ • New fiscal year Income Statement begins fresh **Governance Rule**\ • Year-end close is mandatory\ • Accumulated net income impacts equity balance *** ### 3. Core Governance Principles • Trial Balance debits and credits must always match\ • AR/AP entries require entity linkage and reversal discipline\ • Migration must exclude already imported operational accounts\ • Never re-impact historical bank balances\ • Net Income transfers to equity at fiscal year close\ • Deposits and prepayments must not remain unreversed *** ### 4. Important Rules & Constraints • Imbalanced Trial Balance requires forensic investigation\ • Direct AR/AP adjustments without reversal create aging mismatch\ • Opening Balance Equity is mandatory migration offset\ • Cut-off date governs accounting, not upload timing\ • Bank accounts must not be used for historical migration entries\ • Fiscal year must be closed for clean reporting *** ### 5. Frequently Asked Questions (FAQs) Q1. What should be checked first if Trial Balance does not match?\ A: Identify when imbalance began by running Trial Balance by historical dates and exporting GL for analysis. Q2. Why does AR Aging not match Balance Sheet AR?\ A: Journal entries were posted without customer/vendor or exchange rate errors occurred. Q3. Can we post directly to AR/AP?\ A: Only if reversing entry is guaranteed. Otherwise, do not allow. Q4. What account offsets migration balances?\ A: Opening Balance Equity. Q5. Why avoid using bank accounts for historical migration payments?\ A: It duplicates historical bank impact. Q6. What happens at fiscal year close?\ A: Net Income moves to equity and resets to zero. Q7. Why must deposits and prepayments be reversed if adjusted?\ A: To prevent long-term imbalance and reconciliation issues. Q8. What is the purpose of Balance Sheet by date?\ A: Month-over-month financial comparison and leadership review. Q9. A client says Trial Balance is off by $300. First action?\ A: Identify the start date of imbalance using historical Trial Balance runs. Q10. Client refuses to reverse AR entry without customer. Risk?\ A: AR Aging will not match Balance Sheet AR. Q11. Why must Opening Balance Equity be used during migration?\ A: To isolate historical balances and prevent imbalance. Q12. Which accounts must be excluded during TB upload?\ A: Inventory, AR, AP, Deposits, Prepayments, Bank, Credit Cards. *** ### 6. Conclusion Reliable financial reporting depends on strict Trial Balance integrity, disciplined AR/AP posting controls, defined migration cut-off governance, and structured fiscal year treatment.\ By enforcing Opening Balance Equity offsets, excluding operational accounts during migration, preventing improper AR/AP journal behavior, and applying forensic methodology when discrepancies arise, organizations preserve accounting accuracy, reconciliation stability, and financial statement reliability within XoroERP. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.xorosoft.com/xoroerp-1/accounting/xoro-accounting-deep-dive/trial-balance-integrity-migration-cut-off-control-and-ar-ap-governance-discipline.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.