1. Presented by: Andy Vitullo Principle, Logan Consulting
QAD Enterprise Edition: General Ledger Features, Functions & Transactions
Presented by: Andy Vitullo
Principle, Logan Consulting

2. Session Focus
This session will focus on key configuration requirements that support efficient closing cycles, USGAAP and IFRS transactions, and operational reporting for product line and market results. Configuration settings will focus on GL Accounts, Daybooks, GL Layers and SAFS. Reporting will focus on the configuration of master data and its impact on transactions.

3. About Logan Consulting
Founders: Former Andersen, E&Y, PWC (Optimized Project Methodology)
Project Consultants: Blend of operational & consulting experience
Strategic Alliance Partner with QAD since 1993
160+ Successful QAD Implementations
40+ Dedicated QAD Consultants
Average tenure is 10 years
Headquartered in Chicago

4. Logan Background History Core Services: Core Strengths:
Lean, hard-working consulting firm
Midwest focus with international reach
Longest standing QAD consulting partner (since 1993)
Core Services:
Strategic IT Planning
Technology Assessment, Selection & Negotiation
Program & Project Management
ERP-Specific Business Process Design and Development
ERP Implementation
Extensive Experience with QAD’s MFG/PRO including latest version eB2.1
Core Strengths:
People
Methodology
Tools
References

5. Andy Vitullo 30+ Years of Accounting Experience
20+ Years of Manufacturing Accounting
20+ Years of QAD Experience
19+ Years with Logan Consulting
10+ Years of EE Experience.

6. Your Financial Reporting Requirements
Who are Your Customers?
Internal
External
Corporate Parent
What Financial Reports are produced after Month End Closing is completed?
Balance Sheet, Profit & Loss Statement, Cash Flow?

7. Profit and Loss Reporting
Year over Year?
Month Over Month?
Product Line P&Ls?
Customer Market P&Ls?
What are your Key financial business drivers?

8. The EE Account String

9. GL Layer
DEFINITION:
Accounting layers provide different ways of segregating transactions within a single GL account. The posting of transactions is controlled by associating daybook types.

10. GL Layers

11. Layer Example Entity Yr/Pd Daybook Primary GAAP Acct Sub-Account
Cost Center
Project
SAF’s
SAF’s
SAF’s
SAF’s
SAF’s
Layer - Primary
$100
$192
Layer - Transient
Layer - Addback
$10
Layer - IFRS
$-25

12. Daybooks
Definition:
Daybooks, also known as journals, are system or user-defined views of the general ledger and contain all transactions.
The use of daybooks is mandatory in all modules. Daybooks provide many advantages in terms of analysis, segregation of transactions, numbering, and consequently, speed of period close.

13. Setting Up Daybooks Code appears in General Ledger Transactions
Document Number Segment for customer (Supplier) Invoices
Defines Layer to which the GL transactions will be posted.
Customer Invoice Number Example : I / 2017 /
Daybook / Transaction Year / Voucher Number

14. Operational Daybooks
Operational Daybooks are assigned by the type of transaction create in Sales, Manufacturing and Purchasing Modules.
Analogous to Inventory Transaction Types
Example: Transaction Type of ISS-SO = Daybook Code of ISS-SO.

15. Operational Daybooks

16. Daybooks in Transactions
CIM – CUSTOMER INVOICE CREATE
CINV – INVOICE POST

17. Intercompany Transactions
Used for Arms-Length Transactions between Affiliated trading partners.
Supports Elimination Accounting in Consolidation Domain.
Defined in the Business Relation assigned to the Trading Partner.
Available for Operational Transactions and Financial Transactions

18. Intercompany Setup Requirements
Business Relation
General Ledger Account
Customer Control Account
Supplier Control Account
Profiles
Customer/Supplier

19. Intercompany Setup Business Relation
The Intercompany code value is used in the arms length transactions for balance sheet accounts.
This code appear in the debit transactions to the customer control account when an invoice is posted.

20. Intercompany Setup – General Ledger Account
Fixed Intercompany.
Select this field if you do not want the default intercompany code to be changed during manual entry.

21. GL Transactions with IC Code

22. Configuration Recommendation
If Possible –
Set all the following codes to the same Code Value:
Entity
Site
Customer
Supplier
Business Relation
Company Address
Identifies Affiliate Trading Partners in unique range of supplier and customer views.
Simpler Configuration for Users
Simpler Configuration for eCommerce Configuration(EMT/Trade Sales)

23. Analysis Segments for the GL Account
The system provides sub-account, cost center, project, and SAF analysis to be used for additional analytical reporting on transactions.
General Ledger-wise, Analysis is a further breakdown of a general ledger account. It segregates the general ledger account into smaller activity or balance amounts.

24. General Ledger Analysis Segments
Sub Account
Cost Center
Project
Intercompany Code
Layer
Daybook
Entity

25. SE Approach to Analysis Segments
Sales Account Maintenance
Used to deliver the Sales Account String to the Invoice Post and Shipment Transactions
Intersected Site, Product Line, Customer Type and Channel.

26. SE Sales Accounting
To Achieve product line and customer type segments in the GL for Sales, Sales account maintenance was necessary for the configuration.
Intercompany Sales GL Account are defined using the Intercompany customer type.

27. EE Sales Accounting Config
System Supplementary Analysis Field Replace the requirement to uses sales account maintenance.
System SAFs include:
Site
Product Line
Item Type
Item Group
Customer Type
Customer Region
Supplier Type

28. SAF Configuration
Using System SAFs, Create SAF Structures for types of Transactions.
Sales
Manufacturing
Purchasing
Inventory
Assign the SAF structure to the GL Account

29. SAF Structures
Default SAF Values are used when the transaction cannot find the Master Data.

30. SAF Assignment to GL Account
Accounts can have SAF analysis or Cost Center.

31. SAF Business Value
Enables the Collection of General Ledger Data by the SAF Segments supporting:
Site P&Ls
Product Line P&Ls
Customer Type P&Ls
Reduces the number of natural accounts required in the Chart of Accounts.
Single Sales Account – Trade Sales vs Intercompany sales defined by the customer type.
Single Inventory Account - Raw, WIP and FG defined by Item Type.

32. Tools
Chart of Accounts Design Workbook

33. Financial Report Writer (FRW)
Analogous to GLRW in SE
Report Analysis Codes
Report Tree ( SE Row Group) with Excel Integration.
Build Analysis Codes and Rows with Report Tree Import.
Column Group

34. FRW Control Report Output with Analysis Code Filter.
Common Report Across Domains
Report Analysis Code Filter for Entity or Group of Entity

35. Filter Analysis Code

36. Report Analysis Code
Multi-Dimensional Across Account Code Transactional Segments/Analysis Fields

37. Other Configuration Considerations
Domain
Entity
If Multi-Entity
Shared Services AP / AR?
Single Bank Account for All Entities?
AP/AR at the Operational Entity Level or SS?

38. Thank-You! Questions? Andy Vitullo avitullo@loganconsulting.com