25 financial data quality checks before trusting ERP reports

Twenty-five financial data quality checks a CFO should run before trusting ERP reports: completeness, balance, mapping, duplicates, subledgers, cut-off, FX and VAT.

4 min read
In short

An ERP report is only as good as the books under it. Before trusting a P&L, balance sheet or cash number, check that the data is complete and current, that it balances, that every account is mapped, that nothing is entered twice, that subledgers agree to the ledger and that cut-off, currency and VAT are right. The 25 checks below take a few hours by hand and can run automatically every day.

Why check the data before the report?

Most wrong board numbers are not calculation errors. They come from a sync that stopped, an account nobody mapped, a bill entered twice, a month with no depreciation or a balance in the wrong currency. A report can add up perfectly and still be wrong. The checks below look at the data itself, so a problem is caught before anyone reads the report.

Is the data complete and current? (checks 1–5)

#CheckWhat it catches
1Last successful sync or import for each companyA company whose numbers stopped updating
2Months with no entries inside each company's historyA missing month that makes year-to-date look better or worse
3Regular costs missing in a month (rent, payroll, depreciation)A recurring journal that was not posted
4Gaps in journal numberingEntries deleted, cancelled or left out of the extract
5Entries dated in the futureTyping errors that move income or cost into another period

Do the books balance and sit on the right side? (checks 6–9)

#CheckWhat it catches
6The trial balance balances for each company and monthA broken extract or an unbalanced import
7Every journal balancesOne-sided entries from manual uploads or interfaces
8Balances on the wrong side (assets in credit, liabilities in debit)Misposted entries and missing reclassifications
9Suspense and clearing accounts are clearedUnexplained amounts parked until the auditors ask

Is every account where the report expects it? (checks 10–13)

#CheckWhat it catches
10Every account with activity is mapped to the management reportCosts that silently drop out of the P&L
11Every account has a type and classificationAccounts that land in the wrong statement
12No postings to closed or heading accountsEntries the report layout does not pick up
13No two accounts that look the sameDuplicated accounts splitting one balance in two

Is anything entered twice or reversed? (checks 14–17)

#CheckWhat it catches
14Journals that look entered twiceThe same booking posted by two people or two interfaces
15Supplier bills entered twiceDouble payments waiting to happen
16Customers or suppliers entered twiceBalances split across two records of the same party
17Entries reversed and posted againCorrections that were themselves corrected, or doubled

Do the subledgers agree to the ledger? (checks 18–21)

#CheckWhat it catches
18Open customer invoices equal receivables in the ledgerInvoices or receipts posted outside the subledger
19Open supplier bills equal payables in the ledgerBills booked straight to the ledger
20Receivable and payable lines all carry a customer or supplierBalances nobody can chase or pay
21Bank balance in the books agrees to the statement, with no old unmatched linesMissing receipts, payments or bank charges

Are currency and VAT right? (checks 22–25)

#CheckWhat it catches
22Exchange rates exist for every company that reports in another currencyGroup figures translated at a stale or missing rate
23Bills carry input VAT, and sales carry output VAT, where they shouldVAT missed on purchases or under-declared on sales
24Bills from abroad carry the reverse chargeImported services left out of the VAT return
25VAT at the standard rate, with the supplier's VAT number on input VATWrong rates and input VAT that cannot be reclaimed

How often should these checks run?

Completeness and balance checks every time the books sync, so a broken feed is caught the same day. The rest before each month-end sign-off, and again before a board pack or a tax return leaves the building. A check that could not run should say so; "not checked" is never the same as "clear".

Questions people ask

Which check matters most?

That every account with activity is mapped. An unmapped account drops out of the management report without any error message.

Can these checks run in Excel?

Yes, from a trial balance and a journal export, but it takes hours each month and is rarely repeated after every sync.

Do auditors expect these checks?

Auditors test many of them themselves. Running them first, with evidence of what was found and fixed, makes the audit shorter.

What if our ERP already validates entries?

ERPs validate one entry at a time. Most of these checks look across entries, months and modules, which the ERP does not do.

Does a clean result mean the numbers are right?

It means the data can be trusted for reporting. Judgement on estimates, provisions and classification still belongs to the finance team.

Where Naarvin helps

See it on your own books

A guided demo on Demo Group's books, then we connect one of your companies. In Arabic or English.