Vendors and Purchasing
NetSuite 2025.1
2025-03-01

Payment Times Report 2025: TCP and SBTCP Dataset Filtering Criteria for Australian Compliance

NetSuite's PTR 2025 replaces PTR 2023, introducing Trade Credit Payments (TCP) and Small Business Trade Credit Payments (SBTCP) datasets aligned with updated Australian Taxation Office guidelines. New fields and checkboxes on vendor bills and vendor records control inclusion/exclusion logic.

Affects:Vendor Bill (transaction record)Vendor recordBill Payment recordAUS Reporting subtabPayment Times Report 2025

PTR 2025 is the replacement for PTR 2023, aligned with the March 2025 Australian Taxation Office guidelines. It introduces two distinct datasets — Trade Credit Payments (TCP) and Small Business Trade Credit Payments (SBTCP) — each with explicit filtering criteria that determine which vendor bill transactions are included in the report.

What changed

TCP dataset inclusion criteria

A vendor bill is included in the TCP dataset when all of the following are true:

  • Transaction type is Vendor Bill.
  • At least one non-voided Bill Payment exists against the vendor bill (regardless of the bill's status).
  • The Excluded From TCP checkbox on the vendor bill is not checked.
  • The Excluded From Payments Time Report checkbox on the vendor record is not checked.
  • The Credit Card Payment checkbox is checked and the Payment Amount field value is greater than AUD 100.
  • The Disputed Invoice checkbox on the vendor bill is not checked.
  • The vendor bill has an Australian billing address.
  • Payment is made (or can be made) at least one calendar day after the supply of goods or services, determined by the first matching condition:
    1. A Term is selected on the Billing subtab and the term's Days Till Net Due is >= 1 day.
    2. The Supply Date field has a value and the bill payment date is at least one day after it.
    3. The Date Received field has a value and the bill payment date is more than one day after it.
    4. The bill payment date is at least one day after the bill's creation date.

SBTCP dataset inclusion criteria

A transaction is included in the SBTCP dataset when:

  • The Small Business checkbox on the vendor record is checked.
  • All qualifying TCP payments for that vendor are fully paid.
  • The transaction has an Australian billing address.

AUS Reporting subtab

A new AUS Reporting subtab now appears on vendor records and transaction records when the vendor or transaction has an Australian billing address or is associated with an Australian subsidiary. This subtab surfaces PTR-related fields without requiring custom form configuration.

Key fields and checkboxes

  • Excluded From TCP — vendor bill body field; check to exclude a specific bill from TCP.
  • Excluded From Payments Time Report — vendor record field; check to exclude all bills for that vendor.
  • Credit Card Payment — vendor bill field; must be checked for inclusion (with amount > AUD 100).
  • Disputed Invoice — vendor bill field; checking this excludes the bill.
  • Small Business — vendor record field; flags the vendor as a small business entity for SBTCP.
  • Supply Date / Date Received — vendor bill fields used in the payment-timing calculation.

What to do

  1. Audit vendor records. Ensure the Small Business checkbox is correctly set on all Australian vendors that qualify as small business entities under the ATO definition. This directly controls SBTCP dataset membership.
  2. Review exclusion flags. Check that Excluded From TCP and Excluded From Payments Time Report are only set where intentional. Any scripted or CSV-imported vendor bills should have these fields explicitly handled.
  3. Validate billing addresses. Both datasets filter on Australian billing address. If your vendor records or bills use non-standard address formats, confirm the address resolves to an Australian country code — otherwise transactions will silently drop out of the report.
  4. Check Term records. If you rely on the Term-based payment date calculation, verify that the Days Till Net Due value on your Term records is at least 1. Terms with 0 days will cause the system to fall through to the next date-calculation method.
  5. Update integrations. If you have SuiteScript or workflows that create vendor bills or bill payments, ensure they set the new PTR-related fields (Excluded From TCP, Disputed Invoice, Credit Card Payment) appropriately. The internal IDs for these fields are not documented in the source — use nlapiGetField / record.getField or the Records Browser to confirm field IDs before scripting.
  6. Retire PTR 2023 usage. PTR 2025 replaces PTR 2023. If you have saved searches, scheduled scripts, or dashboards referencing the old PTR, plan to migrate them. The old report remains accessible but is no longer the current standard.

Note: Oracle's documentation does not specify the internal field IDs or SuiteScript enums for the new checkboxes. Before writing automation, inspect the fields via the Records Browser (Setup > Records Catalog) or use record.getFields() on a qualifying vendor bill to discover the exact IDs.