2026.1 Accounting SuiteApps: Account Matching Report Columns and SuiteApprovals Journal Entry Locking

Oracle bundled two unrelated SuiteApp updates into this 2026.1 accounting release note: a minor reporting tweak to the Account Matching Report and a more substantive set of SuiteApprovals changes around journal entry locking and approver visibility. Neither update calls out a SuiteScript API surface, so the impact is primarily configuration- and report-consumer-facing — but anything that customizes saved searches, workflows, or scripts against journal entry approval state should be reviewed.

Account Matching Report SuiteApp 1.1.0

Two new columns and one rename land on the Account Matching Report:

• Applied Trans Date — transaction date of the applied transaction.
• Applied Trans Period — posting period of the applied transaction.
• Applied Date has been renamed to Last Applied Date to make clear that it reflects the most recent application timestamp, not the original.

The release note does not document the underlying field IDs, the saved search definition, or whether the renamed column's internal ID changed. If you have custom saved searches, workbooks, scheduled report exports, or downstream ETL that key off the old Applied Date label, treat the rename as potentially breaking until you verify the field's internal ID in the Account Matching Report's saved search.

SuiteApprovals SuiteApp 2026.1.1

Record Locking and Reapproval for Journal Entries

You can now configure journal entries to become read-only based on approval status (Pending Approval, Approved, or both) and define tolerance thresholds — either as a percentage or a fixed amount — that automatically reroute an edited journal entry back through approval. This replaces the prior pattern of manual resubmission.

The release note does not specify the underlying record type that stores these settings, the field IDs, or whether tolerances are evaluated server-side via a User Event script, a workflow, or native SuiteApp logic. If you have existing customizations that mutate posted or pending-approval journal entries via SuiteScript (N/record) or REST (/services/rest/record/v1/journalentry), test them against the new lock states — silent edits that previously succeeded may now throw permission errors or trigger reapproval routing.

Records for Approval Portlet

The portlet now displays a count of journal entries awaiting approval. Clicking the Journal Entry link opens the Review Documents Awaiting Approval page.

SuiteApprovals Reminders Portlet

• A new journal entry section monitors all journal entries in Pending Approval or Rejected status.
• The Review Documents Awaiting Approval page gains two columns: Aging Days (time waiting for approval) and Next Approver (assigned approver name).

What's not in the release note

Oracle's note is light on technical specifics. None of the following are documented and should be verified in your sandbox:

• The custom record (likely a customrecord_*) that stores Record Locking and Reapproval settings, and its field IDs.
• Whether tolerance evaluation runs in a User Event beforeSubmit, a workflow, or a Map/Reduce — this matters for governance and for understanding where to hook custom validation.
• Whether journal entry edits via REST, SOAP (SuiteTalk WSDL), or CSV import are subject to the new lock, or only UI edits.
• The internal ID of the renamed Account Matching Report column.

What to do

1. Install Account Matching Report SuiteApp 1.1.0 in a sandbox and inspect the report's saved search for the renamed column's internal ID. Update any dependent saved searches, workbooks, or external reports.
2. Audit any SuiteScript or integration that writes to journalentry records — particularly anything that edits records in Pending Approval status. Confirm behavior under the new lock settings before enabling them in production.
3. If you use SuiteApprovals for journal entries, define your record locking and reapproval thresholds in a sandbox first. Decide whether percentage or absolute-amount tolerances better match your materiality policy.
4. Review the SuiteApprovals custom records (customrecord_* from the SuiteApp bundle) post-upgrade to identify the new lock/tolerance configuration record and document its schema for your team.
5. Notify approvers and JE preparers about the new Aging Days / Next Approver visibility and the lock behavior so edits don't silently reroute through approval.
6. Verify whether REST and SOAP-based JE updates are blocked by the lock — the release note doesn't say. Test POST/PATCH against /services/rest/record/v1/journalentry/{id} in both Pending Approval and Approved states.