انتقل إلى المحتوى الرئيسي

Voucher transactions

The Voucher transactions inquiry serves as the ultimate, immutable audit trail for the entire ERP ecosystem. Regardless of which subledger module (Accounts Payable, Accounts Receivable, Fixed Assets, etc.) originates a financial transaction, the final, posted result that impacts the general ledger is recorded and perpetually traceable here.

Filtering transactions​

Given the immense volume of granular data stored within the ledger, navigating to General ledger > Inquiries and reports > Voucher transactions will immediately invoke a Filter side pane. This allows you to efficiently isolate specific accounting entries:

  • Start date / End date: Restricts the inquiry to vouchers formally posted within a specific accounting period or date window.
  • Account: Allows you to filter for transactions hitting a specific ledger account structure (Main account + dimensions).
  • Journal number: Use this parameter to retrieve all the disparate vouchers that were posted collectively under a single journal batch.
  • Voucher number: The most granular filter, allowing you to instantly isolate the exact, balanced double-entry for a singular transaction.

After defining your criteria, click Apply to execute the query.

Analysing the voucher grid​

The resulting inquiry grid provides an exhaustive, column-dense breakdown of the selected transactions. The data is logically segmented into core identification and multi-currency financial valuations.

Core transaction details​

  • Date: The specific accounting date the transaction was recognized in the ledger.
  • Voucher: The unique, sequential identifier assigned to the balanced transaction.
  • Ledger account: The fully resolved Main account and Financial dimension combination (e.g., 1000-Admin-HQ).
  • Account name / Description: Descriptive metadata providing context for the account and the specific line entry.
  • Posting type: A critical, system-generated classification indicating the specific accounting operation that generated the line (e.g., Ledger journal, Customer balance, Cash discount, Sales tax). This is invaluable for tracing the systemic origin of an entry.

Multi-currency financial amounts​

To ensure rigorous compliance with international accounting standards (such as ASC 830 / IAS 21), the inquiry meticulously tracks monetary amounts across three distinct currency layers:

  1. Transaction currency: The original currency in which the business transaction actually occurred (e.g., an invoice received in EUR).
    • Columns: Debit, Credit, Currency, Amount in transaction currency.
  2. Accounting currency: The primary base currency of the legal entity's ledger (e.g., SYP). The system automatically calculates this base amount during posting using active exchange rates.
    • Columns: Accounting currency code, Amount in accounting currency.
  3. Reporting currency: An optional secondary base currency utilised for consolidated corporate reporting (e.g., USD).
    • Columns: Reporting currency code, Amount in reporting currency.

(Important Note: Voucher transactions represent finalised, immutable ledger history. You cannot directly edit these records; any required corrections must be executed via formal reversal procedures or subsequent adjusting journal entries).