Skip to content
Quillix docs
Home Support Open app → (opens in a new tab)

Bank Reconciliation

Where Sidebar › Accounting › Bank Reconciliation

Matches a bank statement against the client's open invoices and bills. Two hard problems are solved here: every Indian bank exports a differently-shaped spreadsheet, and customers pay net of TDS so the amount that lands never equals the invoice.

TDS is handled for you
A payment received net of TDS still settles its invoice in full. That is deliberate — matching on the bare amount would leave a small permanent residue on exactly the invoices that matter most.
SCREENSHOT · statement lines with their status pills — Recommended, Settled, Review, Suspense — beside the documents they were matched to

Upload and map a statement

  1. Choose the bank account and upload the statement file.
  2. Pick the sheet if the workbook has more than one.
  3. Check the columns Quillix detected and correct any it got wrong, then continue to reconcile.
  4. Set the bank ledger name to exactly what it is called in the client's Tally company — before exporting, not after.
Note
Quillix knows the common header wordings used by SBI, HDFC, ICICI, Axis, Kotak and others, and skips the preamble rows above the real header. For an unusual bank you map the columns once and it is remembered. Download template gives you a blank in the expected shape for a client whose export is unusable.

Confirm the proposed matches

Quillix pairs each statement line to an open document — credits to customer invoices, debits to vendor bills — using amount, party, date and reference together.

  1. Work down the proposed matches and Accept the ones that are right.
  2. Use Change on any line matched to the wrong document.
  3. Leave nothing unresolved: what you settle here is exactly what Bank Export will post.

Lines that are not settlements

Not every bank line pays an invoice. Charges, transfers and direct expenses are posted to a ledger instead.

  1. Choose Categorize on the line and pick the ledger it belongs to.
  2. Set up auto-categorisation rules for lines that recur every month, so they are classified for you next time.
  3. For an advance, an opening balance, or a lump payment that does not settle any one invoice, use the on-account option and pick the party. Where the amount covers several documents, allocate it across them instead.
  4. Exclude a line that should not post at all — a duplicate row, or one already booked another way. It stays visible with an Excluded status.
Two easy mistakes
On account is right for a genuine advance and wrong for a payment whose invoice you simply have not found — that one is worth chasing, because it will sit on the party ledger unreconciled. And excluding beats deleting: next month's statement shows the same line, and an excluded row records that it was a decision rather than an oversight.

What each row status means

Recommended
A match is proposed and waiting for you to accept it.
Settled
Matched to a document and done.
On account
Posted to a party ledger with no specific document.
Categorized
Posted to a ledger rather than settling anything.
Transfer
Moved between the client's own accounts.
Review
Quillix could not decide. This one needs you.
Suspense
Parked, and will post to the suspense ledger as it stands.
Excluded
Deliberately left out of the posting altogether.
Work them in this order
Review rows first, then Recommended. Anything still on Suspense at the end is what will land in the client's books unexplained.

Stop part-way and come back

  1. Leave the page whenever you need to — resolved lines are saved as a working draft and nothing is lost.
  2. When you return, Quillix offers to resume your last reconciliation. Choose Resume to pick up where you stopped.
  3. Uploaded statements are kept — pick from the saved statements list, newest first, rather than finding the original file again.
What Discard actually discards
The matching you had already done, not the statement. You would have to work through the lines again.

Last updated