Check a journal upload beyond debits equaling credits

Keep the approved upload file, its supporting calculation, and the reviewer decision together. Record the entity, accounting date, currency, and intended batch reference. If someone changes a value or account after approval, identify the revision and obtain the required review before posting. Approval of a calculation does not automatically cover a later export with different columns or filters.

Separate the file used for calculation from the final import format when the system requires reshaping. Save both versions and explain how one produces the other. The connection matters when formulas are converted to values, zero rows are removed, or a single amount is split across several departments. Each transformation creates a place where an otherwise correct journal can change.

Equal debits and credits establish balance, but a duplicated balanced journal still passes that check. Compare the row count, number of distinct journal references, gross debit total, gross credit total, and expected totals by entity or important dimension. The following checks answer different questions, so retain the ones relevant to the upload.

ICAEW's spreadsheet principles recommend built-in checks and testing proportionate to workbook risk. Apply those principles to the import boundary as well as the calculation sheet, especially where the accounting application transforms or rejects rows.

After import, retain the application's result report or equivalent posting evidence. Identify rejected rows and determine whether the accepted portion became a posted journal, a draft, or no entry at all. Do not infer success from an uploaded-file message. The relevant result is the ledger population that the accounting team can inspect.

For a hypothetical four-journal batch, suppose three journals post and the fourth fails validation. Resubmitting all four without checking the application's duplicate behavior can repeat the first three. Reconcile accepted references first, then prepare a controlled correction or resubmission for the failed portion. Verify product-specific behavior in the actual system before choosing the method.

Export or inspect the posted entries using their final ledger references. Match accounts, dates, signs, currencies, amounts, and dimensions to the approved file. Check any fields that the import does not preserve, such as descriptions or supporting-document links, and attach the missing evidence through the normal workflow. A balanced batch should still be understandable to its future reviewer.

Record the batch as complete only after explaining all rejected or changed rows. Where a correction is necessary, retain both the original result and the authorized repair. Feed recurring import errors back into the source template, then test the affected field with a controlled example. The retained packet should let another accountant establish exactly what was approved, what posted, and how the differences were resolved.