Aconex Filename Rejected? Here's Exactly Why and How to Fix It
5 min read · ISOCheck
You've prepared your drawings, gathered your documents, and you're ready to upload to Aconex. Then it happens — the upload fails, or the document controller rejects your submission.
Nine times out of ten, the problem is the filename.
Oracle Aconex enforces strict document numbering rules on enterprise projects. If your filename doesn't match the agreed naming convention — usually based on ISO 19650 — it won't pass. Here's exactly what goes wrong and how to fix it before you hit upload.
Why Aconex Cares About Filenames
Aconex is a Common Data Environment (CDE). Every document uploaded needs a unique, structured identifier so it can be tracked, versioned, and retrieved across the project lifecycle.
When a project adopts ISO 19650, the document number is the filename (minus the extension). Aconex validates this against the project's configured naming convention. If any field is wrong — even one character — the document is flagged or rejected.
This isn't Aconex being difficult. It's the standard working as intended. The problem is that most teams only find out about naming errors after preparing hundreds of files.
The 7 Fields Every ISO 19650 Filename Must Have
A compliant ISO 19650 filename looks like this:
PRJ123-ACME-ZZ-01-DR-A-0001.pdf
Every hyphen-separated segment is a specific metadata field:
| # | Field | Example | What It Means |
|---|---|---|---|
| 1 | Project | PRJ123 | Unique project code — set in EIR, same for all parties |
| 2 | Originator | ACME | Your organisation code — from BEP |
| 3 | Volume / System | ZZ | Zone or system (ZZ = whole project) |
| 4 | Level / Location | 01 | Floor, level, or location code |
| 5 | Document Type | DR | Drawing, report, specification, etc. |
| 6 | Role / Discipline | A | Architecture, S = Structure, M = MEP |
| 7 | Sequential Number | 0001 | 4-digit minimum, always zero-padded |
All fields must be uppercase. Only A–Z and 0–9. No spaces. No underscores. Hyphens separate fields only — never appear inside a field.
The Most Common Aconex Rejection Reasons
1. Lowercase characters
prj123-acme-zz-01-dr-a-0001.pdf will fail. Every character must be uppercase — including the project code and originator.
2. Wrong number of fields
ISO 19650 requires exactly 7 hyphen-separated fields. Six fields will fail. Eight will fail. Count your hyphens — there should be exactly 6.
3. Sequential number too short
0001 is valid. 001 or 1 is not. Always zero-pad to at least 4 digits.
4. Invalid document type code
Using DWG instead of DR for a drawing? If the project BEP doesn't include that code, it'll be rejected. Always check the BEP for approved type codes — don't invent your own.
5. Wrong project code
The project code is defined in the Employer's Information Requirements (EIR) and must match exactly across every document from every organisation. One extra character causes a mismatch.
6. Spaces or special characters
No spaces. No brackets. No slashes. No dots except before the file extension. Even a single trailing space will cause a failure that's invisible in Windows Explorer.
Quick Rejection Diagnosis Table
| Rejection symptom | Likely cause | Fix |
|---|---|---|
| 'Invalid document number' | Field count wrong or wrong project code | Count hyphens — should be exactly 6 |
| 'Filename not recognised' | Lowercase or special characters | Convert entire filename to uppercase |
| 'Duplicate document number' | Number field not unique | Increment the sequential number |
| 'Invalid type code' | Type code not in project BEP | Check BEP codelist and use approved code |
| 'Sequential number invalid' | Number field less than 4 digits | Zero-pad to 0001, 0002, etc. |
How to Catch Errors Before You Upload
Manually checking filenames works for 5 documents. It doesn't scale to 50 or 500.
The reliable approach is to validate every filename before touching Aconex. ISOCheck does this — paste up to 500 filenames and it checks all 7 fields against ISO 19650 rules instantly. It shows exactly which field failed and suggests a corrected version.
It runs entirely in your browser. No login required for basic use. Your files never leave your device.
What to Do When You Get a Rejection
Step-by-step fix
Prevention Is Faster Than Fixing
The best time to check filenames is before you prepare the submission package — not after. Build a habit of validating as you create documents.
A five-minute check before upload saves hours of back-and-forth after rejection.
Validate your filenames before the deadline
Check up to 500 filenames at once — free, in your browser, your files never leave your device.
Try ISOCheck Free