A checklist is not an all-fund tagging promise
A 485BPOS iXBRL checklist must be adapted to the actual submission, disclosure and current applicable SEC instructions. Do not collapse every fund form into the same Word-to-iXBRL process. Confirm form/submission type, registrant, fund/series/class identifiers, prospectus dates, approved source and complete reviewed prior package.
This is an educational production checklist for qualified supervised review. It does not establish that every 485BPOS document requires the same facts, or that an isolated sample HTML file is a complete validated filing package. Resolve the actual form/taxonomy requirements with the specialist lead.
Map disclosure to the agreed review scope
- Objective and relevant identifiers.
- Fees, expense examples, assumptions, waivers and footnotes.
- Strategies and each principal risk with the applicable fact/dimensional structure.
- Performance tables and narrative boundaries where applicable.
- Series/class, contexts, dates, units and approved transformations.
Check every disclosed expense-example horizon, not only the first figures. Preserve unresolved source blanks as issues for the content owner; never infer an amount to make a table look complete.
Inspect meaning and package relationships
Review concept selection, actual unit measures, scale, decimals, signs and extracted values. Check visible narrative inside intended text-block boundaries, empty required facts, continuations, hidden facts and duplicate inconsistencies. A custom risk-axis member is not interchangeable with a primary risk text-block concept.
Require the correct accepted taxonomy entry point, extension schema/linkbases and referenced assets where needed. Namespace naming alone does not prove correctness or rejection. Strict XML, applicable XBRL/SEC checks, documented findings and qualified human review are separate stages.
Revalidate after revisions
Changes to fund, class or risk identifiers and narrative boundaries can affect tags and relationships. Update the version, regenerate proof, reconcile extracted values and revalidate the complete package. Keep a reviewer and reason for every warning disposition. Do not suppress unresolved errors to produce a clean screenshot.
Authorized TEST processing, exact-version approval and explicit LIVE authority remain separate from production delivery. SEC acceptance is not an accounting/taxonomy opinion.
Use current guidance
Use the current SEC XBRL Guide, form instructions and accepted taxonomies—not a frozen old namespace or vendor article alone. Fund production support · Fee-table review · Supervised iXBRL assistance.