FREE FINANCE OPERATIONS RESOURCE
Check your supplier ledger without connecting your bank.
Upload your own CSV to the free Billquiet beta. Billquiet suggests column matches and lets you confirm them, so you do not need to rename your headings. The template is optional. The first check runs in your browser. Signing in and saving sends the data for server-side checking and stores the findings; the original CSV is not stored.
1. Confirm the columns in your export
Match supplier, invoice reference and amount to your own headings. Select a currency column, or explicitly choose one currency for the entire file if every transaction uses that currency. Never use a single currency setting for mixed-currency data. Payment status and payment references are optional; without them you can still review repeated invoice references, inconsistent amounts and credits.
Use one row per transaction
The template contains fictional examples. Replace them before reviewing your own ledger. Keep each currency separate in your accounting records; Billquiet never converts or adds different currencies together.
- vendor, invoice
- Supplier name and invoice reference are required. Include the year when invoice numbers are reused. If your file has both amount and total columns, choose the intended amount in the import preview. Extra columns can be left unused.
- amount, currency
- Use a decimal amount such as 1234.56 and USD, EUR, GBP, CHF, CAD or AUD. Negative amounts are credits to reconcile. Do not mix gross and net amounts in the same comparison.
- status, payment_id
- Optional but needed to flag possible duplicate payments. Use paid or settled only for settled transactions. A payment ID should identify a distinct payment, not merely an export row. Do not invent missing IDs.
- date
- Optional context. Dates are not currently used in duplicate matching. Put the year in the invoice reference if needed to distinguish invoices.
2. Run the check and verify the evidence
Two paid records for the same supplier and invoice, the same amount and currency, and different payment IDs raise a possible duplicate. Repeated rows with the same payment ID do not establish a second payment. These checks cannot verify bank settlement, installments, supplier identity or recovery.
3. Fix common import errors
- Unrecognized heading: choose the matching column in the import preview. Supplier, invoice reference and amount must be present; currency can be provided per row or explicitly set for a single-currency file.
- Ambiguous columns: confirm the intended column in the import preview, using the first-row example. Billquiet does not silently choose between competing amount columns.
- Wrong number of columns: export as CSV, not an Excel workbook. Quote fields containing commas. A semicolon-separated file can contain decimal commas.
- Ambiguous amount: remove thousands separators and use at most two decimal places. For example, replace 1,234 with 1234.00 if that is the intended amount.
- File or report too large: split by supplier or period. The current limits are 1 MB, 5,000 rows and 250 findings per check.
Need help or want to dispute a finding?
Contact Jamie about support, billing or privacy. No account is required to email us. Describe the error and use fictional example rows; do not include bank credentials or payment card details. A finding can be a legitimate transaction: check the source evidence before contacting a supplier.
Requests are reviewed through the scheduled operating audit. This beta does not offer instant live support or a guaranteed response time. No real payments are currently enabled.
Worked duplicate-payment example · Method and limitations · Privacy and beta terms