v1.0.2 - Import Data Validation
Problem
The import process currently accepts data that may be structurally valid but logically inconsistent. These inconsistencies are not always detected until financial reports are generated, making them difficult to identify and correct.
The following problems need to be addressed:
- A Chart of Account (COA) may contain an account Type or Category that is not supported by the system.
- A Chart of Account (COA) may assign a Category that does not correspond to its Type, resulting in incorrect account classification.
- Journal entries belonging to the same Form Number may contain different transaction dates, even though they represent a single accounting transaction.
These data inconsistencies can compromise accounting integrity and produce inaccurate financial reports.
References:
- ADR#004 How can we ensure imported journal data remains compatible with the reporting formulas?
Solution
Strengthen validation during the import process by:
- Validating that every imported Chart of Account (COA) has a valid Type and Category.
- Ensuring the selected COA Category matches the specified COA Type.
- Ensuring every journal transaction (same Form Number) uses a single transaction date.
These validations prevent invalid accounting data from entering the system and improve the reliability of financial reports.
Features
| Feature | Description |
|---|---|
| 3. Chart of Accounts | Structured list of all accounts used by a company to record financial transactions. |
| 3.1. Import Chart of Account | Upload chart of account data in bulk (CSV/Excel). |
| 4. Journals | Transaction management features for recording and reviewing financial journals. |
| 4.1. Import Journal | Upload transaction data in bulk (CSV/Excel) to create journal entries automatically. |
Scenarios
3.1. Import Journal
4.1. Import Journal
| 4.1.F Failed Scenarios |
|---|
| 4.1.F6. Journal import fails when rows with the same form number contain different dates. |