MA00.1 - Match Table
** Form purpose
Use Match Table (MA00.1) to define a matching table and what match rule groups
will be associated with it. The match table, in conjunction with the match
rules that are assigned to it, determine at what processing level the match
will occur, when the match will be attempted, and the processing rules for the
matching attempt.
** Required fields
At least one match table is required for a company. You can create additional
match tables to override at the vendor level.
For each match table you must define: a unique name for the match table, a
description of the match table, a match table type, and at least one rule
group.
Choose the Rule Groups button to access MA00.4 (Match Rule Groups). Use MA00.4
to define match rule groups.
Updated Files
MAMATCHTBL -
Referenced Files
MAMTCHRULE -
MA00.2 - Match Elements
** Form purpose
Use Match Elements (MA00.2) to define and maintain matching elements. A
matching element consists of the following required components: an element
name, a data type, and a field size.
Each matching element that you define will have a type of "U" (user-defined).
Predefined elements will have a type of "L" (Lawson defined).
To add the predefined elements, select the Predefined Elements ("P") form
action.
Updated Files
MAMTCHELEM -
Referenced Files
None.
MA00.3 - Match Class
** Form purpose
Use Match Class (MA00.3) to define and maintain match classes. A match class
contains a hierarchy of matching elements. A match class can contain a single
element or as many as ten elements. The total field size of all elements in a
match class cannot exceed 55 characters.
Item: One element in the match class must be defined as the Item.
A match class determines how an invoice line will be matched. You are required
to define at least one match class.
The match class can be assigned to one or more companies. You can select from
the list of elements to assign match elements to the match class.
Note: Once the match class is assigned to a company in Company (MA01) you
cannot make any changes. If your match class has changed, you must add a new
match class.
Updated Files
MAMTCHELEM -
MATCHCLASS -
Referenced Files
None.
MA00.4 - Match Rule Groups
** Form purpose
Use Match Rule Groups (MA00.4) to define match rule groups. Rule groups
consist of up to twelve individual match rules. Match rule groups are assigned
to match tables in Match Table (MA00.1). You can assign up to three match rule
groups to a match table.
Match rules define how an invoice will be matched, and in what order. An
invoice can be matched at invoice or detail level; documents within a pool can
have everything from a one to one to all to all comparison done; and matching
tolerances can be defined by percent and/or amount. You can also indicate
whether chargebacks will be automatically created or written off.
Match Level
-----------
You must define a matching level for the matching process. The match level
determines what type of match the system will attempt. There are three match
levels; invoice match, line invoice match, and detail match. You can define up
to twelve match levels for a match rule group.
At all match levels you can automatically generate chargebacks if a match is
found within the tolerance limit and the Invoice Amount exceeds the Receipt
Amount. If you choose not to generate chargebacks, the difference will be
written off to a combination of accounts depending on tolerance and variance
conditions. You define these accounts in Company (MA01.1) or Process Level
(AP00.5).
Invoice Match (Match Level)
---------------------------
Invoice match means the system is matching the invoice goods amount with the
receipt goods amount. One or all invoices within a pool can be matched to one
or all receipts within a pool. The invoice goods amount total and receipt
goods amount total must be within the tolerance amount and/or percent.
If invoice details exist they are used to update the receiver and purchase
order lines. If invoice details do not exist, they are generated during the
match process from the receipt lines of the matched receipts. After the match,
the receipt and all receipt lines are closed.
If this match rule does not process chargebacks the difference between the
invoice and receipt amounts is posted to the tolerance account. You define the
tolerance accounts in Company (MA01.1) and optionally Process Level (AP00.5).
Line Invoice Match (Match Level)
--------------------------------
Line invoice match means the system is matching the invoice goods amount(s)
with the receipt goods amount(s). The items on the invoice must exist on the
receipt.
In a line invoice level match the receipt is fully matched to the invoice. One
or all invoices within a pool can be matched to one or all receipts within a
pool. The invoice total and receipt total must be within the tolerance amount
and/or percent.
If invoice details exist they are used to update the receiver and purchase
order lines. If invoice details do not exist, they are generated during the
match process from the receipt lines of the matched receipts. After the match,
the receipt and all receipt lines are closed.
If this match rule does not process chargebacks the difference between the
invoice and receipt amounts is posted to the tolerance account. You define the
tolerance accounts in Company (MA01.1) and optionally Process Level (AP00.5).
Detail Match (Match Level)
--------------------------
Detail match means the system is matching the individual detail line amounts
by comparing the extended amounts (quantity * cost) to determine if the
difference is within tolerances. You have the option to define a tolerance
amount and/or percent for each rule in the rule match group.
In a detail level match, one invoice is matched to one or all receipts within
a pool (1-1 or 1-A match type - see "Match Type" below). Receipts are matched
based on the receipt lines that match invoice details.
Note 1: After the match, it is possible that the receipt will remain open
since some receipt lines were not matched to invoice details.
Note 2: If a detail-match match rule does not process chargebacks, the cost
difference between the invoice and receipt amounts is posted to the item cost
variance account; the quantity difference is posted to the matched not
received accounts. You define these accounts in Company (MA01.1) and
optionally in Process Level (AP00.5).
Match Type
----------
You must define a match type for each matching level to determine how the
system will attempt a match. There are four match types: one to one, one to
all, all to one, and all to all.
One to one (1-1): This type takes one invoice and compares it to one receipt
in the same match pool.
One to all (1-A): This type takes one invoice and compares the sum of all
receipts in the same match pool.
All to one (A-1): This type takes the sum of all invoices and compares it to
one receipt in the same match pool.
All to all (A-A): This type takes the sum of all invoices and receipts in the
same match pool and compares them to each other.
Match Order
-----------
You must define a unique match order for each match rule. The match order
defines in what sequence the rules will be processed.
Matching Tolerances
-------------------
You can define tolerances for all match rules to automate the matching
process. Matching tolerances let the system match transactions that do not
have exact matching amounts. Tolerances are for an amount and/or a percent.
Invoices and receipts within tolerances will be matched.
Chargebacks
-----------
You can define whether the system will create a chargeback for the differences
if the match is within tolerance.
Updated Files
MAMTCHRULE -
Referenced Files
None.
MA00.5 - Element Value
Use Element Value (MA00.5) to create and maintain match element values.
Updated Files
MAELMVALUE -
Referenced Files
MAELMGROUP -
MAMTCHELEM -
MA00.6 - Element Group
Updated Files
MAELMGROUP -
Referenced Files
None.
MA00.7 - Element Group Relation
Updated Files
MAELMGPREL -
Referenced Files
MAELMGROUP -
MATCHCLASS -
|
