1Z0-1055-26 key terms

A code-based value set that supplies standard lists such as payment terms, invoice types, and payment methods. It is maintained centrally and shared across business units, so codes must be validated before use in configuration or import.

Business-unit-level settings that govern invoice entry behavior, including defaults for liability accounts, payment terms, distribution sets, and automatic withholding. These options determine what a user sees pre-populated when creating an invoice.

Rules that calculate due dates and discount eligibility from invoice dates, such as net 30 or 2/10 net 30. Terms can be multi-installment and can drive both scheduled payment dates and early-payment discount claims.

A location belonging to a supplier that holds purchasing, payment, and tax attributes. Invoices are always tied to a site, which supplies the default payment method, bank account, and remit-to address.

The address to which a payment is sent or, for electronic payments, the location associated with the payment instruction. It is defined at supplier site or site-assignment level and flows onto printed and electronic payment output.

A classification that determines how an invoice is accounted and matched, such as Standard, Credit Memo, Debit Memo, Prepayment, or Expense Report. The chosen type controls available actions and the accounts that receive the liability.

The top-level record of an invoice holding supplier, site, invoice number, invoice date, currency, and total. Header values default down to lines and distributions but can be overridden where the configuration allows.

A detail row describing what was invoiced, carrying item, amount, and tax determinants. Lines can be matched to purchase orders or receipts, or entered as amount-based or quantity-based items without matching.

The accounting split of an invoice line, assigning amount to a charge account, cost center, and optional project or asset information. Distributions are what create the final subledger accounting entries.

Validation that compares invoice price and quantity against an approved purchase order before the invoice can be validated. Tolerances define how much variance is acceptable without holds.

Validation of invoice against both purchase order and receipt quantities, ensuring goods were received before payment. It requires receipt accounting to be in place and uses quantity and amount tolerances.

The process that checks an invoice for completeness and accuracy, applying matching, tolerance, tax, and period rules. Successful validation creates the liability and distributes the invoice to accounting.

A restriction that blocks validation or payment until resolved, raised by matching failures, missing information, or manual action. Holds must be released before the invoice can be paid or accounted.

A configurable routing of invoices to approvers based on amount, supplier, or other attributes before payment. It uses workflow or approval rules and can run before or after validation depending on setup.

A submission that selects payable invoices by criteria such as due date, supplier, or pay group, then builds and formats payments. It runs through selection, build, format, and payment creation phases.

The instrument used to pay a supplier, such as check, electronic funds transfer, wire, or clearing. Each method maps to a payment format and determines how the instruction is produced and reconciled.

The template or program that renders a payment instruction into output, such as a printed check or a bank file. Formats are associated with payment methods and can be customized for bank requirements.

A reduction in the payable amount earned when an invoice is paid by its discount date. The system calculates the discount from terms and applies it during payment unless the invoice is paid late.

The last date on which an early-payment discount can be taken under the invoice terms. It is derived from the invoice date and the discount period and drives the payment schedule.

The disbursement account from which payments are issued, configured with account details, currency, and payment methods. It is assigned to business units and used to generate payment instructions.

The process of matching issued payments against bank statement transactions to confirm funds left the account. Unreconciled payments remain outstanding and affect cash balances and reconciliation reports.

The rules engine that transforms Payables transactions into journal entries using account derivation and mapping sets. It lets accounting be configured without changing transaction processing logic.

A defined interval, usually a month, in which transactions are accounted and reported. Payables periods must be open for invoice accounting and closed only after all entries are transferred and posted.

The sequence of steps that finalizes a Payables period, including resolving holds, accounting invoices, transferring entries to the general ledger, and reconciling balances. Closing prevents further transaction entry in that period.

A Payables report listing supplier balances by period to verify that subledger totals agree with general ledger liability accounts. It is a key control during period-end reconciliation.

A claim submitted by an employee for reimbursable business costs, entered with expense lines, receipts, and cost allocations. Approved reports can be paid through Payables or reimbursed through payroll.

Rules that constrain what employees may claim, including limits, required receipts, and allowed categories. Policies are applied during entry and audit to flag or block noncompliant expenses.

A classification for expense lines that determines default accounts, policy applicability, and reporting grouping. Categories are mapped to expense types and drive how costs are posted.

A review step where selected expense reports are examined against policy before reimbursement. Auditors can approve, adjust, or return reports, and selection can be rule-based or sampled.

A card charge imported into Expenses that an employee matches to an expense report. Unmatched transactions create company liability and must be reconciled or disputed.

Automation that reads scanned or photographed supplier invoices and extracts header and line data for entry. Extracted values are matched to suppliers and validated, reducing manual keying.

Machine-learning-based extraction that improves invoice capture by learning supplier layouts and predicting field values. It complements OCR by handling varied formats and suggesting corrections.

Analytics that flag unusual invoices, suppliers, or payment patterns for review, such as duplicate or out-of-policy items. Flags help auditors focus effort where risk is highest.

A control that compares new invoice numbers, amounts, and supplier references against existing records to prevent double payment. Matches raise a hold or warning for review.

The modern user interface design applied across Oracle Cloud applications, offering consistent navigation, responsive layouts, and improved accessibility. It changes page appearance and interaction without altering underlying business logic.

An isolated environment where configuration and UI changes can be tested before publishing to production. Sandboxes support page customization and safe experimentation with Payables setup.

Adjusting page layout, fields, and defaults for a user or role without code changes. Personalizations are stored as layers and can be promoted through sandboxes to production.