Oracle 1Z0-1056-26 common mistakes
Oracle 1Z0-1056-26 · Understand the traps and how to avoid them.
Treating the AutoInvoice Line and Distribution rule sets as interchangeable and assigning a Line rule to the transaction source's distribution field, or vice versa. Candidates pick whichever rule name looks familiar instead of matching the rule type to the field.
The transaction source setup has separate fields for Line, Tax, Freight, and Distribution rules, and the seeded names (e.g., 'Standard Line', 'Standard Distribution') look similar. Without hands-on experience of which rule type populates which field, the distinction blurs under time pressure.
What to do instead
Memorise the pairing: Line rules derive invoice line segments, Distribution rules derive the accounting distribution segments. In the transaction source, confirm each field accepts only its own rule type. Practise reading a source setup screen and stating which rule controls which output.
Assuming a receipt is applied to the oldest invoice automatically, or that AutoCash rules apply regardless of the receipt's application rule set. Candidates answer cash-application questions as if a single global rule governs all receipts.
AutoCash rule sets are attached to the receipt method and application rule sets, and the order of the AutoCash rules (e.g., apply to oldest, apply to specific, clear the account) determines the result. Candidates who have not traced a receipt through the rule hierarchy default to 'oldest first' intuition.
What to do instead
Learn the AutoCash rule hierarchy: receipt method's application rule set determines which AutoCash rule set runs, and rules execute in a defined sequence until the receipt is fully applied. Rehearse with a scenario where the oldest invoice is partially paid and see which rule fires first.
Configuring a customer or transaction with a single business unit assumption and then failing questions where the customer site, transaction, and receipt belong to different business units or legal entities.
Oracle Receivables is business-unit aware, and many setups (customer accounts, transaction sources, receipt methods) are shared or restricted across business units. Candidates who only studied single-BU flows miss the cross-BU constraints and the Accounted-By vs. Business Unit distinction.
What to do instead
Build a mental model of the three layers: legal entity, business unit (Accounted-By), and operating unit context. For each setup object, note whether it is global, legal-entity-specific, or business-unit-specific. Practise identifying which BU a transaction is accounted in from its source and site.
Confusing the roles of Revenue Management (formerly Revenue Recognition) and standard Receivables accounting: assuming revenue is recognised at invoice creation or that an invoice's GL date drives revenue scheduling.
Revenue adjustments, sellable/returnable flags, and revenue contingencies are configured separately from the invoice. Candidates who learned only basic AR accounting expect revenue to post with the invoice and misread questions about revenue schedules and deferred revenue.
What to do instead
Separate the two ledgers of thought: invoice creation posts to receivables and revenue accounts per the AutoAccounting setup; Revenue Management creates revenue schedules and recognition events. Learn where sellable/returnable flags and revenue contingencies are set on the item or transaction line, and how a revenue adjustment changes the schedule.
Answering period-close questions as if closing Payables or General Ledger also closes Receivables, or as if a closed AR period blocks all transactions rather than only those with GL dates in that period.
AR period close is its own sequence (open, close, permanently close) and interacts with subledger accounting and GL. Candidates conflate the AR period status with the GL period status and miss that transactions can still be entered with a future-dated GL date.
What to do instead
Map the AR period statuses and what each blocks: open allows entry, close prevents new entry but allows adjustments and reconciliation, permanently close is irreversible. Then trace how the AR period status relates to the GL period and to subledger accounting entries before transfer.
Treating a credit memo and an on-account credit as the same object, or assuming a credit memo can be applied to any invoice regardless of the transaction type and customer.
Credit memos are transactions with their own AutoInvoice and accounting rules, while on-account credits are unapplied receipt balances. Candidates who only studied receipts miss that credit memos follow transaction-type rules and can be matched only within allowed parameters.
What to do instead
Distinguish the three credit instruments: credit memo (a transaction), on-account credit (unapplied receipt), and adjustment (a receivable adjustment). For each, note what it debits/credits and how it is applied or cleared. Practise matching a credit memo against an invoice and identifying why a match is rejected.
Ignoring the AutoInvoice validation and rejection workflow: assuming all interface lines post, rather than recognising that lines failing validation are rejected and must be corrected and resubmitted.
AutoInvoice runs validation, groups lines into transactions, and rejects lines with errors (e.g., missing salesperson, invalid GL date, unbalanced distributions). Candidates who only read about the interface assume a single pass succeeds and cannot answer questions about the interface exception report.
What to do instead
Learn the AutoInvoice phases: validation, grouping, and creation, plus the interface tables (RA_INTERFACE_LINES_ALL, RA_INTERFACE_DISTRIBUTIONS_ALL) and the rejection reasons. Know that rejected lines remain in the interface until corrected and that the exception report lists them by error.
Assuming Collections and Credit Management are configured per customer rather than through scored strategies, dunning plans, and credit profiles that can be assigned at the account or site level.
Credit Management uses scoring engines, credit limit rules, and credit profiles; Collections uses strategies, dunning plans, and delinquency. Candidates who have not configured these assume a single credit limit field on the customer and miss the rule-based evaluation.
What to do instead
Study the Credit Management objects: credit profile, credit limit rule, scoring model, and the credit check that runs at order/invoice time. For Collections, learn strategy assignment, dunning plan steps, and how delinquency is calculated. Trace one customer through a credit check and one through a dunning cycle.
Treating subledger accounting as automatic and identical to the seeded rules, failing to recognise that the accounting method, journal line rules, and account derivation rules determine the final GL entries.
Subledger Accounting (SLA) sits between AR and GL, and the seeded accounting method can be overridden. Candidates who only studied basic AR accounting entries do not know where to look when a question asks which account a transaction hits or why a journal entry differs from expectation.
What to do instead
Learn the SLA layers: accounting method, journal line types, account derivation rules, and mapping sets. Know the seeded Receivables accounting method and how to trace a transaction to its subledger journal entry. Practise reading a create-accounting output and identifying the derivation rule behind each segment.
Answering reporting questions as if all AR reports run from the same source and refresh in real time, rather than distinguishing standard reports, BI Publisher reports, and OTBI subject areas with their own refresh and data lineage.
Oracle Fusion offers seeded reports, BI Publisher, and OTBI, each with different data sources and latency. Candidates who have not used the reporting tools assume a single report catalogue and cannot answer questions about which tool to use for a given requirement.
What to do instead
Categorise the reporting options: standard/BI Publisher reports for operational and formatted output, OTBI for real-time transactional analysis, and the Receivables dashboard for ageing and collections. For each common requirement (ageing, unapplied receipts, revenue), name the correct tool and its data source.