This option takes the user into more detail in terms of posting information, where the transaction was sourced, having already displayed the search results within Transaction Enquiry , and then clicking the Detail button.
BUTTONS:
Close: Returns you to the Search Results grid within Transaction Enquiry .
OK: Displays the Selection criteria form for the selected transaction file.
Help: Accesses online help.
Daybook: Daybook information in terms of date created, type of daybook , information that could potentially be used in an audit. By clicking the button, you are taken to Transaction Enquiry-Daybook detail
FIELDS
KEY
Daybook number: The daybook that these transactions was processed on.
Item number The item within the daybook - a daybook can contain a number of items , and these can be controlled from NL System Parameters. An example would be daybook number 1000, with items 1-10.
Sequence: The sequence within the item, in other words the line transactions that make up the item. For example Daybook 1000, Item 3, Sequence 2.
Transfer batch: For use with BACS transfers.
ACCOUNT
Cost Centre: The cost centre [or department code] that the specific transaction was posted to.
Expense code: The charge code that the specific transaction was posted to.
Suffix: Some account codes have a suffix attached as well, for further detail and reconciliation purposes.
VAT Code: The VAT code that the specific transaction was posted to.
GENERAL
Reference: This is populated if a reference was entered at the time from the source module [for example Sales Ledger/Purchase Ledger]
SL/PL account: The account that was used in the source module as above.
Narrative: In some areas of Autoline, the narrative is generated automatically, for example B/fwd, but in some areas the user can enter it manually, or not at all if they choose.
Source module and company: The source module is where the transactions originally were input or generated, for example SO module. The company is the specific company that the module relates to.
Customer reference: This is similar to Narrative/Reference as it is sometimes entered automatically by Autoline and sometimes it is up to the user to enter the reference if wish. As with all references, it is there for users to enter if needs be, to add as much information to the transaction as possible.
Journal class: The class relates to the area of Autoline that the transaction originated from. An example is BK which relates to bank journals.
Journal type: The next level of detail- if the journal class was PI for Purchase invoices, SB [as a journal type] relates to Self-Billing invoices.
Accounts company: The company that the source company relates to from an accounting point of view, for example SO company 02 uses accounts company 00.
Journal seq type: Some cultures require a sequence within their journal classes and types- it allows further detailed breakdown and control in effect.
Document number: The document number that is assigned to the transaction.
POSTING
Posting date: The date that the transaction has been posted - either selected by the user or by Autoline.
Period/Year: When a daybook is created at the time of processing, a period and year is assigned to it, driven by the posting date.
Reconciled: Some transactions are reconciled [such as bank type transactions] and therefore are given a status of R to indicate that they have been reconciled.
Reconciled time/ref/by: This is the time and reference that is "stamped" on the transaction if it has been reconciled, and which user reconciled it.
Base value: The value of the transaction in the user's base currency, for example Pounds sterling in a UKL system.
Currency value: The foreign currency equivalent, if used. In a single currency account, the base and the currency will be the same.
Statement date: The date that is entered in the header when performing a Bank Reconciliation.
Reconciled date: If reconciled, the date the transaction was reconciled.
