ANZ Localization SuiteApp: Payment Times Report 2025 Configuration

The ANZ Localization SuiteApp introduces a new Payment Times Report (PTR) 2025 configuration page that supersedes the PTR 2023 workflow. The update aligns NetSuite's PTR output with the March 2025 Australian Taxation Office (ATO) guidelines. The previous PTR 2023 report remains accessible but is effectively deprecated for new reporting periods.

Note: Oracle does not specify which NetSuite release version bundles this SuiteApp update. The exact SuiteApp bundle version and release window should be confirmed via SuiteBundler or the SuiteApp Marketplace listing for ANZ Localization.

What changed

• New setup page at Setup > ANZ Localization > Reporting Setup (Administrator role) or Setup > Other Setup > Reporting Setup (non-admin roles).
• Configuration is now subsidiary-scoped — you select a subsidiary before entering PTR details.
• Four subtabs replace the previous layout:
  • Entity and Approval Information — approver first/last name, approval date, signed flag, and an entity-information declaration checkbox.
  • Payment Details — three supply-chain-finance / procurement-fee / voluntary-code checkboxes, plus receivable-term comparison (longer/shorter/same) and three numeric fields for expected most-common payment term and min/max estimates for the next period.
  • Others — free-text report comments.
  • Subsidiaries — multi-select list for consolidation (only visible when the Consolidate Subsidiaries checkbox is checked on the parent record).
• A new Consolidate Subsidiaries flag lets you roll child subsidiaries into a parent subsidiary's PTR report. Consolidated subsidiaries are viewable from the View Consolidated Subsidiaries link on the PTR Report Summary subtab.
• Validation rule: Approval Date must be earlier than the Responsible Member Declaration date.

What to do

1. Verify SuiteApp version. Confirm the ANZ Localization SuiteApp is updated to the version that includes PTR 2025 support. Check via Customization > SuiteBundler > Search & Install Bundles > List.
2. Reconfigure PTR settings. Navigate to the new Reporting Setup page and populate all required fields on the Entity and Approval Information, Payment Details, and Others subtabs for each reporting subsidiary.
3. Set up consolidation (if applicable). If you report on a consolidated basis, check Consolidate Subsidiaries, open the Subsidiaries subtab, and multi-select the child subsidiaries to include.
4. Review downstream scripts and integrations. If you have SuiteScript automations, saved searches, or SuiteAnalytics workbooks that reference PTR 2023 custom records or fields, verify they still resolve correctly. Oracle does not document the internal record IDs or field IDs in this page — inspect the SuiteApp bundle contents or use N/record to enumerate exposed fields on the PTR configuration record.
5. Update roles and permissions. Non-administrator users access the page via Setup > Other Setup > Reporting Setup. Confirm the appropriate roles have permission to this menu path and to edit the PTR configuration record.
6. Retire PTR 2023 workflows. If you have scheduled scripts or integrations that generate or submit the PTR 2023 report, plan a cutover to the PTR 2025 equivalents before your next ATO reporting deadline.

Gaps in the source

• No internal record type, field IDs, or SuiteScript module references are provided. You will need to inspect the bundle or use the Records Browser to find the custom record backing this configuration page.
• The specific NetSuite release version and SuiteApp bundle version are not stated.
• No REST/SOAP endpoint or SuiteQL exposure is documented for programmatic access to PTR 2025 data.