Reconciliation record
TxnFlow imports a statement only when its transactions add up to the balances the bank printed. This page records, month by month, how often that happened on the first parse.
Last reviewed
Not enough data yet.
A month is published once at least 20 people and 50 uploads have gone through it, and no one person made more than a quarter of those uploads, so that no figure describes a handful of people.
How each figure is worked out
- An upload is one file. It is counted once, in the UTC calendar month its first parse started, by what happened at that first parse. A later re-run never changes its month's figures.
- Imported on the first parse: the statement's transactions added up to the balances the bank printed, so the upload went through. This includes a file uploaded again whose transactions were all already there, so nothing new was added.
- Withheld by the check: the transactions did not add up, so none of them were imported. Some of these were imported later, after the person typed in the balance the statement printed; those are shown separately and still count as withheld, because the first parse did not read them right.
- Failed before the check: the file could not be read far enough to be checked.
- Re-run before an outcome was recorded: the first parse found nothing new, and the file was parsed again or deleted before we could tell why. These count against the imported share, although some of them were simply duplicates.
- Not known: a first parse past the fair-use allowance leaves no record of its outcome once the file is re-run or deleted. They are listed, and left out of every share.
- Shares are over the uploads whose outcome is known, to one decimal place.
- People are the distinct accounts behind the uploads whose outcome is known. The accounts set up as TxnFlow's administrator accounts are always left out. A month is published only if no one person made more than a quarter of its uploads whose outcome is known.
- Institutions are counted, never named: the number of banks and card issuers with at least one statement that added up that month. Different spellings of one bank's name can make it count twice, so the count may run slightly high.
- File size: at least five people each imported, on its first parse, a file of this many pages or more (1, 10, 25, 50, 100, 200 or 500). It never describes one upload, and it is left blank when fewer than five people imported a file.
- Frozen: each month is published once, on the date shown, and never revised. Deleting an account later does not change a published month.
The check itself
Opening balance plus credits minus debits must equal the closing balance the bank printed (on a credit card, opening plus debits minus credits). A difference under 0.02 is a match, under 0.10 is rounding, and 0.10 or more is held back for review: nothing is imported unless it reconciles. Try the check on your own figures.
What this is not
It is not a measure of how often every row was read right. A statement can add up and still hold a reading that is wrong in a way that cancels out, such as two errors of the same size. The check catches a missed or misread row; it cannot catch every possible mistake. That is why each statement stays reviewable in the app.