> For the complete documentation index, see [llms.txt](https://finspectors.gitbook.io/finspectors-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://finspectors.gitbook.io/finspectors-documentation/audit-modules-auditor-view/upload.md). # Upload The upload workflow consists of: 1. Trial Balance Upload 2. Trial Balance Validation 3. FSLI Mapping 4. Trial Balance Review 5. General Ledger Upload 6. General Ledger Validation 7. Upload Complete *** ## **Step 1: Upload Trial Balance** The Trial Balance is the first file uploaded into the engagement and serves as the foundation for all planning activities. *** ### **Column Mapping** Map the following four mandatory columns: * Account Name * Account Type * Account Number * Net Amount Once the required columns are mapped, the system automatically proceeds to validation. *** ### **Trial Balance Validation** Finspectors validates the uploaded Trial Balance to ensure the data is complete and suitable for audit. The validation checks include: * First row is a valid header * Only one worksheet is present * Total amount balances net to zero * No duplicate account codes * No blank values in mandatory fields Any issues identified should be resolved before proceeding. *** ### **FSLI Mapping** After validation, the platform automatically maps uploaded accounts to the corresponding Financial Statement Line Items (FSLIs). Auditors should: * Review the suggested mappings * Complete any unmapped accounts * Create new FSLIs where required * Confirm all mappings before continuing This ensures every account is correctly classified for downstream planning and execution modules. *** ### **Trial Balance Review** Once mapping is complete, the Trial Balance preview is displayed for final review. Auditors can: * Review mapped balances * Verify account classifications * Add journal adjustments using the **Add Adjustment** option * Confirm the final Trial Balance before submission After submission, the Trial Balance becomes available for Materiality, Risk Assessment and Scoping. *** ## **Step 2: Upload General Ledger** After the Trial Balance has been successfully submitted, upload the General Ledger. *** ### **Column Mapping** Map the required General Ledger fields so the system can correctly interpret the transaction data. Once mapping is completed, validation begins automatically. *** ### **General Ledger Validation** The platform validates the uploaded General Ledger using a series of quality checks. General Ledger checks include: * First row is a valid header * Only one worksheet is present * No blank values in mandatory columns * Total amount balances net to zero * All entries fall within the selected engagement period *** ### **Cross-File Validation** Finspectors also compares the General Ledger with the submitted Trial Balance to ensure consistency across both datasets. The following checks are performed: * Accounts match across both files for completeness * Balances match across both files for tie-out * Account names match across both files for consistency These validations ensure that the Trial Balance and General Ledger are fully aligned before the audit begins. *** ## **Upload Complete** Once all validation checks pass successfully, the engagement data is ready for use throughout the platform. The uploaded Trial Balance and General Ledger will automatically power: * Materiality * Risk Assessment * Scoping * Sampling * Workpapers * Test of Details * Other audit workflows This structured upload process helps ensure that every engagement begins with complete, validated and audit-ready financial data. {% embed url="" %}