Posting Engine PDF

Epicor ERP
Posting Engine Course

10.0.700.2
Disclaimer
This document is for informational purposes only and is subject to change without notice. This document and its
contents, including the viewpoints, dates and functional content expressed herein are believed to be accurate as of its
date of publication. However, Epicor Software Corporation makes no guarantee, representations or warranties with
regard to the enclosed information and specifically disclaims any applicable implied warranties, such as fitness for a
particular purpose, merchantability, satisfactory quality or reasonable skill and care. As each user of Epicor software is
likely to be unique in their requirements in the use of such software and their business processes, users of this document
are always advised to discuss the content of this document with their Epicor account manager. All information contained
herein is subject to change without notice and changes to this document since printing and other important information
about the software product are made or published in release notes, and you are urged to obtain the current release
notes for the software product. We welcome user comments and reserve the right to revise this publication and/or
make improvements or changes to the products or programs described in this publication at any time, without notice.
The usage of any Epicor software shall be pursuant to an Epicor end user license agreement and the performance of
any consulting services by Epicor personnel shall be pursuant to Epicor's standard services terms and conditions. Usage
of the solution(s) described in this document with other Epicor software or third party products may require the purchase
of licenses for such other products. Where any software is expressed to be compliant with local laws or requirements
in this document, such compliance is not a warranty and is based solely on Epicor's current understanding of such laws
and requirements. All laws and requirements are subject to varying interpretations as well as to change and accordingly
Epicor cannot guarantee that the software will be compliant and up to date with such changes. All statements of
platform and product compatibility in this document shall be considered individually in relation to the products referred
to in the relevant statement, i.e., where any Epicor software is stated to be compatible with one product and also
stated to be compatible with another product, it should not be interpreted that such Epicor software is compatible
with both of the products running at the same time on the same platform or environment. Additionally platform or
product compatibility may require the application of Epicor or third-party updates, patches and/or service packs and
Epicor has no responsibility for compatibility issues which may be caused by updates, patches and/or service packs
released by third parties after the date of publication of this document. Epicor® is a registered trademark and/or
trademark of Epicor Software Corporation in the United States, certain other countries and/or the EU. All other
trademarks mentioned are the property of their respective owners. Copyright © Epicor Software Corporation 2014.
All rights reserved. No part of this publication may be reproduced in any form without the prior written consent of
Epicor Software Corporation.
ED841905
90521-10-9273-58310702
10.0.700.2
Revision: July 25, 2014 2:37 a.m.
Total pages: 101
course.ditaval
Posting Engine Course Contents
Contents
Posting Engine Course............................................................................................................7
Before You Begin....................................................................................................................8
Audience.........................................................................................................................................................8
Prerequisites....................................................................................................................................................8
Environment Setup..........................................................................................................................................8
Workshop Constraints..............................................................................................................................9
Overview...............................................................................................................................10
Daily Posting Engine Processing..........................................................................................11
Posting Engine Modes....................................................................................................................................11
Posting Process Output Data..........................................................................................................................12
Business Transaction Documents....................................................................................................................12
Review Journal...............................................................................................................................................13
Posting Process Stages...................................................................................................................................15
Stage 1: Generate Business Transactions.................................................................................................16
Stage 2: Execute Posting Rules................................................................................................................17
Stage 3: Execute Automatic Procedures..................................................................................................18
Stage 4: Review Transactions..................................................................................................................19
Specialized Posting Engine Processing................................................................................21
GL Transaction Type Maintenance..................................................................................................................21
Revision Control.....................................................................................................................................22
Revisions.........................................................................................................................................22
Active Modes..................................................................................................................................24
Workshop - Add a Revision..............................................................................................................24
Manual Review.......................................................................................................................................25
Workshop - Review Transactions in the Review Journal....................................................................25
Activate Manual Posting...........................................................................................................25
Enter an AR Invoice..................................................................................................................25
Use the Review Journal.............................................................................................................26
Automatic Posting..................................................................................................................................27
Workshop - Use Automatic Posting.................................................................................................27
Activate Automatic Posting.......................................................................................................27
Use the Review Journal.............................................................................................................28
Incoming Document Templates...............................................................................................................28
Selection Criteria....................................................................................................................................29
Posting Codes.........................................................................................................................................29
Posting (Booking) Rules...........................................................................................................................29
Workshop - Copy and Delete Posting Rules.....................................................................................31
Copy a Posting Rule.................................................................................................................31
Delete a Posting Rule................................................................................................................31
Epicor ERP | 10.0.700.2 3

Contents Posting Engine Course
Operations......................................................................................................................................31
Workshop - Enter a Header Rule...............................................................................................32
Functions.........................................................................................................................................35
System Functions......................................................................................................................35
Workshop - Create a User-Defined Function.............................................................................36
Workshop - Add a Posting Rule.......................................................................................................42
Add a Posting Rule...................................................................................................................42
Add a Selection Criterion..........................................................................................................42
Define Reference GL Control Information.................................................................................42
Add a Book Amount Operation................................................................................................43
Add a Transaction Amount Operation......................................................................................44
Add a Debit Account Operation...............................................................................................45
Disable the Posting Rule...........................................................................................................46
Activate the Revision................................................................................................................46
Review the Result.....................................................................................................................47
GL Controls...................................................................................................................................................48
GL Control Type Maintenance................................................................................................................49
GL Control Maintenance.........................................................................................................................49
Workshop - Revise AR Invoice Posting Rules............................................................................................50
Review Current Posting Rule Details.................................................................................................50
Add a GL Control Type Context.......................................................................................................51
Review Company Default GL Controls.............................................................................................51
Assign an Account to a GL Control Context.....................................................................................52
Add a Revision.................................................................................................................................52
Update the Rule..............................................................................................................................53
Activate the Revision.......................................................................................................................53
Enter an AR Invoice.........................................................................................................................53
Review the Result............................................................................................................................54
Multiple Books...............................................................................................................................................55
Book Maintenance..................................................................................................................................56
Multiple Currencies.........................................................................................................................57
Rounding Differences......................................................................................................................57
Source Book....................................................................................................................................58
Validations......................................................................................................................................58
Detail......................................................................................................................................................59
Chart of Account Structure Maintenance.......................................................................................................59
Chart of Account Structure Maintenance - Program Features - Segments................................................60
Master Chart of Accounts.......................................................................................................................61
Workshop - Create a Chart of Accounts.................................................................................................62
Structure a Chart of Accounts.........................................................................................................62
Add COA Controlled Segments ......................................................................................................63
Add Chart Segment Values..............................................................................................................63
Add a Division Segment Value.........................................................................................................64
Enter GL Accounts...........................................................................................................................64
4 Epicor ERP | 10.0.700.2

Posting Engine Course Contents
Chart of Accounts Mapping...........................................................................................................................65

Workshop - Use Mapping.......................................................................................................................66
Add COA Mapping..........................................................................................................................66
Add GL Account Mapping...............................................................................................................67
Add a Book.....................................................................................................................................68
Link to Source Book with Mapping..................................................................................................68
Enable GL Transaction Configuration...............................................................................................68
Review the Active Revision...............................................................................................................69
Business Activity Queries in Posting Rules.......................................................................................................70
Workshop - Add a Query to a Posting Rule.............................................................................................70
Create the User-Defined Table.........................................................................................................71
Add Custom Columns.....................................................................................................................71
Synchronize Table............................................................................................................................72
Regenerate Data Model...................................................................................................................72
Add a Revision.................................................................................................................................73
Add a Query and Criteria Parameters...............................................................................................73
Add a Posting Entity........................................................................................................................74
Enter and Apply a Posting Code......................................................................................................74
Workshop - Use the Modified Posting Rule.............................................................................................75
Enter and Receive an RMA...............................................................................................................75
Enter an RMA Credit Memo............................................................................................................75
Post the RMA Credit Memo.............................................................................................................76
Review the Results...........................................................................................................................76
Lookup Tables Setup......................................................................................................................................77
Workshop - Use Lookup Tables...............................................................................................................78
Add a Chart of Accounts.................................................................................................................78
Add a COA Controlled Segment......................................................................................................78
Add COA Dynamic Segments..........................................................................................................79
Add Chart Segment Values..............................................................................................................79
Add Customer Group Segment Values............................................................................................80
Add Product Group Segment Values................................................................................................81
Enter GL Accounts...........................................................................................................................81
Add a GL Book................................................................................................................................82
Add Customer Groups.....................................................................................................................82
Add Product Groups........................................................................................................................82
Set Up Customers............................................................................................................................83
Add a Lookup Table........................................................................................................................83
Add Source Value Fields..................................................................................................................84
Add a Target Value Field..................................................................................................................84
Add Lookup Links............................................................................................................................85
Add a Revision.................................................................................................................................85
Add a Book to the Revision..............................................................................................................86
Epicor ERP | 10.0.700.2 5

Contents Posting Engine Course
Copy Posting Rules..........................................................................................................................86

Add a Posting Code ........................................................................................................................86
Add a Posting Rule..........................................................................................................................87
Add a Book Amount Operation.......................................................................................................87
Add a Transaction Amount Operation ............................................................................................88
Copy and Paste an If Logical Condition for the Credit Account........................................................88
Update the If Logical Operation for the Credit Account....................................................................88
Add an Else Logical Condition for the Debit Account.......................................................................89
Define the Else Logical Operation for the Debit Account..................................................................90
Disable a Posting Rule .....................................................................................................................91
Add AR Invoice Lines ......................................................................................................................91
Post an AR Invoice ..........................................................................................................................92
Posting Process Tracking......................................................................................................94
System Monitor.............................................................................................................................................94
Workshop - Use the System Monitor.......................................................................................................95
Error Handling...............................................................................................................................................95
Workshop - Handle a Lookup Table Posting Error....................................................................................96
Review Errors...................................................................................................................................96
Cancel a Journal Entry.....................................................................................................................96
View a Posting Rule.........................................................................................................................97
Enter a GL Control Context.............................................................................................................97
Post an AR Invoice...........................................................................................................................98
Conclusion.............................................................................................................................99
6 Epicor ERP | 10.0.700.2

Posting Engine Course Posting Engine Course
Posting Engine Course
This course provides an overview of the posting process concept for the Epicor application and the Posting Engine
as the technology to implement this process. In addition, the course discusses how the posting engine provides
flexibility and control over the financial transaction creation process in the Epicor application.
Upon successful completion of this course, you will be able to:
• Explain the unified posting process for all business transactions.
• Manage the flexible, rule-based posting mechanism.
• Demonstrate how user-defined business entities drive posting rules.
• Identify the automated handling of multiple books, currency conversions, and rounding differences.
Epicor ERP | 10.0.700.2 7

Before You Begin Posting Engine Course
Before You Begin
Read this topic for information you should know in order to successfully complete this course.
Audience
Specific audiences will benefit from this course.

• Consultants and partners implementing Epicor ERP or working with customers who are looking to change
their current (or converted) financial structure.
Prerequisites
To complete the workshops in this course, the necessary modules must be licensed and operating in your training
environment. For more information on the modules available, contact your Epicor Customer Account Manager
at EpicorCAM@epicor.com. It is also important you understand the prerequisite knowledge contained in other
valuable courses.
• Navigation Course - This course introduces navigational aspects of the Epicor application's user interface.
Designed for a hands-on environment, general navigation principles and techniques available in two user
interface modes - Classic Menu and Modern Shell Menu. Workshops focus on each of these modes and
guide you through each navigational principle introduced.
• General Ledger Course - This course provides a clear perspective of the maintenance programs, concepts,
processes, and reporting tools you encounter as you work within the General Ledger (GL) module.
• Industry Knowledge:
• A consultant or partner focused on the Epicor ERP posting engine should have the standard amount of
career experience required for any consultant, plus a background in accounting, specifically general ledger
structure and hierarchical flow. International accounting experience is also beneficial. Some experience
working on the technical side of a software package is helpful, because understanding the posting engine
requires knowledge of the posting rules written by the system administrators.
• At least one year experience working with the financial modules (prior versions) is beneficial but not a
requirement since the posting engine is a new functionality.
Environment Setup
The environment setup steps and potential workshop constraints must be reviewed in order to successfully
complete the workshops in this course.
Your Epicor training environment, in which the Epicor demonstration database is found, enables you to experience
Epicor functionality in action but does not affect data in your live, production environment.
The following steps must be taken to successfully complete the workshops in this course.
8 Epicor ERP | 10.0.700.2

Posting Engine Course Before You Begin
1. Verify the following or ask your system administrator to verify for you:
• Your Epicor training icon (or web address if you are using Epicor Web Access) points to your
Epicor training environment with the Epicor demonstration database installed. Do not complete
the course workshops in your live, production environment.
Note It is recommended that multiple Epicor demonstration databases are installed. Contact
Support or Systems Consulting for billable assistance.
• The Epicor demonstration database is at the same service pack and patch as the Epicor
application. Epicor's education team updates the Epicor demonstration database for each service pack
and patch. If your system administrator upgrades your Epicor application to a new service pack or patch,
he or she must also download the corresponding Epicor demonstration database from EPICweb > Support
> Epicor > Downloads and install it. If this is not performed, unexpected results can occur when completing
the course workshops.
• Your system administrator restored (refreshed) the Epicor demonstration database prior to
starting this course. The Epicor demonstration database comes standard with parts, customers, sales
orders, and so on, already defined. If the Epicor demonstration database is shared with multiple users
(that is, the database is located on a server and users access the same data, much like your live, production
environment) and is not periodically refreshed, unexpected results can occur. For example, if a course
workshop requires you to ship a sales order that came standard in the Epicor demonstration database,
but a different user already completed this workshop and the Epicor demonstration database was not
restored (refreshed), then you will not be able to ship the sales order. Epicor's education team has written
the course workshops to minimize situations like this from occurring, but Epicor cannot prevent users
from manipulating the data in your installation of the Epicor demonstration database.
2. Log in to the training environment using the credentials manager/manager. If you are logged into your
training environment as a different user, from the Options menu, select Change User.
3. From the Main menu, select the company Epicor Education (EPIC06).
4. From the Main menu, select the Main site.
Workshop Constraints
The workshops in this course can be performed only once in each instance of a restored (refreshed) database. If
a user has already completed these workshops in the database, the database must be restored (refreshed) before
another user can complete this course.
The posting process is a unified, multi-stage process that collects business transaction data and uses user-defined
rules to process the data. Because the posting process is the core financial functionality within the Epicor
application, only one person can perform the workshops in this course on a shared database.
Contact your system administrator to restore (refresh) the demonstration database before you complete the
workshops in this course.
Epicor ERP | 10.0.700.2 9

Overview Posting Engine Course
Overview
The posting process is a unified, multi-stage process that collects business transaction data and processes the
data using user-defined rules to create appropriate general ledger (GL) transactions. An event is a business
transaction if it should be recorded in the GL (for example - an invoice or a payment).
The posting process is the core financial functionality within the Epicor application. It first collects financial data
and then evaluates this information to create appropriate GL transactions. Depending on the current transactions
and your chart of accounts (COA) structure, transactions can post through one or multiple books to the general
ledger. The functionality which runs this process is the Posting Engine.
Posting engine functionality runs independently for each company within the Epicor application. A company can
also have multiple books defined for specific financial requirements, and each book can have a unique set of
posting rules which you define. These rules indicate how business transactions post to various accounts.
The posting process runs through a number of stages, pulling input data from a series of generated business
transaction documents. It then uses the posting rules created specifically for each book to post the results. The
Epicor application provides default GL transaction types that generate all business transaction documents which
then post to the general ledger; you can extend these GL transaction types to include more data or alternate
posting needs.
Your organization will have unique reasons for leveraging the posting engine. Some common uses for this
functionality include:
• If your company requires multiple books, such as one for taxing purposes and another for accounting purposes,
you can set up posting rules to reflect the different purposes of these books.
• If your organization works in a multi-company environment, you can set up unique posting rules for an
intermediate book which transforms the financial data into a format usable by the receiving company.
• If your company acquires another company, posting rules can be configured to grant the acquired company
the ability to maintain old books, fiscal calendars, and other data during the transition year.
• If your COA uses dynamic segments, you can directly assign dynamic segments to a GL control or use another
posting rule combination. Typically, you will not assign a dynamic segment value in a GL control, so you can
modify a posting rule instead.
• If you customize the Epicor application, you can use the posting engine to handle the automatic posting needs
of the custom programs.
10 Epicor ERP | 10.0.700.2

Posting Engine Course Daily Posting Engine Processing
Daily Posting Engine Processing
The posting process is defined by either mapping tables or posting rules. You can modify both to suit your
business needs.
Create user-defined mapping tables to map the chart of accounts (COA) from one book to another book. Use
COA mapping to create GL transactions in two books at the same time. COA map creation can handle most of
your posting process modification needs. Maps copy the posting hierarchy from one COA to another, so less
modification is required to achieve the desired posting results.
Posting rules are a sequence of instructions (algorithms) which define how an input business transaction is
processed into a GL transaction for a specific book. Posting rule modification is used less often than COA mapping.
Modify posting rules for specific needs, such as posting to a different journal context than the default journal
context.
The Epicor application uses the posting rules originally defined for the 8.03 application. Because of this, 8.03
users can upgrade with no posting rule changes. These standard posting rules (sometimes called booking rules)
ensure that a base set of rules is initially available within each company.
A set of extended posting rules is available for first time installations. This set contains a more open series of
rules which do not contain department and division hierarchies. This provides a flexible framework to reflect the
posting needs of your organization.
Posting Engine Modes
The posting engine process operates in multiple modes.

• Pre-Post Mode - Use this mode when some accounts must be calculated before actual posting occurs. This
mode calculates and outputs data used during the posting process. Pre-posting rules pull in the data required
for the GL transaction type.
• Validation Mode - Use this mode to debug posting rule modifications. This mode generates entries for the
Review Journal so that you can preview GL transactions generated in books when you post source documents.
The transactions are not yet posted to the general ledger. You can then print edit lists and use the Review
Journal to view the results. If you are satisfied with the results in the Review Journal, you can post them from
within this program out to the general ledger.
• Open Invoice Mode - Run this mode when you use Open Invoice Load in either Accounts Payable or Accounts
Receivable. This mode populates reference GL controls without creating GL transactions. You use Open Invoice
Load when you are first pulling in financial data from another application. After you post invoices, you can
use these reference GL controls with your current financial data.
• Regular Posting Mode - This mode posts a source document to create a GL transaction. The posting engine
process uses this mode when a source document posts from an entry program. When the posting process is
complete, the source document is marked as posted. This mode can output calculated accounts for just GL
transactions or both GL transactions and GL controls.
Epicor ERP | 10.0.700.2 11

Daily Posting Engine Processing Posting Engine Course
Posting Process Output Data
The posting process creates GL transactions and calculated accounts; these transactions and accounts are used
in subsequent processing.
Source documents outside the general ledger store the calculated accounts. You can then use a single source
document to associate a number of successive transactions.
Example You create an invoice payment where the payment transaction affects the same AR account
calculated in the previous invoice transaction. Another example is when you use a pre-posting rule, which
the posting process uses to calculate a default account overridden before the source document posts to
GL. In the 8.03 application, AP invoice accounts used this method to calculate defaults.
The posting process can output the following:

• GL transactions
• A number of calculated accounts
• GL transactions and a number of calculated accounts
This process outputs single or multiple calculated accounts and returns them as GL controls. A GL control is a
structure designed to store a set of accounts and journal codes available to a specific record during the posting
process. Within each GL control you define all the account contexts used when posting. GL controls are discussed
in more detail later in this course.
Business Transaction Documents
The primary components which control the posting engine process are business transaction documents. Each
business transaction document gathers the data input the posting engine process requires.
The application contains a series of GL transaction types which it uses as default templates for generating business
transaction documents. You can modify these transaction types when necessary within GL.
GL Transaction Type Maintenance

Each generated business transaction type has a hierarchical structure which contains the following:
• Parent document level
• Unlimited child document levels
• Posting codes
• Amounts
• Posting rules
During posting, operational data in the child document levels create GL transactions for a business event. Each
business event belongs to a specific business event type. The Epicor application supports several business event
types, such as inventory issues and payments. Because of this, Invoice Payment is an event type, while a specific
payment by check number XXX for invoice number YYY is considered a single business event.
Each business event type determines its content; however, the content structure remains the same among all
business transaction documents. This consistency ensures you have standard methods to access document data.
12 Epicor ERP | 10.0.700.2

Each document is populated with the data for a specific business event. At each child document level, business
data is grouped into amount collections and posting codes:
• Amount Collections - These values are a collection of named amounts available at a specific level of the
transaction type hierarchy. For example, an AR Invoice transaction type contains an Extended Price and a
Discount Amount which are available at the Invoice Line child level.
• Posting Codes - Posting codes contain a series of business entities. Each business entity defines a specific
set of chart of account segments. Use entities to create dynamic segments that reference customer, supplier,
part, or other application business entities. For example, the Part business entity can contain a group of fields
from the Part table; these fields are useful when the application creates a GL transaction for the given business
event.
A business entity is not necessarily associated with a specific database table. It may exist only to group several
logically related segments.
The structure of each business transaction document is unique. Each has a different number of child document
levels, and posting codes and amounts are also unique at each level. This document structure enables each
document to correctly reflect the business event. The standardized structure also provides a common way for
posting rules (sometimes called booking rules) to access data.
By default, the posting rules are based on the 8.03 version of the Epicor application. You can modify the transaction
type which generates the document to define posting rules that use additional data. To do this, add new elements
and then add rules to populate those new elements to extend the transaction type templates.
You can create three types of rules:
1. Pre-Posting Rules - These rules populate fields in a lookup table. The posting rules can then use the data
in these fields.
2. Function Rules - These rules populate data in the required fields during the posting process.
3. Posting Rules - These rules cause data to post to the general ledger. Posting rules consist of Header and
Line rules. A Header rule has no journal details, but it sets up data for its child line details. The Line rule
actually posts the data to the general ledger during the posting process.
By modifying the transaction types within GL Transaction Type Maintenance, you can customize the posting
process to generate business transaction documents which reflect the needs of a specific book or a specific chart
of accounts.
Review Journal
Use the Review Journal to adjust, re-validate, cancel, and post accounting transactions. Typically, you use the
Review Journal to locate posting errors and debug custom posting rules.
You can use the Journal Entry Asynchronous Confirmation command to re-post a group of adjusted journals.
Each confirmation is executed independently as processing time becomes available. Using this command improves
performance as you do not have to wait until one journal is processed before requesting another confirmation;
you can schedule all journals to run and then continue other work. Use the Journal Entry Asynchronous
Cancellation command to cancel a list of selected journals.
Main Goals of the Review Journal

The Review Journal does the following:
• Logs invalid journal transactions even if the posting rules are not set up to manually review transactions.
Epicor ERP | 10.0.700.2 13

While you display the Review Journal, you can sort error transactions by module, date, and user. For transactions
within the Epicor application, use the Review Journal's error log to adjust source transactions.
• Displays transactions that generate when debugging a custom posting process.
Typically, developers review all transactions updates create. Their review ensures process changes produce
the desired results.
• Adjusts an entry's line account numbers.
Following the adjustments, you can re-validate and post the journal from this program. You typically adjust
and post review journals when invalid journals originate from an external system.
• Prints edit lists to review posting results.
Generate lists for source transactions when they originate within the application. The ability to print lists from
this program supports this functionality for transactions that originate in external systems.
• Cancels or confirms entries.
Both actions remove the journal entries from the program. Confirmation updates the accounting transactions
in the books to which they post. If the updated transactions are invalid, the Review Journal again displays the
entries with their posting errors.
Review Journal Data Display

The Review Journal segregates the display of journal entries by book for the following reasons:
• Posting a single accounting transaction can create different journal details in multiple books. A single journal
entry groups all the journals posted to all the books by a single accounting transaction.
Example An Accounts Receivable invoice can post a journal with one set of details to the corporation's
financial book and another journal with different lines to the company's legal book. Journal entries that
display in the Review Journal group these accounting transactions.
• Book validation settings determine the errors and warnings the application logs. Book-specific validation
means the same transaction can produce different results when it posts to different books.
Example A transaction that generates an error can be ignored or treated as a warning. The validation
settings of a book do not influence the validation settings in other books. You can set up validation
rules to ignore this transaction in Book 1 while the same transaction type can be set up to generate a
warning in Book 2.
• If multiple books use different base currencies, each transaction amount displays in each book at the correct
currency value.
Summarization
Summarization settings that apply to accounting transactions also affect available adjustments in this program.
Journal summarization, applied to natural accounts and accounting processes, results in the posting of summary
lines for transactions. The Review Journal displays source details for each summarized line but limits the adjustments
to maintain the referential integrity of the summarized lines.
• Dates and accounts are shared between source details and can be adjusted on the summarized line level.
• Amount, debit/credit flag, and references (specific to each source detail) can be adjusted on the source line
level.
14 Epicor ERP | 10.0.700.2

Menu Path
Navigate to this program from the Main Menu:
• Financial Management > General Ledger > General Operations > Review Journal
Posting Process Stages
The posting engine runs its process through a series of stages. Each stage builds on the data generated during
the previous stage.
The following lists the posting process stages:
• Stage 1: Business transactions generate.
• Stage 2: Default and modified posting rules execute. This two-part stage first runs posting rules and then
runs mapped GL transactions.
• Stage 3: Automatic procedures execute.
• Stage 4: This is an optional stage to review the posting process results. Typically, you perform this stage when
you debug custom rules or when posting errors occur.
Epicor ERP | 10.0.700.2 15

Stage 1: Generate Business Transactions
The posting process begins when the Epicor application creates a business transaction for a specific business
event.
A business event type is first detected and then a business transaction template (GL transaction type) loads for
this event type. The loading process first uses the default structure of the posting rules and then extends to any
user-defined elements you may have created.
Next, the template populates with the business event data. It becomes a business transaction document to be
processed during the subsequent posting process stages.
The following image displays the business transaction generation process flow:
16 Epicor ERP | 10.0.700.2

Stage 2: Execute Posting Rules
During this stage, the business transaction document is used to generate GL transactions in the available company
books. GL transactions are generated through two methods.
The first method (Stage 2a) applies posting rules to the incoming business transaction document which directly
defines posting rules for each book separately so that each book can have its own rule set for every business
event type. Each rule constructs a single GL transaction detail or a pair of transaction details which balance each
other, creating an entire GL transaction. When this stage is complete, the GL transactions for the source business
transaction are created in all books which have posting rules that handle the specific business transactions.
The following image displays the process flow for the first stage (Stage 2a) of posting rules execution:
The second method (Stage 2b) maps GL transactions the posting rules generate from one source book to one
or more target books. When a GL transaction is created for a source book, it can also be mapped to other target
books. An optional step is to map a source book to target books when you can reuse the same set of posting
rules to construct GL transactions in other books.
Note GL transactions are not validated (verified) during this stage. They can be unbalanced, may contain
invalid accounting segments, or contain invalid segment combinations in the account.
The following image displays the process flow for the second stage (Stage 2b) of posting rules execution:
Epicor ERP | 10.0.700.2 17

Stage 3: Execute Automatic Procedures
During this stage, several procedures are applied to unverified transactions in all affected books. These procedures
review and validate, or verify, the transactions generated in Stage 2.
When Stage 3 is complete, the GL transactions either update the book journals and account balances or post to
the Review Journal, where you can adjust, validate, confirm, or cancel transactions.
The following image displays the process flow for automatic procedure execution:
The procedures run in the following order:

1. Balance Validation - This verifies the transaction total debit equals total credit. If the process cannot complete
the balance validation, the Posting Engine raises a logic error.
2. Account Validation - This verifies all accounts are valid. This process is a complex review that includes verifying
an account exists and is active, the account segment combination is valid, and all mandatory segments are
specified. If an account is invalid, the Posting Engine raises a logic error.
3. Transaction Summarization - This is an optional process which runs only if summarization is enabled for an
account or the book in the transaction type. When you activate summarization, all transaction details which
affect the same account use one of these following methods for summarization:
• For the parameter set to Summarize, the application replaces its details with a single detail. This detail amount
is calculated by subtracting the total credit amount from the total debit amount for all summarized lines. If a
negative amount is calculated, the resulting detail credits the account; if a positive amount is calculated, the
resulting detail debits the account. Note that even if a negative amount is calculated, the resulting detail
contains it as a positive amount, but in the Credit field.
• For the parameter set to Sum debits and credits separately, the application creates one debit detail and
one credit detail. It creates the debit detail by summing up all the details that debit the account; it creates the
credit detail by summing up all the details that credit the account. The summarized credit or debit detail is
created only if the sum is not zero. The original lines are kept separately as details of the summarized lines to
maintain the integrity of the references. This process is similar to what is done for summarized inventory
transactions.
4. Automatic Posting of Rounding Difference - The Epicor application captures all rounding calculations,
both the original amount and the rounding difference amount before the posting process. When the process
runs, the posting engine updates both the rounded amount and the difference amount per each detail line (for
example, on a sales order). Then these values map to a total account which sums each detail line amount.
5. Self-balancing Segments - This procedure verifies that all accounting segments defined as self-balanced are
actually balanced. If unbalanced segments are detected and the Posting Engine is configured to automatically
18 Epicor ERP | 10.0.700.2

balance such segments, it creates additional lines to balance these segments. If the automatic balancing of
accounting segments is not enabled, the Posting Engine generates a logic error.
6. Final Validations - Several validation rules defined at the book level are applied to GL transactions to verify
the validity of each transaction in a specific book. If a validation rule finds that a transaction is invalid, it either
generates a logic error or a warning, depending on the setup of the rule.
Each GL transaction in the affected book is eventually evaluated as either a valid or invalid transaction. Valid
transactions update book balances, while invalid transactions are sent to the Review Journal for additional user
processing. Note that if a transaction is evaluated in one book as invalid, the entire posting session is then
evaluated as invalid and the transactions go to the Review Journal.
Stage 4: Review Transactions
This stage occurs when a business transaction produces an invalid transaction or when you indicate that valid
transactions should also post to the Review Journal.
Activate the second procedure when you either request manual confirmation of posted journals or when the
Posting Engine runs in validation mode. Note that transactions created in validation mode appear on the edit list
but not in the Review Journal.
During this stage, the Epicor application stores the GL transaction in an intermediate journal, called a transaction
review journal. You can review, adjust, cancel, and confirm transactions while they are in the Review Journal.
Confirmed transactions become permanent journal transactions and later post to the GL.
The following images display the process flow for reviewing posted (invalid and valid) GL transactions:
Epicor ERP | 10.0.700.2 19

The only correction you can make directly in the Review Journal is to change the account code. All other changes
must be made in GL Transaction Type Maintenance or within the data itself. When you make changes, run the
automatic process again (Stage 3) and evaluate the results in the Review Journal.
Note When you are satisfied that the posting rules work correctly, you can indicate on the revision that
you no longer want transactions to automatically display in the Review Journal. Then, valid transactions
post straight to the book and the Review Journal only captures invalid transactions.
20 Epicor ERP | 10.0.700.2

Posting Engine Course Specialized Posting Engine Processing
Specialized Posting Engine Processing
This section of the Posting Engine course focuses on General Ledger processes which may take place when the
need arises.
The following specialized programs are discussed in this course:
• GL Transaction Type Maintenance
• GL Controls
• Multiple Books
• Chart of Account Structure Maintenance
• Chart of Accounts Mapping
• Business Activity Queries (BAQ) in Posting Rules
• Lookup Tables Setup
GL Transaction Type Maintenance
GL Transaction Type Maintenance defines the processes you use to post accounts and journals. The posting
process provides a unified series of rules which are applied against specific business transactions.
Each posting process uses one or more GL transaction types. Each GL transaction type has a set of elements -
posting codes, functions, and amounts - specific to its posting process. These elements contain data the posting
rules need to build account and journal details. It also contains a set of rules each book uses; each rule set can
contain the functions, pre-posting rules, reference rules, and posting rules needed to post business transactions
which match the GL transaction type. These rules are flexible and can be modified to meet the needs of a specific
book.
Important The Virtual Business Document (VBD) and Posting Rules are upgraded only if there is an actual
change, improving the performance of the conversion program when a new service pack is released. Refer
to the Transaction Type Conversion application help topic for detailed information on how the conversion
program updates GL transaction types during an upgrade to a new service pack or a new version of the
product.
Use this program to do the following:

• Define the active revision you need to post transactions. This applies the posting codes, amounts, pre-posting
rules, functions, business activity queries, posting rules, reference rules, and other items defined within the
revision. For example, you can define a transaction type revision so it matches a business process within the
current company, or you can define a revision to integrate your Epicor application with other applications.
• Summarize the journals posted to a book by transaction type. As you post invoices, vouchers, and other
transactions, a large number of detail records can generate within the database. Use summary journals to
reduce how many financial transactions save to general ledger tables.
• Define the posting codes, amounts, and other elements used to post transactions for this type. Posting codes
determine the attributes you use with the accounts and journals.
• Define the rules used to post transactions. Posting rules can create a single detail or a pair of balancing details.
These rules determine the detail line amount, the account to which the detail posts, and whether the detail
amount debits or credits the account. In some cases, the rules create a GL control used to store account
contexts for later processing. Pre-posting rules define the defaults used when you manually enter general
ledger accounts.
Epicor ERP | 10.0.700.2 21

Specialized Posting Engine Processing Posting Engine Course
Important If you modify or delete posting rules, it can cause the Epicor application to generate invalid
journals. Display results in the Review Journal to ensure new and modified posting rules create valid
transactions. You should also first run your modified rules on a test server so that you avoid the risk of
posting invalid journals to the general ledger. For more information on how to create and edit posting
rules, review the Posting Engine Technical Reference Guide. This guide also contains a reference section
which documents the extended set of posting rules. It is available in the application help; use the help
Table of Contents and navigate to the General Ledger > Working With section.
Note that you cannot create a new transaction type. Instead, add a new revision to an existing transaction type.
You can assign revisions to different books. Each book has settings that also affect the posting process. These
settings include the chart of accounts, fiscal calendar, and currency the book uses. The general ledger control
used by the posting process defines the accounts that posting rules use. You can set up the posting rules in one
book and then use these same rules in another book.
Example You define a rule for a journal which generates when a sales order posts. The rule obtains the
warehouse ID for the inventory sold and sets the value of a dynamic segment based on the ID.
Menu Path
• Financial Management > General Ledger > Setup > GL Transaction Type
Important This program is not available in the Epicor Web Access.
Revision Control
The Epicor application contains default revisions which use the elements (posting codes, functions, and amounts)
and posting rules the posting process requires.
You cannot change the installed posting rules and elements to control changes to the posting processes. You
can only change and delete new revisions you create.
The Epicor application also prevents an upgrade revision (typically installed through a service pack) to overwrite
an active, modified revision. You can therefore compare the upgrade revision to your modified revision and
change the upgrade revision as necessary. You can then change the upgraded revision's status to Active.
Revisions
To modify transaction types, you create revisions. Only one revision can be active at a time within the book. You
can either create a new revision by copying the existing posting rules, or you can create an entirely new revision
which contains no posting rules and create the posting rules you need.
You can add or update many items within each revision; you can modify posting codes, pre-posting rules, posting
rules, reference rules, functions, book variables, rules variables, operations, and so on.
You can assign one of three status levels to each revision. Each status defines the current state of the revision.
Assign the status on the Revisions > Revision Detail sheet. The Status field has the following options:
• Active - The revision the application currently uses to post GL transactions for the GL transaction type. The
revision is in use, processing GL transactions for all books assigned to it. Only one revision can be active at a
time for each GL transaction type and you cannot modify an active revision.
• Draft - A revision you are currently modifying; this status is the default when you create a new revision. For
as long as the revision stays in the draft status, you can edit it. Once you change its status to Active or Blocked,
it can no longer be updated.
22 Epicor ERP | 10.0.700.2

• Blocked - A previous or alternate revision which is no longer in use. The application does not use this revision
to generate GL transactions for the current GL transaction type. Although you cannot modify a blocked
revision, you can change its status back to active and use it to post again. Blocked revisions are also used as
a reference to compare against the active and draft revision(s).
Use different revisions to model and test changes in the accounting logic for each transaction type. For example,
your company uses posting rules to set values for a dynamic segment that defines a product line. The product
line expires at the end of the year. You create a revision that includes new posting rules which record this change
at the same time.
Tip You can delete blocked revisions by archiving them into a specified folder from the Actions > Delete
Revisions menu.
Option to Manually Review Transactions

In addition to creating a new revision and assigning it a status, you can activate the manual review option when
you select the Manually review all transactions check box. This causes the application to capture all GL
transactions generated by the process and log them in the Review Journal. Epicor recommends you select this
option while you are creating and testing a revision; after you are satisfied with the results, clear this check box
option so the Review Journal only captures errors and warnings.
Upgrades and Revisions

Transaction Type Maintenance has a separate and independent version control for different parts of the transaction
type. These include:
• VBD level
• Version and Package ID on the rule set level
• Version on the posting rule/function level
This extended versioning allows limiting imports and updates to the parts of transaction types where actual
changes are present during manual imports and patch upgrades. You can choose to import new revisions in
replace mode or apply updates to already existing revisions.
When you upgrade the Epicor application through a service pack or patch, you can configure the upgrade in
Update or Replace mode. Refer to the installation guide for detailed instructions.
In the Replace mode, the current active Revision remains Active if there were no changes in the Business
Document Structure. The revision becomes Blocked and a new Active Revision is generated if changes in VBD
were successfully merged. Custom rules of the current revisions are not upgraded. The new out-of-the-box
Revision is installed as blocked. You can then review the blocked version to see if any updates are needed to your
modified revision. If you wish, you can then add your modifications to the new default revision and set its status
to Active.
In the Update mode, the current Active Revision is updated to reflect changes in the Incoming Document
Template. Only out-of-the-box Posting Rules and Functions which have changes are updated. Customized posting
rules/functions are not updated.
Updates are always automatically installed for both the Standard and Expanded packages of rules.
Compare Revisions
Before you make changes to a revision, you can compare revisions to see the different posting elements and
rules between the two versions. To do this, click on the Actions menu and select Compare Revisions. Use this
window to review the differences between the revisions.
Epicor ERP | 10.0.700.2 23

Active Modes
The Epicor application supports two modes of active revisions.

Define which mode you want on the Accounting Transaction Type sheet:
• Always a Single Active Revision - This GL transaction type can only have a single active revision available
at any time for the posting process.
• Select an Active Revision by Date - The GL transaction can have several active revisions available through
a schedule you define. In this mode, each active revision must have an Effective Revision Date (From) value.
Use this date to indicate when this active revision is specifically used during the posting process. This field is
available on the Revisions > Revision Detail sheet. When the system clock moves to the date value defined
on the next active revision, the application automatically sets the status of the previous active revision to
Blocked.
Example The company uses posting rules to set values for a dynamic segment which tracks a product
line. The product line expires at the end of the year. You set a revision that includes new posting rules to
take effect at the same time.
Workshop - Add a Revision
Default revisions have a status of Active or Blocked and cannot be modified. To configure the posting process,
add a new revision. This workshop demonstrates how to use one of the available revisions as a template to add
a revision.
Navigate to GL Transaction Type Maintenance.
Menu Path: Financial Management > General Ledger > Setup > GL Transaction Type
1. In the Transaction Type field, search for and select AR Invoice.
2. From the New menu, select New Revision.

The New Revision window displays.
3. Verify Create new revision by copying existing revision is selected.
4. In the SourceRevision field, select Base Std (Active).
5. Click OK.
The Revisions > Revision Detail sheet displays. This may take a few minutes.
6. In the tree view, select the new revision, namely A - Draft.
7. In the Revision ID field, enter XXXOp (where XXX are your initials).
8. Click Save.
9. Minimize GL Transaction Type Maintenance.
24 Epicor ERP | 10.0.700.2

Manual Review
Use GL Transaction Type Maintenance to activate the manual review functionality.

Typically, valid transactions automatically post to the general ledger (GL) without review. You can indicate that
you want to review all GL transactions before they post. It is best to leverage this feature when you activate a
new revision. A manual review of the transactions can help identify errors that can occur during the posting
process of a revision.
To activate the manual review functionality, navigate to the Revisions > Revision Detail sheet and select the
Manually review all transactions check box.
When you use the manual review feature, all GL transactions post directly to the Review Journal, where you can
review the transaction line details. From there you can use the Actions menu to confirm, adjust, or cancel each
GL transaction.
Workshop - Review Transactions in the Review Journal
If you need to modify one or more of the posting rules, manual review is recommended. This workshop
demonstrates how to set up and use the manual transaction review functionality.
Note This workshop uses Sales Order 5120 as part of the workshop steps. As an alternative, you can use
Sales Order 5357.
Activate Manual Posting

Maximize GL Transaction Type Maintenance.
1. In the tree view, select AR Invoice > Revision: Base Std - Active.
The Revisions > Revision Detail sheet displays.
2. Select the Manually review all transactions check box.
3. Click Save.
Enter an AR Invoice
Navigate to AR Invoice Entry.
Menu Path: Financial Management > Accounts Receivable > General Operations > Invoice Entry
1. From the New menu, select New Group.
2. In the Group field, enter XXXGroup (where XXX are your initials).
3. From the New menu, select New Miscellaneous Invoice.

The Header > Detail sheet displays.
4. In the Sales Order field, enter 5120 and press Tab.
5. From the New menu, select New Line.

The Line > Detail sheet displays.
Epicor ERP | 10.0.700.2 25

6. In the SO Line/Rel field, search for and select the line that displays.
7. Click Save.
8. From the tree view, note the AR Invoice number _________.
9. From the Actions menu, select Group > Post.

The AR Invoice Post Process window displays.
10. Click Submit and close the AR Invoice Post Process window.
11. Exit AR Invoice Entry.
Use the Review Journal

Navigate to the Review Journal.
Menu Path: Financial Management > General Ledger > General Operations > Review Journal
1. Click the Journal Entry button.

The Review Journal Entry Search window displays.
2. In the User ID field, enter Manager.
3. Click Search.
4. Double-click the latest search record line to select it.
5. In the tree view, navigate to and select NNN > Main Book > YYY AR Invoice > Transaction Lines >
Records: All > 1 (where NNN is the Review Journal number and YYY is the AR Invoice reference).
The Transactions > Lines > Detail sheet displays.
6. Review the transaction details for the first line.

The field below the Amount field displays whether the amount debits or credits an account. In this task,
the amount debits the account used to generate transaction line 1.
The GLAccount section displays the general ledger account number for transaction line 1.
The Booking Rule Reference field displays the posting rule used to generate transaction line 1.
The Description field displays the reference details for the AR invoice.
7. From the Actions menu, select Journal Entry Confirmation.

The transactions are now posted to the general ledger.
8. Exit the Review Journal.
26 Epicor ERP | 10.0.700.2

Automatic Posting
Use the automatic posting functionality (which is the default) to post valid transactions to the general ledger
without review. When using automatic posting, details are not available in the review journal.
Workshop - Use Automatic Posting
This workshop demonstrates how automatic posting works in the Epicor application. When the manual review
functionality is not used, valid transactions (for example, AR invoices) automatically post to the general ledger.
Activate Automatic Posting

1. In the tree view, verify AR Invoice > Revision: Base Std - Active is selected.
2. On the Revisions > Revision Detail sheet, clear the Manually review all transactions check box.
3. Click Save.
Enter an AR Invoice


7. Click Save.

Epicor ERP | 10.0.700.2 27

Use the Review Journal


3. Click Search.
A relevant record does not display. When the AR invoice posted, the Manually review all transactions
check box was clear so the transaction automatically posted to the general ledger. Because the posting
process was successful, a review journal for the transaction is not available.
4. Close the Review Journal Entry Search window and exit the Review Journal.
Incoming Document Templates
An incoming document template specifies the elements used to gather business transaction data for the posting
rules. Each GL transaction type uses one or more templates, and each template has a set of elements unique to
the posting process for that GL transaction type.
All templates gather both general and specific data about posted business transactions. General information
includes the date the business transaction posts, the business entity involved in the transaction, and the journal
code for the transaction. Each template also contains a set of elements specific to a posting process. For example,
the template used to post invoices defines elements that contain data from the invoice header, invoice lines, and
tax lines.
Templates can combine predefined and custom elements. Predefined elements ensure support for the transaction
type's posting processes. You cannot change or delete predefined elements. You can add custom elements to
provide attributes needed by any new or modified posting rules. You can also modify and delete your custom
elements.
The posting rules for a revision use information from the template elements to define journal details. These rules,
except for the reference rule, determine the detail amount, the account to which the detail posts, and whether
the amount debits or credits the account. The reference rule is used to set up and populate a reference GL control
with no direct relation to posting any amounts or selecting debit and credit accounts.
Each incoming document template contains the following elements:
• Document Lines - Document lines group elements obtained from a portion of the posted transaction. For
example, an accounts receivable invoice template contains document lines for the invoice header, invoice line,
tax line, and miscellaneous charge line.
• Posting Entities - Entities group related posting codes together. An entity holds a posting code collection
and provides default settings used to populate fields.
• Posting Codes - Posting codes define the parameters used with posting rule operations and functions. Posting
rules use posting code values to create journal details. You can add posting codes and modify and delete the
codes you create. Posting codes are grouped under a parent posting entity.
• Amounts - Amount elements hold the transaction amounts used by calculated fields.
28 Epicor ERP | 10.0.700.2

Selection Criteria
In GL Transaction Type Maintenance, selection criteria are statements which return specific data from the posting
codes on the revision. The posting rules then use the data to create accounts used in journal details.
The incoming document template contains posting codes unique to its process. The posting codes are grouped
by posting entities and the entities are then grouped by the document lines from the business transaction (incoming
document template).
You can create or update selection criteria to return the posting code data required by a rule. For example, you
want to define a rule which posts an invoice amount to an account segment based on the Warehouse ID. The
incoming document template contains an invoice line element which has the warehouse posting entity which
contains the posting code required for each warehouse. You select Invoice Line in the For Each field and use the
other field in the sheet to create a statement that selects the correct posting code. The result resembles a WHERE
clause in a SQL statement. You then click Add to include the statement in the Selection Criteria field. You use
the And, Or, and Not buttons to insert logical operators into the statement.
Selection criteria can only pull in data from parent tables. Information stored in child tables cannot be pulled in
by using selection criteria from the parent. You must create or modify a posting rule which pulls in data directly
from the child table.
Posting Codes
To add posting codes, you define settings that control how the revision retrieves data used for its posting rules.
These rules includes defining the data source for the posting codes. The application obtains data for posting code
fields by using:
• Entity Fields-- Business entities (do not confuse these items with posting entities) are static database tables
like Part, Customer, and Supplier which contain data a business transaction requires. Because of this, you can
specify a field in the same table to access data in the business entity field.
• Business Activity Queries (BAQs)-- You can pull in more detail into the revision by linking a business activity
query (BAQ) to an incoming document template. The revision then uses selection criteria defined for a posting
rule to obtain data pulled in by the BAQ. The interface can return a value from a single field or a calculated
sum of fields.
Posting (Booking) Rules
Each revision contains a series of booking rules (also called posting rules). These rules include general posting
rules, header rules, pre-posting rules, reference rules, and functions. Rules defined for a single book make up a
rule set; each rule set generates a complete journal which posts to the book.
Posting rules create business transaction journal details. These rules create either a single journal detail entry or
a pair of balancing entries. Rules determine the amount, the accounts to which the amount posts, and whether
the amount debits or credits the account. The Reference rules are different; these rules are used to set up and
populate a reference GL control with no direct relation to posting amounts or selecting debit and credit accounts.
The version control on the rule level is used when comparing two rule sets, one of which is about to be imported
and the other already in the system. This provides a way to distinguish between posting rules that have changed
and therefore need to be pulled in. Those that have not changed do not need to be imported, saving time on
the import and conversion.
The Version field specifies the individual rule version. The Version field uses a single numeric sequence and
increments each time a rule is changed in a corresponding rule.
The Patch Version field specifies the rule patch version. A single numeric sequence is used and it increments
each time a change is released in a patch to a client between service packs. The patch version resets to zero each
time a service pack is released.
Epicor ERP | 10.0.700.2 29

To create a new posting rule, add a rule and select appropriate values to define each modifiable option. Each
rule builds the detail field-by-field. You can create, modify, and delete posting rules.
Example You define a rule for a transaction that generates when a sales order posts. The rule obtains
the warehouse ID for inventory sold and sets the value of a dynamic segment based on that ID.
The items you can modify for posting rules include:

• Variables: Use variables to store an intermediate value required to calculate a specific field in a rule.
• Functions: These reusable rules define processes used across the posting rules for the transaction type. The
posting rules reference them. For example, the book might use a chart of accounts with a mandatory division
segment. A reusable function pulls in a posting code value used to look up and return the segment value.
• Parameters: These items select the posting code to which the posting rules apply. The Selection sheet defines
the process used to select a posting code from one of the document lines in the incoming document template.
• Operations: These items include functions used to define container values. Operations include lookup functions
that set segment values based on the attributes defined in a posted transaction.
Posting rules can also create output general ledger (GL) controls. These optional controls associate source non-GL
data, detail accounts, and account contexts. By storing this data, the Epicor application can then use it during
later processing.
Tip If you need to make minor changes to the posting process for a transaction type, use account mapping
and lookup tables. Chart of Accounts Mapping defines maps between chart of accounts (COA) segments.
A map transfers journal details from one book into another book. Lookup Tables Setup locates a segment
value based on a value in the posted transaction. This reduces the need to define lookup tables in posting
rules.
Header Rule
This posting rule type sets up data that GL journal details share, for example, Journal Code and Apply Date. No
GL journal details are produced.
A header rule always executes before the posting rules. Only one header rule is available for each book.
You can use this rule to assign default values to GL journal detail fields, but you can also override these values
in the posting rules. For example, you can initiate transaction text in the header rule but then override this text
in a posting rule which generates later.
To add a new header rule, add a new posting rule and select its Header check box.
Posting rules, together with a header rule, create a GL transaction.
Pre-Posting Rule
Pre-posting rules create a GL control with a determined account. Use this feature in certain programs to provide
a default account before the actual transaction document posts.
Each pre-posting rule is called individually. They do not produce GL journal details.
To add a pre-posting rule, from the New menu, select New Pre-Posting Rule.
Example A pre-posting rule creates the default expense account for the miscellaneous line on a purchase
invoice.
Reference Rule
The Reference Rule supports correspondence accounting by generating strictly bi-line GL transactions. This rule
functions similarly to the pre-posting rules. The reference rule is used only to populate a GL control and it does
not populate amounts or debit/credit accounts. Correspondingly, this rule type does not create GL journal details.
30 Epicor ERP | 10.0.700.2

However, unlike pre-posting rules, the reference rule is run during the normal posting process and has a property
that indicates the specific posting entity to which the outgoing GL control is attached.
To add a pre-posting rule, from the New menu, select New Reference Rule.
Functions
Each function is an algorithm that pulls in data common to the posting rules within the GL transaction type. The
other rules and functions share it. You can create, modify, and delete functions as necessary. When you add or
modify a function, you extend the operations list available to the posting rules.
To add a new function, from the New menu, select New Function.
Workshop - Copy and Delete Posting Rules
When you modify posting rules, you can use existing posting rules as a template. You can delete a posting rule
up until the point at which it is activated. This workshop demonstrates how to copy and delete a posting rule.
Copy a Posting Rule

1. In the tree view, navigate to and select AR Invoice > Revision: XXXOp - Draft > Rules > Book:Main
Book > Posting Rules > Post Tax Amount.
In the revision title, XXX are your initials.
2. From the Actions menu, select Copy Rule.
3. From the Actions menu, select Paste Rule.

In the tree view, a Post Tax Amount_1 rule is added to the Posting Rules list.
4. Click Save.
Delete a Posting Rule
1. In the tree view, select AR Invoice > Revision: XXXOp - Draft > Rules > Book:Main Book > Posting
Rules > Post Tax Amount_1.
2. Click Delete.
A Delete Confirmation message displays.
3. Click Yes to confirm you want to delete the record.
4. Click Save.
Operations
Use GL Transaction Type Maintenance to add, modify, and delete rule operations.
The Revisions > Book > Booking Rules > Operations sheet has three sections:
• Summary
Epicor ERP | 10.0.700.2 31

• Type
• Options
Summary
This area displays operations available for the posting rules.
Type
Use these radio buttons to indicate whether the type is an Operation or a Logical Condition. An operation is
an algorithm which calculates a value or values; a logical condition uses If, Then, or Else commands to determine
how the data processes as it moves through the operation algorithms. Select the type you need; these options
change what displays in the Options section.
Options
This section contains two fields whose values reflect the selected operation type.
• If you select the Operation option, the Field Name and Formula fields display. The list of fields (Field Name)
available for an operation depend on the GL transaction type and the posting rule details. The Formula field
contains a rule template with variables. The black text is a rule instruction you cannot change. The blue
underlined text is modifiable. Click on this text and select the variable value you need.
• If you select the Logical Condition option, the Logical Condition and Formula fields are available. The
logical condition list includes Else, Else If, and If. Just like the Operation option, the Formula field contains
a rule template with variables. The black text is a rule instruction you cannot change. The blue underlined
text, however, is modifiable. Click on this text and select the variable value you need.
Workshop - Enter a Header Rule
When you are working in a multi-book environment, you have the option to post a manual GL journal entry as
a multiple book entry. Out of the box, the GL multi-book transaction type (MultiGLJrn) includes the standard
set of posting rules for a single book. You can then use these default posting rules as a starting point to build
on the rules for your book. Although a standard header rule exists for MultiGLJrn, in this workshop, add a header
rule for the MultiGLJrn transaction type, and include operations for apply date and journal code.
Sales Order 5357.
32 Epicor ERP | 10.0.700.2

Add a Revision
1. Navigate to the Accounting Transaction Type sheet.
2. In the Transaction Type field, search for and select MultiGLJrn.

5. In the SourceRevision field, select Base Std (Blocked).

If Base Std (Blocked) does not display as a selection, select Base Std (Active). However, in the workshop
task Add a Header Rule, you will need to verify there is no other active header rule.
6. Click OK.
The Revisions > Revision Detail sheet displays.
7. In the tree view, select the new revision.
8. In the Revision ID field, enter XXXHd (where XXX are your initials).
10. Click Save.
Add a Header Rule

To post transaction header details, add a header posting rule.
1. In the tree view, verify MultiGLJrn > Revision: XXXHd - Draft is selected.
2. From the New menu, select New Posting Rule.

The Revisions > Book > Booking Rules > Detail sheet displays.
3. In the Name field, enter XXX_Header Rule (where XXX are your initials).
4. In the Description field, enter Header Rule.
5. Select the Header check box.

If there is another active header rule under XXXHd - Draft that was copied over, a message displays saying
there can only be one. You can select the other Header Rule in the Tree View and clear the Header and Is
Active check boxes to allow the new Header Rule to be created.
6. Click Save.
7. Navigate to the Revisions > Book > Booking Rules > Selection sheet.
8. In the For Each field, select GL Journal Entry.
Epicor ERP | 10.0.700.2 33

9. Click Save.
Add an Apply Date Operation

The posting process apply date operation instructs the Epicor application on what apply date to add to the GL
journal header when a journal posts.
This task demonstrates how to add the following apply date operation:
Apply Date = GL Journal Entry - GL Journal Entry Head - Apply Date
This operation selects an apply date from the header details in GL Journal Entry.
1. Navigate to the Revisions > Book > Booking Rules > Operations sheet.
2. From the New menu, select New Rule Operation.
3. In the Type section (at the bottom of the screen), verify the Operation option is selected.
4. In the operation option field (which currently has Comment selected), select Apply Date.
5. In the formula field (to the right of the operation option field), select the Value formula.
6. In the formula field, click Value and select ABT Field > GL Journal Entry > Posting Codes > GL Journal
Entry Head > Apply Date.
If you cannot access the entire posting rule operation formula field, click the area between the operation
option field and the formula field, and move the field separator to the left.
The formula changes to:
GL Journal Entry - GL Journal Entry Head - Apply Date
In the Summary section, the operation displays as:
Apply Date = GL Journal Entry - GL Journal Entry Head - Apply Date
7. Click Save.
Add a Journal Code Operation

The posting process journal code operation instructs the Epicor application on what journal code to add to the
GL journal header when a GL journal posts.
This task demonstrates how to add the following journal code operation:
Journal Code = GL Journal Entry - GL Journal Entry Head - Journal Code
This operation selects journal code from the header details of GL Journal Entry.
1. In the Summary section, right-click XXX_Header Rule (where XXX are your initials) and select Add.
2. Select the Please select variable and value or function operation line which displays.
3. In the Type section, verify the Operation option is still selected.
4. In the operation option field, select Journal Code.
5. In the formula field, select the Value formula.
34 Epicor ERP | 10.0.700.2

6. In the formula field, click Value and select ABT Field > GL Journal Entry > Posting Codes > GL Journal
Entry Head > Journal Code.
GL Journal Entry - GL Journal Entry Head - Journal Code
Journal Code = GL Journal Entry - GL Journal Entry Head - Journal Code
7. Click Save and minimize GL Transaction Type Maintenance.
Functions
Functions are standard packages of posting rules which contain functionality common across the posting rules
within a revision. They include the rules required to populate account segments for natural accounts, divisions
and departments.
When you install or update the Epicor application, functions are included as part of each GL transaction type
revision.
Typically each function contains a series of account and journal contexts. When the posting engine processes
the function, it pulls in a complex piece of data and makes this data available to the pre-posting, posting, and
reference rules for the revision. For example, when the AR Invoice transaction type is run, its functions pull AR
account information out of the database to make this information available to the AR invoice posting rules.
Each function is an algorithm that gathers the specific data and the function code which processes the information
into a format usable by the pre-posting, posting, and reference rules. The other rules and functions share the
gathered data. You can create, modify, and delete functions as necessary. When you add or modify a function,
you extend the operations list available to the posting rules.
Functions are very useful when you create or update posting rules. You can use functions to avoid writing complex
rules to pull in common financial data. They also help you avoid constantly repeating the GL hierarchy while you
develop posting rules.
System Functions
A list of the system functions is below.

These algorithms define operations common across the GL Transaction Types. Items you can modify are in bold
text.
• A=B
• Value
• Lookup Map name For Field Using arg1, arg2
• Lookup COA map name For Segment Using Segment value
• Lookup Business Data Using Query Field
• Convert Amount To Currency Using Rate Type
• End of Period which includes Date
• Account is Valid
• Account is not Valid
• Value is Available
• Value is not Available
• Get Account From GLControl For Current Book AND Context Context
Epicor ERP | 10.0.700.2 35

• Get Segment From GLControl For Current Book AND Context Context
• Select Amount From Doc Line Where Add Condition
• Comment Text
• Log Error: Log Error Text
• Raise error: Error Description
• Log warning: Warning Description
• End Rule
• Log Debug Message: Log Debug Message
• Argument1 and Argument2 is Available
• Lookup COA map name Using Account Account
• Get Book Amount From GLControl For Current Book AND Context Context
• Get External Account From GLControl For Context Context
Workshop - Create a User-Defined Function
This workshop demonstrates how to create and apply a user-defined function in the posting rules.
Business Scenario: Your business requires you to assign a Division modifier to the AR Account to separate
receivables by site Division. While similar functions exist within the AR Invoice GL Transaction Type, this particular
function does not.
Add a Revision
1. Navigate to the Accounting Transaction Type sheet.
2. In the Transaction Type field, search for and select AR Invoice.

5. In the SourceRevision field, select Base Std (Active).
6. Click OK.
The Revisions > Revision Detail sheet displays. This may take several minutes.
8. In the Revision ID field, enter XXXFunc (where XXX are your initials).
9. Click Save.
Create a Function
1. Navigate to the Revisions > Book > Functions > Detail sheet.
2. From the New menu, select New Function.
36 Epicor ERP | 10.0.700.2

The Function field populates with UserFunction Param1 and Param2.
3. In the Function field, delete UserFunction Param1 and Param2 and enter Compile Account Using
Source Account and Given Division.
4. In the Description field, enter Compiles account from source account and division.
5. In the Function field, double-click in front of and select (highlight) Source Account.
6. Right-click on Source Account and select Make parameter as type > Account > Master Chart.
7. In the Function field, double-click in front of and select (highlight) Given Division.
8. Right-click on Given Division and select Make parameter as type > String.
9. In the Return field, select Account.
10. In the Return field, click Account and select Master Chart.
The Return field displays Account.Master.
11. Click Save.
Add Function Text
1. Right-click Function Text and select Add.

Please select variable and value or function displays.
2. In the Type section (at the bottom of the screen), verify the Operation option is selected.
3. In the operation option field (which currently has Comment selected), select Temp Account.
4. In the formula field (to the right of the operation option field), select the Value formula.
5. In the formula field, click Value and select Variable > Source Account > Source Account.
The function text line changes to:
Temp Account = Source Account
6. In the function text, right-click Temp Account = Source Account and select Add.
7. In the function text, click on the Please select variable and value or function line.
8. In the operation option field, select Temp Account.
9. In the operation option field, click Temp Account and select Division.
11. In the formula field, click Value and select Variable > Given Division.
Temp Account.Division = Given Division
Epicor ERP | 10.0.700.2 37

12. Click Save.
Add a Logical Condition
1. In the function text, right-click Temp Account.Division = Given Division and select Add.
2. In the function text, click on Please select variable and value or function.
3. In the Type section, select the Logical Condition option.
4. In the operation option field, select the If logic.
5. In the formula field, select the Account is not Valid condition.
6. In the formula field, click Account and select Variable > Temp Account > Temp Account.
If Temp Account is not Valid
7. In the function text, right-click If Temp Account is not Valid and select Add.
9. In the operation option field, select Temp Account.
10. In the operation option field, click Temp Account and select Division.
12. In the formula field, click Value and select Variable > Source Account > Division.
Temp Account.Division = Source Account.Division
13. Click Save.
Enter a Result
1. In the function text, right-click Temp Account.Division = Given Division and select Add.
3. In the operation option field, select Result.
5. In the formula field, click Value and select Variable > Temp Account > Temp Account.
Result = Temp Account
38 Epicor ERP | 10.0.700.2

6. Click Save.
Add a Rule Variable
1. From the tree view, navigate to Revision: XXXFunc - Draft > Rules > Book: Main Book > Posting Rules
> Post Invoice Amount to Accounts Receivable.
In the revision ID, XXX represents your initials.
The Revisions > Book > Booking Rules > Operations sheet displays.
2. From the New menu, select New Rule Variable.

The Revisions > Book > Booking Rules > Rule Variables > Detail sheet displays.
3. In the Variable Name field, enter Site Division.
4. Click Save.
Modify Standard Posting Rule
2. In the operation text, right-click the Transaction Amount = Select Amount From AR Invoice Where
Name = Invoice AND Currency Type = Transactional line and select Insert.
Please select variable and value or function displays above the Transaction Amount line.
3. In the Type section, verify the Operation option is selected.
4. In the operation option field, select Site Division.

This option is available because of the steps you took to add a rule variable in the previous workshop task.
5. In the formula field, select the Get Segment From GLControl For Current Book AND Context Context
formula.
6. In the formula field, click Segment and select Values > Division.
7. In the formula field, click GLControl and select ABT Field > AR Invoice > Posting Codes > Plant > GL
Control > GL Control.
8. In the formula field, click Context and select Values > Division.
9. Click Save.
10. In the operation text, right-click the Transaction Amount = Select Amount From AR Invoice Where
Name = Invoice AND Currency Type = Transactional line and select Insert.
Please select variable and value or function displays above the Transaction Amount line.
11. In the operation option field, select AR Account.
12. In the formula field, select the Compile Account Using Source Account and Given Division function.
This is the function you created in a previous workshop task.
13. In the formula field, click Source Account and select Variable > AR Account > AR Account.
Epicor ERP | 10.0.700.2 39

14. In the formula field, click Given Division and select Variable > Site Division.
15. Click Save.
Activate the Revision
1. Navigate to the Revisions > Revision Detail sheet.
3. Click Save.
4. In the Status field, select Active.

Activating a revision can take up to a few minutes. The status field deactivates when activation is complete.
Review GL Controls on Division

Navigate to Site Maintenance.
Menu Path: Financial Management > Multi-Site > Setup > Site Maintenance
1. In the Site field, search for and select Evanston.
2. Navigate to the GL Controls > Detail sheet.
3. In the Control field (populated with EVAN), right-click and select Open With > GL Control Code Entry.
The GL Control Code maintenance opens and displays the selected Division control.
4. From the tree view, navigate to GL Controls > Account Context > Main Book > Division.
5. Notice the value in the Account field (02).

In Division type GL controls, you only need to populate the division segment in the account.
6. Exit GL Control Maintenance.

If you receive a message while exiting the program, click No.
7. Exit Site Maintenance.
Post an AR Invoice

40 Epicor ERP | 10.0.700.2

5. Update the Site field to Evanston.

8. Click Save.

Review the Result


3. Click Search.
Records: All > 1 (where NNN is the Review Journal code and YYY is the AR Invoice reference number).
6. Verify the Booking Rule Reference field displays Post Invoice Amount to Accounts Receivable.
This is the rule to which you applied your user-defined function in a previous task.
7. In the GLAccount field, verify 1100-02-00 displays.

The division segment displays as 02. The application was able to locate and post to that division segment
because of the GL control assigned to the Evanston division and the user-defined function you created and
added to the Post Invoice Amount to Accounts Receivable posting rule.
Important The application will not post to an invalid account. If the receivables account was never
generated for the Evanston division (1100-02-00), the application knows to take the default receivables
account (1100-00-00).

The transaction is now posted to the general ledger.
Epicor ERP | 10.0.700.2 41

Workshop - Add a Posting Rule
If the posting rules for your company differ from the standard or extended posting rules for the Epicor application,
you can modify or add rules and rule operations. This workshop demonstrates how to create a new posting rule
to post AR invoices. Use manual review to verify the AR invoice posts using the new rule.
Add a Posting Rule

1. In the tree view, select AR Invoice > Revision: XXXOp - Draft.

Even if you are working with a different transaction type than in another workshop, you can access the AR
Invoice transaction type from the tree without having to select it on the Accounting Transaction Type sheet.

3. In the Name field, enter XXX_Post to AR (where XXX are your initials).
4. In the Description field, enter Simple posting rule.
5. Click Save.
Add a Selection Criterion

Add a new selection criterion to use the new posting rule for AR invoices but not for credit memos.
2. In the For Each field, select AR Invoice.
3. In the Source field, click ABT Field and select AR Invoice > Posting Codes > Details > Is Credit Memo.
4. In the Operator field, select the equals sign (=).
5. In the Argument field, click the ellipsis button (...).

The Enter value window displays.
6. In the Enter value window, verify False is selected and click OK.
7. Click the Add button.
8. Click Save.
Define Reference GL Control Information
1. Navigate to the Revisions > Book > Booking Rules > Detail sheet.
2. In the Reference Entity field, click ABT Field and select AR Invoices > Details.
42 Epicor ERP | 10.0.700.2

3. In the Outgoing GL Control Type field, select AR Invoice.
4. In the Debit Context field, select Receivables.
5. In the Credit Context field, select Receivables.
6. Click Save.
Add a Book Amount Operation

The posting process book amount operation instructs the Epicor application on what book amount to add to the
transaction details when an AR invoice posts.
This task demonstrates how to add the following book amount operation:
Book Amount = Select Amount From AR Invoice Where Name = Invoice AND Currency = Book Currency
The Select Amount operation uses specific selection criteria to select an amount from the business transaction
document. In this task, the business transaction document is AR Invoice. Selection criteria include the document
level to which the selected amount belongs (in this task, Invoice), and all the amount's attributes (in this task,
Currency).
5. In the operation option field, select Book Amount.
6. In the formula field, select the Select Amount From Doc Line Where Add Condition formula.
7. In the formula field, click Doc Line and select AR Invoice.

Select Amount From AR Invoice Where Add Condition
8. In the formula field, click Add Condition and select Name.

Select Amount From AR Invoice Where Name = Value Add Condition
9. In the formula field, click Name = Value and select Values > Invoice.
Select Amount From AR Invoice Where Name = Invoice Add Condition
10. In the formula field, click Add Condition and select Currency.
If you cannot access the formula field, click the area between the operation options field and the formula
field, and move the separator to the left.
Select Amount From AR Invoice Where Name = Invoice AND Currency = Value Add Condition
Epicor ERP | 10.0.700.2 43

11. In the formula field, click Currency = Value and select Variable > Book Currency.
Select Amount From AR Invoice Where Name = Invoice AND Currency = Book Currency Add
Condition
Book Amount = Select Amount From AR Invoice Where Name = Invoice AND Currency = Book Currency
12. Click Save.
Add a Transaction Amount Operation

The posting process transaction amount operation instructs the Epicor application on what transaction amount
to add to the transaction details when an AR invoice posts.
This task demonstrates how to add the following transaction amount operation:
Transaction Amount = Select Amount From AR Invoice Where Name = Invoice AND Currency Type =
Transactional
The Select Amount operation uses specified selection criteria to select an amount from the business transaction
document. In this task, the business transaction document is AR Invoice. Selection criteria include the document
level to which the selected amount belongs (in this task, Invoice) and all the amount's attributes (in this task,
Currency Type).
4. In the operation option field, select Transaction Amount.
5. In the formula field, select the Select Amount From Doc Line Where Add Condition formula.
6. In the formula field, click Doc Line and select AR Invoice.

Select Amount From AR Invoice Where Add Condition
7. In the formula field, click Add Condition and select Name.

Select Amount From AR Invoice Where Name = Value Add Condition
8. In the formula field, click Name = Value and select Values > Invoice.
Select Amount From AR Invoice Where Name = Invoice Add Condition
9. In the formula field, click Add Condition and select Currency Type.
Select Amount From AR Invoice Where Name = Invoice AND Currency Type = Value Add Condition
44 Epicor ERP | 10.0.700.2

10. In the formula field, click Currency Type = Value and select Values > Transactional.
Select Amount From AR Invoice Where Name = Invoice AND Currency Type = Transactional Add
Condition
Transaction Amount = Select Amount From AR Invoice Where Name = Invoice AND Currency Type
= Transactional
11. Click Save.
Add a Debit Account Operation

The posting process debit account operation instructs the Epicor application on what debit account to use for
the transaction when an AR invoice posts.
This task demonstrates how to add the following debit account operation:
Debit Account = Get Account From AR Invoice - Company Parameters - AR Account GL Control For Current
Book AND Receivables Context
The Get Account operation uses specified selection criteria to obtain an account number from a GL control. In
this task, the GL control type is AR Account. This GL control is taken from the company default GL controls
(Company Parameters) for AR Invoice. Selection criteria include the book (in this case, Current Book), and
the context (in this case, Receivables). The Receivables context means that the debit account is taken from the
Receivables context of the AR Account GL control.
4. In the operation option field, select Debit Account.
5. In the formula field, select the Get Account From GLControl For Current Book AND Context Context
formula.
6. In the formula field, click GLControl and select ABT Field > AR Invoice > Posting Codes > Company
Parameters > AR Account GL Control > AR Account GL Control.
Get Account From AR Invoice - Company Parameters - AR Account GL Control For Current Book
AND Context Context
7. In the formula field, click Context and select Values > Receivables.
Get Account From AR Invoice - Company Parameters - AR Account GL Control For Current Book
AND Receivables Context
Debit Account = Get Account From AR Invoice - Company Parameters - AR Account GL Control For
Current Book AND Receivables Context
Epicor ERP | 10.0.700.2 45

8. Click Save.
Disable the Posting Rule

To use the new posting rule, you must disable the old rule for posting AR invoices.
1. In the tree view, select AR Invoice > Revision: XXXOp - Draft > Rules > Book:Main Book > Posting
Rules > Post Invoice Amount to Accounts Receivable.
3. Clear the Is Active check box.
4. Click Save.
3. Click Save.
5. Wait until the Status field disables and displays Active.
6. Click Save and minimize GL Transaction Type Maintenance.
Enter an AR Invoice


7. Click Save.
46 Epicor ERP | 10.0.700.2


Review the Result


3. Click Search.
Records: All > 1 (where NNN is the Review Journal code and YYY is the AR Invoice reference number).
6. Verify the Booking Rule Reference field displays XXX_Post to AR (where XXX are your initials).
The first line was generated using the posting rule created in prior workshop tasks.
7. In the space provided, note the Transaction Line 1 details.

Booking Rule Reference
______________________________________________________
GL Account and the account Description
______________________________________________________

The transactions are posted to the general ledger now.
Epicor ERP | 10.0.700.2 47

GL Controls
You use General ledger (GL) controls to assign specific accounts to business transactions. Each GL control links
to a GL Control Type which provides the template it uses to generate account and journal contexts.
The application generates accounts through this hierarchy:
1. Business Entity: These are the database tables which store the business transaction information. When a
user enters a business transaction, it populates these tables with data.
2. GL Control Type: These provide the template for the account context the business transaction uses. Each
GL control type links to one or multiple business entities. Any business transactions which populate a business
entity table are then evaluated through the GL control type. Each context can be populated with a specific
account code for every book within the Epicor application.
3. GL Control: Each GL control maintains a list of accounts, and each account, in turn, is assigned to a
user-defined string which defines the specific account. This account displays with the GL transaction.
The same hierarchy is used to maintain a list of journal codes, as each GL control defines the specific context of
the journal. The exception to this method is that journal codes are not dependent on the book.
Example The Sales GL control type defines the account template used for all GL controls linked to it which
generate sales accounts. When a business transaction is recorded in the Customer business entity that
matches the account context on the Sales GL control type, the appropriate account is selected from a GL
control that links to the GL control type.
GL controls do not apply to programs where you select posting accounts when you enter transactions. Examples
of this type of program include AP Adjustment Entry and Cash Receipt Entry. The master chart of accounts defines
accounts available to these programs.
48 Epicor ERP | 10.0.700.2

GL Control Type Maintenance
General ledger (GL) control types group together account contexts, journal contexts, and business entities used
to define the accounts generated through GL controls. Use GL Control Type Maintenance to create and edit
the GL control types you use with the current company.
GL control types define:
• Account contexts - GL controls linked to the GL control type use its account contexts to specify the books
and accounts to which GL transactions post. The posting rules specified within the GL transaction type use
this account information to define each GL detail. You can view and modify posting rules within GL Transaction
Type Maintenance.
• Account entry defaults for GL controls - These default values limit how an account maps to a book or
requires you use a specific account with all GL controls linked to the GL control type.
• Journal contexts - The journal contexts associate journal codes with the GL controls linked to the GL control
type. Journal codes group journals created through the posting process which apply to the business transaction.
• Business Entities - The business entities defined on the GL control type indicate against which database
tables the GL control type is used. Business entities define items such as Customer, Supplier, Project, Product
Group, Part, and so on, and are at the top of the hierarchy which generates accounts during the posting
process. The items directly below business entities in the hierarchy are GL control types. Each GL control type
links to a specific business entity, and so the business entity defines what areas of the database the GL control
type updates through its account and journal contexts. GL control types are the templates the third and final
level of this hierarchy (GL controls) use. A GL control uses the account contexts specified through the GL
control type to define the specific accounts which update for each transaction.
You can modify GL control types to extend the posting functionality. Ensure the new account and journal contexts
are appropriate for the business entities selected on the GL control type.
The Epicor application comes with a set of predefined GL control types. These predefined GL control types
correspond to the programs that maintain GL controls that apply to posted transactions. You can create a GL
control type to support a new accounting process or to integrate the Epicor application with another financial
application.
Menu Path
• Financial Management > General Ledger > Setup > GL Control Type
GL Control Maintenance
General ledger control codes define the accounts and journal codes available during the posting process for a
specific transaction. All the posting accounts the Epicor application uses for each business transaction are defined
through GL Control Maintenance.
GL controls are used in the posting hierarchy. Business entities are at the top of this hierarchy; they are the
database tables/fields which hold the data needed for the posting process. The items directly below business
entities in the hierarchy are GL control types. Each GL control type is linked to a specific business entity, and so
the business entity defines what areas of the database the GL control type updates through its account and
journal contexts. GL control types are templates used by the third and final level of this hierarchy -- GL controls.
A GL control uses the account contexts specified through the GL control type to define the specific accounts
which update for each transaction.
You can create and modify GL controls to extend the posting functionality. First, link a GL control to a GL control
type; each GL control uses the account and journal contexts from the control type as a template. The GL control
Epicor ERP | 10.0.700.2 49

then uses these templates to determine the specific account string and journal code to use with a business
transaction.
You can associate one or more GL controls with a record in a setup (maintenance) program. Each control associated
with a record must belong to a different GL control type. The association allows the use of control values when
the record applies to a posted transaction.
During posting, the posting rules defined in GL Transaction Type Maintenance use GL controls to create
transaction details. The posting rules access account values through the references to the account contexts defined
on the linked GL control types. Often, GL control accounts lack values for one or more segments. The posting
rules then use posted transaction data to define these segment values.
Example The AR Account and AP Account control types reference the Company business entity.
• You define GL controls based on both types and apply them to Company A in Company Configuration.
• You post a transaction that belongs to Company A.
• The posting rules for the GL transaction type use the GL controls' account references to create the
accounts for the company journals.
Example
• You add a Landed Cost account context to the AP Account GL control type.
• You then create a GL control under the AP Account GL control type.
• You can now enter a GL account in the Landed Cost account context in the GL control.
• You now apply this GL control to a company record (Company Configuration).
Ensure the new account contexts are appropriate for the business entities against which the type applies.
When journal codes are linked with GL controls, applicable transactions the posting process creates are recorded
in associated journals. As a result, you can track and report on journals by the generated journal code.
You cannot associate GL controls with programs where users select posting accounts when they enter transactions.
Examples of this type of program include AP Adjustment Entry and Cash Receipt Entry. The Master Chart of
Accounts (COA) defines the accounts available to users of these programs.
Important If you modify or delete GL control codes, it can cause invalid journals to generate. Verify the
posting processes which use the GL control create valid accounts after the changes.
Menu Path
• Financial Management > General Ledger > Setup > GL Control Code
Workshop - Revise AR Invoice Posting Rules
This workshop demonstrates how to change GL control attributes and configure a posting rule operation to use
a new GL control attribute.
Sales Order 5357.
Review Current Posting Rule Details

To change the account used to generate the AR invoice transaction, find the GL control, book, and context used
to generate the AR invoice posting transaction. This task demonstrates how to find the posting rule's operation
detail that relates to an AR invoice account.
50 Epicor ERP | 10.0.700.2

1. In the tree view, navigate to and select AR Invoice > Revision: XXXOp - Active > Rules > Book:Main
Book > Posting Rules > XXX_Post to AR (XXX are your initials).
This rule was used to create the first transaction line related to the last AR invoice you posted for sales order
5120. This rule follows similar logic to the rule, Post Invoice Amount to Account Receivable. That is the
rule you deactivated in a prior workshop.
2. Review the AR invoice operation details.

The XXX_Post to AR (where XXX are your initials) rule has the following operation that relates to the
receivables account:
• Debit Account = Get Account From AR Invoice-Company Parameters-AR Account GL Control For
Current Book AND Receivables Context
This operation means the application looks for the AR Account GL control assigned to the Company
Parameters. From the GL control details, the application gets the account assigned to the Receivables
context of the current book.
Add a GL Control Type Context

Define account contexts on each GL control type. To use a new AR invoice debit account, first add a new context
to the AR Account GL control type.
Navigate to GL Control Type Maintenance.
Menu Path: Financial Management > General Ledger > Setup > GL Control Type
1. In the Type field, enter AR Account and press Tab.
2. From the New menu, select New Account.

The Account Context > Detail sheet displays.
3. In the Context field, enter XXX AR Account (where XXX are your initials).
4. In the Book field, select Main Book.
5. Click Save and exit GL Control Type Maintenance.
Review Company Default GL Controls

The Receivables account for the posting process is taken from the company's AR Account GL control. This
workshop task demonstrates how to locate the details of the company's default AR Account GL control.
Navigate to Company Configuration.
Menu Path: System Setup > Company/Site Maintenance > Company Maintenance
1. Navigate to the Modules > All Modules > GL Control > List sheet.
Epicor ERP | 10.0.700.2 51

2. Review and record the default company GL Control Code for the AR Account GL Control Type
________________________.
3. Exit the Company Configuration.
Assign an Account to a GL Control Context

This task demonstrates how to assign an account to the newly created GL control context.
Navigate to GL Control Maintenance.
Menu Path: Financial Management > General Ledger > Setup > GL Control Code
1. In the Type field, select AR Account.
2. In the GL Control field, enter Default and press Tab.
3. In the tree view, navigate to GL Controls > Epic06 - Company Defaults > Account Context > Main
Book > Receivables.
4. Navigate to the Account > List sheet.
5. View the account details for the Receivables context.

The account details are those used to generate the first invoice transaction line for sales order 5120.
6. In the tree view, navigate to and select GL Controls > EPIC06 - Company Defaults > Account Context
> Main Book > XXX AR Account (where XXX are your initials).
7. In the Account field, search for and select 1100-02-00 (Accounts Receivable - EVAN - CORP).
8. Click Save.

If a prompt window displays, click No.
Add a Revision
When an account context is added to a GL control, you must manually update the posting rule. You cannot
modify revisions with an Active or Blocked status so you must add a new revision.

2. Verify the Create new revision by copying existing revision is selected.
3. In the SourceRevision field, verify XXXOP (Active) is selected (where XXX are your initials).
4. Click OK.
After a few moments, the Revisions > Revision Detail sheet displays.
52 Epicor ERP | 10.0.700.2

6. In the Revision ID field, enter XXXGL (where XXX are your initials).
7. Verify the Manually review all transactions check box is selected.
8. Click Save.
Update the Rule

Earlier in the workshop, we discovered that the AR invoice for sales order 5120 uses the XXX_Post to AR (where
XXX are your initials) posting rule, and the AR Account GL control is taken from the company default parameters.
We added a new context to the AR Account GL control type and assigned an account to the new context in the
company default AR Account GL control.
This task demonstrates how to change the context the posting process uses in the posting rules.
1. In the tree view, navigate to and select AR Invoice > Revision: XXXGL - Draft > Rules > Book:Main
Book > Posting Rules > XXX_Post to AR.
In the revision and rule titles, XXX are your initials.
This rule was used to create the first transaction line for the AR invoice amount posted for sales order 5120.
3. In the Summary section, click the DebitAccount = Get Account From AR Invoice - Company Parameters
- AR Account GL Control For Current Book AND Receivables Context line.
4. In the formula field, click Receivables and select Values > XXX AR Account (where XXX are your initials).
If you cannot access the posting rule operation formula field, click the area between the two options fields
and move the field separator to the left.
5. Click Save.
3. Wait until the Status field disables and Active displays.
4. Click Save.
Enter an AR Invoice
Epicor ERP | 10.0.700.2 53



7. Click Save.

Review the Result

When the AR invoice posts using the new revision, the new account should be used for transaction line 1.

2. In the Group ID field, enter XXXGroup (where XXX are your initials).
3. Click Search.
4. Double-click the search record line to select it.
5. In the tree view, expand NNN > Main Book > YYY AR Invoice > Transaction Lines > Records: All > 1
(where NNN is the Review Journal code and YYY is the AR Invoice reference number).
6. Note the Transaction Line 1 details.

Booking Rule Reference
______________________________________________________
GL Account and account Description
______________________________________________________
7. Compare the transaction line 1 details with the details you recorded for the same transaction line entered
in the Workshop - Add a Posting Rule.
The new account context was debited but the Booking Rule Reference remained the same.
54 Epicor ERP | 10.0.700.2


The transaction is posted to the general ledger now.
Multiple Books
A general ledger book provides a consistent view of the financials within a specific company. Use multiple books
for financial reporting and analysis of the same business transactions in a variety of ways, including different
charts of accounts by book, different reporting currencies, different methods of accounting, and multiple fiscal
calendars.
When configured to do so, the posting engine can generate GL transactions in each book for each input business
transaction. The GL transaction details depend on the different charts of accounts, currencies, methods of
accounting, and calendars defined for each receiving book.
GL transactions generate from a single business transaction and each one represents a different view of that
business transaction. Each GL transaction has a reference to the original business transaction as well as the
resulting GL transactions in other books.
Important Use of multiple books in a company requires posting engine revisions. You can manually enter
a revision on each GL transaction type to which you want multi-book postings. This action requires account
mapping or the entry of GL controls for each book you add. Another option you have is in Book
Maintenance. There, you can set up GL transaction mapping from your source book to a secondary book
for multiple GL transaction types at the same time.
Examples of ways to modify and create GL transactions for multiple books:

• Apply Chart of Accounts (COA) mapping to the GL transaction type: A mapped COA uses the posting
hierarchy from the original COA's posting rules. You can use COA mapping to modify the posting process
by making small changes to the map to reflect most posting process differences between receiving books.
Mapping provides you with a better alternative for designing posting rules for simple cases.
• Apply posting rules to the additional book: You can revise the posting codes, amounts, accounts, functions,
posting rules, and other items the posting process uses for a specific GL transaction type within GL Transaction
Type Maintenance. It is common to copy rules from the main book and then adjust as necessary. Using this
method, you must also set up the required GL controls for each book before you can post transactions that
relate to the revised GL transaction type.
If neither posting rules or mapping is defined for a secondary book, automatic transactions will never be created
against that book.
Important The GL multi-book transaction type (MultiGLJrn) includes the standard default set of posting
rules for a single book. The single book is required to be linked to the master chart of accounts (COA) in
order for the rules to work correctly. You can then use this default set of posting rules as a starting point
to build on the rules for your book or for the COA mapping of other books.
For a sample rule, review the custom MultiGLJrn GL transaction type in the Demonstration Database's
Epicor Education company.
Epicor ERP | 10.0.700.2 55

Book Maintenance
Book Maintenance defines the fiscal books a specific company uses. A book defines the currency, fiscal calendar,
chart of accounts, and Retained Earnings account used to generate its financial statements.
A company can use multiple books to display the same financial information in multiple ways. When you implement
the Epicor application, carefully consider the role each book plays in the financial management and reporting
within a specific company. When a transaction is entered, its amounts can be applied to multiple books, reflecting
the purpose for each book.
Each book can also have its own set of validation rules. These rules define error handling for journals posted to
a specific book. By default, books ignore most posting errors. You can change the defaults so the book blocks
and logs errors as needed.
Books are useful for recording transactions so they match the financial legal requirements for a specific country.
Use Chart of Accounts Structure Maintenance to create a chart of accounts (COA) which matches the structure
your country requires. You can use one book to post transactions in a specific currency for reporting, and then
use another book for posting the same transactions in the base currency the company uses.
Example Use the Modified Accelerated Cost Recovery System (MACRS) to depreciate a physical asset
for tax reporting. For financial reporting, the same asset is depreciated using straight-line depreciation.
Each book displays its own depreciation results.
Example Leverage multiple books so your companies can value items differently in financial and statutory
reports. An insurance company might use Generally Accepted Accounting Principles (GAAP) to value
investments and other items for one report and use National Association of Insurance Commissioners
guidelines for another book. State or provincial regulations can also impact reporting, so you may need to
implement additional books.
Use Book Maintenance to define the following:

• Book Type - Books can record financial transactions or consolidate to other books. Standard books record
the financial activity of the company. Consolidation books mediate the transfer of consolidation journals
between two standard books.
• Chart of Accounts (COA) - Each book can have a different COA, or several books can share the same COA.
The COA defines valid general ledger accounts, available dynamic segments, and balance maintenance for
segments other than the natural account. (The natural account maintains continuous balances.) The book
also determines the retained earnings account.
• Fiscal Calendar - The fiscal calendar determines valid apply dates for each business transaction. The Epicor
application maintains periodic balances for segments based on the fiscal calendar.
• Book Currency - The book currency can be used on financial reports and in consolidations. Journal amounts
post in the currency defined on the book. Books can store journals in additional transaction currencies, but
will only post in the specified book currency.
• Error Handling for Journals - Use the Validations sheet to ensure the transactions are valid. For example,
a validation rule can alert you when the Apply Date for a transaction falls within a closed fiscal period. When
the posting process runs, the Epicor application blocks posting of invalid journals and continues to process
the remaining journals in the batch. Error transactions display in the Review Journal.
• Rounding Tolerance Criteria - For each book, you can specify rounding tolerance criteria as well as an
account to which transactions will post currency differences.
• GL Transaction Mapping - Set up GL transaction mapping from your source (Main) book to a secondary
book. You determine the COA map and transactional currency to use as well as determine which GL transaction
types are affected by this revision.
You can modify a book's details (description, type, COA, calendar, currency) until a journal posts to its COA.
Once a posting process runs through the book, you can only change the book description.
56 Epicor ERP | 10.0.700.2

Note You can also update the posting rules each book uses to record general ledger transactions. Update
posting rules for each book within GL Transaction Type Maintenance. For information on how to create
and update posting rules, review the Posting Engine Technical Reference Guide in Application Help.
Menu Path
• Financial Management > General Ledger > Setup > Book
• Financial Management > Multi-Site > Setup > Book
Multiple Currencies
The Epicor application uses two types of currencies - transactional and reporting.
Use a Transactional currency to state, print, and record the transaction (sometimes called a business document).
This is the original transaction, or document, currency.
Use a Reporting currency to report and analyze business transactions. The application supports four reporting
currencies. One of these reporting currencies is the book currency. The book currency defines the default
currency used for transactions which post to that book. Use the three other reporting currencies for display on
various financial reports.
Every business transaction sent to the posting engine can have amounts measured in up to the three reporting
currencies and the book currency. Since a book currency is one of the reporting currencies, the posting engine
typically does not perform any currency conversion, and the amount typically uses the default book currency.
The following modules do not measure amounts in all reporting currencies:
• Inventory
• Fixed Assets
• Payroll
For transactions posted from these modules, the posting engine may need to convert amounts to the book
currency. This operation requires that you support currency conversion in posting rules and handle the possible
rounding differences that can occur when totals and individual items convert and round separately.
Rounding Differences
If currency is converted during a posting process, a rounding difference can result in an unbalanced GL transaction.
You can correct unbalanced transactions manually or enable the posting engine to automatically add balancing
lines. To use automatic handling of rounding differences, configure the rounding tolerance criterion and specify
the account to use to post the difference.
Both the tolerance criterion and the account that records rounding difference are defined in Book Maintenance.
When a transaction is unbalanced without a currency conversion, it is due to a logic error or an improper
configuration. If currency is converted, the tolerance criterion is used to decide whether the conversion causes
the difference. The tolerance criterion records if a rounding difference results in an unbalanced transaction and
provides the reason for the difference (for example, logic errors, improper configuration, and currency conversion).
If the rounding difference does not meet the tolerance criteria, the transaction is considered unbalanced and the
posting process fails.
The tolerance criterion defines a maximum amount that can be considered as a rounding difference. The posting
engine uses a debit or credit amount, depending on which value is greater.
Epicor ERP | 10.0.700.2 57

Source Book
Use the Source Book sheet to link general ledger accounts used during the posting process, from a source book
to a secondary book.
On this sheet you can determine the COA map and transactional currency to use as well as determine which GL
transaction types you want to be affected by this revision.
Linking secondary books to your source (Main) book allows you to post transactions to multiple books automatically
without having to manually modify posting rules.
Tip If the books you are linking use the same COA, in the COA Map field select Use Source GL Account.
This tells the posting engine to post transactions to the same GL account in both books without having to
set up GL controls or mapping for the secondary book. If the books you are linking use different currencies,
in the Transactional Currency field you can select to either post to the second book in the document
currency or in the currency of the source book.
Validations
The Validations sheet defines error handling for journals posted to a specific book. By default, books ignore
most posting errors. You can change the defaults, so the book blocks and logs errors.
Define validation rules at the book level; because of this feature, you control how issues are handled within a
specific book.
The Epicor application handles invalid journals through one of the following ways:
• Error - This blocks posting of the journal. You can view the journal in the Review Journal.
• Warning - A warning entry displays in the error log, but the journal posts to the general ledger.
• Ignore - No entry displays in the error log, and the journal posts to the general ledger. This method is the
default setting for most posting errors.
• Autocorrect - The Epicor application uses a pre-defined process to correct the error. For example, for a journal
posted to a closed period, the autocorrect process changes the apply date to the open period.
• Warning and Autocorrect - This logs a warning in the Review Journal and automatically corrects the journal.
The following table lists posting errors for existing autocorrect options and describes how the Epicor application
handles each defined error.
Error Autocorrection
The Segment is defined as 'not used' but segment This removes the unused segment and occurs when Account
value is specified (depends on natural account). Segment Values blocks use of the segment with a particular
natural account.
The Closing Period is specified but does not exist. This finds the open period for the book and posts the journal
to that period.
The Apply Date is earlier than the Earliest Apply This changes the apply date of the journal to the first day of
Date. the first open period.
The Fiscal Period is closed. This changes the apply date of the journal to the first day of
the first open period.
The self balancing segment does not balance. This runs the self-balancing process.
58 Epicor ERP | 10.0.700.2

Note You can use the Business Process Management module to define additional validations.
Detail
In GL Transaction Type Maintenance, use the Book > Detail sheet to determine how transactions post to a book.
When you select a book on this sheet, you can define its rules. All posting rules, functions, and variables defined
for a single book are a rule set which generates a complete journal for the book.
The Ruleset Version is incremented each time a change is made in any underlying rule or function. The Package
field is the identifier of the assigned rules package (for example, Standard, Extended, or Russia) and is used to
automatically upgrade rule sets in packages that Epicor supports.
The following are some of the book options you can define:
• Determine whether journals are summarized by account when they post to the book. Summarize posted
details to reduce how many records are stored in the database.
• Designate whether mapped segments populate book accounts. Chart of Accounts Mapping defines maps
between specific chart of accounts (COA) segments. A map transfers journal details from one book to the
current book. Segment maps reduce the need to define the same posting rules in multiple maps. The application
also converts the currency of the journal when the currencies of the two books are different.
• Define functions that the posting rules reference in the book's rule set. Reusable functions reduce the time
needed to modify the posting elements and rules. For example, the book might use a COA with a mandatory
division segment. Define a reusable function that obtains a posting code value used to look up and return
the segment value.
• Define variables that supply values to the book's posting rules. The posting rules use variables to populate
fields in a business transaction. You can create variables that use any of the data types the posting process
allows. You can use a custom variable to store an intermediate value in order to calculate a field in a new or
modified posting rule.
Tip The document template for the GL transaction type can hold predefined and custom variables. The
posting process controlled by the transaction type uses the pre-defined variables. You cannot delete or
modify these variables.
Chart of Account Structure Maintenance
Chart of Account Structure Maintenance defines the segment structure and characteristics for each Chart of
Accounts (COA) you use within the current company. The application uses one or multiple charts of accounts to
control account entry.
Each company book must have a COA. In a multi-company environment, you typically need two or more charts
of accounts in each company, a master COA and a consolidation COA. Books can be assigned different COAs
or several books can share the same COA. When a book links with a COA, you can use the COA to post journals.
Use GL Control Maintenance to specify the journals and accounts used to post transactions within the COA.
Indicate which COA is the Master; a master COA contains the primary list of accounts.
Example Government regulations require reports to use an account structure different from the one you
use for corporate reporting. In this situation, define two books. One book uses a COA for government
reporting; the other uses a COA for corporate reporting. In another scenario, the COAs which the company's
subsidiaries use can supply values to a management COA that contains a limited number of accounts.
In Chart of Accounts Maintenance, you must indicate which COA is the Master; a master COA contains the
primary list of accounts. Your master COA is typically assigned to your company's Main Book.
Epicor ERP | 10.0.700.2 59

When you implement financials in the Epicor application, carefully consider the role each COA and book you
create will play in your company's financial management. You can create as complex an account structure as
you need for each COA. Each GL account can have up to 20 definable account segments. Each segment can be
up to 50 characters in length, and you can define a number of values, such as Effective Date and Normal Balance,
for each segment. The maximum length for an account is 200 characters, including delimiters.
COA Segments can be natural, controlled, dynamic, or optional for data entry. They can display in any order and
that order can be changed at any time (Run the Rebuild Display GL Account process to update the display
throughout the application).
A natural account segment defines the chart segment used with the account. The first segment you save on a
COA automatically saves as its natural account. When a segment is defined as a natural account, the application
zeros balances in income statement accounts and maintains balances for balance sheet accounts. If a segment
is a natural account, the Natural Account indicator is active on the Detail sheet. While you indicate where the
natural account segment is located in the account structure in this program, use Account Segment Values
Maintenance to define other natural account options.
Controlled segments record the primary financial history of the company while dynamic segments record temporary,
unique business activity. Link, or reference, dynamic segments to a business entity, which is a table that records
data placed against customer, supplier, project, part, and other entities.
Once you start to use a COA, you can no longer add a controlled segment to it but you can always add dynamic
segments to a COA in use.
Tip Use Chart of Accounts Structure Maintenance to design the primary account structure for each COA.
To define the specific values each segment uses - such as category, normal balance, and natural account
options - use Account Segment Values Maintenance. To indicate a segment is self-balancing, use
Self-Balancing Segment Maintenance. Generate specific account combinations within General Ledger
Account Maintenance.
Menu Path
• Financial Management > Accounts Payable > Setup > Chart of Accounts
• Financial Management > Accounts Receivable > Setup > Chart of Accounts
• Financial Management > General Ledger > Setup > Chart of Accounts
• Financial Management > Multi-Site > Setup > Chart of Accounts
• Financial Management > Payroll > Setup > Chart of Accounts
• Sales Management > Order Management > Setup > Chart of Accounts
For CRM users, the Main Menu appears as:
• Customer Relationship Management > Order Management > Setup > Chart of Accounts
Chart of Account Structure Maintenance - Program Features - Segments
Chart of Account Structure Maintenance defines chart of accounts (COA) segments and their characteristics.
You can define where COA segments obtain their values. The Epicor application always validates controlled
segments posted to the COA against values defined as valid in general ledger programs. Values defined for
controlled segments are available in fields used for general ledger account entry. Dynamic segments set segment
values based on values in posted transactions or on user input. The Epicor application never validates a combination
of dynamic segments.
Example If a COA has three controlled and two dynamic segments, any account code made up from the
five segments is valid if the combination of three controlled segments of this account is valid.
60 Epicor ERP | 10.0.700.2

A dynamic segment can link to a business entity. A business entity is a database table which contains transaction
information. The Epicor application installs with Customer, Supplier, Project, Part, and other business entities.
Example If a COA has Customer as a dynamic segment, this segment can link to the Customer business
entity and the Epicor application automatically creates a new segment when a new customer is added.
You can define whether these segments are required in COA accounts. Specify a controlled segment as required
or optional in Chart of Account Structure Maintenance. This setting applies to all accounts entered against the
COA. You can also use other general ledger programs to define segment requirements based on natural account
values or, in the case of reference-type segments, account masks.
You can also indicate each segment length and whether they can contain just letters or both letters and numbers.
Lastly, you can specify how each segment maintains balances.
Example You use a required controlled segment to define the company's departments. Values for each
department are defined in Account Segment Values. Then, you define valid combinations of the
department segment and other controlled segments in General Ledger Account Maintenance.
The Epicor application designates the COA segment as the natural account segment. This segment holds balances
that appear on financial statements. The application defines most of the segment characteristics. Define natural
account values in Account Segment Values. In that program, you can define revaluation settings and segment
requirements for each account.
The Epicor application uses posting codes, posting rules, and user input to set dynamic segment values. Methods
of setting values include:
• Accounting Rules - Dynamic segments without a business entity use lookup tables and posting rules to set
a segment value based on the values in a posted transaction. Account Segment Values define the values
which populate the segment. These values are selected when a transaction posts.
• Business Entity IDs - These identifiers are for the Customer, Supplier, Project, Part, or other business entities.
This segment type can define subsidiary ledgers for accounts receivable and accounts payable control accounts.
Account segments can reference the same business entities that GL control types use. A GL control based on
a type can expose the dynamic segment to the posting process for the business entity. As a result, the posting
rules can set the segment value.
• Reference-Type Segment - These segments classify campaigns, projects, and other entities with a fixed life.
Use GL COA Reference Type to define reference types and the accounts with which they are used. Account
Segment Values defines type values. Users determine the value of a reference-type segment when a transaction
posts.
COA segments can contain up to 20 segments, each of which contains up to 50 characters. An account code
can contain up to 200 characters, including separators.
Master Chart of Accounts
The Master Chart of Accounts (COA) defines the general ledger accounts available when you manually enter
general ledger accounts within the current company. Define the Master COA within Company Configuration.
Master COA features include the following:
• Define available values in fields you use to enter general ledger accounts. For example, the Epicor application
limits entries in the GL Account field in AP Adjustment to Master COA accounts. As a result, a Master COA
must define all accounts needed to post from these fields.
• Define the default accounts available when you manually enter journals for multiple books. This multiple book
mode applies to a journal group defined in Journal Entry and results in the use of the Master COA with all
group journals.
• Provide a way to specify the COA to which other GL transaction types post. Optionally, you can limit posting
from AR Invoice, AP Voucher, and other programs to Master COA accounts. The general ledger control
associated with the program sets the limitation.
Epicor ERP | 10.0.700.2 61

• Define the available accounts while you upgrade to the Epicor application. The COA used before the upgrade
populates the general ledger accounts the Master COA uses. When you upgrade, the process creates a Main
Book associated with the Master COA; this maintains default posting processes.
• Determine the COA that displays when general ledger maintenance programs launch. The Master COA
automatically displays within these programs.
Typically, a Master COA maintains a complete set of accounts used to post journals from all programs to the
company's Master Book. Other books use amounts posted to the Master COA. You can map account segments
and define posting rules to transfer amounts between books. Modify posting rules within GL Transaction Type
Maintenance.
Alternatively, you can use the Master COA to capture journals for other books. For example, define two books
with different COAs, neither of which have enough details to derive accounts from each other. The Master COA
combines the COAs from the two books so all accounts are available to both.
Workshop - Create a Chart of Accounts
Create a COA to post an AR invoice against sales order 5120. Enter a COA with the following two controlled
segments and values:
Sales Order 5357.
Segment Value(s)
Chart
1100 - Accounts Receivable
3030 - Retained Earnings
4000 - Sales
4900 - Sales Discounts
Division
01 - South
In a future workshop you will map this COA to the Master COA.
Structure a Chart of Accounts

Navigate to Chart of Account Structure Maintenance.
Menu Path: Financial Management > General Ledger > Setup > Chart of Accounts
1. From the New menu, select New COA.
2. In the Chart of Account field, enter XXXMap (where XXX are your initials).
3. In the Description field, enter COA for Mapping.
4. In the Separator Character field, enter a hyphen (-).
5. Select the Create Default Categories check box.
6. Click Save.
62 Epicor ERP | 10.0.700.2

Add COA Controlled Segments
1. From the New menu, select New COA Segment.
2. On the Detail sheet, enter the following:
Field Data
Name Chart
Abbreviation Chart
Maximum Length 4
Minimum Length 4
3. Click Save.
5. In the Detail sheet, enter the following:
Field Data
Name Division
Abbreviation Div
Maximum Length 2
Minimum Length 2
Entry Control Mandatory
6. Click Save and exit Chart of Account Structure Maintenance.
Add Chart Segment Values

Navigate to Account Segment Values.
Menu Path: Financial Management > General Ledger > Setup > Account Segment Values
1. In the Chart of Account field, select COA for Mapping.
2. Verify the Segment field displays Chart.
3. From the New menu, select New Value.
4. Enter the following information:
Field Data
Segment Values 1100
Name Accounts Receivable
Abbreviation AR
Epicor ERP | 10.0.700.2 63

Field Data
Category CURRENT ASSETS
5. Click Save.
6. Repeat steps 3-5 to add additional segment values.

In place of the data from step 4, use the following information:
Segment Value Name Abbreviation Category

3030 Retained Earnings RET EQUITY
4000 Sales SALE SALES/REVENUE
4900 Sales Discounts DISC SALES/REVENUE
7. Click Save.
Add a Division Segment Value
1. In the Segment field, select Division.
Field Data
Segment Values 01
Name South
Abbreviation S
4. Click Save and exit Account Segment Values.
Enter GL Accounts
Navigate to General Ledger Account Maintenance.
Menu Path: Financial Management > General Ledger > Setup > General Ledger Account
1. In the Chart of Accounts field, select COA for Mapping.
2. From the Actions menu, select Generate.

The Generate Accounts window displays.
3. In the COA field, search for and select XXXMap (where XXX are your initials).
4. Click the Generate button.

The Generate GL Accounts Process window displays.
64 Epicor ERP | 10.0.700.2

5. Click Submit.
6. Close the Generate GL Accounts Process window and exit General Ledger Account Maintenance.
Chart of Accounts Mapping
Use Chart of Accounts Mapping to define maps used to transfer journals between different charts of accounts.
Mapping transforms a portion of one chart of accounts (COA) to a portion of another and eliminates the need
to redefine the posting rules that create journals. You can handle most posting process modifications through
COA mapping. Typically, you create COA maps instead of modifying specific posting rules. COA maps can reflect
minor changes you need between different charts of accounts. COA maps are also easier to maintain.
Use COA maps to:
• Create consolidation journals. The consolidation process uses COA maps to link accounts from a source book
to a target book. Consolidation Definition Maintenance specifies the map a consolidation used.
• Automatically transfer posted journals between books. Associate maps with a book and its posting rules
within GL Transaction Type Maintenance. Use the posting engine functionality to map a source COA to
a target COA. You can set up mapping for entire account codes or for individual segments. When the currencies
of the two books are different, the Epicor application also converts the journal currency.
Tip Modify posting rules within GL Transaction Type Maintenance. If your book requires more complex
posting changes, modify the posting rules for each affected GL transaction type. For information on
how to do this, refer to the Posting Engine Technical Reference Guide in the Application Help.
Example The company has a financial and a legal book that use different charts of accounts (COAs). You
want to post the same accounts payable (AP) journals to both COAs. Create a map with the financial book's
COA as the source COA. This map links natural account segment values for AP accounts in the two COAs.
Next, access the GL transaction type used to post AP journals. This GL transaction type contains the posting
rules which create journals for the financial book. Associate the mapping document with the financial
book. As a result, journals that post to AP accounts in the financial book also post to the COA in the legal
book.
Once you create a COA map between books you need to determine which GL transaction types should post to
both of these books. Once you make that decision, add the secondary book with mapping to each individual GL
transaction type by adding a revision in GL Transaction Type Maintenance. You also have the option in Book
Maintenance to link a secondary book to a source book using the COA map you built.
Tip If you plan to update multiple GL transaction types to post to a multiple books, and no rule modifications
are needed, it makes the most sense to link the secondary book to your source (Main) book in Book
Maintenance. Once you establish this link, you can enable as many GL transaction types as you want, all
at the same time. In GL Transaction Type Maintenance, revisions can only be added one transaction type
at a time.
For more information on Chart of Accounts Mapping, refer to the Posting Engine Technical Reference Guide
in the Application Help or the Posting Engine course.
Menu Path
• Financial Management > General Ledger > Setup > Accounting Segment Mapping
• Financial Management > Multi-Site > Setup > Accounting Segment Mapping
Epicor ERP | 10.0.700.2 65

Workshop - Use Mapping
This workshop demonstrates how to use chart of accounts (COA) mapping.

Business Scenario: Your business requires a new book (Map GL Book). The book's COA has two controlled
segments (Chart and Division). Create a new book and map that book's COA to the COA from the Main Book
(Master Chart of Accounts). Enable GL transaction configuration for the AR Invoice transaction type to create
and activate a revision that will automatically post AR invoices to both books.
Based on the changes made in previous workshops, the current posting of an AR invoice for sales order 5120 to
the Main Book features the following transaction line details:
GL Account GL Account Description

Transaction Type
Line
1 1100-02-00- Accounts Receivable - EVAN - CORP Debit

2 4910-00-00- Sales Discounts Default- CHIG - CORP Debit
3 4010-00-00- Sales Default - CHIG - CORP Credit
The Main Book uses the Master COA which has three controlled segments: Chart, Division, and Department. For
the AR invoice transaction, the Chart segment has three values: 1100, 4910, and 4010. The Division segment
has two values: 00 and 02, and the Department segment has one value: 00.
As a reminder, the Map GL Book has two controlled segments: Chart and Division. The Chart segment has four
values: 1100, 3030, 4900, and 4000. The Division segment has one value: 01.
Segment Value(s)
Chart
1100 - Accounts Receivable
3030 - Retained Earnings
4000 - Sales
4900 - Sales Discounts
Division
01 - South
Add COA Mapping

Map the Master Chart of Accounts to the COA created in the prior workshop.
Navigate to Chart of Accounts Mapping.
Menu Path: Financial Management > General Ledger > Setup > Accounting Segment Mapping
1. From the New menu, select New Chart Of Accounts Map.
2. In the Chart of Account Map field, enter XXX_Map (where XXX are your initials).
Field Data
Source Chart of Account Master Chart of Accounts
66 Epicor ERP | 10.0.700.2

Field Data
Target Chart of Account COA for Mapping
Map Type GL Account Map
4. Click Save.
Add GL Account Mapping
1. From the New menu, select New GLAccount Mapping.

The COA Mapping > Account sheet displays.
Field Data
Source GL Account 1100-02-00
Target GL Account 1100-01
3. Click Save.
Field Data
6. Click Save.
Field Data
9. Click Save.
Epicor ERP | 10.0.700.2 67

Field Data
12. Click Save and exit Chart of Accounts Mapping.
Add a Book
Navigate to Book Maintenance.
Menu Path: Financial Management > General Ledger > Setup > Book
1. From the New menu, select New Book.
2. In the Book fields, enter XXX (where XXX are your initials) and GL Mapping.
3. In the Chart of Account field, select COA for Mapping.
4. In the Calendar field, select Main Fiscal Calendar.
5. Navigate to the Retained Earnings sheet.
6. In the Standard Account field, enter 3030-01 and press Tab.
7. Click Save.
Link to Source Book with Mapping
1. From the New menu, select New Link to Source Book.

The Posting > Source Book > Detail sheet displays.
2. In the Map GL Transaction From Book field, select Main Book.
3. In the Use COA Map field, select XXX_Map (where XXX are your initials).
4. Click Save.
Enable GL Transaction Configuration
1. In the GL Transaction Types grid, use the scroll bar to locate the AR Invoice transaction type row.
2. On the AR Invoice row, select the EnableMapping check box.
3. Click Update Transaction Types.
4. Click Save.
5. Exit Book Maintenance.
68 Epicor ERP | 10.0.700.2

Review the Active Revision

1. From the tree view, select the active revision.
2. Expand the revision's Rules node.

Both the Main Book and your new book display.
3. Select Book:GL Mapping.

The Revisions > Book > Detail sheet displays.
4. Review the Mapping details.
7. Click Save.
Enter an AR Invoice
Navigate to AR Invoice Entry


7. Click Save.

Epicor ERP | 10.0.700.2 69

Review the Result


2. In the Group ID field, enter XXXGroup (where XXX are your initials).
3. Click Search.
If no records are available for selection, review the System Monitor for Active Tasks. (For information on
how to review the System Monitor, refer to the Application Help). The AR invoice post may take longer to
process this time because of the revised posting rules. Once the group posts, navigate back to the Review
Journal and search for the entry.
5. Expand the tree view completely.
6. Compare the transaction line details for both books (GL Mapping and Main Book).
To view the transaction line details, in the tree view, click the transaction line number.

The transactions are now posted to both general ledger books.
Business Activity Queries in Posting Rules
There are times when companies require additional reference data in GL transactions but the data is not available
to add to the posting rules unless it is first retrieved with a business activity query (BAQ).
Pull detailed data into a revision by linking a BAQ to an incoming document template. The revision uses selection
criteria defined for a posting rule to obtain data pulled in by the BAQ. The interface can return a value from a
single field or a calculated sum of fields.
Tip Use BAQs to retrieve related data for use in a posting rule only when necessary. First, check to see if
the data you need is available in an existing posting code. If it is not available in an existing posting code,
but it relates to an existing posting entity, try adding a posting code to the posting entity.
Important Extensive use of BAQs can significantly slow the posting process.
Workshop - Add a Query to a Posting Rule
This workshop demonstrates how to use a business activity query (BAQ) with a posting rule to extend the
information available when a transaction posts. In this case, your business requires additional reference data in
70 Epicor ERP | 10.0.700.2

the GL transaction of an RMA credit memo and the data is not available to be added to the posting codes unless
it is first retrieved with a BAQ.
Note BAQ creation is beyond the scope of this course. This workshop uses a custom BAQ that already
exists in the Education Database. The BAQ used has a Specified Parameter Selection Criteria to enable
its use in a posting rule.
In this workshop, the BAQ ties together the RMA number/line, the associated credit memo number/line,
and the reason code the RMA uses.
This workshop also demonstrates how to store data in a GL Transaction User Defined Field (UD field). To
accomplish this, you will add a UD column and regenerate the data model. Note that these tasks are
typically done by a system administrator.
Create the User-Defined Table

Navigate to Extended User Defined Table Maintenance.
Menu Path: System Setup > System Maintenance > Extended UD Table Maintenance
1. Click New Table.

The Table Search window displays.
2. Click Search and find and select the GLJrnDtl table in order to customize it.
Tip To make it easier to find the table you need, enter a value in the Starting At field.
3. Click OK.
4. Notice the Table Name field automatically displays the name of the database table you selected, adding a
“_UD” suffix to the end of this table.
5. Enter GLJrnDtl_UD in the Description field.
6. The System Code field identifies which Epicor application contains the extended user-defined table. Typically
ERP will appear in this field.
7. Click Save.
Add Custom Columns

Add custom columns to the user-defined table.
1. Click New Column.

The Column > Detail sheet displays.
2. From the tree view, select the 4th column.
3. From the Column > Detail sheet, enter RMAReason in the Column name field.
The system assigns a _c suffix to the name.
4. Enter RMA Reason in the Description field.
Epicor ERP | 10.0.700.2 71

5. Accept the defaults for Data type and Format.
6. Click Save.
Synchronize Table
To complete this user-defined table, you synchronize it. This formats the table so it can be linked to the database.
Note this process does not make the table available for display; you need to update the data model to finish
incorporating this user-defined table in your database.
1. Click on the Actions menu.
2. Select the Sync Current Table to DB option to synchronize the active table.
Tip To synchronize all the tables loaded into Extended User Defined Table Maintenance, select
the Sync all tables to DB option.
3. Click OK to the message that displays saying the table was synchronized to the database.
4. From the Table sheet, verify GLJrnDtl_UD is selected and that the indicator says Table in sync.
5. Minimize User-Defined Table Maintenance.
You are now ready to update the database to include this new table.
Regenerate Data Model

To finish adding the user-defined table, the data model for the Epicor database needs to be regenerated. You
or your system administrator runs this task on the server that contains your database. You regenerate the data
model through the Epicor Administration Console.
1. On your server, press <Windows> + F to display the Search bar.
2. Click on the Apps button.

The Apps screen displays.
3. Locate the Epicor Software section on this screen and click the Epicor Administration Console icon.
4. Expand the Database Server Management node and the XXX database server node (where XXX is the
name of your database server) that contains the database you need to update.
5. Select the database icon.

The properties for the database displays in the center pane.
6. From the Actions pane, click the Regenerate Data Model button.
The Generate Data Model window displays.
7. Verify the Deployment folder field displays the root path location for the server. For example:
C:\inetpub\wwwroot\EpicorERP10
8. Click Generate.
The data model generates, adding the extended user-defined table to the database. Now that the data model
is regenerated, Epicor users can view and enter data in the extended user-defined table.
72 Epicor ERP | 10.0.700.2

To complete the functionality, the latest data model must be pulled from the database and copied to the local
app server by restarting IIS. Launch the Command Prompt window, enter IISRESET and press <Enter>. After IIS
stops and restarts, close the Command Prompt window.
Maximize Extended UD Table Maintenance and click refresh. Once you verify that the Data Model in sync status
displays, exit the program.
Add a Revision

2. Verify the Create new revision by copying existing revision is selected.
3. In the Source Revision field, select Base Std (Blocked).
4. Click OK.
6. In the Revision ID field, enter XXXBAQ (where XXX are your initials).
7. Click Save.
Add a Query and Criteria Parameters
1. From the tree view, navigate to Revision: XXXBAQ - Draft > AR Invoice > Line > Posting Codes.
In the Revision ID, XXX represents your initials.
2. From the New menu, select New Query.

Navigate to the Revisions > Incoming Document Line > BAQ > Detail sheet.
3. In the BAQ field, search for and select EPIC06-RMA_RC.
4. In the BAQ Param List grid, for each line, click Please link BAQ parameter with ABT Field and select
the following parameters:
BAQ Param VBDBAQParam

@InvNum AR Invoice > Posting Codes > Details > Invoice Number
@InvLine AR Invoice > Line > Posting Codes > Details > Line Number
In this step you are telling the application the BAQ specified parameter selection criteria at which the rule
should look.
5. Click Save.
Epicor ERP | 10.0.700.2 73

Add a Posting Entity

The entity you add holds a posting code collection and provides default settings that will be used to populate
the field we specify on the posting code in the next workshop task, Enter and Apply a Posting Code.
1. From the New menu, select New Post Entity.
2. In the Name field, enter XXX_RMA_Reason (where XXX are your initials).
3. In the Data Source field, select EPIC06-RMA_RC.
4. Click Save.
Enter and Apply a Posting Code

When you enter a new posting code you define the settings that control how the revision retrieves data used for
its posting rules.
1. From the New menu, select New Post Code.

The Revisions > Incoming Document Lines > Entities > Posting Codes > Detail sheet displays.
2. In the Name field, enter XXX_RMA_RC (where XXX are your initials).
3. In the Description field, enter RMA Return Reason Code on Credit Memo.
4. In the available Field field, select Reason Code.
5. Click Save.
6. From the tree view, navigate to Revision: XXXBAQ - Draft > Rules > Book:Main Book > Posting Rules
> Post Extended Price Amount (Credit Memo, Part).
In the Revision ID, XXX represents your initials.
7. In the operation text, select the Transaction Amount = Select Amount From AR Invoice-Line Where
Name = Extended Price AND Currency Type = Transactional line.
8. Right click on the selected line, and select Insert.

A new line displays above the selected line.
9. In the Options section, in the operation option field, select UD Field.
10. Click UD Field and select Characters > RMAReason_c.

UD stands for user defined.
11. In the Formula field, select Value.
12. Click Value and select ABT Field > AR Invoice > Line > Posting Codes > XXX_RMA_Reason >
XXX_RMA_RC (where XXX are your initials).
13. Click Save.
74 Epicor ERP | 10.0.700.2

4. Click Save.
Workshop - Use the Modified Posting Rule
In this workshop, enter and receive a Return Material Authorization (RMA), create and post an RMA credit memo,
and review a general ledger detail query to review the data that generates in the RMAReason_c user defined
field per the posting rule revision activated in the Workshop - Add a Query to a Posting Rule.
Enter and Receive an RMA

Navigate to Return Material Authorization.
Menu Path: Financial Management > Accounts Receivable > General Operations > RMA Processing
1. From the New menu, select New RMA.
2. In the Customer field, enter Addison and press Tab.
3. Click Save.
4. Navigate to the Details > Detail sheet.
6. In the Order/Line/Rel field, enter 5181/1/1.
7. In the Quantity field, enter 12.
8. In the Reason field, select Damaged in Shipment.
9. Click Save.
10. From the New menu, select New Receipt.

The Receipts > Detail sheet displays.
11. Accept all defaults and click Save.
Enter an RMA Credit Memo
1. Navigate to the Summary > Credits sheet.
2. At the bottom of the program window, click the Add Credit Memo button.
AR Invoice Maintenance displays with a credit memo specific to the RMA you previously entered.
Epicor ERP | 10.0.700.2 75

3. In the Site field, select Main.
4. In the Confirm Date field, select today's date.
5. Click Save and review the credit memo details.
6. Note the invoice (credit memo) number. _______________________
7. Exit AR Invoice Maintenance.

In Return Material Authorization, the credit memo displays on the Summary > Credits sheet in the RMA
Credit Requests grid.
8. Click Save and exit Return Material Authorization.
Post the RMA Credit Memo

3. Click Save.
4. From the Actions menu, select Get > RMA and Demand Credits.
The Get Invoices window displays.
5. Click Manual Selection.

The Invoice Browse window displays.
6. Select the credit memo you created in the workshop task, Enter an RMA Credit Memo.
7. Click OK.
A message displays and asks, Are you sure?.
8. To the message, click Yes.

A message displays to tell you how many credit memos were selected.
9. To the message, click OK.

The credit memo displays in the Invoices grid.
10. Review the credit memo details.

Review the Results

Navigate to Invoice Tracker.
76 Epicor ERP | 10.0.700.2

Menu Path: Financial Management > Accounts Receivable > General Operations > Invoice Tracker
1. In the Invoice field, search for and select the credit memo you created in the previous work shop task.
2. Navigate to the GL Transaction sheet.
3. Click the Retrieve button.
4. Scroll all the way to the right and review the RMAReason_c column.
5. The RMAReason_c column for your credit memo displays SDMG,the reason code ID for Damaged in
Shipment.
RMAReason_c is the user defined (UD) field you previously added to the posting rule. The posting code you
previously added directed the Reason Code query field to bring the data into the UD field. The current BAQ
includes a Reason Code column to display how the UD field returned the correct data.
6. Exit AR Invoice Tracker.
Lookup Tables Setup
Lookup Tables Setup provides the means to map database field values to segment or account values. Posting
rules can access Lookup tables to set segment and account values for journal details based on a value in a
transaction which is being posted.
When you use lookup tables, you reduce how many changes you need to make on a posting rule to set segment
and account values.
Example You assign a user-defined property "Color" to each part and need to account for the parts
differently, depending on their color. You can use a lookup table to associate color codes with sales
accounts. You set up an AR Invoice transaction type so that it will receive a color code as a posting code
and use it to retrieve a corresponding GL Account directly from the lookup table.
Once the transaction type and an underlying set of booking rules are set up in this way, the only thing you
need to do to make a system account for a new color is to go to the lookup table and associate the new
color code with an appropriate Sales Account, with no need to re-configure the booking rules themselves.
You can define multiple target values for a source value. The rule parameters define the lookup table columns
you use.
Important If you modify or delete lookup tables, it can cause invalid journals to generate. Ensure the
posting rules which use a lookup table create valid accounts after you change the lookup tables.
Menu Path
• Financial Management > General Ledger > Setup > Lookup Table
Epicor ERP | 10.0.700.2 77

Workshop - Use Lookup Tables
This workshop demonstrates how to use lookup tables.

In this workshop:
• Create a new general ledger book (LT Book) with a chart of accounts that has one controlled segment (Chart)
and two dynamic segments (Customer Group and Product Group).
• Add a lookup table (CG_PG_LT) that maps a combination of the Customer Group and Product Group segments
to the Chart segment.
Note Different Customer Group and Product Group combinations result in posting to different accounts.
• Use the CG_PG_LT lookup table to link the Main Book to the LT Book.
• Add an invoice with two lines that refer to parts with different product groups.
At the end of this workshop, when the transaction is posted to the GL, the transaction lines in the Main Book
should display the same account for the Customer Group and Product Group parts. The transaction lines in the
LT Book should display the different accounts for the Customer Group and Product Group parts.
Add a Chart of Accounts

Add a chart of accounts (COA) for the LT Book.
Navigate to Chart of Account Structure Maintenance.
Menu Path: Financial Management > General Ledger > Setup > Chart of Accounts
1. From the New menu, select New COA.
2. In the Chart of Account field, enter XXXLT (where XXX are your initials).
3. In the Description field, enter COA for LT.
4. In the Separator Character field, enter a hyphen (-).
5. Select the Create Default Categories check box.
6. Click Save.
Add a COA Controlled Segment

Add one controlled segment - Chart.
Field Data
Name Chart
Abbreviation Chart
Maximum Length 4
Minimum Length 4
78 Epicor ERP | 10.0.700.2

3. Click Save.
Add COA Dynamic Segments

Add two dynamic segments - Customer Group and Product Group.
Field Data
Name Customer Group
Abbreviation Cust Grp
Maximum Length 10
Minimum Length 0
3. Select the Dynamic check box.
4. Click Save.
Field Data
Name Product Group
Abbreviation Prod Grp
Maximum Length 10
Minimum Length 0
7. Select the Dynamic check box.
8. Click Save and exit Chart of Account Structure Maintenance.
Add Chart Segment Values

Navigate to Account Segment Values.
Menu Path: Financial Management > General Ledger > Setup > Account Segment Values
1. In the Chart of Account field, select COA for LT.

The Segment field automatically displays Chart.
Epicor ERP | 10.0.700.2 79

Field Data
Segment Values 4010
Name Sales for Metal (DOM)
Abbreviation SMD
Category SALES/REVENUE
4. Click Save.
5. Repeat the steps above to add other segment values.

Enter the following information:
Segment Values Name Abbreviation Category

4020 Sales for Plastic (DOM) SPD SALES/REVENUE
4030 Sales for Metal (EU) SME SALES/REVENUE
4040 Sales for Plastic (EU) SPE SALES/REVENUE
3000 Retained Earnings RE EQUITY
1000 Accounts Receivable AR CURRENT ASSETS
6. Click Save.
Add Customer Group Segment Values

Add two Customer Group segment values - DOM for domestic customers and EU for EU customers.
1. In the Segment field, select Customer Group.
Field Data
Segment Values DOM
Name Domestic Customers
Abbreviation DOM
4. Click Save.
Field Data
Segment Values EU
80 Epicor ERP | 10.0.700.2

Field Data
Name EU Customers
Abbreviation EU
7. Click Save.
Add Product Group Segment Values

Add two Product Group segment values - Metal and Plastic.
1. In the Segment field, select Product Group.
Field Data
Segment Values Metal
Name Metal
Abbreviation Mtl
4. Click Save.
Field Data
Segment Values Plastic
Name Plastic
Abbreviation Plt
7. Click Save and exit Account Segment Values.
Enter GL Accounts
When the segment values for the chart of accounts (COA) are added, enter general ledger (GL) accounts. The
Epicor application generates GL accounts based on the available COA segment settings and COA segment values.
Navigate to General Ledger Account Maintenance.
Menu Path: Financial Management > General Ledger > Setup > General Ledger Account
1. In the Chart of Accounts field, select COA for LT.
2. From the Actions menu, select Generate.

The Generate Accounts window displays.
Epicor ERP | 10.0.700.2 81

3. In the COA field, search for and select XXXLT (where XXX are your initials).
4. Click the Generate button.

The Generate GL Accounts Process window displays.
5. Click Submit.
6. Close the Generate GL Accounts Process window and exit General Ledger Account Maintenance.
Add a GL Book
Navigate to Book Maintenance.
Menu Path: Financial Management > General Ledger > Setup > Book
1. From the New menu, select New Book.
2. In the Book field, enter XXXLT (where XXX are your initials) and LT Book.
3. In the Chart of Account field, select COA for LT.
4. In the Calendar field, select Main Fiscal Calendar.
5. Navigate to the Retained Earnings sheet.
6. In the Standard Account field, enter 3000.
7. Click Save and exit Book Maintenance.
Add Customer Groups

Navigate to Customer Group Maintenance.
Menu Path: Financial Management > Accounts Receivable > Setup > Customer Group
1. Click New.
2. In the Group field, enter DOM.
3. In the Description field, enter Domestic Customers.
4. Click Save.
5. Click New.
6. In the Group field, enter EU.
7. In the Description field, enter EU Customers.
8. Click Save and exit Customer Group Maintenance.
Add Product Groups

Navigate to Product Group Maintenance.
82 Epicor ERP | 10.0.700.2

Menu Path: Financial Management > Accounts Receivable > Setup > Product Group
2. In the Group field, enter Metal.
3. In the Description field, enter Metal.
4. Click Save.
6. In the Group field, enter Plastic.
7. In the Description field, enter Plastic.
8. Click Save and exit Product Group Maintenance.
Set Up Customers
This task demonstrates how to add a customer to an existing customer group.
Navigate to Customer Maintenance.
Menu Path: Financial Management > Accounts Receivable > Setup > Customer
1. In the Customer field, search for and select Addison, INC.
2. Navigate to the Billing > Detail sheet.
3. In the Group field, select Domestic Customers.
4. Click Save.
5. Navigate to the Customer > Detail sheet.
6. In the Customer field, search for and select Berlin Medical Equipment.
7. Navigate to the Billing > Detail sheet.
8. In the Group field, select EU Customers.
9. Click Save and exit Customer Maintenance.
Add a Lookup Table

Add a lookup table that maps a combination of the Customer Group and Product Group segments to the Chart
segment.
Navigate to Lookup Tables Setup.
Menu Path: Financial Management > General Ledger > Setup > Lookup Table
1. From the New menu, select New Lookup Table.
Epicor ERP | 10.0.700.2 83

2. In the Lookup Table field, enter CG_PG_LT.
3. In the Detailed Description field, enter Maps a combination of the Customer Group and Product
Group segments to the Chart segment.
4. Click Save.
Add Source Value Fields

Add source value fields to the lookup table.
1. From the New menu, select New Source Value Field.

The Source Value Fields sheet displays.
Field Data
Field Name CustomerGroup
Detailed Description Customer Group
DB Table CustGrup
DB Field GroupCode
3. Click Save.
4. From the New menu, select New Source Value Field.
Field Data
Field Name ProductGroup
Detailed Description Product Group
DB Table ProdGrup
DB Field ProdCode
6. Click Save.
Add a Target Value Field

Add a target value field to the lookup table.
1. From the New menu, select New Target Value Field.

The Target Value Fields sheet displays.
84 Epicor ERP | 10.0.700.2

Field Data
Field Name TargetChart
Detailed Description Target Chart
Value Type Leave this field blank.
COA Code XXXLT (where XXX are your initials)
Validate Do not select this check box.
Segment Chart
3. Click Save.
Add Lookup Links

Add lookup links to the lookup table.
1. From the New menu, select New Lookup Link.

The Details sheet displays.
Field Data
CustomerGroup DOM
ProductGroup Metal
TargetChart 4010
3. Click Save.
4. Repeat the steps above to add other lookup links.
Field Data 1 Data 2 Data 3

CustomerGroup DOM EU EU
ProductGroup Plastic Metal Plastic
TargetChart 4020 4030 4040
5. Click Save and exit Lookup Tables Setup.
Add a Revision
1. Click Refresh.

Epicor ERP | 10.0.700.2 85

3. Verify the Create new revision by copying existing revision check box is selected.
4. In the Source Revision field, select Base Std (Blocked).
5. Click OK.
7. In the Revision ID field, enter XXXLkup (where XXX are your initials).
9. Click Save.
Add a Book to the Revision
1. Navigate to the Revisions > Book > Detail sheet.
2. Click Add Book.
3. Search for and select the LT Book.
4. Click Save.
Copy Posting Rules

When you add the LT Book, it does not have posting rules. You cannot activate a revision which contains a book
that does not have posting rules. Either create or copy posting rules for the added book. Copy the posting rules
for a faster and easier way to set up a book.
1. In the tree view, navigate to and select AR Invoice > Revision: XXXLkup - Draft > Rules > Book:Main
Book > Posting Rules.
2. From the Actions menu, select CopyRuleSet.
3. In the tree view, navigate to and select AR Invoice > Revision: XXXLkup - Draft > Rules > Book:LT Book
> Posting Rules.
4. From the Actions menu, select Paste Rule.

The default posting rules are copied to the LT Book.
5. Click Save.
Add a Posting Code

The Customer Group field is not predefined in posting codes for the standard revision. The CG_PG_LT lookup
table uses the Customer Group value to select the appropriate Chart segment value. To use the Customer Group
field values in posting rules, add a new posting code.
1. In the tree view, navigate to and select AR Invoice > Revision: XXXLkup - Draft > AR Invoice > Posting
Codes > BillTo Customer.
86 Epicor ERP | 10.0.700.2

2. From the New menu, select New Post Code.

The Revisions > Incoming Document Template > Incoming Document Lines > Entities > Posting
Codes > Detail sheet displays.
3. In the Name and Description fields, enter Customer Group.
4. In the Field field, enter GroupCode.

Note When you start to enter data in the Field field, the Epicor application automatically displays
specific values. If a specific value is correct, click in the field or press Tab to accept it.
5. Click Save.
Add a Posting Rule

Add a posting rule that uses a lookup table reference. The posting rule should have operations for the book
amount, transaction amount, and debit and credit accounts.
1. In the tree view, navigate to and select AR Invoice > Revision: XXXLkup - Draft > Rules > Book:LT Book.

Field Data
Name XXX_Post Using Lookup Table (where XXX are your initials)
Description Post to sales using lookup table.
Outgoing GL Control Type AR Invoice Line
Debit Context Sales
Credit Context Sales
5. In the For Each field, select Line.
6. Click Save.
Add a Book Amount Operation

Copy the book amount operation from the rule that refers to the regular invoice.
> Posting Rules > Post Extended Price Amount (Regular Invoice, Part).
2. Right-click the Book Amount = Select Amount From AR Invoice-Line Where Name = Extended Price
AND Currency = Book Currency line and select Copy.
Epicor ERP | 10.0.700.2 87

> Posting Rules > XXX_Post Using Lookup Table (where XXX are your initials).
4. Right-click in the Summary section and select Add.

A new Please select variable and value or function operation line is added.
5. Right-click the Please select variable and value or function line and select Paste > Above.
6. Click Save.
Add a Transaction Amount Operation

Copy the transaction amount operation from the rule that refers to the regular invoice.
2. Right-click the Transaction Amount = Select Amount From AR Invoice-Line Where Name = Extended
Price AND Currency Type= Transactional line and select Copy.
4. Right-click the Book Amount line and select Paste > Below.
5. Click Save.
Copy and Paste an If Logical Condition for the Credit Account

Copy the If logical condition for the credit account operation from the rule that refers to the regular invoice. If
this logical condition is true, the transaction line posts to the credit account.
2. Right-click the If Book Amount.Value > 0 line and select Copy.
4. Right-click the Transaction Amount line and select Paste > Below.
5. Click Save.
Update the If Logical Operation for the Credit Account

Change the If logical operation for the credit account so it can use the lookup table.
This task demonstrates how to add the following If logical operation for the credit account:
88 Epicor ERP | 10.0.700.2

Credit Account.Chart = Lookup CG_PG_LT For TargetChart Using CustomerGroup = AR Invoice-BillTo

Customer-Customer Group ProductGroup = AR Invoice-Line-Product Group-Code
The Epicor application uses the TargetChart target field value from the CG_PG_LT lookup table to select Chart
segment values. The CustomerGroup source field value is taken from the bill to customer details for the accounts
receivable (AR) invoice. The ProductGroup source field value is taken from the product group details for the AR
invoice line.
1. In the Summary section, click the Credit Account = Temp Account operation line.
2. In the operation option field, click Credit Account and select Chart.
In the Summary section, the formula changes to:
Credit Account.Chart = Temp Account
3. In the formula field, select the Lookup Map Name For Field Using arg1, arg2 ... formula.
4. In the formula field, click Map Name and select CG_PG_LT.

Lookup CG_PG_LT For Field Using CustomerGroup = Value ProductGroup = Value
5. In the formula field, click Field and select TargetChart.

Lookup CG_PG_LT For TargetChart Using CustomerGroup = Value ProductGroup = Value
6. In the formula field, click CustomerGroup = Value and select ABT Field > AR Invoice > Posting Codes
> BillTo Customer > Customer Group.
Lookup CG_PG_LT For TargetChart Using CustomerGroup = AR Invoice-BillTo Customer-Customer
Group ProductGroup = Value
7. In the formula field, click ProductGroup = Value and select ABT Field > AR Invoice > Line > Posting
Codes > Product Group > Code.
Group ProductGroup = AR Invoice-Line-Product Group-Code
Credit Account.Chart = Lookup CG_PG_LT For TargetChart Using CustomerGroup = AR Invoice-BillTo
8. Click Save.
Add an Else Logical Condition for the Debit Account

If the Else logical condition is true, the transaction line posts to the debit account.
1. In the Summary section, click the Please select variable and value or function operation line.
Epicor ERP | 10.0.700.2 89

2. In the Type section (at the bottom of the sheet), select Logical Condition.
3. In the operation option field, select Else.
Define the Else Logical Operation for the Debit Account

This task demonstrates how to add the following Else logical operation for the debit account:
Debit Account.Chart = Lookup CG_PG_LT For TargetChart Using CustomerGroup = AR Invoice-BillTo
The Epicor application uses the TargetChart target field value from the CG_PG_LT lookup table to select Chart
segment values. In this table, the CustomerGroup source field value is taken from the bill to customer details for
the accounts receivable (AR) invoice. The ProductGroup source field value is taken from the product group details
for the AR invoice line.
1. In the Summary section, right-click the Else line and select Add.
4. In the operation option field, select Debit Account.
5. In the operation option field, click Debit Account and select Chart.
6. In the formula field, select the Lookup Map Name For Field Using arg1, arg2 ... formula.
7. In the formula field, click Map Name and select CG_PG_LT.

Lookup CG_PG_LT For Field Using CustomerGroup = Value ProductGroup = Value
8. In the formula field, click Field and select TargetChart.

Lookup CG_PG_LT For TargetChart Using CustomerGroup = Value ProductGroup = Value
9. In the formula field, click CustomerGroup = Value and select ABT Field > AR Invoice > Posting Codes
> BillTo Customer > Customer Group.
Group ProductGroup = Value
10. In the formula field, click ProductGroup = Value and select ABT Field > AR Invoice > Line > Posting
Codes > Product Group > Code.
Group ProductGroup = AR Invoice-Line-Product Group-Code
90 Epicor ERP | 10.0.700.2

Debit Account.Chart = Lookup CG_PG_LT For TargetChart Using CustomerGroup = AR Invoice-BillTo

11. Click Save.
Disable a Posting Rule

Now the revision has two rules to post the extended price amount for a regular invoice and a part. First, disable
the old posting rule.
3. Clear the Is Active check box.
4. Click Save.
4. Click Save.
Enter an AR Invoice
2. In the Group field, enter XXXLkup (where XXX are your initials).
4. In the Sold To Customer field, search for and select Addison, INC.
5. Click Save.
Add AR Invoice Lines

Enter two lines for parts that belong to different product groups. The Plastic and Metal parts are not part records
in the database. These records are automatically created during this task, so you do not need to set them up in
Part Maintenance.
Epicor ERP | 10.0.700.2 91

Field Data
Part/Rev Plastic
Description Plastic
Group Plastic
Quantity 10
Unit Price 10
3. Click Save.
Field Data
Part/Rev Metal
Description Metal
Group Metal
Quantity 5
Unit Price 10
6. Click Save.
Post an AR Invoice

Review the Result


92 Epicor ERP | 10.0.700.2

2. In the Group ID field, enter XXXLkup (where XXX are your initials).
3. Click Search.
5. From the Journal Entry field, note the review journal code ______________.
7. Compare the transaction line details for both books.

To view the transaction line details, use the tree view and click the transaction line number.
The LT Book has two lines. The Plastic and Metal product groups do not share the same Sales account in
this book. The transaction details for the Plastic and Metal parts attempt to post to different accounts but
the LT Book has errors. This course covers this issue later in the Error Handling section.
8. Minimize the Review Journal.
Epicor ERP | 10.0.700.2 93

Posting Process Tracking Posting Engine Course
Posting Process Tracking
Indicators on the source documents and the System Monitor provide tracking for the posting process status.
The posting process can be scheduled. The tracking functionality shows the posting process status (in process or
complete) and the posting process result (if it completes successfully or not).
When pre-post mode is used, the posting process always executes immediately.
When a posting process starts, the business entity in the Epicor application is blocked for any adjustment and
displays that the posting has started.
When the posting process is completed successfully, the entity is marked as posted. To view the status of the
entity, use trackers.
If the posting process fails, all errors and warnings can be viewed in the Review Journal.
If the posting process is cancelled in the Review Journal, the source business entity is marked as unposted and
is available for adjustments.
System Monitor
Use the System Monitor to verify the processes, reports, and other scheduled tasks you have run.
This program interacts with the data by displaying the items scheduled to run within your Epicor application. It
displays only those reports/forms, processes, and other items launched through your client workstation.
Tip The System Monitor automatically activates when you start the Epicor application. You can click this
program's icon on the system tray on the Windows toolbar to display it.
Use the System Monitor to perform the following tasks:

• Monitor - Review the status of the item being run.
• Preview - Click the Print Preview button to preview a report/form on your screen before it prints. This
functionality is only available on the Reports sheet.
• Print - Click the Print button to print a generated report/form. You can also reprint reports/forms. Use this
function to reprint a report (for instance, the Stock Status Report) from a previous date. This functionality is
only available on the Reports sheet.
All sheets in the System Monitor display records that indicate a specific program such as a report, executive query,
or process (for example, Process MRP) is run. The status of the record determines the sheet where each record
displays.
Available sheets:
• Active Tasks - This displays the reports, processes, executive queries, or other items currently running.
• History Tasks - This displays the reports, processes, executive queries, or other tasks run in the past. Records
automatically purge from this sheet when they are 30 or more days old.
• Scheduled Tasks - This displays any reports, processes, executive queries, or other tasks scheduled to run in
the future.
• Reports - This displays all report/form programs you have run. All report programs (running on the appserver)
generate physical files. These files are the data source the System Monitor (running on the client) uses to
94 Epicor ERP | 10.0.700.2

Posting Engine Course Posting Process Tracking
perform the actual printing. The TaskAgent (also running on the appserver) runs a purge of the reports
approximately every 15 minutes. To keep a specific report file available for a longer length of time, use the
Archive Period field on the report/form program. When you enter a value in this field, the TaskAgent does
not purge it until the system clock passes this defined Archive Period value.
Menu Path
• System Setup > System Maintenance > System Monitor
Workshop - Use the System Monitor

In the notification area of the Taskbar (bottom right of your monitor), double-click the blue System Monitor
icon.
1. Navigate to the History Tasks > List sheet.
2. Click the TaskDescription header to sort the records.
3. Select the row for the AR Invoice Post task description with the most recent start time.
4. Navigate to the History Tasks > Detail sheet.
5. Note the Task Error description.
6. Exit the System Monitor.
Error Handling
During the posting process, various issues can occur at different stages. Issues which are not ignored or
automatically corrected produce either warnings or errors.
An error does not stop the process immediately. If an application or user-defined error occurs, the error is logged
for the appropriate GL transaction, which marks this transaction as invalid. As a result, an entry is created in the
Review Journal and the posting process proceeds to the review GL transaction stage. Warnings do not make a
GL transaction invalid.
Application Issues
Application issues result from either invalid, inconsistent data or from improper configuration. The Epicor application
maintains a list of these issues, and each issue is classified as either an error handled in a standard way or a special
issue handled in a predefined way. You can select one of the following predefined options:
• The issue is an error.
• The issue is a warning.
• Automatically correct the issue.
• Ignore the issue.
The majority of application issues are discovered while automatic procedures execute and can be handled differently
in each book.
Epicor ERP | 10.0.700.2 95

User-defined Issues
You can define errors or log warnings in posting rules.
Fatal Errors
Fatal errors are considered unexpected errors, like a hardware failure or a lost connection to the server. Fatal
errors are not classified by the error handling functionality.
Workshop - Handle a Lookup Table Posting Error
This workshop demonstrates how to correct the error that occured when you posted the AR Invoice using the
lookup table.
Review Errors
Maximize the Review Journal.
1. In the tree view, navigate to and select NNN > LT Book > YYY AR Invoice > Errors and Warnings >
Error (where NNN is the Review Journal code and YYY is the AR Invoice reference number).
The Transactions > Error Log sheet displays.
2. Note the error log statement.

Because one line is missing for the LT Book, the transaction does not balance. The error log statement is
Transaction does not balance.
3. In the tree view, navigate to and select NNN > Main Book > YYY AR Invoice > Transaction Lines > 1
(where NNN is the Review Journal code and YYY is the AR Invoice reference number).
The Transactions > Lines > Detail sheet displays.
4. From the Booking Rule Reference field, note the posting rule.
___________________________________________
Because the lookup table does not link to this posting rule and the LT Book does not have any GL controls
set up, the Epicor application cannot select a Receivable account to which this transaction should post. This
results in an unbalanced transaction.
In order to correct this error, first cancel this journal entry and then set GL controls for the AR Account type
in the LT Book. Canceling this journal entry gives you a chance to post this AR invoice again after you update
the LT Book's GL controls.
Another option is to add a new GL transaction type revision and update the Post Invoice Amount to Accounts
Receivables posting rule. Another lookup table (or a more detailed table than the one created in the Workshop
- Use Lookup Tables) that incorporates the AR account must exist in order to use this option.
Cancel a Journal Entry
1. From the Actions menu, select Journal Entry Cancellation.

The Deletion of journal entry information message displays.
2. Click Yes to delete the entry.
96 Epicor ERP | 10.0.700.2

Posting Engine Course Posting Process Tracking
View a Posting Rule

1. In the tree view, navigate to and select AR Invoice > Revision: XXXLkup - Active > Rules > Book:LT
Book > Posting Rules > Post Invoice Amount to Accounts Receivable.
The Epicor application cannot locate a debit account from this posting rule.
2. Note the lines for the debit account.

The order of these lines is changed for a clearer explanation.
If Book Amount.Value > 0
Comment: Regular Invoice
Debit Account = AR Account
This means that for a regular invoice, the application takes the debit account from the AR Account GL
transaction type.
AR Account = Get Account From AR Invoice-BillTo Customer-GL Control For Current Book AND
Receivables
This line means the application takes the AR Account from the GL control assigned to the bill to customer.
The Current Book and Receivables context (account) are the GL control's parameters.
If AR Account is not Valid
AR Account = Get Account From AR Invoice-Company Parameters-AR Account GL Control For
Current Book AND Receivables
The application uses this section of the rule if the GL control assigned to bill to customer is not valid (for
example, one is not entered). This section means the application takes the AR Account from the GL control
assigned to the company parameters when one in not available on the bill to customer. The Current Book
and Receivables context are still the GL control's parameters.
3. Exit GL Transaction Type Maintenance.
Enter a GL Control Context

Navigate to GL Control Maintenance.
Menu Path: Financial Management > General Ledger > Setup > GL Control Code
1. In the Type field, select AR Account.
2. In the GL Control field, search for and select Default.

Default is the GL control set as the company parameter's default AR Account control type. Because the
customer (Addison, INC) invoiced in this workshop does not have a specific GL control set on its record, use
the company default.
Note To verify Addison, INC does not have a specific GL control set up on its record, use the steps
from the Workshop - Revise AR Invoice Posting Rules - Review a Customer GL Control (substitute
Addison, INC for Dalton Manufacturing).
Epicor ERP | 10.0.700.2 97

3. In the tree view, navigate to GL Controls > EPIC06 - Company Defaults > Account Context > LT Book
> Receivables.
The Account > Detail sheet displays.
4. In the Account field, search for and select 1000.
5. Click Save.

If a message box appears, click No.
Post an AR Invoice
1. In the Group field, enter XXXLkup (where XXX are your initials) and press Tab.
The invoice created in the Workshop - Use Lookup Tables displays.

Review the Result


2. In the Group ID field, enter XXXLkup (where XXX are your initials).
3. Click Search.
6. Compare the transaction line details for both books.

To view the transaction line details, in the tree view, click the transaction line number. The transactions are
now valid in both books.

The transactions are now posted to both general ledger books.
98 Epicor ERP | 10.0.700.2

Posting Engine Course Conclusion
Conclusion
Congratulations! You have completed the Posting Engine course.
Epicor ERP | 10.0.700.2 99

Index Posting Engine Course
Index
B chart of accounts mapping 65
book maintenance 56
G
C gl control maintenance 49
gl control type maintenance 49
chart of account structure maintenance 60 gl transaction type maintenance 21
100 Epicor ERP | 10.0.700.2

Additional information is available at the Education and
Documentation areas of the EPICweb Customer Portal. To access
this site, you need a Site ID and an EPICweb account. To create an
account, go to http://support.epicor.com.

Posting Engine PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Posting Engine PDF

Uploaded by

Copyright:

Available Formats

Epicor ERP

Posting Engine Course

Epicor ERP | 10.0.700.2 3

4 Epicor ERP | 10.0.700.2

Chart of Accounts Mapping...........................................................................................................................65

Epicor ERP | 10.0.700.2 5

Copy Posting Rules..........................................................................................................................86

6 Epicor ERP | 10.0.700.2

Posting Engine Course

Epicor ERP | 10.0.700.2 7

Before You Begin

Specific audiences will benefit from this course.

8 Epicor ERP | 10.0.700.2

4. From the Main menu, select the Main site.

Epicor ERP | 10.0.700.2 9

10 Epicor ERP | 10.0.700.2

Daily Posting Engine Processing

Posting Engine Modes

The posting engine process operates in multiple modes.

Epicor ERP | 10.0.700.2 11

Posting Process Output Data

The posting process can output the following:

Business Transaction Documents

GL Transaction Type Maintenance

12 Epicor ERP | 10.0.700.2

Main Goals of the Review Journal

Epicor ERP | 10.0.700.2 13

Review Journal Data Display

14 Epicor ERP | 10.0.700.2

Posting Process Stages

Epicor ERP | 10.0.700.2 15

Stage 1: Generate Business Transactions

16 Epicor ERP | 10.0.700.2

Stage 2: Execute Posting Rules

Epicor ERP | 10.0.700.2 17

Stage 3: Execute Automatic Procedures

The procedures run in the following order:

18 Epicor ERP | 10.0.700.2

Stage 4: Review Transactions

Epicor ERP | 10.0.700.2 19

20 Epicor ERP | 10.0.700.2

Specialized Posting Engine Processing

GL Transaction Type Maintenance

Use this program to do the following:

Epicor ERP | 10.0.700.2 21

22 Epicor ERP | 10.0.700.2

Option to Manually Review Transactions

Upgrades and Revisions

Epicor ERP | 10.0.700.2 23

The Epicor application supports two modes of active revisions.

Workshop - Add a Revision

1. In the Transaction Type field, search for and select AR Invoice.

2. From the New menu, select New Revision.

3. Verify Create new revision by copying existing revision is selected.

4. In the SourceRevision field, select Base Std (Active).

6. In the tree view, select the new revision, namely A - Draft.

9. Minimize GL Transaction Type Maintenance.

24 Epicor ERP | 10.0.700.2

Use GL Transaction Type Maintenance to activate the manual review functionality.

Workshop - Review Transactions in the Review Journal

Activate Manual Posting

2. Select the Manually review all transactions check box.

4. Minimize GL Transaction Type Maintenance.