Evidence and process
How Bank2QBO is tested and reviewed.
Published by John Moores for Mockup Maestro · Updated August 12, 2026
Purpose of this site
Bank2QBO exists to make a narrow, error-prone preparation task visible and testable: interpreting common bank CSV columns, reviewing normalized transactions, and creating a file for a supported manual-import workflow. It is not a general accounting publication and does not automate bookkeeping judgment.
Converter test matrix
Automated tests run against invented fixtures rather than customer data. They cover quoted descriptions containing commas, signed amounts, separate debit and credit fields, month-first and day-first dates, negative values shown in parentheses, stable transaction identifiers, duplicate supplied identifiers, normalized QuickBooks CSV output, and a complete QBO bank-statement envelope.
Failure tests reject unsupported decimal commas, impossible dates, rows containing both a debit and a credit, missing amounts, missing QBO bank/account identifiers, missing closing balances, and credit-card QBO envelopes. Those tests verify what Bank2QBO creates; they cannot reproduce every validation rule applied by every QuickBooks version or financial institution.
How original examples are produced
Examples use invented businesses, merchants, dates, amounts, and references. We calculate the row count, debit/credit direction, and net movement so a reader can independently verify the example. Downloadable fixtures are stored with the site so their exact structure can be inspected without an account.
How product claims are checked
Claims about current QuickBooks import formats and workflows are checked against first-party Intuit QuickBooks Support pages linked at the end of each guide. We distinguish those external product rules from behavior controlled by Bank2QBO. If the receiving product differs from a guide, its current interface and documentation take precedence.
Authorship and review
John Moores publishes Bank2QBO through Mockup Maestro and is responsible for the product scope, editorial decisions, and release approval. The guides do not claim professional accounting credentials. They provide technical file-preparation guidance and consistently direct bookkeeping, tax, and reconciliation judgments back to the user or a qualified professional.
Change record
| Date | Material change | Reason |
|---|---|---|
| July 25, 2026 | Initial converter, privacy pages, and guide library | Publish a complete local-processing workflow |
| August 3, 2026 | Normalized CSV became primary; QBO requirements and limitations were made explicit; content and trust pages expanded | Correct compatibility claims and improve testable user value |
| August 12, 2026 | Added the independent readiness diagnostic, downloadable fixtures, named authorship, and this methodology | Expose original work, reproducible controls, and accountability |
Report a reproducible problem
Use the contact instructions and provide the product/version, output format, exact non-sensitive error, and a fictional sample that preserves the relevant layout. Do not send bank statements, account identifiers, credentials, or customer data.