Several fields are required during manual Invoice entry. Which are the fields required at the header level?

Question

Options

• Adate, customer, source, type, GL date, legal entity
• Bdate, legal entity, bill-to, source, type, class, remit-to
• Cterms, date, bill-to, source, legal entity, type, remit-to
• Ddate, customer, source, type, General Ledger (GL) date, class
• Edate, source, class, type, GL date, legal entity, bill-to, terms, remit-to

• A
  3% (1)
• B
  3% (1)
• C
  8% (3)
• E
  87% (33)

Explanation

Option E is correct because it includes all nine fields required at the invoice header level in Oracle Accounts Receivable (or similar ERP systems): date, source, class, type, GL date, legal entity, bill-to, terms, and remit-to. Each of these fields drives downstream processing - legal entity ties to accounting rules, GL date controls posting periods, and remit-to determines where payment instructions appear on the invoice.

Why the distractors fail:

• A & D substitute "customer" for the more specific "bill-to" field and both omit "terms" and "remit-to," which are required for payment processing.
• B drops GL date and terms entirely, and omits legal entity - all critical header requirements.
• C is missing GL date and class, making it incomplete despite having several correct fields.

Memory tip: Think of the acronym "DS CT GL² BT R" - Date, Source, Class, Type, GL date, Legal entity, Bill-to, Terms, Remit-to. The key trap on this question is confusing "customer" (a lookup concept) with the specific required fields "bill-to" and "remit-to," and forgetting that both GL date and terms must appear at the header level before the invoice can be saved.

No community discussion yet for this question.