> 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/erp-financial-control-systems-payment-logic-fiscal-governance-and-reporting-integrity.md).
# 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
{% hint style="info" %}
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.
{% endhint %}
***
#### 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, and 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 the tax in Xoro does not file with the 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
**Can I create a Journal Entry directly using the Customer Deposit account in XoroERP?**\
\
No. The **Customer Deposit account cannot be selected directly when creating a Journal Entry** in XoroERP. Customer deposits should be recorded through the **Customer Deposit workflow or payment-related modules**, which automatically generate the correct accounting entries.
***
**Why is my tax payment not appearing during Bank Reconciliation in XoroERP?**\
\
This usually happens when the **wrong bank account was selected while recording the tax payment**. During **Bank Reconciliation**, XoroERP only displays transactions recorded against the selected bank account. Verify the **payment account used when the tax payment was recorded**.
***
**Can I change the payment account after recording a payment in XoroERP?**\
\
The payment account can only be changed **if the transaction has not been reconciled and the module allows editing**. Once the transaction is **reconciled or locked**, the payment account cannot be modified.
***
**What happens if the fiscal year is not closed in XoroERP?**\
\
If the fiscal year is not closed, the **previous year’s Profit and Loss balances may carry forward into the new fiscal year**, which can result in inaccurate financial reporting by inflating revenue or expense values.
***
* **Why does XoroERP use the Undeposited Funds account?**\
\
The **Undeposited Funds account** is used to temporarily hold payments such as checks or cash before they are deposited into the bank. This allows multiple payments recorded in **Accounts Receivable** to be grouped into a **single deposit using the Bank Deposit module**, matching the actual bank deposit made at the bank.
***
* **Does clicking “File Tax” in XoroERP submit the tax return to the government?**\
\
No. The **File Tax action only records the filing activity within XoroERP** for accounting and tracking purposes. The actual tax return must still be **submitted to the government through the appropriate tax portal**.
***
* **What is the difference between Accrual Accounting and Cash Accounting in XoroERP?**
* **Accrual Accounting:** Transactions are recorded when the **transaction occurs or the obligation is fulfilled**, regardless of when payment is made.
* **Cash Accounting:** Transactions are recorded **only when cash is received or paid**.
***
* **What is the purpose of Project Class in XoroERP?**\
\
The **Project Class** field allows businesses to categorize transactions by **project, department, or business channel**, making it easier to analyze **profitability, revenue, and costs across different segments of the business**.
***
* **Why must a Store be selected when creating an AR or AP Journal Entry in XoroERP?**\
\
In XoroERP, **Accounts Receivable and Accounts Payable transactions must be linked to a Store** to maintain the proper connection between **financial transactions, inventory locations, and operational data**.
***
* **When should adjusting entries be recorded in XoroERP?**\
\
Adjusting entries should be created **before closing the accounting period or fiscal year** to ensure that revenues, expenses, and account balances are accurately reflected in financial reports.
***
* **A tax payment was recorded but does not appear during Bank Reconciliation. What should I check first?**\
\
The first step is to verify the **bank account selected when the tax payment was recorded**. If the payment was recorded against a different bank account, it will **not appear during reconciliation for the selected account**.
***
* **When creating a Journal Entry using Accounts Receivable in XoroERP, what additional fields are required?**\
\
When **Accounts Receivable** is used in a Journal Entry, the system requires the following fields to be selected:
* **Customer**
* **Store**
These fields ensure the entry is properly linked to the **customer account and operational store context**.
***
* **Inventory is received today but the vendor will be paid later. When is the expense recognized under accrual accounting?**\
**Answer:**\
Under **accrual accounting**, the expense is recognized **when the goods are received or the liability is incurred and IR is created**, not when the payment is made.
***
* **If a credit memo is deleted in XoroERP, where can the change be reviewed?**\
\
The impact of the deletion can be reviewed in the **Deleted Transactions or Audit Trail module**, which tracks system activity and changes made to financial records.
***
* **Multiple checks were received on the same day. How should they be deposited together in XoroERP?**\
\
Record each payment to the **Undeposited Funds account**, then use the **Bank Deposit module** to combine them into a **single bank deposit transaction**, matching the deposit recorded by the bank.
***
* **Can the bank account be changed after saving an invoice payment in XoroERP?**\
\
No. Once an **invoice payment has been saved**, the associated bank account **cannot be changed**.
***
* **How is Net Tax Liability calculated in XoroERP?**\
\
Net Tax Liability is calculated as:
**Net Tax Liability = Tax Collected – Input Tax Credit**
This represents the **amount payable to the tax authority after applying eligible tax credits**.
***
* **When should a reversing entry be used in XoroERP?**\
\
A reversing entry should be used when a **temporary adjusting entry needs to be automatically reversed in the next accounting period**, such as accruals or estimated expenses recorded at the end of a reporting 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.
---
# 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/erp-financial-control-systems-payment-logic-fiscal-governance-and-reporting-integrity.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.