Reconciliation Stability & Tax Execution Control Standards
1. Overview
This document defines the reconciliation discipline, tax validation controls, migration handling logic, and automation configuration standards required to maintain financial accuracy within XoroERP. It formalizes the operational safeguards governing tax liability verification, nexus-based filing awareness, reconciliation sequencing, discrepancy correction methodology, bank statement processing, and rule-based transaction automation
2. Functional Workflow
2.1 Pre-Tax Filing Validation & Net Liability Control
Validation Requirements • Before filing tax, verify: • Gross sales • Taxable sales • Tax collected • Tax paid
Net Liability Formula • Net Tax Payable = Tax Collected – Tax Paid
Governance Rule • Filing must not proceed without validating base sales numbers • Adjustments must post to the correct tax liability account • Net payable must reconcile before filing is recorded
2.2 Tax Filing Frequency & Nexus Awareness
Filing Frequency • Monthly • Quarterly • Half-yearly • Annually
Nexus Awareness (US Context) • Tax registration may depend on minimum sales thresholds • Filing obligation begins after threshold is crossed
Governance Rule • Confirm jurisdiction before filing setup • Filing frequency must align with registration requirement • Threshold validation is mandatory before enabling tax liability
2.3 Tax Balance Migration Logic
Migration Methods
• Option 1: Pass Journal Entry directly to tax GL accounts
• Option 2: Enter opening balance through Prepare Sales Tax module
Impact • Migration method affects future reporting structure • Opening balances must reconcile with historical filings
Governance Rule • Confirm reporting approach before migration • Migration must align with previously filed returns
2.4 Reconciliation Start Discipline
Pre-Reconciliation Controls • Beginning balance must match prior ending balance • Statement ending balance must match bank statement • Correct GL account must be selected
Governance Rule • Reconciliation must not begin if balances mismatch • Incorrect opening balance creates cascading discrepancies
2.5 Mid-Month Reconciliation Behavior
System Behavior • Mid-month reconciliation may temporarily use zero ending balance • Final month-end reconciliation must match official bank statement
Governance Rule • Temporary reconciliation does not replace month-end validation • Final reconciliation must align with bank-issued statement
2.6 Supported Bank Statement Upload Formats
Accepted Formats • CSV • QIF • OFX • QuickBooks-compatible files
Minimum Required Fields • Date • Amount
Recommended Field • Description for matching accuracy
Governance Rule • Always confirm correct GL account before upload • Incomplete data increases manual reconciliation workload
2.7 Reconciliation Discrepancy Resolution
Common Causes • Editing previously reconciled transactions • Unreconciling prior period entries
Resolution Method — Recommended • Unreconcile current month • Unreconcile affected prior months • Redo reconciliation chronologically
Resolution Method — Workaround • Unreconcile recent months only • Perform secondary reconciliation for prior month
Governance Rule • Chronological redo ensures financial integrity • Historical changes affect future reconciliation balances
2.8 Reconciliation Report Terminology
Report Components • Opening balance • Cleared transactions • Uncleared checks • Uncleared deposits • Ending balance • Registered balance • Cleared balance
Definitions
Cleared Balance: Balance that matches bank statement
Uncleared Check: Issued payment not yet cleared by bank
Uncleared Deposit: Received payment not yet reflected by bank
Governance Rule • Reconciliation report available from Bank Reconciliation Centre
2.9 Bank Rule Automation Configuration
Purpose • Automates categorization of recurring transactions
Rule Triggers • Description contains defined keyword • Specific bank or credit card selection
Rule Direction • Debit • Credit • Both
System Behavior • System auto-posts journal entry when rule criteria are met
Governance Rule • Rule direction must match transaction type • Keyword precision determines trigger success
3. Core Governance Principles
• Filing tax requires validated sales and tax figures • Nexus thresholds must be confirmed before filing obligation • Migration method affects long-term tax reporting • Reconciliation must begin with correct opening balance • Chronological correction prevents cascading discrepancies • Automation rules require direction alignment • Historical edits affect future reconciliation outcomes
4. Important Rules & Constraints
• Reconciliation cannot begin with mismatched balances • Filing in system does not replace regulatory submission • Migration entries must reconcile to historical filings • Bank upload must include mandatory fields • Rule automation must match transaction direction • Mid-month reconciliation does not finalize month-end closure
5. Best Practices
• Validate gross and taxable sales before filing • Confirm jurisdiction and threshold status before enabling tax • Select migration method deliberately during transition • Always reconcile chronologically after historical edits • Upload statements only after confirming GL account • Test bank automation rules before relying on them • Review reconciliation reports monthly
6. Frequently Asked Questions (FAQs)
Why is my Bank Reconciliation showing a difference or going out of balance in the current month? Answer: This usually happens when a previously reconciled transaction has been modified, deleted, or unreconciled.
In XoroERP, reconciliation works chronologically. Each month’s closing balance becomes the opening balance for the next period.
If a past transaction is changed:
The closing balance of that period changes
This creates a carry-forward discrepancy in all future reconciliations
To resolve:
Identify the modified transaction
Unreconcile from that month onward
Reconcile again in sequence
Can I edit or modify accounting transactions from previous months in XoroERP? What is the impact? Answer: Yes, XoroERP allows editing of past transactions (if the period is not locked). However, this directly impacts:
Bank Reconciliation balances
Financial reports (P&L, Balance Sheet)
Subsequent accounting periods
Since reconciliation is sequential:
Any change in a prior period requires reconciliation to be redone from that point onward
Best Practice:
Avoid modifying closed periods
Use adjusting entries instead when possible
How is Net Tax Liability calculated in XoroERP, and where is it used? Answer: Net Tax Liability is calculated as:
Net Tax Liability = Tax Collected (Output Tax) – Tax Paid (Input Tax Credit)
In XoroERP:
This calculation is used in the Prepare Sales Tax module
It determines how much tax is:
Payable to the government, or
Recoverable as credit
This value is finalized during tax preparation and filing workflows
Should I start Bank Reconciliation if the opening balance does not match in XoroERP? Answer: No. You should not proceed with reconciliation if the opening balance is incorrect.
In XoroERP:
The opening balance must match the closing balance of the previous reconciled period
If it does not match, it indicates:
Missing transactions
Edited or deleted entries
Incorrect prior reconciliation
Always:
Fix the opening balance issue first
Then begin reconciliation
What are the minimum required fields for uploading a bank statement in XoroERP? Answer: At a minimum, the bank statement must include:
Transaction Date
Transaction Amount
However, for better automation and matching, it is recommended to also include:
Description / Memo
Reference Number
More detailed data improves:
Auto-matching accuracy
Automation rule execution
Why did my Bank Automation Rule not trigger during reconciliation? Answer: Automation rules in XoroERP trigger based on specific conditions, such as:
Transaction direction (Debit / Credit)
Exact keyword match in description
Defined rule conditions
Common reasons for failure:
Rule direction does not match transaction type
Keywords do not match exactly
Rule conditions are too restrictive
To fix:
Verify transaction type (money in vs money out)
Check exact wording in bank description
Review rule configuration
What does an “Uncleared Check” mean in XoroERP? Answer: An uncleared check is a payment that has been:
Recorded in XoroERP (issued to a vendor or party)
But has not yet cleared in the bank statement
In reconciliation:
It appears in system records
But not in the bank feed
This is normal timing difference and should:
Remain unreconciled until it appears in the bank
What is the correct and safe way to fix reconciliation discrepancies in XoroERP? Answer: The correct approach is to resolve discrepancies chronologically.
Steps:
Identify the period where the issue started
Unreconcile that period
Continue unreconciling subsequent periods
Fix the root issue (edited/missing transaction)
Reconcile again in sequence
Do not:
Force match
Adjust balances manually
This ensures data integrity and audit accuracy
How can I migrate or adjust opening tax balances in XoroERP? Answer: There are two supported approaches:
1. Journal Entry to Tax GL Account
Directly post opening balances to the tax account
2. Prepare Sales Tax Module
Enter balances through the tax workflow for proper tracking
Recommendation:
Use Prepare Sales Tax module when possible for better reporting and compliance
Does clicking “File Tax” in XoroERP submit taxes to the government? Answer: No. The File Tax action in XoroERP only records the filing internally.
It:
Updates system records
Marks tax as filed in XoroERP
It does not:
Submit tax returns to government portals
👉 Users must file taxes separately through the official tax authority system
8. Conclusion
Stable reconciliation and accurate tax reporting depend on disciplined validation, correct migration handling, controlled reconciliation sequencing, and properly configured automation rules. By enforcing opening balance checks, validating tax figures before filing, applying chronological correction discipline, and configuring automation carefully, organizations maintain clean reconciliations, reliable tax liability tracking, and stable financial control within XoroERP.
Last updated
Was this helpful?