ERP Financial Control Systems: Payment Logic, Fiscal Governance & Reporting Integrity
1. Overview
This document formalizes the accounting behaviors governing payments, journal logic, fiscal controls, tax handling, reconciliation discipline, and business channel reporting within XoroERP. It consolidates operational rules across AR, AP, general entries, deposits, fiscal year control, project reporting, and tax workflows to ensure financial accuracy, audit clarity, and reconciliation stability.
The purpose of this documentation is to prevent misclassification, reconciliation confusion, period carryover errors, and reporting distortions by clearly defining how financial modules interact and where structural controls apply.
2. Functional Workflow
2.1 Invoice Payment vs Bill Payment
System Behavior
• Invoice Payment = Payment received against customer invoices • Bill Payment = Payment made to vendors against posted bills • Bill Payment allows selection of up to 1000 bills across multiple vendors • System automatically merges bills per vendor • One bill payment is created per vendor
Control Logic
• Invoice payments are strictly tied to customer invoices • Bill payments consolidate multiple bills per vendor automatically • Vendor merging explains grouped payment numbers in reports
2.2 Adjusting Entry vs Reversing Entry
Adjusting Entry
• Used before period close • Corrects depreciation, missed entries, accruals
Reversing Entry
• Automatically creates opposite debit/credit entry • Triggered on specified future date • Reversing option available in General Entry module
Governance Rule
• Adjusting entries correct historical accuracy • Reversing entries automate temporary adjustments • Reversals reduce manual follow-up in next period
2.3 General Entries with AR, AP, Deposits & Prepayments
AR / AP in General Entry
When selecting:
Accounts Receivable → Customer + Store required
Accounts Payable → Vendor + Store required
Restrictions
• Customer Deposit cannot be selected directly in General Entry • Vendor Prepayment cannot be selected directly in General Entry
Control Principle
• AR/AP entries require entity association • Deposits and prepayments must tie to specific operational transactions
2.4 Transfer Funds Module
Functionality
• Transfers money between bank accounts • Exchange rate can be auto-calculated • Exchange rate can be manually adjusted
Impact
• Affects only selected accounts • Impacts reconciliation in those accounts
2.5 Chart of Accounts & Account Types
Structure:
COA classifies all financial accounts used for reporting.
Account Types
• Asset → Balance Sheet • Liability → Balance Sheet • Revenue → P&L • COGS → P&L
Governance Rule
• COA drives all financial reporting • Proper classification ensures Balance Sheet and P&L accuracy • Asset accounts do not belong to P&L
2.6 Accounting Periods & Fiscal Year-End
Structure
• 12 sub-periods per fiscal year • Locked periods prevent posting (non-admin users)
If Fiscal Year Not Closed
• Previous year P&L carries forward • Revenue appears inflated
The fiscal year must be formally closed to prevent prior-year balances from carrying into the current reporting period. Consistent fiscal discipline is essential to maintain accurate financial statements and prevent reporting distortion.
2.7 Bank Deposit & Undeposited Funds Workflow
Workflow
• Payments (e.g., checks) recorded to Undeposited Funds • Bank Deposit module transfers funds to bank account • Deposit reconciled against bank statement
Control Logic
• Undeposited Funds acts as clearing account • Multiple payments can be combined into one deposit slip • Reconciliation accuracy depends on correct bank selection
2.8 Cash Basis vs Accrual Basis Accounting
Cash Basis
• Revenue/expense recognized when cash moves
Accrual Basis
• Revenue recognized when obligation fulfilled • Expense recognized when goods/services received
Example
• Inventory received → AP created • Vendor paid later
Governance Rule
• Accrual reflects financial performance • Cash reflects liquidity movement • Xoro recognizes revenue upon shipment
2.9 Accounts Associated with Items, Customers & Vendors
Item-Level Accounts
• Income Account • COGS Account • Inventory Asset Account
Customer-Level Accounts
• Accounts Receivable • Customer Deposit
Vendor-Level Accounts
• Accounts Payable • Vendor Prepayment • Expense Account
Governance Rule
• Correct account linkage ensures automation • Misconfigured item accounts distort margin reporting
2.10 Account Register (Ledger View)
Functionality
• Detailed ledger for specific GL account • Displays debits, credits, references • Exportable for audit
Usage
• Essential for audit validation • Quick trace via reference number • Verifies transaction-level detail
2.11 Audit Trail & Deleted Transactions
Audit Trail
• Complete transaction log
Deleted Transactions Module
Displays: • Deleted record • Impacted accounts • Reference number
Governance Rule
• Critical for troubleshooting • Identifies financial impact of mistaken deletions
2.12 Sales Tax Workflow & Tax Return Center
Structure
• Tax Collected (Sales) • Input Tax Credit (Purchases) • Net Tax Liability = Tax Collected – Tax Paid
Filing Behavior
• “File Tax” does not submit to government • Filing creates entry in Tax Return Center • Payment must be recorded manually • Payment appears in bank reconciliation
Governance Rule
• Filing in system ≠ Government filing • Correct bank selection critical • Net liability must reconcile
2.13 Payment Account Behavior & Reconciliation Rules
High-Risk Area
• Wrong bank selection causes reconciliation confusion
Account Modification Rules
May change account (if not reconciled): • Vendor Prepayment • Customer Deposit • Sales Tax Payment
Cannot change account: • Invoice Payment • Bill Payment
Governance Rule
• Always verify payment account before saving • Reconciled transactions cannot be modified
2.14 Project Class & Business Channel Reporting
Purpose
• Used for channel-wise reporting (Shopify, Amazon, Storefront, etc.) • Income Statement by Class splits P&L by revenue stream
Project Status
• Not Started • In Progress • Completed
Reporting Impact
• Active projects must be marked “In Progress” • Incorrect status may affect P&L visibility
Governance Rule
• P&L by Class preferred for margin analysis • Projects enable strategic cost center tracking
3. Critical Learnings & Special Cases
• AR/AP via JE requires Customer/Vendor + Store • Customer Deposit & Vendor Prepayment cannot be selected directly in JE • Fiscal year must be closed to prevent P&L carryover • Wrong bank selection causes reconciliation confusion • Invoice/Bill payments cannot change bank account after saving • Filing tax in Xoro does not file with government • Undeposited Funds must precede Bank Deposit • Reversing entry auto-creates future opposite JE • Project must be marked “In Progress” for correct reporting visibility
4. Frequently Asked Questions
Q1. Can I create a JE directly on Customer Deposit? A: No. It cannot be selected directly in General Entry.
Q2. Why is my tax payment not appearing in reconciliation? A: Likely the wrong bank account was selected during payment recording.
Q3. Can I change the payment account after recording? A: Only if the transaction is not reconciled and the module allows modification.
Q4. What happens if I don’t close fiscal year? A: Previous year P&L carries forward and inflates revenue.
Q5. Why do we use Undeposited Funds? A: To consolidate multiple checks into a single bank deposit.
Q6. Does clicking “File Tax” submit to government? A: No. It records filing inside Xoro only.
Q7. What’s the difference between accrual and cash? A: Accrual = when obligation fulfilled. Cash = when money moves.
Q8. What’s the purpose of Project Class? A: To analyze profitability by business channel.
Q9. Why must we select store in AR/AP JE? A: To ensure correct system linkage and transaction behavior.
Q10. When should adjusting entries be made? A: Before closing the accounting period.
Q11. A client recorded a tax payment but cannot see it during bank reconciliation. What is the first thing to check? A: Verify the selected payment account.
Q12. A JE is created using Accounts Receivable. What additional selections are mandatory? A: Customer and Store.
Q13. Inventory is received today but vendor will be paid in 60 days. When is expense recognized under accrual? A: When goods are received.
Q14. A user deletes a credit memo. Where should impact be reviewed? A: Deleted Transactions / Audit Trail module.
Q15. Multiple checks received today. How should they be deposited together? A: Record to Undeposited Funds, then use Bank Deposit module.
Q16. Can you change the bank account on a saved invoice payment? A: No.
Q17. What does Net Tax Liability equal? A: Tax Collected – Input Tax Credit.
Q18. When should a reversing entry be used? A: When a temporary entry requires automatic reversal in a future period.
5. Conclusion
Accurate financial operations depend on disciplined payment behavior, correct journal logic, strict fiscal period management, controlled tax recording, and structured reconciliation workflows.
By understanding invoice vs bill payment behavior, AR/AP journal restrictions, deposit sequencing, tax filing mechanics, and project-based reporting controls, organizations maintain clean ledgers, accurate P&L reporting, and stable bank reconciliation outcomes within XoroERP.
Last updated
Was this helpful?