SME Strategy 5 min Read

Common SAFF File Errors & How to Fix Them

By SMEStack Compliance Editorial • General information, not tax or legal advice

Uploading a superannuation contribution file only to have it rejected is a frustrating experience. Most rejections are caused by small formatting errors in the SAFF file.

1. Incorrect USI (Unique Superannuation Identifier)

Funds frequently merge or change their USIs. If you use an old USI from a record two years ago, the file will fail. Solution: Use our migrator, which cross-references the latest Super Fund Lookup (SFLU) data.

2. Invalid ABN Formatting

An ABN must be exactly 11 digits. Sometimes spaces or dashes are accidentally included, causing a validation error. Solution: Always strip non-numeric characters from ABN fields.

3. Date Format Mismatches

Some portals want DD/MM/YYYY, while others want YYYY-MM-DD. The SAFF standard has a specific requirement. Solution: Check your portal's documentation or use a standardized generator.

4. TFN Errors

A missing or invalid TFN for an employee can trigger a "warning" or a "rejection" depending on the fund. Solution: Ensure your source data is clean before attempting an export.

Our SBSCH Migrator includes a built-in validation layer that catches these errors before you download the file, saving you hours of troubleshooting with fund support lines.

Related guides