> For the complete documentation index, see [llms.txt](https://voyzu.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://voyzu.gitbook.io/docs/guide/definitions.md). # Definitions Definitions provided as a general guide. **Organization** A group of companies. A Voyzu instance has only a single Organization **Company** A bounded set of financial records. A company could be a registered company, a charitable organization, a partnership, and individual or a division within a company. **Company Ledger** Synonymous with General Ledger. The full set of financial entries for a Company and thus the source of financial truth for a company. **Company Ledger Entry** An individual entry (record) in the Company Ledger. Also known as a Journal Entry **Posting** A verb. The activity of calculating and entering an entry into the Company Ledger **General Ledger Account** An individual "bucket" representing a financial total. Sometimes shortened to "GL Account" or simply "Account". Sometimes informally known as a General Ledger Code, or GL Code **Account Type** The highest level Accounting classification of a General Ledger Account. One of Asset, Liability, Equity, Revenue or Expense **Dimension** Data that can be attached to a Company Ledger Posting, used for Financial Analysis **Supporting Ledger** A record of the financial transactions that stand behind a particular General Ledger Account balance **Subledger** An Accounts Receivable or Accounts Payable Supporting Ledger **Control Account** A Control Account is a pointer to a General Ledger Account that represents a Subledger Total. **Tax Account** A Voyzu specific term. A pointer to a General Ledger Account that represents a taxation balance **Tax Movement Code** Tax Movement Codes classify tax-related postings so the system can track and report changes in a company’s tax position. **Bank / Cash Account** A Voyzu specific term. A pointer to a General Ledger Account that represents a company Bank Account or Cash Account **Financial Document** A document representing a financial event, for example a company invoice, a supplier bill and so on. Technically Financial Documents are supplied to Voyzu as JSON objects **Financial Document Type** The system classification of the Financial Document, for example `AR_INVOICE`, `AP_BILL` etc. You can see the full list of Financial Documents supported by Voyzu [here](/docs/financial-document-processing/concepts.md) **Financial Document Posting Engine** The logic that validates the Financial Document supplied to the system, posts to the Company Ledger and the relevant supporting ledgers. There is a one to one relationship between Financial Document Types and Financial Document Posting Engines - the `AR_INVOICE` Document Type is posted by the `AR_INVOICE` Posting Engine etc. Sometimes referred to simply as "Posting Engine". **Financial Document Posting Code** POSSIBLE RENAME Maybe "Integration code" A Voyzu Specific term. A stable alias to a General Ledger Account, used by a Posting Engine. Sometimes shortened to "Document Posting Code" or just "Posting Code" **Posting Code** An alias to a GL Account. The Voyzu system defines different types of posting codes, some are defined at a system level and some are user-editable. **Posting Code Type** This replaces Posting Route I think **Posting Route** The alias used by the posting engine to derive the General Ledger Account. For example the `AR_INVOICE` Financial Document Posting Engine will use the `AR_TRADE_RECEIVABLES` Control Account for the Debit side of the Company Ledger posting, and the configured `revenue_posting_code` Financial Document Posting Code for the Credit side **Posting Route Type** The classification of the Posting Route alias. Using the above example the Debit side of the `AR_INVOICE` Company Ledger posting utilizes a Control Account, and the Credit side utilises a Document Posting Code. Posting Routes and Posting Route Types are advanced concepts that help in overall system visibility. --- # 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://voyzu.gitbook.io/docs/guide/definitions.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.