Tax
NetSuite 2026.1
2026-04-08

Philippine Tax Audit Files Now Include Advanced Intercompany Journal Entries

Tax Audit Files SuiteApp v1.90.0 adds Advanced Intercompany Journal Entries to the Philippine General Ledger and General Journal reports, aligning intercompany transaction data with BIR reporting requirements.

Affects:Tax Audit Files SuiteApp (v1.90.0)Advanced Intercompany Journal EntriesPhilippine General Ledger ReportPhilippine General Journal Report

What changed

Tax Audit Files SuiteApp version 1.90.0 expands the Philippine General Ledger and Philippine General Journal reports to include Advanced Intercompany Journal Entries (AIJE). Previously, these intercompany transactions were omitted from the Philippine tax audit file output, which could create gaps when reconciling against Bureau of Internal Revenue (BIR) requirements.

With this update, any Advanced Intercompany Journal Entry records posted in your account will now appear in the generated audit files alongside standard journal entries.

Scope

  • SuiteApp: Tax Audit Files (bundle), version 1.90.0
  • Reports affected: Philippine General Ledger, Philippine General Journal (both under Reports > Tax > Audit Files)
  • Record type: Advanced Intercompany Journal Entry (advintercompanyjournalentry)
  • Locale: Philippines subsidiaries only

What to do

  1. Confirm the Tax Audit Files SuiteApp has been updated to v1.90.0 or later. Check via Customization > SuiteBundler > Search & Install Bundles > List.
  2. If you use the Advanced Intercompany Journal Entries feature, verify it is enabled at Setup > Company > Enable Features > Accounting.
  3. Generate a test Philippine General Ledger or General Journal report from Reports > Tax > Audit Files and confirm that AIJE transactions appear in the output.
  4. If you have downstream integrations or scripts that parse these audit file outputs, review them to ensure they handle the additional intercompany journal entry rows correctly.

Notes

Oracle's release note is light on technical detail. It does not specify whether the audit file XML/CSV schema changed or if new columns were introduced. If you consume the raw audit file programmatically, inspect the updated output for any structural differences before relying on it in production.