AutoInvoice uses grouping rules to determine what items to include on invoices, debit memos and credit memos. Grouping rules contain transaction attributes that must be identical for all items on the same transaction. For example, transaction number (TRX_NUMBER) is a mandatory attribute of all grouping rules. If you have two records in the interface tables with different transaction numbers, AutoInvoice will create separate transactions for each record.

Receivables provides two different types of transaction attributes: mandatory and optional. You cannot delete a mandatory attribute from any grouping rule, but you can add optional attributes to the mandatory attributes to create a new grouping rule.

Following is a list of mandatory and optional grouping rule columns:

Mandatory Attributes

AGREEMENT_ID

APPLICATION_ID

BILLING_DATE

COMMENTS

CONS_BILLING_NUMBER

CONTRACT_ID

CONVERSION_DATE

CONVERSION_RATE

CONVERSION_TYPE

CREDIT_METHOD_FOR_ACCT_RULE

CREDIT_METHOD_FOR_INSTALLMENTS

CURRENCY_CODE

CUSTOMER_BANK_ACCOUNT_ID

CUST_TRX_TYPE_ID

DEFAULT_TAXATION_COUNTRY

DOCUMENT_NUMBER

DOCUMENT_NUMBER_SEQUENCE_ID

DOCUMENT_SUB_TYPE

GL_DATE

HEADER_ATTRIBUTE1-15

HEADER_ATTRIBUTE_CATEGORY

HEADER_GDF_ATTRIBUTE1-30

HEADER_GDF_ATTR_CATEGORY

INITIAL_CUSTOMER_TRX_ID

INTERNAL_NOTES

INVOICING_RULE_ID

LEGAL_ENTITY_ID

ORIG_SYSTEM_BILL_ADDRESS_ID

ORIG_SYSTEM_BILL_CONTACT_ID

ORIG_SYSTEM_BILL_CUSTOMER_ID

ORIG_SYSTEM_SOLD_CUSTOMER_ID

PAYMENT_ATTRIBUTES

ORIG_SYSTEM_BATCH_NAME

PAYMENT_SET_ID

PREVIOUS_CUSTOMER_TRX_ID

PRIMARY_SALESREP_ID

PRINTING_OPTION

PURCHASE_ORDER

PURCHASE_ORDER_DATE

PURCHASE_ORDER_REVISION

REASON_CODE

RECEIPT_METHOD_ID

RELATED_CUSTOMER_TRX_ID

SET_OF_BOOKS_ID

TAXED_UPSTREAM_FLAG

TERM_ID

TERRITORY_ID

TRX_DATE

TRX_NUMBER

Optional Attributes

ACCOUNTING_RULE_DURATION

ACCOUNTING_RULE_ID

ATTRIBUTE1-15

ATTRIBUTE_CATEGORY

CODE_COMBINATION_ID

INTERFACE_LINE_ATTRIBUTE1-15

INTERFACE_LINE_CONTEXT

INVENTORY_ITEM_ID

LINE_GDF_ATTRIBUTE1-20

LINE_GDF_ATTR_CATEGORY

ORIG_SYSTEM_SHIP_ADDRESS_ID

ORIG_SYSTEM_SHIP_CONTACT_ID

ORIG_SYSTEM_SHIP_CUSTOMER_ID

REFERENCE_LINE_ID

RULE_START_DATE

SALES_ORDER

SALES_ORDER_DATE

SALES_ORDER_LINE

SALES_ORDER_REVISION

SALES_ORDER_SOURCE

TAX_CODE

TAX_RATE

If you have transactions that fail validation, Receivables looks at the value you entered in the Invalid Line field for your transaction batch source to determine the grouping of your transactions. (This field is located in the Transaction Sources window, AutoInvoice Processing Options tabbed region.) If you entered 'Reject Invoice', AutoInvoice rejects all of the transactions that make up one invoice if any of the transactions are invalid. For example, if your grouping rule specifies that three transactions should be created as one invoice and one of the transactions has an error, AutoInvoice rejects all three transactions and does not create an invoice.

However, if you entered 'Create Invoice', AutoInvoice rejects the one invalid transaction and creates an invoice from the two remaining valid transactions.

Transaction Number Validation

Receivables validates that transaction and document numbers are unique within a batch after grouping has completed. In certain cases, AutoInvoice will create multiple invoices in the same group with the same transaction or document number. Once grouping is completed, AutoInvoice checks for duplicate transaction and document numbers and reports any lines that fail validation.

For example, two lines are imported with the same transaction number, but they have different currency codes. These lines will be split into two separate invoices during grouping due to the different currency codes. Once grouping has completed, both of the invoices will fail validation due to identical transaction numbers.